Steam: Borderlands 2 crashes when trying to download hotfix

Issue description
Before entering the game it tries to download hotfix data, and crashes. I think this is it https://wiki.archlinux.org/index.php/Steam/Game-specific_troubleshooting#Logging_into_SHiFT but solutions from there doesn't work. Game works fine if launch it in offline mode
Steps to reproduce
nix-env -i steam
Launch steam, log in, download borderlands 2 and launch it
Technical details

System: NixOS: 17.03.1082.4aab5c5798 (Gorilla)
Nix version: nix-env (Nix) 1.11.8
Nixpkgs version: 17.03.1082.4aab5c5798

steam logs
Running Steam on nixos 17.03.1082.4aab5c5798 64-bit
STEAM_RUNTIME has been set by the user to: /steamrt
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Fontconfig error: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig error: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig warning: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)
Installing breakpad exception handler for appid(steam)/version(1493162727)

** (steam:2794): WARNING **: Unknown device type 14

** (steam:2794): WARNING **: Could not create object for /org/freedesktop/NetworkManager/Devices/0: unknown object type

** (steam:2794): WARNING **: Ignoring invalid property 'secondaries'

** (steam:2794): WARNING **: Ignoring invalid property 'route-data'

** (steam:2794): WARNING **: Ignoring invalid property 'address-data'

** (steam:2794): WARNING **: Ignoring invalid property 'route-data'

** (steam:2794): WARNING **: Ignoring invalid property 'address-data'

** (steam:2794): WARNING **: Ignoring invalid property 'secondaries'

** (steam:2794): WARNING **: Ignoring invalid property 'autoconnect-priority'

** (steam:2794): WARNING **: Ignoring invalid property 'route-data'

** (steam:2794): WARNING **: Ignoring invalid property 'address-data'

** (steam:2794): WARNING **: Ignoring invalid property 'route-data'

** (steam:2794): WARNING **: Ignoring invalid property 'address-data'

** (steam:2794): WARNING **: Ignoring invalid property 'secondaries'

** (steam:2794): WARNING **: Ignoring invalid property 'route-data'

** (steam:2794): WARNING **: Ignoring invalid property 'address-data'

** (steam:2794): WARNING **: Ignoring invalid property 'route-data'

** (steam:2794): WARNING **: Ignoring invalid property 'address-data'

** (steam:2794): WARNING **: Ignoring invalid property 'secondaries'

** (steam:2794): WARNING **: Ignoring invalid property 'autoconnect-priority'

** (steam:2794): WARNING **: Ignoring invalid property 'route-data'

** (steam:2794): WARNING **: Ignoring invalid property 'address-data'

** (steam:2794): WARNING **: Ignoring invalid property 'route-data'

** (steam:2794): WARNING **: Ignoring invalid property 'address-data'
Installing breakpad exception handler for appid(steam)/version(1493162727)
Generating new string page texture 2: 48x256, total string texture memory is 49.15 KB
Generating new string page texture 3: 256x256, total string texture memory is 311.30 KB
Installing breakpad exception handler for appid(steam)/version(1493162727)
/run/current-system/sw/share/themes/Breeze-Dark/gtk-2.0/widgets/entry:70: error: unexpected identifier `direction', expected character `}'

(steam:2794): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita",
/run/current-system/sw/share/themes/Breeze-Dark/gtk-2.0/widgets/styles:36: error: invalid string constant "combobox_entry", expected valid string constant
Installing breakpad exception handler for appid(steam)/version(1493162727)
roaming config store loaded successfully - 1323 bytes.
migrating temporary roaming config store
Installing breakpad exception handler for appid(steam)/version(1493162727)
Fontconfig error: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig error: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig warning: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number
Failed to init SteamVR because it isn't installed
ExecCommandLine: ""/home/bugworm/.local/share/Steam/ubuntu12_32/steam" "
Installing breakpad exception handler for appid(steam)/version(1493162727)
System startup time: 4.44 seconds
Generating new string page texture 74: 1024x256, total string texture memory is 1.36 MB
Generating new string page texture 75: 128x256, total string texture memory is 131.07 KB
Generating new string page texture 76: 128x256, total string texture memory is 1.49 MB
Generating new string page texture 77: 64x256, total string texture memory is 1.56 MB
Generating new string page texture 78: 8x256, total string texture memory is 1.56 MB
Generating new string page texture 79: 32x256, total string texture memory is 1.60 MB

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
Generating new string page texture 88: 128x256, total string texture memory is 1.73 MB
Generating new string page texture 90: 256x256, total string texture memory is 1.99 MB
Generating new string page texture 118: 384x256, total string texture memory is 2.38 MB
Game update: AppID 49520 "Borderlands 2", ProcID 2856, IP <IP_ADDRESS>:0
>>> Adding process 2856 for game ID 49520
ERROR: ld.so: object '/home/bugworm/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/bugworm/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
/home/bugworm/.local/share/Steam/steamapps/common/Borderlands 2/./Borderlands2: /steamrt/i386/lib/i386-linux-gnu/libdbus-1.so.3: no version information available (required by /steamrt/i386/lib/libpulse.so.0)
/home/bugworm/.local/share/Steam/steamapps/common/Borderlands 2/./Borderlands2: /steamrt/i386/lib/i386-linux-gnu/libdbus-1.so.3: no version information available (required by /nix/store/3h9x3ya9cbwm53hjj177gwzfszxbibkj-libpulseaudio-10.0/lib/pulseaudio/libpulsecommon-10.0.so)
>>> Adding process 2857 for game ID 49520

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.

(steam:2794): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
Setting breakpad minidump AppID = 49520
Steam_SetMinidumpSteamID:  Caching Steam ID:<PHONE_NUMBER>0972398 [API loaded no]
ERROR: ld.so: object '/home/bugworm/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/bugworm/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/bugworm/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
lspci: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory
>>> Adding process 2859 for game ID 49520
ERROR: ld.so: object '/home/bugworm/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/bugworm/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/bugworm/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
lspci: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory
>>> Adding process 2866 for game ID 49520
Installing breakpad exception handler for appid(gameoverlayui)/version(20170425224519)
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
Fontconfig error: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig error: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 70: non-double matrix element
Fontconfig warning: "/etc/fonts//conf.d/10-scale-bitmap-fonts.conf", line 78: saw unknown, expected number
Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)
Generating new string page texture 132: 256x256, total string texture memory is 393.22 KB
Generating new string page texture 133: 128x256, total string texture memory is 2.51 MB
Game removed: AppID 49520 "Borderlands 2", ProcID 2857
No cached sticky mapping in ActivateActionSet.

I have the same problem.
I have done some investigating and these are my results:

ldd doesn't complain about any missing libraries.

./Borderlands2_bak: /steamrt/i386/lib/i386-linux-gnu/libdbus-1.so.3: no version information available (required by /nix/store/6ypyfg3r421vnxxxiyxq4x23vnqxjzfh-libpulseaudio-10.0/lib/pulseaudio/libpulsecommon-10.0.so)
        linux-gate.so.1 (0xf77a2000)
        /home/stani/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so (0xf7768000)
        libsteam_api.so => ./libsteam_api.so (0xf7758000)
        libcrypto.so.1.0.0 => ./libcrypto.so.1.0.0 (0xf75ab000)
        libX11.so.6 => /steamrt/i386/usr/lib/i386-linux-gnu/libX11.so.6 (0xf7477000)
        libGL.so.1 => /run/opengl-driver-32/lib/libGL.so.1 (0xf73cb000)
        libz.so.1 => /steamrt/i386/lib/i386-linux-gnu/libz.so.1 (0xf73b5000)
        libpthread.so.0 => /usr/lib32/libpthread.so.0 (0xf7397000)
        librt.so.1 => /usr/lib32/librt.so.1 (0xf738e000)
        libdl.so.2 => /usr/lib32/libdl.so.2 (0xf7389000)
        libm.so.6 => /usr/lib32/libm.so.6 (0xf732e000)
        libuuid.so.1 => /steamrt/i386/lib/i386-linux-gnu/libuuid.so.1 (0xf7328000)
        libc++.so.1 => ./libc++.so.1 (0xf727e000)
        libcxxrt.so => ./libcxxrt.so (0xf725f000)
        libc.so.6 => /usr/lib32/libc.so.6 (0xf70a5000)
        libgcc_s.so.1 => /steamrt/i386/lib/i386-linux-gnu/libgcc_s.so.1 (0xf708a000)
        libiconv.so.2 => ./libiconv.so.2 (0xf6fa6000)
        libstdc++.so.6 => /steamrt/i386/usr/lib/i386-linux-gnu/libstdc++.so.6 (0xf6ebd000)
        libssl.so.1.0.0 => ./libssl.so.1.0.0 (0xf6e67000)
        libopenal.so.1 => /steamrt/i386/lib/libopenal.so.1 (0xf6dc8000)
        /lib/ld-linux.so.2 (0xf77a4000)
        libxcb.so.1 => /steamrt/i386/usr/lib/i386-linux-gnu/libxcb.so.1 (0xf6da6000)
        libXext.so.6 => /steamrt/i386/usr/lib/i386-linux-gnu/libXext.so.6 (0xf6d94000)
        libasound.so.2 => /steamrt/i386/lib/libasound.so.2 (0xf6c72000)
        libpulse.so.0 => /steamrt/i386/lib/libpulse.so.0 (0xf6c17000)
        libXau.so.6 => /steamrt/i386/usr/lib/i386-linux-gnu/libXau.so.6 (0xf6c11000)
        libXdmcp.so.6 => /steamrt/i386/usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xf6c0a000)
        libpulsecommon-10.0.so => /nix/store/6ypyfg3r421vnxxxiyxq4x23vnqxjzfh-libpulseaudio-10.0/lib/pulseaudio/libpulsecommon-10.0.so (0xf6b7d000)
        libsndfile.so.1 => /steamrt/i386/usr/lib/i386-linux-gnu/libsndfile.so.1 (0xf6b0b000)
        libFLAC.so.8 => /steamrt/i386/usr/lib/i386-linux-gnu/libFLAC.so.8 (0xf6abd000)
        libvorbisenc.so.2 => /steamrt/i386/usr/lib/i386-linux-gnu/libvorbisenc.so.2 (0xf6945000)
        libvorbis.so.0 => /steamrt/i386/usr/lib/i386-linux-gnu/libvorbis.so.0 (0xf691a000)
        libogg.so.0 => /steamrt/i386/usr/lib/i386-linux-gnu/libogg.so.0 (0xf6910000)
        libdbus-1.so.3 => /steamrt/i386/lib/i386-linux-gnu/libdbus-1.so.3 (0xf68c6000)
        libsystemd.so.0 => /nix/store/s4dd533qfvbrnjh8ryyzhq45m0h2kxhp-systemd-232-lib/lib/libsystemd.so.0 (0xf6836000)
        libcap.so.2 => /steamrt/i386/lib/i386-linux-gnu/libcap.so.2 (0xf6830000)
        libresolv.so.2 => /usr/lib32/libresolv.so.2 (0xf6819000)
        liblzma.so.5 => /nix/store/cijfycgfilg76p91m37blvz0m27pchig-xz-5.2.3/lib/liblzma.so.5 (0xf67ee000)
        liblz4.so.1 => /nix/store/ndv58ld00rj8f8glyax0hbixjamrnyz9-lz4-131/lib/liblz4.so.1 (0xf67db000)
        libgcrypt.so.20 => /nix/store/3hzinps6j8hgj3wcxf1xr6cjz21x8dhb-libgcrypt-1.7.6/lib/libgcrypt.so.20 (0xf670d000)
        libgpg-error.so.0 => /steamrt/i386/lib/libgpg-error.so.0 (0xf66f3000)

Running Borderlands 2 through steam with the 64bit libraries removed from LD_LIBRARY_PATH
it instead complains about libGL being the wrong class

Setting breakpad minidump AppID = 49520
Steam_SetMinidumpSteamID:  Caching Steam ID:<PHONE_NUMBER>8863205 [API loaded no]
ERROR: ld.so: object '/home/stani/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
sh: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32
ERROR: ld.so: object '/home/stani/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
sh: error while loading shared libraries: libGL.so.1: wrong ELF class: ELFCLASS32

Seems that it needs the 64bit libGL, but why would a 32bit game want to use a 64bit lib?

I managed to make the game run by turning off my internet connect right before it launches so it doesn't start downloading the hotfix.
When it runs; it runs smoothly, but still complains about libGL.so.1 in the output, which leads me to believe that there is nothing wrong with that lib and I have been looking in the wrong place -.-

For me it only works if I start steam in offline mode..

@DIzFer has fixed this in #31480


add embedPage()

adds a function embedPage() that embeds a page of the current document into the current page, potentially scaled, rotated & offset.  Fixes #2300.  This has not been extensively tested and is provided for evaluation purposes.

closing; will resubmit.  There was a bug in this version relating to simultaneous use of yscale and rotation.


Added support for object fields

Allows queries to select for fields inside of
object type fields.
Example:
{
  greeting
  person {
    name
    title
  }
}

will yield:
{
  "greeting": "Hello world!",
  "person": {
      "name": "Nick Gartmann",
      "title": "Mr."
    }
}

Currently relying on placing an ObjectType in the fields list for the schema (see here). An argument could be made for having an ObjectType return from FieldDefinition.resolve/1 and having that properly get handled, but the direct placement into the schema made the schema more readable so I went with this.

Thanks for the PR! I'm currently working on this section of code which will change things drastically. You happy if I merge this in as is?

Pretty sure I captured the essence of this PR in #25, let me know if I missed anything! Apologies again about reverting, my bad for not rebasing sooner :disappointed:


Connection to <IP_ADDRESS>

My plugin is working correctly with a bridge in <IP_ADDRESS>
However, I get periodical errors about a connection to <IP_ADDRESS>:
[2022/02/16, 13:28:24] [Nuki] warning: <IP_ADDRESS>: request 1: GET /info
[2022/02/16, 13:28:24] [Nuki] warning: <IP_ADDRESS>: request 1: error: connect ECONNREFUSED <IP_ADDRESS>:8080
It is once every 10 minutes.
Problem persist even after deleting cache, plugin and reinstalling.
My output of nb discover with debug:
nb discover: nuki server: request 1: GET /bridges
nb discover: nuki server: request 1: 200 OK
nb discover: <IP_ADDRESS>: request 1: GET /info
nb discover: <IP_ADDRESS>: request 1: GET /info
nb discover: warning: <IP_ADDRESS>: request 1: error: connect ECONNREFUSED <IP_ADDRESS>:8080
[]
Anything that can be done to remove that residual error?
Many thanks for your work

After going again over closed issues, I got the suggestion to reboot the bridge.
After rebooting the bridge again with nb command, problem dissapeared


Make references clickable

EG I see a product supports another product.
Deeplink to the profile of that product, so a user can explore.

Supports
Deployed on
Main asset


New version: AntibodySoftware.WizTree version 4.19

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Closed in favor of #142182, which I somehow overlooked in the PR search. Sorry :/


az140-42_azuredeploycl42.json needs updated OSVersion

Module: 04
Lab/Demo: 02 Package_AVD_Applications/Package Azure Virtual Desktop applications (AD DS)
Task: 02
Step: 02
Description of issue
\AZ-140\AllFiles\Labs\04\az140-42_azuredeploycl42.json returns an invalid template error [p1], which appears to be an issue with azuredeploycl42.json's 91st line, windowsOSVersion: "22h2-pro" -- no such offer exists. Switching it to Win10-22h2-pro resolves the issue.
[p1]

updated
rgds
Marcin


Fix assertion for floating points  in geomapper tests

Description
Tests in main are failing due to some floating point errors (dont know why they just appeared). This fixes them
Changelog
Itemize code/test/documentation changes and files added/removed.

Change assertions from .equals to == to approximate testing functions.

Fixes

Fixes #(issue)

@korlaxxalrok could you merge this as well? I'm not authorized

@chinandrew Can and shall do.


Double clicking on FAF logo makes the client fullscreen

Not present in 0.8.0
In 0.9.0 upwards double clicking anywhere on the window makes it go fullscreen.
It's great, except when it conflicts with other commands and makes the client fullscreen when it was not intended. Double clicking on the FAF logo is the only way to access connection parameters.
Maybe either make the FAF logo single click, or remove the fullscreen on double click if the click is eaten by another command ?

Double clicking a lot of things make the client full screen


[dvsim] How to specifying user defined --cores-root instead of the default {proj_root}

Currently in hw/dv/tools/dvsim/fusesoc.hjson, the cores root provided to fusesoc is fixed.
fusesoc_cores_root_dirs: ["--cores-root {proj_root}"]

Is there a way this can be updated?

@sriyerg Tagging Srikrishna for visibility

This dvsim HJSON variable is a list. So you can "append" additional paths that contain sources to it in other HJSON files (for instance, your main 'DUT' HJSON file):
  fusesoc_cores_root_dirs: ["--cores-root path/to/foo", "--cores-root path/to/bar"]

dvsim appends them all together, regardless of where the HJSON file is in the import_cfgs tree.
If you want to not include the proj_root dir (not recommended), then dvsim supports an override mechanism (with the limitation of only one override per HJSON variable).
  overrides: [
    {
        name: fusesoc_cores_root_dirs
        value: ["--cores-root path/to/foo", "--cores-root path/to/bar"]
    }
  ]

Thank you Srikrishna! This is exactly what I was looking for and it's working as expected.


Properly summed up contents

Nice format for exposing the information about the feature

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bcc06ead-fe51-85db-1340-87f6473db769
Version Independent ID: 4f2c312e-609c-a643-4af6-c12c6cf74738
Content: Indexers
Content Source: docs/csharp/indexers.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thank you for letting us know that you found the article helpful, @cppxaxa!


Added link to commanding doc

@mijacobs,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Windows builds time-out

Builds fail since #186. The windows build takes too much time.

Both windows and Darwin builds timeout:
https://github.com/iterative/dvc-bench/actions/runs/196560475
https://github.com/iterative/dvc-bench/actions/runs/196961245

We have reached the moment when our Darwin and Windows builds time out, because we have too may benchmarks.
We could try:

optimize our benchmarks (eg preparing whole repo's templates)
pushing through sequential benchmarks (#187) and adjusting existing benchmarks accordingly to make more benchmarks in less time
even roll back the latest "big" change #186
limit the number of runs for our benchmarks (that will take its toll on frequency of new regressions occurrence)

But it will not solve the main problem - that windows (and in case of Github actions Darwin) builds are slow and will sooner or later start timeout-ing again (after someone contributes another heavy benchmark).
As we need our benchmarks to run, I decided to temporarily turn off windows and darwin builds (#197 ). Windows builds are slow, Darwin- they are both slow and unreliable
We are limited by GHA 6 hours build policy.
We need to start running our benchmarks on our own machines and this is what I intend to take care of now. After that we can look into optimization of benchmarks and limiting number of runs per benchmark, if the results turn out reliable (Which does not seem to be a case, for example for darwin builds.

Keeping it open, as ideally, we would like to build on windows too.

closing as stale, will be dealing with windows as we go.


updated readme with a more complete example (closes #1) and fixed errors (closes #2)

This fixes issues #1 and #2
Note that AWS SDK supports promises out of the box and in a more complete example I only used ES2015 Node.js features that are available natively (Node.js version 4.3.2, because that is the latest version currently supported in AWS Lambda) , because setting up webpack and babel in aws lambda/dynamoDB environment is quite tricky, especially for beginners, so this example would get them started quickly.

Thank you for contributing! I'll review and add more comments tonight.

Merged. Thank you!


[Request]

Can you add users function and config file to store settings.

Fetching by user profiles was previously available but RedGIFs updated their API a two months ago which made it unavailable.
A config file to store settings does not make sense in this project but rather here.


Add APPLICATIONINSIGHTS_STATSBEAT_DISABLED_ALL = True

What is being addressed
Set APPLICATIONINSIGHTS_STATSBEAT_DISABLED_ALL = True as believed to be the cause of high CPU.
How is this addressed

Add APPLICATIONINSIGHTS_STATSBEAT_DISABLED_ALL = True to terraform
Add additional metrics
[ ] Run for 24 hours to see if issue resolved.

Looks like CPU is still ramping up, this code change was deployed at the red line. Will monitor:


Added SOLID Principles (C#) and another book

Added A book about SOLID Principles in C# Programming and an Introduction to Dependency Injection (under Misc) alphabetically.

closing after 6 months


Installation advice breaks @nomiclabs/hardhat-waffle

james@gig /tmp/asdf $ npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   dev @nomiclabs/hardhat-ethers<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-waffle
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/james/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/james/.npm/_logs/2021-07-08T18_05_56_589Z-debug.log

james@gig /tmp/asdf $ cat package.json
{
  "devDependencies": {
    "@nomiclabs/hardhat-waffle": "^2.0.1",
    "@nomiclabs/hardhat-ethers": <EMAIL_ADDRESS>    "ethers": "^5.4.1"
  }
}
james@gig /tmp/asdf $

could it be that npm do not support the ^ when using alias ?
my template repo works and the line is :     "@nomiclabs/hardhat-ethers": <EMAIL_ADDRESS>

I'm facing the same problem. I've tried to use your line like this in my package.json:
  "dependencies": {
    "@chainlink/contracts": "^0.2.1",
    "@openzeppelin/contracts": "^4.1.0",
    "dotenv": "^10.0.0",
    "hardhat": "^2.4.1"
  },
  "devDependencies": {
    "@nomiclabs/hardhat-ethers": <EMAIL_ADDRESS>    "@nomiclabs/hardhat-waffle": "^2.0.1",
    "chai": "^4.3.4",
    "ethereum-waffle": "^3.4.0",
    "ethers": "^5.4.1",
    "hardhat-deploy": "^0.8.11",
    "hardhat-gas-reporter": "^1.0.4"
  }

Same here
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   dev @nomiclabs/hardhat-ethers<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-waffle
npm ERR!   dev @nomiclabs/hardhat-waffle@"*" from the root project

<EMAIL_ADDRESS>expects @nomiclabs/hardhat-ethers to be ^2.0.0 but it's "only" 0.3.0-beta.10.

Thanks for your reports.
The best forward will be to fix the following issue in hardhat: https://github.com/nomiclabs/hardhat/issues/1040
This is what is blocking me from making hardhat-deploy-ethers and extension to hardhat-ethers

Encountered the same issue as of now. No update?

@OCWC22 do you have a repo reproducing the issue ?
It is working fine for me in this simple test repo : https://github.com/bug-reproduction/test-hardhat-deploy-ethers

It is working fine for me in this simple test repo : https://github.com/bug-reproduction/test-hardhat-deploy-ethers

Getting the same error in this repo with npm (version 8.3.0) if I delete the package-lock.json first (otherwise I guess it doesn't do any dependency resolution).
With yarn (version 1.22.11) it works, but I get the following warnings:
warning " ><EMAIL_ADDRESS>has incorrect peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>

Can confirm, getting the same error
node version: v16.13.2
npm version: 8.1.2

@jannikluhn @outdoteth if you remove the package-lock what is probably happening is that the ^ make it use something else.
Can you try with the specific version specified as mentioned here : https://github.com/wighawag/hardhat-deploy-ethers/issues/13#issuecomment-877578055

@wighawag I still get the same error
rm -rf package-lock.json
rm -rf node_modules
npm install

Here is my package.json
{
  "name": "backspread",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@nomiclabs/hardhat-ethers": <EMAIL_ADDRESS>    "@nomiclabs/hardhat-waffle": "^2.0.2",
    "chai": "^4.3.6",
    "ethereum-waffle": "^3.4.0",
    "ethers": "^5.5.3",
    "hardhat": "^2.8.3",
    "hardhat-deploy": "^0.10.1"
  }
}

Re warning @jannikluhn
I suppose the ethereum-waffle is unrelated to the issue here
the<EMAIL_ADDRESS>is probably expected since we are using hardhat-deploy-ethers instead of hardhat-ethers
<EMAIL_ADDRESS>is expected as it is an optional peer dependencies

@outdoteth thanks for trying out, I ll see if I can reproduce and figure out what is going on

Ok thanks - fwiw it is working on one of my other machines. I am trying to see what is different between them

I just tried and can reproduce, seems like npm do not likes the npm@ when peer dependencies are involved
Note that npm i --force works in that case though

By the way, the best way froward out of this issue is to have this issue resolved : https://github.com/nomiclabs/hardhat/issues/1040
this would allow me to have hardhat-deploy-ethers be an extension to hardhat-ethers instead of having to install it as alias

Hey
I commented out from hardhat.config.ts:
import "@nomiclabs/hardhat-waffle";
And to my tests added:
import {waffleChai} from '@ethereum-waffle/chai';
use(waffleChai);

And now I can finally use revertedWith assertions in my tests.

This issue seems to come up intermittently for me. Currently it's breaking in our CI after working fine for a few months. I'm having no issues on my local machine.
Console Output
Run npm ci
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   dev @nomiclabs/hardhat-ethers<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-waffle
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nomiclabs/hardhat-waffle
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/runner/.npm/eresolve-report.txt for a full report.
npm ERR!

This seems to be resolved after I set the node version to 16.15.0, from 16.15.1. The changing of the versions may explain the intermittency of the issue for me.

I ran in the same issue just now, after having no problem in the last couple of months (?)
But i ended up defining an override which seems to be the "proper" workaround for now:
  "devDependencies": {
...
    "@nomiclabs/hardhat-ethers": <EMAIL_ADDRESS>...
},
  "overrides": {
    "@nomiclabs/hardhat-waffle": {
      "@nomiclabs/hardhat-ethers": "$@nomiclabs/hardhat-ethers"
    }
  }

@suicide this override fixed it for me, for now... thanks

I'm not sure exactly what the issue is, but changing "@nomiclabs/hardhat-ethers": "npm:hardhat-deploy-ethers@^0.3.0-beta.13",to"@nomiclabs/hardhat-ethers": "^2.2.1",` seems to resolve it.

Thanks for your reports. The best way forward will be to fix the following issue in hardhat: NomicFoundation/hardhat#1040
This is what is blocking me from making hardhat-deploy-ethers and extension to hardhat-ethers
feel free to add your comments there

Looks like this now can be implemented through<EMAIL_ADDRESS>See Pull Request 3498

hardhat-deploy-ethers@next has been released
Please, try it out.
It is now an extension to hardhat-ethers so you need both
But note that that new version do not support external artifact if you were using them

I'm trying to use the @next version with 'npm install --save-dev @nomiclabs/hardhat-ethers@npm:hardhat-deploy-ethers@next' but still having the same installation issues. How should we do now with these changes? Thanks

Hey @wighawag
Added hardhat-deploy to my repo a few weeks ago, but now facing issues with installing or updating packages
Install
> npm install --save-dev @nomicfoundation/hardhat-chai-matchers
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   dev @nomiclabs/hardhat-ethers<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nomicfoundation/hardhat-chai-matchers
npm ERR!   dev @nomicfoundation/hardhat-chai-matchers@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Update
npm update ethereum-waffle

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   dev @nomiclabs/hardhat-ethers<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-waffle
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nomiclabs/hardhat-waffle
npm ERR!     dev<EMAIL_ADDRESS>from the root project

Hey @wighawag
Added hardhat-deploy to my repo a few weeks ago, but now facing issues with installing or updating packages
Install
> npm install --save-dev @nomicfoundation/hardhat-chai-matchers
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   dev @nomiclabs/hardhat-ethers<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nomicfoundation/hardhat-chai-matchers
npm ERR!   dev @nomicfoundation/hardhat-chai-matchers@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Update
npm update ethereum-waffle

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   dev @nomiclabs/hardhat-ethers<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-waffle
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@nomiclabs/hardhat-ethers
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nomiclabs/hardhat-waffle
npm ERR!     dev<EMAIL_ADDRESS>from the root project

hey I was running into the same thing, after i used @next it has no more issue anymore, change your hardhat-deploy-ethers version and it should be working


[HELP] How do I configure selenium2 host url?

I'm running my selenium instance and behat in separate docker containers. By default, behat/mink-selenium2-driver tries to connect to selenium on localhost:4444, so it won't work, but it does allow you to configure the selenium host. How do I configure this in my behat.yml though? I didn't find how to do it in the doc.

Ok, so I just went through the code and found my answer in the Selenium2Factory:84, it receives a wd_host property, so my behat.yml is like this now and it's working:
default:
  extensions:
    Behat\MinkExtension:
      sessions:
        default:
          selenium2:
            browser: chrome
            capabilities: []
            wd_host: http://selenium:4444/wd/hub


Making the physics truly do nothing

Currently, the ice thermodynamics can be turned off by using DummyIceThermodynamics and the ice spread disabled by using DummyIceSpread as the implementations for IIceThermodynamics and LateralSpread, respectively.
To entirely disable any changes to the ice by the physics calculations, the ice growth due to the freezing of sea water also need to be prevented. This can be done by implementing a new derived class of IFluxCalculation which returns 0 for the open water heat flux. The question is then whether this implementation should also zero all other calculated fluxes. Also, this would only be called by atmospheric boundary modules that actually call the flux calculation routine. Other boundary modules, such as FluxConfiguredOcean may result in a situation where all of the 'turn off the physics' implementations have been configured to be used, but the ocean freezing still occurs.
Another alternative would be to wrap the top-level call to the physics in an if statement with an additional model configuration option selecting to turn off the thermodynamics. Does this already exist in neXtSIM-LG?

Yes, thermo.use_thermo_forcing, nextsim/options.cpp:L371

Fix merged as PR #340.


pnpm: support v9 lockfile format for dependabot alerts - and/or warn that it is unsupported

Is there an existing issue for this?

[X] I have searched the existing issues

Feature description
There is already an issue for this: https://github.com/dependabot/dependabot-core/issues/9522 that has been closed, but I've confirmed with GitHub support that in fact it is still not supported for security updates.
We are not seeing any security alerts since upgrading. This seems pretty dangerous given others may also have upgraded without realising they would no longer receive updates - dependabot doesn't seem to trigger any warning for this?

We are also no longer seeing security alerts, having upgraded recently. There has been very little, if no warning, provided.

Not seeing dependabot security alerts for projects using pnpm, found this issue searching for answers... hopefully will be fixed soon.

ICYMI: https://github.com/orgs/community/discussions/134391

I can see dependabot alerts in our repo using the v9 lockfile again as of a few hours ago. I can't see any related notes in the change log. Hopefully this is working again for others as well.

I can see dependabot alerts in our repo using the v9 lockfile again as of a few hours ago. I can't see any related notes in the change log. Hopefully this is working again for others as well.

I don't see anything yet but maybe it will take a bit to propagate.  Are you doing anything with your dependabot.yml to define that you are using PNPM or did dependabot just start picking it up natively?

I can see dependabot alerts in our repo using the v9 lockfile again as of a few hours ago. I can't see any related notes in the change log. Hopefully this is working again for others as well.

We're seeing some alerts too, but I’m unclear on the reason why. The confusion stems from the fact that the dependency graph still doesn’t detect transitive dependencies from v9 lockfiles:

v8: https://github.com/vluoto/dependency-graph-pnpm-v8/network/dependencies
v9: https://github.com/vluoto/dependency-graph-pnpm-v9/network/dependencies

The reason I’m bringing up the dependency graph is because of this section in the README of the repository:

Don't file issues about Security Alerts or Dependency Graph
The issue-tracker is meant solely for issues related to Dependabot's updating logic. Issues about security alerts or Dependency Graph should instead be filed as a Code Security discussion.
A good rule of thumb is that if you have questions about the diff in a PR, it belongs here.

This is also why I opened the aforementioned discussion https://github.com/dependabot/dependabot-core/issues/10534#issuecomment-2393373438.

Are you doing anything with your dependabot.yml to define that you are using PNPM or did dependabot just start picking it up natively?

We're not doing anything special beyond the following @msudol:
version: 2
updates:
  - package-ecosystem: "npm" # See documentation for possible values - npm is used for pnpm
    directories: # Location of package manifests
      - "/"
      - "/apps/*"
      - "/packages/*"
    schedule:
      interval: "weekly"

We're seeing some alerts too, but I’m unclear on the reason why. The confusion stems from the fact that the dependency graph still doesn’t detect transitive dependencies from v9 lockfiles

We're seeing transitive dependencies as part of our dependency graph now.

We've got a support ticket on this running in parallel, I've enquired to find out what change has been made for things to start working again.
Good spot on the readme @vluoto . Thanks for opening the discussion, I'll post an update there as well.

We're seeing transitive dependencies as part of our dependency graph now.

Hmm, I just checked, and we’re also seeing transitive dependencies in our repository:

Interestingly, my v9 showcase repo still only shows direct dependencies:

v9: https://github.com/vluoto/dependency-graph-pnpm-v9/network/dependencies

This could be due to a gradual rollout on GitHub's end. 🤷🏻♂

It works for me, but I had to update dependencies first to trigger a re-scan

Also working here now.

Regarding the visibility of the change, I've had the following back from support:

This is not currently available in our public changelog. The change was classified as a rudimentary support to accompany support for previous versions. So this is a workaround pending when more granular change can be done.

As of 20 Oct 2024, GitHub now successfully detects and reports vulnerabilities detected in pnpm v9 lockfiles.
This appears to be working even without configuring the packageManager (proposed in some workarounds).

Seems this is now addressed; closing this out. Please feel free to open new issues if there are related gaps.


Circular dependencies

store.js -> optimistic-data/store.js -> store.js
core/ObservableQuery.js -> core/QueryManager.js -> scheduler/scheduler.js -> core/ObservableQuery.js
core/QueryManager.js -> scheduler/scheduler.js -> core/QueryManager.js
optimistic-data/store.js -> store.js -> optimistic-data/store.js
scheduler/scheduler.js -> core/QueryManager.js -> scheduler/scheduler.js

@DxCx

@kamilkisiela what is this for? Some tool that cannot handle circular dependencies?
PS: I'm surprised there isn't one between ApolloClient.ts and QueryManager.ts.

@helfer yes, rollup + systemjs for an example. There's a webpack plugin that shows all circular dependencies.
We work on some cool thing and this stops us, last missing piece.

I also managed to hit this issue with rollup. It took quite a while to debug. FWIW, here's the rollup issue for tracking this: https://github.com/rollup/rollup-plugin-commonjs/issues/105


Support modularization within app project

Currently, Accio supports modularization of frameworks and using those in App projects. But sometimes one might want to modularize the app itself into several parts, for example consider this:
// swift-tools-version:5.0
import PackageDescription

let package = Package(
    name: "App",
    products: [
        .library(name: "AppKit", targets: ["AppKit"])
    ],
    dependencies: [],
    targets: [
        .target(
            name: "App",
            dependencies: ["AppKit"],
            path: "App"
        ),
        .target(
            name: "AppKit",
            dependencies: [],
            path: "AppKit"
        ),
    ]
)

When we run accio update today with such a setup, we get this error output:
❌  DependencyGraph: Could not find library product with name 'AppKit' in package manifest for project 'App'.

Okay, after thinking about the a second time, I came to the conclusion that solving such situations by providing a local library is far too complicated and would result to many issues. The much easier and less error prone fix for such situations is to add any helper modules to the "Target Dependencies" of the app target within Xcode without using Accio. Then, in the Package.swift file, make sure that all dependencies of the helper modules are also listed in the app target. For example:
// swift-tools-version:5.0
import PackageDescription

let package = Package(
    name: "App",
    products: [
        .library(name: "AppKit", targets: ["AppKit"])
    ],
    dependencies: [/* ... */],
    targets: [
        .target(
            name: "App",
            dependencies: ["A", "B"],
            path: "App"
        ),
        .target(
            name: "AppKit",
            dependencies: ["A", "B"],
            path: "AppKit"
        ),
    ]
)

Unless someone has an idea of how this situation could be solved properly, without making development a hassle (e.g. needing to re-run Accio each time a change is made in a module), I will mark this as "won't fix" and ask everyone running into this situation to accept the redundancy in specifying subdependencies.


Support Report Generation For Customs

Current month
Last Month
For a given period

Create a new view for reports
Create a new route for reports
Create receipts controller
Move controller code from receipts to controller
Add controller routine to return report view
Populate report with expected data


ValueError: Invalid frequency: ME when using qs.reports.html

I'm encountering a ValueError: Invalid frequency: ME when using the qs.reports.html function.  This error seems to be generated internally within the library, even when I provide a valid integer value for the periods_per_year argument.
Steps to Reproduce
Import libraries

import pandas as pd
import quantstats_lumi as qs

Create Sample Data

dates = pd.date_range('2023-05-01', periods=10)
portfolio_data = [1.02, 0.98, 1.05, 1.01, 1.03, 0.97, 0.99, 1.06, 1.0, 0.99]
benchmark_data = [1.01, 0.99, 1.03, 1.02, 1.06, 0.96, 0.98, 1.05, 0.98, 1.0]

portfolio = pd.Series(portfolio_data, index=dates, name="Port")
bench = pd.Series(benchmark_data, index=dates, name='SPY')

Attempt to generate the report:

qs.reports.html(portfolio, benchmark=bench, output='test_output.html', periods_per_year=365)

The above code produces the following traceback (shortened for clarity):

ValueError: Invalid frequency: ME

I've tried the following troubleshooting steps:

Ensuring the periods_per_year argument is a valid integer.
Restarting my runtime environment.
Inspecting my code for any potential sources of the "ME" string.

You have an old version of pandas, make sure that you upgrade to the latest
version
Robert Grzesik<PHONE_NUMBER>
On Tue, May 7, 2024 at 7:16 PM tampaguy2012 @.***>
wrote:

I've tried the following troubleshooting steps:

Ensuring the periods_per_year argument is a valid integer.
Restarting my runtime environment.
Inspecting my code for any potential sources of the "ME" string.

—
Reply to this email directly, view it on GitHub
https://github.com/Lumiwealth/quantstats_lumi/issues/32#issuecomment-2099460651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIYQK4E7OQSUUZSMNXLV23ZBFODZAVCNFSM6AAAAABHL4IQISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZGQ3DANRVGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have the same issue, have verified that the error occurs even with the latest version of pandas. Pandas documentation https://pandas.pydata.org/docs/whatsnew/v2.2.0.html#deprecate-aliases-m-q-y-etc-in-favour-of-me-qe-ye-etc-for-offsets suggests these are the frequency strings that should be in use, not sure what is going on.


Seconds not working in range time picker

<Datepicker v-model="selectedDate" placeholder="Select Date" enable-seconds range />
Second are showing in time-picker, but they can't be changed.
Seems like second-support was never added to the range time picker.

Hah, I overlooked it. Will be fixed.


chore: update upstream gravity module to fix halt bug

@facundomedica was able to contribute the halting fix upstream albeit still in an unversioned release.
bumps gravity module to 8d660b559b0718c6ff4e20f3b355d94501d8dbb3
ran:
go get github.com/Gravity-Bridge/Gravity-Bridge/module@8d660b559b0718c6ff4e20f3b355d94501d8dbb3

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #932 (ab34d69) into main (d3546fd) will decrease coverage by 0.00%.
The diff coverage is 52.73%.

@@            Coverage Diff             @@
##             main     #932      +/-   ##
==========================================
- Coverage   50.90%   50.90%   -0.01%
==========================================
  Files          64       64
  Lines        9456     9479      +23
==========================================
+ Hits         4814     4825      +11
- Misses       4397     4401       +4
- Partials      245      253       +8

Impacted Files
Coverage Δ

x/leverage/client/cli/query.go
0.00% <0.00%> (ø)

x/leverage/keeper/genesis.go
2.15% <0.00%> (ø)

x/leverage/keeper/grpc_query.go
5.55% <0.00%> (ø)

x/leverage/keeper/interest.go
78.16% <0.00%> (-4.32%)
:arrow_down:

x/leverage/keeper/reserves.go
78.94% <ø> (+2.99%)
:arrow_up:

x/leverage/types/query.pb.gw.go
0.00% <0.00%> (ø)

x/leverage/keeper/keeper.go
45.88% <51.28%> (-1.66%)
:arrow_down:

x/leverage/keeper/token.go
61.73% <55.55%> (+1.34%)
:arrow_up:

x/leverage/keeper/oracle.go
67.07% <66.66%> (-2.16%)
:arrow_down:

x/leverage/client/tests/suite.go
100.00% <100.00%> (ø)

... and 10 more

@mergifyio backport release/v2.x.x

@Mergifyio backport release/price-feeder/v0.2.x


Unable to get merlin-mode to work

(load "/Users/yxchng/.opam/system/share/emacs/site-lisp/tuareg-site-file")
(add-to-list 'load-path
"/Users/yxchng/.opam/system/share/emacs/site-lisp")
(require 'ocp-indent)
;; Add opam emacs directory to the load-path
(setq opam-share (substring (shell-command-to-string "opam config var
share 2> /dev/null") 0 -1))
(add-to-list 'load-path (concat opam-share "/emacs/site-lisp"))
;; Load merlin-mode
(require 'merlin)
;; Start merlin on ocaml files
(add-hook 'tuareg-mode-hook 'merlin-mode t)
(add-hook 'caml-mode-hook 'merlin-mode t)
;; Enable auto-complete
(setq merlin-use-auto-complete-mode 'easy)
;; Use opam switch to lookup ocamlmerlin binary
(setq merlin-command 'opam)
I added this code to .emacs but it doesn't seem to work
it gives me spurious error and says
/usr/local/Cellar/emacs/24.5/Emacs.app/Contents/MacOS/Emacs: /bin/bash: opam: command not found/ocamlmerlin: No such file or directory
How should I solve this problem?

It seems that opam binary is just not reachable from your emacs process.
You should adjust the PATH environment variable, or maybe make a symbolic link to opam which is reachable system-wide PATH.


JS-Client defining type: module while exporting only CJS

Noticed this when installing the latest @wise-old-man/utils. It's because the package.json defines type: module which implies the resulting bundled code is ESM compliant.
There are two fixes here:

The easy one is to just remove that type declaration in package.json (or rename the bundle to .cjs)
But ESM is cool and good so....
We could have another build step that outputs both a commonJS bundle AND and ESM bundle.

Here's an example of someone doing it adding the required exports flag to package.json:
https://dev.to/mbarzeev/hybrid-npm-package-through-typescript-compiler-tsc-150c

Is this something you could contribute to @aleccaputo ?

@psikoi for sure.
Do you think i should just remove the module declaration for now and make a separate PR for exporting both builds?

@psikoi for sure. Do you think i should just remove the module declaration for now and make a separate PR for exporting both builds?

yea that sounds like a good plan

Fixed in #1461


reducedState.get is not a function

I kept getting the above error when trying to use redux-persist-immutable with a react-native app. I noticed the reducedState that the stateReconciler function was receiving was an array containing a Map of my state and an object with type: "NONE", Symbol(isEffect): true instead of just the immutable state. I made some modifications to the stateReconciler function to grab the state out of the array and everything seems to be working fine, but I'd really appreciate any assistance understanding why I had this issue and if there's a better way around it?
my store
import { applyMiddleware, createStore, compose } from 'redux';
import { persistStore, autoRehydrate } from 'redux-persist-immutable';
import { AsyncStorage } from 'react-native';
import { composeWithDevTools } from 'remote-redux-devtools';
import * as reduxLoop from 'redux-loop';

import middleware from './middleware';
import reducer from './combinedReducer';

const enhancer = composeWithDevTools(
  applyMiddleware(...middleware),
  autoRehydrate(),
  reduxLoop.install()
);

const store = createStore(
  reducer,
  null,
  enhancer
);

persistStore(store, { storage: AsyncStorage })

export default store;

my stateReconciler hack
function stateReconciler(state, inboundState, reducedState, logger) {
  var newState = reducedState ? reducedState[0] : (0, _immutable.Map)();
  Object.keys(inboundState).forEach(function (key) {
    // if initialState does not have key, skip auto rehydration
    if (!state.has(key)) return;

    // if reducer modifies substate, skip auto rehydration

    if (state.get(key) !== reducedState[0].get(key)) {
      if (logger) console.log('redux-persist/autoRehydrate: sub state for key `%s` modified, skipping autoRehydrate.', key);
      newState = newState.set(key, reducedState.get(key));
      return;
    }

    // otherwise take the inboundState
    if (state.has(key)) {
      newState = newState.mergeIn([key], inboundState[key]); // shallow merge
    } else {
      newState = newState.set(key, inboundState[key]); // hard set
    }

    if (logger) console.log('redux-persist/autoRehydrate: key `%s`, rehydrated to ', key, newState.get(key));
  });

  return newState;
}

I am also having this issue. Any leads on this?

We were using redux-loop at some point in our project and I believe it was transforming reducedState. When readying the app for deployment I realized it wasn't actually needed, removed it, and now everything is working as expected.


146 visual regression test for component states in storybook stories

I could manage to run proper VRTs for tooltip component. But still trying to figure out for input.
This makes tooltip tests better anyway. So I think we can consider to merge this first and continue for input in a separate issue/PR.

I opened a follow-up issue (#183) for writing visual tests focus, invalid, valid states of input component and cleaned this PR.

We passed layout:centered parameters to meta in the storybook.
<Meta
  title="Components/Tooltip"
  component="bl-tooltip"
  parameters={{
    layout: 'centered',
    chromatic: { viewports: [800] },
  }}
  argTypes={{
    placement: {
      control: 'text'
    }
  }}
/>

Is this not enough for being in the center of the layout? Why do we add this CSS?

Normally, it's enough to show component in the center of canvas in storybook UI. However, chromatic still tries to determine the size of needed space and take screenshot for that area. But since tooltip comes to the screen a bit later, it can not manage to get correct viewport size. Because of that (for having proper screenshots) I needed to set chromatic viewport size and add some styles to make an inner canvas that always has some bigger area.

@buseselvi now visual tests for tooltip component works properly. Please can you check if everything okay in new screenshots of tooltip stories on Chromatic?


msiexec

If you need to install an msi, make sure the .msi file is in the root of the container, not a subfolder.
This works:
msiexec /i MultipleHashInstallerx64.msi /qn /lv %CUSTOM_SETUP_SCRIPT_LOG_DIR%\MultipleHashInstall.LOG
This example using a Subfolder (yes the MSI exists in the subfolder) doesn't - it gets various errors in the MSI log
msiexec /i ".\MHI\MultipleHashInstallerx64.msi" /qn /lv %CUSTOM_SETUP_SCRIPT_LOG_DIR%\MultipleHashInstall.LOG
Errors seen in log:

Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
Note: 1: 1324 2: . 3: 1
MainEngineThread is returning 2

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 16d4ef48-6270-324e-5821-8557cf332320
Version Independent ID: da6ae67f-4d00-63fb-63b4-b615a78317aa
Content: Custom setup for the Azure-SSIS integration runtime
Content Source: articles/data-factory/how-to-configure-azure-ssis-ir-custom-setup.md
Service: data-factory
GitHub Login: @douglaslMS
Microsoft Alias: douglasl

@ElectricLlama Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

#in-progress

@ElectricLlama I want to verify with the product team that this is the expected behavior before adding clarifications to the documentation. Thanks for bringing this to our attention.

@ElectricLlama Here is the response I've received from the SSIS team:

You can have various .msis in subfolders of your blob container, since our custom setup will copy its whole folder hierarchy + content to the current working directory (.) of your Azure-SSIS IR and your main.cmd can then install those .msis from their subfolders.

Can you easily test this variation and report back?

OK - I will try the subfolder method again. However now that I have got a successful install , I tried publishing and running a package and it threw errors about the component (Sorry don't have the error to hand but it was your typical 'not installed' error.

hmmmm now my ADF returns 'Gateway Timeout' every time I try and start my Azure runtime with a SAS URI. I tested the URI in Azure Storage Explorer and it's valid. Could this error be because the runtime is now joined to a VNET? I am actually going backwards on this now as I can't start it anymore. Just as some background, I am trying to install a custom component which I also had an issue with - see here https://github.com/keif888/SSISMHash/issues/13

Just another thing - while trying to debug and troubleshoot this, I noticed that if there is an invalid URI (i.e. https://ZZZ), there is no error or clue in the activity log. It just doesn't write any logs out to the container. Maybe this is by design and maybe it should be obvious but it's just another thing that would've sped up my troubleshooting.

Could you please email me<EMAIL_ADDRESS>your ADF and Azure-SSIS IR names, so our team could investigate?  THX

So if I tick "Use AAD Authentication with your ADF MSI" I get this gateway timeout error is I am also provisioning something. If I'm only provisioning or only using MSI, it's not a problem.

@ElectricLlama The SSIS team has tested your original issue and discovered the following cause and resolution:

Seems MSIEXEC doesn’t support “.\” as a prefix of the target msi path. However, if I remove “.\”, i.e., msiexec /i Subfolder\MultipleHashInstallerx64.msi /qn, instead of  “msiexec /i .\Subfolder\MultipleHashInstallerx64.msi /qn”, the msi will be successfully installed.

@ElectricLlama I have updated the article with a note about the subfolder syntax. Thanks for bringing this to our attention.

#please-close

@ElectricLlama We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and tag me in your reply. We will gladly continue the discussion.


Correct instructions for changing strimzi's logging level

I noticed the instructions we provided were wrong, this fixes it.

I'll take a look tomorrow.

@grdryn could you review please?


Add function reset

This PR adds a function reset that puts all lazy_static variables back in their original, uninitialized states.  Such a function facilitates fuzzing with AFL in persistent mode.
In persistent mode, AFL does not launch a new process for each fuzzing run.  Rather, the process loops, repeatedly executing the function under test with new fuzzing inputs.  This can cause problems for programs that use lazy_static variables in at least two ways:

AFL can give incorrectly low stability reports.  Roughly speaking, stability is the fraction of instructions that are executed the same number of times across different runs of the program with the same input.  Because a lazy_static variable's initializer is executed only on the variable's first use, the initializer's instructions are counted against stability, causing it to be low.

AFL can fail to report timeouts.  Suppose that a fuzzing input X causes a program to use a large number of lazy_static variables, each of which has an expensive initializer.  If each of those variables was used for an earlier fuzzing input, then those variables' intializers will not be run on input X, causing the program to take less time than it otherwise would on input X.

Returning each lazy_static variable to its uninitialized state at the end of each fuzzing iteration addresses these problems.  This causes each lazy_static variable's initializer to be executed for each fuzzing input that uses that variable.  Thus, the initializer's instructions are not counted against stability.  On the other hand, the time taken to execute the initializer is counted against each input that uses that variable.
Conceptually, this PR does two things:

It collects all initialized lazy_static variables in a linked list.

It wraps each lazy_static variable's Once instance in a Cell.

The function reset walks the linked list in order to set the initialized lazy_static variables back to their uninitialized states, assigning ONCE_INIT to each Cell<Once> in the process.
A program demonstrating the problems described above can be found here.  The program further demonstrates that adding a call to reset at the end of each fuzzing iteration addresses these problems.

I would prefer not to do this. It looks like this introduces quite a bit of new complexity in Lazy::get.
Can you suggest any other ways to get better fuzzing in programs with a lazy_static?

Can you suggest any other ways to get better fuzzing in programs with a lazy_static?

You can abandon AFL persistent mode, of course.  But then you give up on the advantages that it provides (e.g., avoiding fork).
Another alternative may be to maintain a "resettable-lazy-static" fork and keep it in sync with the main repository, so that a person can patch-it-in when fuzzing.  lazy-static appears to be pretty stable, so this may be a workable solution.
I will take the issue up with the afl.rs maintainers and see what they say.
I understand your position.  Thanks a lot for your time.


Investigate: parallel upload of askpass file

Describe the bug
From discord:

Hello, I'm a new user of pyinfra, and I have an issue with the sudo mechanism, but most probably there is a problem with my config.
In the inventory.py I have a home group, and running only one operation:

files.directory(
    name="Ensure /etc/nebula exists",
    path="/etc/nebula",
    present=True,
    sudo=True,
    use_sudo_password=host.data.sudo_password,
)

sudo_password is part of the inventory config. It's working fine, if I have only one machine in inventory which needs sudo.
When I'm adding a second one, there is an error with the sudo command:

[machine.local] >>> env SUDO_ASKPASS=pyinfra-sudo-askpass *** sudo -H -A -k sh -c '! test -e /etc/nebula || (stat -c '"'"'user=%U group=%G mode=%A atime=%X mtime=%Y ctime=%Z size=%s %N'"'"' /etc/nebula 2> /dev/null || stat -f '"'"'user=%Su group=%Sg mode=%Sp atime=%a mtime=%m ctime=%c size=%z %N%SY'"'"' /etc/nebula)'
[machine.local] sudo: unable to run pyinfra-sudo-askpass: Exec format error
[machine.local] sudo: no password was provided
[machine.local] sudo: a password is required

It doesn't matter if theay are in the same group or not. One additional info: They are using the same user, same password, one machine is using a key, the other one is using password for the ssh connection. It's working with both of them separately, but not together...

With PARALLEL = 1 config it works like a charm, but I'm not sure why.

Can confirm in 1.4.3, I am experiencing this issue.
Short term solutions that have worked for me:

PARALLEL=1 in config.py.
Pass --limit= to one server when running pyinfra

Error:
    [machine_ip_c] sudo: unable to run pyinfra-sudo-askpass: Exec format error
    [machine_ip_c] sudo: no password was provided
    [machine_ip_c] Error
    [machine_ip_b] sudo: unable to run pyinfra-sudo-askpass: Exec format error
    [machine_ip_b] sudo: no password was provided
    [machine_ip_b] Error
    [machine_ip_a] Success

Also thanks @Fizzadar for pro-actively tracking this issue, I appreciate that.

Confirmed in v1.4.4 when I ran a deploy against real machines rather than the usual cohort of lxd instances I typically test with that don't require a password for SUDO.  Adding "use_sudo_password=True" to operations triggered the issue as soon as I ran the deploy against more than one machine.  The issue was observed during dry run as well as the actual deploy.
PARALLEL=1 in config.py was a viable workaround.

Finally got to the bottom of this - reuse of the same StringIO object; fixed in https://github.com/Fizzadar/pyinfra/commit/07f9d6c80612f12e0faf394d54c9cb1929c42577 & released just now in v1.4.5!

Fix confirmed.  Deploys no longer need PARALLEL=1 to work properly.


Fix a malformed SNS Publish API request when it has message attributes

I found a malformed request when I make an SNS Publish API request with message attributes.  I'm not used to rusoto code generating codes, so I'm unconfident that this change is preferred to fix the problem. It may be little shortsighted and a dirty hack..

Thanks for the PR! I'll be able to look at it in a few days. 👍

Looks like this fixes the bug you found! When digging into this service I found more:
There's another SNS action that needs entry in it: SetEndpointAttributes will also need this.
I'll file a new issue for that bug. 👍
For future reference: when I modified the code in this PR to put .entry. into all query type services, SQS and ELBv2 (also known as application load balancers, ALBs) also picked up this change. Looking over the docs for the affected calls in those services, they do not need .entry..

Thank you for taking look this bug report and its patch 😊


Beast CMakeLists is no longer compatible with cmake 3.8

The CMakeLists.txt refactor performed in commit 75e45287fbe115448281e41222aeac2023bb7ca1 seem to have broken compatibility with CMake 3.8. See this MySQL build: https://drone.cpp.al/boostorg/mysql/955/3/3
The problem seems to be that target_sources(... PRIVATE) is not supported for INTERFACE targets in CMake 3.8.
This problem only happens in develop.

Thanks for reporting this! Did you check if target_sources is the only issue?

It's the only problem reported by the build. It may be covering other issues. If you want to test locally, you can use the ghcr.io/anarthal-containers/build-cmake3_8 Docker image.

Yes, it seems that's the only issue.


Update README.md

This changes the URL referenced in the README, and updates the date ranges in the example text.

Looks good!

Mergin


Deep-link amount is not working on the Android only

Example deep link
https://link.trustwallet.com/send?coin=714&token_id=SWINGBY-888&address=bnb17ya27znhy4cmqczd2wwanyjwc50twxn5auk85k&amount=128.90605714&memo=69f3b1
Expected
the amount should be set<PHONE_NUMBER>4
Actual
the amount on the wallet says<PHONE_NUMBER>4
Trust wallet version
Version 1.11.6

@syrohei I'm gonna close this issue on Wallet Core.
This issue will be fix in the next release next week. Thanks


Incorrect CSS virtual path to absolute path transformation

Hello,
we have an app that is running in the server/MyApp path.
We are using System.Web.Optimization.CssRewriteUrlTransformFixed() to transform URL, but because we are not in root, but MyApp path, relative paths are resolved incorrectly.
Basically
we have something like
var urlTransform = new System.Web.Optimization.CssRewriteUrlTransformFixed();
bundles.Add(new LessBundle("~/Shared/CSS/common")
    .CheckAndInclude("~/Shared/CSS/external/jquery-ui/jquery-ui.css", urlTransform));

and in jquery-ui.css is
.ui-widget-content {
	background: url("images/ui.png");
}

and the transformed URL in CSS is
/Shared/CSS/external/jquery-ui/images/ui.png

instead of
/MyApp/Shared/CSS/external/jquery-ui/images/ui.png

See also http://aspnetoptimization.codeplex.com/workitem/83 and http://stackoverflow.com/a/17702773/2622707.
As a workaround we are using a copy as CssRewriteUrlTransformFixed with following line
var directory = "~" + VirtualPathUtility.GetDirectory(includedVirtualPath.Substring(1));

although I think would work as well
var directory = VirtualPathUtility.GetDirectory(includedVirtualPath);

Is there some reason for stripping tilda from path? If not, would it be possible to fix this?
Thank you very much.

Hi @jahav,
Sorry it has taken me so long to get to this. I have updated the codebase with your suggested fix of removing the .Substring(1), as the VirtualPathUtility methods should handle both scenarios. Thanks for the thorough issue report!
I've release to NuGet the fix as version 2.0.3.
https://www.nuget.org/packages/AspNetBundling/2.0.3
Cheers,
Ben

Hi @jahav,
Sorry it has taken me so long to get to this. I have updated the codebase with your suggested fix of removing the .Substring(1), as the VirtualPathUtility methods should handle both scenarios. Thanks for the thorough issue report!
I've release to NuGet the fix as version 2.0.3.
https://www.nuget.org/packages/AspNetBundling/2.0.3
Cheers,
Ben


update xsimd to version 9.0.1

xsimd version 9.0.1

[X] Check the upstream
https://github.com/xtensor-stack/xsimd/tree/9.0.1

[X] Check the pinnings

[X] Check the changelogs
There is currently no changelogs so the pull requests were reviewed instead
https://github.com/xtensor-stack/xsimd/pulls

[X] Additional research
https://github.com/conda-forge/xsimd-feedstock/issues

There is currently an open issue with version 9.0.1
We might need to keep an eye on the build if we deside to move forward

[X] Verify the dev_url
https://github.com/xtensor-stack/xsimd

[X] Verify the doc_url
https://xsimd.readthedocs.io/en/latest/

[X] License is spdx compliant
BSD-3-Clause

[X] License family is present
BSD

[X] Verify that the build_number is correct

[X] Verify if the package needs setuptools
The package is a C/C++ package so we do not need setuptools

[X] Verify if the package needs wheel
The package is a C/C++ package so we do not need wheel

[X] pip in the test section
The package is a C/C++ package so we do not need pip

[X] Veriy the test section

[X] Verify if the package is architecture specific or Noarch

[X] Verify that private modules are not mentioned on the recipe For example: (_private_module)

Results:
Based on the research findings and the results we can conclude
that it might be ok to update xsimd to version 9.0.1

Artifacts haven't been created. I'll reopen the PR

ask 'parse_webhook_event': Exception encountered during task execution!
Traceback (most recent call last):
  File "/home/builder/miniconda3/envs/prefect/lib/python3.9/site-packages/prefect/engine/task_runner.py", line 880, in get_task_run_state
    value = prefect.utilities.executors.run_task_with_timeout(
  File "/home/builder/miniconda3/envs/prefect/lib/python3.9/site-packages/prefect/utilities/executors.py", line 468, in run_task_with_timeout
    return task.run(*args, **kwargs)  # type: ignore
  File "<string>", line 103, in parse_webhook_event
  File "<string>", line 186, in decide
  File "/home/builder/miniconda3/envs/prefect/lib/python3.9/site-packages/flows/commons.py", line 760, in github_status_report
    if is_newest_build() is False:
  File "/home/builder/miniconda3/envs/prefect/lib/python3.9/site-packages/flows/commons.py", line 738, in is_newest_build
    if flow_runs[0].id != prefect.context.get("flow_run_id"):
  File "/home/builder/miniconda3/envs/prefect/lib/python3.9/site-packages/box/box_list.py", line 68, in __getitem__
    return super(BoxList, self).__getitem__(item)
IndexError: list index out of range

Task 'parse_webhook_event': Finished task run for task with final state: 'Failed'

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_90vkogaq18/clone/recipe/meta.yaml:39: missing_license_url: The recipe is missing a license_url
WARNING: /tmp/abs_90vkogaq18/clone/recipe/meta.yaml:39: missing_doc_source_url: The recipe is missing a doc_source_url
Warnings were found


Frontend folder creation permissions issue

Hi there, thanks for the wonderful project! When setting up and running the app locally, I'm getting an HTML page with no styles. It appears that none of the frontend public/ dirs are getting created.
I'm running on Pop_OS 22.04.
helloflask-css-1       | mkdir: cannot create directory '../public/css': Permission denied
helloflask-js-1        | mkdir: cannot create directory '../public/js': Permission denied

I am exporting linux ids in the env file as recommended:
export UID=1000
export GID=1000

I've also tried modifying the folder creation code in the Dockerfile as follows:
RUN mkdir -p /app/public \
  && chown node:node -R /app/public \
  && if [ "${NODE_ENV}" != "development" ]; then \
  ../run yarn:build:js && ../run yarn:build:css; fi

Since it seems to be a permissions error with the node user, I thought this might fix it but am unfortunately seeing the same error.

Hi,
If you run the id command from your terminal do you get back 1000 for both your id and gid?

Yes:
uid=1000(cmac) gid=1000(cmac) groups=1000(cmac),4(adm),27(sudo),123(lpadmin)

If you run ls -la in the root of the project what is the output? Is everything recursively owned by cmac:cmac?
I'm guessing maybe not since Docker isn't in the output of id, do you run Docker commands with sudo? You can fix that by running sudo groupadd docker and then re-logging into your X session (opening up a new terminal isn't enough) and verify Docker's group is attached to your user with id. Then you can run sudo chown -R cmac:cmac . in the root of your project to get files owned by your user.

 When running sudo groupadd docker, it says group 'docker' already exists.
When I do cat /etc/group I do see that:

docker:x:999:
cmac:x:1000:

Did the id get set incorrectly for docker, should it be 1000?

Oh sorry, I meant to say to run  sudo usermod -aG docker $USER, the first command only creates the group.
Docker being 999 is ok, it's a system level group. The files will still (or should be) still owned by cmac.

My docker group is now as follows: docker:x:999:cmac
I blew away all the containers / volumes / images, restarted the computer, and unfortunately am still seeing the error despite this group and ls -la permissions looking OK.
I briefly tried moving the mkdir commands from out of the run scripts and into the Dockerfile, but then saw more permission issues with esbuild:
helloflask-js-1        | ✘ [ERROR] Failed to create output directory: mkdir /app/public/js: permission denied
helloflask-js-1        |
helloflask-js-1        | ✘ [ERROR] Failed to create output directory: mkdir /app/public/js: permission denied
helloflask-js-1        |
helloflask-js-1        | ✘ [ERROR] EACCES: permission denied, copyfile 'static/safari-pinned-tab.svg' -> '../public/safari-pinned-tab.svg' [plugin copy-static-files]
helloflask-js-1        |
helloflask-js-1        |   This error came from the "onEnd" callback registered here:
helloflask-js-1        |
helloflask-js-1        |     /node_modules/esbuild-copy-static-files/index.js:41:10:
helloflask-js-1        |       41 │     build.onEnd(() => fs.cpSync(src, dest, {
helloflask-js-1        |          ╵           ~~~~~
helloflask-js-1        |
helloflask-js-1        |     at setup (/node_modules/esbuild-copy-static-files/index.js:41:11)
helloflask-js-1        |     at handlePlugins (/node_modules/esbuild/lib/main.js:1292:21)
helloflask-js-1        |     at buildOrContextImpl (/node_modules/esbuild/lib/main.js:978:5)
helloflask-js-1        |     at Object.buildOrContext (/node_modules/esbuild/lib/main.js:786:5)
helloflask-js-1        |     at /node_modules/esbuild/lib/main.js:2185:68
helloflask-js-1        |     at new Promise (<anonymous>)
helloflask-js-1        |     at Object.context (/node_modules/esbuild/lib/main.js:2185:27)
helloflask-js-1        |     at Module.context (/node_modules/esbuild/lib/main.js:2025:58)
helloflask-js-1        |     at file:///app/assets/esbuild.config.mjs:24:31
helloflask-js-1        |
helloflask-js-1        | 3 errors
helloflask-css-1       |
helloflask-css-1       | Rebuilding...
helloflask-css-1       | [Error: EACCES: permission denied, mkdir '../public/css'] {
helloflask-css-1       |   errno: -13,
helloflask-css-1       |   code: 'EACCES',
helloflask-css-1       |   syscall: 'mkdir',
helloflask-css-1       |   path: '../public/css'
helloflask-css-1       | }

Who owns the public/js directory on your file system? Try running ls -la public.

public/js isn't getting created due to the mkdir commands failing.
Here's what public looks like:
➜  helloflask git:(main) ✗ ls -la public
total 8
drwxrwxr-x  2 cmac cmac 4096 Aug  1 10:36 .
drwxrwxr-x 12 cmac cmac 4096 Aug  1 16:26 ..
-rw-rw-r--  1 cmac cmac    0 Aug  1 10:36 .keep

Ok, what if you run docker compose run web mkdir public/js. Does the directory get created or do you get the same permission error?

➜  helloflask git:(main) ✗ docker compose run web mkdir public/js
[+] Creating 2/0
 ✔ Container helloflask-redis-1     Created                                                                                0.0s
 ✔ Container helloflask-postgres-1  Created                                                                                0.0s
[+] Running 2/2
 ✔ Container helloflask-postgres-1  Started                                                                                0.3s
 ✔ Container helloflask-redis-1     Started                                                                                0.3s
mkdir: cannot create directory ‘public/js’: Permission denied

Same error

What does docker compose run web id return?

uid=1000(python) gid=1000(python) groups=1000(python)

Also ran these just to see:
➜  helloflask git:(main) ✗ docker compose run js id
uid=1000(node) gid=1000(node) groups=1000(node)
➜  helloflask git:(main) ✗ docker compose run css id
uid=1000(node) gid=1000(node) groups=1000(node)

Those outputs look good.
How did you install Docker on Linux? Was it through Docker Desktop or straight through Docker's installation for Ubuntu?

I installed it via Docker Desktop
➜  helloflask git:(main) ✗ docker compose version
Docker Compose version v2.19.1
➜  helloflask git:(main) ✗ docker --version
Docker version 24.0.5, build ced0996
https://docs.docker.com/engine/install/ubuntu/
Did the first four steps here, and then followed the Docker Desktop installation from the same site.

If the above works I'd suggest completely removing all traces of Docker Desktop, opening a new terminal and then following https://docs.docker.com/engine/install/ubuntu/.
The TL;DR is you only need to run:
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh ./get-docker.sh

Then for good measure chown -R cmac:cmac in the root of the project and then build + up the project with the volume mounts in tact.

Bingo! That did it, app is now running with styles.
Wow, thanks both for being a docker wizard and devoting so much time to this today!

No problem. It's all working with volumes now too right?
Docker Desktop for Linux is still pretty new, there's a couple of rough edges. I'm sure it'll get fixed in due time.

Yep, volumes are back in!


Support window.history

Hi,
Either I've miss something or not, but the README doesn't make any mention of window.history
I was trying to test my back button that basically does window.history.back() but my test was still returning to the previous page 😅
In the controller that contain the goBack function I've added
import window from 'ember-window-mock';
and in the test I've added both
import { setupWindowMock } from 'ember-window-mock';
and
  setupWindowMock(hooks);
Is this out of scope to support things like that with history or should I do it another way ?
Thanks for your help

It is basically a missing feature! 🙂
Keeping this here as a feature request. But not sure if I am able to implement this in the foreseeable future. PRs certainly welcome...


chore: test webpacking

Recently there was a regression in the NodeJS readable-stream package which required webpack configs to polyfill the stream package.
This adds a test to make sure no such regressions are introduced into our codebase by readable-stream or any other package in the future.
This PR is blocked until https://github.com/nodejs/readable-stream/issues/516 is resolved. I have proposed a fix upstream in https://github.com/nodejs/readable-stream/pull/519.

@jeswr so since this was merged  we dont need this PR anymore right? just a bump on readable-stream?

@chelseapinka  - this PR is for regression testing so we want to keep it and merge it. I tried running this branch on 4.4.1 but discovered this issue - I will try again shortly on 4.4.2 which was just released


FYI Sherpa-onnx in TTS-Wrapper

Just a quick FYI..
I've VERY QUICKLY (so bugs beware) added sherpa-onnx to this python tts-wrapper..
https://github.com/willwade/tts-wrapper?tab=readme-ov-file#sherpa-onnx
We do fun things like listing available voices, auto downloading models and running them.. then our abstract class deals with playing, pausing, streaming audio etc. Many aspects like pitch, volume control and SSML we obviously cant deal with sherpa-onnx. Or word events.. But hey..
I'm really just focusing on MMS models right now.. I'd love a lovely JSON file of all TTS models we could use if anyone has it and I can add them.
Needs a heap loads of testing and very welcoming to PR's. Particularly rewriting automated tests and checking/improving audio playback.. I feel there is a lag somewhere and I cant figure out where..
Use like
pip install "tts-wrapper[sherpaonnx] @ git+https://github.com/willwade/tts-wrapper"

then

from tts_wrapper import SherpaOnnxClient, SherpaOnnxTTS
try:
    client = SherpaOnnxClient(model_path=None, tokens_path=None)
    # or
    # client = SherpaOnnxClient(model_path=None, tokens_path=None, voice_id="eng")
    # where voice_id is a id from the get_voices - typically an iso code from mms
    # Initialize the TTS engine
    tts = SherpaOnnxTTS(client)

    # Get available voices
    voices = tts.get_voices()
    print("Available voices:", voices)

    # Set the voice using ISO code
    iso_code = "eng"  # Example ISO code for the voice
    tts.set_voice(iso_code)

    # Define the text to be synthesized
    text = "Hello, This is a word timing test"
    start_time = time.time()
    tts.speak(text)

except Exception as e:
    print(f"Error: {e}")

Take a look at play/pause/resume etc..
https://github.com/willwade/tts-wrapper?tab=readme-ov-file#streaming-and-playback-control

any advice welcome on how those tts releases are formatted :)

I suggest that you handle models like

vits-zh-hf-xxx
sherpa-onnx-vits-xxx
icefall-vits-xxx
separately.

@csukuangfj the models released under your tts tag release. What action generates those? I'm wondering about creating a json file of all models available

@csukuangfj the models released under your tts tag release. What action generates those? I'm wondering about creating a json file of all models available

Please see
https://github.com/csukuangfj/models/tree/small-fixes/.github/workflows
All workflows containing vits in the above link.

Great. I think its probably best I do the hackier scraping approach
https://github.com/willwade/tts-wrapper/blob/main/tts_wrapper/engines/sherpaonnx/publishedmodels.json
https://github.com/willwade/tts-wrapper/blob/main/tts_wrapper/engines/sherpaonnx/createindex.py


Typo in subtitle

Redis Cluster Contoller with web interface should be Redis Cluster Controller with web interface

Thanks. Fixed.


Add v0.0.3 of operator to OpenShift and Upstream Community Operators

Since most of the functionality of this operator is useful to the upstream Kubernetes community, consider making v0.0.3 available to both the OpenShift and upstream communities on OperatorHub.io.

right now the operator requires routes, which are not available in Kubernetes. However it may be possible to add a flag to disable the route controller and use the rest of the functionalities in a Kubernetes  instance.

Would it be possible on startup to only enable the route controller if the route api resource is available?

I think it should be possible, and this is a good idea.


fix report in a case of afterEach conditional fail

Description of the Change
In our wiki, describe  "Conditionally fail a test after completion".
But it behaves like the explanation.
If a test failed after it already passed, the final report says both the test passed and the test failed. I referred #1944 .

Alternate Designs
I don't have an idea now.

Why should this be in core?
Users could get a correct report.

Benefits
We can report correctly. It is confused if same test place on both pass and failure.

Possible Drawbacks
It seems a broken change because report order could be changed in some edge case.
And this PR is inspired by #1944 , the PR's owner didn't sign CLA. I'm not sure whether we can make this code change or we should get permission from the one.

Applicable issues
close #3345
close #1635

Coverage increased (+0.1%) to 90.154% when pulling ce974dc22f3962169a1ac88c9a457fc6d08c7778 on outsideris:issue-3345 into 99c2f8aa7bf4184fdf694887ef740f31fe29f1f2 on mochajs:master.

How about semver-minor?
I think it is correct behavior, but it works as previous behavior for a long time even if our wiki describes it.
Now, checking test passed ran in afterEach, not run.
This change pass count/failure count.

Can we fix spelling in PR title?

I fixed type in commit message as well and linting error. CI should be passed.

@outsideris, @boneskull,
issue #3569 may be implicating this PR. Can you confirm?
If so, we may need to back this out...

@boneskull, this needs to get unmerged until the order is corrected. See #3569.

I'll reverse this.

@outsideris Hello, I am facing this issue... You seem to have an idea on how to solve it:

We should check afterEach hooks to support conditional fail and report it in a correct order.

How can I help?


Formatting Bug

What is your Quests version / build number (do not say "latest")?
5.0.3-b474
Describe the problem and how to replicate it.
These 2 specific lines do not follow any rational formatting used elsewhere in the file:
completed: "%#555555%%bold%Test"
redoCompleted: "%#555555%%bold%Test"
I have tried the typical %#fff000% that the other lines of the lang file use and work fine, but for some reason these 2 do not. I have tried every formatting way I know, the built in &e &l type MC codes, normal rgb, &#fff000, etc and it seems to just randomly choose the color. #555555 is a dark gray, and for some reason it shows as a Dark purple. The %bold% appears to work still.
Also, the ( ) on the message is not listed in the lang file to edit, but still appears in-game.

Any console errors to share?
n/a

If applicable, can you provide an example quest from quests.yml?
Any/all quests

Strings that have item/entity/enchantment names like this are sent to the client for translation via LocaleLib. I think what's happening is the hex format isn't converting well to the Minecraft json command which is necessary for translation. Part of it seems to be dark purple because only the last char is being applied there (so §5).
I may find time to look into this further, but please understand something like this is extremely low priority.


mpir build generates generic library

I'm building mpir:x64-windows-static on a Broadwell machine, I should be getting the Haswell binaries, but instead I get the generic binaries, which are, other then for educational purposes, rather useless.
The Haswell build is in the .sln file, I guess there need to be several mpir packages (mpir[Haswell] etc.), one per supported architecture.

Hi @degski, sorry for late.
Could you provide some repro steps?
Thanks.

We don't have enough information to solve this issue, unfortunately; if you have any more information to help us solve this, please reopen!


Data Stoarge Example

I need guidance on using Rust for local storage in mobile apps, specifically for iOS and Android. I want to store app state, tokens, and similar data.
I'm considering a file-based approach like SQLite, but I'm unsure how to manage the connection paths across different platforms.
How can I achieve this?
Another approach i thought of is letting the storage to be handled by flutter and invoking the fetching and adding data from rust.
But again i didn't  understand the docs of invoking dart function from rust.

Hi, just write arbitrary Rust code - flutter_rust_bridge does not limit the ways of doing storage. There are many different ways, and here are some quick suggestions:

I'm considering a file-based approach like SQLite, but I'm unsure how to manage the connection paths across different platforms.

One way may be,

https://pub.dev/documentation/path_provider/latest/path_provider/getApplicationSupportDirectory.html in dart to get a path you like
pass path to Rust as an argument, and in rust you play with sqlite etc

But again i didn't understand the docs of invoking dart function from rust.

https://cjycode.com/flutter_rust_bridge/guides/direction/rust-call-dart
I guess maybe you need some background about Rust's async and impl and closures, because the example is using standard Rust. (No worries - everyone is not a Rust expert when born!)
// Rust
pub async fn rust_function(dart_callback: impl Fn(String) -> DartFnFuture<String>) {
    dart_callback("Tom".to_owned()).await; // Will get `Hello, Tom!`
}

// Dart
await rustFunction(dartCallback: (name) => 'Hello, $name!');

@anwarsalim08 if you want to use storage in flutter , I think using isar https://github.com/isar/isar is a good option. Besides, isar
is also built on rust. If you want to implement storage on your own with rust, you can try sqlx https://github.com/launchbadge/sqlx . If you just want to storage some k-v pairs, I think shared-preference is better.

Hello both,
The main idea i am going through this route is that i want the entire business logic to be on the rust side, including the storing and retrieving app state. The main issue i had is that i didn't know how to get the path which @fzyzcjy illustrated.
Therefore, i will attempt to use https://github.com/vincent-herlemont/native_db and see how this goes.

@anwarsalim08 emmm.... as far as I know, only static function from dart side can be called in c++. I am not sure if flutter_rust_bridge can call functions like setState or something else （I still use version 1.82 in my project）. If it could, that is awsome

as far as I know, only static function from dart side can be called in c++. I am not sure if flutter_rust_bridge can call functions like setState or something else （I still use version 1.82 in my project）. If it could, that is awsome

@guchengxi1994 You can call everything: https://cjycode.com/flutter_rust_bridge/guides/direction/rust-call-dart

@fzyzcjy Great!

I am a bit late to the party ... @anwarsalim08 I hope you found a way to implement it (if you have a public repo showcasing this I would be interested).
I not: I try the same thing and made an example application for that: https://github.com/patmuk/flutter-rust-bridge_crux_style

I am getting the "Application Support Dir" path from Flutter.

here I store the app state as a binary via Serde, completely from rust.

Flutter is the UI layer only. Keep in mind that any user input/files need to go through Dart to Rust. This is a trivial method call, but not zero-cost, as FFI requires copying the content. The opposite direction (Rust -> Flutter) is zero-cost (just a pointer reference).

I follow an event-driven approach, inspired by crux:
-- Any action in Flutter can execute an Event, which is a enum in Rust, processed by a "processEvent" function call.
-- This call returns a List of Effects, which are instructions to Flutter what to do. Implemented on the Flutter side. For example, the return Effect could be "render", which can include a viewModel. Fuller would implement presenting this data.

I don't plan to have any state management in Flutter. I don't think setState needs to be called by Rust. I am doing it indirectly: The returned Effect is triggering a setState call on the Flutter side. So, maybe this can be avoided, maybe it should be done more direct ... I set that up with FRB v1 (it is updated to FRB v2 now). I tried to convert it to stateless widgets, but I had troubles to call the rust-future more than the initial time.

Maybe this helps - and, @anwarsalim08, I am interesting to learn about your approach!

FFI requires copying the content

If you use rust auto opaque, then the states are always in rust side and does not require copying. But yes, if something was in dart and you want to transfer it to rust, it needs copying.

I had troubles to call the rust-future more than the initial time

Not sure, does #[frb(sync)] which gives you sync methods help?

I had troubles to call the rust-future more than the initial time

Not sure, does #[frb(sync)] which gives you sync methods help?

It is awesome how responsive you are!
Sorry for being unclear. I just recall that partially, but it was not about frb at all, more about when Flutter decides to repaint. My idea was to have stateless widgets only, and to keep the state on the rust side.
However, a button press, for example, triggered updating the state, but the widget would not rebuild and call a view() function from rust to see the update. This is simplified, but I realized that stateless widgets are quite static, and something up the tree needs to be statefull, so that a repaint can be triggered.
my view() function is async - but I don’t think making it sync would help.
Nevertheless, it is just cosmetic. I do have statefull widgets, and I call setState() to trigger a repaint - but the state is not with Flutter :)


manifest: update loramac-node

Update loramac-node to resolve #36074.
Note that this PR does not necessarily need to be merged due to #35892.
The purpose of this PR is to perform CI checking on the module PR.
The goal of cherry-picking the referenced commits before #35892 is to allow Zephyr v2.5 and Zephyr v2.6 users to use the fix without updating Zephyr to v2.6.99.

Potentially this revision update should be backported to the v2.6 (and v2.5?) branches?


Google and Brave working on example.py

hello , i checked your commit did not understand the changes , can you please explain