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.

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

The previously disabled tasks were restored to a runnable state after migrating the job from version 3.x to 4.0.0-beta2 #1466

Closed
cobolbaby opened this issue Feb 7, 2024 · 3 comments

Comments

@cobolbaby
Copy link
Contributor

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

2024-02-07 09-55-40屏幕截图

curl -v 'https://infra-datajob.ipt.inventec.net/v1/jobs' > backup.json
curl -v http://localhost:6230/v1/restore --form '[email protected]'

2024-02-07 09-56-04屏幕截图

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

** Specifications:**

  • OS: [e.g. linux]
  • Version [e.g. 2.0.1]

Additional context
Add any other context about the problem here.

@cobolbaby cobolbaby changed the title The disabled tasks were restored to a runnable state after migrating the job from version 3.x to 4.x The previously disabled tasks were restored to a runnable state after migrating the job from version 3.x to 4.x Feb 7, 2024
@cobolbaby cobolbaby changed the title The previously disabled tasks were restored to a runnable state after migrating the job from version 3.x to 4.x The previously disabled tasks were restored to a runnable state after migrating the job from version 3.x to 4.0.0-beta2 Feb 7, 2024
@cobolbaby
Copy link
Contributor Author

It seems to be just a UI issue. The API response is normal.

2024-02-07 11-07-49屏幕截图

@vcastellm
Copy link
Member

Nice catch, thanks for reporting, I'll take a look

@vcastellm vcastellm mentioned this issue Feb 8, 2024
@vcastellm
Copy link
Member

Fixed in #1467

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants