core-api | Streamr Core backend ( being phased out in favour | Messaging library

Unfortunately, the only way I was able to solve this was to update my TensorFlow version to 2.7 from 2.2. I did try to update to 2.3 and 2.4 and it was possible to make some errors go away by finding the specific files and commenting out the lines in questions, but in the end an upgrade was required.

Like I said in my initial question, while the API landing pages mentions that it's '2.2' compatible, they use the experimental code found in later versions.

IMHO there's something substantially wrong with what you're trying to achieve. Serializing the result from your controller method should not contain any logic whatsoever.

Even more, your api should allow content negotiation, where Accept: application/json gives you a json string, and Accept: application/xml gives you an xml string.

Instead you should leverage on Dependency Injection, where you inject MyService in your other service and call myResult.whatever = myService.GetValue() there.

TLDR: use the shared AWS credentials file & delete all code related to credentials within your application including the credentials themselves as they are a security risk.

Never, ever, ever, ever, ever, ever, ever, ever, ever store credentials within application files.

Here is what the AWS SDK for .NET Developer Guide issues important warnings on, for credentials:

Do NOT put literal access keys in your application files. If you do, you create a risk of accidentally exposing your credentials if, for example, you upload the project to a public repository.

Do NOT include files that contain credentials in your project area.

This is pretty much reiterated everywhere else too:

We recommend that you never add your AWS access keys directly to the client in any production files. Many developers have had their account compromised by leaked keys.

Instead, use a method of providing credentials within the default credentials provider chain for the .NET SDK to securely provide credentials to your .NET application.

It's easier and much cleaner than creating a POCO, or handling credentials within your code.

For local development, I always prefer the shared AWS credentials file, which you can create yourself or use aws configure via the AWS CLI to set it up. The AWS SDK will then automatically pick up on the credentials without you needing to specify anything within the code.

Using an AWS credentials file offers the following benefits:

• Your projects’ credentials are stored outside of your projects, so there is no chance of accidentally committing them into version control.
• You can define and name multiple sets of credentials in one place.
• You can easily reuse the same credentials among projects.
• Other AWS SDKs and tools support, this same credentials file. This allows you to reuse your credentials with other tools.

Just please don't hardcode credentials whatever you do.

FYI: session tokens are used to validate temporary AWS credentials. Your access key ID & secret access key are permanent methods of authenticating until they are deactivated/deleted, so you don't need to worry about session tokens at all.

i couldnt do this with nodejs and got no help. so i implemented graphql with python and got more better control in websocket client.

i search for ws, websocket some other shitty packages in nodejs none worked

I have found the solution. Turns out that the server was successfully running, however due to the fact that I didn't have and SSL certificate, the server would not accept the connection except on the unsecured 5001 port.

According to your description, it seems this issue is the https://localhost:5001/api/indicators/GetIndicatorsValues will match both the GetIndicatorsValues and GetByIdAsync. I guess your has a default rule which is like {controller}/{action}/{id?}.

I suggest you could try to modify the controller codes to avoid match the same method and then it will work well.

The problem was in the underlying code of the serialization. So this line:

What you did is about json serialization in asp.net core but what you want is to change the Swagger UI. They are the quite different things.

The first way, you can add attribute like: [FromQuery(Name = "account_number")].

Or you can custom an attribute to avoid writing snake_case:

As per your given information it seems your token has expired, so firstly try to regenerate that, additionally, you have added Delegated permissions that's fine but I doubt you haven added the grant admin consent after adding Graph API permission. So its mandatory and please double check that. See the below screen capture. Please follow the below steps to get token and user info using Microsoft Graph API

Grant Admin Consent:

Token Aquisition Example:

Check the appsettings.json it should be like below: