CAP | Distributed transaction solution in micro-service base | Microservice library

I am currently setting up a boilerplate with React, Typescript, styled components, webpack etc. and I am getting an error when trying to run eslint:

Error: Must use import to load ES Module

Here is a more verbose version of the error:

Recently I face an issues to install my dependencies using latest Node and NPM on my MacBook Air M1 machine. Then I found out M1 is not supported latest Node version. So my solution, to using NVM and change them to Node v14.16

Everything works well, but when our team apply new eslint configuration. Yet, I still not sure whether eslint was causes the error or not.

I'm getting this error:

On a brand new digitalocean droplet running Ubuntu 20.10 with a brand new pretty near empty rails 7 alpha 2 app running bundle install results in the following both when running cap production deploy on my local machine and when running from the command shell on the droplet

I'm getting data from using print command but in Pandas DataFrame throwing result as : Empty DataFrame,Columns: [],Index: [`]

I'm planning to move away from Docker to Podman. I use docker-compose a lot so am planning to switch to podman-compose as well.

However I'm stuck at the simplest of podman examples, I can't seem to mount a volume onto my container? Obviously I'm doing something wrong however I cant figure out what it is.

My source file definitely exists on my (hardware) host (so not the podman machine). but I keep getting the error 'no such file or directory'.

Funny thing is if I manually create the same file locally on the podman machine (podman machine ssh --> touch /tmp/test.txt) it works perfectly fine.

Question is;

• should I (manually?) mount all my local files onto the Fedora VM (podman machine) so that in turn this Fedora mount can be used in my actual container? and if so, how do I do this?
• The podman run cmd below should work and there is something else I'm doing wrong?

I have been experimenting with full responsive layouts between desktops, tablet, and mobile phone sizes for a bit but am having trouble with the layout below.

I was using a grid layout from bootstrap but since it is two columns, as the width shrinks, the second column of two goes below the left, main content section. I want to split it up as the screen caps below state.

This is the starting view:

This is what I want to happen:

This would be the mobile phone view:

So the wide view will get shrunk during testing and I want it to jump to the mobile view where the top side bar goes above the main content and matches the width of the main content while the bottom sidebar does the same thing to the bottom.

It is easy to put both sidebars on the bottom but I want to try to figure out the possibility of splitting it up.

For testing I am using flexbox, css3 and bootstrap5+ and no plugins or javascript.

As part of an investigation into the parameters of a method, I tried the new Pattern Matching for switch (Preview). Using a traditional condition, it works perfectly:

I’m writing a pretty complex app in React/Redux/Redux Toolkit, and I came across a situation which I’m not really sure how to handle. I found a way to do it, but I’m wondering if it can cause issues or if there is a better way. The short version is that I want the reducer to communicate to the caller without modifying the state, and the only way I’ve found is to mutate the action.

Description:

To simplify, let’s say that I want to implement a horizontal scrollbar (but in reality it’s significantly more complicated). The state contains the current position, a number capped between some min and max values, and the UI draws a rectangle that has that position and that can be clicked and dragged horizontally.

Main property: If the user clicks and drags further than the min/max value, then the rectangle does not move further, but if the user then moves in the other direction, the rectangle should wait until the mouse is back at its original position before starting to move back (exactly like scrollbars behave on most/all operating system).

Keep in mind that my real use case is significantly more complex, I have a dozen of similar situations, sometimes capping between min and max, sometimes snapping every 100 pixels, sometimes more complicated constraints that depend on various parts of the state, etc. I’d like a solution that works in all such cases and that preserves the separation between the UI and the logic.

Constraints:

• I do not want the UI/component/custom hook to have the responsibility to compute when we reach the min/max, because in my use case it can be pretty complex and depend on various parts of the state. So the reducer is the only place that knows whether we did reach the min/max.
• On the other hand, in order to implement the Main property above, I do need to somehow remember where we clicked on the rectangle, or how many pixels of a given "drag" action was handled, in order to know when to start moving back. But I don’t want to store that in the state as it’s really a UI detail that doesn’t belong there (and also because I have quite a few different situations where I need to do that and my state would become significantly more complex, and unnecessary state changes will be performance heavy).

Problem:

So the reducer is the only part that knows if we reached the min/max, and the only way a reducer usually communicates to the rest of the app is through the state, but I don’t want to communicate that information through the state.

Solution?

I actually managed to find a way to solve it, which seems to work just fine but feels somewhat wrong: mutating the action object in the reducer.

The reducer takes the action "dragged by 10 pixels", realizes that it can only drag by 3 pixels, creates a new state where it has been dragged by 3 pixels, and adds an action.response = 3 field to the action.

Then after my custom hook dispatched the "dragged by 10 pixels" action, it looks at the action.response field of the return value of dispatch to know how much was actually handled, and it remembers the difference with the expected value (in this case it remembers that we are 7 pixels away from the original position). In this way, if at the next mousemove we drag by -9 pixels, my custom hook can add that number to the 7 pixels it remembers, and tell the reducer that we only moved by -2 pixels.

It seems to me that this solution preserves separation of UI/logic perfectly:

• The reducer only needs to know by how many pixels we moved and then return the new state and how many pixels were actually handled (through mutating the action)
• The custom hook can remember how far off we are from the original position (without having to know why), and then it will simply correct event.movementX to compensate with how much the reducer didn’t handle in previous actions, and then send the correct delta to the reducer.

It also works just fine with things like snapping at every 100 pixels or such.

The only weird thing is that the reducer mutates the action, which I would assume is not supposed to happen as it should be a pure function, but I couldn’t find any issue with it so far. The app just works, Redux Toolkit doesn’t complain, and the devtools work just fine as well.

Is there any issue with this solution?

Is there another way it could be done?