Julius
Julius
3 years no change :o
Actually, this is probably due to the fact that it is no longer possible to delete a type (or at least a type mapping). Ref: https://www.elastic.co/guide/en/elasticsearch/reference/5.6/indices-delete-mapping.html
I had the same issue with v2.x. Rolling back to v1 helped. Didn't notice anything in the [CHANGELOG.md](./CHANGELOG.md)
Can confirm. This renders doctrine v3 not yet usable when the project is using uuids.
This might be very similar to https://github.com/doctrine/orm/pull/11090 But breaks as well on the ManyToOne side (the mentioned MR solves the opposite OneToMany)
This issue seems to stem from EAGER loading entities. It happens when the parameter is an association that EAGER loads. ```php class Media { #[ORM\Id, ORM\Column(type: 'uuid_binary'), ORM\GeneratedValue(strategy: 'NONE')] private...
The more I look into this, the more I see that this is not an issue of `ramsey/uuid-doctrine`, but rather `doctrine/orm`
It appears that at this point the server part is covered, but the Client (sse, streamable http) do not support auth yet. Note the MCP SDK already [supports it](https://github.com/modelcontextprotocol/python-sdk/blob/6e418e62f9446e3204f4bf889efcd9e6df76aef8/README.md#oauth-authentication-for-clients).
Like @mkielar, I also am facing a similar issue. I have multiple private keys in `~/.ssh`. Furthermore I don't have the luxury to edit the source code of the "module"...