• State Not Answered
  • Replies 4 replies
  • Subscribers 26 subscribers
  • Views 293 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 285560
Options

Permissions in pynrfjprog are broken

user84397

Hello, we came across a recurring issue:

There are no executable permission for Linux + macOS for the packed binary:

  • jlinkarm_nrf_worker_linux
  • jlinkarm_nrf_worker_osx

The issue was fixed in pynrfjprog v10.15.2, but returned back in v10.15.4.

As a result, the interaction with pynrfjprog ends up with this log:

An error was reported by NRFJPROG DLL: -254 INTERNAL_ERROR.

Using the extended logging, we got the message:

execve failed: Permission denied

(This gave us the clue what the problem is as we have traced it down before)

Side note: We assume there is a lack of continuous integration on pynrfjprog repository and the deployment today is a rather manual process? We suggest setting up an automated pipeline in order to avoid such repetitive issues in the future.

Parents Reply
  • 0 in reply to user114280

    Thanks for the feedback, though I do not understand why is it undesirable? There is an obvious issue because the library calls `exec` system call on one of the binaries inside your package but that cannot be executed. The system call fails on it and your package is unusable on both Linux and macOS. It is a serious deployment bug.

    You have fixed the issue in v10.15.2 but re-introduced this in the next version.

Children
  • 0 in reply to user84397

    Re-reading this discussion again, I think there is a misunderstanding between us. I wanted to set executable bit just to these two binaries listed in my original report:

    • jlinkarm_nrf_worker_linux
    • jlinkarm_nrf_worker_osx

    I did not intend to give executable bits on all files in the folder - of course, that would be a plain wrong approach. Can you please re-evaluate this thread and come back to me? Thanks. P.

Related
Terms of service