noel | A universal , human-centric , replayable javascript event | Pub Sub library

Assumptions:

• input fields are comma-delimited (while OP's sample input is displayed as fixed-width with pipe boundaries, OP's awk code stipulates "FS=",", and since OP claims the awk code is running and generating output, we'll stick with FS=",")
• the 2nd line in OP's sample input (solid line of hyphens) does not actually exist in OP's file (per fact OP's awk code does not code for NR==2)
• output will be tab-delimited (while OP's awk code mentions OFS="\t\t", the sample outputs appear to be ... fixed-width?)
• Ranking assigments are based on the sorted results (ie, not based on the input ordering as shown in OP's awk code)

Setup:

Use a CTE which returns the column Total for each row and ROW_NUMBER() window function to pick the first 3 rows for each Make and to create the column Ranking:

For sum of columns in a single row you need no extra function like SUM. Use + oerator:

This isn't perfect, but I think it will get you what you are looking for. Your first loops through the data to collect GTIN, LOT, and Date is overwriting itself. Look for the "added" and "removed" in the comments. I also have a method of viewing the results commented out. (The code works if you wanted to use it.) I also have two that are not commented out. The last version requires the packaged tabulate. This code requires the packages numpy and re, as well.

I included all of your original code and the changes. Let me know if there's anything I failed to clarify.

First Solition

In Android Studio, Select File > Project Structure.

In that window, on the left side, select the app module. Once selected, click on the Flavors tab on the top of the window pane. Set your minimum SDK version to 21.

Explanation: As Android updates to new versions, tools that developers use for Android change (& update or deprecate). Because of this, you cannot use new tools on an old version. Version 1 is the very first Android SDK (and we definitely don't want to be using that!). Capacitor requires the SDK be at least version 21.

Second Solution

If that doesn't work, we can always try rebuilding the android app all together. (Note: By doing this, you will lose any custom changes in the AndroidManifest.xml, a custom app icon, etc. If you haven't touched any of these things, then great!).

1. Delete android folder from the Ionic Project's root folder.
2. run command ionic capacitor add android
3. run command ionic capacitor build android
4. Build & run!

To .hamburger[aria-expanded="true"] span:nth-child(3) I have added translateX(-2px).

I did research to try and answer this question, so please take the preface that I am not an expert in IntersectionObserver.

With that preface out of the way,

There were many things I changed from your example to create the desired effect, however the core feature that you would have needed to implement in your example is the option for intersection observers, rootMargin. By adding this option you can give the item on the screen a negative top and bottom margin. This is important, because you do not want the observer to fire until the header is about to cross into the observed section, and you dont want the header to change until just before it crosses back into the next section.

The way I chose to emulate this behavior, is by using the rootMargin option to give a negative margin. This makes the actual element observed begin however many pixels after we specify. For example, an element that is 100px in height, with "0px 0px -20px 0px" as the value for rootMargin in the options object, would not trigger the IntersectionObserver until 20px of the element was scrolled into the viewport height.

With this understanding, we can define our goal. We want to preform an action when the observed element is about to touch the header. We can describe this as the viewport height minus the header height in a negative margin to the bottom would adjust the element just enough to trigger the intersection observer as desired. Because the methods of obtaining margins are not exact, I subtract one from the numbers calculated to adjust for small error. If we set both margins to overlap eachother, we will never have the observer fire.

I also decided to use css variables and set the value of the variable depending on whether or not the element observed scrolled into or out of the viewport.

This code is not able to execute properly in a stack snippet because the viewport option that the intersection observer defaults to in the options is not set correctly for the snippet environment. I have not tested this code in environments that resize.

Hopefully that explanation helps you understand this code. Let me know if you have any questions.

relevant html:

This is the "problematic" part: