Pending outgoing STX transfer, amount is not displayed

Top one is an outgoing transfer for 1 STX, amount is not displayed.
Below is an incoming pending transfer there the amount is displayed.

I expect the amount to be displayed in both cases.


cross-compilation to Windows

builder for '/nix/store/dmclfdwb79ipx19q7f3m7zdd81af3pg1-threepenny-gui-<IP_ADDRESS>-lib-threepenny-gui-x86_64-pc-mingw32.drv' failed with exit code 1

hydra job failed`
locally building
library:
nix build -f release.nix nix-tools.libs.x86_64-pc-mingw32-iohk-monitoring.x86_64-linux
executables:
nix build -f release.nix nix-tools.exes.x86_64-pc-mingw32-iohk-monitoring.x86_64-linux
tests:
nix build -f release.nix nix-tools.tests.x86_64-pc-mingw32-iohk-monitoring.tests.x86_64-linux

Ran
nix build -f release.nix nix-tools.tests.x86_64-pc-mingw32-iohk-monitoring.tests.x86_64-linux
after commenting out all tests but still failed.
The other two commands finished successfully.

we need @angerman 's help here
the error we see:
builder for '/nix/store/7zz20wgipfzgic8xdy3329xnd2a2r71b-iohk-monitoring-<IP_ADDRESS>-test-tests-x86_64-pc-mingw32.drv' failed with exit code 1; last 10 log lines:
  RUNNING TESTS for iohk-monitoring-<IP_ADDRESS>-test-tests-x86_64-pc-mingw32 via wine64
  ================================================================================
  Copying extra test libraries ...
  Copying library dependencies...
  ghc-pkg: : getDirectoryContents:openDirStream: does not exist (No such file or directory)
  Running 1 test suites...
  Test suite tests: RUNNING...
  Setup: <file descriptor: 3>: hGetContents: invalid argument (invalid byte sequence)
  <file descriptor: 3>: hGetContents: invalid argument (invalid byte sequence)
  Setup: <file descriptor: 3>: hGetContents: invalid argument (invalid byte sequence)

it is presumably not in our code, since that was commented out.

latest PRs by angerman made it happen! all cross-compilation targets now build.


Cannot build apk after adding this package to my pubspec.yaml file.

I am getting this error when I try to run the command flutter build akp
* What went wrong:
Execution failed for task ':ed_screen_recorder:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > 1 exception was raised by workers:
     com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
     C:\Users\usama\.gradle\caches\transforms-3\213a50da74ca5943e43b6a60fa7c8adf\transformed\core-1.7.0\res\values\values.xml:105:5-114:25: AAPT: error: resource android:attr/lStar not found.

After running flutter doctor in the project
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19043.1706], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[√] Chrome - develop for the web
[!] Visual Studio - develop for Windows (Visual Studio Professional 2022 17.1.4)
    X The current Visual Studio installation is incomplete. Please reinstall Visual Studio.
[√] Android Studio (version 2021.2)
[√] Connected device (3 available)
[√] HTTP Host Availability

! Doctor found issues in 1 category.

Extended Version of flutter doctor.
flutter doctor -v
[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19043.1706], locale en-US)
    • Flutter version 2.10.5 at D:\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (7 weeks ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\usama\AppData\Local\Android\sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: D:\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[!] Visual Studio - develop for Windows (Visual Studio Professional 2022 17.1.4)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Professional
    • Visual Studio Professional 2022 version 17.1.32407.343
    X The current Visual Studio installation is incomplete. Please reinstall Visual Studio.

[√] Android Studio (version 2021.2)
    • Android Studio at D:\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+7-b1504.28-7817840)

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19043.1706]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 102.0.5005.63
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 101.0.1210.53

[√] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Please help me with this issue. Thank you!

The problem may not be related to the package. Can you please take a look at this issue? https://stackoverflow.com/questions/52512326/com-android-builder-internal-aapt-v2-aapt2exception-android-resource-compilatio

I have checked the link  and I changed the compileSdkVersion version of my project from 31 to 28 but I was not successful building the apk file. Then I changed the compileSdkVersion of the ed_screen_recorder package from 30 to 28. After changing the version I am still not able to develop the .apk file.
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':ed_screen_recorder:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
   > 1 exception was raised by workers:
     com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
     C:\Users\usama\.gradle\caches\transforms-3\213a50da74ca5943e43b6a60fa7c8adf\transformed\core-1.7.0\res\values\values.xml:105:5-114:25: AAPT: error: resource android:attr/lStar not fo
und.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 3m 54s

Can you try clearing the cache from the Android Studio program and then opening the android folder and getting a build?

same issue with me , its running perfect in debug mode , but when it comes to building release build, its not working. build failed with "Resource linking failed".

Same issue here too. Can't build with newer gradle versions and the default flutter project's gradle is now 7.1.2, so any new project will probably fail.

Same issue here. Have you find any solution to this?

same issue faced anybody find the solution?

Version 0.0.13 has been released. Could you please check again and report back to me?

The issue is fixed and now I can build apk after adding the package, but the package doesn't work (couldn't record the screen, even when using the example code) on my phone. (Poco F3, Android 13)


Can't persist 100 users-UserNameIndex index is null

I tried to persist  100 users via Volante DB (version <IP_ADDRESS>).After an attempt to read comited data the UserNameIndex equals to null. What are steps need to perform to set UserNameIndex index ?
using System;
using System.Collections;
using Volante;

namespace ConsoleApplication8
{
    public class DatabaseRoot : Persistent
    {
        public IIndex<string, User> UserNameIndex;
    }

    public class User : Persistent
    {
        public string FullName { get; set; }
        public string Username { get; set; }

    }
    class Program
    {
        static void Main(string[] args)
        {

            IDatabase db = DatabaseFactory.CreateDatabase();
            db.Open(@"c:\fileinfo.dbs");

            DatabaseRoot dbRoot = null;
            if (null != db.Root)
            {
                dbRoot = (DatabaseRoot) db.Root;
            }
            else
            {
                // only create root the first time
                dbRoot = new DatabaseRoot();
                db.Root = dbRoot;
                dbRoot.UserNameIndex = db.CreateIndex<string, User>(IndexType.Unique);
                // changing the root marks database as modified but it's
                // only modified in memory. Commit to persist changes to disk.
                for (int i = 0; i < 100; i++)
                {
                    var u = new User
                    {
                        FullName = "User" + i,
                        Username = "usrname_" + i

                    };
                    dbRoot.UserNameIndex.Put(u.Username, u);
                }

                db.Commit();
            }

            IDictionaryEnumerator de = dbRoot.UserNameIndex.GetDictionaryEnumerator();
            string prevName = "";
            //simplified code: doesn't show the first duplicate file
            while (de.MoveNext())
            {
                string name = (string)de.Key;
                if (name == prevName)
                {
                    User fe = (User)de.Value;
                    Console.WriteLine(" " + fe.FullName);
                }
                prevName = name;
            }

            Console.ReadLine();
        }
    }
}

I noticed that you didn't call db.Close() which ensures that everything is fully written. Please try to add Close() and see if it fixes it.

I added db.Close(); just before Console.ReadLine(); .The exception still occurs .

It's subtle but proper sequence of creating a root is:
                dbRoot = new DatabaseRoot();
                dbRoot.UserNameIndex = db.CreateIndex<string, User>(IndexType.Unique);
                db.Root = dbRoot;

When you assign UserNameIndex, it doesn't mark dbRoot as changed, so database doesn't know to persist it. You can also do:
                dbRoot = new DatabaseRoot();
                db.Root = dbRoot;
                dbRoot.UserNameIndex = db.CreateIndex<string, User>(IndexType.Unique);
                dbRoot.Modify();

to manually mark dbRoot object as changed.

Thanks  .
dbRoot.Modify(); solved my problem


Typescript types missing for V3

Features:
Hi and thanks for this awesome library.
Is there any plan for introducing types for version 3?

Thanks for replying @chrvadala .
Those types are for version 2. These migrations have not been implemented in the type definitions: https://github.com/chrvadala/react-svg-pan-zoom/blob/master/docs/migrate-from-v2-to-v3.md
As you can see here: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/react-svg-pan-zoom/index.d.ts

the Value field is nullable, but in version 3 it is required
miniature and toolbar props have not been migrated
and other things making it impossible to compile the component.

You're right... Sorry, but I don't use ts
Can you try to contact https://github.com/huy-nguyen that is the maintenair of the ts descriptor?

I don't use the library anymore but nevertheless opened a PR here: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/39085.

That is great, thanks @huy-nguyen

Thanks @huy-nguyen 🚀


Accessibility Issues in Map Components

WCAG Criterion 2.4.4 Link Purpose (In Context) (Level A)

The ‘Leaflet’ link on the map has link text of ‘Leaflet’, but it’s not clear where this goes. There’s a title attribute that explains it but this isn’t always available to screen reader users. Use an ARIA label that provides a bit more information.

WCAG Criterion 4.1.2 Name, Role, Value (Level A)

‘View Fullscreen’ selection on the map is set as a link but doesn’t function like one. Change to button

WCAG Criterion 2.4.7 Focus Visible (Level AA)

No visible focus indicator for the tab stop between the end of the spaces list and the first interactive item on the map.

Leaflet link fixed in 45569cccf12e11285a89a0091a1bd524966a990a
Fullscreen changed to button and reworked in 4b58731ea75705cb276ecd2764c1c51faff38ff5
Added focus indicator to leaflet container in 187d1a3f0ffb4b1709ef5319bc7b0aabdf7e6c4f


User management: passwordFile does not work as advertised on current stable NixOS

Describe the bug
Using users.users..passwordFile = "path/to/textfile/containing/hashed/password"; does not work as advertised, I'm unable to login.
Using a workaround with hashedPassword sourced from the same file does work and results in a system I can login to.
Steps To Reproduce
Bootstrapping a new system with NixOS and having a configuration.nix containing:
users = {
  mutableUsers = false;

  users.kciredor = {
    isNormalUser = true;
    passwordFile = "/path/to/password.txt";
  };
};

Followed by running nixos-install, results in a system I cannot log in to.
Working around the issue by replacing passwordFile with hashedPassword like this does work:
users = {
  mutableUsers = false;

  users.kciredor = {
    isNormalUser = true;
    hashedPassword = lib.strings.fileContents path/to/password.txt;
  };
};

Please note that both approaches use the exact same password input file.
Looking into https://github.com/NixOS/nixpkgs/blob/nixos-21.05/nixos/modules/config/users-groups.nix#L247 I'm confident that passwordFile should contain a hash and not a plaintext password.
I've created the hashed password using mkpasswd -m sha-512 | tr -d '\n' > password.txt (which also strips the trailing linebreak unfortunately produced by mkpasswd, as can be verified by a hex dump).
Notify maintainers
Could not find any maintainers listed so I'm tagging the most recent committers to users-groups.nix:
@alyssais @symphorien, @dnr, @ncfavier, @infinisil
Metadata
$ nix-shell -p nix-info --run "nix-info -m"
these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked):
  /nix/store/1bpw671p7r93sp3sbdxq9ly6h4npx5ff-bash-interactive-4.4-p23-dev
copying path '/nix/store/1bpw671p7r93sp3sbdxq9ly6h4npx5ff-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 5.10.81, NixOS, 21.05.4394.2553aee74fe (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.16`
 - channels(root): `"home-manager-21.05, nixos-21.05.4394.2553aee74fe, nixos-unstable-22.05pre334685.8a308775674"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Have you tried without | tr -d '\n'? That shouldn't be needed.
Can you compare the contents of /etc/passwd and /etc/shadow in both cases?

Yes @ncfavier my first attempts were without the removal of newline. But because it was not working, and a hint on IRC, I took a better look at the produced hash via a hex dump, and I figured: "ah that must be it, there's a newline character added to the hash". But that was not the problem, I left it there though because for the workaround with hashedPassword it still makes sense.
To be honest /etc/shadow has a hash of '!' for my user after nixos-install. The docs state that it will be updated on system activation, which in my mind is after a boot into the new system.
So currently I'm thinking: what if nixos-install is not the same thing as nixos-rebuild? Could it be nixos-install which does not play nicely with passwordFile?

As soon as I run nixos-switch rebuild from a running system, replacing hashedPassword with passwordFile, my /etc/shadow file user hash is removed and replaced by '!' again. So nixos-install and nixos-rebuild act the same way: '!' instead of the hash.

Think I've got it now. As the documentation states, passwordFile must contain the full path to the file containing the password hash.
When bootstrapping a new system, everything is mounted into /mnt so I have to deal with the /mnt prefix. Using full path it means something like /mnt/path/to/password.txt.
When rebuilding a running system there is no /mnt prefix so the path would suddenly have to became /path/to/password.txt.
For that reason I've been using a relative path in configuration.nix which works fine with other stuff like importing files, lib.strings.fileContents and so on. But not with passwordFile.
I'll stick with my workaround for this reason, sourcing the hashedPassword with lib.strings.fileContents allows a relative path input and works with bootstrapping a new system and rebuilding a running system.
Would be a nice improvement if passwordFile could both accept a full path and relative path I think!

When bootstrapping a new system, everything is mounted into /mnt so I have to deal with the /mnt prefix. Using full path it means something like /mnt/path/to/password.txt.

Have you tried it without the /mnt prefix? I also use passwordFile and bootstrapping new systems works fine for me with that.

Yes thanks @OPNA2608, passwordFile =  "/etc/nixos/secrets/password-user.txt" does not work during install for me. It results in the '!' "hash" in /etc/shadow.
The file /etc/nixos/secrets/password-user.txt is actually a symlink to /mnt/home/username/blah/password-user.txt during install (and to /home/username/blah/password-user.txt after install). Did not think that would matter. To ensure it does or does not, I've used that exact (destination) value with /mnt/ prefix for passwordFile which does not work either.
The value of /home/username/blah/password-user.txt, omitting /mnt, does finally work with nixos-install!
Perhaps passwordFile does not follow symlinks during nixos-install, and does follow them during nixos-rebuild?

Quoting the description of the passwordFile option:

The password file is read on each system activation.

And system activation happens when you nixos-install, nixos-rebuild and when you boot the machine.

For future readers, I was facing this problem while configuring an impermanence setup (with https://github.com/nix-community/impermanence), as I was trying to persist the hashed password file but failing, even though the file was being bind mounted (and/or symlinked). Thanks to the information in this thread, I figured out that I had to add fileSystems."/path/to/password/file".neededForBoot = true; so that the bind mount occurred at the right time, such that the password file was properly picked up, and I could then log in.


board:arm64: add support for Raspberry Pi 4 Model B

This is an AArch64 board. We also add BCM2711 SoC support
TODO：will add spin-table to support smp

This is interesting. I'm just curious about whether these codes can somehow be shared with Pi Zero (BCM2835) and Pi 3B (BCM2837).

This is interesting. I'm just curious about whether these codes can somehow be shared with Pi Zero (BCM2835) and Pi 3B (BCM2837).
I Think the code also can run on BCM283x platform.

raspberry pi 3b is base BCM283X chipset , raspberry pi 4b is base BCM2711 chipset .Due to platform compatibility, the linux drivers for raspberry pi 4b are based on the BCM283x.
But zephyr don't support raspberry pi 3b, so if named bcm283x, It will cause even more confusion.

But zephyr don't support raspberry pi 3b, so if named bcm283x, It will cause even more confusion.

Someone (to be honest, me :p) in the future may be interested in it.

As described in bcm2711-peripherals.pdf:

2.2. Mini UART
The implemented UART is not a 16650 compatible UART. However as far as possible the first 8 control and status registers are laid out like a 16550 UART. All 16550 register bits which are not supported can be written but will be ignored and read back as 0. All control bits for simple UART receive/transmit operations are available.

Instead of submitting a new uart_bcm2711.c, I think the existing uart_ns16550.c should be working.

But zephyr don't support raspberry pi 3b, so if named bcm283x, It will cause even more confusion.

Someone (to be honest, me :p) in the future may be interested in it.

bcm238x don

But zephyr don't support raspberry pi 3b, so if named bcm283x, It will cause even more confusion.

Someone (to be honest, me :p) in the future may be interested in it.

The BCM238x does not use the GIC (Generic Interrupt Controller), and Zephyr does not support the ARMv7 timer. As a result, there are significant differences between the BCM283x and BCM2711 chipsets.

But zephyr don't support raspberry pi 3b, so if named bcm283x, It will cause even more confusion.

Someone (to be honest, me :p) in the future may be interested in it.

The BCM238x does not use the GIC (Generic Interrupt Controller), and Zephyr does not support the ARMv7 timer. As a result, there are significant differences between the BCM283x and BCM2711 chipsets.

As described in bcm2711-peripherals.pdf:

2.2. Mini UART
The implemented UART is not a 16650 compatible UART. However as far as possible the first 8 control and status registers are laid out like a 16550 UART. All 16550 register bits which are not supported can be written but will be ignored and read back as 0. All control bits for simple UART receive/transmit operations are available.

Instead of submitting a new uart_bcm2711.c, I think the existing uart_ns16550.c should be working.

As described in bcm2711-peripherals.pdf:

2.2. Mini UART
The implemented UART is not a 16650 compatible UART. However as far as possible the first 8 control and status registers are laid out like a 16550 UART. All 16550 register bits which are not supported can be written but will be ignored and read back as 0. All control bits for simple UART receive/transmit operations are available.

Instead of submitting a new uart_bcm2711.c, I think the existing uart_ns16550.c should be working.

Unfortunately, it does not work properly. The BCM2711 uses dw8250, which is similar to ns16550 but not identical. Moreover, if the BCM2711 were to use ns16550, it would cause misunderstandings, leading people to mistakenly believe that the BCM2711 actually uses ns16550.

@carlocaione I refactored uart_bcm2711.c and moved uart_addr into the data structure.
@povergoing @vonhust  the cntfrq_el0 register can be read by software. I referred to the Linux code, and Linux also reads the cntfrq_el0  register. Therefore, in Zephyr, enabling the CONFIG_TIMER_READS_ITS_FREQUENCY_AT_RUNTIME configuration option should be sufficient.

It's 54MHZ.
@SgrrZhf  samples/synchronization and samples/subsys/shell/shell_module is all ok , have try again.

It's 54MHZ.

Cool, that's good to know

It's 54MHZ.

Cool, that's good to know. So you need to set SYS_CLOCK_HW_CYCLES_PER_SEC to 54M

static TIME_CONSTEXPR inline int sys_clock_hw_cycles_per_sec(void)
{
#if defined(CONFIG_TIMER_READS_ITS_FREQUENCY_AT_RUNTIME)
	return sys_clock_hw_cycles_per_sec_runtime_get();
#else
	return CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC;
#endif
}

static inline int z_impl_sys_clock_hw_cycles_per_sec_runtime_get(void)
{
	extern int z_clock_hw_cycles_per_sec;

	return z_clock_hw_cycles_per_sec;
}

static ALWAYS_INLINE void arm_arch_timer_init(void)
{
#ifdef CONFIG_TIMER_READS_ITS_FREQUENCY_AT_RUNTIME
	extern int z_clock_hw_cycles_per_sec;
	uint64_t cntfrq_el0 = read_cntfrq_el0();

	__ASSERT(cntfrq_el0 < INT_MAX, "cntfrq_el0 cannot fit in system 'int'");
	z_clock_hw_cycles_per_sec = (int) cntfrq_el0;
#endif
}

If CONFIG_TIMER_READS_ITS_FREQUENCY_AT_RUNTIME is enabled, the SYS_CLOCK_HW_CYCLES_PER_SEC configuration in Kconfig becomes irrelevant because the value will be read from the cntfrq_el0 register at runtime.

If CONFIG_TIMER_READS_ITS_FREQUENCY_AT_RUNTIME is enabled, the SYS_CLOCK_HW_CYCLES_PER_SEC configuration in Kconfig becomes irrelevant because the value will be read from the cntfrq_el0 register at runtime.

Yes, you're right. But why did you set SYS_CLOCK_HW_CYCLES_PER_SEC with an irrelevant value 25M IIRC? Is that the real default value regarding this SOC?

If CONFIG_TIMER_READS_ITS_FREQUENCY_AT_RUNTIME is enabled, the SYS_CLOCK_HW_CYCLES_PER_SEC configuration in Kconfig becomes irrelevant because the value will be read from the cntfrq_el0 register at runtime.

Yes, you're right. But why did you set SYS_CLOCK_HW_CYCLES_PER_SEC with an irrelevant value 25M IIRC? Is that the real default value regarding this SOC? I mean, your SOC Kconfig might be reused in the future, and sometimes the board disables the CONFIG_TIMER_READS_ITS_FREQUENCY_AT_RUNTIME or the board boot from EL3 so that the SYS_CLOCK_HW_CYCLES_PER_SEC is a necessary KConfig because you might get a zero when boot from EL3

You are correct. To avoid any confusion, it is better to set SYS_CLOCK_HW_CYCLES_PER_SEC to 54000000. I have made the necessary changes.

@lenghonglin can you paste the output of ./script/twister -p .... ?

@lenghonglin can you paste the output of ./script/twister -p .... ?

a little slow, pls wait a moment

@carlocaione  Still not complete all test case, It's very slow. The CI Twitser has been successful, and the results should be comparable to running Twitser on my local computer.

@lenghonglin can you paste the output of ./script/twister -p .... ?

Finally
Renaming output directory to /home/hlleng/workspace/zephyr/zephyrproject/zephyr/twister-out.2
INFO    - Using Ninja..
INFO    - Zephyr version: zephyr-v3.4.0-3305-g8a0a1c2abe11
INFO    - Using 'zephyr' toolchain.
INFO    - Building initial testsuite list...
INFO    - Writing JSON report /home/hlleng/workspace/zephyr/zephyrproject/zephyr/twister-out/testplan.json
INFO    - JOBS: 4
INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
INFO    - Total complete: 2223/2223  100%  skipped: 1799, failed:    0, error:    00
INFO    - 2434 test scenarios (2223 test instances) selected, 1799 configurations skipped (1679 by static filter, 120 at runtime).
INFO    - 424 of 2223 test configurations passed (100.00%), 0 failed, 0 errored, 1799 skipped with 0 warnings in 6821.43 seconds
INFO    - In total 4252 test cases were executed, 7625 skipped on 1 out of total 609 platforms (0.16%)
INFO    - 0 test configurations executed on platforms, 424 test configurations were only built.
INFO    - Saving reports...
INFO    - Writing JSON report /home/hlleng/workspace/zephyr/zephyrproject/zephyr/twister-out/twister.json
INFO    - Writing xunit report /home/hlleng/workspace/zephyr/zephyrproject/zephyr/twister-out/twister.xml...
INFO    - Writing xunit report /home/hlleng/workspace/zephyr/zephyrproject/zephyr/twister-out/twister_report.xml...
INFO    - Run completed
./scripts/twister -p rpi_4b  21058.57s user 2317.72s system 342% cpu 1:53:43.45 total


Validate on submit

Thank for creating this fantastic library! I'd like to suggest adding the ability to trigger validation of the form. Specifically when a form is submitted you'd typically want to indicate to the user if he/she is missing some required fields (and maybe there's other stuff to be validated too). Currently if the user hasn't touched a field and tries to submit, that field won't be validated.
A simple and flexible solution would be to expose a method which could be called to trigger validation. Maybe that has some overlap with #52.

+1, I needed this functionality yesterday and my quick hack was to blur and focus the input to trigger the validation. Would love to see a built-in solution.

Hi @EmilEriksen - Thanks for the issue and sorry for the delay.
Unfortunately, this isn't possible with where the library stands today. Currently, validation needs access to the DOM element which can only be possible using the change and blur events, both of which are fired upon user interaction.
That said, you might be able to achieve something similar by creating a custom validator that can validate inputs dependently from useFormState and merge the validity of the latter by the custom validation object to get the final result. Here's an example:
/**
 * This custom hook will validate inputs by accessing the underlying DOM node
 * directly using refs
 */
function useFormValidator() {
  const [validity, setValidity] = React.useState({});
  const inputRefs = useRef({});
  const bind = useCallback(input => {
    if (input) {
      inputRefs.current[input.name] = input;
    }
  }, []);
  const validate = () => {
    for (const name in inputRefs.current) {
      setValidity(validityState => ({
        ...validityState,
        [name]: inputRefs.current[name].validity.valid
      }));
    }
  };
  return { bind, validate, validity };
}

function App() {
  const [formState, input] = useFormState();
  const validator = useFormValidator();

  // final validation result
  const validity = { ...validator.validity, ...formState.validity };

  return (
    <>
      <input {...input.text("username")} ref={validator.bind} required />
      <button onClick={validator.validate}>Click me to validate</button>
    </>
  );
}

Here's a working example: https://codesandbox.io/s/0y87pzxv3w
This isn't perfect, of course, and it might not cover all cases but hopefully it can give you an idea that you can expand on. Supporting something like that will cause breaking changes, but it's definitely something I'll keep in mind for future major releases of react-use-form-state.

Note to self: duplicate of #57 #47

validation needs access to the DOM element which can only be possible using the change and blur events

Well... you could pass a ref to every <input>, and then you could get access to them whenever you wanted to.  You'd have to do a little bit of cleverness if you want to let someone else also pass a ref to the input, but I can think of a couple of ways it could be done.

I spent way too much time trying to figure out how the form submit event could be stopped even if some fields were unvisited and invalid. So inspired by the discussion here, hopefully someone finds my solution useful. The trick was decoupling the submit event (for button clicks) from the onSubmit callback and firing the event manually. What I ended up doing was exposing a submit method in a custom hook that

iterates through the input elements, firing the blur event to trigger validation.
set a boolean state variable true (I called it submitRequest). This is needed as we can't read the validity yet.
on the next render, we use an effect hook to check 2 things:

all fields are valid
the submitRequest is set to true.

Provided those criteria are met, we dispatch a submit event for the onSubmit handler as normal. The submitRequest flag is reset to false to prevent multiple renders from firing the submit more than once.
See Code sandbox


Check so Greninja with Battle Bond always are male

Fixes http://www.smogon.com/forums/posts/7299715

Gender is normally silently corrected to that of the template. See https://github.com/Zarel/Pokemon-Showdown/blob/master/data/rulesets.js#L152

Do you mean rather than rejecting the team it should just silently force it to be male?

No, new policy is to reject instead of silently correct...


Reland rustwide and tokio upgrade

The cause of the leak was that Regex::new leaked 2.5 MB of memory on
every build (in parse_rustc_version). Searching around I found
https://github.com/rust-lang/regex/issues/742, which said this was a
regression in thread_local.  Updating thread_local to 1.1.3 fixed the
issue.
For future reference: I debugged the leak as follows.

Build the crate: cargo build
Run the daemon under massif without registry watching: valgrind --tool=massif target/debug/cratesfyi daemon --registry-watcher disabled
Add a whole bunch of crates to the queue: for i in $(seq 1 100); do cargo run -q queue add serde 1.0.$i; done
Stop the daemon with SIGINT when you get tired of waiting (I ran about 30 builds).
Run massif-visualizer on the generated file.

Successor to https://github.com/rust-lang/docs.rs/pull/1264. Fixes https://github.com/rust-lang/docs.rs/issues/1102. Unblocks https://github.com/rust-lang/docs.rs/issues/1303.
This is a WIP because I tested the leaks with an ancient version of the lockfile, not the one in this PR; I need to test again before this merges.

Ok cool, I ran about 80 builds with no spikes.

Code looks good, I'm setting up an overnight test running builds to see if I get any leaks.

I ran 200 builds on the server running in the docker-compose setup, checking the rss usage after each build:
for i in $(seq 1 200); do
  cargo run -- queue add bs58 0.4.0 2>/dev/null
  sleep 180
  ps -C cratesfyi -o rss --no-headers
done

There is what looks like a slight leak, but it might just be heap fragmentation or something. It's the same as what I previously saw when testing e8a6303, I didn't record the full data the same as this, but at that version after 10 builds it was at 69MB and after 100 builds was at 173M, which are right on the line.
Comparatively when testing 48444ef at 10 builds it had reached 109MB and 100 builds it had reached 530MB, so significantly more leakage.


sbcl: make deriv options overridable attributes

Description of changes
This also makes the options available for reading by other derivations which depend on SBCL. This is useful for derivations who want to evaluate differently based on the capabilities of the SBCL derivation they're passed. Eexample: bordeaux-threads depends on a specific feature of SBCL (threads): having the .threadSupport value readable from the derivation at runtime allows bordeaux-thread to set meta.broken = true for an SBCL without thread support.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hmm - I would put the options in passthru - this is how the Emacs package does it for checking "withNativeCompilation".

Hmm - I would put the options in passthru - this is how the Emacs package does it for checking "withNativeCompilation".

Interesting. Any particular reason? Passthru isn't available to the actual derivation in the end which makes sense for non-fundamental types but I'm curious what the motivation is for putting regular flags on passthru. Maybe I'm personally a bit too jaded by the emacs derivation to take much stock in it as prior art 😂 I looked around at other derivations but I have a feeling it's quite haphazard across the board.

It's only my taste :-)
We could make all assertions at the start (kind of like check-type/declare in lisp) - which feels more "organized" - assertions are separate from build logic. For example:
{

...

# Build options
, threadSupport ? (stdenv.hostPlatform.isx86 || "aarch64-linux" == stdenv.hostPlatform.system || "aarch64-darwin" == stdenv.hostPlatform.system)
, linkableRuntime ? stdenv.hostPlatform.isx86
, disableImmobileSpace ? false
, purgeNixReferences ? false
, coreCompression ? true
, markRegionGC ? threadSupport
}:

assert coreCompression -> !purgeNixReferences;
assert markRegionGC -> threadSupport;

let ...

Similarly - build-time env variables inside mkDerivation  are separate from build options. These options can be used to decide on those flags/vars, but themselves are "metadata". Then it's more immediately visible, what is build-internal and what is "exported". (in passthru attrset).

SO perhaps a reason is to keep overrideAttrs for attrs specific to mkDerivation , and use override for customizations on top of that. But it's hard to find the one true convention in nixpkgs (-:

Feels like we want the opposite for these values, right? Definitely trigger a rebuild--that's kinda the point. Fundamentally different derivation.

I think it's for cases with .pkgs style sets, so as not to cause havoc. In the case if it's referenced inside mkDerivation it will re-build correctly.

Feels like we want the opposite for these values, right? Definitely trigger a rebuild--that's kinda the point. Fundamentally different derivation.

I think it's for cases with .pkgs style sets, so as not to cause havoc. In the case if it's referenced inside mkDerivation it will re-build correctly.

That's a totally fair point!
Re the assertions sprinkled throughout: I've kept them close to the point of use so they don't trip people up who want to override them, e.g.:
https://github.com/NixOS/nixpkgs/blob/1acef6e636e4111933dfd0213ee20ffaafe997c7/pkgs/development/compilers/sbcl/default.nix#L86-L93
I thought this would strike a nice balance between failing loud, but leaving the ultimate decision with the user. I like the idea of leaving the user in charge if they insist on using incompatible flags, e.g. to test a build which does in fact support that combination. What do you think?
Re the derivation: I think I see why you prefer passthru. I realize I see derivations as more bespoke and case-by-case, where mkDerivation (and on a lower level stdenv) is just a framework on top of which you build your derivation. I also thought that any value stored as a direct property on the derivation itself (i.e. passed as a env to the builder) would also be available after an import my-derivation.drvPath, which was already abstruse enough but also turns out to be entirely wrong. So there goes that.
I guess all I have to go off of is a "feeling" that it's nice to have the flags which control the build process live directly on the derivation rather than incidentally in an override tacked on to the object which represents the derivation. It's a very weak intuition so I'm happy to go your way!

ah - I see - yes like this the asserts can be overridden out, unlike on top-level - quite nice.

I also thought that any value stored as a direct property on the derivation itself (i.e. passed as a env to the builder) would also be available after an import my-derivation.drvPath

Theoretically one could builtins.readFile x.drvPath and parse it - I don't know about "pure evaluation mode" though. (One might get dark side points for this).
Hmm a little bit out of scope - but regarding the zstd case - for linux we could allow compression + purge by using a static libzstd.a - I don't know about macos.

I guess all I have to go off of is a "feeling" that it's nice to have the flags which control the build process live directly on the derivation

heh, they say one should follow their gut feeling - go for it (-:

@7c6f434c what are your thoughts? Ready to merge?

I am honestly a bit confused that mkDerivation now allows this! But yeah, any other option is prone to forgetting to inherit something…


Drop Carthage and build using Swift Package Manager (close #735)

Issue #735
Dropped Carthage for build
Development and test dependencies are handled using Swift Package Manager instead of Carthage. Carthage is removed altogether, so it's not even possible to install in other apps using Carthage.
In order to do that, I had to deal with the test dependencies that were previously installed using Carthage:

Nocilla was used for mocking HTTP requests (for remote config or to collector). Since the project is abandoned and doesn't support SPM, I had to find a replacement. Ended up with Mocker from WeTransfer, which seems to be actively maintained. The only downside seems to be that it currently doesn't work well on watchOS but hopefully that will be addressed.
IgluClient was used to validate event payloads using schemas. The ObjC library is also no longer maintained and doesn't support SPM. I tried to add SPM, but there is an external dependency in the project for KiteJSONValidator, which is also not actively maintained and doesn't support SPM. Adding support for SPM there proved not easy because it contains resources (JSON schemas) that I couldn't add to there.

Instead of investing more time into getting the Iglu client to work on SPM, I thought that it'd be better to replace it with Micro. I think that is the more modern and scalable approach (doesn't require a separate client for each language) that we use in tracker tests. I'm happy to reconsider this if someone has a different opinion. Created a separate issue to adopt Micro

Removed XCode project files
Since SPM projects don't require an XCode project file, I removed it from the repository to clean up. XCode can work with the project just by opening the folder. If there is a need, one can regenerate the XCode project file using (but this is not recommended):
swift package generate-xcodeproj

Also cleaned up and removed a bunch of other boilerplate files that are no longer necessary.
Improved CI
Previously the CI only ran tests on iOS and built for watchOS. Now it runs tests for iOS, macOS, watchOS and tvOS. Additionally, it runs lint using CocoaPods.

Thanks @AlexBenny!
As we already discussed, I will post on Discourse a question along with alpha 2 to ask which package managers people use and whether they will miss Carthage.
Reintroducing Carthage would mean adding back the XCode project file and maintaining that which is a bit annoying but not such a big deal.


Add Radio and RadioGroup components

This PR adds two new components, along with examples and supporting docs:

RadioGroup
Radio

It is based on RAC RadioGroup and Radio.
RadioGroup is a container element, that provides visible and semantic labelling and description for a group of radio inputs. It also supports validation and error handling, via the FieldError subcomponent. It supports the following props:

label
description
children (expects an array of Radio components)
orientation (defaults to vertical, also accepts horizontal)
defaultValue (sets an uncontrolled default value)
errorMessage
isDisabled (disables the entire radio group)
isReadOnly
isInvalid

Radio is a subcomponent used to populate a list of options inside a RadioGroup. It cannot be used outside a RadioGroup. It supports the following props:

value (required unique identifier, used by RadioGroup for validation and submission)
children (used to set the label text)
isDisabled (disables an individual item)

@ty2k these components rely on 3.1.0 tokens, so I had to bump the dependency in 667eed9 to make things work.

I've made the following changes:

Dependencies

Added @rollup/rollup-linux-x64-gnu to optionalDependencies  to fix this broken build (see https://github.com/npm/cli/issues/4828#top)

Functional component changes

RadioProps gets used and exported directly from React Aria Components f12768c
flexWrap prop added to RadioGroup to allow wrapping with horizontal groups df94906
Add RadioGroupRenderProps type info to render props in RadioGroup e514c1b

Styling changes

Radio cursor styles apply to both the selector and label 02444c1
Flattened nested CSS rules since we are not doing any CSS pre-processing and nesting in plain CSS is still pretty new 474a20c
No animation transition if user has prefer-reduced-motion set 274d084 (we should do this to Switch as well)

Storybook

Add flexWrap argType to meta c254509

Tests

RadioGroup da226fc
Radio 3d97b6d

This should be good to merge @mkernohanbc. Please take a look and make sure you're happy with my changes!

@ty2k I see no issues with any of these changes, merging now!


Access slug from usePageDetails for getLinkToComment

Potentially resolves #152

Nice!! Thank you so much, crossing fingers this fixes that long-standing bug!


Form repeater is not working with select2

I am using form repeater and selct2 together, at start it works perfectly fine, mean when page refresh once I click on add new, slect2 field repeat its self but its layout and everything got changed.

you should reinitiate select2 in show function

Here is an example of how you can get that to work. Note how you need to initiate the Select2 in both the ready and show methods. The initiation within the ready method will ensure that it works for the very first repeater, the initiation within the show method will ensure that it works within the additional repeaters added to the DOM.
In my case, I had to also tell Select2 where to attach additional instances, but your usage may vary.

I am facing problems with select2. When I add a new line with select2 the previous one disappears. This package does not seem to receive updates for a long time, is there any alternative that has solved this problem? Do you still use it?
Thanks

@garbinmarcelo did you manage to solve this? facing the same issue

@garbinmarcelo did you manage to solve this? facing the same issue

Not really, I ended up working on another project in that time, but I would like to know if there is a solution for that.

@garbinmarcelo  i manage to solve my issue by doing this, hope this helps you
i can add multiple items and all will work with the select2 library
$('#repeater').repeater({
	initEmpty: false,
	isFirstItemUndeletable: true,
	show: function () {
		$(this).slideDown();
		$(this).find(".select2").select2();
	},
	hide: function (deleteElement) {
		$(this).slideUp(deleteElement);
	}
});

I did work for me, I got this somewhere from StackOverflow If I remember correctly, but forget the link!
    $(".select2").select2({
        placeholder: "Select Value",
    });

    $('.repeater-button').repeater({
        show: function () {
            $(this).slideDown();
            $('.select2-container').remove();
            $('.select2').select2({
                placeholder: "Select Value",
                allowClear: true
            });
            $('.select2-container').css('width','100%');
        },
        hide: function (remove) {
            if(confirm('Confirm Question')) {
                $(this).slideUp(remove);
            }
        }
    });

I'm having issues about this because everytime I add a new row the name is messed up with square brackets,
ex:
group-b[0][field_name[]][]
then if I add a new row the previous one removes square brackets and becomes group-b[0][field_name][] (as I think it should be) and the new one is messed up: group-b[1][field_name[]][]

Is anyone able to work select2 with form repeater?

it doesn't work with select2 multiple selections.

it is working, you should do this.
$('.m_repeater_section').repeater({
        initEmpty: false,

        defaultValues: {
            'text-input': 'foo'
        },

        show: function() {
            $(this).slideDown();
            $(this).find('.select2').removeClass('select2-hidden-accessible');
            $(this).find('.select2-container').remove();
             $(this).find('.select2').select2();
        },

        hide: function(deleteElement) {
            if(confirm('Are you sure you want to delete this element?')) {
                $(this).slideUp(deleteElement);
            }
        },
       isFirstItemUndeletable: true
    });

$(this).find('.select2').removeClass('select2-hidden-accessible');
$(this).find('.select2-container').remove();
$(this).find('.select2').select2();

Thank You! it's working fine

it is working, you should do this.
$('.m_repeater_section').repeater({
        initEmpty: false,

        defaultValues: {
            'text-input': 'foo'
        },

        show: function() {
            $(this).slideDown();
            $(this).find('.select2').removeClass('select2-hidden-accessible');
            $(this).find('.select2-container').remove();
             $(this).find('.select2').select2();
        },

        hide: function(deleteElement) {
            if(confirm('Are you sure you want to delete this element?')) {
                $(this).slideUp(deleteElement);
            }
        },
       isFirstItemUndeletable: true
    });

Thank You! it's working fine

If anyone is having problems with select2 in the repeater, what happened for me is that when a repeater item was added the select tags would have the same id as the first repeater item. As I would add more items, the previous selects would stop working.
In my case I had two select tags inside each repeater item so I had to iterate through them (you'll see in the code). You can remove the id from the generated select in the new repeater item to fix the issue.
show: function () {
  $(this).slideDown();

  // Edit this selector for your select tags
  $(this).find('select[data-input-field="select-dropdown"]').each(function(index) {
    $(this).removeAttr('id');
    $(this).select2();
  });
},

how to remove search in select2

The solutions work with a normal select input but not with multiple=True ones. For example, if you create select2 input with multiple attribute and repeat them, only the last one will be initialized.

I invested some time trying to find the best way to make Select2 work with jquery-repeater. I was using the solution from @mtariq786 , but I still encountered some issues.
After testing, I came up with the following solution that works for both multiple and single select elements:
Problem:
When adding the new item in the following way, the new item worked, but the existing one lost its Select2 functionality:
$('.select2-container').remove();
$('.select2').select2({
    placeholder: "Select Value",
    allowClear: true
});

Solution:
I removed the id from my select elements and controlled them with a data attribute. To keep the semantic structure, I wrapped the select element inside a label:

  Label
  <select class="form-select" name="name" data-select-type="select2" data-placeholder="Placeholder" aria-label="Label" style="width: 100%;">
    <option></option>
    <option value="1">1</option>
    <option value="2">2</option>
    <option value="3">3</option>
  </select>

And in the JavaScript, I ensured that the Select2 is properly initialized and re-initialized:
$('.repeater-links').repeater({
  ready: function () {
    $('[data-select-type="select2"]').select2();
  },
  show: function () {
    $(this).find('[data-select-type="select2"]').select2();
    $(this).slideDown();
  },
  hide: function (deleteElement) {
    $(this).slideUp(deleteElement);
  },
});

This approach solved my issues with Select2 and jquery-repeater, making both single and multiple select elements work smoothly.


RN stand alone app showing expo icon (like building javascript bundle) before my first screen

Hi, I just detached my RN apps since I need to use native lib. Then, I tried to generate my APK from Android Studio. However, after installing to my phone, my apps shows expo icon (similar with expo building javascript bundle...).  I did not happen before I detached my RN project.

It shows that pict for few secs, before go to my first screen. Is it an issue or I need to do something after I detached my project? (Expo ver: 23.0.4)
Thank you.

Please re-open this issue since I have not got the solution yet


Sync WRK550 With post-MSIgnite Updates

Update:
Main and AI Tour branches will be updated to v0.4 in 2025.
This PR will be revisited at that time to see if it should be discarded or merged.


About submission

I sent my submission of the test set evaluation to<EMAIL_ADDRESS>, but there was no reply.
I do not know whether I sent the wrong email address or other reasons.

Hi. I noticed it fell into spam folder. We will get back you soon with the result!


Bug: 1947774: fix imagePullPolicy to ifNotPresent

This pull request explicitly set the imagePullPolicy to IfNotPresent
fixes  bug

/retest


healthz endpoint

I'm interested in creating a PR for a /healthz endpoint. Would you entertain the idea if I put something together?
Thanks.

why not just use /status/200?

Assuming there are no external dependencies to check (network access for example) a 301 from /healthz to /status/200 could work.


Cannot Download https://www.youtube.com/watch?v=feZluC5JheM

Checklist

[ y] I'm reporting a broken site support issue
[ y] I've verified that I'm running youtube-dl version 2021.12.17
[ y] I've checked that all provided URLs are alive and playable in a browser
[ y] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ]y I've searched the bugtracker for similar bug reports including closed ones
[ y] I've read bugs section in FAQ

Verbose log

PASTE VERBOSE LOG HERE

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.youtube.com/watch?v=feZluC5JheM']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.10.6 (CPython) - Linux-5.15.0-60-generic-x86_64-with-glibc2.35
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] feZluC5JheM: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 815, in wrapper
return func(self, *args, **kwargs)
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 836, in __extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
ie_result = self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 1012, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Description

WRITE DESCRIPTION HERE
Cannot Download by address --> https://www.youtube.com/watch?v=feZluC5JheM

Have you readed
https://github.com/ytdl-org/youtube-dl/issues/31658

[ ]y I've searched the bugtracker for similar bug reports including closed ones

Yet not well: #30839.


Update FFlLib with recent changes from the openfedem project

Most of the changes have no relevance for this project - only to ease future comparison of the code bases

jenkins build this please

jenkins build this please


few issues with 0.23.0 docs

few nitpicks found in latest docs...

section: Deploying the Address Space Controller  >> prerequisites
there is a linewrap in the first code example that introduces a space in the code (not desirable) ...other code examples have an horizontal scroll bar, could be used here

====================
2. search for RoleBinding.yaml
some of the code examples are colored and some are bold... others not, not exactly sure why?
====================
3. search for ifdef
====================
4. differences between
3.7.1. Creating an address space
3.7.2. Creating addresses

section titles
procedure texts
text after the procedure is finished

====================
5. section 4.1. User model
The following is an example user:
====================
6. search for 'Prerequisite'
the 17/17 result doesnt have a bullet point ( the rest do )
when there is 1 prerequesite, sometimes it says 'Prerequisite' and sometimes 'Prerequisites'
====================
7. Users can in EnMasse can be deleted using standard command line tools.
====================
8. search for addressses ( 4 s's in total )
====================
9. Appendix B: REST API Reference >> tags
addresses : Operating on Addresses.
addressspaces : Operate on AddressSpaces <----- operating on ? ( or others can be 'operate on' )
messagingusers : Operating on MessagingUsers.
====================
An address space in address space A might have the same name as an address in address space B.
Im sure this sentence should be...
An address in address space A might have the same name as an address in address space B.

Latest docs (0.24.0) checked and all these issues are fixed, thanks a lot @jenmalloy! closing this issue now


0.8.x: Creation of Buff item no longer works

Creation of Buff item no longer works
Originally posted by @Lavaeolous in https://github.com/Lavaeolous/PF1-StatBlock-Converter-Module/issues/425#issuecomment-846520017

Fixed in 3.3.0


Update firefox-beta-bin to 96.0b5

Checklist

[x] Checked the nixpkgs master branch

[x] Checked the nixpkgs pull requests

Project name
nix search name:

current version: 95.0b3
desired version: 96.0b5
Notify maintainers

maintainers: @taku0 @lovesegfault
Note for maintainers
firefox-devedition-bin needs an update too.
Please tag this issue in your PR.

firefox-bin has been updated to 96.0 in #154354 so this is obsolete now.


Add polygon to python ROIs examples

This updates the Python ROIs example code according to changes in the examples at https://github.com/openmicroscopy/openmicroscopy/pull/4412 (Polygons)
and
https://github.com/openmicroscopy/openmicroscopy/pull/4415 (Masks).
Check for formatting errors etc.
Code changes themselves are checked by the above PRs.

Probably best to wait for the code examples PR above to be merged, so code changes can be updated in the docs too.

@sbesson Can you remove the ON_HOLD label now? Thanks.

Done. Worth integrating my masks changes here as well (assuming they make it in tomorrow)?

@joshmoore Yes, I was just thinking that.

The workflow looks okay but I have not explicitly tested the code.

Code should have been tested in the related PRs.

Thanks @joshmoore for some reason I completely failed to see the descrion, just jumping to the staging docs and the diffs!

Code PRs merged, is this good to merge too @ximenesuk @joshmoore ?

@hflynn I'd not seen the final commit but that looks fine so I'm happy for it to be merged.

Yup, merging, but he change will need to be backported to https://github.com/openmicroscopy/openmicroscopy/pull/4412/files#diff-721941e13150907e2a501f3e5cef6ad3R115 otherwise it'll propagate back to the documentation.

@will-moore leaving you to deal with the backporting Josh mentioned.


Bugfix: archivebox django branch look

Describe the bug
I know that the django branch is a WIP but I would like to be sure there is not a problem on my side, about the look of it. Should it look better than what you see on the screenshot below? If yes, then I can try to find why on my side looks like that. If not, I might be able to help on making it look better with some contribution on my side, if you like.
Screenshots or log output

Software versions

OS:                                  macOS 10.14
ArchiveBox version:        1866da3

Try with archivebox server instead of opening the index file directly.

I think this PR should have fixed it: https://github.com/pirate/ArchiveBox/pull/360
Can you please confirm @walkero-gr ?


Equipment and consumable stats are disabled frequently

Type
Incorrect behavior
Operating System
Windows
OS Version
Windows 10
Bug description
I have noticed that the item stats plugin's Enable consumable stats and Enable equipment stats are often disabled. I have always left these on, but every once in a while, these are turned off. I have not found a pattern to recreate the error on demand, but I have noticed this while doing some ToA recently (as I'm grinding to get a profitable purple 🤞 )
I had noticed this same behavior a couple of months ago (but not at ToA as I recently started doing that, I don't remember where I was running into the issue before) but it was fixed and I didn't see the issue again until kind of recently.
Screenshots or videos
No response
RuneLite version
RuneLite version: 1.9.9
Launcher version: 2.5.0
Logs
client.log
launcher.log

Do you have the "Bank item stats toggle" plugin installed?

I do! Do those plugins not play nicely with each other?

If you don't want to have the overlays toggled while banking, remove that plugin. Per the README of the project, that's literally what it does:

Toggles Item Stats plugins overlays when banking

My bad, didn't see that


CheckStyle Plugin can not show source from the check result from gometalinter

#283

@alecthomas I find the problem about this issue, the detail is described in #283.

I'd welcome a patch to fix this.

No response.


Socket io only works if the app is apk generated

Socket io not working when generating app bundle instead of APK

Socket io not working when generating app bundle instead of APK

use google crashlytics for Analytic why socket.io not working for your app generating


chore: remove more bex and ball from lemma names

Follow-up to #10816.
Remaining places containing such lemmas are

Option.bex_ne_none and Option.ball_ne_none: defined in Lean core
Nat.decidableBallLT and Nat.decidableBallLE: defined in Lean core
bef_def is still used in a number of places and could be renamed

I only audited the first ~150 lemmas mentioning "ball"; too many lemmas named after Metric.ball/openBall/closedBall.

Thank you for the quick review. I have addressed all comments.

Updated again.

Thanks!
bors d=@YaelDillies

in Logic.Basic: this has lemmas like forall_of_ball and conversely, so it's not obvious how to name them

Can you simply replace ball by forall_mem in those names?

I went over all lemmas in Logic.Basic, replacing "bex" by "exists_mem" and "ball" by "forall_mem". Oof.
There are a couple of occurrences of "bef_def"; be my guest to remove them :-)

Do you have an opinion about {BAll,BEx}.imp_{left,right} in Logic.Basic?
I could rename them to Forall/Exists.imp_{left,right} instead.

Do you have an opinion about {BAll,BEx}.imp_{left,right} in Logic.Basic? I could rename them to Forall/Exists.imp_{left,right} instead.

There are also BEx.intro and BEx.elim remaining.

Thanks for the careful comments again; I have addressed them.

Feel free to do any of the remaining three lemmas yourself, if it's faster this way.

Must be gone for the night, but I will if you haven't done them in the next 8-9 hours.

@YaelDillies I just rebased this and fixed the one easy lemma. Do you have energy left to fix the two remaining lemmas?
In any case: thanks for all your help on this PR!


[2.0-wip] Grid Customization

The (@gridColumns * @gridColumnWidth) + (@gridGutterWidth * (@gridColumns - 1)) will not be seen in Firefox 10, as when you click in the textarea, it's blank. Plz find another way to inform people about it of maybe keep it inside upon user click.

This will be going away in the docs—we no longer use @siteWidth and it won't be customizable via static value any longer.


If container throughput not set on create , then defaults to CosmosDbThroughput.minimum

I have a database  with a fixed throughput of 1000 RU/s
I wish to add containers as in the Azure portal, where you just don't tick the checkbox for Provisioning dedicated throughput for the container.
This way all containers in the database share the throughput provisioned for the Database.
If I create the container as follows:
final deviceCollection = await database.containers.openOrCreate(
      'device',
      partitionKey: partitionKey,
      throughput: CosmosDbThroughput.autoScale(1000),
      indexingPolicy: indexingPolicy,
    );

it provisions 1000RU/s just for that container, thus exceding my 1000 RU/s.
If I set to minimun:
 throughput: CosmosDbThroughput.minimum,
it obviously sets it to a minimum of 400 RU's
If I leave off the throughput parameter, then it also defaults to 400RU's
How do I NOT provision dedicated throughput for this container? as in the image below:

Indeed the code uses a default value for throughput when you don't provide one. I'll try and remove it so it inherits from the parent database throughput, I'll keep you posted.

Thanks for your contribution, I've added a test case and prepared pubspec.yaml before official release.

Version 2.2.0 published! Thanks for your help.

Thx a lot. I had time to test today, and it solves the problem. Much appreciated.


Added dist-query option to riak-admin

Opted instead to use the set command to set the cuttlefish setting via riak-admin.


Do not modify MANIFEST.in on install

What does this PR do?
Part of https://github.com/Lightning-AI/lightning/issues/15474
Each package keeps it's own MANIFEST.in
Does your PR introduce any breaking changes? If yes, please list them.
None
cc @carmocca @akihironitta @borda

Failures will be avoided by 15584

Now blocked by https://github.com/Lightning-AI/lightning/pull/15558

Now blocked by #15558

resolved

Something here is making e2e examples hang. Haven't found the cause...

Just curious, why this had to be reverted? :thinking:


Support for custom repo (e.g. archzfs)?

Hello,
Thanks for the project! I have multiple Arch installs on my LAN and a single, very slow, internet connection, so I'm looking into options for package caching. A project in rust always catches my eye.
Is there support for custom repos like archzfs?
In contrast to core / extra / community, adding the flexo url to my archzfs section of pacman.conf seems not to work, resulting in:
error: failed retrieving file 'archzfs.db' from localhost:7878 : The requested URL returned error: 404

[archzfs]
Server = http://localhost:7878/$repo/os/$arch
Server = http://archzfs.com/$repo/$arch
...

I tried adding http://archzfs.com/ to mirrors_predefined in flexo.toml with no change in behavior.
I see a few other issues mentioning zfs but nothing on the archzfs repo or adding custom repos.
Is using flexo to cache packages from custom repos possible?

Hi,
thanks for your feedback!
custom repos are currently not supported, but I'm optimistic that this can be implemented without much effort. I'll take a closer look this weekend.

Hi,
thanks for your feedback!
custom repos are currently not supported, but I'm optimistic that this can be implemented without much effort. I'll take a closer look this weekend.

Thanks for your time and attention!

Awesome, thank you!

You're welcome. Feel free to comment if something doesn't work as expected.

Seems to be working great. Thanks again.


NOISSUE - Add socket pool to Verne plugin

Signed-off-by: drasko<EMAIL_ADDRESS>Pull request title should be MF-XXX - description or NOISSUE - description where XXX is ID of issue that this PR relate to.
Please review the CONTRIBUTING.md file for detailed contributing guidelines.
What does this do?
Add socket pool to speed up HTTP req towards Things service during authorization.
Which issue(s) does this PR fix/relate to?
Put here Resolves #XXX to auto-close the issue that your PR fixes (if such)
List any changes that modify/break current functionality
Have you included tests for your changes?
Did you document any new/modified functionality?
Notes

Codecov Report

Merging #830 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #830   +/-   ##
=======================================
  Coverage   85.57%   85.57%
=======================================
  Files          72       72
  Lines        4701     4701
=======================================
  Hits         4023     4023
  Misses        442      442
  Partials      236      236

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2d1347e...cb2897b. Read the comment docs.


Refactor as NPM module, using keras-model-viewer as dependency

Closed by https://github.com/neurals-ro/keras-model-editor/pull/2


Redirection with +layout.server.js [server side] isn't working

Describe the bug
I have some old url parameters of NextJs, and I have recently unpdated my app to SvelteKit, and it's in production. And I wanted to redirect my old urls to new ones and tried the instruction according to https://kit.svelte.dev/docs/load#redirects about tweaking +layout.server.js and using throw.
Reproduction
The below code isn't working, throw is just logging some useless stuff.
    import { redirect } from "@sveltejs/kit";

    export function load({ url }) {
      if (url.pathname === '/old-url-param') {
        throw redirect(301, '/new-url-param');
      } else if (url.pathname === '/old-url-param-2') {
        throw redirect(301, '/new-url-param-2');
      }
    }

Logs
{
  has: [ 1, 31 ],
  keys: [
    { open: '\x1B[1m', close: '\x1B[22m', rgx: /\x1b\[22m/g },
    { open: '\x1B[31m', close: '\x1B[39m', rgx: /\x1b\[39m/g }
  ],
  reset: [Function: bound ],
  bold: [Function: bound ],
  dim: [Function: bound ],
  italic: [Function: bound ],
  underline: [Function: bound ],
  inverse: [Function: bound ],
  hidden: [Function: bound ],
  strikethrough: [Function: bound ],
  black: [Function: bound ],
  red: [Function: bound ],
  green: [Function: bound ],
  yellow: [Function: bound ],
  blue: [Function: bound ],
  magenta: [Function: bound ],
  cyan: [Function: bound ],
  white: [Function: bound ],
  gray: [Function: bound ],
  grey: [Function: bound ],
  bgBlack: [Function: bound ],
  bgRed: [Function: bound ],
  bgGreen: [Function: bound ],
  bgYellow: [Function: bound ],
  bgBlue: [Function: bound ],
  bgMagenta: [Function: bound ],
  bgCyan: [Function: bound ],
  bgWhite: [Function: bound ]
}
Redirecting /generator/about-us-generator
{
  has: [ 1, 31 ],
  keys: [
    { open: '\x1B[1m', close: '\x1B[22m', rgx: /\x1b\[22m/g },
    { open: '\x1B[31m', close: '\x1B[39m', rgx: /\x1b\[39m/g }
  ],
  reset: [Function: bound ],
  bold: [Function: bound ],
  dim: [Function: bound ],
  italic: [Function: bound ],
  underline: [Function: bound ],
  inverse: [Function: bound ],
  hidden: [Function: bound ],
  strikethrough: [Function: bound ],
  black: [Function: bound ],
  red: [Function: bound ],
  green: [Function: bound ],
  yellow: [Function: bound ],
  blue: [Function: bound ],
  magenta: [Function: bound ],
  cyan: [Function: bound ],
  white: [Function: bound ],
  gray: [Function: bound ],
  grey: [Function: bound ],
  bgBlack: [Function: bound ],
  bgRed: [Function: bound ],
  bgGreen: [Function: bound ],
  bgYellow: [Function: bound ],
  bgBlue: [Function: bound ],
  bgMagenta: [Function: bound ],
  bgCyan: [Function: bound ],
  bgWhite: [Function: bound ]
}

System Info
System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
    Memory: 593.53 MB / 9.60 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.17.0 - /usr/local/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 8.15.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 105.0.5195.52
    Firefox: 104.0

Severity
blocking all usage of SvelteKit
Additional Information
Just lemme know how can I redirect from server side within +layout.js or +layout.server.js or something equivalent.

Experiencing the same error https://github.com/david-plugge/sveltekit-redirect-issue

Experiencing the same error https://github.com/david-plugge/sveltekit-redirect-issue

Have you solved it?

No, but if you only need the redirect on direct requests you can do it like this

While that totally makes sense i don´t think the error logs should look like that. It seems like an instance of kleur is printed to the console?

@david-plugge for me the solution given by @dummdidumm worked. Thanks to you both.


[DOC-3206] Update SMP patch release description

Update SMP patch release description
For reviewers, a preview is available.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


DIF PE handler should not determine whether "schema.uri" is type or context based on "#"

As I already mentioned in https://github.com/hyperledger/aries-cloudagent-python/pull/1125#discussion_r630778201 it is wrong to assume the schema.uri in PE is an @type if it contains a #.
Take a look at this playground: https://tinyurl.com/ye9whcca
the expanded types result in:
    "@type": [
  	  "https://www.w3.org/2018/credentials#VerifiableCredential",
      "http://schema.org/Person"
    ]

https://github.com/hyperledger/aries-cloudagent-python/blob/319a2ff30d9ddd4a9fdb4b3ab69d1946c110c21b/aries_cloudagent/protocols/present_proof/v2_0/formats/dif/handler.py#L201-L204
@shaangill025

I thought maybe we can use some of the advanced WQL syntax to include an OR statement:
https://hyperledger-indy.readthedocs.io/projects/sdk/en/latest/docs/design/011-wallet-query-language/README.html
According to the docs something like this should be possible:
{
 $or: [
	  {
	     "type:https://example.com#Something": "1"
	  },
	  {
	  	"schm://example.com#Something": "1"
	  }
 ]
}

@andrewwhitehead does Askar provide the same WQL as indy?

Ok, search_credentials in storage.vc_holder.in_memory has a tag_query parameter [tag filter cluase], I am not sure if this can be used for passing WQL query dict.

Yes, Askar supports the same WQL as well as "$exist": ["key1", "key2"]


refactor: run storage_client_mock_samples without scripts

Fixes #3673

This change is

google/cloud/storage/examples/storage_client_mock_samples.cc, line 28 at r2 (raw file):
Previously, mr-salty (Todd Derr) wrote…
nit: we've been avoiding the using since this is only used in one place.

Ack, but this file uses it 5 times.  The functions have a different form because they are supposed to show you how to initialize gcs::Client

google/cloud/storage/examples/storage_client_mock_samples.cc, line 28 at r2 (raw file):
Previously, coryan (Carlos O'Ryan) wrote…
Ack, but this file uses it 5 times.  The functions have a different form because they are supposed to show you how to initialize gcs::Client

ha, i shouldn't do reviews when I first get up I guess ;)
in that case, I think we should fully qualify it (::google...)


Question: Why is jest a dependency and not a dev dependency?

Since there's no template for questions, opening this as a feature request.
Current Behavior
jest is added a dependency which means all consumers of tsdx install it and thus get security alerts for test tooling used for tsdx development.
Desired Behavior
Only packages used by jest during runtime are added to dependencies so that consumers of tsdx are not impacted by security issues lying in tsdx dev tooling.
Suggested Solution
Only packages used by jest during runtime are added to dependencies.
Who does this impact? Who is this for?
All consumers of tsdx
Additional context
Case and point is the node-notifier CVE which has been patched within tsdx using yarn's resolutions but leaves all other package manager users out in the cold.

I'm pretty sure it belongs there. Jest is a part of the final build and runtime. It's abstracted away in the tsdx test script.

Fair. Do I understand correctly that in this case all tsdx users are then stuck with an open vulnerability until tsdx upgrades jest?

I've managed to get past it with yarn resolutions but for the most part yes. Whether or not TSDX will be maintained going forward is also an open question.

Yupp, that's my worry as well. I think it's time to rip this out as a dependency from our projects.


Add ability to filter components that have Status set to NR

See also https://github.com/nexB/aboutcode-manager/issues/116
If a component has the Status set to NR (Not Reporting), provide the ability to filter these components to not show in the Node View tree.

@majurg When you get a chance can you test this? This iteration has the ability to hide nodes based on status. I anticipate there will be future enhancement issues. One in particular is:

Show child nodes that should be visible even if ancestor nodes are hidden.

@jdaguil Just took some time to test this, here are some thoughts:

Marking nodes as NR does not make them disappear from the node view when one expands its ancestor node, it simply turns the node white (not sure if this was the intent or not).

Marking a child node "Needs attention" (or anything NOT NR) keeps the child node visible even when its ancestor is marked NR

@majurg do the behaviors you described above still occur when checking the status you would like to hide? For example in the gif below, the NR nodes are hidden when selected in the filter.

@jdaguil Ah good point I did not catch that. After following your directions:

Marking nodes NR DOES make them disappear from the node view when the correct check-box is selected.

Marking a child node "Needs attention" (or anything not NR) DOES NOT keep the child node visible when an ancestor is marked NR

An additional comment: maybe consider changing the Hide Nodes dropdown to Node Visibility or something like that.
For me, checkboxes signify something is selected and visible, while an un-checked box indicates to me that the particular checkbox item/category is not visible.

@majurg thanks for testing and feedback! I've switched the behavior to show nodes when checked and hide nodes when unchecked. For:

Marking a child node "Needs attention" (or anything not NR) DOES NOT keep the child node visible when an ancestor is marked NR

This is a little more complicated to resolve because it requires knowing what every child is doing which will require a db call. So I was planning to add a separate enhancement issue for that so the overall feature wouldn't be held up. Is that ok?

@jdaguil Yes, a separate issue is a good idea. The changes look great so far in any case.

thanks @majurg!


Added delete operation

Hi Harald,
I implemented deleting data from the cache. It's all fire-and-forget so there's no async. I still have to update the Sample projects, but the functionality and tests are done. Please take a look and let me know if there's anything I should change.
Great library by the way.

I've added the additions to the Sample project.

Thanks! I'll have a look at it later today.

I had forgotten all about the pattern matching or Redis PubSub, so two channels are perfectly fine, but we could get away with one subcription to redis.  http://redis.io/topics/pubsub.

That is a good point about preserving message order.
My initial aversion to adding a new property to the CacheUpdateNotificationArgs is that it could break backwards/forwards compatibility if you did a staged rollout, though I did not test it and that is not a problem that I have.
I can make a branch which uses a single channel and submit it as a separate pull request. We can compare the two and see which is better.

I'm not sure I understand your pattern matching comment. I think you mean to say in RedisSubscriber we subscribe to "cache*" and in the handler call CacheUpdated() or CacheDeleted() based off the channel name. Thus, there would still be 2 publishing channels, but only a single subscribing channel.
Reading the PubSubOrder doc from StackExchange.Redis I think there might not be a message-ordering problem. It discusses sequential or parallel message processing from the same connection, so it sounds like DoubleCache's ConnectionMultiplexer will receive, and process, the messages in the order that Redis sends them regardless of if it's one channel or two.

Yes, flag is not an option. Should have seen that myself, had message version problems a few months ago.
On the single/vs double subscriber you got my thinking. As I read the StackExchange and Redis documentation, I belive messages will be ordered from Redis, but the StackExchange client by default will not wait for the completion of the Action handler passed to the Subscribe method. I.e. the "order" or completion of the CacheUpdated method in RedisSubscriber.cs will not be guaranteed. This leaves me with two questions.

Is message ordering important when dealing with cache updates?
If we have two channels for publishing but one subscription for

I think that message ordering is important, as you may have cached data that is dependent on other data that might also be cached, eg: a playlist will have songs.

From reading the StackExchange.Redis sources I'm 99% sure that message ordering is per-connection, not per-subscriber, and done serially. I will do a couple tests tonight to make sure

I wrote this test to see whether separate channels were processed in-order. I tried massaging a few things, like making subscription and publishing async or not, changing the sleep time, etc, and they all were done in-order.
[Fact]
public void Subscribe_MessagesProcessedInOrder()
{
    var strings = new List<string>();
    var subscriber = _fixture.ConnectionMultiplexer.GetSubscriber();

    subscriber.Subscribe("Test1", (channel, msg) => { Thread.Sleep(1000); strings.Add("Test1"); });
    subscriber.Subscribe("Test2", (channel, msg) => strings.Add("Test2"));

    subscriber.PublishAsync("Test1", "");
    subscriber.PublishAsync("Test2", "");
    subscriber.PublishAsync("Test1", "");
    subscriber.PublishAsync("Test2", "");
    subscriber.PublishAsync("Test2", "");
    subscriber.PublishAsync("Test1", "");

    Thread.Sleep(4000);

    strings.ShouldBe(new[]{ "Test1", "Test2", "Test1", "Test2", "Test2", "Test1"});
}

If I add the line _fixture.ConnectionMultiplexer.PreserveAsyncOrder = false; then strings has all the "Test2"s first, followed by the "Test1"s. I get the same result if I create a second ConnectionMultiplexer and subscribe to the "Test2" channel using the second muxer.

@cbigsby thank you so much for your contribution.


Unknown attribute PathIsDir

Looks like Will's SConstruct changes does have a small fault:
AttributeError: '_PathVariableClass' object has no attribute 'PathisDir':
  File "C:\Users\basti\Development\My tutorials\gdnative_cpp_example\godot-cpp\SConstruct", line 34:
    opts.Add(PathVariable('headers_dir', 'Path to the directory containing Godot headers', 'godot_headers', PathVariable.PathisDir))

@willnationsdev  :)
Personally seeing this is now a submodule I would say, get rid of it :)

Ok, that one is a case error, its PathIsDir with capital I.
After fixing that I get:
AttributeError: 'builtin_function_or_method' object has no attribute 'UnknownVariables':
  File "C:\Users\basti\Development\My tutorials\gdnative_cpp_example\godot-cpp\SConstruct", line 39:
    unknown = vars.UnknownVariables()

And that is just vars.UnknownVariables should be opts.UnknownVariables
Now its just not treating custom_api_file as an optional parameter but a mandatory one..

Ok fixed, it all, PR coming

Lol, wow. Looks like I missed the party. I hadn't quite gotten a chance to test the changes yet, so I'm sorry about that.

That's why we help each other out :)


Web Interface: Improve Jobs page

"The refresh in the jobs page (the summary of the validation done) of the web interface version is annoying because reloads the page every time moving the content up and down"

Fixed in v0.5.5


Excessive lags for AU and NZ data

There's some sort of bucket boundary issue which means AU and NZ data doesn't get processed promptly.
In the UK evening, average lag is low and a handful of solutions are > 6h
in the UK morning, average lag is larger and as many as 60% of stations are <> 6 hours. However, these are all Australasian stations so i am reasonably sure its something to with the buckets. I suspect the final bucket end-time is not correct.

Fixed by adding one to the buckets, so that there's definitely a bucket covering the timeperiod from 12:00 to the latest time of any avaialble data.


Fix update rust vulnerabilities no longer work

Refer

#73
https://github.com/RustSec/advisory-db/issues/414

Feel free to work on it if there are any issues.


cmake nuttx copy with rsync

Tested on linux and windows.
@davids5 if you wanted to improve the incremental nuttx build experience from here you could remove --delete from rsync and add nuttx distclean to the clean target. You'll need to figure out how to make nuttx changes trigger the copy.

@dagar Awesome!

Can we merge this?

@davids5 do you want to cherry-pick this into the nuttx update and I'll close this PR?

@dagar I will pick it up when I have a chance this week.


Some Ideas about improving the workflow/Scalability Enhancements

I'm a huge fan of this plugin and I feel confident saying it is by far the best one available for Godot and I have few suggestions that could potentially improve the user experience and make the plugin scalable and flexible to fit any type of scenario you may come across.
**Suggestion 1 : ** Make titles shared between dialogue files (.tscn files)
Basically the ability to call titles from other dialogue files. This is helpful for couple of reasons,

It will keep the project more organized.
Remove Repetitive dialogues .
You can make a series of events that can be called in other dialogues, In my experience, On of the strength of this plugin is not only to easily write dialogues but It's ability to call functions through dialogues makes it super helpful at making scriptable events for any scenario you may come across.  Ex : An event that changes the room the player is in with some dialogue in the middle.

**Suggestion 2 : ** Title blocks should not stop upong meeting a new title
I can understand why blocks would end upon meeting a new title but nesting titles will make you able to save a lot of effort and time.
So each title should end with an '=> END' if you truly want it to end
This will be explained in the Suggestion 3 example as they go together
**Suggestion 3 : **  Title blocks can execute as functions.

You can add '()' after a title name to make it jump back to where it was called from after ending.
Just like in renpy when you call a title block, uporn reaching an END it should jump back to where it was called from, then continue the dialogue as you would normally do. it's like executing a function.
Example (This example is written with Suggestions 1 and 2 in mind):

~ talk_to_mia
=> fade_screen_in() [This could be stored in another helper file because it's repetitive]
do actor_join("mc", "left")
do actor_join("mia", "right")
=> greeting_mia()
~ mia_options
- Video games
	=> ask_about_video_games
- Leave
mc : Okay then...I'll see you later...
=> fade_screen_out() [This could be stored in another helper file because it's repetitive]
=> END

~ greeting_mia
mc : Hi, Mia, How is your day going?
if good_mood
	mia : My day has been great so far
	mc : That's awesome
else
	mia : I was doing just fine until you showed up
	mc : Oh....
=> END

~ ask_about_video_games
mc : Is the challenge still up?
if good_mood
	mia : Ofcourse, 50 bucks if you win
	start_playing_video_games()
	=> END
else
	mia : I don't want to play right now!
	=> mia_options

Anyway these are all just Suggestions based on my own experience with the plugin while using it on somewhat of a long game and most of the enhancements are inspired from renpy workflow.
I know that they can bee too much work but maybe Nathan can consider them for the future of the plugin.

Suggestion 1 is something I've been thinking about for version 2 (Godot 4 is going to mean a lot of changes so I'm saving the bigger stuff for when its going to be a lot of work anyhow). Once I figure out a nice way for this to work robustly I'll start prototyping something up.
Suggestion 2 is probably something I can add already (behind a compiler setting).
For Suggestion 3 I'd probably prefer a syntax like =>< title so that it kind of suggests returning there after it's done. Implementing this might be a little fiddly but it is probably something I can do without waiting for v2.

I've added support for passing through titles as a compiler setting and added =>< syntax for jumping to titles and returning after.
I've moved suggestion 1 into issue #57 so that I can close this one.


[bug] Unmaximize window by double clicking data-tauri-drag-region does not resize correctly

Describe the bug
I have a window with "decorations": false set. When double-clicking an element with the data-tauri-drag-region attribute to restore a maximized Tauri window, the window state changes to "unmaximized," but the size and position of the window remain unchanged. This behavior is unexpected
Running window.unmaximize works as expected. So does dragging the data-tauri-drag-region window from maximized state.
Reproduction
Create a Tauri application with a window that has an element marked as data-tauri-drag-region.
Maximize the window any way you want
Double-click the data-tauri-drag-region element to restore the window.
Expected behavior
The window should return to its pre-maximized size and position.
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.26100 x86_64 (X64)
    ✔ WebView2: 131.0.2903.86
    ✔ MSVC:
        - Visual Studio Build Tools 2019
        - Visual Studio Professional 2022
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 22.2.0
    - npm: 10.9.1

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.2
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.1.1
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-dialog 🦀: 2.2.0
    - @tauri-apps/plugin-dialog : 2.2.0
    - tauri-plugin-shell 🦀: 2.2.0
    - @tauri-apps/plugin-shell : 2.2.0
    - tauri-plugin-updater 🦀: 2.2.0
    - @tauri-apps/plugin-updater : 2.2.0 (outdated, latest: 2.3.0)
    - tauri-plugin-fs 🦀: 2.2.0
    - @tauri-apps/plugin-fs : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:5173/
    - framework: React
    - bundler: Vite

Stack trace
No response
Additional context
No response

Also double clicking to maximize behaves badly directly after dragging the window from maximized state.
It seems the double click is not registered the first time. Sometimes you need multiple double clicks to maximize it again.


Add support for SQLite, expose BaseDatabase constructor to outside packages

I initially tested this with HikariPooledDatabase and turns out it's not working if you use BaseDatabase.
I can look into that later


florence-2-vision Application Crash on IGX with qt_app.py

Description
I tried to follow the tutorial, with the florence-2-vision example. Knowing that the full QT UI app is not yet supported for iGPU. But I need to use UI in my app, and I perfer PySide.
I'm just wondering how to run the florence-2-vision example on IGX. Anyone tried it before?
Hardware Discription

Hardware: IGX Developer Kit
Software: IGX-SW 1.0 Production Release

Steps to Reproduce
Step 1 - clone the repo
git clone https://github.com/nvidia-holoscan/holohub.git
cd holohub

Step 2 - switch branch
git fetch --tags
git checkout -b v2.4.0 tags/holoscan-sdk-2.4.0

Step 3 - modify code
sed -i '/RUN MAX_JOBS=4 python3 -m pip install --no-cache-dir --no-build-isolation flash-attn/s/^/# /' ./applications/florence-2-vision/Dockerfile
sed -i 's/v2.3.0/v2.4.0/g' ./dev_container

Step 4 - build container
./dev_container build --docker_file ./applications/florence-2-vision/Dockerfile

Step 5 - launch container
./dev_container launch

Step 6 - build application
./run build florence-2-vision

Step 7 - launch application
./run launch florence-2-vision python

Output
A GUI window pop up for seconds and the app crash, with log below:
smartsurgery@smartsurgery-igx:~$ ./run launch florence-2-vision python
Run environment: export PYTHONPATH=${PYTHONPATH}:/../../../python/lib:/workspace/holohub/build/florence-2-vision/python/lib:/workspace/holohub && export HOLOHUB_DATA_PATH=/workspace/holohub/data && export HOLOSCAN_INPUT_PATH=/opt/nvidia/holoscan/data
Run workdir: cd /workspace/holohub/build/florence-2-vision
Run command: python3 /workspace/holohub/applications/florence-2-vision/qt_app.py
Run command args:
[command] export PYTHONPATH=${PYTHONPATH}:/../../../python/lib:/workspace/holohub/build/florence-2-vision/python/lib:/workspace/holohub && export HOLOHUB_DATA_PATH=/workspace/holohub/data && export HOLOSCAN_INPUT_PATH=/opt/nvidia/holoscan/data
[command] cd /workspace/holohub/build/florence-2-vision
[command] python3 /workspace/holohub/applications/florence-2-vision/qt_app.py
/usr/local/lib/python3.10/dist-packages/torchvision/io/image.py:13: UserWarning: Failed to load image Python extension: '/usr/local/lib/python3.10/dist-packages/torchvision/image.so: undefined symbol: _ZN5torch3jit17parseSchemaOrNameERKSs'If you don't plan on using image functionality from torchvision.io, you can ignore this warning. Otherwise, there might be something wrong with your environment. Did you have libjpeg or libpng installed before building torchvision from source?
  warn(
[info] [fragment.cpp:586] Loading extensions from configs...
[info] [gxf_executor.cpp:249] Creating context
/workspace/holohub/applications/florence-2-vision/qt_app.py:114: DeprecationWarning: 'exec_' will be removed in the future. Use 'exec' instead.
  sys.exit(app.exec_())
[info] [gxf_executor.cpp:1971] Activating Graph...
[info] [gxf_executor.cpp:2003] Running Graph...
[info] [gxf_executor.cpp:2005] Waiting for completion...
2024-09-12 03:18:07.092 INFO  gxf/std/greedy_scheduler.cpp@191: Scheduling 5 entities
Opening in BLOCKING MODE
Fatal Python error: _PyGILState_NoteThreadState: Couldn't create autoTSSkey mapping
Python runtime state: initialized

Thread 0x0000ffff747df120 (most recent call first):
  File "/workspace/holohub/applications/florence-2-vision/qt_app.py", line 32 in run

Thread 0x0000ffff8cb9b6c0 (most recent call first):
  File "/workspace/holohub/applications/florence-2-vision/qt_app.py", line 114 in <module>
./run: line 83:   425 Aborted                 (core dumped) python3 /workspace/holohub/applications/florence-2-vision/qt_app.py
[command] export PYTHONPATH=/opt/nvidia/holoscan/python/lib:/workspace/holohub/benchmarks/holoscan_flow_benchmarking && export HOLOHUB_DATA_PATH="" && export HOLOSCAN_INPUT_PATH="/opt/nvidia/holoscan/data"

Thanks for the report @Smart-Surgery-Eason. Can you confirm that you are running on IGX iGPU? We have seen the same issue on AGX (Jetson) and will look into it.

@Smart-Surgery-Eason, I was investigating this issue and found that this might be related to a v4l2 issue.  On your IGX, please run the following commands and then try running the florence-2-vision application again.
cd /usr/lib/aarch64-linux-gnu/
ls -l libv4l2.so.0.0.999999
sudo rm libv4l2.so.0.0.999999
sudo ln -s libv4l2.so.<IP_ADDRESS>  libv4l2.so.0.0.999999


Vocal tract length perturbation

Implemented VLTP as introduced in http://www.cs.toronto.edu/~hinton/absps/perturb.pdf. Adopted from the numpy code here: https://github.com/makcedward/nlpaug/blob/master/nlpaug/model/audio/vtlp.py
Additional notes:

Only supports single channel for now
At the moment, the entire batch will use one (randomized) warp factor
Added a sanity test case

Fixes #115

Thanks for the pull request :) I'll find time to review this

I added VTLP to the demo script and added a speech example there:
https://github.com/akashrajkn/torch-audiomentations/pull/1
I listened to the outputs, and it very much resembles a band stop filter. Is that what you intended? I've attached the sounds in this zip:
vtlp_demo_output.zip
And I have another question: is this a different technique? https://www.isca-speech.org/archive/pdfs/interspeech_2019/kim19_interspeech.pdf

I'm trying to learn about what Vocal Tract Length Perturbation is. Reading the paper, I get the idea that it's about frequency warping

For VTLP, we generate a random warp factor α for each utterance, and warp the freqency axis, such that a frequency f is mapped to a new frequency f ′

But I don't see frequencies getting re-mapped in the spectrogram gif I posted above
I also found this video online:
https://www.youtube.com/watch?v=vCDnfUM6gn8
Could you try to enlighten me? Do you have some reference examples of what VTLP should sound like? Am I missing something, or is there a bug in your implementation?

I understand that this transform does not support stereo/multichannel audio yet. Is that right?

[ ] That is right. I will modify it to support stereo audio

Is that the case here, or is it enough to just use the sample_rate you get from forward calls?

[ ] You are right, it is not required in the init function. I'll change it accordingly

And I have another question: is this a different technique? https://www.isca-speech.org/archive/pdfs/interspeech_2019/kim19_interspeech.pdf

I wasn't aware of this paper, I will read it and get back to you

Do you have some reference examples of what VTLP should sound like?

[ ] I postponed adding tests in this PR. I will add some reference examples

Am I missing something, or is there a bug in your implementation?

I think maybe there is an issue with my implementation. I will check it out and comment here (probably on the weekend)

Closing for inactivity. Feel free to suggest a reopen later if the work gets picked up again


Problems with "last update" time

Version of mod: latest (v0.5.1)
Last update time at "detail" layout and sidebar show in UTC+0 time, which is very inconvenient for understanding time.
Example, last update time of the newly saved item and current time:

But after restart NeosVr, last update time converts to local, and it's making problems with sorting by update time.
Example, folder contains item saved at past open of NeosVr (at item update time show in local time). I save in this folder new item and update time shows as UTC time:

Thank you for your report, it fixed in v0.5.2.


Switch badge to travis-ci.com

JIRA Ticket: none
What does this Pull Request do?
Changes badge URL in README
Interested parties
@fcrepo4/committers

<bump>


TEXTBOOK TRADE

the textbook trade button on the header doesnt have any subtitle when you scroll over it. For now, the subtitle could just be NEW

i meant * NEW * without the spaces, but it made that italics lol


Add AsRef<[usize]> and AsMut<[usize]> bounds to Dimension trait

This provides a simple, public way to convert a dimension to a slice. (Before, the only way visible in the docs to do this was dim.as_array_view().as_slice() or dim.as_array_view_mut().as_slice_mut().)

Makes me uneasy. Should it be public that the dimensions are all convertible to slices?

Should it be public that the dimensions are all convertible to slices?

I thought about this and couldn't come up with a good justification why not. I don't anticipate this ever not being true in the future, and it's useful today for users to be able to convert to slices.
Addionally, we currently provide .as_array_view() and .as_array_view_mut(), which already reveal that the dimension types are represented linearly in memory (possibly with a stride other than 1). I don't see any use for non-1 strides in the dimension representation, and even if there is a use in the future, dimension representations are small enough that converting to an [usize; N]/IxDynImpl will be cheap anyway.

I don't think we should do this, let's look at reworking Dimension first.

Okay.