Closed jenny-m-wood closed 1 month ago
@xhagrg @slesaad ESDIS is promoting the use of QuARC for new missions such as PACE and NISAR, so please prioritize this ticket during pyQuARC development. Thanks!
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
We 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 urlextract
package, which attempts to save some files in local storage for caching purposes, resulting in the error.
Initialize function for URLExtract class. Tries to get cached TLDs, if cached file does not exist it will try to download new list from IANA and save it to cache file.
We need to find an alternative solution to the urlextract
package that does not rely on writing to the file system.
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.