Documentation error: Add "{normal:" to scatter label

On this page https://ecomfe.github.io/echarts-doc/public/en/option.html#series-scatter.label you don't mention the property normal in the label. And it doesn't work in version 4 of Echarts if you try to use it.
Instead this example of yours, https://ecomfe.github.io/echarts-examples/public/editor.html?c=bar-label-rotation, correctly shows on line 71 that you need to include a subproperty called normal. Then my chart shows labels.

One-line summary [问题简述]
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:
Browser version [浏览器类型和版本]:
OS Version [操作系统类型和版本]:

Expected behaviour [期望结果]
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息]

normal can be ignored since ECharts 4.0, but it also works if there is normal to compat ECharts 3. Here's an example, fontSize works with or without normal.
option = {
    xAxis: {},
    yAxis: {},
    series: [{
        symbolSize: 20,
        data: [
            [10.0, 8.04],
            [8.0, 6.95]
        ],
        type: 'scatter',
        label: {
            show: true,
            fontSize: 30
        }
    }]
};


APPS-970 Add restore job statistics

PR is getting pretty big, so I decided to stop here. There are also changes in ecosystem project.
Left todo:

add more fields to status
add more tests

PR is getting pretty big, so I decided to stop here. There are also changes in ecosystem project.
Left todo:

add more fields to status
add more tests

Codecov Report
Attention: 42 lines in your changes are missing coverage. Please review.

Comparison is base (2dcad6b) 20.45% compared to head (0508282) 24.77%.

Files
Patch %
Lines

pkg/service/restore_memory.go
51.92%
18 Missing and 7 partials :warning:

pkg/model/restore_result.go
0.00%
6 Missing :warning:

pkg/service/jobs_holder.go
76.92%
6 Missing :warning:

pkg/model/config.go
0.00%
5 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #107      +/-   ##
==========================================
+ Coverage   20.45%   24.77%   +4.32%
==========================================
  Files          28       29       +1
  Lines        1325     1356      +31
==========================================
+ Hits          271      336      +65
+ Misses       1023      977      -46
- Partials       31       43      +12

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


Soft wrap should be turned on when Zen is activated

As @samglover mentions in #11, it's jarring when Zen is turned on before soft wrap.  Zen mode should turn on soft wrap if possible when toggled.

Could this be made an option? I just looked this issue up because I would prefer not having soft wrap enabled by default when turning on Zen.


Queue Class not recognisable

So I am working on an assignment in F# for a class, and I came across this issue. When I tried running the program through the interpreter and through a .fsx file before I upgraded to 2.23.5, this message would pop up, but running it through fsharpi in the terminal worked...

After upgrading to 2.23.5, the error message saying that Queue was undefined disappeared and the program ran, but the Queue class had this red line underneath with the following message...

I'm going to try to take a crack at this once #380 is resolved.

Can confirm the reproduction of this error on Fedora 25, ionide 2.35.5, vsc version 1.9.1

.fs files should have .fsproj file to which they belong. For standalone files use .fsx files.

This works in both Community and on the command-line. Are we sure that this is intended behavior?
Maybe leave it open but mark it as up for grabs?

If anything, this is probably "issue" (i'm not even sure if it's issue) in FsharpCompilerService.

I'm going to work on this today, will report back iff I make any progress.

Does version 2.25.4+ resolve this?

No idea, the workaround I've proposed is still valid. Renaming file to .fsx should be enough.

Should be fixed in 2.25.7


Error: The getter 'spot' was called on null

Getting the below error every time the charts are drawn.
I/flutter (18757): ══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
I/flutter (18757): The following NoSuchMethodError was thrown during paint():
I/flutter (18757): The getter 'spot' was called on null.

Also, below is the code which I am using to draw the chart.
FlChart(
  chart: BarChart(
    BarChartData(
      barGroups: barChartGroupsData,
      titlesData: FlTitlesData(
        bottomTitles: SideTitles(
          showTitles: false,
        ),
        leftTitles: SideTitles(
          margin: 0.0,
          showTitles: false,
          getTitles: (tileIndex) {
            return tileIndex.toInt().toString();
          }
        )
      ),
      alignment: BarChartAlignment.spaceEvenly,
      backgroundColor: AppColors.white,
      borderData: FlBorderData(
        show: false
      ),
      gridData: FlGridData(
        drawHorizontalGrid: true,
      ),
      barTouchData: BarTouchData(
        enabled: false,
        touchTooltipData: TouchTooltipData(),
        allowTouchBarBackDraw: false,
      )
    ),
  ),
),

Any idea as to why this might be occuring? Thanks in advance for your help.
Also, many thanks for creating this awesome package!

touchTooltipData is the reason.
touchTooltipData: TouchTooltipData(
                          tooltipBgColor: Colors.blueGrey,
                          getTooltipItems: (touchedSpots) {
                            return touchedSpots.map((touchedSpot) {
                              if (touchedSpot?.spot == null) { return null; }  // ***** this is the key code
                              return TooltipItem('***' + '\n' + touchedSpot.spot.y.toString(), TextStyle(color: Colors.yellow));
                            }).toList();
                          }
                        )

fixed in 0.2.0, the problem is that you forgot to set x in BarChartGroupData, now it is required


Pleaase keep this project updated

Pleaase keep this project updated. I love the work you've done by keeping this project updated.

1 week before Vanguard global release unlikely they update it again

They can't continue with the project for Anti-cheat Riot Vanguard.


Port support for computing model bounding box in physics system

Porting changes from this bitbucket PR that was merged into ign-gazebo2:
https://osrf-migration.github.io/ignition-gh-pages/#!/ignitionrobotics/ign-gazebo/pull-requests/546/page/1
see original changes in this commit: 4cdef0c1ea957439b6d87ebdf3650f3d4b967827
Signed-off-by: Ian Chen<EMAIL_ADDRESS>

Is an ign-physics release needed to fix the builds?

Is an ign-physics release needed to fix the builds?


howdy does not work in Fedora 30

Please describe the issue in as much detail as possible, including any errors and traces
The installation works fine. After I set device_path=/dev/video0 it allows me to do "howdy add"
however, it is not activated when I try to login.
Linux distribution (if applicable):
Fedora Workstation 30
Howdy version:
 rpm -q howdy
howdy-2.5.1-2.fc30.x86_64
Fedora 30 Cinnamon desktop.
I suspect the issue is related to pam config.

can confirm this issue.

Can confirm this is an issue for me as well. Program seems to install correctly. No errors displayed. Can successfully run 'sudo howdy test', but program does not seem to be registering active for the login screen and the terminal prompt.

did anyone get a workaround?

Not so far. Was seeing if @boltgolt might have an idea when he had the chance. Wasnt in a huge rush :)

Same for Fedora29 (i did not upgraded yet). Test works but no camera/IR gets activated (no red squeres in IR emmiters) during sudo nor logon.
Thank you in advance for fixing this!
Alex

Can confirm.
Fedora 30
Dell XPS 9370
"sudo howdy test" works on X11 but I get the following:
[ INFO:0] VIDEOIO: Enabled backends(7, sorted by priority): GSTREAMER(1000); V4L2(990); OPENNI(980); CV_IMAGES(970); CV_MJPEG(960); FIREWIRE(950); UNICAP(940)
OpenCV | GStreamer warning: GStreamer: unable to start pipeline
(/builddir/build/BUILD/opencv-3.4.4/modules/videoio/src/cap_gstreamer.cpp:872)
(python3:7282): GStreamer-CRITICAL **: 21:30:52.997: gst_element_get_state: assertion 'GST_IS_ELEMENT (element)' failed
OpenCV | GStreamer warning: GStreamer: unable to query pipeline state (/builddir/build/BUILD/opencv-3.4.4/modules/videoio/src/cap_gstreamer.cpp:420)
Had to add "/dev/video2" to the config.ini file to get "howdy test" working.  I also tried adding "auth sufficient pam_python.so /lib64/security/howdy/pam.py" to the files in /etc/pam.d  but that didn't work.

Can confirm.

Fedora 30
Gnome 3.32
HP Elitebook 735G5

Additional information.
No protocol specified
qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Does KDE work properly?

Same here
Output of
sudo howdy test
[ INFO:0] VIDEOIO: Enabled backends(7, sorted by priority): GSTREAMER(1000); V4L2(990); OPENNI(980); CV_IMAGES(970); CV_MJPEG(960); FIREWIRE(950); UNICAP(940)
OpenCV | GStreamer warning: GStreamer: unable to start pipeline
 (/builddir/build/BUILD/opencv-3.4.4/modules/videoio/src/cap_gstreamer.cpp:872)

(python3:4469): GStreamer-CRITICAL **: 22:28:12.366: gst_element_get_state: assertion 'GST_IS_ELEMENT (element)' failed
OpenCV | GStreamer warning: GStreamer: unable to query pipeline state (/builddir/build/BUILD/opencv-3.4.4/modules/videoio/src/cap_gstreamer.cpp:420)

Opening a window with a test feed

Press ctrl+C in this terminal to quit
Click on the image to enable or disable slow mode

No protocol specified
qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Aborted

This part

No protocol specified
qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Sounds like you're running Wayland when Howdy (or one of its dependencies) expects you to be using X11. When you log in (for the first time after boot) click on the gear next to the login button and select the option that contains Xorg or X11. Do you still get the same error?
Fedora 30 (I think) started defaulting to running GNOME on Wayland instead of X11, so it would make sense for this to be the reason for the breakage.

Cant speak for him, but I know that all testing and attempts to get Howdy to work in Fedora 30 for me was all on X11 and I still ran into issues.

I got it to work for sudo -i by manually adding it to the /etc/pam.d/system-auth file and installing pam_python.so (which can be found in the RPM Sphere repository).
This situation is not ideal at all as pam-python still requires python 2, which basically no distro likes to maintain at this point (due to it going EoL very soon)
Here is my pam.d file that I referred to (so you see where it must be inserted)
doridian@fennec ~]$ cat /etc/pam.d/system-auth
#pam.d Generated by authselect on Thu Oct 10 17:51:17 2019
# Do not modify this file manually.

auth        required                                     pam_env.so
auth        required                                     pam_faildelay.so delay=2000000
auth        sufficient                                   pam_fprintd.so
auth        sufficient                                   pam_python.so /lib64/security/howdy/pam.py
auth        [default=1 ignore=ignore success=ok]         pam_succeed_if.so uid >= 1000 quiet
....

Its working under Wayland, Fedora 31 beta, Gnome 3.34 and PAM set as Doridian said (only terminal root access).
The only thing I had to find which source camera is so in my case is /dev/video0 and I had to install older rpm from fedora30 pam_python as 31 is still in testing phase.
but nevertheless everything works fine.

So in theory,
If us gents who are on 30 wait until the official 31 release and then install from the appropriate repo, the issue should be resolved?
Thanks,
-----Original Message-----
From: Vladimir Travalja <notifications@github.commailto:Vladimir Travalja<EMAIL_ADDRESS>Reply-To: boltgolt/howdy <reply@reply.github.commailto:boltgolt/howdy<EMAIL_ADDRESS>To: boltgolt/howdy <howdy@noreply.github.commailto:boltgolt/howdy<EMAIL_ADDRESS>Cc: Dillon Wood <dillon.wood@outlook.commailto:Dillon Wood<EMAIL_ADDRESS>Comment <comment@noreply.github.commailto:Comment<EMAIL_ADDRESS>Subject: Re: [boltgolt/howdy] howdy does not work in Fedora 30 (#233)
Date: Fri, 11 Oct 2019 00:57:59 -0700
Its working under Wayland, Fedora 31 beta, Gnome 3.34 and PAM set as Doridian said (only terminal root access).
The only thing I had to find which source camera is so in my case is /dev/video0 and I had to install older rpm from fedora30 pam_python as 31 is still in testing phase.
but nevertheless everything works fine.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fboltgolt%2Fhowdy%2Fissues%2F233%3Femail_source%3Dnotifications%26email_token%3DADVEP4OO3H2WYAHCLBVASRDQOAWYPA5CNFSM4IDLM7B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA7F5TY%23issuecomment-540958415&data=02|01||7b5cae3fa04d4ab9cb3e08d74e20bc35|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637063774807729449&sdata=fEgua46BsApo4D4tZdLfjeaeCHCgCEh8ma7rNmEQdck%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADVEP4LNW5GR5QPIALOP6ZLQOAWYPANCNFSM4IDLM7BQ&data=02|01||7b5cae3fa04d4ab9cb3e08d74e20bc35|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637063774807739460&sdata=AFRKbnCX20%2F6bO6MGKnAynCEgxIxheyVMBq0BBpBjIQ%3D&reserved=0.

As I mentioned above, it works on f31, Wayland, kernel 5.4-rc2, with pam_python binary for fc30, only if you set it correctly.

One problem found. When you try to open an application such as "timeshift" which initially requires a password to be executed, video login does not work, in fact it looks like howdy calls camera to take a photo, but ends in a loop, as my camera constantly flickers and trying to get picture (possibly some issue with PAM, but again no output so I cannot tell). Not sure what is the cause of that, but apparently GUI password inquiry and Howdy does not work properly. Again, opening application such as Timeshift executes password inquiry and it gives directive to howdy to execute camera function, but ends in loop and application "timeshift"  is never starts...

Not working on Fedora 31. Similarly, sudo howdy test works with the following output:
[ INFO:0] VIDEOIO: Enabled backends(7, sorted by priority): GSTREAMER(1000); V4L2(990); OPENNI(980); CV_IMAGES(970); CV_MJPEG(960); FIREWIRE(950); UNICAP(940)
OpenCV | GStreamer warning: GStreamer: unable to start pipeline
 (/builddir/build/BUILD/opencv-3.4.6/modules/videoio/src/cap_gstreamer.cpp:872)

(python3:12491): GStreamer-CRITICAL **: 14:29:47.448: gst_element_get_state: assertion 'GST_IS_ELEMENT (element)' failed
OpenCV | GStreamer warning: GStreamer: unable to query pipeline state (/builddir/build/BUILD/opencv-3.4.6/modules/videoio/src/cap_gstreamer.cpp:420)

Opening a window with a test feed

Fedora 31
Gnome 3.34.1
Lenovo Thinkpad T590

It works with me on Fedora 31 & Wayland with solution from @Doridian , Thanks a lot.

Fedora 31
GNOME 3.34.1
Lenovo Thinkpad T590

Steps:

Before that:
-- Install howdy according to the instruction.
-- Run sudo howdy config and set device_path to the camera path of your device, e.g., device_path = /dev/video0 (You may need to install nano editor if you got FileNotFoundError, see #290 )

Install RPM Sphere repository
Follow  https://rpmsphere.github.io/

Install pam_python (not python_pam) by the following command:
sudo yum install pam_python

Manually edit /etc/pam.d/system-auth file and make it like this:

user@localhost ~]$ sudo vi /etc/pam.d/system-auth

#pam.d Generated by authselect on Thu Oct 10 17:51:17 2019
# Do not modify this file manually.

auth        required                                     pam_env.so
auth        required                                     pam_faildelay.so delay=2000000
auth        sufficient                                   pam_fprintd.so
auth        sufficient                                   pam_python.so /lib64/security/howdy/pam.py
auth        [default=1 ignore=ignore success=ok]         pam_succeed_if.so uid >= 1000 quiet
....

Where auth        sufficient                                   pam_python.so /lib64/security/howdy/pam.py is a newly inserted line to the file.

Run sudo howdy test  and sudo -i to check whether it works.

for the howdy to work you need to edit some of your pam.d configuration files if they are not edited by the installer.
Basically you will want to edit the /etc/pam.d/sudo and add the following line:
auth sufficient pam_python.so /lib/security/howdy/pam.py
at the beginning so that authentication system first try a facial recognition and if that works it will grant you privilege if not it will start other methods of authenticating namely password in most cases.
You can follow the archwiki https://wiki.archlinux.org/index.php/Howdy on how to setup.
Also if you are using for example GDM or LightDM you would want to edit their configuration files inside  /etc/pam.d/ and add the same line.
Yeah its manual setup but at least you control where you want to add and where you don't want to add.

For Fedora, please consider testing the repo at:
https://copr.fedorainfracloud.org/coprs/luya/howdy/

Followed all the steps (add pam_python, chmod +x howdy dir, set the device_path, install nano) and still getting the same error on test.
Fedora 31
[ INFO:0] VIDEOIO: Enabled backends(6, sorted by priority): GSTREAMER(1000); V4L2(990); OPENNI(980); CV_IMAGES(970); CV_MJPEG(960); FIREWIRE(950)
[ WARN:0] OpenCV | GStreamer warning: Embedded video playback halted; module source reported: Could not read from resource.
[ WARN:0] OpenCV | GStreamer warning: unable to start pipeline
[ WARN:0] OpenCV | GStreamer warning: GStreamer: pipeline have not been created

Opening a window with a test feed

Press ctrl+C in this terminal to quit
Click on the image to enable or disable slow mode

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'

@thoroc that error is related to #318 you can ignore it if everything works.
@EfraimLA Are you using sddm for logging in?
The issue for me was related to selinux.
my config:
$ cat /etc/pam.d/sddm
auth     [success=done ignore=ignore default=bad] pam_selinux_permit.so
auth       sufficient   pam_python.so /lib64/security/howdy/pam.py
...

To fix the issue:
ausearch -c 'python3' --raw | audit2allow -M my-python3
semodule -i my-python3.pp

Fedora 30 is end of life.
<EMAIL_ADDRESS>Is this issue still relevant to newer versions?

I am still on Fedora 31 (32 is already out) and the issue persist

Have same (or similar) issue on fedora 34. howdy add and howdy test works fine. Updated the etc/pam.d/sudo file but I just get password prompt when I do sudo -i

Same here
Output of
sudo howdy test
[ INFO:0] VIDEOIO: Enabled backends(7, sorted by priority): GSTREAMER(1000); V4L2(990); OPENNI(980); CV_IMAGES(970); CV_MJPEG(960); FIREWIRE(950); UNICAP(940)
OpenCV | GStreamer warning: GStreamer: unable to start pipeline
 (/builddir/build/BUILD/opencv-3.4.4/modules/videoio/src/cap_gstreamer.cpp:872)

(python3:4469): GStreamer-CRITICAL **: 22:28:12.366: gst_element_get_state: assertion 'GST_IS_ELEMENT (element)' failed
OpenCV | GStreamer warning: GStreamer: unable to query pipeline state (/builddir/build/BUILD/opencv-3.4.4/modules/videoio/src/cap_gstreamer.cpp:420)

Opening a window with a test feed

Press ctrl+C in this terminal to quit
Click on the image to enable or disable slow mode

No protocol specified
qt.qpa.xcb: could not connect to display :0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

Aborted

I'm having the same issue here. Howdy works perfectly fine on Arch Linux with Sway installed other that running sudo howdy test crashes due to the errors written in this comment.

@KoalaV2 you should open a new issue with more information, because that has nothing to do with the OP's issue.
This issue should actually be closed.

I am using Fedora Plasma 34 (which is the KDE version of fedora). After doing what @Doridian prompt to make sudo work, I also managed to make login authentication work by adding the same line into password-auth below the first two "required" line.


(FFM-6483) Wider linux kernel support

Issue
When running an ubuntu 20.04 image on a centos7 machine with linux kernel 3.10 we run into this fairly common linux kernel issue of error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory. This comes when launching our pushpin dependency.
This errors on kernel versions 3.10 because that kernel is incompatible with libQt5Core.so.5 which is only compatible with kernels 3.17 and above. These .note.ABI tags trigger compatibility checks by the linker when loaded. Stripping this tag out only disables the check by the dynamic linker for the kernel version to be at least as high and has no other effects. See this discussion and the many pr's that reference it. This and a multitude of forums/articles/github issues all had this same suggested workaround to remove these tags and prevent the kernel refusing to start over incompatibilities in parts of OS libraries we don't need or use.
Other changes
Also bumped our pushpin version and we now pull the focal version instead of the bionic one to be consistent, though both work fine.
Note
The only thing I'm unclear on and investigating is why this is an issue with ubuntu:20.04 but wasn't with ubuntu:18.04 for us, it's more for curiosity because the proposed solution I have here seems to be the standard workaround on every repo I've seen encounter it. It appears the answer is that some of these OS level dependencies changed between these ubuntu OS versions and that's why it's now being pulled into the dynamic linker when running on ubuntu:20.04 when it wasn't on ubuntu:18.04 and triggering this issue.
Testing
Tested that this new image runs successfully on centos7 machines with a linux 3.10 kernel as well as on regular aws linux2 AMI

Tested using the official aws marketplace centos7 ami which runs Linux kernel 3.10.0-1160.76.1.el7.x86_64 and now functions correctly.
Also sanity tested using Amazon Linux 2 OS on kernel 5.10 and and ECS fargate instance to verify no regressions in addition to our regular e2e test suite.


WIP: Improve the efficiency of cupyx.scipy.ndimage.convolve (and correlate)

This PR rewrites the n-dimensional convolution kernel to make it more efficient. This is especially true when the filter itself only has a small number of non-zero entries.
Prior to this PR, in n dimensions, the kernel consisted of n nested for loops that looped over the filter kernel.
In this PR, the change is that the filter kernel is first converted to a 1d array containing the non-zero coefficients and a second array containing the coordinates of these coefficients. This allows replacing the n nested for loops by a single loop that only traverses the non-zero coefficients.
In my initial testing this seems to give a substantial performance benefit, even in the case when the filter does not have any non-zero entries. Here is a basic benchmark:
import cupy
from cupyx.scipy.ndimage import convolve

d = cupy.cuda.Device()
x = cupy.random.randn(256, 256, 256);

# densely populated filter
w = cupy.ones((5, 5, 5))
w /= w.size
%timeit convolve(x, w); d.synchronize()

# sparsely populated filter
w2 = cupy.zeros((5, 5, 5))
w2[0, 0, 0] = 0.5
w2[-1, -1, -1] = -0.5
%timeit convolve(x, w2); d.synchronize()

Prior to this PR the times for these dense and sparsely populated filters are equivalent. I measure:
201 ms ± 7.45 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
After this PR, I get the following for the densely populated case:
127 ms ± 283 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)
and for the sparsely populated case:
3.71 ms ± 69.6 µs per loop (mean ± std. dev. of 7 runs, 100 loops each)

I can refactor slightly to pass wshape and the number of nonzero entries instead of the array w to _generate_correlete_kernel. That should allow restoring the caching of kernels.

Why does this PR improve the performance of the densely populated inputs?

Prior to this PR the times for these dense and sparsely populated filters are equivalent. I measure:
201 ms ± 7.45 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

Some values are cached internally after the first function call. Please measure the time by repeating 10 times also in this case.

I locally compared the performance in the densely populated case.
import cupy
from cupyx.scipy.ndimage import convolve
from cupyx.time import repeat

d = cupy.cuda.Device()
x = cupy.random.randn(256, 256, 256);
w = cupy.random.randn(5, 5, 5)

perf = repeat(convolve, (x, w), n=50, n_warmup=10)
print(perf)

master(40b59e44d):
convolve            :    59.998 us   +/-54.305 (min:   46.976 / max:  339.244) us  72760.652 us   +/-79.005 (min:72704.094 / max:73062.813) us

This PR (bca5bba25):
convolve            :   359.820 us   +/-55.769 (min:  344.258 / max:  743.166) us  75956.443 us   +/-93.009 (min:75915.840 / max:76360.062) us

I cannot do it immediately, but will take a look again at performance later today or tomorrow. I did not necessarily expect it to be faster for the densely populated case (but would also not expect it to be much slower).
It would also be possible to keep the current implementation and call it instead of the newly proposed one when all (or most) entries of the filter are non-zero.

Okay, I reran with that repeat utility and also see a similar result to @asi1024. I think the CPU time being higher is to be expected due to the extra handling of weights to get the coordinates and values, but it looks like the GPU time is also slightly higher (212 vs 196 ms).
master(40b59e4):
convolve            :   234.678 us   +/-74.324 (min:  105.436 / max:  376.489) us  196379.369 us   +/-875.660 (min:194806.778 / max:197748.734) us

This PR (bca5bba):
convolve            :   759.932 us   +/-67.219 (min:  699.047 / max: 1095.894) us  213619.128 us   +/-916.371 (min:212165.634 / max:215121.918) us

Given that there is some loss of performance for the fully dense case, I no longer want to merge this as-is. So I guess there are three main options:
1.) close the PR as is
2.) retain both kernel generation functions and select between the two either in an automated fashion (probably hard to do at least some minimal overhead) or via a new kwarg.
3.) improve the proposed solution so it is also faster in the dense case (not sure this is possible)
I am interested in how best to implement kernels that use a support mask of this type as that is a common pattern for a number of other functions in scipy.ndimage which use a structure or footprint argument. All of the morphological operations do this for example, so I don't think it is wasted effort even if we do not choose to use it here.
Have any of you worked on or have plans to work on these other types of image operations (e.g. binary erosion, minimum_filter, etc.)?

I opened a separate PR with a simpler approach that I initially tried prior to this one: #2846.

I feel it's a waste to just throw away this optimization, because it's siginificant in almost-zero case.
As an option for (3), how about doing this optimization only if weights is a sparse matrix?
That wouldn't work in scipy.ndimage, but I think it's at least better than introducing a new argument in (2).

Is this PR still needed @grlee77? Wasn't sure based on your earlier comment and the fact PR ( https://github.com/cupy/cupy/pull/2846 ) was merged.

Is this PR still needed @grlee77? Wasn't sure based on your earlier comment and the fact PR ( #2846 ) was merged.

I will go ahead and close it given that some of the benefit was obtained by the simpler change in #2846.  This implementation can have some benefit for filters that are mostly zeros, but I think that is a pretty niche case, and perhaps not worth maintaining a separate code path here.


Fix AnsiCastOpSuite failures with Spark 3.2

This PR updates an assertion in AnsiCastOpSuite and fixes all 21 test failures when running against Spark 3.2
This partially addresses https://github.com/NVIDIA/spark-rapids/issues/3376

build

I am looking into the test failures

build

build

This PR does not build on Databricks. I will have a fix up later today.

I pushed a fix and this now builds on Databricks 7.3

build

build


OnStarting cannot be set because the response has already started

Description
When creating a response within the body of the function using the following:
            this.logger.LogError(responseMessage.ToString());
            var badRequestResponse = request.CreateResponse(HttpStatusCode.BadRequest);
            await badRequestResponse.WriteStringAsync(responseMessage.ToString());
            return badRequestResponse;

I'm getting the error "OnStarting cannot be set because the response has already started". It took me hours to resolve this issue as I thought it was an issue with our code but as it happens, I updated to the latest version (1.3.0) of "Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore" and the minute I went back to version 1.2.1, the problem got resolved.
Steps to reproduce

Create a .net azure function project using .NET 8 and make sure it is set to use isolated process.

Add the following packages:
 <PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="2.22.0" />
 <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.22.0" />
 <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.2.0" />
 <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore" Version="1.3.0" />
 <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.17.2" />
 <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk.Analyzers" Version="1.2.1" />
 <PackageReference Include="Microsoft.Extensions.Logging" Version="8.0.0" />

and make sure that it is using 1.3.0 for "Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore"

Change the function to return an HttpResponseData and use the HttpRequestData and return a basic response as follows:
         this.logger.LogError(responseMessage.ToString());
         var badRequestResponse = request.CreateResponse(HttpStatusCode.BadRequest);
         await badRequestResponse.WriteStringAsync(responseMessage.ToString());
         return badRequestResponse;

I think this should be fixed in 1.3.1 but feel free to reopen this and we can investigate further, thanks!


Delete the CHANGELOG.md

Summary
Delete this file.
Motivation
This file in 2 release out of date. We're clearly not updating it. It's costly and with little benefit.
Proposal
Delete the file.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@jessesuen @sarabala1979 thoughts?

Why not add to the top something like: This file is deprecated and no longer supported. For latest release information please see our [releases page](https://github.com/argoproj/argo/releases)?


Coindesk API provides inaccurate fiat conversions rates

While using wallet i came across strange currency conversion. The coindesk api reports vastly different prices from other providers or even from their own web version.
https://api.coindesk.com/v1/bpi/currentprice/CZK.json
https://www.coindesk.com/price/bitcoin/
the problem seems to affect all non USD currencies.
The behavior can be huge missmatch for EUR
https://api.coindesk.com/v1/bpi/currentprice/EUR.json
given the recent EUR drop in price against USD. As of writing(19 169 USD) API price:  18 673 EUR   vs "real price":  19 720 EUR.

Are you using Phoenix on Android or on iOS?
FYI, on both the Android app and the iOS app, the EUR/BTC and USD/BTC tickers come from the blockchain.info API, so we do not use Coindesk there, and the rates are accurate (right now the rate in the app is 1 btc = 19 974 EUR, which is correct).
Coindesk is used for the currencies other than USD/EUR, and that's where there can be discrepancies. We're aware of that and we have plans to fix that in the future.

I've seen the EUR only in the API and didn't check phoenix itself, sorry for this misinformation. I'm using the app on Android. I'm glad you are aware of the issue for other currencies. It seems to me that coindesk is using some old exchange rates between USD and other currencies which is causing this behavior.

Notes:

We've had reports of inaccurate SEK, Swedish crowns (ticket 47508568)
We don't currently support CNH, but we would like to

Exchange rate for COP is very inaccurate recently. For example, today:

coindesk: 1 USD = 4,219 COP
everybody else: 1 USD = 4,757 COP

The raw JSON from the coindesk feed contains this disclaimer:

"This data was produced from the CoinDesk Bitcoin Price Index (USD). Non-USD currency data converted using hourly conversion rate from openexchangerates.org"

However, if I pull directly from the source, I get very different exchange rates:

direct from CoinDesk API: 1 USD = 4,218.99 COP
direct from OpenExchangerRtes API: 1 USD = 4,765.08 COP

So the OpenExchangeRates API has an accurate value, while CoinDesk does not. So if CoinDesk is indeed pulling from this source, then they're doing so poorly (either infrequently, of their update job is crashing).

Fixed via PR #331
It will be available in the next (major) app release: v1.6.0


'Speed' measurement possibly misleading for image classification

If I am correct in assuming that the time calculated for evaluating the whole dataset (https://github.com/paperswithcode/torchbench/blob/master/torchbench/image_classification/utils.py#L75) is used for calculating the speed on the leaderboard, then I would like to point out several issues with this

The disk read time gets included in the measurement, and models that are fast enough that the disk speed cannot keep up would report an unfairly low speed.
If consistent disk speeds are not ensured between runs (because some other process happened to be accessing the same disk), then it further compounds (1) above, and the evaluated speed would not be the same between runs.

I believe that the speed measurement should be done on a chunk of preloaded dummy data, with a note on the leaderboard saying that the actual speeds people can get in practice would depend on the rate at which the model can be fed.

In my opinion this is a serious enough bug (if I am correct in my assumptions) to warrant putting a note on the leaderboard saying that the speed values should not be trusted until this is resolved.
I only checked for image classification, but perhaps such an issue exists for other tasks too.

and to add one more point to this: The intention of the 'speed' column is to indicate the intended throughput, but even when measured by factoring out the disk read speeds, throughput has a non trivial dependence on batch size.

Thank you for, as always, very thorough and thoughtful comments Dushyant!
To address your individual points:

You are absolutely correct that reading the image from the disk is included in the measurement. This is indeed problematic for very fast models and introduces an upper limit to the max speed. However, looking at the graph at https://sotabench.com/benchmarks/image-classification-on-imagenet it looks like this doesn't affect the models we have benchmarked right now. If we would be hitting the "ceiling" in speed many models would form a near-perfect vertical line on that graph, which we don't observe. Therefore, although speed is data loading+inference, we still feel it's useful at least for relative ranking of methods. I would welcome a PR to solve this problem for future super-fast models as well though!
Consistency of disk speed between runs. On sotabench.com we run the benchmark on a dedicated, freshly spun-up, isolated machine so in our experience in that setting there isn't really much variation. E.g. running a box-standard ResNeXt-101-32x8d model 3 times yields following speeds: (288.4, 286.0, 288.2). So although there is some variability, it seems to be only around 1-2%. Given that the range of speeds we are seeing is 6 to 500, we didn't feel this is significant enough. Furthermore, I feel that the size of the green dot in that graph probably captures a rough estimate of this variability.
Batch size. You are absolutely correct - changing the batch size will drastically change the speed. And indeed, some of the "small" models get their improvements by enabling larger batch sizes and we assume authors have optimized the batch size to make max usage of GPU memory. Alternatively, one could just send a single image at the time, which will make the benchmarks run longer but remove the effect of the batch. However, as many people do use these methods in batches it's not clear to me which one is better.

To add a few more caveats here:

We are testing everything on a specific machine, with a specific GPU and GPU memory size. It's possible that on a different GPU type you would get different results.
I say we assume that the batch size has been optimized by the author, but that's sometimes not the case and we don't have a way of checking if they've done this or not.
For repositories that test multiple models it's unclear how order influences the performance because some of the disk content might get cached differently after being repeatedly accessed. Same might hold for GPU cache as well.
The same model might be implemented in various frameworks, in various versions of those frameworks and with various subtle differences. Each of these might make a difference, so one needs to be careful about generalizing the results to "models" as abstract entities and instead only talk about using a model implemented in a specific way, in a specific environment, under a specific use case - in our case in batch-reading imagenet from the disk, on a specific hardware and a specific set of dependencies.

Hi Robert
Thanks for the detailed response.
I can work on a patch to also report the loading + inference breakdown, and perhaps code to try different batch sizes and report the maximum speed obtained.
Also, it may be helpful to list the caveats you mention here, on the website as well, along with information of what GPU the inference would run on.
Best,


HMR broken with @vanilla-extract/vite-plugin v4.0.1 and later

Describe the bug
After upgrading from v3.9.5 to v4.0.3 HMR broke in our setup. Seem like v4.0.0 actually works alright and it broke in v4.0.1. Downgrading to v4.0.0 fixes the problem.
Reproduction
https://github.com/jakst/vanilla-extract-hmr

Clone repo
run pnpm install
Start dev server
edit src/styles.css.ts
Observe HMR not functioning, and page fully reloading
Downgrade @vanilla-extract/vite-plugin to v4.0.0 (pnpm add -E<EMAIL_ADDRESS>Repeat steps 3 and 4
Observe HMR working properly

System Info
System:
  OS: macOS 14.2
  CPU: (12) arm64 Apple M3 Pro
  Memory: 822.20 MB / 36.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 20.10.0 - ~/.proto/shims/node
  Yarn: 4.0.2 - ~/.proto/shims/yarn
  npm: 10.2.3 - ~/.proto/shims/npm
  pnpm: 8.15.1 - ~/.proto/shims/pnpm
  bun: 1.0.25 - ~/.proto/shims/bun
  Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Browsers:
  Brave Browser: <IP_ADDRESS>
  Chrome: 121.0.6167.139
  Edge: 121.0.2277.98
  Safari: 17.2
npmPackages:
  @vanilla-extract/css: 1.14.1 => 1.14.1
  @vanilla-extract/recipes: 0.5.1 => 0.5.1
  @vanilla-extract/vite-plugin: 4.0.3 => 4.0.3
  vite: 5.0.12 => 5.0.12

Used Package Manager
pnpm
Logs
No response
Validations

[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hey @mrm007 sure! Seems to work fine so far, but I'll keep that version for a while and report back if anything breaks.

Can you share the list of Vite plugins you're currently using?

I see the same issue. The snapshot also fixes it for me.
plugins: [react(), vanillaExtractPlugin({})],

    "@vitejs/plugin-react-swc": "^3.6.0",
    "vite": "^5.0.11"
+ vanilla-extract

import { sentryVitePlugin } from '@sentry/vite-plugin'
import { TanStackRouterVite } from '@tanstack/router-vite-plugin'
import { vanillaExtractPlugin } from '@vanilla-extract/vite-plugin'
import react from '@vitejs/plugin-react-swc'
import Unfonts from 'unplugin-fonts/vite'
import { defineConfig } from 'vite'
import relay from 'vite-plugin-relay'
import tsconfigPaths from 'vite-tsconfig-paths'

// https://vitejs.dev/config/
export default defineConfig({
  build: {
    sourcemap: true,
  },
  plugins: [
    tsconfigPaths(),
    vanillaExtractPlugin(),
    react(),
    relay,
    TanStackRouterVite(),
    Unfonts({ }),
    sentryVitePlugin({ }),
  ],
})

Thanks gents, that's very promising. We'll release the fix soon.


[Monitoring V2] root_url issues for non-local clusters

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a NON-local cluster
On the non-local cluster install monitoring with this addition to the configuration

grafana:
   grafana.ini:
      server:
         root_url: https://floof.com/floofy

Result:
The base url of the grafana dashboard isn't changing which prevents me from loading grafana dashboards within the rancher dashboard because I either load the iframe with the original url and can't inject our assets or I load the iframe with localhost and subsequent resources and scripts fail to load due to cors.

Other details that may be helpful:
This is only happening for non-local clusters. When defining root_url for local we can see the base url change.

I've also attempted to use the domain and subpath properties without luck.
grafana:
   grafana.ini:
      server:
         root_url: https://floof.com/floofy
         domain: floof.com
         serve_from_sub_path: true

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):  v2.5-b2a34d7cef440e3ed1de7d506233aa3a332649ae-head
Installation option (single install/HA): single install

@sowmyav27 Can we test if this was a regression from 2.5.6 or 2.5.7 with the monitoring chart today? The fact that this is only affecting local clusters makes me think that this is related to the changes we made to rancher/rancher for the downstream cluster proxies

I tested this on 2.5.5 (monitoring version 9.4.202 and 9.4.200) and the issue reproduces using the downstream (non-local) cluster.  I added the following to the monitoring yaml

Blocks https://github.com/rancher/dashboard/issues/812 in a non-local cluster

@aiyengar2 - is this related to https://zube.io/rancher/rancher/c/37339

Hmm I'm not sure @SheilaghM . @codyrancher do you remember if the Zube issue (https://github.com/rancher/rancher/issues/31732) was in a downstream cluster as well?
It would make sense to me that both might be related.

It wasn't a downstream cluster. If it were downstream I wouldn't be able to set the root_url to resolve it.
However, I did just test this in both a local and downstream cluster. It looks like I'm able to sign in even though the root_url isn't set. So this appears to be resolved unless @aiyengar2 expects the the root_url to be set.

I don't think root_url needs to be set, afaik.
Also, @codyrancher you mean https://github.com/rancher/rancher/issues/31732 is resolved, not this issue right?

@codyrancher and I hopped on a call about this offline and decided that it was okay to push this back to 2.6 instead of 2.5.8.
cc: @SheilaghM @gaktive @Jono-SUSE-Rancher @sowmyav27
Scope of Issue
The scope of this issue is something that should only impact the UI development process. Normal users of Rancher will not experience this issue since this is something that arises from the fact that the UI developer is using a local development URL (e.g. http://localhost:8085 that is rendering the rancher/dashboard code pointing to the Rancher deployment) that differs from the Rancher URL.
Note: this is not really a root_url problem but rather an inconsistency that happens when root_url is not set. We do not expect root_url to be set.
Summary of Technical Issue
For the current UI developer working on rancher/dashboard, the overall workflow for local clusters looks something like this (when the root_url is not set):

UI Developer makes a request from the origin http://localhost:8085 to the rancher/rancher backend at RANCHER_URL/k8s/clusters/local/{k8s-api-server-proxy-stuff}/proxy/{actual-grafana-path}
Rancher sees the request coming to /k8s/clusters/local/{k8s-api-server-proxy-stuff}/proxy/{actual-grafana-path} and forwards it to {k8s-api-server-proxy-stuff}/proxy/{actual-grafana-path}
The api-server sees {k8s-api-server-proxy-stuff}/proxy/{actual-grafana-path} and queries the Grafana pod at port 8080 for /{actual-grafana-path}
On return, the base href that is encoded is a relative URL which is just /{actual-grafana-path}

However, in downstream clusters, there is an additional step between 2 and 3 where the /k8s/cluster/{clusterId} part goes through our rancher pod (I believe cluster-agent?) on the management cluster to the corresponding pod on the downstream cluster and for some reason this is causing Grafana to return a base href that is RANCHER_URL/k8s/cluster/{clusterId}/{k8s-api-server-proxy-stuff}/{actual-grafana-path}, even when the root_url is not set.
We tried to do a number of things to debug this issue, including adding a sidecar to the Grafana deployment and tcpdump-ing the incoming requests and looking through the Grafana UI code, but we weren't able to catch anything that was fairly intuitive that was causing this difference to occur.
@ibuildthecloud do you have any idea what issue we might be running into here? I'm not 100% familiar with the Rancher Steve proxying mechanism in rancher/rancher, so perhaps I'm misunderstanding something here on why this workflow is failing.

Also, @SheilaghM @Jono-SUSE-Rancher @gaktive we should prioritize this fairly soon since this does block the ability for UI developers to be able to test things like etcd embedding of cluster overview graphs without spinning up a local RKE cluster for testing, since the normal local k3s cluster does not have etcd monitoring.

Note: There were some issues talking about potentially updating k3s to use etcd which may solve this issue for UI developers, but not positive. Check with broader team when this issue comes up to be picked up.

This is extremely annoying, we ran into this limitation as well  😅
We needed to set the root URL of the non-local clusters, so that we can enable OIDC authentication to Grafana.
server:
  root_url: "https:/mycompany.com/k8s/clusters/${ .ClusterName }/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy"
  serve_from_sub_path: false

As a result, Grafana failed to load, with the following hint in the network tab:
Request URL:
https://mycompany.com/k8s/clusters/CLUSTER_ID/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/k8s/clusters/CLUSTER_ID/api/v1/namespaces/cattle-monitoring-system/services/http:rancher-monitoring-grafana:80/proxy/public/fonts/roboto/xxxxxxxxxxxxx
Request Method:
GET
Status Code:
404 Not Found

For some reason the k8s/clusters/CLUSTER_ID..... part is double-added to the call.
Note, this issue persists whether we set serve_from_sub_path to true or false.


locize and next-i18next

Hi,
I would like to thank you for the work you are doing.
I'm trying to use a localization framework that can automatically download resources from locize. I saw many google results on how to integrate other frameworks but I can't find any helpful resource on how to do it with the new version.
I follow this https://github.com/isaachinman/next-i18next/pull/705/files#diff-bda3f4b5c1b38db2dcde53a9832453e3R1 but I'm not successful.
I would like to ask you if you can provide any resources on how to connect your library to this service. I would like to use "create if missing" feature and I don't want to download resources at build time with the locize-cli.
Kindly, Míla

@adrai Wondering if you have any input? Should be a very straightforward i18next setup at this point.

https://github.com/locize/next-i18next-locize

thank you guys, very much. I'll look.

@adrai your example works correctly. But when I tried to apply to my project I got this error
react-i18next:: You will need to pass in an i18next instance by using initReactI18next

I can't find where is the problem
Any ideas?
Thanks Míla

a reproducible example would help

It looks like the problem is with the Auth0 security. When I remove this implementation it looks like it is working.
i18next::translator: missingKey cs common Profile53čččč Profile53čččč

When I give back the
    <Auth0Provider
      domain={publicRuntimeConfig.AUTH0_DOMAIN}
      clientId={publicRuntimeConfig.AUTH0_CLIEND_ID}
      redirectUri={publicRuntimeConfig.AUTH0_REDIRECT_URI}
    >
      <Component {...pageProps} />
    </Auth0Provider>

and add to page new key then no translator log in console.

@adrai  - confirmed
This index page works
import { useTranslation } from 'next-i18next';
import { serverSideTranslations } from 'next-i18next/serverSideTranslations';
import { withAuthenticationRequired } from '@auth0/auth0-react';

function Profile({ auth0 }) {
  const { t } = useTranslation();

  return (

{t('Profile')}

{t('Profile4')}

{t('new.1')}

This is the profile page.

  );
}

export const getStaticProps = async ({ locale }) => ({
  props: {
    ...(await serverSideTranslations(locale, ['common'])),
  },
});

export default Profile;

and when I change the last row to
export default withAuthenticationRequired(Profile);

it is not working...
I'll investigate further

When I use export default Profile; then I see in next logs information that i18next miss keys and upload them to the locize.
When I use export default withAuthenticationRequired(Profile); then I see in browser POST to the /public/locales/cs/common.missing.json  ending with the 404.

I think it is working. I have to add addPath to the backend
  i18n: {
    defaultLocale: 'cs',
    locales: ['en', 'cs'],
  },
  // this will download the translations from locize directly, in client (browser) and server (node.js)
  // DO NOT USE THIS if having a serverless environment => this will generate too much download requests
  //   => https://github.com/locize/i18next-locize-backend#important-advice-for-serverless-environments---aws-lambda-google-cloud-functions-azure-functions-etc
  backend: {
    projectId: 'xxx',
    apiKey: 'xxx',
    referenceLng: 'cs',
    private: false,
    allowedAddOrUpdateHosts: ['localhost'],
    onSaved: (lng, ns) => {
      console.log(`Saved ${lng}, ${ns}`);
    },
    addPath: 'https://api.locize.app/update/{{projectId}}/{{version}}/{{lng}}/{{ns}}',
  },
  use: [require('i18next-locize-backend/cjs')],
  ns: ['common'], // the namespaces nees to be listed here, to make sure they got preloaded
  serializeConfig: false, // because of the custom use i18next plugin
  saveMissing: true,
  debug: true,
};

// for a serverless environment bundle the translations first. See downloadLocales script in package.json
// and configre this file like this:
// module.exports = {
//   i18n: {
//     defaultLocale: 'en',
//     locales: ['en', 'de'],
//   }
// }```

@mvlach as I coincidently using Auth0 as well consider to use their official https://github.com/auth0/nextjs-auth0 which just got a final 1.x release. Are you using SSG / SSR approach of NextJS? I think you could re-run before the build the npm script mentioned in the i18next-locize project and don't use the backend method but the CLI if you could add it to the build script

@mvlach you may want to check this out: https://github.com/isaachinman/next-i18next/pull/1000


64 bit compiler not exposed to IDE

Either the 64 bit g++ compiler is not available from the IDE, or I'm just not able to figure out how to get it to work

If I edit pvf_FLAGS under [preset Default] (can do so by clicking on "Build" - the clicker icon) then it builds in 64 bit mode. Also, can pass -p64 to use 64 bit precision

it works if I set cb_GPP64=1 as an environment variable, and pass the following arguments:

thank you very much for trying the ide and even found a work around (that i didn't think of)!!!
what i now and wrote somewhere that the ide is not ready .
the 64 bit in the current ide is not implemented yet.
it was in a pause state because of accidently lost of source.
it is now in develop state.

Implemented


ENH: Add power operator to mathinterpreter, 2**2 == 4

Before adding this operation, write the test.

@hsguidi
Here is how to use mark a test to be skip by pytest.
https://docs.pytest.org/en/8.0.x/how-to/skipping.html

@aureliobarbosa
To implement multi char symbols, like '**', 'sin', 'ln'..., we need remake 'lexer.py'.
This is something I would like to do, but I am not sure if now is the best moment.

Understood. As an exercise you implement the rest of division operator, '%'. What do you think?

This is being tracked on #30.


Increase iterations

How to increase iteration speed? on GPU RTX 3090 ?

If you are already using data.batch_size=1, there's no trivial way to speed up. You may try to enable token merging described here, but there's no guarantee that the results are the same. Also, it only works with stable diffusion guidance.

I've tried a bunch of things (e.g. decreasing system.renderer.num_samples_per_ray from 512 to 384) but all "easy" options resulted in noticeable degradation in quality. Closing.


jstree 3.3.6 not available on cdnjs.com

Last available is 3.3.5 :
https://cdnjs.com/libraries/jstree

Thank you - just pushed to npm, so cdnjs should update shortly.


UI: only show cell settings on non-prime connection

[x] merge #25902
[x] refactor UIState to emit signal on prime type change
[x] hide gsm toggles in AdvancedNetworking on UIState#primeTypeChanged
[x] also fixed map settings not being visible after upgrading to prime

Set them to default to visible since you might need to change the APN to get a network connection. Confirmed with local chffr backend that the UI updates immediately (5 seconds) after prime state changes while offroad, for both the networking settings and nav settings.


PDF Fragment selectors are no longer defined in RFC 3778

RFC 3778 was obsoleted by RFC 8118 (https://www.rfc-editor.org/rfc/rfc8118) and then 8118 was obsoleted by ISO 32000-2:2020, Annex O.

@lrosenthol any particular reason for that?

Why was 3778 replaced?  Same reason that many RFCs get replaced - they are out of date and changes have been made.
In this particular area, there are more types of fragment identifiers in the newer specs.

Got it. Do you think that this draft should be more specific and target a specific subset of these fragment identifiers?

Possibly, yes.  There are some that wouldn't make sense in this use case...

The reference is in the W3c Web Annotation Data Model https://www.w3.org/TR/annotation-model/#fragment-selector
PDF | http://tools.ietf.org/rfc/rfc3778
We could replace this reference by a new one in our Annotation spec. Who can provide a new URL?

Yes, that is my recommendation is to directly reference the updated RFC or ISO 32000.
For the RFC, I put the link in my initial comment.  That should be fine.


Implement FromIterator/Extend for StringList

@bilelmoussaoui This sentence has to be adapted since we don't adapt new anymore.
https://github.com/gtk-rs/gtk4-rs/blob/b18674c03b23ca170cdd20adc7b90e2a9bed4767/book/src/list_widgets.md?plain=1#L236
Also please tag me or request me as reviewer if you modify the book :)

@bilelmoussaoui This sentence has to be adapted since we don't use new anymore. https://github.com/gtk-rs/gtk4-rs/blob/b18674c03b23ca170cdd20adc7b90e2a9bed4767/book/src/list_widgets.md?plain=1#L236

Any suggestions on how to write that? at worst I can drop the book commit or you can push on top of my branch with the changes you like

Also please tag me or request me as reviewer if you modify the book :)

Sure

Any suggestions on how to write that? at worst I can drop the book commit or you can push on top of my branch with the changes you like

Note that we can create StringList directly from an iterator over strings.


Announce Route Navigation To Assistive Technologies

Is your feature request related to a problem? Please describe.
When navigating websites with assistive technologies (like screen readers), no announcements are made on navigation. This differs from the native full-page navigation that happens without "client-side routing". E.g. If I open "BaseCamp.com" from google, NVDA will announce that a new page has loaded. However, if I open any of the links on BaseCamp.com, I get no such announcement.
This has potential to confuse users.
Describe the solution you'd like
So this is not a "solved" problem in the domain of client-side routing. Though Marcy Sutton has done some research with Fable Tech Labs that has suggested some "best practices" that are worth considering. From that study, the best suggestion is to use an aria-live region to announce the results of the page navigation.
Describe alternatives you've considered
Additional context
Haven't had a chance to dive into the API to see how this might be implemented, but wanted to get a conversation moving before I looked into it further. Can also try and grab a recording of the scren reader behavior over the next few days, if that would be helpful.

I have put together a navigation announcer demo based on the findings of Marcy Sutton / Fable Tech Labs. It's pretty simple: on each page load append an aria-live div containing either some custom content, the title, the h1, or the location path.
I am not an experienced screenreader user so I'd be interested to know if this works well.

Source code for the demo


Feature/add scrutinizer

@GeeH
Something's still wrong with the Scrutinizer setup, can you have a look?

https://scrutinizer-ci.com/g/zendframework/modules.zendframework.com/inspections/39f884ff-eb8b-48de-a3c2-8c8093999a61

This proposal should be raised to crteam ML


lyxal: Watch sassyos.com

lyxal requests the watch of the watch_keyword sassyos\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

sassyos\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.


Last plot of the Gridded guide to fix

Ush something got wrong with this plot in the Gridded guide:

This is how it should look:


docs: updated docs

Description

Updated docs

Related issues
Link to open issues
Checklists

[x] npm run lint
[x] npm test
[x] npm run build

Codecov Report
Patch and project coverage have no change.

Comparison is base (f979965) 95.52% compared to head (a24582b) 95.52%.

:exclamation: Current head a24582b differs from pull request most recent head 494a16e. Consider uploading reports for the commit 494a16e to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #677   +/-   ##
=======================================
  Coverage   95.52%   95.52%
=======================================
  Files           2        2
  Lines          67       67
  Branches        9        9
=======================================
  Hits           64       64
  Misses          2        2
  Partials        1        1

Flag
Coverage Δ

unittests
95.52% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


CTF Estimation

Hello,
I have a question regarding the ability of MotionCor3 to estimate the CTF?
How exactly does one call the CTF estimate function in MotionCor3.
From looking at the list of command line parameters/options to be entered I could not find any parameter indicating CTF estimation.
Is CTF estimated by default, which parameters are dedicated to control CTF estimation.
Furthermore, is there a separate dedicated documentation/manual for MotionCor3 or does the official manual for MotionCor2 serves as the manaual, the parameters should be the same, right?
Thank you for providing this powerful tool to the field.
Edit:
So CTF appears to be estimated by default. Are there any parameters that allow one control over the CTF estimate, defocus range, patch, astigmatism...
Which CTF estimate algorithm is employed by MotionCor3, one of the better known ctffind4, GCTF, or something different?
Best
Dennis

Hi Dennis,
MotionCor3 implements its own algorithm for CTF estimation rather than calling an external package. The only adjustable parameter for CTF estimation is -ExtPhase, which controls whether an extra phase shift is estimated. Shawn recently released another open-source software package, GCtfFind, specifically for CTF estimation which can be found here: https://github.com/czimaginginstitute/GCtfFind. For both MotionCor3 and GCtfFind, the optimal defocus and astigmatism search ranges are estimated automatically. Patch-wise defocus estimation will be implemented soon.
We look forward to receiving feedback from the community and hope you’ll reach out with any other questions.
Ariana


Authorization resource required fields

Description

Updates the AuthorizationResource.permissions[].resource schema to match the influx API: https://docs.influxdata.com/influxdb/cloud/api/v2/#operation/PostAuthorizations
Relations

Relates https://github.com/komminarlabs/pulumi-influxdb/issues/10
References

Output from Acceptance Testing

> # zevisert in /code/o/g/ko/terraform-provider-influxdb/ on authorization-resource-required-fields
> make testacc
TF_ACC=1 go test ./... -v  -timeout 120m
?       github.com/komminarlabs/terraform-provider-influxdb     [no test files]
=== RUN   TestAccAuthorizationDataSource
--- PASS: TestAccAuthorizationDataSource (6.15s)
=== RUN   TestAccAuthorizationResource
--- PASS: TestAccAuthorizationResource (8.71s)
=== RUN   TestAccAuthorizationsDataSource
--- PASS: TestAccAuthorizationsDataSource (3.60s)
=== RUN   TestAccBucketDataSource
--- PASS: TestAccBucketDataSource (3.65s)
=== RUN   TestAccBucketResource
--- PASS: TestAccBucketResource (8.07s)
=== RUN   TestAccBucketsDataSource
--- PASS: TestAccBucketsDataSource (3.64s)
=== RUN   TestAccOrganizationDataSource
--- PASS: TestAccOrganizationDataSource (4.96s)
=== RUN   TestAccOrganizationResource
--- PASS: TestAccOrganizationResource (7.73s)
=== RUN   TestAccOrganizationsDataSource
--- PASS: TestAccOrganizationsDataSource (3.62s)
PASS
ok      github.com/komminarlabs/terraform-provider-influxdb/internal/provider   50.138s

@zevisert thanks for your PR. Let me check it out and get back to you.

@zevisert I had a look at the API and yes, the attribute id & name in permissions are optional. But the permissions needs orgID even though it is optional in the docs.
The problem now is if you set name attribute the influx api does not send the attribute back in the response causing unexpected new value issue in the provider. You can follow the discussion going on here. I will wait for the response from hashicorp and see how to proceed on this.
If this is something urgent for you then ofcourse I can set the name attribute read-only for now so you can continue with using id attribute. Let me know.

But the permissions needs orgID even though it is optional in the docs.

From my testing, orgID in permissions is optional at request time, and if it's missing, then the token's required orgID parameter is assumed for the permissions. For example:
POST http://localhost:8086/api/v2/authorizations
Cookie: influxdb-oss-session=a6[...]Iw==
content-type: application/json

{
    "orgID": "90a2dbdc3b0ff490",
    "description": "komminarlabs/terraform-provider-influxdb#22",
    "permissions": [
        { "action": "read",  "resource": { "type": "buckets" } },
        { "action": "write", "resource": { "type": "buckets" } }
    ]
}

---
HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8
X-Influxdb-Build: OSS
X-Influxdb-Version: v2.7.4
Date: Mon, 15 Apr 2024 14:48:13 GMT
Content-Length: 692
Connection: close

{
  "id": "0ce48e112f82f000",
  "token": "Aw4[...]JXQ==",
  "status": "active",
  "description": "komminarlabs/terraform-provider-influxdb#22",
  "orgID": "90a2dbdc3b0ff490",
  "org": "test",
  "userID": "0cdd7d2ab673a000",
  "user": "admin",
  "permissions": [
    { "action": "read", "resource": { "type": "buckets" } },
    { "action": "write", "resource": { "type": "buckets" } }
  ],
  "links": {
    "self": "/api/v2/authorizations/0ce48e112f82f000",
    "user": "/api/v2/users/0cdd7d2ab673a000"
  },
  "createdAt": "2024-04-15T14:48:13.246200754Z",
  "updatedAt": "2024-04-15T14:48:13.246200754Z"
}

The problem now is if you set name attribute the influx api does not send the attribute back in the response causing unexpected new value issue in the provider. You can follow the discussion going on here. I will wait for the response from hashicorp and see how to proceed on this.

Maybe that's been fixed? I'm using containerized influx version docker.io/library/influxdb:2.7.4-alpine, and I'm getting more fields back in permissions than I'm sending
POST http://localhost:8086/api/v2/authorizations
Cookie: influxdb-oss-session=a6[...]Iw==
content-type: application/json

{
    "orgID": "90a2dbdc3b0ff490",
    "description": "komminarlabs/terraform-provider-influxdb#22 (named)",
    "permissions": [
        {
            "action": "read",
            "resource": {
                "orgID": "90a2dbdc3b0ff490",
                "type": "buckets",
                "id": "e42561946e0fbc6c",
                "name": "telegraf"
            }
        },
        {
            "action": "write",
            "resource": {
                "orgID": "90a2dbdc3b0ff490",
                "type": "buckets",
                "id": "e42561946e0fbc6c",
                "name": "telegraf"
            }
        }
    ]
}

---
HTTP/1.1 201 Created
Content-Type: application/json; charset=utf-8
X-Influxdb-Build: OSS
X-Influxdb-Version: v2.7.4
Date: Mon, 15 Apr 2024 14:55:02 GMT
Content-Length: 920
Connection: close

{
  "id": "0ce48fa0bd42f000",
  "token": "v_m[...]xA==",
  "status": "active",
  "description": "komminarlabs/terraform-provider-influxdb#22 (named)",
  "orgID": "90a2dbdc3b0ff490",
  "org": "test",
  "userID": "0cdd7d2ab673a000",
  "user": "admin",
  "permissions": [
    {
      "action": "read",
      "resource": {
        "type": "buckets",
        "id": "e42561946e0fbc6c",
        "orgID": "90a2dbdc3b0ff490",
        "name": "telegraf",
        "org": "test"
      }
    },
    {
      "action": "write",
      "resource": {
        "type": "buckets",
        "id": "e42561946e0fbc6c",
        "orgID": "90a2dbdc3b0ff490",
        "name": "telegraf",
        "org": "test"
      }
    }
  ],
  "links": {
    "self": "/api/v2/authorizations/0ce48fa0bd42f000",
    "user": "/api/v2/users/0cdd7d2ab673a000"
  },
  "createdAt": "2024-04-15T14:55:02.389518988Z",
  "updatedAt": "2024-04-15T14:55:02.389518988Z"
}

If this is something urgent for you then ofcourse I can set the name attribute read-only for now so you can continue with using id attribute. Let me know.

If you're comfortable making a release like that, I'd appreciate it. The application I'm working with needs to create all-access tokens, and I can't use this custom resource in pulumi to do that since the permission's id is currently marked as required. See https://github.com/komminarlabs/pulumi-influxdb/issues/10

@zevisert Made some changes to the schema and docs. The name field is read-only now, I will spend some time to test the name field with more influx versions and release it in a future version. For now, you can use the id field together with a data source for specific resource authorization and ignore the id field to create all access token.

Thanks @thulasirajkomminar! This is great! Can I do anything to help release this into your pulumi provider as well?

Thanks @thulasirajkomminar! This is great! Can I do anything to help release this into your pulumi provider as well?

It's fairly simple so will try to release a new version today/tomorrow.


types(segment): add end_time to Segment

Description of changes:
I use xray creating the wrapper manually, and normally have something like:
const segment = new AWSXRay.Segment(rootName);
const ns = AWSXRay.getNamespace();
await ns.runPromise(async() => {
  segment.addIncomingRequestData(this.createFakeIncomingRequest(rootName));
  AWSXRay.setSegment(segment);
  await func(); // Original function
  segment.close();
  console.log({
    traceId: segment.trace_id,
    elapsed: +(segment as any).end_time - +segment.start_time, // This PR solve the (segment as any) as workaround
  });

To prevents the segment as any I mapped the end_time on Segment class.

Given the small surface area of the change and since #351 might take some time to merge, I will merge this for now.


Link to documentation in Readme is broken

No auto-redirect or manual way to reach the correct page.

I've added a redirect as a temporary fix whilst we get the url in the README updated.


Special requirements question

Introduce a new question for the applicant to describe any special requirements or particular need they may have for the hearing.

Danger was complaining about some commits messages and I had to rebase and force push the new commits. @zaparka @AlexaVB  can you please review again?


Timeline and Variable Folder searching bugfix

Fixes deeper level folder depth bugs not previously found in PR #748 before it got merged

Good catch! Thanks for the fix!


Have a lock North up mode

Perhaps pushing the compass icon for a longer time, should turn it into a Lock North Up mode. So no matter how we mess with the screen, the map won't tilt.

That would be great.


Maperture assumes PR reviewer is running locally

When reviewing a PR, if I switch to "Vector Toner" from Maperture, I get this:

It's because I am not running Maperture locally from my repo.
Possible solutions:

Delete this menu item when PR moves from Draft to Publish and replace it instead with the name of the remote PR branch
Label this item in the menu ("Vector Toner (local)")

This issue can/should be solved in the config file for the particular consumer repo. Transferring the issue there.


No trades made yet PLEASE HELP ASAP

I'm submitting a ...
[X] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)
I started a live Gekko using doker on ubuntu and it has not made any trades.

Expected result (what you hoped would happen)
It making a trade

Actual result (unexpected outcome)
Nothing, no trades have occurred or anything.
https://gyazo.com/9897eace412885fee9c3c2afd43d0070
https://gyazo.com/e7e6750c567a27a7a162e97c1739ab12

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

Congrulations on making it impossible to even help you slightly, by blurring out your strategy and parameters. Depending how you configured your trader, you might never ever make a trade...

Binance is currently not working. Check your Log files and you can check the errors. Currently, the person working on it has given an ETA for Monday / Tuesday for a fix.


If syntax sugar

See #724
$bool -> if {
    then -> receiver_1
    else -> receiver_1
}

Before
flow Main(start) (stop) {
	Println, Gt<int>, If
	---
	:start -> [
		(10 -> gt:compared),
		(50 -> gt:actual)
	]
	gt -> if
	if:then -> ('Actual is greater' -> println -> :stop)
	if:else -> ('Actual is lower' -> println -> :stop)
}

After
flow Main(start) (stop) {
	Println, Gt<int>
	---
	:start -> [
		(10 -> gt:compared),
		(50 -> gt:actual)
	]
	gt -> if {
	    then -> ('Actual is greater' -> println -> :stop)
	    else -> ('Actual is lower' -> println -> :stop)
	}
}

maybe more clean form (but not clear how idiomatic)
gt -> if {
    'Actual is greater' -> println -> :stop
} else {
    'Actual is lower' -> println -> :stop
}

Or even
if gt {
    'Actual is greater' -> println -> :stop
} else {
    'Actual is lower' -> println -> :stop
}

Without incoming ->
def Main(start) (stop) {
	Println, Gt<int>
	---
	if (10 == 50) {
	    then -> ('Actual is greater' -> println -> :stop)
	    else -> ('Actual is lower' -> println -> :stop)
	}
}

About if-else branching
I was thinking about if {...} else {...} but there's a problem - we need to route signal from then/else outports to trigger downstream nodes, i.e. we need then -> and else -> stuff

Maybe match is enough?
If match will allow not only to select value but also trigger branch (routing), then if is barely needed
match v {
  true -> ...
  false -> ...
}

See #291 for more details

At this point I'm more than sure that we don't need this, switch is already implemented in a way that it can completely replace it without any downsides and match will most likely do the same


Slack likes custom emotes

Is your feature request related to a problem? Please describe.
Add support of custom emotes like slack does
Describe the solution you'd like
CustomEmotes should support either a local image source or a distant url image source.
CustomEmotes should support also "recently used" existing feature.
CustomEmotes should be available to be searched.
CustomEmotes should be referenced in a customEmote specific category

https://github.com/TheWidlarzGroup/rn-emoji-keyboard/pull/190


Trouble with jsfmt

I followed the instructions here, but ran into some troubles :

Could not make it to work unless I added the suggested config into the Default config file.
It works, but changing the configuration parameters does not seem to work as intended. For example changing * attrsOnSameLineAsTag* to false does nothing, attributes are still on the same line as the tag.

Hi @antoinecomte can you provide a bit more of info about your setup?

version of esformatter, esformatter-jsx, jsfmt
a sample of your config file

Just to verify, you can use from the cli this wrapper for esformatter esbeautifier
At least that might help to see if there is anything wrong with the plugin itself or it might be the integration with jsfmt

Versions:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>My setting are :
User
{
  "autoformat": true,
  "extensions": [
    "js",
    "jsx",
    "sublime-settings"
  ],
  "plugins": [],

}

Default :
{
  // autoformat on save
  "autoformat": false,

  // array of extensions for autoformat
  "extensions": ["js", "sublime-settings"],

  // options for jsfmt
  "options": {
    "preset": "jquery",
    "indent": {
      "value": "    "
    },
    // plugins included
    "plugins": [
      "esformatter-jsx"
    // "esformatter-quotes",
    // "esformatter-semicolons",
    // "esformatter-braces",
    // "esformatter-dot-notation"
    ]
  },
  "jsx": {
    "formatJSX": true,
    // change these to your preferred values
    // refer to https://github.com/royriojas/esformatter-jsx#best-configuration for more options
    "attrsOnSameLineAsTag": false,
    "maxAttrsOnTag": 1,
    "firstAttributeOnSameLine": true,
    "alignWithFirstAttribute": true
  },
  "options-JSON": {
    "plugins": [
      "esformatter-quotes"
    ],
    "quotes": {
      "type": "double"
    }
  },
  "node-path": "node",
  "alert-errors": true,
  "ignore-selection": false
}

Feeling so dumb right now, as I realize my config was totally messed up.
Moving the jsxentry under options where it belongs fixed things up.
So sorry to have wasted your time


[IR] Implement topological sorting on Graph

A Priority Queue + Breadth First Search (PQ+BFS) method, sorting the graph:

Parent node should be always be ahead of its child node.
Nodes should keep original position as possible.

Remaining issues:

Input must be Directed Acyclic Graph (DAG).
Not utilizing Doubly Linked List effectively. (It's a burden!)
Need more testcases.

Fixes https://github.com/microsoft/onnxscript/issues/1427

@microsoft-github-policy-service agree [company="{UCLA}"]

@microsoft-github-policy-service agree

Thank you for your contribution!

One this is done. We can also move it to passes and share it across Graph and Function

@justinchuby


enable gradle build cache on circleci

Totally copied from https://github.com/square/okhttp/pull/4866

Pretty fast if no tests end up actually running :)


METRON-177 Fix typos on the Metron website

The link to Benefits is not going to the right place. It should link to:
https://cwiki.apache.org/confluence/display/METRON/Metron+Benefits

In the Architecture section, when I hover “Multi-Vendor..”, “Leverages..” and “Interactive..”, it browser thinks its links but its not. Don’t show those as links or people will think they are broken links

The “Read More” in Functional Themes section doesn’t work. It should go to:
https://cwiki.apache.org/confluence/display/METRON/Metron+Core+Capabilities+and+Functional+Themes#MetronCoreCapabilitiesandFunctionalThemes-CoreFunctionalThemesCoreFunctionalThemes

Misspled words in About and News

Security Data Scientist Text incorrect

Favicon

The “Github” link on the main page is going to the README, rather than https://github.com/apache/incubator-metron/

Ok, this looks good, +1

+1


Questions concerning the workflow

Sometimes there's a certain lag in accessing new language messages.
Translatewiki.net --> Intuition Repo GitHub --> Intuition src on Tool Labs
The latter is the source for the tool (if you don't want to rely permanently on your own textfile)
Is this an automated process (all 3 steps), or is this done by hand?
It would be great, if these steps - and the merge of new tool domains/messages - would happen in a fixed period. This would make things more predictable.
Eg.: message updates from TWN every day (two/three days?), merges not later than a week and GitHub repo synced to Tool Labs every day.
Thanks.

You may also be interested in #45 and 75cfbc25a.


App builds with NativeBase carry needless bloat

I have gone through these following points

[x] Check latest documentation: https://docs.nativebase.io/
[x] Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[x] Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[n/a] Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[n/a] For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[n/a] For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description
I would like to see Native Base reduce its build bloat, by offering the option to omit unused resources, like the dozen icon fonts.
node, npm, react-native, react and native-base version, expo version if used, xcode version
n/a
Expected behaviour
Smaller builds.
Actual behaviour
Larger builds 😉
Steps to reproduce
Run react-native link on a project with Native Base installed and behold!
Is the bug present in both iOS and Android or in any one of them?
It's present in both, but Native Base has the even-worse behavior for Android of installing copies of the fonts into the versioned /android directory.
Any other additional info which would help us debug the issue quicker.
###Important
If you want your issue to be looked at quicker, attach a snack reproducible with your issue. Makes it easier for us!

Did you find any solution to this?
I just realized the multiple MBs added to the build after adding custom fonts and having to use react-native link.
Now my android\app\src\main\assets\fonts is filled with all these:

When I actually only need my one custom fonts and two icons library (material and ionicons) :/

Actually I wish it got the attention it deserves without being closed; I still believe NativeBase brings along a too heavy package...

@prometheas Apologies for the delay in replying! We're busy with our latest release.
I know this is frustrating that NativeBase includes needless bloat. We've added this to our list, hope to fix this in next release 🤞
Thanks for reporting!

Fair enough. Software is hard. Looking forward to it.

Stale bot closed this issue again. How'd it this effort turn out?
Full disclosure: I'm asking in part because my team and I are at a juncture where we'll either wind up upgrading from 2.x to 3.x or drop NativeBase altogether from our project.

@prometheas Sorry for the inconvenience. I know this is frustrating. We're working on it and try to fix this as soon as possible.

Eh. Software is hard. The update does help us with our considerations, though. Good fortunes!

@prometheas for web, I wrote a simple script like this to clear out the unnecessary bloat. Saved a few MB.
import os

def remove_files(path):
  names = ['MaterialCommunityIcons']
  for root, dirs, files in os.walk(path):
      for name in files:
          path = os.path.join(root, name)
          if os.path.isfile(path):
              for n in names:
                  if n not in path:
                      print('Removing: ' + name)
                      os.remove(path)

os.chdir('./apps/next/deploy/.next/static/chunks/fonts')

path = os.getcwd()

remove_files(path)

os.chdir('../../../../../../../')
path = os.getcwd()
os.chdir('./apps/next/deploy/.next/server/static/chunks/fonts')

path = os.getcwd()
remove_files(path)


[core] File index result should be able to process and/or.

Purpose
FileIndexPredicate return FileIndexResult, not Boolean any more.
For example, bit map index:
SQL:
SELECT * FROM <TABLE> WHERE a1 = 1 and a2 = 2

Bitmap index for a1 returns rows 1,2,3
Bitmap index for a2 returns rows 4,5,6.
Then this file could be skipped.
SQL
SELECT * FROM <TABLE> WHERE a1=1 or a1=2 or a1=3

Bitmap index for a1=1 returns rows null
Bitmap index for a1=2 return rows 1,2,3
Bitmap index for a1=3 return rows 3,4,5
Then this file should be found, and rows should be 1,2,3,4,5 (push down not implement yet)
Generally, file index implement should handle method 'or', whatever the IndexResult is produced by the file index type itself, or other kind of file index.
Tests

API and Format

Documentation

Can you write an example about how to use FileIndexResult.

Can you write an example about how to use FileIndexResult.

Added an example about bitmap int pull request description.

+1


Horreum Elasticsearch Authentication

Feature idea.
Support user/pass along with API-Key
Describe the solution you'd like
Allow Horreum Elasticsearch Integration to supply a User/Pass to read from Elasticsearch
Additional information
Attempting to make a read-only API key w/
POST /_security/api_key
{
  "name": "rook-key",
  "role_descriptors": {
    "role-a": {
      "cluster": ["all"],
      "indices": [
        {
          "names": ["*"],
          "privileges": ["read"]
        }
      ]
    }
  }
}

However, I am met with this response {"Message":"Your request: '/_security/api_key' is not allowed."}
Looking at AWS-ES documentation it appears an API-Key is not possible.
Security API is part of x-pack which is not support yet by AWS Elasticserach service.

Fixed in : https://github.com/Hyperfoil/Horreum/pull/1299


Collect necessary  information  regarding the conference website.

Acceptace

[ ]  I have all the information which are required to move forward on the conference website development.

Tasks

[x]  Set a meeting with sagar for the discussion.
[x] Collect require information on docs.
[ ] Add  other tasks after the sync. ( if any)

DOCS

Working docs which will have conference details here.

Added the link for the working docs, where the committee members are working to finalize the conference structure.
cc @sagargg

@arjun-gautam @sagargg Guys, I have updated the link of working docs. That doc will contain all necessary information required for the conference website.

@nikeshbalami @sagargg All the content in the following doc link is up to date.
https://docs.google.com/document/d/18lMgzpZETJs4dHBJACqeI9CZ7eTTvQb-9C5FG_LE0Zw/edit

Mistakely "close with comment"ed the issue. haha. reopened it.

New details has been updated in the working docs docs. cc @arjun-gautam @sagargg

@nikeshbalami noted. I will update it

@nikeshbalami  updated it

@nikeshbalami  anything remaining to update. Please review the content section.

The conference page looks good.
Closing the issue.


Password value: input vs editor

When you use the input helper for a password field, the value attribute is not rendered. When you use the editor helper, the value attribute is rendered. This is how it works in MVC 5, I haven't tried in Core but a quick look at the code tells me it should work the same (see DefaultEditorTemplates.PasswordTemplate.
Is there a reason for this difference?

Hi @maxtoroq. This behavior is intentional.
The reason is that it can lead to sensitive data to be exposed in clear text on the client side, as in the rendered page that value will be in clear text (in the source of the page).

@mkArtakMSFT You either didn't read or didn't understand. I know the behavior is by design. My question is, why isn't the editor helper behavior consistent?

I indeed misunderstood you, @maxtoroq. Reopening to understand how we should move forward here.

@dougbu, seems like a bug. How hard will it be to fix this?

If we confirm this happens in ASP.NET Core MVC as well, it's a one-line fix. Would need a few tests of course.
I also suggest we add a default display template for passwords.

f061d328d9


topk support to get most frequent elements along with its frequency.

Added in https://github.com/tylertreat/BoomFilters/pull/9.


docs(README): add reference to the audit report

Same than https://github.com/axone-protocol/axoned/pull/747. Thought it’d be a good idea to include the audit report in the README to make it clear.

Summary by CodeRabbit

New Features

Introduced an "Audit" section in the README for enhanced transparency.
Added a detailed audit table documenting the audit of the Axone Smart Contract, including date, auditor, version, and a link to the audit report.

size-limit report 📦

Path
Size

target/wasm32-unknown-unknown/release/axone_objectarium.wasm
458.07 KB (0%)

target/wasm32-unknown-unknown/release/axone_law_stone.wasm
648.51 KB (0%)

target/wasm32-unknown-unknown/release/axone_cognitarium.wasm
882.03 KB (0%)

target/wasm32-unknown-unknown/release/axone_dataverse.wasm
683.93 KB (0%)


Ref docs issue

Error:

Traceback (most recent call last):
File "D:\a_work\1\s\target_repo\update_toc.py", line 6, in
import yaml
ModuleNotFoundError: No module named 'yaml'
##[error]The process 'C:\hostedtoolcache\windows\Python\3.10.11\x64\python.exe' failed with exit code 1

https://apidrop.visualstudio.com/Content CI/_build/results?buildId=391326&view=results

@danieljurek for notification.

Closing. This was a transient error.


[OB-2323] fix: CSP crashing on M1 macs

Similar to recent crashes that have been fixed for Quest & Android, mimalloc crashes when CSP is initialized within an application running on an M1 Mac.
The short-term fix for this is the same as was applied for Quest. We fall back to STL allocator behaviour and avoid the usage of mimalloc entirely when we're running on macosx.

We also need to exclude mimalloc from the linker arguments otherwise this will not build when building a shared library.

Great catch! Thanks

We also need to exclude mimalloc from the linker arguments otherwise this will not build when building a shared library.

Great catch! Thanks

Fixed in latest.


Appstudio update test-component-pac-utju

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-utju-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
31 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
30 seconds
deprecated-base-image-check

✅ Succeeded
30 seconds
inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
29 seconds
sbom-json-check

✅ Succeeded
14 seconds
optional-label-check

✅ Succeeded
14 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
14 seconds
show-summary

Pipelines as Code CI/test-component-pac-utju-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
31 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
30 seconds
deprecated-base-image-check

✅ Succeeded
30 seconds
inspect-image

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
1 minute
clamav-scan

✅ Succeeded
29 seconds
sbom-json-check

✅ Succeeded
14 seconds
optional-label-check

✅ Succeeded
14 seconds
label-check

✅ Succeeded
14 seconds
show-summary

✅ Succeeded
6 seconds
show-sbom

Pipelines as Code CI/test-component-pac-utju-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
35 seconds
build-container

✅ Succeeded
9 seconds
clair-scan

✅ Succeeded
14 seconds
inspect-image

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
14 seconds
deprecated-base-image-check

✅ Succeeded
47 seconds
clamav-scan

✅ Succeeded
12 seconds
optional-label-check

✅ Succeeded
9 seconds
label-check

✅ Succeeded
6 seconds
show-sbom

✅ Succeeded
7 seconds
show-summary


Include of non-modular header inside framework module 'SQLite.SQLite_Bridging'

Hi,
I recently added SQLite to my project through cocoapods. I am having trouble running the test target, getting these errors:

Any thoughts on how to fix this?

I was getting that error as well, but I found a workaround for now. I noticed that import was wrapped in a #ifndef cocoapods, so I added SQLite.swift as a pod of my test target, which at least let me run tests. Here's what my podfile looks like:
target 'MyProject' do
    pod 'Alamofire'
    pod 'SQLite.swift'
    ...

    target 'MyProjectTests' do
        pod 'SQLite.swift'
    end
end

Thanks @nickmshelley ! That resolved the issue!

Specify the correct version of the SQLite pod, like so:
pod 'SQLite.swift', '~> 0.10.1'
That version works on xCode 7.3.1