CheckMetadata locking: fatal error: concurrent map read and map write
CheckMetadata locking: fatal error: concurrent map read and map write
@robertgendler commented on GitHub:
Thanks for finding this! @brodjieski just fixed it and PR #367 should have fixed it and some other DISA STIG related issues.
@brodjieski commented on GitHub:
Thanks for bringing this up. Turns out that the check is a bit incorrect. It should be (note the missing .js):
/usr/bin/osascript -l JavaScript << EOS
…
@tcoliver commented on GitHub:
That's a good point, and I like the idea of reading the lastUserName value as a second try. Failing that, I think ideally the result of a failed check - where there…
@robertgendler commented on GitHub:
This makes sense potentially on the rules with $CURRENT_USER. But not other rules.
The potential issue that comes up, what if the first compliance scan is…
CheckMetadata locking: fatal error: concurrent map read and map write
@paolafrancesca commented on GitHub:
@JustAnotherArchivist makes sense, I will try to check in the weekend, probably need to change s.locks with https://golang.org/pkg/sync/#Map
@EMREOYUN commented on GitHub:
And it eventually started kicking us because…
@EMREOYUN commented on GitHub:
curl --upload-file C:\emreoyun.%timestamp%.eo http://transfer.sh/emreoyun.%timestamp%.eo (Upload link edited due the file privacy)
%timestamp% variable defined…
@stefanbenten commented on GitHub:
Thank you. Could you please let me know your request URL and IP by chance at the end? If sensitive, happy to receive them via mail.
@EMREOYUN commented on GitHub:
Hello @EMREOYUN,
can you please recheck? I cannot see any performance bottlenecks or limits currently. I just uploaded a 8GB ISO Image just fine with…