notifications  

Messages by Thread

• • Re: [PR] fix(frontend): enable operator reuse toolbar [texera] via GitHub
• [I] Operator reuse toolbar action is always disabled [texera] via GitHub
  • Re: [I] Operator reuse toolbar action is always disabled [texera] via GitHub
  • Re: [I] Operator reuse toolbar action is always disabled [texera] via GitHub
  • Re: [I] Operator reuse toolbar action is always disabled [texera] via GitHub
• Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
  • Re: [PR] feat(frontend): add toggleable performance heat-map overlay [texera] via GitHub
• [I] Dashboard relative times use plural units for singular values [texera] via GitHub
  • Re: [I] Dashboard relative times use plural units for singular values [texera] via GitHub
  • Re: [I] Dashboard relative times use plural units for singular values [texera] via GitHub
• [PR] fix(frontend): protect selected dataset paths [texera] via GitHub
  • Re: [PR] fix(frontend): protect selected dataset paths [texera] via GitHub
  • Re: [PR] fix(frontend): protect selected dataset paths [texera] via GitHub
  • Re: [PR] fix(frontend): protect selected dataset paths [texera] via GitHub
  • Re: [PR] fix(frontend): protect selected dataset paths [texera] via GitHub
  • Re: [PR] fix(frontend): protect selected dataset paths [texera] via GitHub
  • Re: [PR] fix(frontend): protect selected dataset paths [texera] via GitHub
  • Re: [PR] fix(frontend): protect selected dataset paths [texera] via GitHub
• [PR] fix(frontend): preview xlsx dataset files [texera] via GitHub
  • Re: [PR] fix(frontend): preview xlsx dataset files [texera] via GitHub
  • Re: [PR] fix(frontend): preview xlsx dataset files [texera] via GitHub
  • Re: [PR] fix(frontend): preview xlsx dataset files [texera] via GitHub
  • Re: [PR] fix(frontend): preview xlsx dataset files [texera] via GitHub
  • Re: [PR] feat(frontend): preview xlsx dataset files [texera] via GitHub
• [I] Selected dataset file path remains editable [texera] via GitHub
  • Re: [I] Selected dataset file path remains editable [texera] via GitHub
  • Re: [I] Selected dataset file path remains editable [texera] via GitHub
• [I] Dataset preview rejects xlsx files [texera] via GitHub
  • Re: [I] Dataset preview rejects xlsx files [texera] via GitHub
  • Re: [I] Dataset preview rejects xlsx files [texera] via GitHub
• [PR] ci: register the v1.3 release line with Meng Wang as its manager [texera] via GitHub
  • Re: [PR] ci: register the v1.3 release line with Meng Wang as its manager [texera] via GitHub
  • Re: [PR] ci: register the v1.3 release line with Meng Wang as its manager [texera] via GitHub
  • Re: [PR] ci: register the v1.3 release line with Meng Wang as its manager [texera] via GitHub
  • Re: [PR] ci: register the v1.3 release line with Meng Wang as its manager [texera] via GitHub
• [I] Register the v1.3 release line in the backport automation with its release manager [texera] via GitHub
  • Re: [I] Register the v1.3 release line in the backport automation with its release manager [texera] via GitHub
• [PR] fix(frontend): preserve dashboard filter dates [texera] via GitHub
  • Re: [PR] fix(frontend): preserve dashboard filter dates [texera] via GitHub
  • Re: [PR] fix(frontend): preserve dashboard filter dates [texera] via GitHub
  • Re: [PR] fix(frontend): preserve dashboard filter dates [texera] via GitHub
  • Re: [PR] feat(frontend): preserve dashboard filter dates [texera] via GitHub
• [PR] test(amber): cover the Python worker's interpreter selection and teardown [texera] via GitHub
  • Re: [PR] test(amber): cover the Python worker's interpreter selection and teardown [texera] via GitHub
  • Re: [PR] test(amber): cover the Python worker's interpreter selection and teardown [texera] via GitHub
  • Re: [PR] test(amber): cover the Python worker's interpreter selection and teardown [texera] via GitHub
  • Re: [PR] test(amber): cover the Python worker's interpreter selection and teardown [texera] via GitHub
  • Re: [PR] test(amber): cover the Python worker's interpreter selection and teardown [texera] via GitHub
  • Re: [PR] test(amber): cover the Python worker's interpreter selection and teardown [texera] via GitHub
• [I] Cover the Python worker's interpreter selection and teardown [texera] via GitHub
  • Re: [I] Cover the Python worker's interpreter selection and teardown [texera] via GitHub
• [I] Cover the sync execution's validation, error classification and teardown [texera] via GitHub
  • Re: [I] Cover the sync execution's validation, error classification and teardown [texera] via GitHub
  • Re: [I] Cover the sync execution's validation, error classification and teardown [texera] via GitHub
• [PR] test(frontend): render the computing-unit rows and the metrics popover [texera] via GitHub
  • Re: [PR] test(frontend): render the computing-unit rows and the metrics popover [texera] via GitHub
  • Re: [PR] test(frontend): render the computing-unit rows and the metrics popover [texera] via GitHub
  • Re: [PR] test(frontend): render the computing-unit rows and the metrics popover [texera] via GitHub
  • Re: [PR] test(frontend): render the computing-unit rows and the metrics popover [texera] via GitHub
  • Re: [PR] test(frontend): render the computing-unit rows and the metrics popover [texera] via GitHub
• [PR] test(frontend): cover the virtual-environment package management guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the virtual-environment package management guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the virtual-environment package management guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the virtual-environment package management guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the virtual-environment package management guards [texera] via GitHub
  • Re: [PR] test(frontend): cover the virtual-environment package management guards [texera] via GitHub
• [I] Cover the virtual-environment package management guards [texera] via GitHub
  • Re: [I] Cover the virtual-environment package management guards [texera] via GitHub
  • Re: [I] Cover the virtual-environment package management guards [texera] via GitHub
• [I] Render the computing-unit list rows and metrics popover [texera] via GitHub
  • Re: [I] Render the computing-unit list rows and metrics popover [texera] via GitHub
  • Re: [I] Render the computing-unit list rows and metrics popover [texera] via GitHub
• Re: [PR] chore(deps, amber): update pekkoversion to v1.7.0 [texera] via GitHub
• Re: [PR] test(amber): cover WorkflowExecutionService state events and teardown [texera] via GitHub
• Re: [I] Add unit test coverage for seven small pyamber gaps [texera] via GitHub
• Re: [I] Add unit test coverage for WorkflowExecutionService state events and teardown [texera] via GitHub
• Re: [I] Add unit test coverage for the end-channel and retry handlers and the range partitioner [texera] via GitHub
• Re: [I] Add unit test coverage for the frontend build-version script and four small service gaps [texera] via GitHub
• Re: [PR] test(frontend): cover the build-version script, user config and agent registration [texera] via GitHub
• [PR] fix(amber): grant unheld collaboration locks [texera] via GitHub
  • Re: [PR] fix(amber): grant unheld collaboration locks [texera] via GitHub
  • Re: [PR] fix(amber): grant unheld collaboration locks [texera] via GitHub
  • Re: [PR] fix(amber): grant unheld collaboration locks [texera] via GitHub
  • Re: [PR] fix(amber): grant unheld collaboration locks [texera] via GitHub
• [I] AcquireLockRequest fails when no collaboration lock is held [texera] via GitHub
  • Re: [I] AcquireLockRequest fails when no collaboration lock is held [texera] via GitHub
  • Re: [I] AcquireLockRequest fails when no collaboration lock is held [texera] via GitHub
• Re: [PR] test(pyamber): close the schema, table, proxy and network-sender gaps [texera] via GitHub
  • Re: [PR] test(pyamber): close the schema, table, proxy and network-sender gaps [texera] via GitHub
• Re: [PR] test(amber): cover the end-channel and retry handlers and the range partitioner [texera] via GitHub
  • Re: [PR] test(amber): cover the end-channel and retry handlers and the range partitioner [texera] via GitHub
• Re: [PR] chore(build): remove the dead -Xelide-below scalac option [texera] via GitHub
• Re: [I] Remove the -Xelide-below scalac option, which no longer switches anything [texera] via GitHub
• Re: [I] Remove the deprecated project feature from the frontend [texera] via GitHub
• [PR] ci: gate each backport on its release manager's approval [texera] via GitHub
  • Re: [PR] ci: gate each backport on its release manager's approval [texera] via GitHub
  • Re: [PR] ci: gate each backport on its release manager's approval [texera] via GitHub
  • Re: [PR] ci: gate each backport on its release manager's approval [texera] via GitHub
  • Re: [PR] ci: gate each backport on its release manager's approval [texera] via GitHub
  • Re: [PR] ci: gate each backport on its release manager's approval [texera] via GitHub
  • Re: [PR] ci: gate each backport on its release manager's approval [texera] via GitHub
  • Re: [PR] ci: gate each backport on its release manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
  • Re: [PR] ci: block the merge until each release/* label has its manager's approval [texera] via GitHub
• Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
  • Re: [PR] feat(notebook-migration): resolve the Jupyter URL and token per user [texera] via GitHub
• Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
  • Re: [PR] feat(sql): remove superseded manual update scripts 01-22 [texera] via GitHub
• Re: [PR] refactor(amber): remove dead members and unreachable guards [texera] via GitHub
  • Re: [PR] refactor(amber): remove dead members and unreachable guards [texera] via GitHub
  • Re: [PR] refactor(amber): remove dead members and unreachable guards [texera] via GitHub
  • Re: [PR] refactor(amber): remove dead members and unreachable guards [texera] via GitHub
  • Re: [PR] refactor(amber): remove dead members and unreachable guards [texera] via GitHub
  • Re: [PR] refactor(amber): remove dead members and unreachable guards [texera] via GitHub
• Re: [I] Flaky frontend unit test: joint-ui.service per-port counts test times out on Windows CI [texera] via GitHub
• Re: [PR] fix(ci, test, frontend): stop the frontend matrix manufacturing false reds [texera] via GitHub
• [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • Re: [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • Re: [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • Re: [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • Re: [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • Re: [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • Re: [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • Re: [PR] fix(amber): guard logic changes before execution [texera] via GitHub
  • Re: [PR] fix(amber): guard logic changes before execution [texera] via GitHub
• Re: [I] Python InternalQueue: disable_data does not cover data channels registered after the pause(plus a dead InternalMarker branch in put) [texera] via GitHub
• [PR] fix(pyamber, v1.2): disable data sub-queues registered after disable_data [texera] via GitHub
  • Re: [PR] fix(pyamber, v1.2): disable data sub-queues registered after disable_data [texera] via GitHub
  • Re: [PR] fix(pyamber, v1.2): disable data sub-queues registered after disable_data [texera] via GitHub
  • Re: [PR] fix(pyamber, v1.2): disable data sub-queues registered after disable_data [texera] via GitHub
  • Re: [PR] fix(pyamber, v1.2): disable data sub-queues registered after disable_data [texera] via GitHub
• [I] ModifyLogic before execution initialization fails with a null pointer [texera] via GitHub
  • Re: [I] ModifyLogic before execution initialization fails with a null pointer [texera] via GitHub
  • Re: [I] ModifyLogic before execution initialization fails with a null pointer [texera] via GitHub
• Re: [PR] fix(pyamber): disable data sub-queues registered after disable_data [texera] via GitHub
  • Re: [PR] fix(pyamber): disable data sub-queues registered after disable_data [texera] via GitHub
• Re: [PR] feat(frontend): remove the deprecated project feature [texera] via GitHub
  • Re: [PR] feat(frontend): remove the deprecated project feature [texera] via GitHub
• [PR] fix(amber): report malformed websocket messages [texera] via GitHub
  • Re: [PR] fix(amber): report malformed websocket messages [texera] via GitHub
  • Re: [PR] fix(amber): report malformed websocket messages [texera] via GitHub
  • Re: [PR] fix(amber): report malformed websocket messages [texera] via GitHub
  • Re: [PR] fix(amber): report malformed websocket messages [texera] via GitHub

• Later messages