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

[BUG] querying a node API directly fails #138

Closed
1 task done
surchs opened this issue Apr 18, 2024 · 3 comments · Fixed by #139
Closed
1 task done

[BUG] querying a node API directly fails #138

surchs opened this issue Apr 18, 2024 · 3 comments · Fixed by #139
Assignees
@surchs
Labels
released This issue/pull request has been released.

Comments

@surchs
Copy link
Contributor

surchs commented Apr 18, 2024 •
edited
Loading

Is there an existing issue for this?

  • I have searched the existing issues

Expected Behavior

  • docker compose --profile local_node_query up -d from the recipes
  • go to the query tool (now pointing at a local n-API)
  • attempt to query anything

expect it should succeed

Current Behavior

The request arrives at the API and the API responds,
but the query tool crashes once it retrieves the response

Error message

Unexpected Application Error!
Cannot read properties of undefined (reading 'sort')
TypeError: Cannot read properties of undefined (reading 'sort')
    at oj (http://localhost:3000/assets/index-ZYyfRoec.js:202:5051)
    at gh (http://localhost:3000/assets/index-ZYyfRoec.js:38:19519)
    at Xf (http://localhost:3000/assets/index-ZYyfRoec.js:40:3139)
    at ax (http://localhost:3000/assets/index-ZYyfRoec.js:40:44804)
    at rx (http://localhost:3000/assets/index-ZYyfRoec.js:40:39766)
    at mE (http://localhost:3000/assets/index-ZYyfRoec.js:40:39694)
    at $u (http://localhost:3000/assets/index-ZYyfRoec.js:40:39547)
    at ap (http://localhost:3000/assets/index-ZYyfRoec.js:40:35914)
    at ex (http://localhost:3000/assets/index-ZYyfRoec.js:40:34865)
    at k (http://localhost:3000/assets/index-ZYyfRoec.js:25:1565)

Environment

  • OS:
  • Python/Node version:

How to reproduce

No response

Anything else?

No response
@surchs surchs self-assigned this Apr 18, 2024
surchs added a commit that referenced this issue Apr 18, 2024
@surchs
[Fix] Hotfix for handling responses from n-API
c0eb4ba 
Fixes #138
This is a temporary fix until we get rid of the
non-federated deployment option in general
@surchs surchs mentioned this issue Apr 18, 2024
Merged
7 tasks
@surchs surchs moved this to Implement - Done in Neurobagel Apr 18, 2024
surchs added a commit that referenced this issue Apr 19, 2024
@surchs
[Fix] Hotfix for handling responses from n-API (#139)
c6b0ad7 
Fixes #138
This is a temporary fix until we get rid of the
non-federated deployment option in general
@github-project-automation github-project-automation bot moved this from Implement - Done to Review - Done in Neurobagel Apr 19, 2024
@surchs
Copy link
Contributor Author

surchs commented Apr 19, 2024

🚀 Issue was released in v0.2.2 🚀

1 similar comment
@surchs
Copy link
Contributor Author

surchs commented Apr 19, 2024

🚀 Issue was released in v0.2.2 🚀

@surchs surchs added the released This issue/pull request has been released. label Apr 19, 2024
@surchs
Copy link
Contributor Author

surchs commented Apr 19, 2024

🚀 Issue was released in v0.2.2 🚀

@surchs surchs mentioned this issue May 3, 2024
Closed
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@surchs surchs

Labels
released This issue/pull request has been released.
Projects
Neurobagel
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[FIX] Hotfix for handling responses from n-API neurobagel/query-tool
1 participant
@surchs