Brian Ward

I believe Bob is correct: https://github.com/llvm/llvm-project/pull/80801

When we open a PR to change model base our CI should tell us whether or not it’s a problem on older clang and GCC

Ah, upstream resolved this in https://github.com/stan-dev/stan/pull/3228 (part of 2.34) by removing the `template` keyword in this case. I think adding the `` is equivalent, but removing the keyword seemed more...

Hi @wds15 - Some explanation was given in https://github.com/stan-dev/math/issues/3088, but in short there are 3 main reasons: - This 'feature' is almost completely undocumented. There were ~two mentions of it...

As Bob said, I have tried to ensure most of the open issues are not things that have already been implemented. I've been much more conservative closing issues for things...

@SteveBronder mind giving this a look? I think it got lost in the travel for ISBA

I wonder if this has something to do with one being run under ARM and one under x86 Did you install cmdstan with conda or with install_cmdstan?

Are all the processes in ARM when run from the terminal as well?

From the jupyter notebook, can you try running the commands directly? Even just `!/Users/ff/.cmdstan/cmdstan-2.34.1/bin/diagnose --help` might be helpful to see the output of

Very odd that those files are now missing - it sounds similar to some sporadic issues we've heard with code signing: https://discourse.mc-stan.org/t/cmdstanpy-reduce-sum-doesnt-produce-executable/33637/14 This seems to be an OS issue for...