Jennifer Hamon

Can you confirm the name of the property you are setting in `uaa.yml`?

Right now it seems like the way [this has been implemented](https://github.com/cloudfoundry/uaa/blob/0252d75654f3286a0d1c34349b004a6cfd3957c4/server/src/main/java/org/cloudfoundry/identity/uaa/util/UaaTokenUtils.java#L214) is to always append `/oauth/token` to the configured issuer url. This is consistent with the value we put into...

Is this something that should be configured on the client? Or on the zone?

I agree this would be useful. Once I reached belt speeds of 12 items/s I can't really identify objects anymore.

Sorry all for the trouble. Looking into it now.

Is anyone seeing this error outside of a next.js context? My working theory is that the fetch implementation is missing/non-functional due to next.js stubbing out the cross-fetch polyfill we rely...

I think I've solved this issue in the [v1.1.0 release](https://github.com/pinecone-io/pinecone-ts-client/releases/tag/v1.1.0). Please upgrade and let us know if you're still having a problem with this.

Thank you for the detailed bug report. I will try to look at this soon and add some bun integration tests so this doesn't happen again.

@Nipunwalia08 From that stacktrace alone I'm not sure that this is a Pinecone error. Can you open a fresh issue in this repo (just to focus the discussion around your...

> @jhamon thanks for taking a look and fixing the issue in a new release! > > Interestingly enough, I am getting this issue (with the same stack trace as...