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

"kick-job" should not return 'NOT_FOUND' on IO error #534

Open
ysmolski opened this issue Aug 8, 2019 · 1 comment
Open

"kick-job" should not return 'NOT_FOUND' on IO error #534

ysmolski opened this issue Aug 8, 2019 · 1 comment
Labels
NeedsFix The path to resolution is known, but the work has not been done.

Comments

@ysmolski
Copy link
Member

ysmolski commented Aug 8, 2019

kick-job should return MSG_INTERNAL_ERROR on IO error so the client will get a clue what is going on.
@ysmolski ysmolski added the NeedsFix The path to resolution is known, but the work has not been done. label Aug 13, 2019
@ysmolski
Copy link
Member Author

This can be fixed only after #535

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ysmolski