ci: relese SLSA Provenance and sign checksum file by Cosign

https://github.com/aquaproj/registry-tool/releases/tag/v0.1.6-2


Make it possible to checkout the repo under Windows

File paths containing ':' can not be checked out under Windows. This was
probably the reason that cargo refuses to publish a package containing
files with such file names. The exact seed name should however not
matter much, in the worst case it can probably be restored locally.
See https://github.com/image-rs/image/issues/915

@Shnatsel This is kind of awkward as it affects all repos which contain afl fuzzing seeds generated from a minimized, but automatically discovered fuzzing corpus. It occurred to me that you might be interested in this issue, and potentially have ideas on workaround, or better workflows to change that?

Ouch. Uuuh, you can safely rename the files, AFL doesn't really care what they're called. References to files from unit tests would have to be updated (if any), but that's it.
I don't think this is going to be solved in AFL upstream as there is no longer an AFL upstream, but you could open a feature request against afl-rs I guess?


1.08 release

Version 1.08:
New Converters:

RoboForm converter now available.
Keeper Desktop converter now available.
Txt2notes converter now available, converts text files into Secure
Notes.
F-Secure KEY converter now available.
Passwords Plus converter now available (OS X).

New Features:

Option --addfields or -a will create custom fields for non-mappable
fields instead of placing
them into notes.
Option --tags or -t will add the specified comma-separated list of
tags to each record.
The keepassx converter will decode and convert an entry's
attachment. It is placed in a folder
named 1P4_Attachments in the same location that the 1P4_import.1pif
file will be created.  An entry's
attachment is placed in a sub-directory named with the entry's
Title.
The vcard converter option --securenote will place vCard data into
a Secure Note, with custom fields
similar to an Identity.
The 1PIF module supports icons if either of the Perl 'GD' or
'Image::Magick' libraries are available.
The vCard converter will include icons when the --icon option is
specified (and the required
library is available - see previous note).
Added more import types to handysafe converter; added a multiple
field-matching system to assist
category detection.
The handysafe converter now has support for localalization (lang
nl-nl).  More languages will be added
as requested.
Languages directory for per-converter language translation files.
Added output diagnostic to onepif2html converter to indicate the
name of the created output file.
Add support for 1Password's 'Password' category.
The csv converter now accepts a Tags column.  The comma-separated
values within that column will be
imported as 1Password Tags.

Changed:

The --help option is a little more instructive.
Converter ewallet's combolock and voicemail categories go to the
Password category now.
Converter splashid's frequentflyer now maps to the 1Password
Rewards category.

Fixed:

Several fixes for the onepif2html print converter: strip the BOM on
Windows 1PIF exports; gracefully
handle unknown 1PIF typeNames; support the legacy typeNames allowed
in the Windows UI.
Minor Perl syntax changes throughout the code to satisfy Perl
versions > 5.16.
Remove extraneous, but harmless setting of imptypes in essetialpim
converter.
Remove extraneous comment in msecure converter; fixed duplicate key
in frequentflyer definition.
Splashid converter was not honoring --imptypes for user-defined
types (user defined types are
specified as 'userdefined'.
Splashid converter was not converting \b end of line characters
into newline characters in
an entry's notes section (Windows only).
The debug function unfold_and_chop() was not honoring its maxlen
parameter.
The debug function print_record was not outputing notes.
Date parsing was broken in some cases for converters ewallet and
lastpass.
Several ewallet converter fixes.
The safewallet converter was incorrectly detecting a web login
category as an irc category.
Several vcard converter fixes: 1) prevent vcard converter from
importing an encoded photo into the notes
section; 2) converter was bailing after the first entry in a list
of vcards.  3) Uses a new module for
parsing / packaging vCard data (Text::vFile::asData). 4) Handles
vCard exports via iCloud.
The handysafe converter was not picking up root-level nodes.
Some debug output errors in Utils::PIF.pm.
A date converter routine for some converters could cause an error
under anomalous conditions - affected
converters: dataguardian, ironkey, keepass2, keepassx, keychain,
passwordagent, passworddepot, spbwallet.
The datavault converter on Windows could botch some multiline
entries in the notes section.
The onepif2html converter was not outputing a label for unlabeled
URLs.
The onepif2html converter was not handling the Password category.
Converter keychain now avoids outputting a 0x0 (nil) hexvalue as a
URI protocol.
Converter keychain export instructions for iCloud keychain export
was missing part of the fully-qualified
keychain name (e.g. local-icloud should have been
local-icloud.keychain).

Internal Changes:

Miscellaneous code refactoring and consolidating.
New module Utils::Normalize.
Simplify the lastpass converter's %card_field_specs table.
convert_to_1p4 will now accept and pass to a converter more than a
single filename argument.
Modified the %card_field_specs table to include custom field
definitions within the table.
Made the normalize_card_data() function universal, and moved it to
Utils::PIF.pm.
Code updates to work with Perl versions newer than the old
requirement of Perl 5.16.
Debug output will include info about the export file supplied on
the command line.
Many code cleanups.

Wow! Crazy big. Thanks, Mike!

Trying to keep you honest.  :-)

On Jan 12, 2016, at 4:20 PM, Rob Yoder<EMAIL_ADDRESS>wrote:
Wow! Crazy big. Thanks, Mike!


Wip: Forward ref

Hi, @righ ! Thank you for this awesome library!
I am working on a project that requires displaying Jupyter notebooks in a next.js website. However, I run into issues when dynamically loading the component using next/dynamic.
One thing is that I would like to know when the component has loaded. I know you can use the loading attribute  but I can't modify the state of the parent component in that case.
The other reason is, that I would like to parse the HTML output from the react-ipynb-renderer  component and generate a table of contents by doing a .querySelectAll('h1,h2,h3') in that component. When running in a simple React app, that is fine since I can just use a ref in the parent component but when using the Lazy Load in next.js with {ssr: false}, this makes things complicated since I don't know when the notebook has rendered.
Either way, I think it will be generally useful to be able to pass a ref to this notebook regardless of this particular use case.
What do you think of this? Also, in order to merge this, apart from examples, what else do I need to add to make this change?
Thank you!

Hi @righ ,
Thank you for the comments! Sorry for disappearing for a while there.
I will see what I can do about this. Due to changed requirements, I will no longer need this library but I still want to support it. I will get back to this as soon as time permits.
Again, thank you!

This PR is closed as it has been addressed by #32 and 2c309f6b7b. Thank you for the good idea.


improve the kubeflow.org landing page

Improvements for the kubeflow.org page:

[ ] Most users will never see the "cards" at the bottom of the page (the blue part expands to 100% screen height, and most users will miss the scroll bar):

ACTION: reduce the blue section to be 75% of the screen height, so users know there is further content

[ ] The content of the "cards" at the bottom is out of date

ACTION: update the content of the cards

Current image of kubeflow.org landing page:

/priority p2

@RFMVasconcelos what are your thoughts?

Thanks for starting this Mathew. I do believe there is room to improve here!
+1 to both suggestions: reduce height and update cards

/assign


After clicking Join, the page will refresh, and the login cannot be successful

I  local install the project on macOS 10.15 locally， beside using coturn， I follow the install guild，Howerer，when I click Join Button， the page refreshed and did not enter the chatroom，could you help me, this trouble me several days，thank you！

How can I enter the next step to chat?

Hi, It's probably some problem/bug related with your browser interface language (chinese?)

Provide me an information about your browser's lang by putting the below code to the console and let's us know what;s the result.
console.log("window.navigator.userLanguage: " + window.navigator.userLanguage + " | window.navigator.language: "+ window.navigator.language)

Provide your envirnonment  setup you use:

browser name & version,
node.js version,
package manager name & version,
branch name (i guess it's master)

Can you try to run edumeet on a system/browser with a native english interface and see if the problem still occurs?

Try to run a develop version where this problem may be already solved (AFAIR ther was some problem with "chinese" languages that has been fixed on develop  branch

Hi @roman-drozd-it,
Version used,
Npm Version: 6.14.15
Node Version: 12.22.1
Branch: Master
Browser: Chrome latest version
I am facing the similar issues and here is the details which you requested, this is the latest git clone.
Previously I was using Node version: 10.19.0 and everything was fine.
Now I have been facing this issue,
When I do npm start at edumeet/server I have been facing some issues so upgraded to V12.22.1.
Have a look at the console . it is nothing more than React and Material UI warning nothing more than that.

I have created my own Certificate and where I have changed the Local host as the IP address for the local development.
Will be great if you can suggest some ideas

I have same problem - reload after login button, but the only interesting message in console is: WebSocket connection to '....' failed: WebSocket is closed before the connection is established. I have configured correct listenIP in webRtcTransport and have good certificates. Any suggestion?

I have set up the window.navigator.language to be "en",but the console still show the error in the first picture

I have seted up the window.navigator.language to be "en",but the console still show the error .If I click the Join button,the network will show Provisional headers are shown.In the edumeet source code,i have changed the mediasoup version into 2.6.19 because version of 3 i can't successfully npm install,and the redis version change to 4.0.3 so that when I npm start in the server there no error in the terminal.

browsername:chrome
node.js version:13.7.0
npm:6.13.6
branch name:master

I have seted up the window.navigator.language to be "en",but the console still show the error .If I click the Join button,the network will show Provisional headers are shown.In the edumeet source code,i have changed the mediasoup version into 2.6.19 because version of 3 i can't successfully npm install,and the redis version change to 4.0.3 so that when I npm start in the server there no error in the terminal.

browsername:chrome
node.js version:13.7.0
npm:6.13.6
branch name:master

I have seted up the window.navigator.language to be "en",but the console still show the error .If I click the Join button,the network will show Provisional headers are shown.In the edumeet source code,i have changed the mediasoup version into 2.6.19 because version of 3 i can't successfully npm install,and the redis version change to 4.0.3 so that when I npm start in the server there no error in the terminal.
image
image
image
browsername:chrome
node.js version:13.7.0
npm:6.13.6
branch name:master

I have the same problem. I get the following message in Firefox dev tools:
Firefox can’t establish a connection to the server at wss://localhost:8443/socket.io/?peerId=7vupbdr1&roomId=5bw9bp4m&EIO=4&transport=websocket&sid=pYAWuTe1u59wmsKKAAAI.
edumeet:ERROR:JoinDialog Error checking login status +0ms SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

I changed server code  in runWebSocketServer()
 io = require('socket.io')(mainListener, { cookie: false, cors: true });
I ran app by npm run dev


Define the specification process

How we manage specification (as much for us and the contributors)
How we expect people to define them
What is our process to manage them (Tommy review them...)

@qdequele & @tpayet, please start to add the ideas you have about this process or list things that were already discussing before our team arrived.

@qdequele & @tpayet, please start to add the ideas you have about this process or list things that were already discussing before our team arrived.

@tpayet started to work on it. Can you share the work done so far?

It's now on the PM plate.


Smart Contract issue For BEP20

Ive used on 11.02.2022 the service Vittominacori generator, after i paid 2BNB fees, for the feature Common BEP20 ive got the token in my metamask, called Triumph, smart contract address :0x8f99d8a9dA753d74008C9490a8b57438A240eF98 few days ago, browsing into BSC scan, in search box ive inserted the smart contract address of the token ive got it, and surprise!!! while ive  press Contract button said that 0x8f99d8a9dA753d74008C9490a8b57438A240eF98is asigned to a  Similar Match Source Code
Note: This contract matches the deployed ByteCode of the Source Code for Contract [0xA6B077aba99583F8f2AA03e2eF0DF75136c7E59A](https://bscscan.com/address/0xA6B077aba99583F8f2AA03e2eF0DF75136c7E59A

Hello, having similar match is not an issue as it means that your code is similar to others built on token generator.
You could try to verify your contract again by copy/paste source code in verify contract page on bscscan https://bscscan.com/verifyContract.

Compiler: 0.8.11+commit.d7f03943.Emscripten.clang
Optimization: Yes
Runs (Optimizer): 200

Note: it says it is temporary not available so please try again later with your user credentials.

Thank U! Understood! ;)


HPC toolkit no longer works with a2 instances

Describe the bug
The controller node fails to initialise Slurm with node groups of a2 instance types (e.g. a2-highgpu-8g - where the suffix of the instance name refers to the number of GPUs and not the number of CPUs), failing with the logs:
2023-08-07 12:04:08,247 INFO: Setting up controller
2023-08-07 12:04:08,249 INFO: installing custom scripts: compute.d/ghpc_startup.sh,controller.d/ghpc_startup.sh,partition.d/a2/ghpc_startup.sh,partition.d/dev/ghpc_startup.sh
2023-08-07 12:04:08,249 DEBUG: install_custom_scripts: compute.d/ghpc_startup.sh
2023-08-07 12:04:08,251 DEBUG: install_custom_scripts: controller.d/ghpc_startup.sh
2023-08-07 12:04:08,252 DEBUG: install_custom_scripts: partition.d/a2/ghpc_startup.sh
2023-08-07 12:04:08,254 DEBUG: install_custom_scripts: partition.d/dev/ghpc_startup.sh
2023-08-07 12:04:08,259 DEBUG: compute_service: Using version=v1 of Google Compute Engine API
2023-08-07 12:04:44,512 WARNING: core count in machine type a2-highgpu-8g is not an integer. Default to 1 socket.
2023-08-07 12:04:44,512 ERROR: invalid literal for int() with base 10: '8g'
--
  File "/slurm/scripts/setup.py", line 1071, in setup_controller
    gen_cloud_conf()
  File "/slurm/scripts/setup.py", line 341, in gen_cloud_conf
    content = make_cloud_conf(lkp, cloud_parameters=cloud_parameters)
  File "/slurm/scripts/setup.py", line 330, in make_cloud_conf
    lines = [
  File "/slurm/scripts/setup.py", line 333, in <genexpr>
    *(partitionlines(p, lkp) for p in lkp.cfg.partitions.values()),
  File "/slurm/scripts/setup.py", line 272, in partitionlines
    group_lines = [
  File "/slurm/scripts/setup.py", line 273, in <listcomp>
    node_group_lines(group, part_name, lkp)
  File "/slurm/scripts/setup.py", line 210, in node_group_lines
    machine_conf = lkp.template_machine_conf(node_group.instance_template)
  File "/slurm/scripts/util.py", line 1540, in template_machine_conf
    _div = 2 if getThreadsPerCore(template) == 1 else 1
  File "/slurm/scripts/util.py", line 1117, in getThreadsPerCore
    if not isSmt(template):
  File "/slurm/scripts/util.py", line 1099, in isSmt
    machineTypeCore: int = int(matches["core"])
ValueError: invalid literal for int() with base 10: '8g'

Related commits:

https://github.com/SchedMD/slurm-gcp/commit/9dc7bb7f100388e9b4dd1cdd4eef64de49df4ece by @bsngardner
https://github.com/SchedMD/slurm-gcp/commit/6cb0fd3f706ee5fc742a7c243bf2648ee45a9729 by @bsngardner
https://github.com/SchedMD/slurm-gcp/commit/c5095d0bc2f38054d678e9a32568883dec0132c5 by @SkylerMalinowski

Steps to reproduce
Steps to reproduce the behavior:

Use an example blueprint that uses a2 instances, e.g. https://github.com/GoogleCloudPlatform/hpc-toolkit/blob/main/examples/ml-slurm.yaml
./ghpc create ml-slurm.yaml
./ghpc deploy ml-example
log into the controller and inspect /slurm/scripts/setup.log

Expected behavior
The cluster to successfully initialise
Actual behavior
An uninitialised cluster with no ability to schedule work
Execution environment

OS: macOS
Shell: zsh
go version: 1.20.6

Additional context
Upstream bug:

https://bugs.schedmd.com/show_bug.cgi?id=17363

I think it may have been introduced in #1661

This looks like it's a problem beyond just #1661 - the regression has made it into the base image projects/schedmd-slurm-public/global/images/slurm-gcp-5-7-debian-11-1691089583 (latest for image family slurm-gcp-5-7-debian-11) so appears even when deploying from an older version of ghpc (e.g. 1.19.1)

The previous image in the family, slurm-gcp-5-7-debian-11-1686755499, does not have this issue. It also has none of the fixes released with #1661.

Thank you for the base image update - that has definitely mitigated the issue for us

Closing the issue, feel free to reopen though.


[Excel] Add new error codes

Adding new error codes RequestPayloadSizeLimitExcceded and ResponsePayloadSizeLimitExcceded. Also adding other existing error codes that were missing from docs, and updating article title.

Docs Build status updates of commit 5722f1b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/excel-add-ins-error-handling.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 996cbf0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/excel-add-ins-error-handling.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 9ba161f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/excel-add-ins-error-handling.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a702465:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/excel-add-ins-error-handling.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b87dc13:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/excel-add-ins-error-handling.md
:bulb:Suggestion
View
Details

docs/excel/excel-add-ins-error-handling.md

Line 50, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4424394:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/excel-add-ins-error-handling.md
:bulb:Suggestion
View
Details

docs/excel/excel-add-ins-error-handling.md

Line 50, Column 1: [Suggestion-column-header-missing] Column headers are required for tables. Add appropriate header text. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 695c110:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/excel/excel-add-ins-error-handling.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


C++ project fails to compile due to use of protected keywords as variable names

Hiya!
I'm incorporating hpglib in a C++ ESP-IDF project and part of the library fails to build. The files, xplr_com_types.h and xplr_nvs.h, name a member variable, operator, and a parameter, namespace, respectively. These are both reserved C++ keywords.
Environment:

Machine: M1 Macbook Pro
OS: I'm using a Dev Container built from espressif/idf:v4.4.2
ESP-IDF: v4.4.2

Reproduction:
I have pushed an example that can be used to reproduce this error to this branch of a fork. To reproduce the issue:

Clone the fork and change to the example-failing-build-cpp branch.
cd to the XPLR-HPG-SW directory.
Configure the project with idf.py menuconfig.
Build the project with cmake --build build or idf.py build.

This is what I'm getting back:

Expand terminal output:
root@d5b552aa6e72:/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW# idf.py menuconfig
Executing action: menuconfig
Running cmake in directory /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DESP_PLATFORM=1 -DIDF_TARGET=esp32 -DCCACHE_ENABLE=1 /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW"...
-- -----------Package Info---------
--  XPLR_HPG_SW_PATH is /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW
--  XPLR_HPG_EXAMPLE_SELECTED: hpg_cell_mqtt_correction_certs
-- Loading  source files...
-- Loaded from: examples/cellular/02_hpg_cell_mqtt_correction_certs
-- Found Git: /usr/bin/git (found version "2.25.1")
-- Component directory /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib does not contain a CMakeLists.txt file. No component will be added
-- ccache will be used for faster recompilation
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- The ASM compiler identification is GNU
-- Found assembler: /opt/esp/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /opt/esp/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /opt/esp/tools/xtensa-esp32-elf/esp-2021r2-patch3-8.4.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32
--  -----------Board Info---------
--  IDF_TARGET = esp32
--  Board DIR =
--  ---------Board Info End---------
-- -----------Project Info---------
--  Building Component: hpglib
-- -----------Project Info---------
--  Building Component: xplr_mqtt
-- -----------Project Info---------
--  Building Component: xplr_wifi_starter
-- -----------Project Info---------
--  Building Component: xplr_ztp
-- -----------Project Info---------
--  Building Component: xplr_ztp_json_parser
-- Project sdkconfig file /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/sdkconfig
Loading defaults file /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/sdkconfig.defaults...

TERM environment variable is set to "xterm-256color"
Loaded configuration '/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/sdkconfig'
No changes to save (for '/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/sdkconfig')
Loading defaults file /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/sdkconfig.defaults...
root@d5b552aa6e72:/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW# cmake --build build/
[0/1] Re-running CMake...
-- -----------Package Info---------
--  XPLR_HPG_SW_PATH is /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW
--  XPLR_HPG_EXAMPLE_SELECTED: hpg_cell_mqtt_correction_certs
-- Loading hpg_cell_mqtt_correction_certs source files...
-- Loaded from: examples/cellular/02_hpg_cell_mqtt_correction_certs
-- Component directory /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib does not contain a CMakeLists.txt file. No component will be added
-- ccache will be used for faster recompilation
-- Building ESP-IDF components for target esp32
--  -----------Board Info---------
--  IDF_TARGET = esp32
--  Board DIR =
--  ---------Board Info End---------
-- -----------Project Info---------
--  Building Component: hpglib
-- -----------Project Info---------
--  Building Component: xplr_mqtt
-- -----------Project Info---------
--  Building Component: xplr_wifi_starter
-- -----------Project Info---------
--  Building Component: xplr_ztp
-- -----------Project Info---------
--  Building Component: xplr_ztp_json_parser
-- Project sdkconfig file /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/sdkconfig
Loading defaults file /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/sdkconfig.defaults...

Merged 1 ELF section
Successfully created esp32 image.
 -I/opt/esp/idf/components/esp_hw_support/port/esp32/private_include -I/opt/esp/idf/components/heap/include -I/opt/esp/idf/components/log/include -I/opt/esp/idf/components/lwip/include/apps -I/opt/esp/idf/components/lwip/include/apps/sntp -I/opt/esp/idf/components/lwip/lwip/src/include -I/opt/esp/idf/components/lwip/port/esp32/include -I/opt/esp/idf/components/lwip/port/esp32/include/arch -I/opt/esp/idf/components/soc/include -I/opt/esp/idf/components/soc/esp32/. -I/opt/esp/idf/components/soc/esp32/include -I/opt/esp/idf/components/hal/esp32/include -I/opt/esp/idf/components/hal/include -I/opt/esp/idf/components/hal/platform_port/include -I/opt/esp/idf/components/esp_rom/include -I/opt/esp/idf/components/esp_rom/include/esp32 -I/opt/esp/idf/components/esp_rom/esp32 -I/opt/esp/idf/components/esp_common/include -I/opt/esp/idf/components/esp_system/include -I/opt/esp/idf/components/esp_system/port/soc -I/opt/esp/idf/components/esp_system/port/public_compat -I/opt/esp/idf/components/esp32/include -I/opt/esp/idf/components/xtensa/include -I/opt/esp/idf/components/xtensa/esp32/include -I/opt/esp/idf/components/driver/include -I/opt/esp/idf/components/driver/esp32/include -I/opt/esp/idf/components/esp_pm/include -I/opt/esp/idf/components/esp_ringbuf/include -I/opt/esp/idf/components/efuse/include -I/opt/esp/idf/components/efuse/esp32/include -I/opt/esp/idf/components/vfs/include -I/opt/esp/idf/components/esp_wifi/include -I/opt/esp/idf/components/esp_event/include -I/opt/esp/idf/components/esp_netif/include -I/opt/esp/idf/components/esp_eth/include -I/opt/esp/idf/components/tcpip_adapter/include -I/opt/esp/idf/components/esp_phy/include -I/opt/esp/idf/components/esp_phy/esp32/include -I/opt/esp/idf/components/esp_ipc/include -I/opt/esp/idf/components/app_trace/include -I/opt/esp/idf/components/esp_timer/include -I/opt/esp/idf/components/mbedtls/port/include -I/opt/esp/idf/components/mbedtls/mbedtls/include -I/opt/esp/idf/components/mbedtls/esp_crt_bundle/include -I/opt/esp/idf/components/app_update/include -I/opt/esp/idf/components/spi_flash/include -I/opt/esp/idf/components/bootloader_support/include -I/opt/esp/idf/components/nvs_flash/include -I/opt/esp/idf/components/pthread/include -I/opt/esp/idf/components/esp_gdbstub/include -I/opt/esp/idf/components/esp_gdbstub/xtensa -I/opt/esp/idf/components/esp_gdbstub/esp32 -I/opt/esp/idf/components/espcoredump/include -I/opt/esp/idf/components/espcoredump/include/port/xtensa -I/opt/esp/idf/components/wpa_supplicant/include -I/opt/esp/idf/components/wpa_supplicant/port/include -I/opt/esp/idf/components/wpa_supplicant/esp_supplicant/include -I/opt/esp/idf/components/ieee802154/include -I/opt/esp/idf/components/console -I/opt/esp/idf/components/asio/asio/asio/include -I/opt/esp/idf/components/asio/port/include -I/opt/esp/idf/components/cbor/port/include -I/opt/esp/idf/components/unity/include -I/opt/esp/idf/components/unity/unity/src -I/opt/esp/idf/components/cmock/CMock/src -I/opt/esp/idf/components/coap/port/include -I/opt/esp/idf/components/coap/libcoap/include -I/opt/esp/idf/components/nghttp/port/include -I/opt/esp/idf/components/nghttp/nghttp2/lib/includes -I/opt/esp/idf/components/esp-tls -I/opt/esp/idf/components/esp-tls/esp-tls-crypto -I/opt/esp/idf/components/esp_adc_cal/include -I/opt/esp/idf/components/esp_hid/include -I/opt/esp/idf/components/tcp_transport/include -I/opt/esp/idf/components/esp_http_client/include -I/opt/esp/idf/components/esp_http_server/include -I/opt/esp/idf/components/esp_https_ota/include -I/opt/esp/idf/components/esp_https_server/include -I/opt/esp/idf/components/esp_lcd/include -I/opt/esp/idf/components/esp_lcd/interface -I/opt/esp/idf/components/protobuf-c/protobuf-c -I/opt/esp/idf/components/protocomm/include/common -I/opt/esp/idf/components/protocomm/include/security -I/opt/esp/idf/components/protocomm/include/transports -I/opt/esp/idf/components/mdns/include -I/opt/esp/idf/components/esp_local_ctrl/include -I/opt/esp/idf/components/sdmmc/include -I/opt/esp/idf/components/esp_serial_slave_link/include -I/opt/esp/idf/components/esp_websocket_client/include -I/opt/esp/idf/components/expat/expat/expat/lib -I/opt/esp/idf/components/expat/port/include -I/opt/esp/idf/components/wear_levelling/include -I/opt/esp/idf/components/fatfs/diskio -I/opt/esp/idf/components/fatfs/vfs -I/opt/esp/idf/components/fatfs/src -I/opt/esp/idf/components/freemodbus/common/include -I/opt/esp/idf/components/idf_test/include -I/opt/esp/idf/components/idf_test/include/esp32 -I/opt/esp/idf/components/jsmn/include -I/opt/esp/idf/components/json/cJSON -I/opt/esp/idf/components/libsodium/libsodium/src/libsodium/include -I/opt/esp/idf/components/libsodium/port_include -I/opt/esp/idf/components/mqtt/esp-mqtt/include -I/opt/esp/idf/components/openssl/include -I/opt/esp/idf/components/perfmon/include -I/opt/esp/idf/components/spiffs/include -I/opt/esp/idf/components/ulp/include -I/opt/esp/idf/components/wifi_provisioning/include -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/boards/xplr-hpg2-c214 -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/at_client/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/error/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/assert/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/location/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/mqtt_client/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/http_client/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/security/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/sock/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/ubx_protocol/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/spartn/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/utils/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/port/platform/common/debug_utils/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/cfg -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/type/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/port/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/network/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/device/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/common/short_range/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/ble/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/wifi/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/cell/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/gnss/api -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/port/platform/esp-idf -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/port/platform/esp-idf/mcu/esp32/cfg -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/port/clib -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/ubxlib/port/platform/common/mbedtls -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/common -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/nvs_service -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/com_service -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/mqttClient_service -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/httpClient_service -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/thingstream_service -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/location_service/location_service_helpers -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/location_service/gnss_service -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/hpglib/src/location_service/lband_service -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/xplr_ztp_json_parser/include -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/xplr_mqtt/include -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/xplr_wifi_starter/include -I/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/xplr_ztp/include -mlongcalls -Wno-frame-address  -fdiagnostics-color=always -ffunction-sections -fdata-sections -Wall -Werror=all -Wno-error=unused-function -Wno-error=unused-variable -Wno-error=deprecated-declarations -Wextra -Wno-unused-parameter -Wno-sign-compare -ggdb -Og -fmacro-prefix-map=/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW=. -fmacro-prefix-map=/opt/esp/idf=IDF -fstrict-volatile-bitfields -Wno-error=unused-but-set-variable -fno-jump-tables -fno-tree-switch-conversion -std=gnu++11 -fno-exceptions -fno-rtti -D_GNU_SOURCE -DIDF_VER=\"v4.4.2\" -DESP_PLATFORM -D_POSIX_READER_WRITER_LOCKS -MD -MT esp-idf/main/CMakeFiles/__idf_main.dir/hpg_cell_mqtt_correction_certs.cpp.obj -MF esp-idf/main/CMakeFiles/__idf_main.dir/hpg_cell_mqtt_correction_certs.cpp.obj.d -o esp-idf/main/CMakeFiles/__idf_main.dir/hpg_cell_mqtt_correction_certs.cpp.obj -c /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp
In file included from /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/boards/xplr-hpg2-c214/./../../../components/hpglib/src/com_service/xplr_com.h:26,
                 from /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:50:
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/boards/xplr-hpg2-c214/./../../../components/hpglib/src/com_service/xplr_com_types.h:97:33: error: expected type-specifier before '[' token
     char                operator[32];                   /**< Network operator name. */
                                 ^
In file included from /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/boards/xplr-hpg2-c214/./../../../components/hpglib/src/mqttClient_service/xplr_mqtt_client_types.h:27,
                 from /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/boards/xplr-hpg2-c214/./../../../components/hpglib/src/mqttClient_service/xplr_mqtt_client.h:26,
                 from /workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:51:
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/components/boards/xplr-hpg2-c214/./../../../components/hpglib/src/mqttClient_service/./../../../../components/hpglib/src/nvs_service/xplr_nvs.h:72:57: error: expected ',' or '...' before 'namespace'
 xplrNvs_error_t xplrNvsInit(xplrNvs_t* nvs, const char* namespace);
                                                         ^~~~~~~~~
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp: In function 'void configCellMqttSettings(xplrCell_mqtt_client_t*)':
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:491:28: error: cannot convert 'uMqttQos_t' to 'uCellMqttQos_t' in assignment
     client->settings.qos = U_MQTT_QOS_AT_MOST_ONCE;
                            ^~~~~~~~~~~~~~~~~~~~~~~
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp: In function 'void timerInit()':
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:530:5: warning: missing initializer for member 'timer_config_t::alarm_en' [-Wmissing-field-initializers]
     };
     ^
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:530:5: warning: missing initializer for member 'timer_config_t::counter_en' [-Wmissing-field-initializers]
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:530:5: warning: missing initializer for member 'timer_config_t::intr_type' [-Wmissing-field-initializers]
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:530:5: warning: missing initializer for member 'timer_config_t::counter_dir' [-Wmissing-field-initializers]
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:530:5: warning: missing initializer for member 'timer_config_t::auto_reload' [-Wmissing-field-initializers]
/workspaces/tmp/XPLR-HPG-software/XPLR-HPG-SW/examples/cellular/02_hpg_cell_mqtt_correction_certs/main/hpg_cell_mqtt_correction_certs.cpp:530:5: error: designator order for field 'timer_config_t::counter_dir' does not match declaration order in 'timer_config_t'
ninja: build stopped: subcommand failed.

Fix:
https://github.com/TendedLtd/XPLR-HPG-software/commit/6fcb6cb9237794e7b815713c57c0766a25dd2d44 fixes this by renaming the variables and https://github.com/TendedLtd/XPLR-HPG-software/commit/fb25c293957cd6ccf217dd9bff2d3f0a9434de97 fixes some C++ errors in hpg_cell_mqtt_correction_certs.cpp to prove that the fix works. The changes in prove-fb25c29-fixes-#8 allow the project to be built successfully.
Let me know if this is a valid issue. I have opened #9 in case you are accepting PRs.

Hello Francisco,
glad to here that you are working with our repo.
Unfortunately we are not testing the repo against C++ builds but your feedback is welcome.
We are going to release a new version of the repo with some additional features like dead reckoning, sd logging MQTT Thingstream update for cellular and more. The update version will be public next week and is highly recommended to try it.As soon as the updated version (v1.0) of the repo is up we will create a branch with your proposed changes to ease your migration to it.
I hope that works for you.
Best,
Alex

Hello Francisco, glad to hear that you are working with our repo. Unfortunately we are not testing the repo against C++ builds but your feedback is welcome. We are going to release a new version of the repo with some additional features like ntrip client support, dead reckoning, sd logging, MQTT Thingstream update for cellular and more. The update version will be public next week and is highly recommended to try it.As soon as the updated version (v1.0) of the repo is up we will create a branch with your proposed changes to ease your migration to it. I hope that works for you.
Best, Alex

Hiya Alex. Looking forward to trying it all. Thanks for the update!

Hello @fng97,
V1.0 of xplr-hpg is up, introducing more features to the kits. You can have a look at the release notes if you want.
A branch with related renamings to forbidden C++ keywords was also created that may be of interest for you.
V1.0 of the software brings some changes regarding the functionality of the location_service module but we tried to keep it as simple as possible for the end user.
If you find any difficulties migrating to the latest version please let me know and we will support you :)
Please feel free to close the issue if you are happy the created branch.
Best,
Alex

Hello @fng97, V1.0 of xplr-hpg is up, introducing more features to the kits. You can have a look at the release notes if you want. A branch with related renamings to forbidden C++ keywords was also created that may be of interest for you.
V1.0 of the software brings some changes regarding the functionality of the location_service module but we tried to keep it as simple as possible for the end user. If you find any difficulties migrating to the latest version please let me know and we will support you :) Please feel free to close the issue if you are happy the created branch.
Best, Alex

Hiya Alex. Very exciting! I'll be trying out NTRIP and SD card logging today!
Thanks for adding a branch with those changes. Just to clarify, will that branch be merged or is the intention that my submodule should track the commit in that branch?

If no other changes are needed for your C++ needs then please close the issue.
I will make sure to keep the renamed variables for the next release :)

Sure thing. I'll test this and then close the issue.


Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

i want to train a new wav2vec base model, when i run:
**fairseq-hydra-train
task.data=/Home/code/guozhi/slr
--config-dir ~/Home/code/guozhi/fairseq/examples/wav2vec/config/pretraining
--config-name wav2vec2_base_librispeech
**
there are some error:
**
Additional config directory '/home/gaogzh/Home/code/guozhi/fairseq/examples/wav2vec/config/pretraining' not found
Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
**
for why?

hi，bro. Have you finally solved the problem?

sure, i used the relative path to solve.

hi，bro. Have you finally solved the problem?

sure, i used the relative path to solve.

hi, bro, I also met the same problem, could you please tell me the specific operation, thanks!

hi, bro, I also met the same problem, could you please tell me the specific operation, thanks!


Add script to set demo up

We can then set this to run daily on Heroku scheduler to get rid of any cruft that may get added

Coverage remained the same at 83.284% when pulling fb4670416fe03f7837f2d904c3e4120df94b2df0 on feature-setup-demo into 527bccfdd7ff3eca593fb712a8dfc6edbbd70009 on master.


How do you use this?

Beyond the console command, I have no idea how to use this properly.

Console command


chore: add artistArtworksGridEnd

The type of this PR is: chore

This PR resolves ONYX-295
Description
This PR adds the right context module that is required to track taps on the create alert button in the footer of artist artworks grid.

PR Checklist (tick all before merging)

[x] If I've added a new file to the tree I've exported it from the common index.ts
[x] I've added comments with examples for any new interfaces and ensured that they're in the docs
[x] No platform-specific terminology has been used outside of click and tap (platform is inferred by the DB storing events)

cc @olerichter00


Functions to run kernels

Current behavior
To run a kernel, users write their own loop or scan manually. This can make it inconvenient for a user to quickly run an algorithm.
Desired behavior
A function which runs a kernel, like:
def run_sampling_algorithm(
    sampling_algorithm: SamplingAlgorithm, num_steps: int, initial_val, rng_key
):
    keys = jax.random.split(rng_key, num_steps)
    state = sampling_algorithm.init(initial_val)
    _, info = jax.lax.scan(
        lambda s, k: (sampling_algorithm.step(k, s)), state, keys
    )
    return info

could be made available. In addition, functions which both do tuning and subsequently run the kernel could be useful.
On the other hand, I understand that BlackJax is intended as an un-opinionated backend for other PPLs, so perhaps this is overkill.

Yeah we have discuss this in the past somewhere, the challenge is to have something flexible enough in case user wants to interact at different level of the sampling routine (and also work with all existing kernel), but at the same time not overly complicated.
However, we probably dont need to over engineer it: there are many sampling_routine in our example and test right now, so at the very least we should have a single sampling function so we can refactor out the repeated code.

@junpenglao @reubenharry I'd be happy to work on this if neither of you want to.

@reubenharry cool! I'll take a look and ping you here with updates

@reubenharry @junpenglao this is only my 3rd time contributing to open-source so forgive me for any naivete :). Inspired by both @reubenharry 's comment and the sampling book entry on pathfinder, here is a preliminary design.
def run_inference_algorithm(
    rng_key: PRNGKey,
    inference_algorithm: Union[SamplingAlgorithm, VIAlgorithm],
    num_steps: int,
    initial_position: ArrayLikeTree,
) -> Tuple[State, State, Info]:
    """
    Wrapper to run an inference algorithm.

    Parameters
    ----------
    rng_key : PRNGKey
        The random state used by JAX's random numbers generator.
    inference_algorithm : Union[SamplingAlgorithm, VIAlgorithm]
        One of blackjax's sampling algorithms or variational inference algorithms.
    num_steps : int
        Number of learning steps.
    initial_position : ArrayLikeTree
        The initial position to initialize the state of an inference algorithm.

    Returns
    -------
    Tuple[State, State, Info]
        1. The final state of the inference algorithm.
        2. The history of states of the inference algorithm.
        3. The history of the info of the inference algorithm.
    """

    @jax.jit
    def one_step(state, rng_key):
        state, info = inference_algorithm.step(rng_key, state)
        return state, (state, info)

    keys = jax.random.split(rng_key, num_steps)
    initial_state = inference_algorithm.init(initial_position)
    final_state, state_history, info_history = jax.lax.scan(
        one_step, initial_state, keys
    )

    return final_state, state_history, info_history

I've only tested it with the example in the README but wanted to have both your thoughts before moving forward.

@junpenglao thanks for the suggestions! Here are two (functionally equivalent, but different interfacing) variants that I think better follow your suggestions:
1.
initial_position and initial_state have default values so are not followed by any required args.
def run_inference_algorithm(
    rng_key: PRNGKey,
    inference_algorithm: Union[SamplingAlgorithm, VIAlgorithm],
    num_steps: int,
    initial_position: ArrayLikeTree = None,
    initial_state: ArrayLikeTree = None,
) -> Tuple[State, State, Info]:
    """
    Wrapper to run an inference algorithm.

    Parameters
    ----------
    rng_key : PRNGKey
        The random state used by JAX's random numbers generator.
    inference_algorithm : Union[SamplingAlgorithm, VIAlgorithm]
        One of blackjax's sampling algorithms or variational inference algorithms.
    num_steps : int
        Number of learning steps.
    initial_position : ArrayLikeTree, optional
        The initial position to initialize the state of an inference algorithm,
        by default None. Note that either `initial_position` or `initial_state`
        must be passed in, but not both.
    initial_state: ArrayLikeTree, optional
        The initial state of the inference algorithm, by default None.
        Note that either `initial_position` or `initial_state` must be passed in,
        but not both.

    Returns
    -------
    Tuple[State, State, Info]
        1. The final state of the inference algorithm.
        2. The history of states of the inference algorithm.
        3. The history of the info of the inference algorithm.
    """
    if (initial_position is None) == (initial_state is None):
        raise ValueError(
            "Either `initial_position` or `initial_state` must be specified, but not both."
        )
    if initial_state is None:
        initial_state = initial_state = inference_algorithm.init(initial_position)

    keys = jax.random.split(rng_key, num_steps)

    @jax.jit
    def one_step(state, rng_key):
        state, info = inference_algorithm.step(rng_key, state)
        return state, (state, info)

    final_state, state_history, info_history = jax.lax.scan(
        one_step, initial_state, keys
    )
    return final_state, state_history, info_history

2.
initial_position is the 2nd arg, but this requires only keyword arguments due to optional arg preceding required args.
def run_inference_algorithm(
    rng_key: PRNGKey,
    *,
    initial_position: ArrayLikeTree = None,
    initial_state: ArrayLikeTree = None,
    inference_algorithm: Union[SamplingAlgorithm, VIAlgorithm],
    num_steps: int,
) -> Tuple[State, State, Info]:
    """
    Wrapper to run an inference algorithm.

    Parameters
    ----------
    rng_key : PRNGKey
        The random state used by JAX's random numbers generator.
    initial_position : ArrayLikeTree, optional
        The initial position to initialize the state of an inference algorithm,
        by default None. Note that either `initial_position` or `initial_state`
        must be passed in, but not both.
    initial_state: ArrayLikeTree, optional
        The initial state of the inference algorithm, by default None.
        Note that either `initial_position` or `initial_state` must be passed in,
        but not both.
    inference_algorithm : Union[SamplingAlgorithm, VIAlgorithm]
        One of blackjax's sampling algorithms or variational inference algorithms.
    num_steps : int
        Number of learning steps.

    Returns
    -------
    Tuple[State, State, Info]
        1. The final state of the inference algorithm.
        2. The history of states of the inference algorithm.
        3. The history of the info of the inference algorithm.
    """
    if (initial_position is None) == (initial_state is None):
        raise ValueError(
            "Either `initial_position` or `initial_state` must be specified, but not both."
        )
    if initial_state is None:
        initial_state = initial_state = inference_algorithm.init(initial_position)

    keys = jax.random.split(rng_key, num_steps)

    @jax.jit
    def one_step(state, rng_key):
        state, info = inference_algorithm.step(rng_key, state)
        return state, (state, info)

    final_state, state_history, info_history = jax.lax.scan(
        one_step, initial_state, keys
    )
    return final_state, state_history, info_history

Of course there could be a cleaner way to achieve (2.) that I am no aware of! Let me know what you think.

@albcab what do you think?

You could just:
def run_inference_algorithm(
    rng_key: PRNGKey,
    initial_position: ArrayLikeTree,
    inference_algorithm: Union[SamplingAlgorithm, VIAlgorithm],
    num_steps: int,
    initial_state: ArrayLikeTree = None,
) -> Tuple[State, State, Info]:

    if initial_state is None:
        initial_state = inference_algorithm.init(initial_position)

    keys = jax.random.split(rng_key, num_steps)

    @jax.jit
    def one_step(state, rng_key):
        state, info = inference_algorithm.step(rng_key, state)
        return state, (state, info)

    final_state, (state_history, info_history) = jax.lax.scan(
        one_step, initial_state, keys
    )
    return final_state, state_history, info_history

Any initial state that needs more than an initial position to initialize or is initialized by an adaptation mechanism would need to be initialised outside the run_inference_algorithm; looks good to me.

hmm i dont think isinstance(initial_state, NamedTuple) works, because a log_density could accept NamedTuple as input.

But i think this is a good idea, maybe:
try:
    initial_state = inference_algorithm.init(initial_state)
except ...:
    pass  # initial_state is already in the right format.

@junpenglao is there any time an initial_position and initial_state have the same shape (and type) for an algorithm? For example the init just modifies the entries of initial_position but not the shape/type. If so, there would be an issue right?
If there is no such conceivable situation then that looks nice to me, unless trying the init is a costly computation.


fix: suggestion for volume mount issue

i believe this should mitigate a problem i found when using volume for containers:
➜  .robopages robopages run --function zap_baseline_scan
>> enter value for argument 'target': https://scanme.nmap.org/

[2024-11-07T21:20:51Z WARN ] executing: /usr/local/bin/docker run --rm -v${HOME}:/zap/wrk --net=host zaproxy/zap-stable -t https://scanme.nmap.org/ zap_headless_scan
>> enter 'y' to proceed or any other key to cancel: y

EXIT CODE: exit status: 125
ERROR: docker: Error response from daemon: create ${HOME}: "${HOME}" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.
See 'docker run --help'.

please noob me if this is not the case :) i also receive the same result with sql_map example and is not specific to my WIP robopage

@GangGreenTemperTatum the problem here is that the volume seems mapped to relative path which is not allowed, the double argument push is wrong

@GangGreenTemperTatum the problem here is that the volume seems mapped to relative path which is not allowed, the double argument push is wrong

totally makes sense, thank you! :)


Defend against Prototype.js

When testing code that needs to run on a page that also has Prototype.js 1.5.1 I discovered that Prototype breaks sendMessage in bridge.js because Prototype < 1.7.1 extended native objects in an unsafe way.
Since sendMessage will alway attempt to stringify an Array the stringify function added to bridge.js should be relatively safe.

Sorry, I feel your pain if you have to support Prototype 1.5, but I'm not going to introduce code specific to a 7 year old library that probably has less usage than IE6. You should probably just create a test helper to override JSON.stringify to call toJSON() on the object if it has it defined.
var origJSONStringify = JSON.stringify;
JSON.stringify = function(o) {
  if (typeof o == 'object' && typeof o.toJSON == 'function') {
    return o.toJSON();
  }

 return origJSONStringify.apply(this, arguments);
}


storage services authentication

I am playing with the emulator. Seems like it does not support authentication,
https://docs.microsoft.com/en-us/rest/api/storageservices/authentication-for-the-azure-storage-services
The emulator provides static account and key.
AccountName =:: devstoreaccount1
AccountKey ::= Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==
My expectation that it should fail incoming API request with a wrong account and/or key, but it seems azurite does not care much about authentication. Perhaps I am missing some configuration option?

@vitaly-goot many thanks for reporting this.
I'm working my way through quite a backlog at the moment, but as Azurite is not designed for production workloads, this doesn't surprise me.
However, as we want to emulate the API as  closely as possible, we should also appropriately respond to invalid credentials.
I'll add this to my Backlog and let you know when it's been addressed.
Kind regards,
Edwin

contributed my code here:
https://github.com/Azure/Azurite/pull/25

#25 merged into dev


Consider removing PrecisionConfigAttr

It looks like the intended use of PrecisionConfigAttr is to have either 0 or 2 PrecisionAttr values - one for the lhs, and one for the rhs (or none at all, and then DEFAULT is going to be used). Let's consider removing this attr and introducing optional attributes lhs_precision and rhs_precision.

At the moment, https://github.com/openxla/stablehlo/pull/441 will be adding the missing constraints on PrecisionConfigAttr as is. With that the verifer for affected ops (DotGeneral, and Convolution op) can be in sync with the StableHLO spec w.r.t this attribute.

The following definition
def StableHLO_PrecisionConfigAttr:
    OptionalAttr<
          TypedArrayAttrBase<StableHLO_PrecisionAttr, "Precision Config attribute">>;

allows multiple ways to represent empty precision_config attribute, which is confusing.
In case we chose to keep StableHLO_PrecisionConfigAttr as is (as part of resolving the PR), we need to make sure to avoid the representation issue.


diagnostic: Fix suggested git remote commands

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

git remote add origin ... doesn’t work because there’s already a remote.

Nice! Does this work both with non-existing and already existing remotes?

No, but the origin.nil? case is already taken care of in both… cases.

Nice work @bfontaine!


Refactor org.carbondata.query package

Remove unused classes
Move packages to make it more modular
Rename the package to org.carbondata.scan

Packages looks more arranged now  :- )


DWARF debug symbols parsing in ELF files

Conversion from ELF now has feature parity with conversion from assembly, so I am setting it as the default.

For the Keccak test the generated powdr-asm file is almost 100kb smaller, I wonder why

it seems to do some more optimizations (e.g., noticed some inlining that didn't happen before)

For the Keccak test the generated powdr-asm file is almost 100kb smaller, I wonder why

I think this is mainly due to two things:

There are 145 fewer .debug file lines. I guess because they are unique in the ELF, but can be repeated across multiple .s files.
In asm path, every label is prefixed with the name of the file, something like compiler_builtins_dash_46285d5d86658fbf_, but in the ELF path, either the linkage name name it is used or an address based label is used.


[Bug] FromAppSettings doesn't exists

Context / Scenario
I update from 0.23.x to 0.26.x
What happened?
Who Can we use FromAppSettings?
new KernelMemoryBuilder(builder.Services)
    .FromAppSettings()
    .WithCustomOcr(builder.Configuration)
    .Build();

Importance
I cannot use Kernel Memory
Platform, Language, Versions
Windows, net core.
Relevant log output
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS1061	'KernelMemoryBuilder' does not contain a definition for 'FromAppSettings' and no accessible extension method 'FromAppSettings' accepting a first argument of type 'KernelMemoryBuilder' could be found (are you missing a using directive or an assembly reference?)

To optimize our codebase, the FromAppSettings method, which relies on third-party packages, has been relocated to the Service project. While one option is to package the entire Service project, it poses the challenge of importing numerous external dependencies for just two files.
To optimize the codebase and reduce unnecessary dependencies, we recommend copying the relevant code and removing the extraneous dependencies. This way, you can maintain the required functionality without importing unnecessary packages.

https://github.com/microsoft/kernel-memory/blob/main/service/Service/KernelMemoryBuilderExtensions.cs
https://github.com/microsoft/kernel-memory/blob/main/service/Service/ServiceConfiguration.cs

See https://github.com/microsoft/kernel-memory/issues/283


gpu_operator_run_gpu-burn: store the gpu-burn sources within the role

This avoid any external dependency, instead of relying on my Github:
     GITHUB_REPO=kpouget/gpu-burn
     REF=471cc9b3ea3967a4d7bec698ec768df80344504a # kpouget/ci-friendly
     SRC=https://raw.githubusercontent.com/$GITHUB_REPO/$REF

or any manually-generated image as it was the case before this ^^^ update

/test gpu-operator-e2e

/test gpu-operator-e2e
On Mon, Sep 20, 2021 at 11:23 AM openshift-ci[bot] @.***>
wrote:

@kpouget https://github.com/kpouget: The following test failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/gpu-operator-e2e 228b722
https://github.com/openshift-psap/ci-artifacts/commit/228b7220ce4a792b57313d8946abfb51d6ac8432
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/256/pull-ci-openshift-psap-ci-artifacts-master-gpu-operator-e2e/1439874057745993728
true /test gpu-operator-e2e
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-psap&repo=ci-artifacts&pr=256.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:kpouget.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openshift-psap/ci-artifacts/pull/256#issuecomment-922761797,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZVQISFSTEEIAO4DNDGE5LUC34P5ANCNFSM5ELORLPA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

/test gpu-operator-e2e

/test custom

/lgtm

/test gpu-operator-e2e

/override ci/prow/custom
(wrong test triggered for this PR)

test passed for the OperatorHub deployment:
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift-psap_ci-artifacts/256/pull-ci-openshift-psap-ci-artifacts-master-gpu-operator-e2e/1439952962762838016/artifacts/gpu-operator-e2e/presubmit-operatorhub/artifacts/011__gpu_operator__run_gpu_burn/gpu_burn.ip-10-0-131-178.us-west-1.compute.internal.log
/approve


Implement lightweight Dotsama connector

Overview of the problem
API called with ApiPromise of polkadot{.js} consume too much resources and time if we connect to many networks.
It consum so much resources because it need to load metadata and create type in registry and prepre for some other method.
Solution
Instead of use full Dotsama API promise we can use connect to API endpoint directly with provider like WsProvider.

After compare ram need to connect via on WsProvider and ApiPromise I have this result:

Connect with 4 endpoint: WsProvider only need ~71mb ram with ApiPromise it need to ~137mb ram
Connect with 20 endpoint: WsProvider only need ~72mb ram with ApiPromise it need to ~264mb ram

Connect only with WsProvider we need to do more work

Need too know exactly what we call, we can found this by inspect WS call from polkadot-js apps with its endpoint
Need to hash data before call storage api and decode response data with registry

This solution will have some limitation and we still to use ApiPromise for dervive methods and complex methods in tx.

Additional content
Need fix some case like #93

Will implement when rebuilding architecture for Manifest V3 in #349


React + typeScript+ bugsnag possible ?

Hello everyone !
My question :  is it possible to integrate bugsnag inside React App witch is using typeScript?
I am currently working on my API call crash/error protect and I heard some good stuff about bugsnag and the rise of 'Unhandled error'.
I don't see any typeScript mention inside the official doc, so I ask my question here to get more information

Yes, definitely possible

https://docs.bugsnag.com/platforms/javascript/react/#typescript-support

Hi @hpachy, as above from @apexskier, yep absolutely! We have a couple of examples here using Typescript in Node.js and Angular if you'd like to check them out, too: https://github.com/bugsnag/bugsnag-js/tree/master/examples/ts
Closing this one out. If you have any queries please do get in touch with us at<EMAIL_ADDRESS>


allow flags to have false value in when

We have certain scenarios where we want to disallow users from using a --no flag when another flag is present. It seems we can do this by checking the value of the flag we want to disallow in when, but it ignores false values.
Flags
action: Flags.string({
    description: "Deploy a specific action",
    exclusive: [{ name: 'actions', when: async (flags) => flags.actions === false }]
}),
actions Flags.boolean({
    description: "Deploy actions",
    allowNo: true
})

Execution
bin/run app deploy --action=a --no-actions
<success>

With this PR, the above will throw an error.
The following error occurred:
  --actions=false cannot also be provided when using --action
See more help with --help

Related Issue
Closes https://github.com/oclif/core/issues/556
Currently a draft PR, because this was added without any tests failing and only one case has been added.

Thanks for the contribution! Before we can merge this, we need @purplecabbage to sign the Salesforce.com Contributor License Agreement.

Signed :thumbsup:

@mdonnalley Thanks for taking a look at this!
Added a new failure test case. CLA has been signed and the commits have been updated with a valid author 👍

@mdonnalley CLA has been signed. I may have confused the bot with the force push to fix the commit authors.

hey @MichaelGoberling 👋🏼 ,is this ready for review? if so please update the PR as it is marked as draft and can't be merged.

Hey @cristiand391 :wave: Yup! This is ready for review now.

<EMAIL_ADDRESS>was published with this fix, thanks @MichaelGoberling for contributing :)


[ BUG ] 'onPress' prop does not fire when dropdown items are pressed

Describe the bug
The (native only) Dropdown Menu component doesn't fire onPress callbacks that are provided to as props to the DropdownMenuItem children.
To Reproduce
Steps to reproduce the behavior:

Follow the manual instructions for setting up a dropdown-menu component.  When setting up the dropdown-menu primitive, use the native only option.
Start an iOS simulator
Use the below minimal implementation of the component & notice that the log isn't ever displayed when you press the item

import * as React from 'react';
import { Button } from '~/components/ui/button';
import { MenuIcon } from '~/components/icons';
import {
  DropdownMenu,
  DropdownMenuContent,
  DropdownMenuItem,
  DropdownMenuTrigger,
} from '~/components/ui/dropdown-menu';
import { Text } from '~/components/ui/text';
import { useSafeAreaInsets } from 'react-native-safe-area-context';

export const Dropdown = () => {
  const [open, setOpen] = React.useState(false);
  const insets = useSafeAreaInsets();
  const contentInsets = {
    top: insets.top,
    bottom: insets.bottom,
    left: 12,
    right: 12,
  };

  return (
    <DropdownMenu
      open={open}
      onOpenChange={(newVal) => {
        setOpen(newVal);
      }}
    >
      <DropdownMenuTrigger asChild>
        <Button variant="link">
          <MenuIcon className="text-foreground -mr-2 -mt-4" />
        </Button>
      </DropdownMenuTrigger>
      <DropdownMenuContent
        insets={contentInsets}
        className="w-64 native:w-72 border border-primary"
      >
        <DropdownMenuItem onPress={() => console.log('onPress fired')}> // This is the meaningful line
          <Text>fire onPress</Text>
        </DropdownMenuItem>
      </DropdownMenuContent>
    </DropdownMenu>
  );
};

Expected behavior
When using the above component I would expect that a log of onPress fired would be shown when item is pressed.
Platform

Type: Simulator
OS: iOS

Additional context
As noted in another issue, this project is awesome -- thanks for building it!

@tctrautman Thank you!
Unfortunately I am not able to recreate this issue so I will close this issue. I tried in the this repositories showcase app and in a new project and they both work.
There were come updates to the CLI since this issue was created. Perhaps you could delete your dropdown-menu ui and primitive files and try again by adding it to your project with: npx @react-native-reusables/cli@latest add dropdown-menu
If you still have this issue after trying with the CLI, please open a new issue with a minimal reproduction issue so that I help resolve it.

Using the updated CLI command seems to have fixed the issue -- thanks, @mrzachnugent!

I have same issue
 <DropdownMenu>
      <DropdownMenuTrigger asChild>
        <Button size="icon" variant="outline">
          <Text>open</Text>
        </Button>
      </DropdownMenuTrigger>
      <DropdownMenuContent>
        <DropdownMenuItem
          closeOnPress
          onPress={() => {
            console.log("pressed");
            // navigation.navigate("profile");
          }}
        >
          <UserRoundCog size={20} />
          <TextView text="profile" />
        </DropdownMenuItem>
        <DropdownMenuItem closeOnPress>
          <LogOut size={20} />
          <TextView text="logOut" />
        </DropdownMenuItem>
      </DropdownMenuContent>
 </DropdownMenu>

Platform
 Type: Device
 OS:  Android


Shell:OnPlatformViewDestroyed not working with thread merging

The current implementation Shell:OnPlatformViewDestroyed is not compatible with thread merging.
For example on iOS, imagine an app contains a google map. When the map first shows up, the system alert view pops up for a location permission. The system alert view then triggers the ApplicationWillResignActive, which triggers Shell:OnPlatformViewDestroyed on the platform thread.
At the same time, the threads are about to merge on the raster thread because the google map view is about to show up at the next frame. If the merging thread happened after we check if the threads are merged here (We are not checking the thread merging now, which we also need to fix. But that's not the main issue here), we will still post the task to the "raster_task_runner" here. And the posted task is actually going to run on the platform thread, because the threads are merged when the task started. It leads to a dead lock because the platform thread is still waiting for this posted task to release it.

From the offline conversation: @cyanglaz will share a design doc about this issue.

Triage: The linked pull request has been discussed and we have a way forward. It is still a WIP for now.

The PR is ready for review.


First push to PR

Hi,
Done.
Thanks, Julie.
From: Daniel Wroblewski @.>
Sent: 25 July 2021 08:25
To: SAPDocuments/Tutorials @.>
Cc: Plummer, Julie @.>; Author @.>
Subject: Re: [SAPDocuments/Tutorials] First push to PR (#6859)
@thecodester requested changes on this pull request.
Looks good. Please add period at end of description and remove the "Context" heading from the introduction. Then I will merge.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/SAPDocuments/Tutorials/pull/6859#pullrequestreview-714282004, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFNPXTLWK6ADFDEXGFGUGZ3TZOU35ANCNFSM5AZ3QUOQ.


Declare precedence on enum types

Fixes issue #1198 where an enum matches the pattern for multiple enum types, such as constified module enum AND rustified enum.
Documents precedence in Builder doc comment.

@bors-servo r+
Thanks!

:pushpin: Commit 8c9b3ab has been approved by emilio

:hourglass: Testing commit 8c9b3ab4d650bd30b5f50cc85a19621f920f91c6 with merge 22041e13d08dbd4cb0ea777fa540897735d9e7c2...

:sunny: Test successful - status-travis
Approved by: emilio
Pushing 22041e13d08dbd4cb0ea777fa540897735d9e7c2 to master...


FAQ on app

FAQ for commonly faced problems on the app and information about certain features.

Hello @shreyas1599
can you provide some more information like how it looks like(Design) and some questions?
so I can build that FAQ page.
Thanks.


Propose developer branch norms

Propose a set of norms/guidelines for us to follow as we develop. Not only branch naming guidelines and pull request guidelines but also who to send the review to or how long to wait before pinging the person.
Typically these norms are developed over time on a team, but let's try to be explicit up front so we can move faster.

Maybe we don't need to explicitly define these.


🐞 Incorrectly extract the group syntax in Svelte ( by Discord Tdyi )

Description
From Tdyi:
Thanks for taking the time to answer and look into this!
Also, I tried the Group Feature, and got this error in Sveltekit, as curly braces are used to pass JS data, it expects no colon :
/src/routes/+layout.svelte:8:16 Expected }
8 |
li">
                  ^

I've managed to get around it like so :

...

li my:0 pl:0 fg:white gap:15 flex">

but I'd rather not rely on this workaround, using script tags just to style seems not viable

For the group feature, you should escape curly braces in Svelte Kit:

li'} my:0 pl:0 fg:white gap:15 flex">

Svelte allows the use of {} inside "" to bind data with a high risk of collision.


⚠ PrivateHD has degraded performance

In a18fbb7, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1480 ms

Resolved: PrivateHD performance has improved in 7919abf.


eDell / Superfish subdomains?

i.e. famous certs with known private keys.

I was just talking to @marumari about this. I have the private keys already and want to do this. :)

@lgarron What do you think about the Atheros cert detailed https://www.duosecurity.com/blog/dude-you-got-dell-d-publishing-your-privates ? Could it also be of use?


Catch XHR errors

When the XHR request triggers an error (e.g. in case of CORS issues), it is now catched properly. Needed to fix weird Karma/Jasmine issues in Angular CLI projects.

I did not change any of the original code in this PR, just added the try/catch. But of course I can have a look at it.

@johnjbarton fixed.

Thanks! 👍

@LinusU When are you planning to make a release that will contain this commit?

Thx ❤ released as 0.5.9 🚀


VAE example outdated

The VAE example in /flax/examples/vae seems to have some outdated requirements, jax.random usage, and absl.flags usage.
Modifications I made to get the example running:

change jax.random.key to jax.random.PRNGKey
install clu==0.0.10
run main.py without workdir argument (change README to not use --workdir)

System information

jax==0.4.6
flax==0.6.9
other requirements installed from requirements.txt

I'd be happy to open a PR with these changes.

jax.random.PRNGKey is a deprecated version of jax.random.key, so the usage of latter is preferred. You are using a very old JAX version that still uses PRNGKey.
And it looks like clu was constrained to be below 0.0.10 by https://github.com/google/flax/pull/3394 - maybe this is to fix some CI test? @cgarciae
And yes the --workdir argument seems to be mistakenly copied - a PR fixing that would be perfect.

As far as I can see jax.random.PRNGKey is still referenced in Pseudo Random Numbers in JAX. I also updated my JAX version to 0.4.23, and this had no problem with jax.random.PRNGKey, however, I can't find current documentation for jax.random.key, did I miss this in my search?

Ah, JAX documentation is a bit outdated... One of the JAX owners actually wrote the PR that converted all Flax examples to use jax.random.key: https://github.com/google/flax/pull/3337 I might open a PR later to change the JAX doc.


Update java-driver-core, ... to 4.15.0

Updates

com.datastax.oss:java-driver-core
com.datastax.oss:java-driver-query-builder

from 4.14.1 to 4.15.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.datastax.oss" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.datastax.oss" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #1515.


perf(reactivity): should not track __v_isRef and some methods in pr…

…ototype.eg.toString
Reproduction
 const App = {
    setup: () => {
      const data = reactive( {
        array: [1],
        object: {a: 1}
      } );

      return { data }
    },
    renderTracked(e) {
      console.log('key', e)
    },
    template: `
      <div  :literal="data.object" :obj="data.array.map((e) => e)"></div>
    `
  }

  let app = createApp(App);
  app.mount("#app");

Current Behavior

Changed Behavior

I'm not sure for this.I think it is helpful for better performance.If you agree with me, I will add some test for it.

This adds the cost of the hasOwn checks to every get access, which is likely even more expensive.

Multiple hasOwn checks are expensive, in addition, it's not entirely safe to skip these keys - for example, the user may add a new property named map to an object and this would cause it to not be tracked on the initial run when map is not on the object yet.


bioblend.ConnectionError when running with --deploy-docker

Hello,
I'm trying to run snyphyl-galaxy-cli on a local server as I don't have access to Galaxy. Here is my run command:
python igas/snvphyl-galaxy-cli/bin/snvphyl.py --deploy-docker --fastq-dir igas/test --reference-file igas/data/AE009949.1.fasta --min-coverage 5 --output-dir igas/output/test
However, upon running I get the following error/output:
Error: bioblend.ConnectionError: GET: error 403
Deploying Docker Container
==========================
Running 'docker run --detach --publish 48888:80 --volume /home/vitalite-dev/igas/test:/snvphyl-data/fastq phacnml/snvphyl-galaxy-1.0.1:1.0.1b'
Docker id 29770d99961911c4fa25181b0d175f88d3b6cbc8eea01abca3319e7cda603a3d
Waiting for docker to complete launching Galaxy on port 48888 .....finished.  Galaxy in Docker has (hopefully) started successfully.
Took 0.31 minutes to deploy docker

Examining input fastq files
===========================
Structuring data in directory '/home/vitalite-dev/igas/test' like:
igas-8-20240205_S5_L001: paired {forward: /home/vitalite-dev/igas/test/igas-8-20240205_S5_L001_R1_001.fastq.gz, reverse: /home/vitalite-dev/igas/test/igas-8-20240205_S5_L001_R2_001.fastq.gz}

Set up workflow input
=====================
setting parameter {irida.corefacility.ca/galaxy-shed/repos/nml/consolidate_vcfs/consolidate_vcfs/1.8.0, snv_abundance_ratio, 0.75}
setting parameter {irida.corefacility.ca/galaxy-shed/repos/nml/consolidate_vcfs/consolidate_vcfs/1.8.0, coverage, 5}
setting parameter {irida.corefacility.ca/galaxy-shed/repos/nml/verify_map/verify_map/1.8.0, mindepth, 5}
setting parameter {irida.corefacility.ca/galaxy-shed/repos/nml/consolidate_vcfs/consolidate_vcfs/1.8.0, mean_mapping, 30}
setting parameter {irida.corefacility.ca/galaxy-shed/repos/nml/find_repeats/findrepeat/1.8.0, length, 150}
setting parameter {irida.corefacility.ca/galaxy-shed/repos/nml/find_repeats/findrepeat/1.8.0, pid, 90}
setting parameter {irida.corefacility.ca/galaxy-shed/repos/nml/consolidate_vcfs/consolidate_vcfs/1.8.0, use_density_filter.threshold, 2}
setting parameter {irida.corefacility.ca/galaxy-shed/repos/nml/consolidate_vcfs/consolidate_vcfs/1.8.0, use_density_filter.window_size, 500}

Undeploying and cleaning up Docker Container
=============================================
Running 'docker rm -f -v 29770d99961911c4fa25181b0d175f88d3b6cbc8eea01abca3319e7cda603a3d'
29770d99961911c4fa25181b0d175f88d3b6cbc8eea01abca3319e7cda603a3d
Traceback (most recent call last):
  File "/home/vitalite-dev/igas/snvphyl-galaxy-cli/bin/snvphyl.py", line 1302, in <module>
    main(snvphyl_version_settings, **dic)
  File "/home/vitalite-dev/igas/snvphyl-galaxy-cli/bin/snvphyl.py", line 973, in main
    main_galaxy(url, key, snvphyl_version, workflow_id, fastq_dir, fastq_history_name, reference_file, run_name, relative_snv_abundance, min_coverage, min_mean_mapping,  File "/home/vitalite-dev/igas/snvphyl-galaxy-cli/bin/snvphyl.py", line 1051, in main_galaxy
    snvphyl_workflow=find_workflow_uuid(gi.workflows.get_workflows(), workflow_settings.attrib['uuid'])
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vitalite-dev/mambaforge/envs/igas/lib/python3.12/site-packages/bioblend/galaxy/workflows/__init__.py", line 63, in get_workflows
    workflows = self._get(params=params)
                ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/vitalite-dev/mambaforge/envs/igas/lib/python3.12/site-packages/bioblend/galaxy/client.py", line 134, in _get
    raise ConnectionError(
bioblend.ConnectionError: GET: error 403: b'{"err_msg": "API authentication required for this request", "err_code": 403001}', 0 attempts left: {"err_msg": "API authentication required for this request", "err_code": 403001}

Is a Galaxy API Key/account needed to run the docker-deployed version of snyphyl (I am a bit unfamiliar with how Galaxy and Docker interact)?
Other stats:
Running on Ubuntu 22.04
Docker version 24.0.6, build ed223bc
Python 3.12.1
Thanks for any help with this,
Pierre

Hello @PierreLyons , you will likely have to install the exact version of bioblend found in the requirements.txt for this to work (https://github.com/phac-nml/snvphyl-galaxy-cli/blob/development/requirements.txt)
However, this method of running SNVPhyl is out of date and no longer being supported. We have just (as of today) released a version of SNVPhyl within Nextflow, which you can find here: https://github.com/phac-nml/snvphylnfc

You're welcome. I'm glad I could help 😄

For anyone else running into the same issue, I was able to get it running by downgrading python to 3.11. Newer python versions don't work with bioblend 0.7.0.


Angular Dynamic Menu using Material design

I want to create a dynamic menu, the data is get from database for instance. Here is the https://stackblitz.com/edit/angular-dmenu project
In the dynamic-menu.component.html in the StackBlitz project there are the dynamic solution and the static solution(that is commented).
The static solution should be how the dynamic solution will be rendered after executes.
If i just run with the static solution(uncomment and commented the dynamic) everything runs as expected, but if i try with the dynamic solution the menu does not work as expected (the main buttons stays on top of each other and the submenus do not display and work properly).
Is this related with how ng-template affect the CSS styles ?
Looking through Chrome developer tools i am able to see that the class="mat-menu-item ng-star-inserted" attribute in the dynamic version is added to the button for instance and this does not happen in the static version. I have try everything but i can not get it why is this happening. And how can i fix this. I am new to Angular but i want really understands how the frameworks works
Thanks in advance
Best regards

Check out this StackOverflow answer - it may point you in the right direction: https://stackoverflow.com/questions/48146171/dynamic-nested-material-menu-from-json-object-in-angular-5
In particular, I think you want the answer provided by Datum Geek where you have an arbitrary amount of nesting. His approach was to create a component named MenuItemComponent that rendered a button and items, but could possible contain itself for nested menu buttons


Typo in object

[LEVEL]/[COMPONENT]
TASK:
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Only
[ ] Refactor

Description, Motivation and Context

Screenshots - Animations

Thank you so much @humbertovnavarro 🙌🏻


Question about use of .data in SparseAutoencoder class

In the SAE code, there's a number of places that read and write to .data instead of the tensor itself, for instance here, and here. Why is this done, and is it necessary? It appears that reading and writing from .data in pytorch is deprecated and potentially dangerous: https://discuss.pytorch.org/t/the-difference-between-torch-tensor-data-and-torch-tensor/25995/2

I didn't know this was deprecated, thanks for sharing!
I was using .data when I wanted to ensure gradients weren't tracked; it seems now we use @torch.no_grad everywhere so feel free to send a PR


Filenames with "+" get converted to spaces

Our team recently ran into an issue where the filenames store within the package index were incorrect when updated with the latest version of deb-s3. There were ~10 packages we have stored in s3 that include a "+" in the version and path (e.g. libnvinfer-plugin7=7.1.3-1+cuda10.2). When we attempted to install the packages, the following error occurred for all packages:
E: Failed to fetch s3://xxxx-xxx/xxx-xxx/private/pool/bionic/l/li/libnvinfer-plugin-dev_7.1.3-1 cuda10.2_arm64.deb  403  Forbidden
Note that there is a space in the filename instead of a "+". A snippet of the package index generated by deb-s3 can be seen below:
Incorrect Version
Package: libnvinfer-plugin7
Version: 7.1.3-1+cuda10.2
Filename: pool/bionic/l/li/libnvinfer-plugin7_7.1.3-1 cuda10.2_arm64.deb

When we re-uploaded the packages with v0.10.0 of the original deb-s3 (https://github.com/krobertson/deb-s3/tree/0.10.0), the filename is correctly included in the package index:
Correct Version
Version: 7.1.3-1+cuda10.2
Filename: pool/bionic/l/li/libnvinfer-plugin7_7.1.3-1+cuda10.2_arm64.deb

Looking through the source, this looks to be caused by replacing URI.unescape with CGI.unescape in package.rb (https://github.com/deb-s3/deb-s3/blob/master/lib/deb/s3/package.rb#L254)

Can you try to reproduce w/ latest version?

The latest version(s) of the deb-s3 gem, which hadn't been updated in 4 years, broke source APT source repo which broke our production environment, i.e. I can confirm we are seeing the same issue.

The template in https://github.com/deb-s3/deb-s3/blob/0.11.5/lib/deb/s3/templates/package.erb#L43 is using https://github.com/deb-s3/deb-s3/blob/0.11.5/lib/deb/s3/package.rb#L147-L149 and not the line w/ CGI.unescape.

Could it be because https://github.com/deb-s3/deb-s3/blob/0.11.5/lib/deb/s3/package.rb#L147-L149 does:
  def url_filename_encoded(codename)
    @url_filename || "pool/#{codename}/#{self.name[0]}/#{self.name[0..1]}/#{s3_escape(File.basename(self.filename))}"
  end

and @url_filename is set when extract_info is called (in https://github.com/deb-s3/deb-s3/blob/0.11.5/lib/deb/s3/package.rb#L258)?

Recently i've been granted access to upload to rubygems, so latest version has been uploaded to https://rubygems.org/gems/deb-s3/versions/0.11.6
Works for me.
Upload:
# deb-s3 upload graphsurgeon-tf_8.5.1-1+cuda11.8_amd64.deb --bucket deb-s3-11 --codename test --access-key-id ... --secret-access-key ... --endpoint https://minio.morph027.de --sign ... --force-path-style
>> Retrieving existing manifests
>> Examining package file graphsurgeon-tf_8.5.1-1+cuda11.8_amd64.deb
>> Uploading packages and new manifests to S3
   -- Transferring pool/test/g/gr/graphsurgeon-tf_8.5.1-1+cuda11.8_amd64.deb
   -- Transferring dists/test/main/binary-amd64/Packages
   -- Transferring dists/test/main/binary-amd64/Packages.gz
   -- Transferring dists/test/main/binary-i386/Packages
   -- Transferring dists/test/main/binary-i386/Packages.gz
   -- Transferring dists/test/main/binary-armhf/Packages
   -- Transferring dists/test/main/binary-armhf/Packages.gz
   -- Transferring dists/test/Release
   -- Transferring dists/test/InRelease
   -- Transferring dists/test/Release.gpg
>> Update complete.

Results in:
root@5eded8af43c6:/tmp# apt-cache policy graphsurgeon-tf
graphsurgeon-tf:
  Installed: (none)
  Candidate: 8.5.1-1+cuda11.8
  Version table:
     8.5.1-1+cuda11.8 500
        500 https://minio.morph027.de/deb-s3-11 test/main amd64 Packages
root@5eded8af43c6:/tmp# apt-cache show graphsurgeon-tf
Package: graphsurgeon-tf
Version: 8.5.1-1+cuda11.8
License: unknown
Vendor: none
Architecture: amd64
Maintainer: cudatools<EMAIL_ADDRESS>Installed-Size: 81
Section: multiverse/devel
Priority: optional
Homepage: http://nourlgiven.example.com/
Filename: pool/test/g/gr/graphsurgeon-tf_8.5.1-1+cuda11.8_amd64.deb
Size: 14636
SHA1: 247f54db8cb8dfe8091dacf12cbd3cdf8b5a2f71
SHA256: a76fdb5834e7f9977d813bebcca197325a8d1f0fd69e4385a94d23f366c0dbc0
MD5sum: bec2793fda6a9911d7a9f7426c91a9b8
Description: GraphSurgeon for TensorRT package
 GraphSurgeon for TensorRT package.
Description-md5: 2ed78147a56e5008fc61f05c12bb0cf5
Source: tensorrt

root@5eded8af43c6:/tmp# apt-get download graphsurgeon-tf
root@5eded8af43c6:/tmp# dpkg -I graphsurgeon-tf_8.5.1-1+cuda11.8_amd64.deb
 new Debian package, version 2.0.
 size 14636 bytes: control archive=916 bytes.
     280 bytes,    10 lines      control
    1340 bytes,    14 lines      md5sums
 Package: graphsurgeon-tf
 Source: tensorrt
 Version: 8.5.1-1+cuda11.8
 Architecture: amd64
 Maintainer: cudatools<EMAIL_ADDRESS> Installed-Size: 81
 Section: multiverse/devel
 Priority: optional
 Description: GraphSurgeon for TensorRT package
  GraphSurgeon for TensorRT package.

https://github.com/deb-s3/deb-s3/blob/2ec9c4172013207e2592a5870a0d0af9fe46b002/lib/deb/s3/package.rb#L258
CGI.unescape converst "+" to " ". This happens when reading Packages. So the error occurs only when rewriting old entries which seems to have caused some confusion.

Is there an easy way to fix the Package list after this bug happens?
Currently, all our old packages result in 404 errors because of the incorrect Filename path.
We're able to manually edit the package files and re-upload them... but this is a tedious task...

Is there an easy way to fix the Package list after this bug happens? Currently, all our old packages result in 404 errors because of the incorrect Filename path.
We're able to manually edit the package files and re-upload them... but this is a tedious task...

I think you should be able to just fix the "Packages" file, edit the check-sums in "Release" and re-sign it.
My use case was an automated upload from a CI/CD service and I just erased the whole repository and re-ran all pipelines.


fix(build): Fixed coveralls upload

@homu r+

:pushpin: Commit a870d97 has been approved by MichaelHirn

:hourglass: Testing commit a870d97 with merge 4916312...

:sunny: Test successful - status


virt-handler: do not crash when a qemu disk has no alias set

When a sidecar adds a disk to the VM's XML, it is not forced to include an alias.
What this PR does / why we need it:
We were seeing crashes of virt-handler with this log on deletion of a VM:
"component":"virt-handler","kind":"","level":"info","msg":"VMI is in phase: Running | Domain does not exist","name":"my-instance","namespace":"customer-project-priederer","pos":"vm.go:1759","timestamp":"2023-11-13T19:16:28.910982Z","uid":"ff66f4be-de79-4bb9-841a-12da78300a
ce"}
E1113 19:16:28.911054 3776784 runtime.go:79] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 571 [running]:
kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/util/runtime.logPanic({0x1e32500?, 0x381fd70})
        vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:75 +0x99
kubevirt.io/kubevirt/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0x0, 0x0, 0xc002c55d30?})
        vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:49 +0x75
panic({0x1e32500, 0x381fd70})
        GOROOT/src/runtime/panic.go:884 +0x212
kubevirt.io/kubevirt/pkg/virt-handler.(*VirtualMachineController).updateVolumeStatusesFromDomain(0xc00081c540, 0xc003a31180, 0xc003a30c00)
        pkg/virt-handler/vm.go:892 +0x95b
kubevirt.io/kubevirt/pkg/virt-handler.(*VirtualMachineController).updateVMIStatus(0xc00081c540, 0xc003afc580, 0xc003a30c00, {0x0?, 0x0})
        pkg/virt-handler/vm.go:1291 +0x617
[...]
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1b7c25b]

We are using side-cars to extend the qemu domain XML and did not always include an alias for a disk — as qemu does not need it. In our tests, even adding the alias did not always prevent this crash, possibly because of some weird caching?
Release note:
NONE

In a non-sidecar VMI creation, converter.go:250 is where alias get set. I'd expect that to happen still when we do use sidecars, but notice that you shouldn't set the Alias,  you should only set the Name.

Yes, when we do not set the Alias, sometimes an alias would still be in the XML as shown by dumpxml, but never with the attribute userDefined…
To be honest, I am confused about what's going on here, but I wanted to share the fix anyway :-D

as other places in the codebase will consider Alias to be set.

This place is the only one we see in backtraces.

ET.SubElement(disk, 'alias', name=f"gc-virtio-{diskNames[diskID]}") # Having this does not help!

Alias name should start with ua- prefix. Ref https://libvirt.org/formatdomain.html#devices

To help users identifying devices they care about, every device can have direct child alias element which then has name attribute where users can store identifier for the device. The identifier has to have "ua-" prefix and must be unique within the domain. Additionally, the identifier must consist only of the following characters: [a-zA-Z0-9_-].

That's fun :-D
When we do not add the alias, the automatically generated one (that sometimes appears) is virtio-disk0…
I'll try again with the ua- prefix.

Indeed, if I use the prefix, ua- the alias gets created and virt-handler does not crash. Thank you for pointing that out!
Do you want to keep this PR (arguably it makes virt-handler more robust), or should I close it?

Indeed, if I use the prefix, ua- the alias gets created and virt-handler does not crash. Thank you for pointing that out!

Nice :+1:

Do you want to keep this PR (arguably it makes virt-handler more robust), or should I close it?

I personally agree with Victor's comment. There might be different scenarios where this may also pop up. Additionally, if we silently skip disks without aliases, I am not sure that volume statuses will be properly updated. I do agree that crashing is not nice... but after a quick look, it seems that KubeVirt code expects that aliases are always set. I would then say that it should probably report an error...

Then I'll close this. Sorry for the noise and thanks for the help!