-
Notifications
You must be signed in to change notification settings - Fork 727
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
sra_ids_to_runinfo.py UnicodeEncodeError #525
Comments
Thanks for reporting this @carrere 👍 I can indeed reproduce this locally by manually running the |
You're welcome. I think the main problem come from the EBI API that not declare the document encoding:
Or in the firefox console: "The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature. filereport" I do not know if you can fix this automatically on the client side ... but if you know someone @ EBI, you could ask them to fix on the API side. Sebastien |
I been trying to solve the issue. The script works as it is when run with Python 3 but not with Python 2. The reason is that in Python 3 |
Thanks! But we should be using Python 3 for that process? |
I think we are using Python 2.7.13 |
Indeed we are!! Yes, that would be great we just need to replace those lines with the snippet below and that would be the best fix. Sorry, I was looking at the wrong process🤦🏽 conda (params.enable_conda ? "conda-forge::python=3.8.3" : null)
if (workflow.containerEngine == 'singularity' && !params.singularity_pull_docker_container) {
container "https://depot.galaxyproject.org/singularity/python:3.8.3"
} else {
container "quay.io/biocontainers/python:3.8.3"
} |
Thanks @JoseEspinosa. This will be fixed in the next release via f33eb6d |
Perfect @drpatelh ! was about to implement it now and saw that you closed the issue 😎 |
No worries! I had to use another container in the end that specifically contained |
It's Python >3 in the
|
👍 |
Dear nf-core team, first of all, many thanks for your amazing work that make our analyses more easy and straightforward !
I am using this nf-core/rnaseq pipeline (release 2.0) with the experimental feature --public_data_ids to retrieve SRA datasets and I face some issues with some SRA projects for which some characters are non-ascii.
Here is an example: looking for SRP290966, you can find the degree character "°" in the experiment_title field encoded in unicode: [ENA API RESULT] (https://www.ebi.ac.uk/ena/portal/api/filereport?accession=SRP290966&result=read_run&fields=experiment_title) )
The workflow ends with this error:
Thanks for your help,
Sébastien
The text was updated successfully, but these errors were encountered: