Remove deprecated handlers

Pending: https://github.com/neovim/neovim/pull/13649

@tjdevries This removes almost all the handlers, except one workaround that I mentioned on the gitter. If people have nightly builds older than week, it will cause issues for them.

@tjdevries This removes almost all the handlers, except one workaround that I mentioned on the gitter. If people have nightly builds older than week, it will cause issues for them.


Could we adjust this pattern?

In https://github.com/jedireza/reserved-subdomains/blob/master/patterns.json#L20
Is there a reason why a-z is included in the pattern whereas all earlier patterns only do [0-9]?
I have a situation where someone legitimately wants to have a subdomain with ww in the beginning and while I could just fork it would be nice if the pattern:
"ww[a-z0-9-]+" could be changed to "ww[0-9]+"
In the actual main package in npm.
https://www.npmjs.com/package/reserved-subdomains
Thanks for considering!

Sure. Submit a PR and we'll get it published right after.

Thanks! Just created PR #5


feat: Remove the core scripts

After discussion, we decided that the core scripts provided by this library were more confusing than useful. Indeed, a developer working on a project using this library may want to be able to easily view the code of all scripts he is running. By bundeling some scripts here, we have made this a little difficult.
Now, these core scripts (test-units, lint, watch, etc) will have to be defined in the projects themselves, like any other script.
Instead of providing the scripts in this library, we will add them to the API and Library templates.

Excellent travail @electrotype ! Tout passe de mon côté. Alors je vais merger et faire une nouvelle release.


ESP32 DEVKIT V1 Bad Firmware

ESP32 DEVKIT V1 ESP32-D0WD-V3 Rev 3 micrUSB version
Works partially or not at all.
I achieved partial work only with the firmware TCode_ESP32_Release_v0.3b-bldc
The display shows information about the access point and there is a connection.
I can connect it to the player, but the servos don't work.
With other firmware versions TCode_ESP32_Release_v0.3b и TCode_ESP32_Release_v0.34b-bldc
TCode_ESP32_Release_v0.34b does not work at all, the display does not turn on, there is no Wi-Fi connection, the servos do not work, there is communication via the COM port:
ets Jul 29 2019 12:21:46
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13232
load:0x40080400,len:3028
entry 0x400805e4
INFO main: ESP32 Chip model = ESP32-D0WD-V3 Rev 3
INFO main: This chip has 2 cores
INFO main: Chip ID: 5298060
INFO settings-handler: Read Settings file: /userSettings.json
INFO settings-handler: Read password file
INFO settings-handler: Load settings
INFO settings-handler: Last reset reason: Brownout reset (software or hardware)
INFO main: Version: 0.34b
INFO display-handler: Setting up display
INFO settings-handler: Scanning for I2C...
INFO settings-handler: I2C device found at address 0x3c, byte 60
INFO settings-handler: No I2C devices found in system, trying again...
INFO display-handler: No I2C devices found in system
INFO main: Starting in APMode
Brownout detector was triggered
Regarding the utility: flash.exe
If you click update, an error appears, saying the System cannot find the specified path
It is not intuitively clear at what stage you need to enter the Wi-Fi password
There is no choice of turning on the display with an indication of its settings, and this is important, because it is not clear what state the board is in.
There is no stopping logging to read errors and understand what is wrong. You have to turn off the device so that you can read the text.
Fortunately, the display should turn on automatically and show the state of the board.

ets Jul 29 2019 12:21:46
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:1184
load:0x40078000,len:13232
load:0x40080400,len:3028
entry 0x400805e4
INFO main: ESP32 Chip model = ESP32-D0WD-V3 Rev 3
INFO main: This chip has 2 cores
INFO main: Chip ID: 5298060
INFO settings-handler: Loading wifi info
INFO settings-handler: Loading json file /wifiInfo.json
INFO settings-handler: Loading common settings
INFO settings-handler: Loading json file /userSettings.json
INFO settings-handler: Last reset reason: Brownout reset (software or hardware)
INFO settings-handler: Loading motion profiles
INFO settings-handler: Loading json file /motionProfiles.json
INFO main: Version: 0.35b
INFO display-handler: Setting up display
INFO settings-handler: Scanning for I2C...
INFO settings-handler: I2C device found at address 0x3c, byte 60
INFO settings-handler: No I2C devices found in system, trying again...
INFO display-handler: No I2C devices found in system
INFO main: Starting in APMode
Brownout detector was triggered

Absolutely nothing works! The display does not show information!
The board is connected via USB, there are no servos, the display is connected (it worked in one of the firmwares)
NO voltage dips! The computer is new, the cable is connected to the motherboard.

I found what's wrong!
USB power problem “Brownout detector was triggered”
Namely, a lack of current due to the cord or computer, and not even every power adapter could cope with this.
Can’t even connect to Wi-Fi, although he tries
The ESP32 simply goes into defense and does not perform any actions!!!!
I'm more than sure that many people will have this problem.
Ways to solve it, as I see it. I need to add a display switching point to my firmware program so that I can see if the board starts up and it is advisable to display a message saying Low power
Although I don’t know how you power the board, because the connection is via wi-fi and a usb cable is not required...
But feeding it in the same circuit with servos is very bad, since they cause interference on the board. I'm not sure whether filters will save you.
Low power control can be disabled in the firmware code:
#include "soc/soc.h"
#include "soc/rtc_cntl_reg.h"
// in setup()
WRITE_PERI_REG(RTC_CNTL_BROWN_OUT_REG, 0);
https://www.youtube.com/watch?v=_SIfywxHqL0
Make it possible to stop logging in the flasher window, because it is difficult to read the error code.

https://stackoverflow.com/questions/73200166/exception-handling-for-brownout-detector-was-trigerred

I found what's wrong!
USB power problem “Brownout detector was triggered”
Namely, a lack of current due to the cord or computer, and not even every power adapter could cope with this.
I discovered that there is no diode on my board and what I feed to VIN goes straight via USB to the computer.
Which is dangerous. I found one solution, unsolder the 0 ohm resistor on the ESR32 board and power it only from an external source, even during firmware. The issue of power filtering also arises, because there is a lot of interference from servos and this can negatively affect the operation of the device as a whole. Electrolyte and ceramics in the circuit, I doubt that they will help much... Separate power supplies are inconvenient...

ESP32 DEVKIT V1 ESP32-D0WD-V3 Rev 3 micrUSB version Works partially or not at all. I achieved partial work only with the firmware TCode_ESP32_Release_v0.3b-bldc The display shows information about the access point and there is a connection. I can connect it to the player, but the servos don't work. With other firmware versions TCode_ESP32_Release_v0.3b и TCode_ESP32_Release_v0.34b-bldc TCode_ESP32_Release_v0.34b does not work at all, the display does not turn on, there is no Wi-Fi connection, the servos do not work, there is communication via the COM port:
ets Jul 29 2019 12:21:46
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0030,len:1184 load:0x40078000,len:13232 load:0x40080400,len:3028 entry 0x400805e4
INFO main: ESP32 Chip model = ESP32-D0WD-V3 Rev 3 INFO main: This chip has 2 cores INFO main: Chip ID: 5298060 INFO settings-handler: Read Settings file: /userSettings.json INFO settings-handler: Read password file INFO settings-handler: Load settings INFO settings-handler: Last reset reason: Brownout reset (software or hardware) INFO main: Version: 0.34b INFO display-handler: Setting up display INFO settings-handler: Scanning for I2C... INFO settings-handler: I2C device found at address 0x3c, byte 60 INFO settings-handler: No I2C devices found in system, trying again... INFO display-handler: No I2C devices found in system INFO main: Starting in APMode
Brownout detector was triggered
Regarding the utility: flash.exe If you click update, an error appears, saying the System cannot find the specified path It is not intuitively clear at what stage you need to enter the Wi-Fi password There is no choice of turning on the display with an indication of its settings, and this is important, because it is not clear what state the board is in. There is no stopping logging to read errors and understand what is wrong. You have to turn off the device so that you can read the text.
Fortunately, the display should turn on automatically and show the state of the board.

Thanks for the UX tips. I will attempt to make it more clear somehow.
As far as the other issue, these seem like hardware issues and not really issues with the firmware so I'm closing this request


Linux remote SSH installations are unable to update

Installations for the remote SSH integration are unable to update for versions v1.4.6 and v1.5.0. Users on these versions will need to manually update by installing according to the instructions outlined in the AWS documentation.
Essentially, run:
# For x86_64
curl --proto '=https' --tlsv1.2 -sSf "https://desktop-release.codewhisperer.us-east-1.amazonaws.com/latest/q-x86_64-linux.zip" -o "q.zip"
# For ARM
# curl --proto '=https' --tlsv1.2 -sSf "https://desktop-release.codewhisperer.us-east-1.amazonaws.com/latest/q-aarch64-linux.zip" -o "q.zip"

unzip q.zip
./q/install.sh

v1.5.1 has been released which includes #234


[MWPW-134535] Subtle active effect for dropdown

Resolves: MWPW-134535
Small dropdown active effect improvement
Test URLs:

Before: https://main--express--adobecom.hlx.page/express/templates/?lighthouse=on
After: https://mwpw-134535--express--adobecom.hlx.page/express/templates/?lighthouse=on

Codecov Report

Merging #137 (5cf9d4b) into stage (2f4eacc) will not change coverage.
Report is 5 commits behind head on stage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            stage     #137   +/-   ##
=======================================
  Coverage   35.34%   35.34%
=======================================
  Files          25       25
  Lines        9452     9452
=======================================
  Hits         3341     3341
  Misses       6111     6111

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Scale not set

On my retina display, I'm experiencing a bug where the image rendered takes up half the canvas context. This is because my browser's defaultView.devicePixelRatio is 2.
In ForiegnObjectRenderer.js, the scale should be set like:
this.ctx.scale(options.scale, options.scale);

to normalize the coordinate system to show CSS pixels. This is shown on mdn too.
Here's how a rendered site looks like without this fix:

And with this fix:

I can make a PR. How long until a new release could be made with this?  Thanks and GREAT tool!

An alternative would allow the scale to be configured instead of hard-coded:
scale: defaultView.devicePixelRatio || 1,


[Bug Report] Build failing on Clang 18 due to use of VLA

Describe the bug
tt-metal currently fails to build on clang 18 due to the use of VLA. With the following error message. I'm using clang 18 as that's what Arch is shipping.
In file included from /home/marty/Documents/not-my-projects/tt-metal/tt_metal/common/utils.cpp:8:
In file included from /home/marty/Documents/not-my-projects/tt-metal/tt_metal/llrt/rtoptions.hpp:17:
/home/marty/Documents/not-my-projects/tt-metal/tt_metal/common/core_coord.h:291:30: error: variable length arrays in C++ are a Clang extension [-Werror,-Wvla-cxx-extension]
  291 |         bool grid[max_y + 1][max_x + 2];

To Reproduce
Steps to reproduce the behavior:

Build tt-metal with clang 18 (cmake .. -DCMAKE_CXX_COMPILER=clang++-18 -DCMAKE_C_COMPILER=clang-18 -DCMAKE_BUILD_TYPE=RelWithDebInfo)
Observe the error

Expected behavior
Should build successfully.
Screenshots
If applicable, add screenshots to help explain your problem.
Please complete the following environment information:

OS: Arch Linux
Commit: 259daa277bfd8119a78c9663d81cef2a33fc7d0d

Additional context
Add any other context about the problem here.

Assigning @TT-billteng; I got mixed up in this due to some commit history snafus in a side branch.

Currently don't support clang 18. Will prioritize as a feature request.


Use a new tracy example in readme

Image was taken before multithreading was added so the graph is very misleading

Resolved 65df0ff


Add footer widget and code copy features

Fixes: https://github.com/minio/gluegun/issues/60

oh my prev pr removes the lib/_sidebar.erb.

@kaankabalak Excluded _sidebar.erb from the commit. Please check.


[Feature] Automations

Is it also possible to store the automations in the ioBroker object tree with the given API?
Background: If automation was triggered via the app / bridge, I would like to react to this in ioBroker.

see #657


Added gen2-fast-depth

Added gen2-fast-depth experiment.

Let's try to keep the repo size small; gifs could be stored on GitHub, eg upload in comment and copy the url to the README

:


Turn down git status output noise

Please consider this solution for #28.

nice

@YufengXin Can you merge this PR (to develop branch maybe, based on the documented workflow), and then close the PR? Thanks. :-)

I think I learned a thing today:
It might be that GitHub's defaults are a little lax.  I do not have access to the repository settings right now, so I can't change that, and I should not be making such policy decisions unilaterally anyway.  We should probably discuss this separately. I am mainly making a quick note here.
It probably should be such that PRs should be merged only after reviewed and approved, if we want to be disciplined about this.
But that is something for later. :-)


VTOL Tilt Rotor arm/disarm and tilt control bug?

Using the latest px4 build as of a few days ago.
Is there any reason I would lose the ability to disarm my vtol tiltrotor aircraft from the rc transmitter after performing a transition to fixed wing mode as a test on the ground in an armed state? In multi-copter mode I can disarm though. I can also disarm during the transition phase in either state.

We could verify in a log, but I'm guessing this is due to the recent land detector changes which now only report not landed while in FW mode.
@sanderux  FYI

I ran a test in fixed wing mode where I powered on the aircraft, pressed the safety button, unkilled the aircraft via a switch on the transmitter, armed the aircraft via a switch on the transmitter, actuated some aileron controls, spun up the motors, spun down the motors, then tried disarming via the same switch i armed with on the transmitter.
14_08_15.ulg.tar.gz

I may have misunderstood. Disarming via RC is intentionally disabled for FW so it doesn't happen in flight accidentally.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Securing pages outside of ANCESTOR_ID sub-folder structure from deletion

First of all, thanks for enabling asciidoc publication to Confluence!
I want to expose and discuss here an unfortunate use case where few pages got deleted and lost without Confluence trash recoverability.
The issue is that confluence-publisher seem to indirectly allow deletion of pages outside of ANCESTOR_ID sub-structure.
Scenario:
Assume Confluence space contains pages structure, manually created, such as below:
<project1>
 +- Designs
    +- design-A
    +- design-B
 +- any-other-folders
    +- ...
<project2>

We publish project2 from adoc using confluence-publisher folder structure.
The target Confluence structure is the same as page structure used in project1.
IOW, project2 to be published has following structure:
<project2>
 +- Designs
    +- design-C
    +- design-D
 +- any-other-folders
    +- ...

What happens is that during publication, confluence-publisher:

moved the "Designs" page from project1 into project2 structure (the page indeed has same name "Designs")
deleted "design-A" and "design-B" pages
then publication went on as expected for "design-C", etc

Note that deleted "design-A" and "design-B" pages are not found in Confluence trash.
What do you think of this use case?
Browsing the code, I see that page can be fetched by title and first one with given name is returned.
ConfluenceRestClient.java in getPageByTitle(...) l.128
    String contentId = extractIdFromJsonNode(jsonNode.withArray("results").elements().next());

Does this explain my unfortunate deletions?
At last, do you have knowledge why the deleted document are not in Confluence trash?

For this scenario of moved pages under AncestorId, orphanRemovalStrategy=KEEP_ORPHANS seems a good workaround to avoid deletes.


Adds two randomized equivalence oracles based on the W method

Here is my implementation of the randomized W/Wp method. It is more successful in finding counter examples than the current W/Wp methods in learnlib, but they do not provide any completeness guarantees. (Of course it is also more efficient than just a random walk.)
I have some concerns with the current state of affairs. In particular I found it annoying that I had to implement execution of tests and a bound in each equivalence oracle. I think that this can be decoupled, in order to make more generic testing oracles which can be reused. I will open a separate issue to discuss this.
In the meantime, this patch works, and provides a nice utility. I noticed that it is not consistent with the current naming, but I don't really like the current naming (all oracles ends with EQracle...)

See #41 for some thought on testing equivalence oracles.

I renamed the classes to end on EQOracle.


Shell fails to open in a pod

Setup

Rancher version: v2.9-c9be13b09329bbee60a5f6419d500198f83c44d1-head
Browser type & version: Google Chrome 123.0.6312.107 (Official Build) (arm64) and Safari 16.6

Describe the bug
Shell fails to open in a pod due to an unknown path /bin/sh: no such file or directory: unknown. According to the console logs, the error occurs in file ContainerShell.vue:319.
To Reproduce

Create a downstream cluster (in this example, it's a GKE cluster)
When the cluster is available, via UI, go to Workloads > Pods and click on the 3 dot button of any pod, then click on Execute Shell
Observe the error message when the shell is open

Result
Shell fails to open in a pod due to an unknown path /bin/sh: no such file or directory: unknown
Expected Result
Shell should be open in a pod with no errors
Screenshots

I wonder if this is related to changing the underlying image to BCI?
We should confirm if this is a bug in 2.7 and 2.8 as well

Will file something for Mapps to figure out what we can do around new BCI behaviours. Ideally, the UI could detect that there is no shell and elegantly state there's nothing to shell into.

@IsaSih when you get a moment, can you check the behaviour in 2.8.x? I don't know if we have to go back into 2.7.x at all but that may help if the problem existed somewhat earlier than 2.9.0

This issue does not occur in version 2.8-head. Tested on v2.8-94108186cf35028bb5f7db2c34c5ae99450dad9b-head

Internal reference with Mapps: SURE-8318
May have to monitor here as that team works on that in case it comes back to UI or QA

We should re-validate that this is still an issue - I believe this is down to a change in base image which does not contain sh - I think this may have been fixed - we should validate.
Should also add an automated test for this.

Worked through this with Neil.
The description shows pods with images not from Rancher, it looks like those just don't contain a shell so will never work.
I've brought up a new v2.9-head with the BCI change and can confirm some work

alertmanager-rancher-monitoring-alertmanager-0, cattle-monitoring-system, docker.io/rancher/mirrored-prometheus-alertmanager:v0.26.0
gitjob-7f85cd5774-4r429, cattle-fleet-system, rancher/fleet:v0.10.0-rc.13

and some don't

capi-controller-manager-64b8d54977-c54w6, cattle-provisioning-capi-system, rancher/mirrored-cluster-api-controller:v1.4.4
coredns-6799fbcd5-dzggt, kube-system, rancher/mirrored-coredns-coredns:1.10.1

I don't think this is a regression, but we need to make the error clearer. One is the root failure and one is from the UI. We can do this by adding a return after each error and maybe some before our error.

Holding on backport for now until someone picks this up to see what a solution looks like.

I updated to logging so that it's easier to parse when an error occurs, we'll also get some additional context when /bin/sh is missing from the container.
@gaktive this will be a fairly easy change to backport, what should our targets be at this point?

@gaktive this will be a fairly easy change to backport, what should our targets be at this point?

Following up from my previous comment: we discussed backporting OOB and decided that there is no need to do so at this point.


Changes to footer CSS

In response to Issue #29. I changed the height of the footer section to 20vh. I changed the Facebook icon to 2.5 rem.

Perfect, looks good to me.  Thank you!


Owls 103828 - Fix for the Cluster and Domain 'Available' conditions for admin only domains and intentionally shutdown clusters

Owls 103828 - Fix for the Cluster and Domain 'Available' Conditions for admin only domains and intentionally shutdown clusters. This PR includes changes from the PR # 3597 (OWLS-103825 branch).

Set Cluster 'Available' Condition to false if no servers expected to run.
Set Domain 'Available' Condition to true if only admin server is running and cluster(s) and managed servers are intentionally shutdown.

Integration test run - https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/13685/console

@ankedia @lennyphan Does this PR include all the changes from PR 3597 for OWLS-103825? Do we still need PR 3597?

@ankedia @lennyphan Does this PR include all the changes from PR 3597 for OWLS-103825? Do we still need PR 3597?

This PR includes the changes from PR 3597.  We made a conflicting change so decided it was best to resolve both JIRA's in one PR, if possible.

Please also update the doc to something similar to what we discussed in the Slack...

The doc update LGTM.


Caves and ores below y=0 in VanillaCubic

What needs to be done:

[ ] caves and ravines
[ ] other structures
[ ] vanilla ores
[ ] modded ores

Is this a poll or a checklist?

This could be useful for ores: https://github.com/way2muchnoise/JustEnoughResources

You probably know already, but I wanted to point out that it exists in the CustomCubic world type, not sure if that's portable code

it is, but it requires a bit of changes to make sure it interacts correctly with vanilla caves.


Update sbt-tpolecat to 0.1.17

Updates io.github.davidgregory084:sbt-tpolecat from 0.1.14 to 0.1.17.
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.github.davidgregory084", artifactId = "sbt-tpolecat" } ]

labels: sbt-plugin-update, semver-patch

Superseded by #168.


M1 debugger unable to build

I have problems to built the debugger library
I read the document InstructionsForBuildingLLDBInterface.txt  and also  #4035
this is my system
Mac mini M1
Monterey 12.3.1
ghidra_10.1.3_PUBLIC
lldb-13<IP_ADDRESS>
Apple Swift version 5.6 (swiftlang-<IP_ADDRESS>3.62 clang-13<IP_ADDRESS>)
java version "17.0.1" 2021-10-19 LTS
Java(TM) SE Runtime Environment (build 17.0.1+12-LTS-39)
Java HotSpot(TM) 64-Bit Server VM (build 17.0.1+12-LTS-39, mixed mode, sharing)
I have done the follow to build
I skip the first 2 step because I just have lldb v 13 installed (not the brew version)
git clone https://github.com/llvm/llvm-project.git
export JAVA_HOME=$(/usr/libexec/java_home)
export LLVM_HOME=/Users/cri/llvm-project
export LLVM_BUILD=/Users/cri/llvm-project
gradle build
The modules decompiler , sleigh , demangler_gnu_v2_33_1 is built correct in arm64
but I received the follow message from gradle

Configure project :Debugger-swig-lldb
OS: Mac OS X
Arch: aarch64 (gradle: arm-v8)
Using platform: mac_arm_64

Configure project :Decompiler
OS: Mac OS X
Arch: aarch64 (gradle: arm-v8)
Using platform: mac_arm_64

Configure project :PDB
OS: Mac OS X
Arch: aarch64 (gradle: arm-v8)
Using platform: mac_arm_64

Task :Debugger-swig-lldb:checkLLVM
Debugger-swig-lldb: using LLVM_HOME=/Users/cri/llvm-project

Task :Debugger-swig-lldb:linkMainMac_arm_64SharedLibrary FAILED
ld: warning: directory not found for option '-L/Users/cri/llvm-project/lib'
ld: library not found for -llldb
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Task :Debugger-swig-lldb:linkMainMac_x86_64SharedLibrary FAILED
ld: warning: directory not found for option '-L/Users/cri/llvm-project/lib'
ld: library not found for -llldb
clang: error: linker command failed with exit code 1 (use -v to see invocation)

FAILURE: Build completed with 2 failures.
1: Task failed with an exception.

What went wrong:
Execution failed for task ':Debugger-swig-lldb:linkMainMac_arm_64SharedLibrary'.

A build operation failed.
Linker failed while linking liblldb-java.dylib.
See the complete log at: file:///Applications/ghidra_10.1.3_PUBLIC/Ghidra/Debug/Debugger-swig-lldb/build/tmp/linkMainMac_arm_64SharedLibrary/output.txt
Linker failed while linking liblldb-java.dylib.

The content of the output file is
See file:///Applications/ghidra_10.1.3_PUBLIC/Ghidra/Debug/Debugger-swig-lldb/build/tmp/linkMainMac_arm_64SharedLibrary/output.txt for all output for linkMainMac_arm_64SharedLibrary.
linking liblldb-java.dylib failed.
ld: warning: directory not found for option '-L/Users/cri/llvm-project/lib'
ld: library not found for -llldb
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Finished linkMainMac_arm_64SharedLibrary, see full log file:///Applications/ghidra_10.1.3_PUBLIC/Ghidra/Debug/Debugger-swig-lldb/build/tmp/linkMainMac_arm_64SharedLibrary/output.txt.
And no dylib is created in the lib folder
/Applications/ghidra_10.1.3_PUBLIC/Ghidra/Debug/Debugger-swig-lldb/build/libs
Is correct to set  export LLVM_BUILD=/Users/cri/llvm-project. like  LLVM_HOME. ?
The instructions tellto  set LLVM_BUILD “path_to_llvm_build_directory_or_whatever_contains_lib/liblldb.(so/dylib/dll)”
I can find any dylib named  liblldb
The path that appear in error message
ld: warning: directory not found for option '-L/Users/cri/llvm-project/lib'
Doesn’t exist in   llvm-project
Thank you for your help

@crismi2 OK, going to ask a stupid question, but....have you already built llvm_project?  During that build process, you would have specified the "build" library.  I usually put it in llvm_project, but some folks consider that a bit unsanitary.  In any case, if that build succeeded, llvm_project/build/lib should have liblldb.13.0.1.dylib and a link liblldb.dylib in it.  You want LLVM_BUILD to point to one of those.

@d-millar  Thank you so much for your time
I made a big mistake
I compiled llvm using brew and modified the gradle.build as you explained and it was all sorted out in no time
Thanks again


patched input strategy

In the paper, "we compare resizing the cropped faces to 224×224 with the bilinear interpolation
and patching 224×224 the patches from the face images, and patched input strategy achieves better ACER metric." I don't understand what's  'patched input strategy', can you explan that? thx!!!

Hi，mydlgit, this strategy is to crop the 224x224 patches directly from the original face images, which means that there is no resize operation

Hi mydlgit, we have submitted new code with patched input strategy, please infer https://github.com/VIS-VAR/LGSC-for-FAS/pull/8


Set up a full working logging + runnable scripts for VM

partially done in #60

I think that we can withdraw this one - scripts will be replaced by pipelines

Yes


Not remove unused docker image in Portainer

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description

It existed docker image in server.
Expected Behavior
I want to delete Unused images in Portainer UI, how to delete Unused images in Portainer UI.
Actual Behavior
It shows Failure error.
Steps to Reproduce

Go to Images
Set Filter "Unused"
Check list and click remove button

Portainer logs or screenshots
No response
Portainer version
2.21.1
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
2.21.1
OS and Architecture
Linux
Browser
No response
What command did you use to deploy Portainer?
No response
Additional Information
No response

After a refresh is the image now gone?

No, It exists the image, and show the grid on Portainer.

I fight these problem after switch from standalone to swarm.... (More than one year ago..) not found any solution.... if you try to delete it again and again, once in a while it will work. I think , when it "found" the node , where the image are really exist...
I already give it up, go to the spec. node and delete it with terminal.
But i really like that these problem are fixed sometime

@vampywiz17 Ah yes, I remember this now. @jjkim0816, this is an issue we’ve encountered before, and I will check/raise it internally. We have tested this in Swarm, and when trying to delete an image that exists on a specific node, it seems to check a random node each time. If you repeatedly click delete, the image will eventually be removed.

@vampywiz17 Ah yes, I remember this now. @jjkim0816, this is an issue we’ve encountered before, and I will check/raise it internally. We have tested this in Swarm, and when trying to delete an image that exists on a specific node, it seems to check a random node each time. If you repeatedly click delete, the image will eventually be removed.
internal: BE-11259

Exactly! Any plan to try fix it? Very annoying...

Thank you, @vampywiz17. It showed popup message on Potainer UI when tried to delete image.
As a result, there is no images in any node.

Is this possibly related to BE-11062?
https://github.com/portainer/portainer/issues/12068

Is this possibly related to BE-11062?
#12068
https://github.com/orgs/portainer/discussions/12067

Maybe yes. Seems the problem is that Portainer dont know, which node on the image currently. Seems randomly try to access it one of node. Sometime success , sometime not...
It not only affect delete, but all operation on image. Tag, Push, etc...
It is really annoying, weeks ago i use command promt instead. Butthe reason to install portainer that not need to use terminal...

I just see the very same with version 2.21.4 of Portainer throughout a docker swarm. Also here no hosts liste in the host column an operations on tag, push, etc. are not working because there is always an error when selecting an image to perform a certain operation on it. Hope this gets fixed anytime soon since this really limits functionality of portainer to some extend.

Any progress guys? I alread made a Ansible rules to manage the image things (push,delete, etc...) because it totally useless now in swarm mode....

This issue still exists in the latest 2.24.1 version of Portainer.

This issue still exists in the latest 2.25.1 version of Portainer.


Add Cython tip when you install aiohttp in documentation

one note, i don't have pip3, i have only pip

Well, we are assume the environment is always Python3 ready.
I've changed pip3 -> pip in 3846bb7


feat: 🎸 can optionally pass initial params to optimize function

:tada: This PR is included in version 1.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Leaderboard row count percentage in tooltip 2

This prototype PR updates the leaderboard tooltip in two ways:

removes the row label from the top of the tooltip, since this is redundant information (the row label is always shown)
replaces the row label with the number of rows and the percentage of filtered rows that each leaderboard row represents.

If no filters are active, then the row count and percentage are out of all available data:

If a filter is active, then we only use the filtered row count, and the tooltip mentions "filtered rows"

@hamilton this PR is ready for review. FYI, the tricky bug I mentioned in slack that @skokenes tests caught seemed to be caused by what I will call, for lack of a better term "slot drilling" -- passing target component down slots through multiple layers of other components, which was preventing the target component from getting rerendering/getting updated props even though I could see in the console that the parent of this target component was getting (and should have been passing on) new props. Flattening out DimensionLeaderboardEntrySet.svelte fixed this problem, though it does means I touched more files than I might have desired.
(I recall that about a month ago I encountered a similar problem of a slotted component not updating correctly, so it's something to watch out for)
@jkhwu per your request, tagging you here so you can see @hamilton's proposed approach re the tooltip.

@hamilton I also want to point out one behavior detail and get your take -- in the image below, when I hover on the row for "Google", the leaderboard entry shows a value (which in this case happen to be the same as the row count) even though the row is actually not included in the filter. This also means that the row count inline query data is available, so we are able to show the number of rows for Google in the tooltip. However, since Google is not actually included in the 32k filtered rows, it doesn't really make sense to say that google is "18k of 32k filtered rows", since its really 0 of 32k filtered rows

I think I'd recommend that if we want to indicate the proportion of filtered rows, we should simply say "excluded from current filter set" or something along those lines, but this could be confusing in other ways. In general, the semantics of items that are not included in the filter set but are shown in a leaderboard could bear some more detailed thought wrt to old denominator problem, since they are shown to the user but not included in any summary number

the tricky bug I mentioned in slack that @skokenes tests caught seemed to be caused by what I will call, for lack of a better term "slot drilling" -- passing target component down slots through multiple layers of other components, which was preventing the target component from getting rerendering/getting updated props

Interesting, I saw a similar bug in our UI a couple of weeks ago that was not completely solved by, but was helped by, flattening some "slot drilling" happening. It makes me question where there is some underlying bug with slots in Svelte that we keep hitting

@skokenes I talked to @hamilton this morning and he suggested that I tag you for review on this one, though we will hold off on merging for a moment while some product and design discussions are happening

closing as obsolete -- we put this info in the context column in the leaderboards


Use @slot for slot descriptions in template comments

Suggesting using @slot in the HTML comment for Vue templates so that it's more inline with the other notations such as @model and @event. This would also allow for another comment to follow the slot description and not override it.
Love the project. Keep up the great work!

Thanks @dbryantm for the PR!, I will review it and then publish it.
Regards!


Patch 7 to master

The license items from April and May are added with a bit of guidance.
Please use this template to ensure easier processing of your pull request
Category

[x] Content fix
[ ] New article

Related issues:

fixes #141

What's in this Pull Request?
The updates with RPA!
Guidance
Post as is after review thanks

Docs Build status updates of commit 6facb47:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Community/known-folder-move-benefits-for-enduser.md
:white_check_mark:Succeeded
View

Community/powerplatformlicensingforcitizendeveloper.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

Thanks!

Can we kill the bad PR?
Get Outlook for iOShttps://aka.ms/o0ukef

From: Marc D Anderson<EMAIL_ADDRESS>Sent: Wednesday, May 27, 2020 3:51:40 PM
To: MicrosoftDocs/microsoft-365-community<EMAIL_ADDRESS>Cc: Ralph Rivas<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/microsoft-365-community] Patch 7 to master (#181)
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmicrosoft-365-community%2Fpull%2F181%23issuecomment-634932410&data=02|01||c11271c64c944fd3f82e08d8027fc207|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637262095017684225&sdata=A1FtkLDx1PfAnqV3HgCsgMLd%2BjAMeo5WRLiwhy4YpOQ%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAB2OOTRE56S53W2LPTJSISDRTV4NZANCNFSM4NMPULRA&data=02|01||c11271c64c944fd3f82e08d8027fc207|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637262095017694214&sdata=LZOU9EJIp%2F7%2BqlfRNjrDuNuK8dLnVm0X3fJpXOEdkrU%3D&reserved=0.

I closed it, so it should be no more.


Dependency issue in 17.1 (Microsoft.VisualStudio.CodeCoverage.Shim)

Description
17.1 breaks dependency on Microsoft.VisualStudio.CodeCoverage.Shim (<IP_ADDRESS>)
Tests running just fine in 17.0
Switching to 17.1 makes the tests suddenly throw an exception about the above dependency not being able to load.
Steps to reproduce
I don't know what is really causing this.
This is how our task in the DevOps pipeline is set up:
steps:
- task: VisualStudioTestPlatformInstaller@1
  displayName: 'Visual Studio Test Platform Installer'
  inputs:
    versionSelector: specificVersion
    testPlatformVersion: 17.0
- task: VSTest@2
  displayName: 'Unit test solution'
  inputs:
    testAssemblyVer2: |
     **\*UnitTests.dll
     !**\obj\**
    vsTestVersion: toolsInstaller
    codeCoverageEnabled: true

Target framework: .NET Framework 4.8
DevOps Build Agent: Self hosted
Expected behavior
Expect tests to run just as fine with 17.1 as with 17.0
Actual behavior
The following exception is thrown in 17.1, not in 17.0:

##[error][xUnit.net 00:00:05.93] Our.UnitTests: Catastrophic failure: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.CodeCoverage.Shim, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
##[error]File name: 'Microsoft.VisualStudio.CodeCoverage.Shim, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
##[error]   at Xunit.DiaSessionWrapperHelper..ctor(String assemblyFileName)   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
##[error]   at ExceptionExtensions.RethrowWithNoStackTraceLoss(Exception ex) in C:\Dev\xunit\xunit\src\common\ExceptionExtensions.cs:line 29
##[error]   at Xunit.AppDomainManager_AppDomain.CreateObject[TObject](AssemblyName assemblyName, String typeName, Object[] args) in C:\Dev\xunit\xunit\src\xunit.runner.utility\AppDomain\AppDomainManager_AppDomain.cs:line 85
##[error]   at Xunit.DiaSessionWrapper..ctor(String assemblyFilename) in C:\Dev\xunit\xunit\src\xunit.runner.utility\Utility\DiaSessionWrapper.cs:line 22
##[error]   at Xunit.VisualStudioSourceInformationProvider..ctor(String assemblyFileName) in C:\Dev\xunit\xunit\src\xunit.runner.utility\Frameworks\VisualStudioSourceInformationProvider.cs:line 24
##[error]   at Xunit.XunitFrontController..ctor(AppDomainSupport appDomainSupport, String assemblyFileName, String configFileName, Boolean shadowCopy, String shadowCopyFolder, ISourceInformationProvider sourceInformationProvider, IMessageSink diagnosticMessageSink) in C:\Dev\xunit\xunit\src\xunit.runner.utility\Frameworks\XunitFrontController.cs:line 70
##[error]   at Xunit.Runner.VisualStudio.VsTestRunner.RunTestsInAssembly(IRunContext runContext, IFrameworkHandle frameworkHandle, LoggerHelper logger, TestPlatformContext testPlatformContext, RunSettings runSettings, IMessageSinkWithTypes reporterMessageHandler, AssemblyRunInfo runInfo) in /_/src/xunit.runner.visualstudio/VsTestRunner.cs:line 498

Diagnostic logs
As this is observed only in our DevOps pipeline, getting these logs is not easily done.
Environment
Operating System: Windows Server 2019
vstest.console:
Microsoft (R) Test Execution Command Line Tool Version 17.1.0
Copyright (c) Microsoft Corporation.  All rights reserved.
vstest.console.exe "C:\VSTSAgent\_work\9\s\Tests\Our.UnitTests\bin\Release\Our.UnitTests.dll"
"C:\VSTSAgent\_work\9\s\Tests\Our.Services.UnitTests\bin\Release\Our.Services.UnitTests.dll"
/Settings:"C:\VSTSAgent\_work\_temp\kxszxmgj3no.tmp.runsettings"
/Logger:"trx"
/TestAdapterPath:"C:\VSTSAgent\_work\9\s"

I know the stack trace above points to Xunit, and it may seem the error lies with them, but seeing as this happens when changing the vstest version it's likely not an Xunit issue. Changing vstest from 17.0 to 17.1 should not result in breaking changes.

@jakubch1 can you look into this?

@gthvidsten we will investigate this issue. As workaround you can try to add runsettings and with content:
<?xml version="1.0" encoding="utf-8"?>
<!-- File name extension must be .runsettings -->
<RunSettings>
  <DataCollectionRunSettings>
    <DataCollectors>
      <DataCollector friendlyName="Code Coverage" uri="datacollector://Microsoft/CodeCoverage/2.0" assemblyQualifiedName="Microsoft.VisualStudio.Coverage.DynamicCoverageDataCollector, Microsoft.VisualStudio.TraceCollector, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">
        <Configuration>
          <CodeCoverage>
            <UseVerifiableInstrumentation>False</UseVerifiableInstrumentation>
          </CodeCoverage>
        </Configuration>
      </DataCollector>
    </DataCollectors>
  </DataCollectionRunSettings>
</RunSettings>

Please check: https://github.com/microsoft/vstest/issues/1654

This seems to be working for us though https://github.com/microsoft/azure-pipelines-tasks/issues/12808#issuecomment-634609977 but probably not the best option

I can confirm that the @jakubch1 fix is working as expected and for now it's the way to go.
We found the root cause of issue on the agent side that we'll fix soon as possible.

@rkapoor028 Are you still experiencing issue with newer versions?

Closing the issue. Feel free to ping us if you are still having any issue.

I am still facing the very same issue, with VS Professional version 17.8.4
========== Starting test run ==========
Testhost process for source(s) 'C:\Users\xxx\IntegrationTests.dll' exited with error: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.CodeCoverage.Shim, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
   at Microsoft.VisualStudio.TestPlatform.ObjectModel.EqtTrace.Error(String format, Object[] args)
   at Microsoft.VisualStudio.TestPlatform.TestHost.Program.Main(String[] args) in /_/src/testhost.x86/Program.cs:line 41
. Please check the diagnostic logs for more information.
Testhost process for source(s) 'C:\Users\xxx\IntegrationTests.dll' exited with error: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.CodeCoverage.Shim, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
   at Microsoft.VisualStudio.TestPlatform.ObjectModel.EqtTrace.Error(String format, Object[] args)
   at Microsoft.VisualStudio.TestPlatform.TestHost.Program.Main(String[] args) in /_/src/testhost.x86/Program.cs:line 41
. Please check the diagnostic logs for more information.
========== Test run aborted: 0 Tests (0 Passed, 0 Failed, 0 Skipped) run in < 1 ms ==========

I am using Microsoft::VisualStudio::CppUnitTestFramework. I've tried the above comment to no avail.


Integration: raw fetch / graphql-request

Done in https://github.com/graphprotocol/graph-client/pull/7

graphql-request provides a GraphQLClient but I don't see it used or generated anywhere. Might make sense to provide a out-of-the-box integration for this too.
Link to GraphQLClient source code: https://github.com/prisma-labs/graphql-request/blob/1565d490407a57b79447e5d82b1fa34d5a959005/src/index.ts#L222

@kasparkallas We don't need GraphQLClient or graphql-request in Graph Client.
We have easier options;

execute -> https://github.com/graphprotocol/graph-client/blob/main/examples/node/src/index.ts#L4
SDK -> https://github.com/graphprotocol/graph-client/blob/main/examples/cross-chain-sdk/src/index.ts#L4

@ardatan The title just mentioned graphql-request for integration and I have a small library that takes GraphQLClient as input.
Looking at GraphQLClient definition, it doesn't look very extendable... I'll just find a solution without it. Thanks again!


Remove the default "## Changes" section

This PR is to remove the default "Changes" section in the release so that we enforce the maintainer to put every PR in a dedicated section.
Also, this should ensure the "breaking changes" section is at the top of the release (following https://github.com/meilisearch/integration-guides/issues/148)

bors merge


Unvendor dependencies

As part of the OpenSSF Best Practices badges, we must monitor and periodically verify that none of the project dependencies contain known vulnerabilities. We also need to have the dependencies in a machine-parseable format. And we also need to make it easy to update dependencies.
Currently, all our dependencies are vendored in src/rez/vendor. This makes it hard to monitor them and update them. It's also very easy to start modifying them, which makes it even harder to update them after. Even worse, some of our vendored dependencies were heavily modified :(
This was done mainly because some studios don't have internet access and the original author of rez wanted these studios to be able to install rez in an easy way. Another reason was because rez is "special". After multiple conversations within the TSC, we think that this is not a valid concern for multiple reasons:

they still need to download rez in some ways
they probably have other softwares to install that do require internet access to be installed
they probably already have infrastucture in place to mirror parts of the internet. For example they probably have a PyPI cache/mirror in place (Artifactory, Nexus, devpi, etc).

But vendoring does provide value because dependencies are guaranteed to always work due to the fact that their version are baked and the code is vendored.
We should look at unvendoring our dependencies. We'll have to plan this very carefully and potentially do it gradually. We might also want to run our test suite using the lowest and highest supported version of each library (so one run with lower bounds and one with upper bounds) and have them run on a periodic basis. We'd want these tests to report any error very loudly so that we can address incompatibilities with newer versions.
We could have a requirements.txt file for users that install with the install script. That requirements file would have == for all versions. (Not sure though).
Requirements:

https://www.bestpractices.dev/en/projects/8389?criteria_level=1#external_dependencies
https://www.bestpractices.dev/en/projects/8389?criteria_level=1#dependency_monitoring
https://www.bestpractices.dev/en/projects/8389?criteria_level=1#updateable_reused_components
https://www.bestpractices.dev/en/projects/8389?criteria_level=1#interfaces_current

I'm not entirely on board with this idea (But hear me out).
I think a valid alternative might be looking into an automated approach to vendoring dependencies, such as using the https://pypi.org/project/vendoring/ project. (I am not saying this exactly, but, some sort of similar automated approach). I could imagine a setup where the dependencies are still shipped as vendored (provided that licensing is not a problem as it isn't a problem now), but that it is easier to automatically apply updates to the latest things automatically, automatically test that nothing is broken, etc. The same caveats of "doing this carefully" apply, and I do agree we should remove any/every vendored dep that we don't actually need, but I don't necessarily think that moving to a "user pip-installs things" model is 100% the best approach.

Thanks for the input @maxnbk!
I'd be very interested in understanding what makes you hesitate. You probably wrote about this in the past, but I can't remember your arguments. When you have time, can you describe what value you see in keeping our dependencies vendored please? I did try to add some pros in the issue description, but I'm sure I missed some.
It might be one of these decisions that will require us to prob the community to get a good sense of what they want. I could even take some time to write a proper REP with lots of details and clear details on how things would work for our users.

I think a valid alternative might be looking into an automated approach to vendoring dependencies, such as using the https://pypi.org/project/vendoring/ project.

I thought about using vendoring and I think it would work. But it wouldn't remove us the burden of keeping things up to date. We'd have to come up with a way to automatically monitor the vendored dependencies and update them. That could be achieved by creating a requirements.txt file and feed it to vendoring. With that requirements.txt file, we could instruct dependabot to create PRs when newer versions are available.  The missing piece is how to actually trigger the re-vendoring process from there. I'm not sure how we could do that.
I'm still not sold to the idea though. It just adds us more work and things to maintain. Another argument for unvendoring is that we get support for newer python versions for free.

Edit: And, in the case that we decide to nix the easy "install rez behind studio firewall" capabilities, we should be very careful to explicitly state what approach we expect users/studios to take who are in that scenario, and vet that the approach works. While it was never an explicitly stated "compatibility guarantee", it was a fairly big implicit compatibility promise that rez made for years and years, and we shouldn't necessarily abandon it without explicit alternatives laid out.

I agree that if we go that route, we'll need to better document how to deploy rez.

@instinct-vfx and @bpabel any opinions? I think Thorsten was/is supportive of unvendoring our dependencies, but a written statement might help here.

I don't see any reasons to vendor something that could simply be specified as a dependency that is handled at build time, so I'd prefer to get rid of them.
That being said, I think the most likely issue with switching from vendored libraries to dependencies is that it introduces the potential for dependency conflicts with other libraries that use the rez python api. I think that's actually a good thing for users of the api, because it means the 3rd party types are better defined and documented, rather than being an unknown version of some vendored library. And vendoring a library that's a different version than the normal installed version in a python environment has potential for weird errors as well, so vendoring isn't really a solution the issue, and I'd prefer to offload that problem to package management systems.
For the "install rez behind firewall" situation, all studios have at least one machine connected to the internet, and are capable of building a rez installation that can then by manually copied to all the other airgapped machines, so I don't really see that as a real issue. I also don't really like that rez needs to be installed from source. That really shouldn't be the way that rez is most commonly distributed IMHO.
I'd prefer to see rez deployed mainly as a bundled exe/app. PyInstaller is an option, but there are a ton of others. Technically, we'd still be redistributing dependencies, but they would be managed as dependencies via a package management tool, like pip-tools or poetry, instead of vendoring them. Using a package manager for dependencies that are resolved at build time makes managing them easier. It makes it trivial to use compiled dependencies with different versions for different architectures, python versions, OS's, etc. At the moment, we're basically limited to pure python dependencies because we vendor them.

From my POV, the most important aspect of vendoring was -- and still remains -- site package isolation.  Rez's python dependencies must be accessible only to the rez CLI -- they should not end up on the PYTHONPATH within environments created by Rez.   Hopefully that statement comes as no surprise.
That said, this story gets more complicated for those who wish to use rez as a python API.   With the vendored solution, you have a guarantee that providing access to the rez python package via the PYTHONPATH will not introduce Rez's third-party python libraries, e.g. yaml, in a way that could cause conflicts with your own third-party requirements.  This is a nice guarantee to have for such a low-level tool.   Providing access to rez's python dependencies via rez-pip is not a valid solution, because in order to detect/prevent conflicts, a studio would need to adopt rez-pip for their own tooling and, frankly, rez-pip is an abomination (Any solution that could add potentially hundreds of entries to the PYTHONPATH is a non-starter for performance reasons.  Also, Windows has a very real maximum on env-var length, and also python's platform compatibility tags can get very complex when it comes to platform, implementation, and ABI compatibility and trying to reverse engineer it using Rez concepts is a Sisyphean task).  I think that unvendoring will force you into a position where you, as the authors of Rez, are forced to prescribe how the users of Rez ought to handle python dependencies (in order to provide access to rez as a python API), and I think you
may want to carefully consider if you want to insert yourself into that debate.   As one of the lowest level tools in a studio, Rez is special -- it needs to keep a low profile and avoid creating the types of problems it's designed to solve.
Personally, I think the best choice is an automated vendoring solution like the one proposed by @maxnbk, so that you can achieve your OpenSSF goal rapidly without painfully rediscovering why vendoring was introduced in the first place.   If you choose not to vendor, that's fine, just make sure you carefully consider the API scenario presented above.

By the way, the policy and rationale for pip’s use of vendoring is probably relevant here: https://pip.pypa.io/en/stable/development/vendoring-policy/#

Sorry for not following up earlier. Will give some feedback today.

I have always been pro-unvendoring (or contra-vendoring?). The current status is a testament to how bad things get. The most recent (!) version vendored is 4 years old. For some of the dependencies we do not even really know. Not even if we may have modified dependencies.
For $current_job, we isolate our rez runtime environment completely. But even if you don't would you not at least use a virtualenv? Why would that force us to prescribe handling of dependencies? It is a virtualenv separate from whatever you would need on the system level or in other runtime environments.
I actually feel it is the other way around right now: I have no choice but use old vendored versions (that might get flagged by security scans and worst case enforce removal of rez alltogether). With dependencies documented as python dependencies we also get to use dependabot for example.
re: requirements.txt: For some of our projects we use requirements.in -> requirements.txt compilation to manage "general restrictions for requirements vs. version pins for releases". That seems to work quite well.
re: air gapped scenarios: My take always was there needs to be some kind of process in place already if you are in an air-gapped scenario and my expectation would be for studios to use their chosen process. (we are not, so this is pure speculation on my behalf!). We also use Nexus as a pypi proxy/cache that we also use to host internal packages privately for example.
Sorry for the brevity, this week is wild here. Also keep in mind this is from a mostly Windows perspective so i might be missing Linux specifics completely.

Just to be clear, nothing says that an automated-vendoring approach wouldn't also use dependabot-updatable-requirements files. I don't see that as an entirely valid argument either for or against; We want dependabot's to work and flag issues, but neither approach (other than leaving it as it is) has to go without that aspect.
I could imagine a world where we could ship a "all dependencies vendored-in" package, and an "some assembly required but you can tweak the requirements yourselves or bring in your own pypi cache or whatever"-package. (Which is really just the source, but that's semantics.)

Thank you so much @chadrik for taking some time to give us your perspective on this!
I'll take some time to reply to react to @instinct-vfx and @chadrik later, but

I could imagine a world where we could ship a "all dependencies vendored-in" package, and an "some assembly required but you can tweak the requirements yourselves or bring in your own pypi cache or whatever"-package. (Which is really just the source, but that's semantics.)

is what I'm kind of what I also was starting to think about.

I'm also not married to the "all deps vendored" not just being a matrix of platform/arch/os venv's that get built and shipped out from the same requirements, if it has to be that. Automation can still be what we get at the end of the day. Of course, it'd be a lot easier if we can still rely on locking ourselves to ABI-agnostic packages.

Two thoughts:
1: We have a way to download files to the locked-down production network - but not an easy way to mirror arbitrary set of PyPI dependencies.
So it is meaningfully easier to grab the rez source tarball and be ready to install it, compared to to grabbing the rez and finding/downloading 19 separate packages of the compatible versions for the vendored dependencies
I suspect this is not uncommon - it's been case in at least two places I've worked
Something like Gaffer's dependencies repo might be a good middleground - where the packages can be referenced in a way compatible with dependency scans, but also a known-good set of dependencies are packaged into a single download
2: A bunch of the dependencies (which are nicely listed here) look like they should maybe be removed, rather than unvendored, e.g

six should be unneeded now Python 2 support is dropped
enum also included in Python 3.4 onward
atomicwrites is unmaintained, and from it's README seems like it can now be implemented with os.rename
pydot seems like it could potentially replaced with a small helper function (removing the pyparsing dependency also) - as, based on very brief search, it it only seems to be used in graph_utils.py to essentially call dot tempfile.dot -o output.png

It's also hard to tell from that list which are dependencies-of-dependencies (e.g I think six is not used directly, unclear what requires it), and how that situation would change updating to newer versions


Automated cherry pick of #2921: fix: 避免删除不存在的快照出错

Cherry pick of #2921 on release/2.10.0.
#2921: fix: 避免删除不存在的快照出错

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@889c6d5). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release/2.10.0   #2925   +/-   ##
================================================
  Coverage                  ?   7.47%
================================================
  Files                     ?     414
  Lines                     ?   65974
  Branches                  ?       0
================================================
  Hits                      ?    4933
  Misses                    ?   60619
  Partials                  ?     422

Flag
Coverage Δ

#aFlag
7.47% <ø> (?)

Continue to review full report at Codecov.

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

/approve
/lgtm


OSAL API Documentation Should Be Doxygen Based

The OSAL API documents are currently available as separate word and .pdf documents.  The API's are defined and maintained in the source code.  Any changes or new findings to the API's can easily get left undocumented, creating a disconnect between the source code and what is stated in the OSAL API word and .pdf documents.  It is highly recommended to couple the documentation with the source code via doxygen.

Imported from trac issue 121.  Created by sstrege on 2015-11-30T17:28:19, last modified: 2019-08-14T14:11:46


Updated Snowplow Analytics listing in technologies

Updated the Snowplow Analytics listing in the technologies.json file.

Thanks!


Patch redis.Redis

Allow for magic patching redis for application that use redis-py such as message queues for socketio.

Test against celery broker and backend


Task Main Idea

I assume that we will do the following steps to carry out this task:
To determine the equilibrium configurations of Na4Cl4 clusters for tetramers and plot their configurations with energies, we can proceed with the following steps:

Define the potential energy function for the Na4Cl4 cluster.
For our case the potential energy is of the form:

The potential energy function parameters for the Na4Cl4 cluster are defined as follows:

$\ A_{ij} = 423.80 \ eV$
$\ \rho = 0.317 \ Å$
$\ \frac{e^2}{4 \pi \epsilon_0} = 1.44 \ eV·nm$

Initialize the cluster geometry to an ideal case.
Use an optimization algorithm to minimize the energy and find the equilibrium configuration.
Note: We will use CG algorithm for the optimization.
What about you guys?
Plot the equilibrium configurations using scatter plots and label them with their energies.

Correction to my views and your suggestions will  really be appreciated

Well I have read the paper but still trying on to figure it out. However, you are of great help. Thank you


bugfix/1540/fix UI for authorization form

Description
Fixed threw https://docs.google.com/spreadsheets/d/12P5AgSMLZywGaZsVRWR87HAODDG04-F7YM35R2qGeh4/edit#gid=1661224271

Refactored code of pages Login, GEnerate Password, Restore Password to meet the one standard.
 Please revise the file structure for them.
Changed background
Added adaptive design
Fixed unpretty loader Rectangle

Screenshots

Original
Updated

**  **
**  **

MOBILE

Original
Updated

:-----------------------:
:----------------------:

** **
** **

Fixed Loader Background

Original
Updated

**

**
**

**

Checklist

[x] 🔽 My branch is up-to-date with "development" branch
[x] ✅All tests passed locally
[x] ✨My changes working with up-to-date admin and back-end part locally, like charm
[x] 🔗 Link pull request to issue

Please clean code smells

@mrjnmzk fixed code smells

hi please change header according to mockap

hi please change header according to mockap when user move to recovery password page

The header component is reused in all pages, it's rendered on the recovery page in the same way as on others. Need new issue to fix it like on the mockup one.

I moved files with tests and components to separated folders. Fixed problem with responsive design at 320px screen resolution that was mentioned by @DeLettenhove


How do I perform validation?

❓ Questions and Help
Hello,
Once in a while I would like to perform test on validation set, what is right way to do so ?
THanks

Hi,
You could add a condition in here so that it calls the inference function to validate on a dataset.
You might need to pass a few extra arguments around, but it should be fairly straightforward.
But given that we are doing training on multiple GPUs, if you want to perform testing on multiple GPUs as well you might need to unwrap the model from the DistributedDataParallel, add a synchronize call in the end of the inference and wrap the model back in DistributedDataParallel just before the training starts again.
Let me know if you have further questions

unwrap the model from the DistributedDataParallel, add a synchronize call

Sorry but how to unwrap the model?
Like what should I change in this code:
`if iteration % checkpoint_period == 0 or iteration == max_iter:
model.eval()
iou_types = ("bbox",)
if cfg.MODEL.MASK_ON:
iou_types = iou_types + ("segm",)
inference(
model,
val_data_loader,
iou_types=iou_types,
box_only=cfg.MODEL.RPN_ONLY,
device=cfg.MODEL.DEVICE,
expected_results=cfg.TEST.EXPECTED_RESULTS,
expected_results_sigma_tol=cfg.TEST.EXPECTED_RESULTS_SIGMA_TOL,
verbose=False
)
            model.train()  # reset training flag
        synchronize()

`

@JoyHuYY1412 yes, this makes sense, but I won't guarantee that it will work 100% in all cases.

@JoyHuYY1412 yes, this makes sense, but I won't guarantee that it will work 100% in all cases.

It does not work with multigpu. I don't how to tell it just use one GPU in validation


782 optional schema switch

Description
Make the user able to disable the schema validation. By default the schema validator is used, the new switch disables it.
Changes

Added --disable-schema switch to commandlineBase
Added a provider for the ProfileSchemaValidator
Added NoopProfileSchemaValidator as the new validator if switch is used

Issue
Resolves #782

Codecov Report

Merging #800 into master will increase coverage by 0.12%.
The diff coverage is 43.75%.

@@             Coverage Diff              @@
##             master     #800      +/-   ##
============================================
+ Coverage     65.91%   66.03%   +0.12%
- Complexity     1696     1739      +43
============================================
  Files           277      280       +3
  Lines          6005     6095      +90
  Branches        699      710      +11
============================================
+ Hits           3958     4025      +67
- Misses         1795     1804       +9
- Partials        252      266      +14

Impacted Files
Coverage Δ
Complexity Δ

...c/deg/schemas/v0_1/NoopProfileSchemaValidator.java
0% <0%> (ø)
0 <0> (?)

...deg/generator/commandline/GenerateCommandLine.java
25.8% <0%> (-0.87%)
2 <0> (ø)

...eg/generator/commandline/VisualiseCommandLine.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...gic/deg/generator/commandline/CommandLineBase.java
37.5% <100%> (+8.92%)
1 <0> (ø)
:arrow_down:

...com/scottlogic/deg/generator/guice/BaseModule.java
85.36% <100%> (ø)
3 <0> (ø)
:arrow_down:

...enerator/guice/ProfileSchemaValidatorProvider.java
71.42% <71.42%> (ø)
2 <2> (?)

...or/restrictions/GranularityRestrictionsMerger.java
50% <0%> (-50%)
4% <0%> (-1%)

...enerator/restrictions/GranularityRestrictions.java
41.17% <0%> (-29.42%)
5% <0%> (-2%)

...r/reductive/fieldselectionstrategy/FieldValue.java
75% <0%> (-10.72%)
3% <0%> (-3%)

...or/walker/reductive/ReductiveRowSpecGenerator.java
100% <0%> (ø)
3% <0%> (ø)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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


Polars: rename accuracy to summarize

Closes #1939

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1943
#1942  👈
#1920
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Shoeboxam and the rest of your teammates on  Graphite


could you share your program to generate lmdb for rgb images?

Sure, I had given a tool in README.md. Please ref to it.


MI300 documentation

Mi300 documentation

@ooreilly @eemorsi please review this PR, we would like to merge this in.

@LisaDelaney Rebased our changes, please approve the PR, id it looks good.

Rebased the branch.


[Talk Proposal] P2P vs Lords of the Ring

About your talk
Title
From single computers to ONE. A quest for the precious.
Languages

[x] 🇫🇷
[x] 🇬🇧

Estimated duration
~20 min
Required knowledge level

Network
Cryptography
Blockchain
General Tech

[ ] None
[ ] None
[ ] None
[ ] None

[x] Beginner
[x] Beginner
[x] Beginner
[x] Beginner

[ ] Advanced
[ ] Advanced
[ ] Advanced
[ ] Advanced

[ ] Expert
[ ] Expert
[ ] Expert
[ ] Expert

Video recording

[ ] Yes (mandatory)
[x] Yes (if possible)
[ ] No

Description of your talk

Light Client - Client / Server - P2P

History: P2P Dark Age & Revival

Industry 4.0: DRM, Cloud, bio-authentication, 1st & 2nd class services, money! Feodal attitude ;(

Precious Unique ID!

Blockchain / Crypto = Web 3.0

Open Source != Libre

Politics / Media / Money

P2P & Private copy

Libra + Dune

Ḡ1 = Duniter + WOT

IPFS: Interplanetary MediaCenter + NextCloud

Decentralized Asynchronous Mesh Internet

REC Machine(s)
Music: https://github.com/ritiek/spotify-downloader ...
Video: https://sh.invidiou.sh/ ...

https://www.youtube.com/watch?v=H_kNnbieO7o
About you

Born in 72. Pong geek. Network engineer. Linkeo.com Founder. Autonomous living tech. Volunteer for global world change.

Name: Fred
Matrix handle: TODO
Discord handle: TODO
Other contact info<EMAIL_ADDRESS>Links to your previous talks: TODO
Other (your projects, etc...): MadeInZion. G1sms. Zicmama. CopyLaRadio
Availability (monthly number, date): 4 sept 2019 .

All right dude ! =)

Hey! Nice proposal :)
About the "Video recording" section, you just need to mention if you want your talk to be recorded then posted to p2p.paris website with 3 options:

if possible (you want to be recorded if the conditions are suitable: not to noisy, light ok, etc...)
mandatory (you want to be recorded and you prefer to postpone your talk if the conditions are not suitable)
no (you don't want your talk to be recorded)

I book you the last slot during the next event

https://tube.p2p.legal/videos/watch/f45b8e45-df35-4189-bd71-0050ca5c375b

@zicmama peux-tu m'envoyer un screenshot de ta presentation ou quelque chose que je peux mettre dans les slides d'intros qui presentent la soiree et les 2 talks stp ?

No slides :)


Installation error "error: identifier "__shfl_down" is undefined"  (Trying with Compute Capability  2.0)

I'm trying to install tensor flow from source, as I would like to use GPU's
that have compute capability == 2.0. (And I suspect that problems lies here and might be not have a trivial solution)
Environment info
Operating System:
uname -or
3.16.0-4-amd64 GNU/Linux
bazel release 0.2.0
Commit hash
git log --pretty=format:'%h' -n 1
99952d6
git log -1 --format="%H"
99952d68444cd2b08e88af972bd9eb7034fbc1e7
I use TF_UNOFFICIAL_SETTING=1 ./configure
and  choose Compute Capability  2.0
bazel build -c opt  --config=cuda  --spawn_strategy=standalone --verbose_failures  //tensorflow/cc:tutorials_example_trainer
Full output here : https://gist.github.com/cbonnett/97aec5a35209f0501993
What seems to be the key-error:
INFO: From Compiling tensorflow/core/kernels/sparse_xent_op_gpu.cu.cc:
external/eigen_archive/eigen-eigen-017cff30cf74/unsupported/Eigen/CXX11/src/Tensor/TensorReductionCuda.h(111): error: identifier "__shfl_down" is undefined
It seems "__shfl_down" was added in Kepler (compute capability == 3.x )
https://devblogs.nvidia.com/parallelforall/faster-parallel-reductions-kepler/
and as my cards are pre-Kepler, this seems to be the culprit. Can anybody confirm this ? or might there be a solution ?

Yeah, I don't think TensorFlow's or Eigen's GPU kernels are written for pre 3.0 compute capability :(

I was afraid that was the case....

Have you found the solution to undefined __shfl_down?
I am trying to install cunn for lua and I have the save issue:

error: identifier "__shfl_down" is undefined

I am using a GPU with compute capability 2.1.

I'm having the same problem.
`/tmp/luarocks_cunn-scm-1-7288/cunn/lib/THCUNN/SpatialClassNLLCriterion.cu(16): error: identifier "__shfl_down" is undefined
1 error detected in the compilation of "/tmp/tmpxft_0000402e_00000000-20_SpatialClassNLLCriterion.compute_20.cpp1.ii".
CMake Error at THCUNN_generated_SpatialClassNLLCriterion.cu.o.cmake:264 (message):
Error generating file
/tmp/luarocks_cunn-scm-1-7288/cunn/build/lib/THCUNN/CMakeFiles/THCUNN.dir//./THCUNN_generated_SpatialClassNLLCriterion.cu.o
make[2]: *** [lib/THCUNN/CMakeFiles/THCUNN.dir/./THCUNN_generated_SpatialClassNLLCriterion.cu.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [lib/THCUNN/CMakeFiles/THCUNN.dir/all] Error 2
make: *** [all] Error 2
Error: Build error: Failed building.
`
Any ideas?

I found a __shfl_down replacement here: https://github.com/parallel-forall/code-samples/blob/master/posts/parallel_reduction_with_shfl/fake_shfl.h
That might help you get around this particular compile issues.

I never looked for a solution, I was lucky enough to find access to some newer cards.

I meet the same problem, @cbonnett did you find a solution?

nope, I got access to newer GPU cards so that solved my problem. Theano should work fine though.

@zach-capalbo the replace func can compile well ,but is this func produce the same result as the offical one?

Try to move from cuda 10.1 to cuda 9.1 sudo apt install nvidia-cuda-toolkit and gcc-7 to gcc-5/gcc-6 . It worked for me after trying all solutions available so far.


why version 3 's aes speed up many times but sm4 remain unchanged

I running openssl on termux.
version 1.1.1
$ openssl speed aes
Doing aes-128 cbc for 3s on 16 size blocks: 42671097 aes-128 cbc's in 3.00s
Doing aes-128 cbc for 3s on 64 size blocks: 11475752 aes-128 cbc's in 3.00s
Doing aes-128 cbc for 3s on 256 size blocks: 2884822 aes-128 cbc's in 3.00s
Doing aes-128 cbc for 3s on 1024 size blocks: 730315 aes-128 cbc's in 3.00s
Doing aes-128 cbc for 3s on 8192 size blocks: 91601 aes-128 cbc's in 3.00s
Doing aes-128 cbc for 3s on 16384 size blocks: 45807 aes-128 cbc's in 3.00s
Doing aes-192 cbc for 3s on 16 size blocks: 36514008 aes-192 cbc's in 3.00s
Doing aes-192 cbc for 3s on 64 size blocks: 9648718 aes-192 cbc's in 3.00s
Doing aes-192 cbc for 3s on 256 size blocks: 2425423 aes-192 cbc's in 3.00s
Doing aes-192 cbc for 3s on 1024 size blocks: 612453 aes-192 cbc's in 3.00s
Doing aes-192 cbc for 3s on 8192 size blocks: 76775 aes-192 cbc's in 3.00s
Doing aes-192 cbc for 3s on 16384 size blocks: 38400 aes-192 cbc's in 3.00s
Doing aes-256 cbc for 3s on 16 size blocks: 33070936 aes-256 cbc's in 2.99s
Doing aes-256 cbc for 3s on 64 size blocks: 8671311 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 256 size blocks: 2178433 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 1024 size blocks: 549241 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 8192 size blocks: 68804 aes-256 cbc's in 3.00s
Doing aes-256 cbc for 3s on 16384 size blocks: 34403 aes-256 cbc's in 3.00s
OpenSSL 1.1.1m  14 Dec 2021
built on: Sun Jan 23 03:27:31 2022 UTC
options:bn(64,64) rc4(char) des(int) aes(partial) idea(int) blowfish(ptr)
compiler: aarch64-linux-android-clang -fPIC -pthread -Wa,--noexecstack -Qunused-arguments -fstack-protector-strong -Oz -DNO_SYSLOG -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DZLIB -DZLIB_SHARED -DNDEBUG  -I/data/data/com.termux/files/usr/include
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
aes-128 cbc     227579.18k   244816.04k   246171.48k   249280.85k   250131.80k   250167.30k
aes-192 cbc     194741.38k   205839.32k   206969.43k   209050.62k   209646.93k   209715.20k
aes-256 cbc     176968.22k   184987.97k   185892.95k   187474.26k   187880.79k   187886.25k
~ $ openssl speed sm4
speed: Unknown algorithm sm4
~ $ openssl speed -elapsed -evp sm4-cbc
You have chosen to measure elapsed time instead of user CPU time.
Doing sm4-cbc for 3s on 16 size blocks: 15331406 sm4-cbc's in 3.00s
Doing sm4-cbc for 3s on 64 size blocks: 4135146 sm4-cbc's in 3.00s
Doing sm4-cbc for 3s on 256 size blocks: 1068443 sm4-cbc's in 3.00s
Doing sm4-cbc for 3s on 1024 size blocks: 269379 sm4-cbc's in 3.00s
Doing sm4-cbc for 3s on 8192 size blocks: 33754 sm4-cbc's in 3.00s
Doing sm4-cbc for 3s on 16384 size blocks: 16885 sm4-cbc's in 3.00s
OpenSSL 1.1.1m  14 Dec 2021
built on: Sun Jan 23 03:27:31 2022 UTC
options:bn(64,64) rc4(char) des(int) aes(partial) idea(int) blowfish(ptr)
compiler: aarch64-linux-android-clang -fPIC -pthread -Wa,--noexecstack -Qunused-arguments -fstack-protector-strong -Oz -DNO_SYSLOG -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DPOLY1305_ASM -DZLIB -DZLIB_SHARED -DNDEBUG  -I/data/data/com.termux/files/usr/include
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
sm4-cbc          81767.50k    88216.45k    91173.80k    91948.03k    92170.92k    92214.61k

3.01
~ $ openssl version
OpenSSL 3.0.1 14 Dec 2021 (Library: OpenSSL 3.0.1 14 Dec 2021)
~ $ openssl speed aes
Doing aes-128-cbc for 3s on 16 size blocks: 172488051 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 64 size blocks: 81608439 aes-128-cbc's in 2.97s
Doing aes-128-cbc for 3s on 256 size blocks: 24524165 aes-128-cbc's in 2.96s
Doing aes-128-cbc for 3s on 1024 size blocks: 6571803 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 8192 size blocks: 832937 aes-128-cbc's in 3.00s
Doing aes-128-cbc for 3s on 16384 size blocks: 355297 aes-128-cbc's in 2.56s
Doing aes-192-cbc for 3s on 16 size blocks: 158186219 aes-192-cbc's in 2.96s
Doing aes-192-cbc for 3s on 64 size blocks: 72587495 aes-192-cbc's in 3.00s
Doing aes-192-cbc for 3s on 256 size blocks: 21085478 aes-192-cbc's in 3.00s
Doing aes-192-cbc for 3s on 1024 size blocks: 5417662 aes-192-cbc's in 3.00s
Doing aes-192-cbc for 3s on 8192 size blocks: 694263 aes-192-cbc's in 3.00s
Doing aes-192-cbc for 3s on 16384 size blocks: 334192 aes-192-cbc's in 2.95s
Doing aes-256-cbc for 3s on 16 size blocks: 156830489 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 64 size blocks: 63938219 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 256 size blocks: 18231596 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 1024 size blocks: 1943852 aes-256-cbc's in 1.23s
Doing aes-256-cbc for 3s on 8192 size blocks: 579493 aes-256-cbc's in 2.96s
Doing aes-256-cbc for 3s on 16384 size blocks: 298056 aes-256-cbc's in 3.00s
version: 3.0.1
built on: Tue Mar  1 12:36:05 2022 UTC
options: bn(64,64)
compiler: aarch64-linux-android-clang -fPIC -pthread -Wa,--noexecstack -Qunused-arguments -fstack-protector-strong -Oz -DNO_SYSLOG -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DZLIB -DZLIB_SHARED -DNDEBUG  -I/data/data/com.termux/files/usr/include
CPUINFO: OPENSSL_armcap=0xbf
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
aes-128-cbc     919936.27k  1758565.69k  2121008.86k  2243175.42k  2274473.30k  2273900.80k
aes-192-cbc     855060.64k  1548533.23k  1799294.12k  1849228.63k  1895800.83k  1856068.38k
aes-256-cbc     836429.27k  1364015.34k  1555762.86k  1618296.30k  1603786.03k  1627783.17k
~ $ openssl speed sm4
speed: Unknown algorithm sm4
~ $ openssl speed -elapsed -evp sm4-cbc
You have chosen to measure elapsed time instead of user CPU time.
Doing SM4-CBC for 3s on 16 size blocks: 14774526 SM4-CBC's in 3.00s
Doing SM4-CBC for 3s on 64 size blocks: 4092991 SM4-CBC's in 3.00s
Doing SM4-CBC for 3s on 256 size blocks: 1066587 SM4-CBC's in 3.00s
Doing SM4-CBC for 3s on 1024 size blocks: 269486 SM4-CBC's in 3.00s
Doing SM4-CBC for 3s on 8192 size blocks: 33798 SM4-CBC's in 3.00s
Doing SM4-CBC for 3s on 16384 size blocks: 16901 SM4-CBC's in 3.00s
version: 3.0.1
built on: Tue Mar  1 12:36:05 2022 UTC
options: bn(64,64)
compiler: aarch64-linux-android-clang -fPIC -pthread -Wa,--noexecstack -Qunused-arguments -fstack-protector-strong -Oz -DNO_SYSLOG -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DZLIB -DZLIB_SHARED -DNDEBUG  -I/data/data/com.termux/files/usr/include
CPUINFO: OPENSSL_armcap=0xbf
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
SM4-CBC          78797.47k    87317.14k    91015.42k    91984.55k    92291.07k    92301.99k
~ $

Assembly optimisations for AES but not for SM4?

Because in 1.1.1 the openssl speed aes does not use the AES-NI instructions. You have to compare -evp aes128-cbc  performance between 1.1.1 and 3.0 to see if there is any difference.

~ $ openssl speed -elapsed -evp aes-128-cbc
You have chosen to measure elapsed time instead of user CPU time.
Doing AES-128-CBC for 3s on 16 size blocks: 141590295 AES-128-CBC's in 3.00s
Doing AES-128-CBC for 3s on 64 size blocks: 71904736 AES-128-CBC's in 3.00s
Doing AES-128-CBC for 3s on 256 size blocks: 20703479 AES-128-CBC's in 3.00s
Doing AES-128-CBC for 3s on 1024 size blocks: 3232311 AES-128-CBC's in 3.00s
Doing AES-128-CBC for 3s on 8192 size blocks: 460202 AES-128-CBC's in 3.00s
Doing AES-128-CBC for 3s on 16384 size blocks: 229641 AES-128-CBC's in 3.00s
version: 3.0.1
built on: Tue Mar  1 12:36:05 2022 UTC
options: bn(64,64)
compiler: aarch64-linux-android-clang -fPIC -pthread -Wa,--noexecstack -Qunused-arguments -fstack-protector-strong -Oz -DNO_SYSLOG -DOPENSSL_USE_NODELETE -DOPENSSL_PIC -DOPENSSL_BUILDING_OPENSSL -DZLIB -DZLIB_SHARED -DNDEBUG  -I/data/data/com.termux/files/usr/include
CPUINFO: OPENSSL_armcap=0xbf
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
AES-128-CBC     755148.24k  1533967.70k  1766696.87k  1103295.49k  1256658.26k  1254146.05k
~ $

Now please run that command on 1.1.1 to be able to compare.

Now please run that command on 1.1.1 to be able to compare.

sorry, the openssl is upgraded and 1.1.1 is destroyed.

Anyway, my explanation stands. The openssl speed aes in 1.1.1 is not really relevant for showing the performance of an application unless the application uses the low level calls (and thus not using the aes-ni instructions even if available).

he is using arm instruction,and in 1.1.1, there is HWAES_encrypt define in https://github.com/openssl/openssl/blob/4bb34766d41489cfe95002e861f4a655727ebaf9/crypto/evp/e_aes.c#L2558.
and the compile config is the same.
maybe other reason?

The reason is still the same. The things in e_aes.c does not have any influence on openssl speed aes command in the 1.1.1 branch.

yes, I see it.in 1.1.1, https://github.com/openssl/openssl/blob/d3602088603605f39993f03781163df2decf85e3/apps/speed.c#L826-L83
just call AES_cbc_encrypt which is not Assembly optimisation code.while in 3.0，https://github.com/openssl/openssl/blob/e9492d1cecf459261f1f5ac0eb03e9c631600537/apps/speed.c#L2078-L2094 call evp interface which use aeesmbly optimisation。
sm4 remain unchanged is because there is no assembly optimisation in 1.1.1,while only assembly optimisation for ARMv8.2 in 3.0


chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.2.4

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.2.3 -> v1.2.4

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper
v1.2.4
Compare Source
Bug Fixes

deps: update module github.com/ibm/platform-services-go-sdk to v0.29.2 (#166) (b1e04f1)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Pubsub does not auto-reconnect with get_message()

Counterpart of https://github.com/andymccurdy/redis-py/issues/1572
Run the following script:
import itertools
import traceback
import asyncio

import aioredis

async def consumer(pubsub):
    await pubsub.subscribe('test')
    while True:
        try:
            message = await pubsub.get_message(
                ignore_subscribe_messages=True,
                timeout=1.0,
            )
            if message:
                print(f'Receive: {message}')
        except asyncio.CancelledError:
            raise
        except Exception:
            traceback.print_exc()
            await asyncio.sleep(1.0)

async def producer(redis):
    for i in itertools.count():
        try:
            print(f'Publish {i}')
            await redis.publish('test', str(i))
        except Exception:
            traceback.print_exc()
        await asyncio.sleep(1.0)

loop = asyncio.get_event_loop()
redis = aioredis.from_url('redis://', decode_responses=True)
loop.create_task(consumer(redis.pubsub()))
loop.run_until_complete(producer(redis))

While running, stop the Redis server and then start it again.
Expected behavior:  publish() and get_message() will fail while server is stopped, then succeed again after server restarts.
Observed behavior:  publish() resumes working, but get_message() continues to fail with the following traceback:
Traceback (most recent call last):
  File "/Users/luhn/Code/aioredis-py/test.py", line 12, in consumer
    message = await pubsub.get_message(
  File "/Users/luhn/Code/aioredis-py/aioredis/client.py", line 4154, in get_message
    response = await self.parse_response(block=False, timeout=timeout)
  File "/Users/luhn/Code/aioredis-py/aioredis/client.py", line 4034, in parse_response
    if not block and not await conn.can_read(timeout=timeout):
  File "/Users/luhn/Code/aioredis-py/aioredis/connection.py", line 850, in can_read
    return await self._parser.can_read(timeout)
  File "/Users/luhn/Code/aioredis-py/aioredis/connection.py", line 453, in can_read
    return await self.read_from_socket(timeout=timeout, raise_on_timeout=False)
  File "/Users/luhn/Code/aioredis-py/aioredis/connection.py", line 464, in read_from_socket
    raise ConnectionError(SERVER_CLOSED_CONNECTION_ERROR) from None
aioredis.exceptions.ConnectionError: Connection closed by server.

This is great code, but I believe we had a discussion before about how this was not the job of redis-py or aioredis. In my personal belief, I agree with this since people may want to be able to have a custom implementation for server failing.

Currently when a connection breaks, get_message() behaves differently than Redis.publish(), PubSub.subscribe(), or whatever your favorite command might be.  That's why I'm reporting a bug.  It should work exactly the same as everything else and discard the bad connection.
There's even a whole connect callback that will resubscribe to all subscribe topics upon reconnection, so obviously the implementation is meant to reconnect.

I don't see where publish has a reconnection option. subscribe needs reconnection since it's long living, whereas publish (which I didn't see have a reconnect option) and get_message are single execution commands.

Maybe "reconnect" is the wrong word.  All get_message needs to do is conn.disconnect() when a ConnectionError occurs.  Connection will handle the rest.
I'm not sure what publish() does behind the scenes, but the effect is the same—The next call to publish() will use a new connection.

FWIW, the equivalent issue+PR I opened with redis-py has been merged.  https://github.com/andymccurdy/redis-py/issues/1572

@luhn apologies, I never had a chance to respond, especially after I made sense of "Maybe "reconnect" is the wrong word". Thanks for also linking to redis-py. I'll probably be skipping your PR since I'll be making a huge PR port from redis-py tomorrow.
Thanks for creating the issue though!


Render global styles with useEffect hook

Fixes #3076
Rendering of styles is a side-effect and should not be performed before mounting.
React.StrictMode helps to enforce this rule by running various functions (lifecycle methods or the function itself in case of function components) twice to make sure that they are idempotent. GlobalStyleComponent was not idempotent, calling Sheet#allocateGSInstance on render, which led to generating a different id on the second render and absence of corresponding unmount callback for the first one.

I need help with fixing the failed tests. They pass on my local machine though.

I tried doing this originally and we ultimately moved away from it because of issues. I don't remember what they were though.

I believe we had an issue with SSR, and we also need to avoid issues with concurrent mode.
One thing that needs to happen is that during SSR the insertion must be synchronous. Luckily we won't have to handle unmounts in that case.
In the browser timing is important. We don't want to let a React render without stylings in place, so we must use useLayoutEffect if we want an effect to insert styles with an element.
Now comes the tricky part: Concurrent Mode and Strict Mode. I'll skip over the details but the important thing is that an effect may never run, which is fine, but is becoming a problem if we're doing non-symmetrical effects, e.g. synchronous insertion like we're doing now but removal in an effect's teardown.
So to solve this we need to insert synchronously for SSR and otherwise use useLayoutEffect to solve this comprehensively

@kitten so that's essentially what I tried to do. I agree that useLayoutEffect is more suitable than useEffect that I used. I might try again, using a library to detect the environment this time. Something like exenv. It will also facilitate testing.
Also, what do you mean by issues with concurrent mode? What should I be aware of?

I rewrote the code - it uses useLayoutEffect now. Moreover, it turned out that the project already had means of detecting the environment, so I didn't need any libraries.

@probablyup Do we want to pick this back up and get this ready or just defer it for a rewrite? I have some more nits, since this has some other problems, but depends on whether it's worth getting this ready

Obsolete / Resolved


Update display-control-verification.md

Removed Private Preview tag.

@kelxia : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


ISSUE: xteve.xml missing original xml details

Please first read the documentation. Problems affecting the client, e.g. Plex or Emby should be reported there in the forum.
Describe the bug
keys from the original xml are not included in the xteve.xml
For example, I have this in my original xml in the programs.
		<rating system="TV Parental Guidelines">
			<value>TV-14</value>
			<icon src="https://upload.wikimedia.org/wikipedia/commons/thumb/c/c3/TV-14_icon.svg/240px-TV-14_icon.svg.png" />
		</rating>

Server (please complete the following information):

OS [e.g. Linux - Ubuntu]: Win 10 Pro
Arch [e.g. Intel 64 Bit]: 64 bit
xTeVe Version and Build [to be found in the xTeVe log]: 2.1.2

To Reproduce
Steps to reproduce the behavior:

Add xml epg with rating key and map channels to it.
Wait for xteve to produce merged xml.

Expected behavior
All original details of programs should be included in xteve.xml.
Screenshots
1-Original (rating not added)

1-Xteve version

2-Original (length not added... possibly redundant with start and stop times, but thought I'd point it out)

2-Xteve

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
XMLTV standard is here (https://github.com/XMLTV/xmltv/blob/master/xmltv.dtd)
Also missing subtitles key (don't think there's anyway to access subtitles when playing through xteve though)... Could be others missing as well, this is just what I noticed.

Is already fixed in the beta
https://github.com/xteve-project/xTeVe#xteve-beta-branch


Is date time handled with a 32bit code ?

Go field is defined as time.time that is 64bit, so it should manage the datetime properly.
Internal clickhouse test show that Clickhouse should store it as 0000-00-00 00:00:00.
I just want to get a clarification of the exact behavior of this librairy in that case, as I can workaround it.
==> Can you confirm that the transformation to  2036-02-07 06:28:16 come from here ?
==> What is the max-min datetime that can be managed, and what is the behavior when out of range ?
Thanks

Hi, yes it's a 32bit limitation. ClickHouse can store dates between 1970 and 2105 years.
That transformation is a bug, the driver must checks dates.


update tests for windows

review test for os specific assumptions.

working in branch 29.dockter.1


Add missing rel="stylesheet" to link examples

If you try and copy from the example verbatim it will not work because of the missing rel="stylesheet" - added it :)

Cool @OpherV thanks!


Where is commaDelimited in styles?

Hi,
I've found in Parameters Examples this: "style": "commaDelimited"
Where is this style defined?

I think this is meant to be simple (which is a comma-separated style), and is a mistake in that example.

Yeah, we went back and forward on the name and that update was missed.

Ok so it works just like old "csv" in swagger 2?

It is intended to work like "simple" in RFC6570 https://tools.ietf.org/html/rfc6570#section-3.2.2  which should be effectively equivalent to csv in OpenAPI V2.

Thank you!


Update DI system with DSL for configuring bindings

DI.FactoryBuilder and related builder classes for configuring a ConfigurableInstanceFactory.
Repeatable @TestBinding test annotation for specifying simple bindings in tests.
@LegacyLoggerContextSource test annotation for specifying v1-style configuration files.
Test extension updates to improve compatibility of different annotations.
Various test updates to make use of said test extension updates.
Some nullability updates that got pulled in from my changes in spi-updates.

The "late" DI changes are being made now based because I wasn't trying to indefinitely delay pre-3.0.0 releases. In the lead up to 2.0.0, we accepted API changes up until 2.0.0 was cut (2.0 technically).


Add support for blocking queries, and made KV store functionality use Array[Byte] instead of String

Lots of breaking changes to the APIs here, sorry. No good way around it.
Give me your worst on the review. I'm open to whatever changes.
Also, it doesn't seem that the Docker integration tests work on Mac OS X so I had to do some hacky stuff to get the tests to run against my local Consul instance, but I'm pretty sure the integration tests work correctly and are effective.
P.S. this fixes #8

@timperrett, @adelbertc: Care to weigh in from a Nelson perspective?
@timperett: Do you have an automated release for this, or do we need to cut it manually?

Should we bring in scodec-bits for ByteVector instead of using Array[Byte] ? Relatively small footprint and stable as far as I can tell.

I have no strong preference on the ByteVector question, personally. I'm not really concerned about the mutability in this use case, but it looks like it'd be fairly simple to call ByteVector.view on the Array[Byte] or something like that. I'm also not using the KV store for anything, so I've no skin in the game.

Yeah I think I'm OK keeping it Array[Byte], at least for now. Good by me 👍


Use Aliases from service Network Attachment Config in Task Network Attachment

With this change, the alias config in network attachment from Service Spec is copied to task's Network attachment. Hence the executor can make use of it to provide proper aliasing support.
Signed-off-by: Madhu Venugopal<EMAIL_ADDRESS>

ping @aluzzardi @mrjana

@aluzzardi this PR doesn't cover the indexing work that you are concentrating on.

[Current coverage][cc-pull] is 54.03%

Merging [#974][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.05%

@@             master       #974   diff @@
==========================================
  Files            75         75
  Lines         11414      11412     -2
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6174       6167     -7
- Misses         4368       4371     +3
- Partials        872        874     +2

[][cc-pull]

Powered by Codecov. Last updated by [d93da96...3ddd9fa][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/swarmkit/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/docker/swarmkit/compare/d93da96c85f888cd4b770918a3ab5bc384ffc427...3ddd9fa1649ffc7eb070dddc37eec693f42e9464
[cc-pull]: https://codecov.io/gh/docker/swarmkit/pull/974?src=pr

Are these aliases for the individual task instances or the service itself?

these are for the service for each network attachment. That will get translated into the DNS resolution alias for each container that powers the service / task.

LGTM

/cc @stevvooe

LGTM