monoton | Highly scalable , single/multi node | Database library

I am working on a charting module where I can pass on dataframe and the module will create reports based on plots generated by calling few functions as mentioned below.

I am using Altair for plotting and "Datapane" for creating the report, the documentation of the same can be found here : https://datapane.github.io/datapane/

My DataFrame looks like this

I have a requirement where I need to show the values between 1,2 as a group and 2,3 as a seperate group. I am trying to customise the x-axis but it's not working

In the above picture I need to show the bars 3 and 3.5 together with miminum gap between them and in sameway 4 and 4.5 together

and this is my code

I'm having trouble in setting up a task migrating the data in a RDS Database (PostgreSQL, engine 10.15) into an S3 bucket in the initial migration + CDC mode. Both endpoints are configured and tested successfully. I have created the task twice, both times it ran a couple of hours at most, the first time the initial dump went fine and some of the incremental dumps took place as well, the second time only the initial dump finished and no incremental dump was performed before the task failed.

The error message is now:

I am looking for a way to display month numbers in such a way as seen below for a line chart using Recharts library:

As you can see, the chart starts with the first month of each year for 4 years of total data in the x-axis and the month increments by 2 for each year. Each year has a reference line, with the thicker stroke referenceline being the current year and month followed by future months including the next year first month as displayed.

How can I display the ticks on the x-axis along with the month numbers for each year which is denoted with the reference lines (except the beginning of the line chart should not have a reference line)? I am new to react and also to recharts so bear with me. Below is the code I have so far in the recharts components which only takes into account the year at the reference lines as a placeholder:

I'm having trouble deploying a simple Flask app behind a Nginx reverse proxy. The app is the one found at https://docs.docker.com/compose/gettingstarted/

I'm trying to make the app show up at subdomain.example.com/flask but with the current configuration it doesn't work. What i'm missing?

Now my docker-compose.yml looks like this:

I am using a ComposedChart and shoing bars and the line. Usually the line should start from 0 of x-axis. But when using the Composed Chart Not able to do that

If you observe in the above picture tick a should be starting at x axis (the 0 point where x and y axis started) But it's not

This is the code I am using

Redshift's ROW_ID column is somewhat similar to PostgreSQL's OID column. That's a "unique" key for each record in a table, a hidden column added to each table.

Would you expect ROW_ID to be wrapped at some point?

In PostreSQL, OID column are 32 bits only -

OIDs are implemented using 4-byte unsigned integers. They are not unique–OID counter will wrap around at 2³²-1. OID are also used to identify data types (see /usr/include/postgresql/server/catalog/pg_type_d.h).

Because of the wrapping, OIDs in PostgreSQL are not truly unique.

What's scale of ROW_ID in RedShift? Are they expected to be wrapped at some point? Can we expect ROW_ID to be unique? To be monotonically increasing?

Can't find documentation on this.

ps. ROW_ID is documented at least here https://docs.amazonaws.cn/en_us/redshift/latest/dg/c_load_compression_hidden_cols.html but it might has been removed in later versions of Redshift? Thanks

I have been using the following references to try to determine if a Point is inside of a 2D Polygon that has Arcs:

Is a point inside of 2D polygon, no curves

Is a point inside a compound polygon (C#)

Is a point inside a curve (Theory)

My approach uses Ray Casting to determine if a point is within the polygon boundary. This is my code that attempts to string the references together (C#):

I would like to smooth a survival curve so it has no 'steps'. With the following data I am trying this: