notifications  

Messages by Thread

• • Re: [PR] fix(test, frontend): stop the agent-panel tab test depending on nz-tabs click timing [texera] via GitHub
• [I] Should a table with no rows keep its declared schema? [texera] via GitHub
  • Re: [I] Should a table with no rows keep its declared schema? [texera] via GitHub
  • Re: [I] Should a table with no rows keep its declared schema? [texera] via GitHub
  • Re: [I] Should a table with no rows keep its declared schema? [texera] via GitHub
  • Re: [I] Should a table with no rows keep its declared schema? [texera] via GitHub
• [PR] refactor(amber): use region links in Fries for cache reuse [texera] via GitHub
  • Re: [PR] refactor(amber): use region links in Fries for cache reuse [texera] via GitHub
  • Re: [PR] refactor(amber): use region links in Fries for cache reuse [texera] via GitHub
  • Re: [PR] refactor(amber): use region links in Fries for cache reuse [texera] via GitHub
  • Re: [PR] refactor(amber): use region links in Fries for cache reuse [texera] via GitHub
• [PR] feat(amber): schedule a run with cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): schedule a run with cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): schedule a run with cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): schedule a run with cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): schedule a run with cache reuse [texera] via GitHub
• [PR] feat(amber): schedule saved-result reads for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): schedule saved-result reads for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): schedule saved-result reads for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): schedule saved-result reads for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): schedule saved-result reads for cache reuse [texera] via GitHub
• [PR] feat(amber): decide what a run skips for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): decide what a run skips for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): decide what a run skips for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): decide what a run skips for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): decide what a run skips for cache reuse [texera] via GitHub
  • Re: [PR] feat(amber): decide what a run skips for cache reuse [texera] via GitHub
• [PR] fix(amber, v1.2): bump filelock and imageio in LICENSE-binary-python [texera] via GitHub
  • Re: [PR] fix(amber, v1.2): bump filelock and imageio in LICENSE-binary-python [texera] via GitHub
  • Re: [PR] fix(amber, v1.2): bump filelock and imageio in LICENSE-binary-python [texera] via GitHub
• [PR] refactor(blog): unify blog post styling in a shared stylesheet [incubator-texera-site] via GitHub
• Re: [PR] feat(workflow): freeze a pinned version as the public copy [texera] via GitHub
  • Re: [PR] feat(workflow): freeze a pinned version as the public copy [texera] via GitHub
  • Re: [PR] feat(workflow): freeze a pinned version as the public copy [texera] via GitHub
  • Re: [PR] feat(workflow): freeze a pinned version as the public copy [texera] via GitHub
  • Re: [PR] feat(workflow): freeze a pinned version as the public copy [texera] via GitHub
  • Re: [PR] feat(workflow): freeze a pinned version as the public copy [texera] via GitHub
  • Re: [PR] feat(workflow): freeze a pinned version as the public copy [texera] via GitHub
• Re: [PR] fix(amber, frontend): inline Hugging Face audio uploads as data URLs instead of a server temp file [texera] via GitHub
  • Re: [PR] fix(amber, frontend): inline Hugging Face audio uploads as data URLs instead of a server temp file [texera] via GitHub
  • Re: [PR] fix(amber, frontend): inline Hugging Face audio uploads as data URLs instead of a server temp file [texera] via GitHub
  • Re: [PR] fix(amber, frontend): inline Hugging Face audio uploads as data URLs instead of a server temp file [texera] via GitHub
• [PR] fix(gui): release the previous row's work when the result modal navigates [texera] via GitHub
  • Re: [PR] fix(gui): release the previous row's work when the result modal navigates [texera] via GitHub
  • Re: [PR] fix(gui): release the previous row's work when the result modal navigates [texera] via GitHub
  • Re: [PR] fix(gui): release the previous row's work when the result modal navigates [texera] via GitHub
  • Re: [PR] fix(gui): release the previous row's work when the result modal navigates [texera] via GitHub
  • Re: [PR] fix(gui): release the previous row's work when the result modal navigates [texera] via GitHub
• Re: [PR] chore(deps, ci): update github-actions [texera] via GitHub
  • Re: [PR] chore(deps, ci): update github-actions [texera] via GitHub
  • Re: [PR] chore(deps, ci): update github-actions [texera] via GitHub
  • [PR] chore(deps, ci): update github-actions [texera] via GitHub
  • Re: [PR] chore(deps, ci): update github-actions [texera] via GitHub
  • Re: [PR] chore(deps, ci): update github-actions [texera] via GitHub
  • Re: [PR] chore(deps, ci): update github-actions [texera] via GitHub
• Re: [PR] feat(operator-demo-video): add login and workflow-navigation controllers [texera] via GitHub
  • Re: [PR] feat(operator-demo-video): add login and workflow-navigation controllers [texera] via GitHub
• Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
  • Re: [PR] chore(deps, agent-service): update agent-service patch updates [texera] via GitHub
• Re: [PR] fix(pyamber): keep LinkedBlockingMultiQueue priority groups sorted [texera] via GitHub
  • Re: [PR] fix(pyamber): keep LinkedBlockingMultiQueue priority groups sorted [texera] via GitHub
  • Re: [PR] fix(pyamber): keep LinkedBlockingMultiQueue priority groups sorted [texera] via GitHub
• Re: [PR] feat: Added backend routes to export workflows + datasets to google drive [texera] via GitHub
  • Re: [PR] feat: Added backend routes to export workflows + datasets to google drive [texera] via GitHub
  • Re: [PR] feat: Added backend routes to export workflows + datasets to google drive [texera] via GitHub
• Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
  • Re: [PR] feat(frontend): add admin computing units dashboard [texera] via GitHub
• Re: [PR] feat(engine): add TryCatch/Finally control blocks with in-band error handling [texera] via GitHub
  • Re: [PR] feat(engine): add TryCatch/Finally control blocks with in-band error handling [texera] via GitHub
• Re: [PR] chore(deps, pyamber): update dependency sqlalchemy to v2.0.52 [texera] via GitHub
  • Re: [PR] chore(deps, pyamber): update dependency sqlalchemy to v2.0.52 [texera] via GitHub
  • Re: [PR] chore(deps, pyamber): update dependency sqlalchemy to v2.0.52 [texera] via GitHub
• Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
  • Re: [PR] feat(local-dev): detect the host LAN IP on Windows [texera] via GitHub
• Re: [PR] refactor(service): unify Dropwizard service bootstrap into common/auth [texera] via GitHub
  • Re: [PR] refactor(service): unify Dropwizard service bootstrap into common/auth [texera] via GitHub
  • Re: [PR] refactor(service): unify Dropwizard service bootstrap into common/auth [texera] via GitHub
  • Re: [PR] refactor(service): unify Dropwizard service bootstrap into common/auth [texera] via GitHub
• Re: [PR] refactor(agent-service): centralize backend DTOs, metadata, endpoint config, and auth [texera] via GitHub
  • Re: [PR] refactor(agent-service): centralize backend DTOs, metadata, endpoint config, and auth [texera] via GitHub
• Re: [PR] refactor(agent-service): isolate HTTP clients [texera] via GitHub
  • Re: [PR] refactor(agent-service): isolate HTTP clients [texera] via GitHub
• Re: [PR] refactor(amber): remove redundant result-readiness wait in SyncExecutionResource [texera] via GitHub
  • Re: [PR] refactor(amber): remove redundant result-readiness wait in SyncExecutionResource [texera] via GitHub
• Re: [PR] refactor(access-control-service): reuse SecurityContext to skip duplicate JWT parse [texera] via GitHub
  • Re: [PR] refactor(access-control-service): reuse SecurityContext to skip duplicate JWT parse [texera] via GitHub
• Re: [PR] feat(agent): call LiteLLM directly and authenticate the agent-service [texera] via GitHub
  • Re: [PR] feat(agent): call LiteLLM directly and authenticate the agent-service [texera] via GitHub
• Re: [PR] feat: route computing-unit metadata over HTTP, off Postgres [texera] via GitHub
  • Re: [PR] feat: route computing-unit metadata over HTTP, off Postgres [texera] via GitHub
• Re: [PR] feat(agent-service): add opt-in access control and per-user isolation [texera] via GitHub
  • Re: [PR] feat(agent-service): add opt-in access control and per-user isolation [texera] via GitHub
• Re: [PR] feat(agent-service): persist agent state to disk and rehydrate on startup [texera] via GitHub
  • Re: [PR] feat(agent-service): persist agent state to disk and rehydrate on startup [texera] via GitHub
• Re: [PR] feat(frontend): Support flow control (backpressure) visualization in frontend [texera] via GitHub
  • Re: [PR] feat(frontend): Support flow control (backpressure) visualization in frontend [texera] via GitHub
• Re: [PR] fix(python): improve in-memory size estimation for queue items [texera] via GitHub
  • Re: [PR] fix(python): improve in-memory size estimation for queue items [texera] via GitHub
• Re: [PR] feat(backend): Support flow control (backpressure) visualization in backend [texera] via GitHub
  • Re: [PR] feat(backend): Support flow control (backpressure) visualization in backend [texera] via GitHub
• [I] Align schema validation across the four legacy Hugging Face operators [texera] via GitHub
  • Re: [I] Align schema validation across the four legacy Hugging Face operators [texera] via GitHub
  • Re: [I] Align schema validation across the four legacy Hugging Face operators [texera] via GitHub
  • Re: [I] Align schema validation across the four legacy Hugging Face operators [texera] via GitHub
  • Re: [I] Align schema validation across the four legacy Hugging Face operators [texera] via GitHub
• [I] Row details modal leaks blob URLs and can show a stale row when navigating [texera] via GitHub
  • Re: [I] Row details modal leaks blob URLs and can show a stale row when navigating [texera] via GitHub
• [PR] fix(deploy, v1.3): load example datasets against the account's real email [texera] via GitHub
  • Re: [PR] fix(deploy, v1.3): load example datasets against the account's real email [texera] via GitHub
  • Re: [PR] fix(deploy, v1.3): load example datasets against the account's real email [texera] via GitHub
  • Re: [PR] fix(deploy, v1.3): load example datasets against the account's real email [texera] via GitHub
  • Re: [PR] fix(deploy, v1.3): load example datasets against the account's real email [texera] via GitHub
• [PR] fix(deploy, v1.2): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy, v1.2): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy, v1.2): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy, v1.2): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
• [PR] fix(deploy, v1.3): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy, v1.3): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy, v1.3): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy, v1.3): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy, v1.3): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
• [PR] fix(deploy): load example datasets against the account's real email [texera] via GitHub
  • Re: [PR] fix(deploy): load example datasets against the account's real email [texera] via GitHub
  • Re: [PR] fix(deploy): load example datasets against the account's real email [texera] via GitHub
  • Re: [PR] fix(deploy): load example datasets against the account's real email [texera] via GitHub
  • Re: [PR] fix(deploy): load example datasets against the account's real email [texera] via GitHub
• [PR] fix(deploy): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
  • Re: [PR] fix(deploy): lift nginx's 1 MiB body cap that rejects dataset upload parts [texera] via GitHub
• [I] up --with-examples leaves both example datasets empty, and the loader reports success anyway [texera] via GitHub
  • Re: [I] up --with-examples leaves both example datasets empty, and the loader reports success anyway [texera] via GitHub
  • Re: [I] up --with-examples leaves both example datasets empty, and the loader reports success anyway [texera] via GitHub
• Re: [PR] [prototype] feat(amber): schedule loops with materialized boundaries instead of a fully materialized workflow [texera] via GitHub
• Re: [PR] chore(amber): remove the unused UpdateRecoveryStatus and ResendOutputTo payloads [texera] via GitHub
• Re: [I] Remove the unused UpdateRecoveryStatus and ResendOutputTo recovery payloads [texera] via GitHub
• [PR] refactor(deploy): remove the standalone python-language-server manifest [texera] via GitHub
  • Re: [PR] refactor(deploy): remove the standalone python-language-server manifest [texera] via GitHub
  • Re: [PR] refactor(deploy): remove the standalone python-language-server manifest [texera] via GitHub
• [I] Remove dead WorkflowUtilService members [texera] via GitHub
  • Re: [I] Remove dead WorkflowUtilService members [texera] via GitHub
• [I] Dataset uploads fail with 413 in the single-node deployment [texera] via GitHub
  • Re: [I] Dataset uploads fail with 413 in the single-node deployment [texera] via GitHub
• Re: [I] Remove the 19 unreferenced PropertyNameConstants [texera] via GitHub
• Re: [PR] chore(workflow-operator): remove the unreferenced PropertyNameConstants [texera] via GitHub
• [I] Remove the unused AdminExecutionComponent filters [texera] via GitHub
  • Re: [I] Remove the unused AdminExecutionComponent filters [texera] via GitHub
• [PR] refactor(frontend): remove the unused AdminExecutionComponent filters [texera] via GitHub
  • Re: [PR] refactor(frontend): remove the unused AdminExecutionComponent filters [texera] via GitHub
  • Re: [PR] refactor(frontend): remove the unused AdminExecutionComponent filters [texera] via GitHub
  • Re: [PR] refactor(frontend): remove the unused AdminExecutionComponent filters [texera] via GitHub
• [PR] refactor(frontend): remove dead WorkflowUtilService members [texera] via GitHub
  • Re: [PR] refactor(frontend): remove dead WorkflowUtilService members [texera] via GitHub
  • Re: [PR] refactor(frontend): remove dead WorkflowUtilService members [texera] via GitHub
  • Re: [PR] refactor(frontend): remove dead WorkflowUtilService members [texera] via GitHub
• [I] Remove the standalone python-language-server Kubernetes manifest [texera] via GitHub
  • Re: [I] Remove the standalone python-language-server Kubernetes manifest [texera] via GitHub
• Re: [PR] fix(pybuilder): recognize the Encodable marker on a trait member [texera] via GitHub
• Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
  • Re: [PR] fix(workflow): keep workflowSettings and formBinding in the shared model [texera] via GitHub
• Re: [I] release/v1.2: coursier/cache-action pin no longer on the ASF actions allowlist [texera] via GitHub
• Re: [I] Refactor the Dataset Detail Page into a Tab-Based Layout [texera] via GitHub
• [PR] feat(blog): add idle Kubernetes CU cleanup post [incubator-texera-site] via GitHub
  • Re: [PR] feat(blog): add idle Kubernetes CU cleanup post [incubator-texera-site] via GitHub
  • Re: [PR] feat(blog): add idle Kubernetes CU cleanup post [incubator-texera-site] via GitHub
  • Re: [PR] feat(blog): add idle Kubernetes CU cleanup post [incubator-texera-site] via GitHub
• [PR] feat: turn on per-user warehouses [texera] via GitHub
  • Re: [PR] feat: turn on per-user warehouses [texera] via GitHub
  • Re: [PR] feat: turn on per-user warehouses [texera] via GitHub
  • Re: [PR] feat: turn on per-user warehouses [texera] via GitHub
  • Re: [PR] feat: turn on per-user warehouses [texera] via GitHub
  • Re: [PR] feat: turn on per-user warehouses [texera] via GitHub
  • Re: [PR] feat: turn on per-user warehouses [texera] via GitHub

• Earlier messages
• Later messages