`load_hdf5()` filename issues

Open
#458 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
distributed-systems

Research direction

Start at Context.load_hdf5 and trace how its filename is passed to engines; reproduce the failure with a relative path and compare it with an absolute path. Done means relative filenames are resolved client-side before dispatch and the reported CompositeError no longer occurs.

Written by the indexing model from the issue text.

Description

bug prio-low

If Context.load_hdf5() is called with a relative path, it may fail with an:

IPython.parallel.error.CompositeError: one or more exceptions from call to method: func_wrapper
[0:apply]: IOError: Unable to open file (Mpi_err_no_such_file: no such file or directory)
[1:apply]: IOError: Unable to open file (Mpi_err_no_such_file: no such file or directory)
[2:apply]: IOError: Unable to open file (Mpi_err_no_such_file: no such file or directory)
[3:apply]: IOError: Unable to open file (Mpi_err_no_such_file: no such file or directory)

No error results if an absolute path is passed in instead.

I'd like to see Context.load_hdf5 detect relative paths client-side and resolve into absolute paths before passing to engines, which should resolve this issue.

Dominant language
Python
Stars
5
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from enthought/distarray

All issues in enthought/distarray

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.