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

Ensure the getOperation doesn't change operation status in 1.8.x version #1803

Closed
zcgandcomp opened this issue Dec 13, 2024 · 1 comment
Closed

Ensure the getOperation doesn't change operation status in 1.8.x version #1803

zcgandcomp opened this issue Dec 13, 2024 · 1 comment

Comments

@zcgandcomp
Copy link
Member

No description provided.

zcgandcomp added a commit that referenced this issue Dec 13, 2024
@zcgandcomp
Fix #1803: Ensure the getOperation doesn't change operation status
b3173f5
zcgandcomp added a commit that referenced this issue Dec 13, 2024
@zcgandcomp
Fix #1803: Ensure the getOperation doesn't change operation status (#…
3f949a7 
…1804)

* Fix #1803: Ensure the getOperation doesn't change operation status
@zcgandcomp
Copy link
Member Author

Tested:

  • operation created in the future.
  • manually changed expiration to the past.
  • called getDetail endpoint.

Result: endpoint returns properly Expired, but the DB is not changed (this is done only in expiration job)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zcgandcomp