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

Set default value for storage taskqueue #765

Merged
merged 1 commit into from
Nov 10, 2023

Conversation

djjuhasz
Copy link
Collaborator

@djjuhasz djjuhasz commented Nov 9, 2023

Fixes issue #759.

  • Also fix SetDefault key for setting a3m.processing defaults
  • Add config test to confirm default values are set
  • Reorder embedded configs alphabetically
  • Log detailed error when storage.InitStorageUploadWorkflow fails

Fixes issue #759.

- Also fix SetDefault key for setting a3m.processing defaults
- Add config test to confirm default values are set
- Reorder embedded configs alphabetically
- Log detailed error when storage.InitStorageUploadWorkflow fails
@Diogenesoftoronto
Copy link
Contributor

I was confused for a second because there were differently profile pictures haha.

Copy link
Contributor

@Diogenesoftoronto Diogenesoftoronto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks good. Just have a question about the reordering.

internal/config/config.go Show resolved Hide resolved
Copy link
Contributor

@sevein sevein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! I have a couple of thoughts:

  1. Was it hard to identify the root issue, David? Yesterday I only had time to reproduce the issue before I had to move to something else, but I remember seeing a cryptic uninmplemented gRPC error code, I guess because the worker was not listening on the expected task queue. If there is a learning here on how to diagnose these kind of issues I'd be happy to capture it in our docs.
  2. @Diogenesoftoronto now I understand what was going on behind this line change... 😆
    image
    Hopefully we can build some high-level end-to-end tests soon to identify this kind of regression before the code is merged.

@sevein sevein merged commit 5884d1f into main Nov 10, 2023
10 checks passed
@sevein sevein deleted the dev/issue-759-fix-upload-activity branch November 10, 2023 05:17
@djjuhasz
Copy link
Collaborator Author

djjuhasz commented Nov 10, 2023

@sevein the biggest barrier to identifying the root problem was that I was getting a very generic "cannot perform operation" from the storage.Service here: https://github.com/artefactual-sdps/enduro/blob/main/internal/storage/service.go#L126

Which is why I added error logging here: https://github.com/artefactual-sdps/enduro/blob/main/internal/storage/service.go#L125

I don't know if the error message is very general on purpose to avoid leaking implementation details to the caller, or if it's just a poorly written error message. I assumed the error message was intentionally vague and added the logging to provide additional context to the system adminstrators.

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

Successfully merging this pull request may close these issues.

3 participants