perf-regression: collect report at each staging release

The idea is to start collecting performance regression report at each staging release. From there, we would learn whether:

the report generation can be run on distinct machines, operating systems
reports looks consistent across versions, machines, operating systems
the default duration of 10 minutes is a good trade-off to quickly spot potential regressions
the current scenario provide the best value
it would be valuable to reject a release with -5% regression detected

Camel Quarkus Throughput Performance Increase Compared to Previous Version
Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
            2.12.0  |       10m  |  21492.67 req/s [+0.00%]  |   11516.03 req/s [+0.00%]  |      OK  |
            2.13.0  |       10m  |  21299.82 req/s [-0.90%]  |   11828.55 req/s [+2.71%]  |      OK  |

Camel Quarkus Throughput Performance Increase Compared to Previous Version
Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                2.13.0  |       10m  |  38872.21 req/s [+0.00%]  |   22154.66 req/s [+0.00%]  |      OK  |
                2.15.0  |       10m  |  38605.46 req/s [-0.69%]  |   22438.48 req/s [+1.28%]  |      OK  |

 Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                2.13.1  |       10m  |  38888.74 req/s [+0.00%]  |   22779.41 req/s [+0.00%]  |      OK  |
                2.13.2  |       10m  |  38918.29 req/s [+0.08%]  |   23068.36 req/s [+1.27%]  |      OK  |

 Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |               Status               |
------------------------------------------------------------------------------------------------------------------------------------
                2.16.0  |       10m  |  23394.75 req/s [+0.00%]  |   13429.86 req/s [+0.00%]  |                                OK  |
              3.0.0-M1  |       10m  |  23976.32 req/s [+2.49%]  |   12576.25 req/s [-6.36%]  |  Potential performance regression  |
2023-03-20 20:33:52,502 INFO  [io.quarkus] (main) perf-regression stopped in 0.006s

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                2.13.2  |       10m  |  39515.19 req/s [+0.00%]  |   23098.37 req/s [+0.00%]  |      OK  |
                2.13.3  |       10m  |  39745.16 req/s [+0.58%]  |   22774.74 req/s [-1.40%]  |      OK  |

            Camel Quarkus Throughput Performance Increase Compared to Previous Version

Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
          3.0.0-M1  |       10m  |  25477.00 req/s [+0.00%]  |   13664.18 req/s [+0.00%]  |      OK  |
          3.0.0-M2  |       10m  |  27129.07 req/s [+6.48%]  |   14002.18 req/s [+2.47%]  |      OK  |

               Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |  JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
---------------------------------------------------------------------------------------------------------
              3.0.0-M2  |       10m  |  9569.35 req/s [+0.00%]  |    6022.07 req/s [+0.00%]  |      OK  |
             3.0.0-RC1  |       10m  |  9091.22 req/s [-5.00%]  |    6312.80 req/s [+4.83%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
             3.0.0-RC1  |       10m  |  39443.07 req/s [+0.00%]  |   22666.68 req/s [+0.00%]  |      OK  |
             3.0.0-RC2  |       10m  |  39347.05 req/s [-0.24%]  |   22559.33 req/s [-0.47%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
             3.0.0-RC2  |       10m  |  40384.40 req/s [+0.00%]  |   22582.53 req/s [+0.00%]  |      OK  |
                 3.2.0  |       10m  |  39638.48 req/s [-1.85%]  |   22462.29 req/s [-0.53%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.2.0  |       10m  |  39873.77 req/s [+0.00%]  |   22604.50 req/s [+0.00%]  |      OK  |
                 3.4.0  |       10m  |  39788.82 req/s [-0.21%]  |   22057.67 req/s [-2.42%]  |      OK  |

 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.2.0  |       10m  |  19495.67 req/s [+0.00%]  |   11577.53 req/s [+0.00%]  |      OK  |
                 3.2.1  |       10m  |  19257.06 req/s [-1.22%]  |   11733.54 req/s [+1.35%]  |      OK  |

                             Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]    |  Native req/s [%increase]  |               Status               |
-------------------------------------------------------------------------------------------------------------------------------------
                 3.4.0  |       10m  |   20250.91 req/s [+0.00%]  |   12564.35 req/s [+0.00%]  |                                OK  |
                 3.5.0  |       10m  |  15222.80 req/s [-24.83%]  |   9273.02 req/s [-26.20%]  |  Potential performance regression  |

                             Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]    |  Native req/s [%increase]  |               Status               |
-------------------------------------------------------------------------------------------------------------------------------------
                 3.4.0  |       10m  |   20250.91 req/s [+0.00%]  |   12564.35 req/s [+0.00%]  |                                OK  |
                 3.5.0  |       10m  |  15222.80 req/s [-24.83%]  |   9273.02 req/s [-26.20%]  |  Potential performance regression  |

Woops, this looks pretty bad. Let's try to confirm this measure with other runs, possibly 1h duration.

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.2.1  |       10m  |  19241.25 req/s [+0.00%]  |   12220.36 req/s [+0.00%]  |      OK  |
                 3.2.2  |       10m  |  19023.79 req/s [-1.13%]  |   11801.31 req/s [-3.43%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]    |  Native req/s [%increase]  |  Status  |
-----------------------------------------------------------------------------------------------------------
                 3.5.0  |       10m  |   10184.32 req/s [+0.00%]  |    6655.12 req/s [+0.00%]  |      OK  |
                 3.6.0  |       10m  |  11328.00 req/s [+11.23%]  |   7618.24 req/s [+14.47%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.2.2  |       10m  |  26745.20 req/s [+0.00%]  |   16353.16 req/s [+0.00%]  |      OK  |
                 3.2.3  |       10m  |  25663.29 req/s [-4.05%]  |   15666.90 req/s [-4.20%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.6.0  |       10m  |  20520.59 req/s [+0.00%]  |   11885.86 req/s [+0.00%]  |      OK  |
                 3.7.0  |       10m  |  20577.29 req/s [+0.28%]  |   11885.30 req/s [-0.00%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.7.0  |       10m  |  33532.36 req/s [+0.00%]  |   17749.33 req/s [+0.00%]  |      OK  |
                 3.8.0  |       10m  |  32340.26 req/s [-3.56%]  |   17498.96 req/s [-1.41%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.8.0  |       10m  |  19217.32 req/s [+0.00%]  |   11275.71 req/s [+0.00%]  |      OK  |
                 3.8.1  |       10m  |  19457.29 req/s [+1.25%]  |   11112.60 req/s [-1.45%]  |      OK  |
2024-03-18 08:42:35,326 INFO  [io.quarkus] (main) perf-regression stopped in 0.006s

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.8.0  |       10m  |  32583.61 req/s [+0.00%]  |   17899.62 req/s [+0.00%]  |      OK  |
                 3.9.0  |       10m  |  32610.64 req/s [+0.08%]  |   17575.19 req/s [-1.81%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.8.1  |       10m  |  19543.29 req/s [+0.00%]  |   11300.57 req/s [+0.00%]  |      OK  |
                 3.8.2  |       10m  |  19289.10 req/s [-1.30%]  |   11163.94 req/s [-1.21%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                3.11.0  |       10m  |  31612.49 req/s [+0.00%]  |   16867.78 req/s [+0.00%]  |      OK  |
                3.12.0  |       10m  |  30904.69 req/s [-2.24%]  |   17089.98 req/s [+1.32%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.8.2  |       10m  |  19512.99 req/s [+0.00%]  |   11358.99 req/s [+0.00%]  |      OK  |
                 3.8.3  |       10m  |  20256.12 req/s [+3.81%]  |   11189.47 req/s [-1.49%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                3.12.0  |       10m  |  19220.23 req/s [+0.00%]  |   11335.07 req/s [+0.00%]  |      OK  |
                3.13.0  |       10m  |  19540.48 req/s [+1.67%]  |   11387.82 req/s [+0.47%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                3.13.0  |       10m  |  31313.87 req/s [+0.00%]  |   17044.78 req/s [+0.00%]  |      OK  |
                3.14.0  |       10m  |  31667.66 req/s [+1.13%]  |   17015.65 req/s [-0.17%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                3.14.0  |       10m  |  19539.85 req/s [+0.00%]  |   11221.73 req/s [+0.00%]  |      OK  |
                3.15.0  |       10m  |  19359.64 req/s [-0.92%]  |   10901.39 req/s [-2.85%]  |      OK  |
2024-09-19 12:51:07,012 INFO  [io.quarkus] (main) perf-regression stopped in 0.007s

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                3.15.0  |       10m  |  19720.46 req/s [+0.00%]  |   11058.51 req/s [+0.00%]  |      OK  |
                3.16.0  |       10m  |  19449.12 req/s [-1.38%]  |   11244.35 req/s [+1.68%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                3.15.0  |       10m  |  19221.50 req/s [+0.00%]  |   11110.07 req/s [+0.00%]  |      OK  |
                3.15.1  |       10m  |  19264.67 req/s [+0.22%]  |   11014.42 req/s [-0.86%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                 3.8.3  |       10m  |  19278.67 req/s [+0.00%]  |   11101.30 req/s [+0.00%]  |      OK  |
                 3.8.4  |       10m  |  19503.30 req/s [+1.17%]  |   11090.91 req/s [-0.09%]  |      OK  |

                Camel Quarkus Throughput Performance Increase Compared to Previous Version
 Camel Quarkus version  |  Duration  |   JVM req/s [%increase]   |  Native req/s [%increase]  |  Status  |
----------------------------------------------------------------------------------------------------------
                3.16.0  |       10m  |  19489.36 req/s [+0.00%]  |   10753.13 req/s [+0.00%]  |      OK  |
                3.17.0  |       10m  |  19313.40 req/s [-0.90%]  |   10559.63 req/s [-1.80%]  |      OK  |


fix(types): update Channels type

Hey @lovell, improving on the types again
This PR adds 1 and 2 as possible values for the Channels type:
1: The image has only one channel representing grayscale values. Each pixel is stored as a single intensity value, ranging from black to white.
2:  The image could have one channel for grayscale intensity and another channel for alpha (transparency). This is similar to an RGBA image but without the color information, only grayscale (intensity) and alpha.
Possibly there are other reasons for a 2 channel Image but this is the most common one in my experience

Thanks for the PR. It looks like Channels is also used to define the interface when creating an image, and that should continue to only allow a value of 3 or 4.
https://github.com/lovell/sharp/blob/fc32e0bd3f9111b80cf078df7b0cfc355695674e/lib/index.d.ts#L985-L986
Perhaps we could split this into something like CreateChannels vs Channels?

Landed via commit https://github.com/lovell/sharp/commit/1533bf995acda779313fc178d2b9d46791349961, thank you for fixing this.


Updates for displaying pagination total number.

Coverage remained the same at 50.277% when pulling 61657600b362eef8778c2a2b35ba5c929a259fe9 on wknet123:dev-show-totals into 5cf381fc43feda8bb7af93fd529ab0ca894e20d0 on vmware:dev.


Fix issue with ab testing regarding UITabBarButton image change

Fix issue with ab testing regarding UITabBarButton image change showing for all buttons rather than a single one

Is there any way to add a unit test for this?

Sure, how would you like to test it though? The best way is to add a UITabBar and see if the changes show when editing the image of the tab bar button. But that is done manually rather than an exclusive unit test. I'm open to suggestions


Adding new CMS: Troglio

New headless CMS in town :)

Using Trello as a CMS is a really interesting concept, thanks for the add!
We'll need to leave this PR open until:

Troglio can be used (can't install the power up in Trello as far as I can tell)
The source is published to the GitHub repo

Please comment once you're there and we can get this merged.

Hey @erquhart I may have made a mistake in the markdown file: Troglio is not open sourced for now though it is publicly available at https://powerup.troglio.com.
Regarding the install, please check our guide at https://troglio.com/guide/enable-troglio.
Basically, Troglio needs to be installed manually, and not through the Trello panel for now.


Shashank/Typo fix reflecting in mobile app

Coverage remained the same at 57.391% when pulling 692f847a3a8420373c9736374baa18ee8ca49fe6 on Shashank-In:patch-1 into b9ba63325f17b7b128ebd65e571f4635f41f83a7 on binary-com:master.


Version `GLIBC_2.34' not found.

I got these errors after run spf :
./spf: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./spf)
./spf: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./spf)

It looks like you need to install libc.so.6.
Can you try it?

yes.
the result of sudo apt install libc6 is this:
libc6 is already the newest version (2.31-13+deb11u10).

I think this seems to be an ubuntu package problem
Maybe you can try it
https://www.reddit.com/r/linux4noobs/comments/15nfcwb/version_glibc_234_not_found_when_using_the/

i tried but dont working... :(

Apparently, GitHub Actions' glibc version is too high causing this problem. Building precompiled binaries that link to libc should take this into account.
There are two possible solutions, either compiling under a lower version of glibc, which docker will help with, or using a c compiler that supports setting the glibc version, such as zig cc or something like that

If you want to support the major operating systems, it would be a good idea to set it to 2.17, which will support almost all still-active distros. But configuring the environment can be a pain, only centos7 out of the mainstream distros I know of still uses glibc at such a low version. or 2.22/23, which is pre-installed on Ubuntu 16.
Check out https://repology.org/project/glibc/versions for the full list

Or, alternatively, opt for a direct static link to musl so that you don't have to think about all this hassle. Static linking to glibc is not recommended for complex reasons, and many good explanations can be found on Google.

I'm going to close this issue for now, but if there are any more problems, feel free to reopen it.


tmux status bar text need a higher contrast

Description
I tried 'nightfox' and 'dayfox' themes for tmux, the text in the status bar are hard to see, as you can see in the following screenshots.
Screenshots
dayfox

nightfox

Configuration
https://github.com/edeneast/nightfox.nvim/raw/main/extra/dayfox/nightfox_tmux.tmux
https://github.com/edeneast/nightfox.nvim/raw/main/extra/nightfox/nightfox_tmux.tmux

Resolved by #264


Can't Run Sparkswap Desktop

I downloaded the appimage on a fresh installation of debian, made it executable using chmod a+x, and tried to execute it. I got this error message:
[4388:1201/140302.353000:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /tmp/.mount_SparksBpSYBG/chrome-sandbox is owned by root and has mode 4755.
Trace/breakpoint trap
I don't see a directory called .mount_SparksBpSYBG in my /tmp/ directory. What should I do?

Hey @supertestnet !! Thanks for giving us the heads up. I haven't seen this error before, but https://github.com/electron/electron/issues/17972 looks like its related. I'll see if there is something we (sparkswap) can do for the app (aside from using --no-sandbox)
I'll continue to post updates on this issue if there is a resolution. FWIW this looks to be affecting debian (not ubuntu to my knowledge)

Additionally, this tutorial has some decent info on the cause of the error: https://equk.co.uk/2018/04/02/forcing-namespace-sandbox-in-chrome-electron

Your second link had the solution I needed:
sudo sh -c "echo 'kernel.unprivileged_userns_clone=1' > /etc/sysctl.d/00-userns.conf"
After running that, and restarting, Sparkswap started up perfectly. 👍


For a quick start, lithops test failed as "storage_bucket is mandatory"

It's understandable that I'll need to use Cloud Object Storage with lithops sooner or later. But, for a quick starter, I just wanted to run the "lithops test" on my local machine only to make sure the installation and initial configuration are good.
This is my simple config file in ~/.lithops/
lithops:
        storage: localhost
        executor: localhost

The installation was successfully:
...
Successfully installed Click-7.1.2 bcrypt-3.2.0 cachetools-4.1.1 cycler-0.10.0 docker-4.3.1 docutils-0.15.2 glob2-0.7 google-auth-1.23.0 ibm-cos-sdk-2.8.0 ibm-cos-sdk-core-2.8.0 ibm-cos-sdk-s3transfer-2.8.0 jmespath-0.10.0 kiwisolver-1.3.1 kubernetes-12.0.0 lithops-2.2.2 lxml-4.6.1 matplotlib-3.3.2 numpy-1.19.3 oauthlib-3.1.0 pandas-1.1.4 paramiko-2.7.2 pika-0.13.1 pillow-8.0.1 pyasn1-0.4.8 pyasn1-modules-0.2.8 pynacl-1.4.0 python-dateutil-2.8.1 pytz-2020.4 redis-3.5.3 requests-oauthlib-1.3.0 rsa-4.6 scipy-1.5.3 seaborn-0.11.0 tblib-1.7.0 websocket-client-0.57.0

And, lithops test failed due to "storage_bucket is mandatory...", which is not true.
...
    log_level=log_level
  File "/Users/thanhlam-us.ibm.com/anaconda/lib/python3.6/site-packages/lithops/executors.py", line 51, in __init__
    config = default_config(copy.deepcopy(config))
  File "/Users/thanhlam-us.ibm.com/anaconda/lib/python3.6/site-packages/lithops/config.py", line 124, in default_config
    raise Exception("storage_bucket is mandatory in lithops section of the configuration")
Exception: storage_bucket is mandatory in lithops section of the configuration

Fixed in master branch, thanks @thanh-lam

@JosepSampe , thank you! That's quick. Will the issue close itself or I'll have to do that after verifying the fix? I installed it by using pip. So I probably have to wait until the new version is available with pip install.

@thanh-lam i will make a new release asap

@thanh-lam I just released version 2.2.3. Hope it solve the issue

@gilv , thanks for the new version! It's installed and lithops test now works! Looking forwards to explore further with lithops.
$ lithops test
WARNING:root:'executor' key in lithopos section is deprecated, use 'mode' key instead
WARNING:root:'executor' key in lithopos section is deprecated, use 'mode' key instead
Lithops v2.2.3 init for Localhost
ExecutorID acb378/0 | JobID A000 - Selected Runtime: python3 (Installing...)
ExecutorID acb378/0 | JobID A000 - Uploading function and data - Total: 697.0B
ExecutorID acb378/0 | JobID A000 - hello() Invocation done - Total: 1 activations
ExecutorID acb378/0 - Getting results...

  100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1

ExecutorID acb378/0 - Cleaning temporary data

Hello World! Lithops is working as expected :)

@thanh-lam Great! Note that with the recent modifications there is no need to have a config file for running jobs in the localhost


IUnityContainer does not contain a definition for LoadConfiguration()

Description
I've upgrade the nuget package from 4.0.1 to 5.8.6 and now it's saying that it cannot find the method loadconfiguration
To Reproduce
using System;
using System.Threading;
using Unity;
using Unity.Configuration;
namespace Puzzle.Web
{
internal static class UnityConfig
{
private static Lazy container =
new Lazy(() =>
{
var container = new UnityContainer();
RegisterTypes(container);
return container;
}, LazyThreadSafetyMode.PublicationOnly);
    internal static IUnityContainer Container => container.Value;

    internal static void RegisterTypes(IUnityContainer container)
    {
        // NOTE: To load from web.config uncomment the line below.
        // Make sure to add a Unity.Configuration to the using statements.
        container.LoadConfiguration();
    }
}

}
Additional context
This is to load the mappings from the web config file.
I've also changed

Ah I see. We still require the following namespace 'using Microsoft.Practices.Unity.Configuration;'


feat: add more reservation control to create nexus

This allows the create to specify whether we want to preempt the existing holder when the existing holder is not known.
EG: If a nexus create times out, we don't know if the reservations have changed or not, so if we attempt to create a nexus, which reservation key do we preempt? With NexusNvmePreemption::Holder we can preempt the existing holder, whomever that might be.
This logic is already kind used by the dataplane, but only if the existing holder is type 1, which we cannot create at the moment as we hardcode to 5, which is a "shared" scheme. By passing the resvType as an arg, it allows us to control that, and also might be useful for the future.


Russian translation

Translation for Russian language

Rebased changes from @Limych PR, with some changes

Your changes, unfortunately, are full of neologisms, which are often extremely difficult to perceive by the older generation of users. In addition, some of the phrases are written so that their meaning can be confused to the contrary. And others have exactly the same meaning, but they are written longer.
I took this into account when creating my translation.
The only correct change is for the “Cancel” button. Thank you.


Not possible to find-all-references for export default of anonymous type

TypeScript Version:  2.5.3
Code
export default function () {}

Expected behavior:
It is possible, somehow, to Find all references of the exported anonymous function declaration.
Actual behavior:
It is not possible to Find all references through any means other than temporarily giving the function declaration a name; or to import it from somewhere else and try to Find all references of the imported value.
This also affects anonymous classes and anonymous expression results.

In this case, the best case behavior would be that asking to Find all references of the default token in export default would find the references to the default export.

default should get you the references..

I happened to reproduce it now in my project but not with an anonymous function, but an anonymous expression.
Not possible to find all references:
export default connect(mapStateToProps, mapDispatchToProps)(Settings)

Possible to find all references by searching for references to default:
const x = connect(mapStateToProps, mapDispatchToProps)(Settings)
export { x as default }

Note that searching for references to the x variable does not report things that import it, even though it is an aliased live-binding export. Only looking for references to default return users of the component.
In either case, it's not possible to find them in any way with the export default connect(...)(...) expression.
This was tested with 2.5.3 as I have not been able to update to 2.6.0 yet.

I see. thanks for the repro. here is a simpler repro:
export default 1;


feat: update tbDEXHttpClient to use submitCancel()

this pr replaces the submitClose() method with submitCancel() since the Close message is reserved for PFI use while the Cancel message is reserved for clients

Codecov Report
Attention: Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.

Project coverage is 93.59%. Comparing base (7d7e6d5) to head (2869b5b).

Files with missing lines
Patch %
Lines

...s/tbDEXTests/HttpClient/tbDEXHttpClientTests.swift
83.33%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #104   +/-   ##
=======================================
  Coverage   93.59%   93.59%
=======================================
  Files          36       36
  Lines        1374     1374
=======================================
  Hits         1286     1286
  Misses         88       88

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[4.0.0-beta2] Thread.get_CurrentThread in UWP

Hi!
I found some bug in 4.0.0-beta2 from master https://github.com/mbdavid/LiteDB/commit/c0904d371d20735d73b985a2ed165f905e450d08
When I use LiteDB with UWP (10240 min.target), it throws exception:
System.Exception: Method 'Thread.get_CurrentThread()' was not included in compilation, but was referenced in LockService.Read(). There may have been a missing assembly.
   at LiteDB.LiteEngine.<Find>d__9.MoveNext()
   at LiteDB.LiteEngine.<Find>d__13.MoveNext()
   at LiteDB.LiteCollection<LiteDB.BsonDocument>.<Find>d__17.MoveNext()
   at FSClient!<BaseAddress>+0xc5988d
   at FSClient.Shared.Repositories.FavoritesRepository.ToDictionary()
   at FSClient!<BaseAddress>+0x1007830

After some google I found, that Thread.CurrentThread in some reason is not available in UWP, and we have to use Task.CurrentId.
But we can't use Task in Net3.5.
So, next code works well (in UWP at least)
#if !NET35
using System.Threading.Tasks;
#endif

#if NET35
_log.Write(Logger.LOCK, "exited read lock mode in thread #{0}", Thread.CurrentThread.ManagedThreadId);
#else
_log.Write(Logger.LOCK, "exited read lock mode in thread #{0}", Task.CurrentId);
#endif

I not sure, is it the best solution.
But I desired to write about issue.

Hi @Tirraon, thanks! I'm fixing this now. For final v4 release, I will remove .net 3.5 support because there are too much differences.


Music Playlist with Online Content is not working

What version of Music Assistant has the issue?
2.1.0
What version of the Home Assistant Integration have you got installed?
No response
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
Platform:

intel NUC with music assistant server 2.1.0 in docker container
I have YouTube music as my provider

Issue:

I created a playlist on Music Assistant
Searched for a track on the search page
Selected the track 3 dots menu
Chose add to playlist and selected the newly created playlist
System reports:

The action is performed by the server in the background and may take some time to complete. Keep an eye on the server log for progress.

The playlist remains empty and nothing in the logs except "adding track xxx to playlist".
Is there something im doing wrong?
How to reproduce
Steps above
Music Providers
Youtube music
Player Providers
Chromecast
Full log output
No response
Additional information
No response
What version of Home Assistant Core are your running
None
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

Ok, i restarted the container now it works fine..
I will close it here.m


Sparse Vector

Just wondering,
if pqkmeans can be optimized for sparse vectors
, csr format, instead of dense ones
thank you

No. You need to convert sparse vectors to dense ones before applying pqkmeans.
My general advice is to project the sparse data to a lower (denser) space, e.g., from D=10K to D=100. That way, PQ will work better.

Thanks.
Is there a way to project in a  fast way on
low dense ?
(umap exists but, not so fast).
Yes, kmeans require gaussian vectors…..

On Dec 27, 2021, at 10:43, Yusuke Matsui @.***> wrote:

No. You need to convert sparse vectors to dense ones before applying pqkmeans.
My general advice is to project the sparse data to a lower (denser) space, e.g., from D=10K to D=100. That way, PQ will work better.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.

You can try multiplying by a random matrix. Multiplication of a matrix and a sparse vector would be generally fast.

Thanks.
Interesting way to give “gaussianity” to
a vector…. and should preserve distance.

On Dec 30, 2021, at 0:41, Yusuke Matsui @.***> wrote:

You can try multiplying by a random matrix. Multiplication of a matrix and a sparse vector would be generally fast.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.


🐛 Mobile | Settings page issues

The Settings page has some issues that should be resolved.

[x] Investigate the tap colour differences between iOS and Android
[x] Dividers have different colours on iOS and Android
[x] Close button is too large on the About popup
[x] "Get Started" button in intro should be removed
[x] QR scanner should not be displayed

Done - Anton completed the issue with dividers on Android here: #932

Figure: Dividers for headers and cells are transparent


Result Set Bundling

Provide a func interface for packaging results sets as they are intended to be used by the application. Should be a nice feature for when multiple result sets are used to represent child collections or related objects of a parent object, by allowing the user the option of strongly associating the bundling work to the command.

FluentData has an interesting way of handling multiple results that may be a good blend of functionality with this and Dapper's GridReader concept.


feat: ✨ adds UserFollows widget/component

Status
READY
Description

Adds the UserFollows widget/component

Contains followers & follows count and is going to be used later in the profile page header.

Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

Oh, and it would be great as well if PRs only have 1 commit (and merges). But you can merge this without fixing it. Just saying it so we have it that way in upcoming PRs 👍🏻

Oh, and it would be great as well if PRs only have 1 commit (and merges). But you can merge this without fixing it. Just saying it so we have it that way in upcoming PRs 👍🏻

Just FYI I usually do the 1 commit thing after you review just in case I have to add additional edits and commits.

No worries. To hard enforce this in the future, we should also have an action that checks for such a convention. But I think we currently have better things to do 😀


Change topbar month header background colour

Hello,
How to change topbar month header background colour,

I would suggest playing around with the setters for header or implementing your own. Sorry for the delay.


Enhancing the HHL algorithm

What is the expected enhancement?
Improving the HHL algorithm as follows:

Support matrices beyond those of size 2^n x 2^n
Support non-Hermitian matrices
Separate the classical verification into a classical algorithm

The requested enhancements have now been added by the above referenced PRs and so this is complete


[SDK Cold Start] - Retry Metadata Requests in Other Regions When Preferred Regions is Empty and Hub Region is Offlined

Acceptance Criteria:

Today, when the .NET sdk is in clod start mode and the primary hub region is experiencing an outage, given that the user didn't specify the preferred regions list, the SDK won't do a cross regional retry to get the metadata information.

This behavior causes the SDK to act as a single point of failure in the above situation, and the goal of this task is to fix this behavior and do cross regional retry attempts, even when the user didn't specify the preferred regions list. That ideally means to populate the preferred regions internally, when the list is provided empty.

@kundadebdatta This is not just limited to cold start only right?
In general to have HA with GlobalEndpoint when the PrefrredRegions are not set.

@kundadebdatta This is not just limited to cold start only right? In general to have HA with GlobalEndpoint when the PrefrredRegions are not set.

Correct - I'd say the pending fix won't help with cold start at all as it isn't possible to construct region suffixed endpoints for the SDK to reach out for database account resolution without preferred regions. The fix will help to not have availability be restricted to just hub / primary in case of an outage to hub / primary once the client has been warmed / has cached account metadata even with preferred regions not set.

@kundadebdatta This is not just limited to cold start only right? In general to have HA with GlobalEndpoint when the PrefrredRegions are not set.

Yes correct - this is not just bounded to cold start scenarios.


Release policy

Hi,
what is your release policy, when can we expect the next release.
Thanks a lot in advance
Frank

There is not really a release policy
First I make some test and then there is git tag -> so carthage could use it easily
then I must publish to cocoapods
Everybody could use HEAD code we cautious. If there is a fix that someone want, I could make a new release if I have time for testing


chore: Setup chromatic

Codecov Report

Merging #399 (52cee93) into main (b713660) will decrease coverage by 0.05%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #399      +/-   ##
==========================================
- Coverage   41.26%   41.20%   -0.06%
==========================================
  Files         158      158
  Lines        1711     1711
  Branches      305      305
==========================================
- Hits          706      705       -1
- Misses        963      964       +1
  Partials       42       42

Flag
Coverage Δ

client
36.93% <50.00%> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...client/src/components/ui/Avatar/Avatar.stories.tsx
0.00% <ø> (ø)

...il/client/src/components/ui/Avatar/AvatarGroup.tsx
38.46% <ø> (ø)

...l/client/src/components/ui/Entry/Entry.stories.tsx
0.00% <ø> (ø)

...client/src/components/ui/Marker/Marker.stories.tsx
0.00% <ø> (ø)

...client/src/components/ui/Switch/Switch.stories.tsx
0.00% <0.00%> (ø)

...ril/client/src/components/ui/User/User.stories.tsx
0.00% <ø> (ø)

<EMAIL_ADDRESS>76.74% <100.00%> (-0.53%)
:arrow_down: