vg | Virtualgo : Easy and powerful workspace based development | Command Line Interface library

I don't know this protocol, but VarInt in protobuf are coded with the MSB bit:

Each byte in a varint, except the last byte, has the most significant bit (msb) set – this indicates that there are further bytes to come. The lower 7 bits of each byte are used to store the two's complement representation of the number in groups of 7 bits, least significant group first.

Note: Too long for a comment, so posting as an answer.

Update: I browsed a bit through the URL you gave, and it is indeed the ProtoBuf VarInt. It is also described there with pseudo-code:

https://wiki.vg/Protocol#VarInt_and_VarLong

VarInt and VarLong Variable-length format such that smaller numbers use fewer bytes. These are very similar to Protocol Buffer Varints: the 7 least significant bits are used to encode the value and the most significant bit indicates whether there's another byte after it for the next part of the number. The least significant group is written first, followed by each of the more significant groups; thus, VarInts are effectively little endian (however, groups are 7 bits, not 8).

VarInts are never longer than 5 bytes, and VarLongs are never longer than 10 bytes.

Pseudocode to read and write VarInts and VarLongs:

Assigning to stdout (or stdin or stderr) is Undefined Behaviour. And in the face of undefined behaviour, odd things happen.

Technically, no more needs to be said. But after I wrote this answer, @zwol noted in a comment that the glibc documentation claims to allow reassignment of standard IO streams. In those terms, this behaviour is a bug. I accept this fact, but the OP was not predicated on the use of glibc, and there are many other standard library implementations which don't make this guarantee. In some of them, assigning to stdout will raise an error at compile time; in others, it will simply not work or not work consistently. In other words, regardless of glibc, assigning to stdout is Undefined Behaviour, and software which attempts to do so is, at best, unportable. (And, as we see, even on glibc it can lead to unpredictable output.)

But my curiosity was aroused so I investigated a bit. The first thing is to look at the actual code generated by gcc and see what library function is actually being called by each of those output calls:

If you remove things that are related to vgrouter it works.

You could zip the string with an offset like this:

With your shown samples, please try following awk code. We can do all this in single awk.

We have an awk variable named space where I have defined value as 10 as per shown attempts of OP, one could change it as per need.

So, with some help i finally found what was wrong with my process. I would like to point out that honestly, this type of error can be easily avoided by reading the documentation correctly, Which I didn't do...

Here's my final code

Try this line instead:

Curently your VG have those gigabytes, check your screens:

I got a CORS error the in console even though I've already set Access-Control-Allow-Origin to *

The question is:

Are you trying to enable CORS for a Lambda proxy integration or a Lambda non-proxy integration?

Enabling CORS will differ based on the integration type.

First, refer to the Enable CORS on a resource using the API Gateway console section of the Amazon API Gateway developer guide as it includes images etc.

Follow the guide for proxy & non-proxy.

If it is a non-proxy integration, you're done.

If it's a proxy integration (which I don't think it is), your request will still fail - a DELETE request is classed as a complex request by the CORS specification.

This means that if you are making a call to this endpoint using a web app, you may have allowed all origins but you haven't specified which HTTP methods to allow (which the web app will request for in the form of a preflight request before the DELETE request).

So you'll need to also set the Access-Control-Allow-Methods header to * to allow HTTP DELETEin the response returned by your Lambda: