I have checked if this is actually an issue inside issues::invoke and the stack trace is just messed up, but that does not appear to be the case.