Sergey B Kirpichev

I notice same error in https://github.com/diofant/diofant/commit/6740f83761a14a06f44ab0b1d001907f70bcba0e/checks?check_suite_id=262644565 This build was initially triggered by tag push, but was unsuccessful due one of slow tests and then - was restarted.

I hope so, there are [remnants](https://github.com/diofant/diofant/blob/de99963e5864cd5d83bb3ebf78698c6e228fcd9d/.github/workflows/test.yml#L9-L10) of such check in the workflow file.

Hmm, that was related with the selected scopes of the used personal token. I'll leave this open, perhaps that should be documented.

I'll test the 1st option.

Hmm, this option [does work](https://github.com/diofant/diofant/commit/6740f83761a14a06f44ab0b1d001907f70bcba0e/checks?check_suite_id=262989757). But a bit fragile: if for some reasons the whole job was restarted - I got error from #20.

(As depicted in https://github.com/PyCQA/flake8/issues/234 there might be some second thoughts - to be polite, it seems they just ban any thoughts :). Look for closed issues, mentioned the pyproject.toml.). Thanks...

On Tue, Jun 08, 2021 at 03:53:53AM -0700, André Roberge wrote: > If you have concrete suggestions to offer as to how I might > go about to address this...

> any patch submitted to pytest to solve this issue were to be rejected by the maintainers of that project Probably, so. But I would like to see huge number...

Just for record, I corrected the example - it was wrong. The problem happens only for invalid asserts: tracebacks aren't very helpfull.

FYI: permission error can be fixed easily. In fact, I don't know why you open files for updating [here](https://github.com/aroberge/ideas/blob/f0c8a49f7030276f629101480be77138db07d881/ideas/import_hook.py#L144-L145): 'rb' mode seems to be more correct. Unfortunately, pytest's tracebacks aren't...