Skip to content

Conversation

@aldavidson
Copy link

There's a File.write operation to a hard-coded filename xml_for_signing.xml that means you can't run multiple zatca operations simultaneously in sidekiq, as they conflict and cause errors. See issue #39 for details.

This PR fixes the problem by simply removing the File.write - I can't see anywhere else that file is accessed, so presumably it's some debugging code that was inadvertently left in? (as per b4a4507#diff-ad3e2839a3df5a1ca12bed1822b34313e34095c0c03f010ad69f36e6330dd897R19)

@aldavidson aldavidson changed the title remove File.write to hard-code xml_for_signing.xml. Fixes issue #39 remove File.write to hard-coded xml_for_signing.xml. Fixes issue #39 Feb 20, 2025
obahareth added a commit to theamazingteam/zatca that referenced this pull request Apr 30, 2025
@obahareth
Copy link
Contributor

obahareth commented Apr 30, 2025

I applied your fix in my fork and published it to rubygems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants