node-cache | A simple in-memory cache for nodejs | Runtime Evironment library

Instead of a per-dyno cache, you can use something outside of your dynos entirely. Heroku offers several add-ons for common products. I've never used node-cache, but it is described like this:

A simple caching module that has set, get and delete methods and works a little bit like memcached.

That suggests that Memcached might be a good choice. The Memcached Cloud addon has a free 30MB tier and the MemCachier addon has a free 25MB tier.

In either case, or if you choose to host your cache elsewhere, or even if you choose another tool entirely, you would then connect each of your dynos to the same cache. This has several benefits:

• Expiring items would then impact all dynos
• Once an item is cached via one dyno it is already in the cache for other dynos
• Cache content survives dyno restarts, which happen at least daily, so you'll have fewer misses
• Etc.

Fortunately increasing timeoutSeconds for both livenessProbe & readinessProbe from 1 to 60 fixes the issue.

Assuming that excel has data for test automation and it does not include any writing operations, I would suggest reading the content and store it in a constant. If you declare that variable globally, it will be available to all your tests. The complexity of this READ function depends on how diverse is your data. You can use libraries like https://www.npmjs.com/package/xlsx, https://www.npmjs.com/package/exceljs, etc..,

Your production environment variables is missing REACT_APP_API_URL

So it turns out there is a short somewhere between the RX pin and the +3.3V pin which is not allowing me to send anything to the board. Thank you to those who have commented.

Your kernel command line says "console=tty0", which means "please send console to the first virtual terminal", ie to the graphics device. But there is no graphics device in the machine you're running (you say "-nographic" on your QEMU command line and the kernel says "Console: colour dummy device 80x25"). So what happens is that you see the initial bootup messages via the "uart8250" earlycon (ie the serial port), but as soon as the kernel gets to a point where it can honour your command line request, it enables tty0 (which goes nowhere) and disables uart8250 (so you see no further output).

You need to tell the kernel to send the console output to the serial port if that's where you'd like to see it appear, which for the malta board I think you can do by using "console=ttyS0" instead. Alternatively, you can drop '-nographic', make sure your kernel has the driver for the VGA card built in, and leave "console=tty0" and you'll see the console on the virtual console on the graphical window.

If you look at the README for the website you downloaded your image files from you'll see that it does indeed suggest using "console=ttyS0".

The thing that was tripping me up was I had run this as -u root many times and I only have one agent (don't ask) and jenkins caches the workspace directory. So the file permissions had been changed in that code by the docker container running as root. So when I got rid of -u root and it started using the jenkins user it didn't have rights to some files and directories.

The solution was to delete the workspace and make sure that all make calls had an export HOME=${WORKSPACE} before any command.

There might be a better way to export HOME but this solves the prob

You don't seem to be using any library that handles dynamic mapping of your parameters to the required ordinal format into the query itself(like pg-parameterize) so the line:

const sql = 'INSERT INTO public.city(cep, logradouro, complemento, bairro, localidade, uf, ibge, gia, ddd, siafi) VALUES ?';

and more specifically the VALUES ? part shouldn't be doing anything useful. Change that to:

const sql = 'INSERT INTO public.city(cep, logradouro, complemento, bairro, localidade, uf, ibge, gia, ddd, siafi) VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10)';

as the pg npm package is using ordered parameters for parameterized queries.

Checkout the "Parameterized query" section in the docs for queries.

You're either inserting the new record or getting an error. There is no other option. If you don't see any new record in the db after refresh, then you're just swallowing the error result in your code. As you're going the async/await promise route, the code await pool.query(sql, values); will throw if something goes wrong.

Then, in your caller:

You have created a high-order function by returning a function in verificaCache(), so to properly call it you need to do it like that await verificaCache(cep)(req, res), remember, the first time you call it, you have a function being returned, since you want the tasks inside of that function to be executed, you need to call it as well.

Take a reading about high-order functions here: https://blog.alexdevero.com/higher-order-functions-javascript/

My recommendation, you could just get rid of the other function you are returning to simplify your code, and let the service only handle business logic, all the http actions should be handled on the controller level: