Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Computational backend: service shall be able to define how progress is defined in the service #4376

Closed
Tracked by #950
sanderegg opened this issue Jun 16, 2023 · 1 comment · Fixed by #4814
Closed
Tracked by #950

Computational backend: service shall be able to define how progress is defined in the service #4376

sanderegg opened this issue Jun 16, 2023 · 1 comment · Fixed by #4814
Assignees
@sanderegg @bisgaard-itis
Labels
a:dask-service Any of the dask services: dask-scheduler/sidecar or worker bug buggy, it does not work as expected
Milestone
Baklava

Comments

@sanderegg
Copy link
Member

sanderegg commented Jun 16, 2023 •
edited
Loading

iSolve issues:
Logs like the following are wrongly parsed as progress logs

1957728 / 1933878        (100.00% / 100.00%) : Total
1951940 / 1929102        ( 99.70% /  99.75%) : Dielectric
1951940 / 1933878        ( 99.70% / 100.00%) : Background
  16       16      32    1                 794.62
@sanderegg sanderegg added the a:dask-service Any of the dask services: dask-scheduler/sidecar or worker label Jun 16, 2023
@sanderegg sanderegg added this to the Watermelon milestone Jun 16, 2023
@sanderegg sanderegg self-assigned this Jun 16, 2023
@sanderegg sanderegg modified the milestones: Watermelon, Pastel de Nata Jun 16, 2023
@sanderegg
Copy link
Member Author

@mguidon

@sanderegg sanderegg mentioned this issue Jun 16, 2023
Open
@sanderegg sanderegg added the bug buggy, it does not work as expected label Jul 21, 2023
@sanderegg sanderegg changed the title some non progress logs from iSolve are wrongly parsed as progress entries Computational backend: some non progress logs from iSolve are wrongly parsed as progress entries Jul 25, 2023
@sanderegg sanderegg modified the milestones: Sundae, Baklava Aug 17, 2023
@sanderegg sanderegg changed the title Computational backend: some non progress logs from iSolve are wrongly parsed as progress entries Computational backend: service shall be able to define how progress is defined in the service Sep 18, 2023
@bisgaard-itis bisgaard-itis mentioned this issue Oct 2, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sanderegg sanderegg

@bisgaard-itis bisgaard-itis

Labels
a:dask-service Any of the dask services: dask-scheduler/sidecar or worker bug buggy, it does not work as expected
Projects
None yet
Milestone
Baklava
Development

Successfully merging a pull request may close this issue.

🐛 Detect progress regex from docker label ⬆️ bisgaard-itis/osparc-simcore
3 participants
@sanderegg @matusdrobuliak66 @bisgaard-itis