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

Try bumping JuliaSyntax to 0.4.10 #56110

Merged
merged 1 commit into from
Dec 10, 2024
Merged

Try bumping JuliaSyntax to 0.4.10 #56110

merged 1 commit into from
Dec 10, 2024

Conversation

Keno
Copy link
Member

@Keno Keno commented Oct 11, 2024

The last time we tried to bump JuliaSyntax (#53119), it didn't work out due to test failues. As a result, we haven't actually bumped JuliaSyntax in about a year and there are several syntax changes in JuliaSyntax that we haven't picked up yet (i.e. are waiting in PRs). I don't know what the current situation is, but I think we need to get back to a point where we can bump JuliaSyntax regualarly, so let's try to take the first step.

@Keno
Copy link
Member Author

Keno commented Oct 12, 2024

REPLCompletions issue is:

julia> s = "CompletionFoo.test(1, 1, "
"CompletionFoo.test(1, 1, "

julia> Base.incomplete_tag(Meta.parse(s, raise=false, depwarn=false))
:none

vs

julia> Base.incomplete_tag(Meta.parse(s, raise=false, depwarn=false))
:other

simeonschaub added a commit that referenced this pull request Oct 14, 2024
This adopts the semantics discussed in #1289, namely the `else` block is executed whenever the loop never runs. Unlike Python, `break` and `continue` are irrelevant. Multidimensional loops are not supported since there is some ambiguity whether e.g.

```julia
for i in 1:3, j in 1:0
    print(1)
else
    print(2)
end
```

should print 2 once, thrice or maybe not even at all.

Currently only supported in the flisp parser, so requires `JULIA_USE_FLISP_PARSER=1`. I could use some guidance on the necessary steps to add this to JuliaSyntax as well - AFAIU this would also require #56110 first.

closes #1289
@Keno
Copy link
Member Author

Keno commented Oct 16, 2024

@c42f could you take a look at the JuliaSyntax issue that's blocking this? Hopefully it should be fairly straightforward, but I'd really like to make sure that we can start bumping JuliaSyntax again.

The last time we tried to bump JuliaSyntax (#53119),
it didn't work out due to test failues. As a result, we haven't actually
bumped JuliaSyntax in about a year and there are several syntax changes
in JuliaSyntax that we haven't picked up yet (i.e. are waiting in PRs).
I don't know what the current situation is, but I think we need to get
back to a point where we can bump JuliaSyntax regualarly, so let's try
to take the first step.
@KristofferC KristofferC merged commit 9d28a06 into master Dec 10, 2024
5 of 7 checks passed
@KristofferC KristofferC deleted the kf/bumpsyntax branch December 10, 2024 13:20
@KristofferC
Copy link
Member

I think this broke Revise tests which didn't run on this PR for some reason. Maybe it needed a rebase to pick up on the new buildkite config? On https://buildkite.com/julialang/julia-master/builds/42947#0193b85a-4e0e-4101-b248-0e43faef0607 there is

Recipes: Test Failed at /root/.julia/packages/Revise/UvZ44/test/runtests.jl:2881
--
  | Expression: definition(m) isa Expr
  | Evaluated: nothing isa Expr
  |  
  | Stacktrace:
  | [1] top-level scope
  | @ ~/.julia/packages/Revise/UvZ44/test/runtests.jl:89
  | [2] macro expansion
  | @ /cache/build/builder-amdci5-5/julialang/julia-master/usr/share/julia/stdlib/v1.12/Test/src/Test.jl:1724 [inlined]
  | [3] macro expansion
  | @ ~/.julia/packages/Revise/UvZ44/test/runtests.jl:2869 [inlined]
  | [4] macro expansion
  | @ /cache/build/builder-amdci5-5/julialang/julia-master/usr/share/julia/stdlib/v1.12/Test/src/Test.jl:1724 [inlined]
  | [5] macro expansion
  | @ ~/.julia/packages/Revise/UvZ44/test/runtests.jl:2881 [inlined]
  | [6] macro expansion
  | @ /cache/build/builder-amdci5-5/julialang/julia-master/usr/share/julia/stdlib/v1.12/Test/src/Test.jl:679 [inlined]

I'll see if I can fix it quickly on the Revise side.

@Keno
Copy link
Member Author

Keno commented Dec 12, 2024

That error happens when Revise fails to parse base. one possible reason is the include issue I fixed last week. I'm on my phone so it's hard to see if that build is on master. If it's not, them the error is unsurprising because it needs my fixes from last week. Otherwise it is indeed possible that this commit broke it and will need to look at what suppressed error revise had while parsing Base.

@KristofferC
Copy link
Member

KristofferC commented Dec 12, 2024

Maybe it is fine considering for example #56798 is all green which was made after this PR. I also couldn't immediately reproduce this locally. The PRs that fail probably have an old base commit. (I still think it is kinda crazy not to run CI on the merge commit).

@Keno
Copy link
Member Author

Keno commented Dec 12, 2024

Yeah, old base commits will fail, because they're using Revise master, which needs a fix on julia master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants