logf | structured logger in Go with zero allocation count

Problem: I have a struct which contains a map and two slices. When I pass the pointer value, no matter what I do, these collections within the struct are always nil (i.e. cannot append anything to the map or slices).

Details: I cannot figure out why this is happening. I made a seemingly unrelated change (which I can't remember) and now nothing will append to the Map in the struct. I am passing the Map pointer to subsequent functions, but it keeps throwing an error "panic: assignment to entry in nil map".

I pass the pointers for the LinkResource and the LinkReport type values, but it always says the map is nil. I even forcefully Zeroed the LinkReport struct values with make(...) as a debugging test, but when the value is passed to subsequent functions it still claims the Map and Slices are nil; how is this possible and how do I correct it?

LinkResource

I am supplying different minibatches to optimize a GPflow model (SVGP). If I decorate the optimization_step with tf.function I get the following error:

NotImplementedError: Cannot convert a symbolic Tensor (concat:0) to a numpy array. This error may indicate that you're trying to pass a Tensor to a NumPy call, which is not supported

In order for the optimizer to run I had to remove the tf.function decorator, losing the speed-up advantages. What do I need to change so that I can keep using the tf.function decorator?

The xAndY input shapes and types are all numpy arrays.

i have the following form with 2 inputs (or more). i need to change the label style when input:focus and input:valid and to do so i need label to be after input. how can i reorder label and input with pure javascript?!

p.s. i can't change html manually :)

and please don't mind the css below, it includes additional styles i use for other forms on the page i work on

I'm using aws-go-sdk to create and manage spot instances. Every request I send in order to create a new Spot Instance Request is performed with RequestSpotInstances. I'm trying to get the Instance ID of the instance that was created for my last request, I saw that in the response object RequestSpotInstancesOutput there is a parameter for each instance that was created, but it does not include the instance id, in fact, the InstanceID is not being filled in the RequestSpotInstanceOutput, (returned from RequestSpotInstances call), I tried to use CreateTags in order to create a tag for each instance with the request id, but it didn't work. seen here: TagSpecifications with requestSpotInstances UnexpectedParameter with aws-sdk

I need to print all form requests to log, for later debugging. I need to have something like this, where formInput are different kind of structs. (All defined in my code.)

I cross compiled tensorflow lite C from source for ARM64 using Bazel (https://www.tensorflow.org/lite/guide/build_arm64) and got binary libtensorflowlite_c.so

Now I am trying to compile my C code which uses TFLIte C api functions for arm using android-ndk standalone toolchain but am getting lot of undefined reference errors.

Error Logs:

I am trying to a append a numpy array and a scalar value to a numpy array.

I'm testing a c code for linux with large arrays to measure thread performance, the application scales very well when threads are increased until max cores (8 for Intel 4770), but this is only for the pure math part of my code.

If I add the printf part for resulted arrays then the times becomes too large, from few seconds to several minutes even if redirected to a file, when printf those arrays should add just a few seconds.

The code:

(gcc 7.5.0-Ubuntu 18.04)

without printf loop:

gcc -O3 -m64 exp_multi.c -pthread -lm

with printf loop:

gcc -DPRINT_ARRAY -O3 -m64 exp_multi.c -pthread -lm

I have a simply shader creation pipeline. Nothing special. The shader source reads in properly from what I can tell. Originally, I had the shader code in files with a suffix of '.glsl' just because I wanted to, but they are now plain '.txt' files.

After reading in the shader code, I compile the shader and link the shader as well as check the compile status and info log for errors. The actual shader code below doesn't look to me like it has an error considering it't now basically a carbon copy of a simple tutorial you can find online which I'll link if you need it.

I do get an error though, which is "0(1) : error C0104: Unknown pre-processor directive #version330". This is the same for both the vertex and the fragment shaders, which have an almost identical creation process.

My driver version is [4.6.0 NVIDIA 445.87] as well, so I should be able to use #version 330. I did also have them both set to '#version 330 core', but I was getting the same error.

This is my program and shader creation process.