-
Notifications
You must be signed in to change notification settings - Fork 0
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
QuARC does not pull in current master branch from pyQuARC repo #273
Comments
Alternative example record: C2068391958-LARC_ASDC (format: umm-c) |
I compared pyQuARC output and QuARC output, and it looks much better! Thank you so much for making those updates @rajeshpandey2053 I did notice that the URL recommendations from pyQuARC were missing from QuARC. When testing on C2103888967-LARC (dif10), this recommendation was provided by pyQuARC: QuARC however did not provide that recommendation, and this error message was shown: I noticed something similar when testing with G1001367981-LARC (echo-g). Any thoughts on why this may be happening or the next steps for resolving? |
@jenny-m-wood @rajeshpandey2053 is working on identifying what's causing it and then fixing it |
IssueWe are running pyQuARC in AWS Lambda functions to build the QuARC API. Lambda only supports a read-only file system. If someone attempts to write something to the Lambda, it throws an error. In our case, pyQuARC uses the SolutionWe need to find an alternative solution to the |
Describe the bug
QuARC does not pull in the current master branch of the pyQuARC repo. It is pulling in an outdated version, so the recommendations do not align.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect the output from pyQuARC's master branch and output from QuARC to be identical.
Additional context
When briefly investigated, it seemed like it may be an issue with the Lambda function. An issue in QuARC was created for this in 2023 and may still exist.
The text was updated successfully, but these errors were encountered: