Like they said, if you use a language for which serializers aren’t written yet, you can write the encoded event yourself. Here are both the recipe and the link:
| 0 | Magic Byte | Confluent serialization format version number; currently always 0. |
| 1-4 | Schema ID | 4-byte schema ID as returned by Schema Registry. |
| 5-… | Data |
https://docs.confluent.io/platform/current/schema-registry/fundamentals/serdes-develop/index.html#wire-format
#kafka #avro #schema #id #raw #event #wire #format
#GPT4 is so amazing that it is a little bit frightening.
But hey, you can pour it a book and talk… to the book, isn’t it amazing ??
Seriously, the GPTs are incredible and the futur is going to change for sure.
Good or bad, well, wait and see.
PS: I can only encourage you to follow Two Minutes Papers. That channel is just so good, with simple and quick explanations, even when it’s a heavy subject like GPT4
If ever at some points Spotify on Linux refuses to start or start with fucked up graphics, there is a high probability that it’s due to hardware acceleration and a pesky update.
Spotify isn’t that much of a GUI CPU hog, so you can start it with hardware acceleration OFF and make it work again, like this:
spotify –disable-gpu
Some users reported that they needed to use –no-zygote too, but it made it instable for me.
Some had to also use –disable-software-rasterizer. I saw no changes when using it.
#spotify #gpu #linux #crash
Sometimes when using a program linked with librdkafka, you can encounter the ‘symbol lookup error.
Most of the time it’s because your program have been linked to an old version of librdkafka in your system (like outdated RedHat librdkafka yum package VS the latest build from librdkafka’s git)
Solutions:
-Check your LD_LIBRARY_PATH, be sure to find the directories containing latest librdkafka .so file is listed first
-Check what’s installed on your system
-In some case you will have to rebuild your project, having a proper LD_LIBRARY_PATH configured before
#KAFKA #C #librdkafka
In case you’re building yourself everything from source in your project, there is a good chance you once had a problem because you were using relative (like ../myressource) paths in your CFLAGS or LD_FLAGS definition and passed them down to the build system.
Short answer: when getting down in sub directories to i.e build your dependencies, the relative path can’t stay good. Only the absolute path can work.
One solution, if using GNU make, is to use something like this to compute the absolute path:
RES_RELATIVE_PATH=./path_to_my_ressource
RES_ABSOLUTE_PATH=$(realpath $(RES_RELATIVE_PATH))
CFLAGS+= -I$(RES_ABSOLUTE_PATH)
# Note: the naming is up to you. In my case, for something like cJSON, I'm using the following naming:
CJSON_RELPATH=./external/cJSON
CJSON_PATH=$(realpath $(CJSON_RELPATH))
CFLAGS+= -I$(CJSON_PATH)You can also directly initialize with a shell call:
CJSON_CFLAGS=-I$(shell realpath "./external/cJSON")
CFLAGS+= $(CJSON_FLAGS)#code #makefile #gnu #path #absolute #relative
Recently I stumbled upon that kind of error when trying to update a submodule:
git submodule update –remote –merge
fatal: unable to access ‘https://github.com/DaveGamble/cJSON.git/’: Received HTTP code 407 from proxy after CONNECT
Turns out that it was the proxy authentification not being sent correctly.
In our case we are using system defined proxy, so we do not need git’s ones
Solved by using:
git config –global http.proxyAuthMethod ‘basic’
git config –global –unset http.proxy
git config –global –unset https.proxy
Some also encountered SSL verification problems due to auto signed certificate use in their network, and had to disable SSL verification. It’ done with the following command, but we do not recommend to use it unless really needed:
git config –global http.sslVerify false
Have you even stumbled upon a strange warning when trying to print an uint64_t or a size_t ?
Do no take that warning lightly, as your code can break anytime if you’re not fixing it.
Warning example:
warning: format '%llu' expects argument of type 'long long unsigned int', but argument 4 has type 'uint64_t' [-Wformat]
#include <inttypes.h>
uint64_t i;
printf("%"PRIu64"\n", i);
Macros for printf family can be found here.
Are you in search of an open source free and offline alternative to #ChatGPT ?
Here comes GTP4all ! Free, open source, with reproducible datas, and offline.
Can run on Windows, Linux, Mac.
https://github.com/nomic-ai/gpt4all
#ChatGPT #GTP4all
The level app is as simple as possible and allow you to monitor available level meters in a single view.
There is a live graph of each RSSI values and power level.
Link to Documentation
Link to official Nightly build
or click to download compiled version at the time of the post (bin only)
#hackrf #portapack #mayhem #level-app
Edit: it’s the hundredth post of that blog, yay !
I was tasked with the following wishlist:
I wanted to make a robot game were you evade corroding fluids, which led me to fluid animation and Mathias Müller’s Ten Minutes Physics videos and tutorials (see https://matthias-research.github.io/pages/index.html)
I ended up only being able to port his Javascript demo to C, but here it is, and working (need allegro5 installed):
Video of the effect;
UPDATE:
The last version in github is now a threaded processing version.
It’s way quicker.
I left both threaded and unthreaded functions in the sources.
How the same demo is looking now:
KrampusHack 2022 is opened and starting on December 13 to December 31 !
goal. You are secret santa – create a surprising gift for a selected participant.
On Tuesday 13 December 2022, you will be assigned one of the other participants and you have to make your game as a gift for them (Once the competition starts, you can read here for whom you have to make a gift).
Everyone should post a wishlist of features that they would like to see in the game. Note this is a wishlist and not a requirement list – you should tune the game to your giftee, taking the wishlist as well as the person itself into account, and create something that is a nice and thoughtful surprise to them. To make your wish list easily findable, simply post it on your own log.
Rules: https://tins.amarillion.org/krampu22/rules
Join in and have fun with us ! https://tins.amarillion.org/join/
#tins #gamejam #hack #krampus #krampushack
I was searching about a very specific warning that the gcc compiler started to sprout some few weeks ago:
That I extracted and translated from the original that was in French:
“/usr/bin/ld: warning: xxxxxxx.o: requires executable stack (because the .note.GNU-stack section is executable)”
And I stumbled upon that little gem page was one of the few to have a correct explanation:
https://www.redhat.com/en/blog/linkers-warnings-about-executable-stacks-and-segments
And also a few more here:
https://wiki.gentoo.org/wiki/Hardened/GNU_stack_quickstart
#gcc #compiler #linker #warning
MagicLantern page updated with latest build and informations.
Go and check it here
If you use grep / egrep on a single file, it will display the matched patterns, but not the filename nor the line number.
This can be boring in case you encapsulate a grep / egrep call inside i.e a find:
find ./mydir -type f -name '*.msg' -exec grep 'mysearch' {} \;
In that case it will only print the match and you will not know in which file.
The trick is to add a dummy filename as a second file to search. Doing so will trick grep / egrep into thinking you are searching in multiples files, thus displaying the filename on each match.
/dev/null is the perfect target for the second dummy file as it will never match anything.
Example:
find ./mydir -type f -name ‘*.msg’ -exec grep ‘mysearch’ {} /dev/null \;
Bonus / reminder:
In grep / egrep use the -n option to also display the match line number
Example:
find ./mydir -type f -name ‘*.msg’ -exec grep -n ‘mysearch’ {} /dev/null \;
#sysadmin #tips #tricks #grep #egrep