News:Important Bioconductor Release 3.18 deadlines this week
0
0
Entering edit mode
shepherl 3.8k
@lshep
Last seen 17 hours ago
United States

The deadline for fixing packages in preparation for the release is this Friday October 20th. All packages should be installing, building, and checking without ERROR in the Bioconductor build report. While you can continue to push changes past this date, this ensures all changes are reflected in at least one build report before the code freeze for release. Packages that continue to show ERRORs in the build report after the release will be consideration for deprecation. We are on schedule to release Wednesday October 25th.

Please also remember to update your NEWS files for any information about changes to your packages during this last development cycle. Bioconductor collates all package news files as part of the release announcement. If your NEWS file is not formatted correctly and not updated by this weekend, it will not be included in the release announcement.

For clarification: The release 3.18 branch has not yet been created. Please continue to update the devel branch. Next week when the release occurs the core team will automatically create the RELEASE_3_18 branch on git.bioconductor.org but until that time the only branch accessible is devel. Do NOT try to create a RELEASE_3_18 branch on your own; the core team will do this for you. Bioconductor will also handle bumping the y of a package version x.y.z on release day.

Release Devel release devel • 708 views
ADD COMMENT
0
Entering edit mode

My package vignette for categoryCompare currently depends on the estrogen data package, which itself depends on genefilter, which at some point was not building, making estrogen unavailable for v 3.18. Should I just wait on the next build report, or take further actions to make sure my vignette builds?

ADD REPLY
0
Entering edit mode

Regarding the URL 403 issue, I actually can't reproduce that locally, unfortunately. I suspect that what may be happening is that the KEGGREST package when it fetches the annotations for the genes, hit a limit on KEGG, or something else?? I also see the same error on Linux for 3.17.

That does say something about either removing the KEGGREST explicit example, or caching a set of results for use in the vignette. I'm also considering loading the DEG results that right now use estrogen from a file instead of working through it all in the vignette.

ADD REPLY
0
Entering edit mode

Just chiming in regarding your remark on the URL 403 issue and KEGGREST: I also recently repeatedly experienced this 'error 'while using the KEGGREST package, and I reached out to the KEGG helpdesk. They informed me that this is indeed due to a protection system that is activated when too many requests are made to their server.

Hello, I would like to query the KEGG database in R using the Bioconductor library KEGGREST.
However, since the last couple of days I noticed that my code doesn't work anymore. I always get an error "Forbidden (HTTP 403)."

When manually copying the generated URL in my webbrowser I do observe the same error.
That is, the link:
https://rest.kegg.jp/pathway/hsa

results in:
"Forbidden
You don't have permission to access this resource.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request."

Any idea on what may be going on? Did something change on the server that may cause this?

Thank you,


-+-+
     We are sorry for the inconvenience.
    Our server is configured to consider intermittent accesses as an attack as a countermeasure against DDoS attacks.

    Your IP addres xxx.xxx.xxx.xx is denied access by the server.

    The criteria are as follows:
    1) When there are 240 accesses within 60 seconds of the last access,
       the SuspectDoS environment variable is set to "1".
    2) When there are 240 additional accesses within 3600 seconds,
       our server denies access from the corresponding IP address.
    3) When there are no accesses for the next 3600 seconds,
       the counter will return to 0.
    4) If there is another access within 3600 seconds of the last access,
       the counter continues to add.

    Please consider the frequency of access based on the above.

    Sincerely,
    ....
ADD REPLY

Login before adding your answer.

Traffic: 619 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6