fero | light , fast , scalable , streaming microservices | Pub Sub library

The gist of this error is that the version of binary used to generate the code isn't compatible with the current version of code. A quick and easy solution would be to try updating the protoc-gen-go compiler and the gRPC library to the latest version.

go get -u github.com/golang/protobuf/protoc-gen-go

then regen the proto

heres a link to a reddit thread that discusses the issue

I see that craco.config.js format needs correction.

Change

The problem seams to be that gorm uses the first gorm.Open argument as a dialect name (it has a set of predefined dialects) and not as a database/sql driver name.

So you need to use a gorm known dialect name as the first argument, in this case you want "postgres" since you will be using postgresql as the underlying database hence you need gorm using the corresponding sql dialect.

Then you tell gorm to use the "txdb" driver and "tx_1" as the connection url.

This seem to work:

From this blog in Oracle magazine, here is what happens if you use an ORDER BY clause in a window function without specifying anything else:

An ORDER BY clause, in the absence of any further windowing clause parameters, effectively adds a default windowing clause: RANGE UNBOUNDED PRECEDING, which means, “The current and previous rows in the current partition are the rows that should be used in the computation.” When an ORDER BY clause isn’t accompanied by a PARTITION clause, the entire set of rows used by the analytic function is the default current partition.

So, your first query is actually the same as this:

You are basically asking how to to create a contained windowing system. This is neither trivial, nor even possible in some operating systems.

If your 4 "executables" are QML code you have access to, you can easily compose them in a single executable.

If they are 3rd party applications, it ain't so easy. It is possible to do that under linux, by utilizing wayland, or even possibly using some X API. But on windows you don't really get that kind of access, at the very least, I haven't found a way to do that, the OS controls the process windows and there isn't much you can do about it.

It might be possible to use the low level GUI APIs windows possibly offers, and if possible, hide the decoration for the 4 windows, and compose the windows so they are on top of your QML application window, and scale and move the 4 windows by code as your QML application window scales and moves.

At any rate, it seems you have wildly underestimated the complexity of implementing this, mostly because it is not an unreasonable expectation that one should be able to do that, but the reality of the situation is different. Windowing systems are very much still black boxes, things people aren't supposed to be meddling with.

It is a good problem, and I did not know about axios interceptors. Anyway, I found a solution for this problem. The main thing is that you have to wrap your interceptor setup in a function, so you can pass the history object as a parameter. And you need the history object. One possible solution is to create one and provide the same history object to the Router as well the wrapped interceptor setup.

It seems like the issue is with your og:url tag. Each time I re-scrape with the sharing debugger it is different. To me, this suggests the get_permalink() method is not returning a consistent result.

FYI, the og:url meta tag is not required, so an easy fix here is just to leave it off. You only really need it if you have multiple URLs to access the same resource and you want to let FB's crawler which is URL is the canonical one.