Temo
Temo
>but this is too risky I mean, you could just not approve the PR if the generated code is somehow malicious. Which is extremely unlikely.
#495 Ray tracing support would also be great.
>I know the browsergym change will break things as-is, but we have a fix incoming @rbren Why? Does it conflict with other dependencies or something? Also, why tf is it...
Please re-review and tell me clearly about any conflicts. Also would appreciate the max versions of any dependencies I can update the project to because of code-breaking changes, if any....
I will be closing this since it died. I do however have another commit unrelated to this PR to pull request. I'll be opening that shortly.
I encountered it on the opendevin:main docker image.
Is there anything else that I can do, or do I just wait for #1941 to be merged?
I mean I personally think this prompt is fine, but IDK if the maintainers also think so.
So am I supposed to revert the changes and just fix any typos and things like that? It's unclear to me what is conflicting here.
Because modern Vulkan versions are necessary for both performance and feature compatibility.