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

Issue in MongoDB node module #2909

Closed
kirill-tolochko opened this issue Nov 17, 2023 · 3 comments
Closed

Issue in MongoDB node module #2909

kirill-tolochko opened this issue Nov 17, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@kirill-tolochko
Copy link
Collaborator

Problem description

In some cases there is an error in mongodb node module

Step to reproduce

Steps to reproduce the behavior:

  1. Import Verra\Verra Redd\VM0044 policy
  2. Run it in dry run, create Project_proponent user, create project, add it by administrator
  3. Create VVB user, assing created project to this user
  4. Check status history and console of policy service

Expected behavior

Waiting for validation should be presented 2 times (or 1?)

Actual behavior

Now "Waiting for validation" is presented 3 times. 1 time right after it was added by administrator, and 2 times after it was assigned to VVB.

Also there is an error in the policy service console:

2023-11-17T11:24:53.693Z [GUARDIAN_SERVICE,3ddad476-20bf-4103-803e-6eb793b1b690,sendToGuardianBlock,save_assign,6554ca6d393ee331e0a7d633]: runAction
MongoRuntimeError: File not found for id 65574d3951582bf6ebd2ca47
at GridFSBucket.delete (C:\Users...\guardian\node_modules\mongodb\lib\gridfs\index.js:70:19)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
[Symbol(errorLabels)]: Set(0) {}

Private Zenhub Image

@kirill-tolochko kirill-tolochko added the bug Something isn't working label Nov 17, 2023
@simvalery
Copy link
Collaborator

#2145

@kirill-tolochko
Copy link
Collaborator Author

Now there are only 2 "waiting for validation" messages, that's ok.

@artembuslaev
Copy link
Contributor

Fixed partially, duplicate events are a special case. Issue may occur when we are trying to update documents in parallel threads and it requires a more complex solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants