dashboard setup#1
Merged
Merged
Conversation
mmabrouk
pushed a commit
that referenced
this pull request
Aug 6, 2023
Format Python code with psf/black push
aakrem
pushed a commit
that referenced
this pull request
Aug 31, 2023
…ions ci/cd: added github actions for agenta-web
aybruhm
added a commit
that referenced
this pull request
Nov 28, 2024
…r `$ref=#/components/schemas/agenta_backend__models__api__evaluation_model__LMProvidersEnum-Input__1` see fix [#1](https://github.com/Agenta-AI/agenta_cloud/commit/3770adabaa1d0dd415db5ec18e4630e4f2dc1bcd)
christseng89
added a commit
to christseng89/agenta
that referenced
this pull request
Oct 18, 2025
ardaerzin
added a commit
that referenced
this pull request
Dec 2, 2025
VahantSharma
added a commit
to VahantSharma/agenta
that referenced
this pull request
Dec 20, 2025
- Add shouldIgnoreRowClick guard to AppTable row click handler - Add shouldIgnoreRowClick guard to VariantsTable row click handler - Fixes issue where clicking checkboxes or dropdown menus triggers row navigation - Affects app management page and all variant table contexts (overview, deployment, evaluation) Builds on shared utility from PR Agenta-AI#1
VahantSharma
added a commit
to VahantSharma/agenta
that referenced
this pull request
Dec 20, 2025
- Add shouldIgnoreRowClick guard to AppTable row click handler - Add shouldIgnoreRowClick guard to VariantsTable row click handler - Fixes issue where clicking checkboxes or dropdown menus triggers row navigation - Affects app management page and all variant table contexts (overview, deployment, evaluation) Builds on shared utility from PR Agenta-AI#1
VahantSharma
added a commit
to VahantSharma/agenta
that referenced
this pull request
Dec 24, 2025
- Add shouldIgnoreRowClick guard to AppTable row click handler - Add shouldIgnoreRowClick guard to VariantsTable row click handler - Fixes issue where clicking checkboxes or dropdown menus triggers row navigation - Affects app management page and all variant table contexts (overview, deployment, evaluation) Builds on shared utility from PR Agenta-AI#1
ardaerzin
added a commit
that referenced
this pull request
Feb 5, 2026
…ayground-entities-package-updates [Frontend] App playground local mode #1 - entities package update
ardaerzin
added a commit
that referenced
this pull request
Apr 30, 2026
JP shipped the TS Fern client with a default generators.yml ("0 seconds
configuring Fern, maybe we need to re-generate"). Adds a config: block
that addresses the bulk of the PoC's documented build/runtime issues at
the source instead of via per-app workarounds.
clients/scripts/generate.sh
- omitFernHeaders: true — drops X-Fern-* headers the
Agenta API CORS allowlist doesn't accept (PoC finding #5)
- includeCredentialsOnCrossOriginRequests: true — withCredentials
baked into every request so cookie-session auth works without a
custom fetch wrapper (was finding in convenience layer)
- fetchSupport: native, streamType: web, formDataSupport: Node18,
fileResponseType: binary-response — prefer browser/web standards
- retainOriginalCasing: true — keep wire snake_case (matches
backend, OpenAPI spec, v2 entities Zod schemas; camelCase conversion
would break ~all existing consumer code)
- defaultTimeoutInSeconds: 30, maxRetries: 3 — explicit network
defaults aligned with v2 stage-0 client
- packageJson.browser: { fs/stream/buffer: false } + devDependencies:
@types/node — bake the browser-stub and node types into the
generated package.json (PoC findings #1 and #2)
clients/typescript/package.json (bootstrap heredoc): mirror the same
browser field + @types/node devDep so the static bootstrap matches.
generate.sh adds fix_typescript_admin_duplicates: a Python post-gen
patch that renames the second `createAccounts` (and its private __
partner) to `createAccountsAlt`. Two OpenAPI operations resolve to the
same TS function name — backend should disambiguate via explicit
operation_id. Admin endpoints aren't in v0 scope so the rename is safe.
Serde stays OFF: noSerdeLayer: false + allowExtraFields exposed ~200
codegen errors in fern-typescript-sdk@3.63.7 (broken
Record<string, T | null> handling, recursive type aliases for
FullJson*/LabelJson*, plus the duplicate methods). Documented in
generate.sh inline. The convenience layer's Zod boundary continues to
handle Pydantic extra="allow" at the entity level instead.
web/packages/agenta-sdk/src/index.ts: slim the fetch wrapper now that
omitFernHeaders + withCredentials are upstream. The wrapper is only
non-undefined when no apiKey was supplied — strips the empty
Authorization header HeaderAuthProvider sets in the cookie-auth case.
Verified: pnpm install clean; @agenta/sdk + @agenta/entities typecheck
+ lint pass; @agenta/client builds standalone (tsc with no errors);
next dev --turbopack on web/ee returns HTTP 200 on /w (was 500 before
the CORS fix) with no Module-not-found errors; next build on web/oss
completes successfully.
ardaerzin
added a commit
that referenced
this pull request
Jun 1, 2026
After Arda's note that tracing works on main but not on our branch (suspected interaction between PR #4469 and our merge), did a full static-analysis pass on the FE tracing pipeline. Findings: * All tracing-related FE files are BYTE-IDENTICAL to main — `runnableSetup.ts` (references builder), the two tracing API endpoint files, `executionItems.ts` references-passing block, `store.ts` sourceRef setter. * All commits from PR #4491 (`fix/broken-tracing-and-workflow-events`, the fix JP shipped after PR #4469 broke tracing) are reachable from branch HEAD — `b1b5b899df`, `83495a340a`, `601c9de468`, `69379a9f04`, `301f74f65f`, `92be0a87e2`. * Our branch's actual diff vs main does NOT touch the trace pipeline, references building, sourceRef construction, or tracing endpoints. The diff is mustache token plugin, playground inputs body, visibility rule, template format picker, schema-aware seeding, view-type ordering, chat single- testcase gate, native-vs-stringified input transport. Recorded three plausible hypotheses in the inventory: 1. Premise re-check — "main works" may need re-verification with the same repro Mahmoud used. 2. Indirect effect from native-input transport — the only semantically meaningful FE change that touches the request body. Backend trace-save might choke on nested-object inputs even though trace_id was already returned. 3. Environmental — staging state, build cache, env var. Not code. Recommended next steps documented in inventory: re-verify main → capture wire-format diff → hand off to JP if backend-side.
ardaerzin
added a commit
that referenced
this pull request
Jun 1, 2026
…rk locally
Confirmed via:
* Local HEAD == origin HEAD (`396ecd5eda`).
* `origin/main` (`d7c60c14e6`, frozen since 2026-06-01 10:21Z, i.e.
6 minutes BEFORE Mahmoud's tracing report) is an ancestor of our
HEAD.
* `origin/feat/add-mustache-rendering` (`a12751604a`, Arda's main-
merge at 15:08Z) is an ancestor of our HEAD via merge
`8dd4da1870`.
* Static analysis earlier (commit `396ecd5eda`) confirmed all FE
tracing files (`runnableSetup.ts`, `tracing/api/index.ts`,
`trace/api/api.ts`, executionItems `payloadRefs` block) are
byte-identical to main.
* Arda re-tested locally on the synced branch and traces work.
Net read: Mahmoud's #1 was a transient state at QA time, almost
certainly the staging deploy catching FE post-#4469 / backend
pre-#4491 (or the inverse) before JP's tracing fix had fully
propagated. The code on our branch IS the post-fix state; staging
behaves like local once redeployed.
All nine inventory items now marked fixed/resolved.
ashrafchowdury
pushed a commit
that referenced
this pull request
Jun 4, 2026
After Arda's note that tracing works on main but not on our branch (suspected interaction between PR #4469 and our merge), did a full static-analysis pass on the FE tracing pipeline. Findings: * All tracing-related FE files are BYTE-IDENTICAL to main — `runnableSetup.ts` (references builder), the two tracing API endpoint files, `executionItems.ts` references-passing block, `store.ts` sourceRef setter. * All commits from PR #4491 (`fix/broken-tracing-and-workflow-events`, the fix JP shipped after PR #4469 broke tracing) are reachable from branch HEAD — `b1b5b899df`, `83495a340a`, `601c9de468`, `69379a9f04`, `301f74f65f`, `92be0a87e2`. * Our branch's actual diff vs main does NOT touch the trace pipeline, references building, sourceRef construction, or tracing endpoints. The diff is mustache token plugin, playground inputs body, visibility rule, template format picker, schema-aware seeding, view-type ordering, chat single- testcase gate, native-vs-stringified input transport. Recorded three plausible hypotheses in the inventory: 1. Premise re-check — "main works" may need re-verification with the same repro Mahmoud used. 2. Indirect effect from native-input transport — the only semantically meaningful FE change that touches the request body. Backend trace-save might choke on nested-object inputs even though trace_id was already returned. 3. Environmental — staging state, build cache, env var. Not code. Recommended next steps documented in inventory: re-verify main → capture wire-format diff → hand off to JP if backend-side.
ashrafchowdury
pushed a commit
that referenced
this pull request
Jun 4, 2026
…rk locally
Confirmed via:
* Local HEAD == origin HEAD (`396ecd5eda`).
* `origin/main` (`d7c60c14e6`, frozen since 2026-06-01 10:21Z, i.e.
6 minutes BEFORE Mahmoud's tracing report) is an ancestor of our
HEAD.
* `origin/feat/add-mustache-rendering` (`a12751604a`, Arda's main-
merge at 15:08Z) is an ancestor of our HEAD via merge
`8dd4da1870`.
* Static analysis earlier (commit `396ecd5eda`) confirmed all FE
tracing files (`runnableSetup.ts`, `tracing/api/index.ts`,
`trace/api/api.ts`, executionItems `payloadRefs` block) are
byte-identical to main.
* Arda re-tested locally on the synced branch and traces work.
Net read: Mahmoud's #1 was a transient state at QA time, almost
certainly the staging deploy catching FE post-#4469 / backend
pre-#4491 (or the inverse) before JP's tracing fix had fully
propagated. The code on our branch IS the post-fix state; staging
behaves like local once redeployed.
All nine inventory items now marked fixed/resolved.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.