statemachine | Simple Finite State Machine in go

I'm trying to use SignalR in my Xamarin Forms project. It works perfectly when I'm using Android (device or simulator). But using the same code on iOS, it hangs at await hubConnection.StartAsync();

I'm using Visual Studio 2022. XAML hot reload is disabled. I've tried adding the System.Memory and System.Buffers IncludeAssets None fix.

Here's the code

I was trying to deploy a practice project to Heroku and it gets deployed. However there is a application error, which is preventing the app to run on the server. I got some details about the errors, after running heroku logs.

I have been able to use awscli to get start the execution but I need to be able to know when is completed or result is success before it can go to the next step in the pipeline.

aws stepfunctions start-execution --state-machine-arn arn:aws:states:us-west-2:2xx244xxxx:stateMachine:SamplePipeOrchestration-ftpiles --name SamplePipeOrchestration-ftpiles --input {} --region us-west-2 --profile sampledev

I'm working on a project with this workflow : an API Gateway (defined using open api) trigger a Step function from AWS. There is 2 steps, and in case of errors, there is a catch block in the State machine definition.

But I'm facing an issue with error handling. Even if my code throw an error (400 for example), my Postman (or other REST API testing tools) respond with a 200. And I would like to have a 500/400...

Here is the code :

Step function definiton as serverless

I'm aware of many posts regarding these warnings in Chrome dev tools. For all of them, the solution is to turn off notifications "Enable javascript source maps" and "Enable CSS source maps".

What I want to know is how to FIX this and what is the reason under the hood that causes these warnings.

I'm currently developing a Vue JS app that uses Twilio Js SDK and I'm getting tons of warnings when the app is built in stage mode by using sudo npm run build -- --mode staging

Any advice will be appreciated.

I am having a lot of issues handling concurrent runs of a StateMachine (Step Function) that does have a GlueJob task in it.

The state machine is initiated by a Lambda that gets trigger by a FIFO SQS queue.

The lambda gets the message, checks how many of state machine instances are running and if this number is below the GlueJob concurrent runs threshold, it starts the State Machine.

The problem I am having is that this check fails most of the time. The state machine starts although there is not enough concurrency available for my GlueJob. Obviously, the message the SQS queue passes to lambda gets processed, so if the state machine fails for this reason, that message is gone forever (unless I catch the exception and send back a new message to the queue).

I believe this behavior is due to the speed messages gets processed by my lambda (although it's a FIFO queue, so 1 message at a time), and the fact that my checker cannot keep up.

I have implemented some time.sleep() here and there to see if things get better, but no substantial improvement.

I would like to ask you if you have ever had issues like this one and how you got them programmatically solved.

Thanks in advance!

This is my checker:

I'm using swifts stateMachine from gamePlayKit. It works great, but there is one thing I don't understand: The stateMachineseems to be its own isolated island; from what I can tell there is no way to pass in arguments or get callbacks. And this raises questions like, how do I update the UI?

Lets say I enter combat state:

I am sure I am missing some basic info but my setup is as follows:

I have 1 lambda function and I have 2 State Machines. Each state machine is calling the same lambda function twice in sequence (30 sec pause between calls) Then I have rules setup to trigger the state machines every minute. Below is what each of my state machines look like, each lambda invoke is for the same function.

Each state machine is passing different params to the lambda function so I am trying to get to a situation where my Lambda function is called every 30 seconds with 1 set of params (from statemachine 1), and the same lambda function is called with a different set of params (via statemachine 2) every 30 seconds.

Looking at the lambda function logs it looks like the state machines will not run the lambda function until the other state machine has completed its entire execution (ie calling the lambda function twice). I would expect that the two state machines would run independently of each other and there would be no timing dependency between them?

Is there some limitation because they are all calling the same lambda function? Or is there some setup issue or is this just how it works?

Thanks!

I am trying to build a statemachine in C++ using variadic templates.