-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot create property '__metadata' on number '5' ( intermittent ) #108
Comments
I will check, can you share the relevant parts of your model? What is |
BTW. Which version of Can you try latest version: |
this is the abstract - meanwhile let be change to 1.13.8 and give it a try. My primary observation is, I had a GET call to another API , with in which I am updating a table. The immediate GET call to an unrelated entity was throwing 404 / 500 randomly - I suspect some sort of a db lock or so for the 404. 500 is due the the metadata caching ? I commented the DB update and its smooth for now. Somewhere its inconsistent entity Materials
{
key ID : Integer;
MATERIAL_TYPE_ID : Integer ;
ItsMaterialType : Association to one MaterialType on ItsMaterialType.ID = $self.MATERIAL_TYPE_ID;
}
entity MaterialType
{
key ID : Integer ;
DESCRIPTION : LargeString;
TEXT_ID : Integer;
ItsText : Association to one MaterialTypeText on ItsText.ID = $self.TEXT_ID ;
}
entity MaterialTypeText
{
key ID : Integer ;
TEXT : LargeText ;
} |
Thanks for the model. I looks very common, but I will check. You can explain where the Do you have a new callstack trace when the exception happens, so that I at least can match the line, where the error occurs? I don't think it's related to any caches, but it seems to be a race condition... Are use missing an |
I provided a fix, that prevents the crashing of response conversion: 890b8ba Will be part of next release, beginning of next year. Still I guess the OData V4 response is malformed in some cases, so you should check, why you have a number |
Awesome. Let me test this commit |
This issue is stale because it has been open for 14 days with no activity. |
Hello, any update on this issue? I have a similar problem. When could we expect new patch version release? BTW I found a workaround by setting cds.features.odata_new_adapter=false as described CAP documentation. Please note that the issue occurs only in CAP v8. Thanks. |
I will release on Tuesday morning. |
1.14.0 is released: https://github.com/cap-js-community/odata-v2-adapter/releases/tag/v1.14.0 |
I have an association from /Materials(key)?$expand=ItsMaterialType/ItsText , where ItsMaterialType ( corresponding entity ) has a LargeString in its property. This call gives 500 , intermittent , the below stack trace. Running the same URL again works perfectly. Something to do with cache ?
The text was updated successfully, but these errors were encountered: