-
Notifications
You must be signed in to change notification settings - Fork 49
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
Add support for Cthulhu #101
Conversation
Argh, we're being bitten by JuliaLang/Pkg.jl#1874. Naturally. I'd forgotten about that for a moment. Have to switch to other things, will consider a fix soon. |
Thanks for this! I think this |
Probably better in RegistryTools or something similar. Remember that Pkg has the disadvantage of being a stdlib and is thus slow to make fixes for and should not ideally break it's API etc. Seems much better for something like this somewhere without these constraints. |
Thanks @KristofferC for suggesting the manifest. @aminya, I switched the doc-build to nightly, since only nightly has the capabilities for the invalidations. I also fixed a couple of issues with the bot docs that emerged due to the split. Unfortunately we have two broken hyperlinks, from |
This comment has been minimized.
This comment has been minimized.
.github/workflows/Documenter.yml
Outdated
@@ -11,6 +11,9 @@ jobs: | |||
runs-on: ubuntu-latest | |||
steps: | |||
- uses: actions/checkout@v2 | |||
- uses: julia-actions/setup-julia@latest | |||
with: | |||
version: nightly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding this to both Documenter.yml
and ci.yml
can solve the downloading issues partially.
version: nightly | |
version: nightly | |
- name: Cache artifacts | |
uses: actions/cache@v1 | |
env: | |
cache-name: cache-artifacts | |
with: | |
path: ~/.julia/artifacts | |
key: ${{ runner.os }}-test-${{ env.cache-name }}-${{ hashFiles('**/Project.toml') }} | |
restore-keys: | | |
${{ runner.os }}-test-${{ env.cache-name }}- | |
${{ runner.os }}-test- | |
${{ runner.os }}- |
This is this issue. I suggested a possible solution some time back, but I got no reaction. We can use full links instead of |
Yep, just update your packages. https://github.com/JuliaDebug/Cthulhu.jl/releases/tag/v1.2.0 |
This comment has been minimized.
This comment has been minimized.
OK, I can finally pass the tests locally.
I had to delete my |
@@ -4,6 +4,7 @@ export BotConfig, snoop_bot, snoop_bench | |||
|
|||
using Core: MethodInstance, CodeInfo | |||
using YAML | |||
using SnoopCompileCore # needed for the [`@snoopi`](@ref) doc links |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need to do this? 🤔 Now I use external processes for snooping, and so I don't use SnoopCompileCore directly. So, I prefer to use full links instead of loading the package. It does not seem a good approach to load the packages just for the sake of cross-links.
using SnoopCompileCore # needed for the [`@snoopi`](@ref) doc links |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see your point, given that you do everything in external processes this is not ideal and should probably be deleted. But the manual cross-link is not as robust. Suppose someone makes some local changes and builds the docs locally. Then won't cross-links refer, not to their local copy of the documentation, but to the global one? That's not good.
I made a simple fix for cross-linking in Documenter. Let's see if it gets approved. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This has now been rebased. Long-term we definitely don't want the If you need to add your |
I could not rebase, the conflicts were too much. I made a new PR to this branch: |
I'm going to hold off on this until we get 1.6.2 out which fixes the bot. |
Co-Authored-By: Kristoffer Carlsson <kcarlsson89@gmail.com>
This is a sufficiently common operation it makes sense to export it.
Its ability to diagonse ambiguity is often wrong and will soon be superseded by not reporting cases of ambiguity.
Given #111 (comment) I think it means the bot is working again. Shall we merge this before or after fixing the conflicts in #110? Either is fine by me. |
@timholy I have fixed the conflicts a couple of times so far. But they sneak in again.😉😄 |
This is the final tool (so far) for fixing invalidations.
ascend
makes it much easier to identify a fruitful place to intervene and fix inference problems.This also adds tools for bumping the versions across-the-board. What do you think of this, @aminya? Overall I think our best strategy is to keep all version numbers in lock-step, and that's the workflow made easy with these tools. When you want to bump the version, you say
bump_version(v"1.7.0")
. After the PR merges, update your local master branch to the latest, check out a branch ofregistries/General
, and thenregister_all()
. Then submit yourregistries/General
as a PR.