Add another test case:
- compiled tag calcite-1.35.0 with JDK8(1.8.0_391) on
MacOS with M2 chip: cannot reproduce
Put it altogether, I agree with Julian that it might be something
changed from 1.35.0 to 1.36.0 (such as the Guava version we're
compiling with) which causes the problem (I'm not
I tried to reproduce this using Guillaume's
project(https://github.com/MasseGuillaume/asm-remapper-bug), and the
findings are below:
- compiled latest main branch
(50a20824c4536450dcae963b5e757cf4bbc7e406) with JDK8(1.8.0_391) on
MacOS with M2 chip: reproduced
- compiled latest main branch
Here’s how I would find out. Find the git commit where those properties were
added. Look for tests added in the same commit. Do those tests cover the case
you are interested in? Do those tests still work? How do they work? Step
through them in the debugger if it’s not clear.
> On Dec 18, 2023,
I think you're saying that prepare can return warnings. I wasn’t aware of that;
I was only aware of warnings from execution (e.g. divide by zero happened).
Can you describe what warnings facility you have in mind?
> On Dec 18, 2023, at 10:53 PM, Mihai Budiu wrote:
>
> All these cases where at
Egor Ryashin created CALCITE-6170:
-
Summary: Invalid
Key: CALCITE-6170
URL: https://issues.apache.org/jira/browse/CALCITE-6170
Project: Calcite
Issue Type: Bug
Components:
