Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The extract api still returns some bytes instead of strings #6095

Closed
4 tasks
ptormene opened this issue Sep 24, 2020 · 4 comments
Closed
4 tasks

The extract api still returns some bytes instead of strings #6095

ptormene opened this issue Sep 24, 2020 · 4 comments
Assignees
@micheles
Labels
investigation
Milestone
Engine 3.16.0

Comments

@ptormene
Copy link
Member

  • Extracting realizations, branches are returned as bytes
  • Extracting asset_tags, all items (taxonomies and tags) are returned as arrays of bytes
  • Boundaries of ruptures are returned as bytes
  • Extracting agg_curves, units are returned as bytes

Also see gem/oq-irmt-qgis#743
@micheles
Copy link
Contributor

micheles commented Sep 13, 2021 •
edited
Loading

Is this a problem, @ptormene ? If not, we can close the issue.

@ptormene
Copy link
Member Author

It is not an urgent matter and it is not necessary.

@micheles
Copy link
Contributor

This will come hot again due to #6668: h5py 3.1 returns bytes instead of strings, so it may break the plugin even more.

@micheles
Copy link
Contributor

We already switched to h5py 3.1 without big issues; let's keep the status quo.

@micheles micheles added this to the Engine 3.16.0 milestone Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@micheles micheles

Labels
investigation
Projects
None yet
Milestone
Engine 3.16.0
Development

No branches or pull requests
2 participants
@ptormene @micheles