Yep, that looks like what was happening over in this post, where using rstan::stan() instead of loading RStan was a workaround.
I thought @bgoodri fixed it in RStan 2.21 though, so this might be new
2 Likes