Receiving "Invalid reference token: __bundled__" in CI

[yjp20]

Context

We've been seemingly spurious errors in CI with Invalid reference token: __bundled__. This is happening here:

https://github.com/openai/openai-python/actions/runs/10010129012/job/27670617482

Current Behavior

[4:35:54 PM] › [HTTP SERVER] post /threads/string/messages ✖  error     Request terminated with error: Error: Invalid reference token: __bundled__

Expected Behavior

I wouldn't expect the prism server to have a fatal error here

Steps to Reproduce

npm exec  --package=@stoplight/prism-cli@~5.8 -- \
      prism mock https://storage.googleapis.com/stainless-sdk-openapi-specs/openai-518ca6c60061d3e8bc0971facf40d752f2aea62e3522cc168ad29a1f29cab3dd.yml

curl -L localhost:4010/threads/string/messages -X POST \
            -H 'Authorization: Bearer xxx' \
            -H 'Content-Type: application/json' \
            --data '{"content":"hello","role":"user"}'

Strangely this does not happen after cloning the repo, then running the cli through (cd packages/cli && yarn cli mock https://storage.googleapis.com/stainless-sdk-openapi-specs/openai-518ca6c60061d3e8bc0971facf40d752f2aea62e3522cc168ad29a1f29cab3dd.yml)

Environment

• Versions: 5.8.3, 5.8.2, 5.7.0
• OS: MacOS 13.4 (but also in CI)

[yjp20]

Removing yarn.lock and running (cd packages/cli && yarn cli mock https://storage.googleapis.com/stainless-sdk-openapi-specs/openai-518ca6c60061d3e8bc0971facf40d752f2aea62e3522cc168ad29a1f29cab3dd.yml) seems to reproduce the issue actually, so it may just be a different behavior in a dependency.

[yjp20]

After some bisecting it seems like upgrading from

@stoplight/json@3.20.0
to
@stoplight/json@3.20.3

causes a breakage, which breaks on the consumer end of the library.

[RobertCraigie]

Note that short of forking to pin the @stoplight/json dependency we aren't aware of any workarounds

[mnaumanali94]

Should be fixed by: stoplightio/json#141

[dgellow]

@mnaumanali94 We are seeing this issue again.

https://github.com/openai/openai-go/actions/runs/10322573838/job/28578086104?pr=7

[RobertCraigie]

@mnaumanali94 this time I think it's because prism-http

[RobertCraigie]

yup it looks like pinning these deps fixes it stainless-api@335f8a8