Git Product home page Git Product logo

hepdata-converter-ws-client's Introduction

HEPData

GitHub Actions Build Status Coveralls Status License Docker Image Size GitHub Issues Documentation Status

The Durham High-Energy Physics Database (HEPData) has been built up over the past four decades as a unique open-access repository for scattering data from experimental particle physics. It currently comprises the data points from plots and tables related to several thousand publications including those from the Large Hadron Collider (LHC). HEPData is funded by a grant from the UK STFC and is based at the IPPP at Durham University.

HEPData is built upon Invenio v3 and is open source and free to use!

Research notice

Please note that this repository is participating in a study into sustainability of open source projects. Data will be gathered about this repository for approximately the next 12 months, starting from June 2021.

Data collected will include number of contributors, number of PRs, time taken to close/merge these PRs, and issues closed.

For more information, please visit the informational page or download the participant information sheet.

hepdata-converter-ws-client's People

Contributors

alisonrclarke avatar graemewatt avatar jstypka avatar michal-szostak avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

hepdata-converter-ws-client's Issues

Correct call to tarfile.open in 'convert' function

One of the most frequent causes of failed submission jobs (see HEPData/hepdata#248, addressed by HEPData/hepdata#316), is a FileNotFoundError when converting from the oldhepdata format (see an example event in Flower and Sentry). The same exception is sometimes also raised by the convert_and_store task (see another example event in Flower and Sentry). In both cases the exception is raised by this line:

tarfile.open('r:gz', fileobj=BytesIO(r.content)).close()

This looks like invalid syntax. The first argument should be a keyword argument mode='r:gz', otherwise it is interpreted as being a pathname name, explaining the FileNotFoundError since a file named r:gz does not exist. What I don't understand is why this works for some calls but not for others. It might be the case that name is normally ignored if a fileobj argument is given, but if fileobj cannot be opened, then the code attempts to open a pathname name instead. Another case of a missing mode appears a few lines below:
with tarfile.open('r:gz', fileobj=BytesIO(r.content)) as tar:

The solution is probably just to replace 'r:gz' by mode='r:gz' in these two lines, but it would be good to have a better understanding of the failure.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.