Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to repo-config v0.5.2 #587

Merged
merged 12 commits into from
Aug 29, 2023
Merged

Conversation

llucax
Copy link
Contributor

@llucax llucax commented Aug 17, 2023

All changes here are derived from regenerating files using the templates in repo-config v0.5.2.

@llucax llucax requested a review from a team as a code owner August 17, 2023 12:15
@llucax llucax self-assigned this Aug 17, 2023
@github-actions github-actions bot added the part:tooling Affects the development tooling (CI, deployment, dependency management, etc.) label Aug 17, 2023
@llucax llucax requested a review from Marenz August 17, 2023 12:15
@llucax llucax added this to the v0.25.0 milestone Aug 17, 2023
@llucax llucax added type:tech-debt Improves the project without visible changes for users cmd:skip-release-notes It is not necessary to update release notes for this PR labels Aug 17, 2023
@llucax llucax force-pushed the repo-config-0.5 branch 2 times, most recently from 3d58e9e to c2b73b2 Compare August 17, 2023 13:11
@llucax llucax changed the title Upgrade to repo-config v0.5.1 Upgrade to repo-config v0.5.2 Aug 18, 2023
@llucax llucax enabled auto-merge August 18, 2023 07:39
@llucax
Copy link
Contributor Author

llucax commented Aug 18, 2023

Not sure what's going on with the tests, locally it passes and if I remove the # type: ignore locally, it fails 😠

@llucax llucax disabled auto-merge August 18, 2023 09:20
@llucax llucax modified the milestones: v0.25.0, v1.0.0-rc Aug 24, 2023
@llucax llucax force-pushed the repo-config-0.5 branch 2 times, most recently from 7814900 to f12b14a Compare August 25, 2023 13:13
@Marenz
Copy link
Contributor

Marenz commented Aug 28, 2023

test is failing

llucax added 7 commits August 29, 2023 14:57
We always want to use the template provided extensions, keeping our own
list only makes it more likely to have errors when upgrading.

Also `_cookiecutter` is just noise, not very useful to keep.

Signed-off-by: Leandro Lucarella <[email protected]>
The key needs to be there, but the contents is only to show on the first
generation, so we don't need to save it in the replay file.

Signed-off-by: Leandro Lucarella <[email protected]>
This is just to be nice to editors, that usually like having a `\n` at
the end of text files.

Signed-off-by: Leandro Lucarella <[email protected]>
Signed-off-by: Leandro Lucarella <[email protected]>
This is to have a common basic configuration that should work with most
editors/IDEs.

Signed-off-by: Leandro Lucarella <[email protected]>
Now repo-config ships support to easily enable the collection and
linting of code examples in docstrings, so we use that instead.

Also make sure that we label the `conftest.py` file properly and we
exclude it from the source distribution.

Signed-off-by: Leandro Lucarella <[email protected]>
This is not really used in this project, but it is included as part of
the repo-config ci template, as it doesn't hurt either.

Signed-off-by: Leandro Lucarella <[email protected]>
llucax added 4 commits August 29, 2023 14:57
This is to match the name used by the repo-config template.

Signed-off-by: Leandro Lucarella <[email protected]>
Signed-off-by: Leandro Lucarella <[email protected]>
@github-actions github-actions bot added the part:microgrid Affects the interactions with the microgrid label Aug 29, 2023
@llucax llucax changed the title Upgrade to repo-config v0.5.2 Upgrade to repo-config v0.6.0 Aug 29, 2023
@github-actions github-actions bot removed the part:microgrid Affects the interactions with the microgrid label Aug 29, 2023
@llucax llucax changed the title Upgrade to repo-config v0.6.0 Upgrade to repo-config v0.5.2 Aug 29, 2023
This option avoids using a cache. It is slower but prevents some issues
with `mypy` giving different results on different runs (typically
complaining about some `type: ignore[issue]` not being used but when
removing it complaining about an `issue` again.

Signed-off-by: Leandro Lucarella <[email protected]>
@llucax
Copy link
Contributor Author

llucax commented Aug 29, 2023

OK, after a long investigation it seems like the problem with mypy is caching.

This failed in the CI but worked locally because it seems like the first uncached run is the one failing, but if you run mypy again it works and sometimes, if you run it again it will fail again and alternate. I found a similar issue that was fixes, so I guess this is a persistent problem (not sure if it is worth reporting unless we spend some time to reduce it to a small test case): python/mypy#2960

Using the --no-incremental option (which avoids caching) the issue is fixed, so I added that as a temporary fix in a new commit (the new repo-config will probably use this option by default).

@llucax llucax modified the milestones: v1.0.0-rc, v0.25.0 Aug 29, 2023
@llucax llucax added this pull request to the merge queue Aug 29, 2023
Merged via the queue into frequenz-floss:v0.x.x with commit 953e320 Aug 29, 2023
@llucax llucax deleted the repo-config-0.5 branch August 29, 2023 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cmd:skip-release-notes It is not necessary to update release notes for this PR part:tooling Affects the development tooling (CI, deployment, dependency management, etc.) type:tech-debt Improves the project without visible changes for users
Projects
Development

Successfully merging this pull request may close these issues.

3 participants