input-format | Formatting user 's text input on-the-fly | Document Editor library

Not very sure about what you mean by hotter, whether it's two different color schemes for the different columns. Here's a modified code from this answer, I split a cool-warm into 2 color schemes. The lower, is used for your first column, the hotter for the 2nd column:

It seems like you're setting 1 lambda to handle 2 trigger sources, one is IoT service, the other is API Gateway Websocket. Since you use 1 lambda, you have to handle cases when the request is came from sources:

1. While event.requestContext is available when the request is triggered from API Gateway, it is not available when the request is triggered from IoT service (check the IoT event object here https://docs.aws.amazon.com/lambda/latest/dg/services-iotevents.html). So the error you faced (which is Cannot read property 'domainName' of undefined") is about that. You should turn off the lambda trigger from IoT service or handle the request when it comes from IoT Service.
2. I'm not sure about the forbidden error but it is more like you sent unstructured message to API gateway WS, it should be connection.send(JSON.stringify({ action: "sendmessage", data: "hello world" })); instead of connection.send("hello world");

Edited based on post update:

I know ws is there because if I console it it returns a big object with a bunch of functions

Lambda function is not really a server, it is an instance Node environment (that's why it is called FUNCTION), Lambda function doesn't work as the way you think normal Nodejs app does, its container (node environment) usually is halted (or freeze) whenever its job is done so you cannot keep its container alive like a normal server. That's the reason while you can console log the Websocket object, you cannot keep it alive, the NodeJS container was already halted whenever you return/response.

Since you cannot use the Websocket object to open WS connection in Lambda, Amazon offers a way to do that via API Gateway. The way we work with API Gateway Websocket is different than the normal server does too, it would be something like:

• User -> request to API Gateway to connect to websocket -> call Lambda 1 (onconnect function)
• User -> request to API Gateway to send message over Websocket -> call Lambda 2 (sendmessage function)
• User -> request to API Gateway to close connection -> call Lambda 3 (ondisconnect function)

3 settings above is configured in API Gateway (https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-websocket-api-integrations.html), logic of 3 functions onconnect, sendmessage, ondisconnect can be handled in 1 lambda or 3 lambda functions depending on the way we design, I check your 3 lambda functions and it looks okay.

I see that you want to use IoT but I'm not sure why. You should test your Websocket API first without anything related to IoT. It would be better if you can tell what you want to achieve here since IoT works more like a publish/subscribe/messaging channel and I don't think it's necessary to use it here.

It seems I was editing the python file at "python-debugging/hello_world/build" following the guideline of the doc (there is a step in the doc which asks you to copy the python file to "python-debugging/hello_world/build").

But then when you run "sam local start-api", it actually runs the python file at the location specifed by the CloudFormation template (tempalted.yaml), which is at "python-debugging/hello_world" (check the "CodeUri" property).

When I moved all the libriaries to the same folder as the python file it works.

So I suppose you have to make sure which python (or lambda) script you are running, and ensure the libraries are together with the python script (if you are not using layers).

Folder structure

Entering debugging mode in Visual studio code Step 1: Invoke and start up the local API gateway

• Server

Step 2: Send a test request

• Client

Step 3: Request received, lambda triggered, pending activating debug mode in Visual Studio Code

• Server

Step 4: Lambda function triggered, entering debug mode in Visual Studio Code

In the IDE, open the "Run" perspective, select the launch config for this file ("SAM CLI Python Hello World"). Start the debug.

Step 5: Step through the function, return response

• Server

• Client

Im not sure if this is the answer but, You cant use async/await inside foreach. use for of instead.

As mentioned by Isabelle Newbie in the comments, swipl.exe (that is started by default) has a long-running bug associated with proper input/output. Navigating to where Prolog is installed and instead using swipl-win.exe seems to have done the trick.

Your question has no sense. CH does not have a system catalog. You can manually fix metadata .sql or parts.

clickhouse-local is the same binary as server. It's the same tool.

clickhouse-local is just a synonym (symbolic link)

I got it working. I ended up creating a second lambda to push to the database as the call bakc url for the google auth. and then 301 redirect to localhost for now.

I needed to also add event updates for stripe sku creation in the webhook in stripes dashboard. A little confusing, but now I have all the data.

The main solution to my problem was running sam init again, installing node version 12