notifications  

Messages by Thread

• [PR] test(amber): cover the PVE websocket endpoint and the missing-interpreter guard [texera] via GitHub
  • Re: [PR] test(amber): cover the PVE websocket endpoint and the missing-interpreter guard [texera] via GitHub
  • Re: [PR] test(amber): cover the PVE websocket endpoint and the missing-interpreter guard [texera] via GitHub
  • Re: [PR] test(amber): cover the PVE websocket endpoint and the missing-interpreter guard [texera] via GitHub
  • Re: [PR] test(amber): cover the PVE websocket endpoint and the missing-interpreter guard [texera] via GitHub
  • Re: [PR] test(amber): cover the PVE websocket endpoint and the missing-interpreter guard [texera] via GitHub
• [PR] fix(pyamber): add_sub_queue replaces existing sub-queue instead of using putIfAbsent semantics [texera] via GitHub
  • Re: [PR] fix(pyamber): add_sub_queue replaces existing sub-queue instead of using putIfAbsent semantics [texera] via GitHub
  • Re: [PR] fix(pyamber): add_sub_queue replaces existing sub-queue instead of using putIfAbsent semantics [texera] via GitHub
  • Re: [PR] fix(pyamber): add_sub_queue replaces existing sub-queue instead of using putIfAbsent semantics [texera] via GitHub
  • Re: [PR] fix(pyamber): add_sub_queue replaces existing sub-queue instead of using putIfAbsent semantics [texera] via GitHub
  • Re: [PR] fix(pyamber): add_sub_queue replaces existing sub-queue instead of using putIfAbsent semantics [texera] via GitHub
  • Re: [PR] fix(pyamber): add_sub_queue replaces existing sub-queue instead of using putIfAbsent semantics [texera] via GitHub
• [I] Close the remaining branch arms in the Hugging Face panel and two workflow-graph services [texera] via GitHub
  • Re: [I] Close the remaining branch arms in the Hugging Face panel and two workflow-graph services [texera] via GitHub
• [PR] fix(amber): report an uninitialized execution, not an NPE [texera] via GitHub
  • Re: [PR] fix(amber): report an uninitialized execution, not an NPE [texera] via GitHub
  • Re: [PR] fix(amber): report an uninitialized execution, not an NPE [texera] via GitHub
  • Re: [PR] fix(amber): report an uninitialized execution, not an NPE [texera] via GitHub
  • Re: [PR] fix(amber): report an uninitialized execution, not an NPE [texera] via GitHub
  • Re: [PR] fix(amber): report an uninitialized execution, not an NPE [texera] via GitHub
• [I] Cover the PVE websocket endpoint and the missing-interpreter guards [texera] via GitHub
  • Re: [I] Cover the PVE websocket endpoint and the missing-interpreter guards [texera] via GitHub
• [PR] test(auth, amber): cover the activity tracker upsert and the amber home path [texera] via GitHub
  • Re: [PR] test(auth, amber): cover the activity tracker upsert and the amber home path [texera] via GitHub
  • Re: [PR] test(auth, amber): cover the activity tracker upsert and the amber home path [texera] via GitHub
  • Re: [PR] test(auth, amber): cover the activity tracker upsert and the amber home path [texera] via GitHub
  • Re: [PR] test(auth, amber): cover the activity tracker upsert and the amber home path [texera] via GitHub
  • Re: [PR] test(auth, amber): cover the activity tracker upsert and the amber home path [texera] via GitHub
• [I] Cover the activity tracker upsert, the amber home path and the actor preStart catch [texera] via GitHub
  • Re: [I] Cover the activity tracker upsert, the amber home path and the actor preStart catch [texera] via GitHub
• [PR] test(frontend): cover the code editor's worker wiring and disposal ordering [texera] via GitHub
  • Re: [PR] test(frontend): cover the code editor's worker wiring and disposal ordering [texera] via GitHub
  • Re: [PR] test(frontend): cover the code editor's worker wiring and disposal ordering [texera] via GitHub
  • Re: [PR] test(frontend): cover the code editor's worker wiring and disposal ordering [texera] via GitHub
  • Re: [PR] test(frontend): cover the code editor's worker wiring and disposal ordering [texera] via GitHub
• [I] Cover the code editor's worker wiring, retry memo and language-server timeout [texera] via GitHub
  • Re: [I] Cover the code editor's worker wiring, retry memo and language-server timeout [texera] via GitHub
• [PR] fix(frontend): don't count dropped folders as failures [texera] via GitHub
  • Re: [PR] fix(frontend): don't count dropped folders as failures [texera] via GitHub
  • Re: [PR] fix(frontend): don't count dropped folders as failures [texera] via GitHub
  • Re: [PR] fix(frontend): don't count dropped folders as failures [texera] via GitHub
  • Re: [PR] fix(frontend): don't count dropped folders as failures [texera] via GitHub
• [PR] test(frontend): drive the workspace menu template through the DOM [texera] via GitHub
  • Re: [PR] test(frontend): drive the workspace menu template through the DOM [texera] via GitHub
  • Re: [PR] test(frontend): drive the workspace menu template through the DOM [texera] via GitHub
  • Re: [PR] test(frontend): drive the workspace menu template through the DOM [texera] via GitHub
  • Re: [PR] test(frontend): drive the workspace menu template through the DOM [texera] via GitHub
  • Re: [PR] test(frontend): drive the workspace menu template through the DOM [texera] via GitHub
• [PR] test(frontend): cover the search-instructions and agent settings panels [texera] via GitHub
  • Re: [PR] test(frontend): cover the search-instructions and agent settings panels [texera] via GitHub
  • Re: [PR] test(frontend): cover the search-instructions and agent settings panels [texera] via GitHub
  • Re: [PR] test(frontend): cover the search-instructions and agent settings panels [texera] via GitHub
  • Re: [PR] test(frontend): cover the search-instructions and agent settings panels [texera] via GitHub
  • Re: [PR] test(frontend): cover the search-instructions and agent settings panels [texera] via GitHub
• [I] Render the search-instructions and agent settings panels so their templates are covered [texera] via GitHub
  • Re: [I] Render the search-instructions and agent settings panels so their templates are covered [texera] via GitHub
  • Re: [I] Render the search-instructions and agent settings panels so their templates are covered [texera] via GitHub
• [I] Drive the workspace menu template through the DOM instead of calling its handlers [texera] via GitHub
  • Re: [I] Drive the workspace menu template through the DOM instead of calling its handlers [texera] via GitHub
  • Re: [I] Drive the workspace menu template through the DOM instead of calling its handlers [texera] via GitHub
• [PR] refactor(amber): remove the unused SuccessExecutionResult DTO [texera] via GitHub
  • Re: [PR] refactor(amber): remove the unused SuccessExecutionResult DTO [texera] via GitHub
  • Re: [PR] refactor(amber): remove the unused SuccessExecutionResult DTO [texera] via GitHub
  • Re: [PR] refactor(amber): remove the unused SuccessExecutionResult DTO [texera] via GitHub
  • Re: [PR] refactor(amber): remove the unused SuccessExecutionResult DTO [texera] via GitHub
• [PR] test(frontend): close the branch arms left in the dataset explorer components [texera] via GitHub
  • Re: [PR] test(frontend): close the branch arms left in the dataset explorer components [texera] via GitHub
  • Re: [PR] test(frontend): close the branch arms left in the dataset explorer components [texera] via GitHub
  • Re: [PR] test(frontend): close the branch arms left in the dataset explorer components [texera] via GitHub
• [PR] test(amber): cover the auth resource's bootstrap and validation guards [texera] via GitHub
  • Re: [PR] test(amber): cover the auth resource's bootstrap and validation guards [texera] via GitHub
  • Re: [PR] test(amber): cover the auth resource's bootstrap and validation guards [texera] via GitHub
  • Re: [PR] test(amber): cover the auth resource's bootstrap and validation guards [texera] via GitHub
  • Re: [PR] test(amber): cover the auth resource's bootstrap and validation guards [texera] via GitHub
  • Re: [PR] test(amber): cover the auth resource's bootstrap and validation guards [texera] via GitHub
• [I] Cover the auth resource's bootstrap and validation guards [texera] via GitHub
  • Re: [I] Cover the auth resource's bootstrap and validation guards [texera] via GitHub
• [I] Close the branch arms left in the dataset explorer components [texera] via GitHub
  • Re: [I] Close the branch arms left in the dataset explorer components [texera] via GitHub
  • Re: [I] Close the branch arms left in the dataset explorer components [texera] via GitHub
• [PR] test(workflow-core): cover the lakeFS file document against the loopback stub [texera] via GitHub
  • Re: [PR] test(workflow-core): cover the lakeFS file document against the loopback stub [texera] via GitHub
  • Re: [PR] test(workflow-core): cover the lakeFS file document against the loopback stub [texera] via GitHub
  • Re: [PR] test(workflow-core): cover the lakeFS file document against the loopback stub [texera] via GitHub
  • Re: [PR] test(workflow-core): cover the lakeFS file document against the loopback stub [texera] via GitHub
  • Re: [PR] test(workflow-core): cover the lakeFS file document against the loopback stub [texera] via GitHub
• [I] Cover the lakeFS file document against the existing loopback stub [texera] via GitHub
  • Re: [I] Cover the lakeFS file document against the existing loopback stub [texera] via GitHub
• [I] Remove the unused SuccessExecutionResult DTO [texera] via GitHub
  • Re: [I] Remove the unused SuccessExecutionResult DTO [texera] via GitHub
• [I] Pin the published version of a workflow [texera] via GitHub
  • Re: [I] Pin the published version of a workflow [texera] via GitHub
  • Re: [I] Pin the published version of a workflow [texera] via GitHub
• [PR] fix(frontend): read autofill required-ness from the property's own schema level [texera] via GitHub
  • Re: [PR] fix(frontend): read autofill required-ness from the property's own schema level [texera] via GitHub
  • Re: [PR] fix(frontend): read autofill required-ness from the property's own schema level [texera] via GitHub
  • Re: [PR] fix(frontend): read autofill required-ness from the property's own schema level [texera] via GitHub
  • Re: [PR] fix(frontend): read autofill required-ness from the property's own schema level [texera] via GitHub
• [I] Autofill required-ness is read from the root schema, not the property's own level [texera] via GitHub
  • Re: [I] Autofill required-ness is read from the root schema, not the property's own level [texera] via GitHub
  • Re: [I] Autofill required-ness is read from the root schema, not the property's own level [texera] via GitHub
• [I] Six admin user table columns sort backwards under their own caret [texera] via GitHub
  • Re: [I] Six admin user table columns sort backwards under their own caret [texera] via GitHub
• [PR] fix(frontend): sort the admin user columns ascending under the ascend caret [texera] via GitHub
  • Re: [PR] fix(frontend): sort the admin user columns ascending under the ascend caret [texera] via GitHub
  • Re: [PR] fix(frontend): sort the admin user columns ascending under the ascend caret [texera] via GitHub
  • Re: [PR] fix(frontend): sort the admin user columns ascending under the ascend caret [texera] via GitHub
• [I] Reconfiguration service leaks its engine callback past unsubscribeAll [texera] via GitHub
  • Re: [I] Reconfiguration service leaks its engine callback past unsubscribeAll [texera] via GitHub
  • Re: [I] Reconfiguration service leaks its engine callback past unsubscribeAll [texera] via GitHub
• [PR] fix(amber): release the reconfiguration service's engine callback on teardown [texera] via GitHub
  • Re: [PR] fix(amber): release the reconfiguration service's engine callback on teardown [texera] via GitHub
  • Re: [PR] fix(amber): release the reconfiguration service's engine callback on teardown [texera] via GitHub
  • Re: [PR] fix(amber): release the reconfiguration service's engine callback on teardown [texera] via GitHub
  • Re: [PR] fix(amber): release the reconfiguration service's engine callback on teardown [texera] via GitHub
• [PR] fix(agent-service): reject maxSteps 0 in settings [texera] via GitHub
  • Re: [PR] fix(agent-service): reject maxSteps 0 in settings [texera] via GitHub
  • Re: [PR] fix(agent-service): reject maxSteps 0 in settings [texera] via GitHub
  • Re: [PR] fix(agent-service): reject maxSteps 0 in settings [texera] via GitHub
  • Re: [PR] fix(agent-service): reject maxSteps 0 in settings [texera] via GitHub
• Re: [I] Remove the fully commented-out PythonWorkflowWorkerSpec [texera] via GitHub
  • Re: [I] Remove the fully commented-out PythonWorkflowWorkerSpec [texera] via GitHub
• [PR] feat(gui): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(gui): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(gui): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(gui): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(gui): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(gui): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(frontend): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(frontend): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(frontend): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(frontend): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(frontend): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(frontend): add the per-user warehouse API client [texera] via GitHub
  • Re: [PR] feat(frontend): add the per-user warehouse API client [texera] via GitHub
• [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
  • Re: [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
  • Re: [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
  • Re: [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
  • Re: [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
  • Re: [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
  • Re: [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
  • Re: [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
  • Re: [PR] feat(gui): warehouse dashboard tab [texera] via GitHub
• [I] [BYO-S3] Frontend: on-canvas per-execution warehouse picker [texera] via GitHub
  • Re: [I] [BYO-S3] Frontend: on-canvas per-execution warehouse picker [texera] via GitHub
• [PR] test(amber): cover exportOperatorsAsZip and the remaining ResultExportService entry points [texera] via GitHub
  • Re: [PR] test(amber): cover exportOperatorsAsZip and the remaining ResultExportService entry points [texera] via GitHub
  • Re: [PR] test(amber): cover exportOperatorsAsZip and the remaining ResultExportService entry points [texera] via GitHub
  • Re: [PR] test(amber): cover exportOperatorsAsZip and the remaining ResultExportService entry points [texera] via GitHub
  • Re: [PR] test(amber): cover exportOperatorsAsZip and the remaining ResultExportService entry points [texera] via GitHub
  • Re: [PR] test(amber): cover exportOperatorsAsZip and the remaining ResultExportService entry points [texera] via GitHub
• [PR] test(pyamber): extend the OutputManager tests to cover its partitioning, output-port and emit semantics [texera] via GitHub
  • Re: [PR] test(pyamber): extend the OutputManager tests to cover its partitioning, output-port and emit semantics [texera] via GitHub
  • Re: [PR] test(pyamber): extend the OutputManager tests to cover its partitioning, output-port and emit semantics [texera] via GitHub
  • Re: [PR] test(pyamber): extend the OutputManager tests to cover its partitioning, output-port and emit semantics [texera] via GitHub
  • Re: [PR] test(pyamber): extend the OutputManager tests to cover its partitioning, output-port and emit semantics [texera] via GitHub
  • Re: [PR] test(pyamber): extend the OutputManager tests to cover its partitioning, output-port and emit semantics [texera] via GitHub
• [I] extend ResultExportServiceSpec to cover exportOperatorsAsZip and the two remaining export entry points [texera] via GitHub
  • Re: [I] extend ResultExportServiceSpec to cover exportOperatorsAsZip and the two remaining export entry points [texera] via GitHub
• [I] extend the Python OutputManager tests to cover its partitioning, output-port and emit semantics [texera] via GitHub
  • Re: [I] extend the Python OutputManager tests to cover its partitioning, output-port and emit semantics [texera] via GitHub
• [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API (metadata + access control) [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API (metadata + access control) [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
  • Re: [PR] feat(file-service): add model management API and unify shared resource access [texera] via GitHub
• [PR] fix(v1.2): raise default WebSocket payload limit to avoid dropping large result frames [texera] via GitHub
  • Re: [PR] fix(v1.2): raise default WebSocket payload limit to avoid dropping large result frames [texera] via GitHub
  • Re: [PR] fix(v1.2): raise default WebSocket payload limit to avoid dropping large result frames [texera] via GitHub
• Re: [I] Large result/visualization frames exceed the default WebSocket message limit and are silently dropped [texera] via GitHub
• Re: [PR] fix(pyamber): keep LinkedBlockingMultiQueue priority groups sorted [texera] via GitHub
• [I] `LinkedBlockingMultiQueue.add_sub_queue` replaces an existing sub-queue instead of keeping it (putIfAbsent divergence) [texera] via GitHub
  • Re: [I] `LinkedBlockingMultiQueue.add_sub_queue` replaces an existing sub-queue instead of keeping it (putIfAbsent divergence) [texera] via GitHub
• [PR] fix(amber, operator, v1.2): keep error information on three failure paths [texera] via GitHub
  • Re: [PR] fix(amber, operator, v1.2): keep error information on three failure paths [texera] via GitHub
  • Re: [PR] fix(amber, operator, v1.2): keep error information on three failure paths [texera] via GitHub
  • Re: [PR] fix(amber, operator, v1.2): keep error information on three failure paths [texera] via GitHub
  • Re: [PR] fix(amber, operator, v1.2): keep error information on three failure paths [texera] via GitHub
• Re: [PR] fix: raise default WebSocket payload limit to avoid dropping large result frames [texera] via GitHub
  • Re: [PR] fix: raise default WebSocket payload limit to avoid dropping large result frames [texera] via GitHub
  • Re: [PR] fix: raise default WebSocket payload limit to avoid dropping large result frames [texera] via GitHub

• Earlier messages
• Later messages