Corey Hammerton

Results 15 comments of Corey Hammerton

Using the [pystack debugger](https://pypi.org/project/pystack-debugger/) I managed to use gdb to get a thread dump of some of our hanging processes. I've attached the dump of one of our hung threads...

Got a dump of the parent PID of the defunct processes. the results are attached below. [mongodb_consistent_backup_threaddump.txt](https://github.com/Percona-Lab/mongodb_consistent_backup/files/2420195/mongodb_consistent_backup_threaddump.txt) This one points to https://github.com/Percona-Lab/mongodb_consistent_backup/blob/master/mongodb_consistent_backup/Oplog/Resolver/Resolver.py#L105

Make sure your `production.lock_file` is configured differently on each configuration.

mongdb-consistent-backup version 1.3.0 is not affected by this bug.

I have the same error message when downloading a helm chart from a privately hosted Google Artifact Registry location using oauth2accesstoken login. Debug logs show nothing

I can confirm it is present in terraform v0.13.5. We had one check that flagged a change in a datasource which caused exit code 2

Is there any update to this issue? We do use the `service_accounts_map` output, but it renders the output variables `emails` and `iam_emails` effectively useless