[cluster-test] Additional terraform setup for cluster test instance

Previously to properly setup cluster test instance some manual steps were needed after terraform apply, for example copying /libra_rsa key, copying ct binary and setting up some permissions
With this change cluster test runner instance is ready to go after terraform apply is done
Also it changes instance type family c5d->c5 and increases size of root block device for cluster test runner

@bors-libra r+

:pushpin: Commit 4cfdb88 has been approved by ankushagarwal

:hourglass: Testing commit 4cfdb884a4e04380d4eaca7e9829d7295cfaae89 with merge 73e688b5139427b0d729d7825f3c1667c66e5329...

This is awesome, thanks!

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r=ankushagarwal

:pushpin: Commit 1e506ea has been approved by ankushagarwal

:hourglass: Testing commit 1e506ea04c44ec14bacf6d678aaf7f7997945d5e with merge b1e3785898df4f175071a0c0fed7ea66d98e3d02...

:broken_heart: Test failed - checks-circle_commit_workflow

@bors-libra r=ankushagarwal

:pushpin: Commit 4cc23b7 has been approved by ankushagarwal

:hourglass: Testing commit 4cc23b70263c9deb3b7ae04644fe48014b6aa0c3 with merge c6a8746e8730c60a7bf75fc5a128a0d938f68d14...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: ankushagarwal
Pushing c6a8746e8730c60a7bf75fc5a128a0d938f68d14 to master...

:eyes: Test was successful, but fast-forwarding failed: 422 Update is not a fast forward

@bors-libra retry

:hourglass: Testing commit 4cc23b70263c9deb3b7ae04644fe48014b6aa0c3 with merge 4c0fce92d0056d41e5dcba3db867f19cb8edf067...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: ankushagarwal
Pushing 4c0fce92d0056d41e5dcba3db867f19cb8edf067 to master...


AxiosError: Request failed with status code 429

const userID = await threadsAPI.getUserIDfromUsername(username);

doesn't work.

I keep getting this error as well on my linux server, and not on my Windows laptop.

Update: I downgraded to v1.3.1 and my problem resolved. Any long-term solutions would be great to hear.


Consider symlinks as potential provides for so:

Some packages provide symlinks in /usr/lib/ that point to the library installed in another path.
Examples:
lua5.3 usr/lib/liblua-5.3.so.0 -> lua5.3/liblua-5.3.so.0
lua5.4 usr/lib/liblua-5.4.so.0 -> lua5.4/liblua-5.4.so.0
llvm17 usr/lib/libRemarks.so.16 -> ../lib/llvm17/lib/libRemarks.so.17

The total number of these cases in wolfi is only 12 links across 7 origins:
llvm-18-18.1.8-r3
llvm-19-19.1.4-r0
llvm15-15.0.7-r7
llvm16-16.0.6-r3
llvm17-17.0.6-r2
lua5.3-5.3.6-r5
lua5.4-5.4.7-r1

The result was that those packages don't get listed as providing the library that the do provide.
The target of the symlink above previously would get considered itself, but the fact that the target was not in isInDir(libDirs) meant it would get marked as vendored.
It meant that packages that depend on liblua-5.4.so.0 can't really resolve their dependency.

not all the fails seem related to may change. https://github.com/chainguard-dev/melange/pull/1663 is a test rebuild of main.

Fixed the test failures in #1664 , rebasing should see some green.

OK. Gave this a pretty good test, here is what I found.
the wonderfully named 'go-now' program is:
#!/bin/sh
if [ -z "$PROCESS" ]; then
    jobs=32
    outd=$1
    shift
    mkdir -p "$outd"
    ${MELANGE:-melange} version > "$outd/melange-version.txt"

    PROCESS=true exec parallel \
       "--jobs=$jobs" --line-buffer -- \
       "$0" "$outd" ::: "$@"
fi

outd="$1"
pkg="$2"

pkg=${pkg%.yaml}
out=$outd/$pkg.out
err=$outd/$pkg.err
rcf=$outd/$pkg.rc
tmpout="$outd/.$pkg.out"
tmperr="$outd/.$pkg.err"
tmprcf="$outd/.$pkg.rc"

cleanup() {
    rm -f "$tmpout" "$tmperr" "$tmprcf"
}
fail() { echo "$@" 1>&2; exit 99; }

trap cleanup EXIT
if [ -f "$out" ] && [ -f "$err" ] && [ -f "$rcf" ]; then
    read rc < $rcf
    echo "$pkg - $rc [already done]"
    exit 0
fi

melange=${MELANGE:-melange}
$melange scan --diff "$pkg.yaml" >"$tmpout" 2>"$tmperr"
rc=$?
echo "$rc" > "$tmprcf" || fail "failed writing to tmprcf"
echo "$pkg - $rc"

mv "$tmpout" "$out" &&
    mv "$tmperr" "$err" &&
    mv "$tmprcf" "$rcf" ||
    fail "odd: failed renames - $pkg"
exit $rc

I used it to run melange scan --diff against *.yaml in wolfi at the commit listed.
$ git log HEAD^.. --oneline --no-decorate
a3e5a2aa8 php-8.3-pecl-http - enable updates and update to 4.2.6 (#34749)

$ ls -l packages
lrwxrwxrwx    1 user     docker          50 Nov 21 12:18 packages -> /gcsfuse/wolfi-production-registry-destination/os/

$ for m in main mine; do d=out.$m; time env MELANGE=$HOME/src/melange/melange.$m ./go-now $d *.yaml; done

Then collect the differences in output, using
diff -ru '--exclude=*.err' out.main/llvm15.out out.mine/llvm15.out
--- out.main/llvm15.out	2024-11-21 13:55:58.107295357 -0500
+++ out.mine/llvm15.out	2024-11-21 14:00:30.680188771 -0500
@@ -0,0 +1,10 @@
+diff llvm15-15.0.7-r7.apk llvm15.yaml
+--- llvm15-15.0.7-r7.apk
++++ llvm15.yaml
+@@ -14,4 +14,6 @@
+ depend = so:libm.so.6
+ depend = so:libstdc++.so.6
+ depend = so:libz.so.1
++provides = so:libLTO.so.15=15
++provides = so:libRemarks.so.15=15
+ datahash = 23a2e286edcd4ef174d5890756c775faa548ee8d4407be91d3513f9a78e9c85c
diff -ru '--exclude=*.err' out.main/llvm15.rc out.mine/llvm15.rc
--- out.main/llvm15.rc	2024-11-21 13:56:05.995350151 -0500
+++ out.mine/llvm15.rc	2024-11-21 14:00:30.684188799 -0500
@@ -1 +1 @@
-0
+1
diff -ru '--exclude=*.err' out.main/llvm16.out out.mine/llvm16.out
--- out.main/llvm16.out	2024-11-21 13:55:58.159295718 -0500
+++ out.mine/llvm16.out	2024-11-21 14:00:30.181185305 -0500
@@ -0,0 +1,10 @@
+diff llvm16-16.0.6-r3.apk llvm16.yaml
+--- llvm16-16.0.6-r3.apk
++++ llvm16.yaml
+@@ -14,4 +14,6 @@
+ depend = so:libm.so.6
+ depend = so:libstdc++.so.6
+ depend = so:libz.so.1
++provides = so:libLTO.so.16=16
++provides = so:libRemarks.so.16=16
+ datahash = e64275b4d81210efd3d49e90bd68515060eedc84babd8881a0e976a8cbf4b52a
diff -ru '--exclude=*.err' out.main/llvm16.rc out.mine/llvm16.rc
--- out.main/llvm16.rc	2024-11-21 13:56:05.772348602 -0500
+++ out.mine/llvm16.rc	2024-11-21 14:00:30.187185346 -0500
@@ -1 +1 @@
-0
+1
diff -ru '--exclude=*.err' out.main/llvm17.out out.mine/llvm17.out
--- out.main/llvm17.out	2024-11-21 13:55:58.183295885 -0500
+++ out.mine/llvm17.out	2024-11-21 14:00:30.898190285 -0500
@@ -0,0 +1,10 @@
+diff llvm17-17.0.6-r2.apk llvm17.yaml
+--- llvm17-17.0.6-r2.apk
++++ llvm17.yaml
+@@ -14,4 +14,6 @@
+ depend = so:libm.so.6
+ depend = so:libstdc++.so.6
+ depend = so:libz.so.1
++provides = so:libLTO.so.17=17
++provides = so:libRemarks.so.17=17
+ datahash = 8e204146f4942b643f784bc537ef09a660440025a681cd955dade63296094da8
diff -ru '--exclude=*.err' out.main/llvm17.rc out.mine/llvm17.rc
--- out.main/llvm17.rc	2024-11-21 13:56:06.480353520 -0500
+++ out.mine/llvm17.rc	2024-11-21 14:00:30.902190313 -0500
@@ -1 +1 @@
-0
+1
diff -ru '--exclude=*.err' out.main/lua5.3.out out.mine/lua5.3.out
--- out.main/lua5.3.out	2024-11-21 13:56:02.648326901 -0500
+++ out.mine/lua5.3.out	2024-11-21 14:00:27.565167133 -0500
@@ -7,3 +7,12 @@
  license = MIT
 +depend = man-db
  datahash = a6012234cbc881270340b93e19549a651b7af066b197c69783a9209dd6f96f54
+diff lua5.3-5.3.6-r5.apk lua5.3.yaml
+--- lua5.3-5.3.6-r5.apk
++++ lua5.3.yaml
+@@ -14,4 +14,5 @@
+ depend = so:libm.so.6
+ provides = cmd:lua5.3=5.3.6-r5
+ provides = cmd:luac5.3=5.3.6-r5
++provides = so:liblua-5.3.so.0=0
+ datahash = 619f77b14ec3d7b42df5e1b6c3992b513ee6fa94002bcf4990e4904e29779ad4
diff -ru '--exclude=*.err' out.main/lua5.4.out out.mine/lua5.4.out
--- out.main/lua5.4.out	2024-11-21 13:56:02.669327047 -0500
+++ out.mine/lua5.4.out	2024-11-21 14:00:27.453166355 -0500
@@ -7,3 +7,12 @@
  license = MIT
 +depend = man-db
  datahash = 015a53ac8eeef09a15e34c9445cc641b9f96c2cae3b5a327da46aa9638af62cd
+diff lua5.4-5.4.7-r1.apk lua5.4.yaml
+--- lua5.4-5.4.7-r1.apk
++++ lua5.4.yaml
+@@ -14,4 +14,5 @@
+ depend = so:libreadline.so.8
+ provides = cmd:lua5.4=5.4.7-r1
+ provides = cmd:luac5.4=5.4.7-r1
++provides = so:liblua-5.4.so.0=0
+ datahash = 44212eda3b6802569d8ee669f3bf16b9bdfca45256dcec54b7733d7f8113c8a3
diff -ru '--exclude=*.err' out.main/melange-version.txt out.mine/melange-version.txt
--- out.main/melange-version.txt	2024-11-21 13:54:46.686799236 -0500
+++ out.mine/melange-version.txt	2024-11-21 13:59:09.468624638 -0500
@@ -5,10 +5,10 @@
  |_|  |_| |_____| |_____| /_/   \_\ |_| \_|  \____| |_____|
 melange

-GitVersion:    v0.15.12-2-gc0f7f40
-GitCommit:     c0f7f40012d053dde760758b15d80c3220cfcdd0
+GitVersion:    v0.15.12-3-g4c43b40
+GitCommit:     4c43b40b6bd327921e0d9fa3e0be1d3b5b4b3f56
 GitTreeState:  clean
-BuildDate:     '2024-11-21T17:24:19Z'
+BuildDate:     '2024-11-21T17:27:54Z'
 GoVersion:     go1.23.3
 Compiler:      gc
 Platform:      linux/amd64

The diff above is almost exactly what i was expecting.
I had expected 7 origins to have changed.  Instead there were 5.  The two that didn't change as I expected were llvm-18-18.1.8-r3
llvm-19-19.1.4-r0.  Looking further, those two did have symlinks but the source was not in /usr/lib/ so they were not considered.
So... this is exactly the changes I expected.


mixxx: 2.2.1 -> 2.2.2

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @haslersn

I didn't test it, yet, but I can approve that the done changes suffice.

@GrahamcOfBorg build mixxx

builds locally on x86_64-linux and seems to run.

Should we backport this to stable?


Prepare the database for Good Job v4

Context
We need to perform some database migrations to prepare for the upgrade from Good Job v3 to v4. This will allow us to re-apply the upgrade in #828, which was reverted by #838.

[!NOTE]
This PR does not upgrade Good Job to v4. It prepares the database for v4, but these changes are still compatible with v3.99.1 which is currently in use.

Changes proposed in this pull request
I've followed the instructions in the upgrade guide. The database migrations were automatically generated by the gem.
I've also updated the DfE Analytics blocklist to exclude the newly added fields.
Guidance to review
Run the migrations in this pull request, then open a Rails console and run:
GoodJob.v4_ready?

It should return true.
Link to Trello card
https://trello.com/c/vneRTcpO/554-review-and-merge-dependabot-prs

Note:
GoodJob.v4_ready?

is a bit sneaky. If there are no enqueued jobs, it will always return true.

If there are no enqueued jobs, it will always return true.

🤦🏻♂


reach: 1.5.1-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository reach to 1.5.1-1:

upstream repository: https://github.com/ros-industrial/reach.git
release repository: https://github.com/ros2-gbp/reach-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: None

Holding for Humble sync


publish<EMAIL_ADDRESS>

Requested by: @adinauer
Merge target: 6.7.x
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave the #retract comment under this issue to retract the release (original issuer only).
Targets

[x] symbol-collector
[x] maven
[x] github
[x] registry

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

My bad, specified the wrong branch (6.7.x instead of feat/6.7.x) as merge target. Merged manually. Release seems to have gone through.


Add Windows & Linux PCAN-Basic driver

Right now, the project only has a Socket CAN hardware layer plugin. I actually do a lot of my development on my Windows machine though, and would really like the project to have a turnkey Windows integration. So, I've ordered a PCAN probe as a little Christmas present for myself and plan to officially add support for their PCAN-Basic driver for both Linux and Windows. This will provide at least one alternative to Socket CAN out of the box.
The PCAN-Basic driver is an All Rights Reserved license, but they state:
PEAK-System Technik GmbH grants the right to the customer to use the files in
this software package as long as this is done in connection with original
hardware by PEAK-System or OEM hardware coming from PEAK-System.

Therefore I believe it is probably OK to include them in this project as long as we include their license terms and appropriately make users aware of this restriction.
This work should be pretty easy, and basic instructions for how to get started on it are in the README file in hardware_integration:
https://github.com/ad3154/ISO11783-CAN-Stack/tree/main/hardware_integration

In theory, this could also support Mac OS, I think, but I do not have a Mac to test it with.


CI: switch from LXD to Incus

LXD is now banned from https://images.linuxcontainers.org/

TODO: consider using Lima (w/ user-v2 network) instead of LXD/Incus


Missing site.

This is fantastic. It is so annoying the gov site does not have a map version of the data, so great work.
But there is at least 1 missing site.
goto:
https://www.coronavirus.vic.gov.au/exposure-sites
search for suburb: glen iris
that returns:

Glen Iris
Coles Tooronga VillageTooronga RoadGlen Iris VIC 3146
23/05/2021 4:00pm - 4:30pm
Case attended venue
29/05/2021
Tier 2 - Get tested urgently and isolate until you have a negative result

The data says it was added to the source on the 29th.
Goto the map.
Map says data from the 30th, but the location isnt plotted.

It isnt in the data.json in the repo (dated 35 mins ago as of 4:24pm Melb time)
If i pull the data manually with:
wget 'https://www.coronavirus.vic.gov.au/sdp-ckan?resource_id=afb52611-6061-4a2b-9110-74c920bede77&limit=10000'
then it is present.
So unless it was added in the last 35 mins (which the gov site says it was added on the 29th) then it might be worth investigating.

Fixed, looks like it may have returned previously from the API as a different piece of data, and so it was using the cache instead of the fresh API data. I've changed it to overlay the fresh API data on top of the cache.
Thanks for finding @korg !


Not working as expected when NoSleep is defined/initialised and the page was hidden before enabling

Documentation Is:

[ ] Missing
[ ] Needed
[ ] Confusing
[x] Not Sure?

Please Explain in Detail…
When you use NoSleep like demonstrated in the Live Demo, where you initialise the NoSleep object via new NoSleep() during page load, and only .enable() it when tapping the button, it won’t activate as expected, if the page was hidden after initial load and before enabling NoSleep.
Here’s how you should be able to reproduce this:

Open the Live Demo in your iOS device’s browser.
Hide the page (switch to another tab, or push the home button, or let the device go to sleep etc.).
Go back to the page in your browser.
Hit the button to enable NoSleep.
After a while, the device will go to sleep.

I experience this on my iOS 12.1 devices. Haven’t tested on Android.
Your Proposal for Changes
Not sure. Maybe this is even intended or preferred behaviour for the demo. But for me it was a bit of a head-scratcher debugging this.
So it might be relevant to amend the example code to avoid this behaviour. Here’s a quick example of what works (this is the JS from the example):
var noSleep = null; // DON’T DEFINE IT HERE
var wakeLockEnabled = false;
var toggleEl = document.querySelector("#toggle");
toggleEl.addEventListener('click', function() {
  if (!wakeLockEnabled) {
    noSleep = new NoSleep(); // DEFINE IT HERE
    noSleep.enable(); // keep the screen on!
    wakeLockEnabled = true;
    toggleEl.value = "Wake Lock is enabled";
    document.body.style.backgroundColor = "green";
  } else {
    noSleep.disable(); // let the screen turn off.
    noSleep = null // DELETING REFERENCE AGAIN
    wakeLockEnabled = false;
    toggleEl.value = "Wake Lock is disabled";
    document.body.style.backgroundColor = "";
  }
}, false);

Alternatively, it might be more suitable to amend the constructor and the enable() method, so that you could use the example code as is (and avoid creating and destroying a NoSleep object on each run) and still avoiding this “issue”.

I just ran into what I assume is the same issue. I'm glad you found the solution as I'm sure this would have been trial and error.
I have a visibilitychange listener and a 5 minute timeout to disable NoSleep so the device doesn't get stuck on forever. However on iOS 12 it seems like once NoSleep has released the wakelock it can't get it back (not a problem on Android).
I found that reinitialising NoSleep on my visibilitychange listener fixed the issue:
document.addEventListener('visibilitychange', function() {
    if (document.hidden) {
        clearTimeout(noSleepTimer);
        noSleep.disable();
    } else {
        noSleep = new NoSleep(); // For iOS
        // Now do your normal enable code or rely on your click handlers etc
    }
});


create faq pages

drawing inspiration from the Payy Network, they currently provide dedicated FAQs for both the wallet and the network. The wallet settings include a direct link to the FAQ, a telegram link to ask questions, and importantly, a feature to share diagnostics with the development team.
we plan to create dedicated FAQs for both the prax wallet and the network. These FAQs will be written in simple language for easy understanding and added to our Nextra guide.

This should exist in https://github.com/penumbra-zone/guide no?

This should exist in https://github.com/penumbra-zone/guide no?

good point, will move 👍


⚠ Bofrost.de has degraded performance

In 324847d, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1473 ms

Resolved: Bofrost.de performance has improved in 6e14f68 after 305 days, 10 hours, 21 minutes.


ESOCKETTIMEDOUT in listen.js

I've checked #665 and there wasn't any solution to this error.
Basically, every few hours I get this error and the only way to make it work again is to restart the whole bot.
Stacktrace:
ERR! listen Error: ESOCKETTIMEDOUT
ERR! listen     at ClientRequest.<anonymous> (/usr/local/lib/node_modules/miscord/node_modules/request/request.js:812:19)
ERR! listen     at Object.onceWrapper (events.js:273:13)
ERR! listen     at ClientRequest.emit (events.js:182:13)
ERR! listen     at TLSSocket.emitTimeout (_http_client.js:706:34)
ERR! listen     at Object.onceWrapper (events.js:273:13)
ERR! listen     at TLSSocket.emit (events.js:182:13)
ERR! listen     at TLSSocket.Socket._onTimeout (net.js:444:8)
ERR! listen     at ontimeout (timers.js:427:11)
ERR! listen     at tryOnTimeout (timers.js:289:5)
ERR! listen     at listOnTimeout (timers.js:252:5)
ERR! listen     at Timer.processTimers (timers.js:212:10)

Yes, I do have a stable internet connection. It's hosted on DigitalOcean and I never had any issues with connection on their servers.

I'll try to add it, I have currently 12 bots running so I hope I'll get some results soon

Update: the env variable didn't help.
I'll try the maxSockets option.

Thanks for testing that.
o.O 12 bots? I'm assuming they're on different accounts? Otherwise I wouldn't be surprised if there was some sort of rate limiting happening.
Honestly I don't really know much about what's happening here and all I'm doing is looking at stackoverflow... https://stackoverflow.com/a/43857814  This one seems to try to set keepAlive: true somehow. Could be worth a shot if you can figure it out.
Unfortunately the only other guess I would have is to somehow catch it and optionally try to retry the call (or ignore).

12 bots, each on a different account and split in half to 2 separate servers. I'll try that approach, maybe this time it will work.

any update?
I receive this error too

I've had the same problem few days ago... over 30% of requests were failing
but the same script was working fine (with no changes) after 12 hours :/
I'm wondering is this is a facebook's issue ...

@ravkr Today it probably is a Facebook issue, I'm getting timeouts on servers that never had them...

I also have same issue, affter 5h active 1 account
now, how to resolved it??
thanks

How's this going? I am experiencing same thing as well

How's this going? I am experiencing same thing as well

But it still active, I try on function  api.listen(). It still run ok.

0|Bot    |  login Error: connect ECONNREFUSED <IP_ADDRESS>:443 0|Bot    | ERR! login     at Object._errnoException (util.js:1022:11) 0|Bot    | ERR! login     at _exceptionWithHostPort (util.js:1044:20) 0|Bot    | ERR! login     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14) 0|Bot    | ERR! login 0|Bot    |   { Error: connect ECONNREFUSED <IP_ADDRESS>:443 0|Bot    | ERR!  0|Bot    | login     at Object._errnoException (util.js:1022:11) 0|Bot    | ERR! 0|Bot    |  login 0|Bot    |      at _exceptionWithHostPort (util.js:1044:20) 0|Bot    | ERR! login     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14) 0|Bot    | ERR! 0|Bot    |  login   cause:  0|Bot    | ERR! login    { Error: connect ECONNREFUSED <IP_ADDRESS>:443 0|Bot    | ERR! login     at Object._errnoException (util.js:1022:11) 0|Bot    | ERR! login     at _exceptionWithHostPort (util.js:1044:20) 0|Bot    | ERR! login 0|Bot    |      at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14) 0|Bot    | ERR! 0|Bot    |  login      code: 'ECONNREFUSED', 0|Bot    | ERR!  0|Bot    | login      errno: 'ECONNREFUSED', 0|Bot    | ERR! login 0|Bot    |       syscall: 'connect', 0|Bot    | ERR! login 0|Bot    |       address: '<IP_ADDRESS>', 0|Bot    | ERR! login      port: 443 }, 0|Bot    | ERR! 0|Bot    |  login 0|Bot    |    isOperational: true, 0|Bot    | ERR! login   code: 'ECONNREFUSED', 0|Bot    | ERR! login   errno: 'ECONNREFUSED', 0|Bot    | ERR! login   syscall: 'connect', 0|Bot    | ERR! 0|Bot    |  login   address: '<IP_ADDRESS>', 0|Bot    | ERR! login   port: 443 }
Hi, I'm having this error today. Is this some kind of fb error?


The python example video isn't available, you can change the docs or upload the video

Bug report
Describe the bug
The Python example video isn't available, you can change the docs or upload the video
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to the python server read me
Click on the youtube video link: https://www.youtube.com/watch?v=Tgjwx-38Dic
See error

Screenshots

If applicable, add screenshots to help explain your problem.
Add any other context about the problem here.

Thanks for the report! Fixed in https://github.com/stripe-samples/accept-a-payment/pull/1946


Confusing error message when standard library header is not found

In the file src/master/liboslcomp/oslcomp.cpp:
If the test on line 323  fails:
if (OIIO::Filesystem::exists (path.string())) {
The variable path will not be updated to contain "/stdosl.h" in the end. This makes the error reported on line 339 in the same file confusing since the path it says it can't find doesn't say anything about stdosl.h but only mentioning a missing directory. It makes more sense to explicitly say it's the standard library missing and write the full path to the missing file.
Off topic:
It's the first time I post here, would you prefer to see a patch here or is this form ok?

I think this is long since fixed.


Attached movies getters

Looks like some useful getters are missed in С++ core. In charp core
they’re implemented and made public. Added them using csharp core as an
example

thanks


Fix missing timestamp for Sundays' presentation

polite ping @kenvandine

already in https://github.com/ubuntu/community-fosdem-2022-content/pull/2


Add wget instructions since Debian (and others) don't ship curl by default

Instructions that will work on systems w/o curl.

Hi @brendandburns, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (bburns). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


[FormRecognizer] BuildClassifierOperationCanPollFromNewObject failing in nightly runs

FormRecognizer nightly test runs are failing with:

Error message
Azure.RequestFailedException : Invalid request.
Status: 200 (OK)
ErrorCode: InvalidRequest
Additional Information:
AdditionInformation: InvalidRequest: Invalid request.
Details:
ContentSourceNotAccessible: Content is not accessible: Invalid data URL
Raw:
{
"code": "InvalidRequest",
"message": "Invalid request.",
"details": [
{
"code": "ContentSourceNotAccessible",
"message": "Content is not accessible: Invalid data URL"
}
]
}
Content:
Headers:
Transfer-Encoding: chunked
ms-azure-ai-errorcode: REDACTED
x-envoy-upstream-service-time: 19
apim-request-id: 52e70713-905d-4a68-b27c-40893958a9fc
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
x-content-type-options: nosniff
x-ms-region: REDACTED
Content-Type: application/json; charset=utf-8
Date: Fri, 07 Apr 2023 04:26:33 GMT
Data:
AdditionInformation: InvalidRequest: Invalid request.
Details:
ContentSourceNotAccessible: Content is not accessible: Invalid data URL
Raw:
{
"code": "InvalidRequest",
"message": "Invalid request.",
"details": [
{
"code": "ContentSourceNotAccessible",
"message": "Content is not accessible: Invalid data URL"
}
]
}
Stack trace
at Azure.Core.OperationInternal1.GetResponseFromState(OperationState1 state) in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalOfT.cs:line 290
at Azure.Core.OperationInternal1.<UpdateStatusAsync>d__20.MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalOfT.cs:line 278 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Threading.Tasks.ValueTask1.get_Result()
at Azure.Core.OperationInternalBase.<UpdateStatusAsync>d__13.MoveNext() in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalBase.cs:line 87
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Threading.Tasks.ValueTask1.get_Result()    at Azure.Core.OperationPoller.<WaitForCompletionAsync>d__11.MoveNext() in D:\a\_work\1\s\sdk\core\Azure.Core\src\Shared\OperationPoller.cs:line 79 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Threading.Tasks.ValueTask1.get_Result()
at Azure.Core.OperationInternalBase.<WaitForCompletionResponseAsync>d__19.MoveNext() in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalBase.cs:line 212
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Threading.Tasks.ValueTask1.get_Result()    at Azure.Core.OperationInternal1.<WaitForCompletionAsync>d__19.MoveNext() in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalOfT.cs:line 242
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Threading.Tasks.ValueTask1.get_Result()    at Azure.Core.OperationInternal1.<WaitForCompletionAsync>d__15.MoveNext() in D:\a_work\1\s\sdk\core\Azure.Core\src\Shared\OperationInternalOfT.cs:line 177
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Threading.Tasks.ValueTask1.get_Result()    at Azure.AI.FormRecognizer.DocumentAnalysis.BuildDocumentClassifierOperation.<WaitForCompletionAsync>d__16.MoveNext() in D:\a\_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\src\BuildDocumentClassifierOperation.cs:line 91 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Threading.Tasks.ValueTask1.get_Result()
at Azure.AI.FormRecognizer.DocumentAnalysis.Tests.OperationsLiveTests.<BuildClassifierOperationCanPollFromNewObject>d__6.MoveNext() in D:\a_work\1\s\sdk\formrecognizer\Azure.AI.FormRecognizer\tests\DocumentAnalysisModels\OperationsLiveTests.cs:line 147
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Azure.AI.FormRecognizer.DocumentAnalysis.Tests.OperationsLiveTests.<BuildClassifierOperationCanPol

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2685224&view=results

@jsquire for notification.

Will be fixed by https://github.com/Azure/azure-sdk-for-net/pull/35362.


Add additional information to breaking update JSON format

In order to get an overview if any particular dependency is over-represented, it would be beneficial to add the following to the JSON format:

[ ] Date the PR was created
[ ] Dependency changed
[ ] Previous version
[ ] New version

In addition to any changes to the Java code, we must also go back and update previously found updates with this information.

This issue has now been fixed trough 388bbf7 and bea6455


in frame and bridge updates

visibility function added in InFrame.js
implemented it in bridge exercise

Let's apply this consistently to all exercises and try to refactor it to be cleaner or more modular. I can hop on the branch and take a try at it

Why is the inFrame method only checking the topmost, bottommost, etc. landmarks. Wouldn't it be easier to just pass a list of landmarks which all need to be visible?


WebSocket is already in CLOSING or CLOSED state error in console

Stopping a sample that is playing, or attempting to play a different sample, results in a console error.

fixed


nixos/public-inbox: remove unused indexing code

This was never run, because public-inbox-init now always initializes Xapian.
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

@OfBorg build public-inbox


fix #75

Hi, thanks for sharing.
Can you explain why you need this feature?
I do not think this feature should be added. We want the same behavior as if you do not use native transitions.

I got it. Releasing a new version with this included. I found an easier way to do the same.

Only this test is necessary:
if ($state.current.name === state){

https://github.com/shprink/ionic-native-transitions/commit/36323f660530eeb0f9cf95bc266770f2a7ecca3e#diff-1c25f2af06a7bfd6c36abff0f88b9a2bR200


Initial tests for spacy and stanza / base modules

This also closes #15

@np179 could you also address the merge conflicts, in addition to the above comment?


Add BHUSA 2022 presentation by Le Wu

https://www.youtube.com/watch?v=dIVjQrqpKC0
https://i.blackhat.com/USA-22/Wednesday/US-22-Wu-Devils-Are-in-the-File.pdf

Fixed by https://github.com/xairy/linux-kernel-exploitation/commit/a93ac0b2430a565d59974ac364b3b97177247bf9, thanks!


how to use ORD datasets into the model?

ORD datasets have two parts: scene-graph and region-description,. How can you use it to complete a I2T or T2I task? Do you rewrite the region descriptions to a whole sentence as a text input?

Yes, we did some data augmentation based on the original data. You can find the details in Appendix A.3 https://arxiv.org/pdf/2206.07699

Thanks for your rapid reply! Whether the prompt template only consider the objects, but ignore the attributions and relations?

Yes, but you could explore it if you think it is beneficial.
Thanks!

Thank you very much,  your reply is crucial to me!


Why does the parser refuse to parse this statement?

I have these two lines of code:
let sql = "CREATE EXTERNAL TABLE t(c1 int) STORED AS CSV DELIMITER '|' LOCATION 'foo.csv'";
Parser::parse_sql(&dialect::GenericDialect {}, sql).unwrap();

and the second line is panicking like so:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ParserError("Expected fileformat, found: CSV")', src/sql.rs:24:57

I'm on the current version of the these packages:
datafusion = { version = "23.0.0", features = ["default", "avro"]}
datafusion-sql = { version = "23.0.0", features = ["default"]}

I grabbed this statement from the tests I see here:
https://github.com/apache/arrow-datafusion/blob/cda00b545e1b4492269f76f65545c82264f79b88/datafusion/sql/src/parser.rs#L589-L604
Would anyone know why this fails here?

I realised I needed to use parser::DFParser


Unable to retrieve child resources

Whenever opening Azure storage explorer getting the following error, even though my credentials are already saved in it.
Unable to retrieve child resources.
Details:
["Error:Unable to retrieve authentication token."]

@Karthik-Nagendiran at what point in the tree are you getting the error? Or in other words, after expanding what node are you seeing this error?

Closing due to lack of response. Please open a new issue if you are still having problems.


Performance of provisioning area in KIM

Description
We have to agree on performance KPIs and measuring for KIM.
Following KPIs have to be verified:

Duplicated by https://github.com/kyma-project/infrastructure-manager/issues/14


don't display the lockscreen if we are initializing a seed

This fixes the issue where users could see a lockscreen and attempt to unlock during seed initialization.

Would like to see unit tests accompanying these PRs. That's how we make sure we don't get regressions, on top of just verifying it works in the first place.

This PR included a unit test: https://github.com/NebulousLabs/Sia-UI/pull/587/commits/bb3d0073875ffd47c8c0645f6f0b0b34c5ee6381#diff-3f1974fdfc963ead85c7f3af84fc4129R23

Derp I am just blind. Thanks


EOS-21367 Changes as per RE PR #472

Signed-off-by: Vaibhav Paratwar<EMAIL_ADDRESS>EOS-21367 Changes as per RE PR #472

@knekrasov , @shailesh-vaidya, @vaibhavparatwar,
Just one concern, here we are assuming that the puppet-agent package will include the relevant version of facter, thus we are restricting the given puppet-agent version, what if puppet stops distributing facter as part of it? can we handle such a situation?

@shailesh-vaidya  @knekrasov - what is your view on @mssawant's concern? Community is blocked on this - pls check this GitHub issue - https://github.com/Seagate/cortx-hare/issues/1665

@vaibhavparatwar, @mssawant, @knekrasov   With regards to issue https://github.com/Seagate/cortx-hare/issues/1665, I tried out this PR and I get another error
error: Failed dependencies:
	puppet-agent >= 6.13.0 is needed by cortx-hare-2.0.0-1_git47b95c8.el7.x86_64

which is expected, right?
I tried to run make and make install on hare directory, but the puppet is still not installed automatically.
So, which script will install this puppet-agent at which step (w.r.t the hare README)?
Perhaps the README should be edited as well, to include puppet installation. My main task is to make sure that the README is bulletproof :)
Thanks!

@vaibhavparatwar, kindly address @daniarherikurniawan's comment.

@vaibhavparatwar, @mssawant, @knekrasov With regards to issue #1665, I tried out this PR and I get another error
error: Failed dependencies:
	puppet-agent >= 6.13.0 is needed by cortx-hare-2.0.0-1_git47b95c8.el7.x86_64

I tried to run make and make install on hare directory, but the puppet is still not installed automatically.
So, which script will install this puppet-agent at which step (w.r.t the hare README)?
Perhaps the README should be edited as well, to include puppet installation. My main task is to make sure that the README is bulletproof :)
Thanks!

Hi @daniarherikurniawan The script is part of Cortx-RE - check this. - https://github.com/Seagate/cortx-re/pull/472/files#diff-e2aa453f6758b0dcb4f493b2e1c6ba48a30ada3cc2023093ad34f24a9a7a4fff  actually it runs as part of full stack deployment.
We may need to add this in hare README. Will discuss with @knekrasov and @mssawant for this.

Thanks @vaibhavparatwar !
I believe the cortx-re is a private repo that we (community) don't have access to. Looking forward to seeing the update at the public cortx repo so that we can safely satisfy all dependencies!

@daniarherikurniawan let me get some idea on this from @knekrasov , @mssawant and @shailesh-vaidya - Like this dependency are there any other dependencies as well, which are not part of README? so we address them all together in hare README?

@knekrasov and @mssawant and @vaibhavparatwar , what is the status of this one please?

raised PR #1743 for this. Closing this here.


Fix SSR with ziggy

Note this does not fix SSR in the javascript version, only typescript. I'm getting a strange error in the js version and haven't figured it out yet.

Thanks Sam. I will by pass merge this. Oh gosh, I think I should disable the signing commit. This makes anyone feel interrupted.

Oh shoot whoops I deleted my key to set up a new one which caused the signed commits to become unverified. My bad! Should be good going forward


Provision failure: Resource group name

Describe the bug
I get this error after I have entered all details for creating a new publishing profile. While entering the 'Resource Group name' I do not get any error validation. Therefore, I do not know that in the future my provisioning will fail
Version
R1.3.1
Browser

[ ] Electron distribution

OS

[ ] macOS

To Reproduce
Steps to reproduce the behavior:

Go to project settings, click on add new publishing profile
Enter this in resource group name input filed - " Contoso app"
Fill the other inputs, hit done
You will get the error

This is already fixed in the latest main branch, just close it.


No style are applied with webpack with the target: node activated

Version
2.2.6
Reproduction link
https://github.com/raultrysw/issue-with-vuejs-and-webpack
Steps to reproduce
In the webpack.config.js file, quit the target: node option and next make electron . in the root folder, you will see that the style in component.vue appears correctly, but if that line is not present, not.
What is expected?
The style appears whether is present or not target:node
What is actually happening?
If target: node is present, the style not appears

target: node is used by vue-loader to detect server side rendering mode. This is expected behavior. Use target: electron if you are building for electron.

Thanks to all you!
Vuejs is a great framework for development apps! =)


MSSQL Streaming does not handle backpressure

First of all thank you for this great library and support for mssql.
I'm working with rather huge datasets (3.9M rows joined with other tables) which cannot be paged without risking timeouts. Unfortunately, I cannot influence the schema or indices so I have to work with what I got and that is streaming the query results. This is were I noticed that my app crashes with OOM depending on the number of selected columns (and rows of course).
Short digression about how streaming mssql works right now:
There is an array that is filled with rows as they come in from the tedious request.
A loop (with setTimeout 0) checks if the array is larger than the requested batch size (let's call it n) and resolves a deferred with the same number n of rows.
Now this is the problem as only the first n rows are passed to the application. If the application is fast in handling the batch this creates no problem. But otherwise the row buffer fills up and is not cleared fast enough, thus consuming all the memory.
I solved this problem locally by using a (nodejs) readable stream and pausing the tedious request if the stream cannot buffer more rows. This works really great but I could only test this for reading data as I have only read-only access to the database.
Are you interested in a PR? I'm not sure about other runtimes that kysely supports.

Hey 👋
Thank you!
Is using a stream absolutely necessary? Shouldn't using request.pause() and request.resume() suffice?

Yes, I use Request.pause() and Request.resume(). I'm not familiar how to detect back pressure other than via stream, so that's what I went with.
Thinking about it, it might be enough to check the size of the rows array after splicing it and pausing the request if it is not empty.

Let's try the array length approach. PRs welcome.

And it's solved. Use #1041's changes for now.


I.click() method stuck when element is not exist on the page and method should fails for Playwright >1.17.0

I.click() method stuck when element is not on the page and method should fails.
the issue in Playwright.js file:
async function proceedClick(locator, context = null, options = {})
it stuck on:
await element.click(options);
It seems that Playwright team changed ElementHandle class https://playwright.dev/docs/api/class-elementhandle
Details

CodeceptJS version: "3.2.2",
Playwright version: "1.17.1"

Should be resolved in 3.3


cpu-affinity-range not applied when changing charm config

there's a missing flag to be checked when config-changed.

(by afreiberger)
There is a functional test that ensures this setting is changed.
https://git.launchpad.net/~gabor.meszaros/charm-sysconfig/tree/src/tests/functional/test_deploy.py#n214
Can you please help by explaining the exact scenario and versions of the charm you are running and what failed?
Is the issue that the file isn't updated, or is it that systemd needs to be daemon_reloaded, or did you have a service that needed restarted after the change was applied?

(by xavpaice)
The line in tests assert "CPUAffinity=1,2,3,4" in systemd_content should ensure that the failure is picked up.  The test reads /etc/systemd/system.conf.
I built a test system using the current 'master' for the charm, cpu-affinity-range was "".  Content of /etc/systemd/system.conf included #CPUAffinity=1 2.
Change:
juju config sysconfig-focal-local cpu-affinity-range="1,2,3,4"
/etc/systemd/system.conf included CPUAffinity=1,2,3,4
My test was using focal, and charm code which at the time matches stable/21.04

(by peppepetra)
I can't reproduce that either in candidate/21.10

(by peppepetra)
I had a look again today and I can reproduce the bug when using focal despite the revision used.
I am marking this bug as valid

(by peppepetra)
Workaround is relying on the deprecated cpu-range and reservation
i.e.
juju config sysconfig cpu-affinity-range="1,2,3,4" # Not working
Reconfigure with cpu-range
juju config sysconfig --reset cpu-affinity-range
juju config sysconfig cpu-range="1,2,3,4" reservation="affinity"


Create sample CZML utilizing all current graphics

As we add more capabilities to the DynamicScene/CZML layer, we should maintain a sample CZML file that demonstrates all primitives, with examples of constant/interval/sampled properties.  It doesn't have to be a realistic example, since it would serve as a catalog of what's possible, and also as a quick visual smoke test.

Closing as duplicate with #3027


Setup pkg

Setup the whole package again and add some files to .gitignore. Also removes the gitlab ci config.
This supersedes the #4 PR and hopefully gets rid if the init branch f***up #3 also closes #2, #5

Still needs:

a fixed R version? I think it is like this:

env:
   - TRAVIS_R_VERSION=3.5.2

only one license file

I think that the following (that was setup by @mrustl) checks on different R versions, an old and the current released version (I do not know which they are but assume that release refers to 3.5.2) and the current development version:
r:
  - oldrel
  - release
  - devel

I would like to keep that.

The markdown copy of the license file is required for the auto-generation of the documentation, so I would like to keep it even though it is just a duplicate.

Okay. Cool. Let's keep it that way. I goes this is an approved review and I'll merge this now.


Processes written file, not buffer

Executing Neomake processes the content of the saved file. Hence changes to the buffer which are note saved yet won't be considered. I often find my self fixing an error and checking if it worked by running Neomake and consequently wondering, while there still is an error.
Expected behavior

I would have expected Neomake to process the content of my buffer, so what I actually see. So I can first check if I really fixed my error before writing the file.
This would also allow a more responsive behavior like e.g. Pyflakes-Vim has, where Neomake via multiple auto-commands in the background, while I am still typing.
Of course a feature for a continuous scan in the background for IDE like error-warnings would be a welcome feature.

let g:neomake_tempfile_enabled = 1
It is not enabled by default, since I wanted to see how it behaves with people opting in, but in the long run we might enable it by default.
See https://github.com/neomake/neomake/pull/1167 for a start at automaking.


Changes for 3.7.1

perf(LuaJIT): revert optimization for hash (#13240)
docs(changelog): move changelog file to correct place
docs(release): genereate 3.7.1 changelog

Summary
This PR includes all the changes needed between 3.7.0 and 3.7.1:

A perf change on LuaJIT
A small fix to the previous change; changelog yml file was not in the correct spot
A manual generation of the changelog with that single change.

Related with  KAG-4466

superseded by #13262 due to branch name protection


Doesn't encode page names

I was attempting to run the script on http://enwp.org/Dungeons_%26_Dragons_Online and was curious to why I kept getting sent to http://enwp.org/Dungeons to post the results when I realized the link to the page was https://en.wikipedia.org/w/index.php?title=Dungeons_&_Dragons_Online&action=submit and it was breaking on the & in the middle of the title.  https://github.com/zhaofengli/reflinks/blob/fd6be503ab4b126bec558d8288cc9d6a63777956/style/templates/result.html#L13 shows that it is sending ?title={{ pagename }}&action=submit back to the page.  I'm not familiar enough with your setup to know if there is a {{ url_encoded_pagename }} of some kind or where those variables are coming from, but that is what is needed to correct this problem.

Fixed. Thanks for reporting! :-1:


Onboard APIScan to our build pipeline

The deadline is January 2024.

Send payment
On Thu, Oct 12, 2023, 3:06 AM JasonYeMSFT @.***> wrote:

The deadline is January 2024.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/AzureStorageExplorer/issues/7391, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AMBWFPOSC2EL2BRGLFKQAETX63U3PANCNFSM6AAAAAA54O5UPU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

All files are covered now!


Domain

I want to buy a domain name for the application and I think to deploy it on production. Give me some advices which domain to use:

.net
.com
.eu
????

Okay, thank you for the suggestion.


Having .rml and .rcss named the same prevents from one of them loading

Currently, if you, for example, have main.rml and main.rcss in the same folder, with main.rml file linking main.rcss file as a stylesheet, then main.rcss is going to fail from loading. This is probably the main reason for the issue that got fixed with https://github.com/GoaLitiuM/RmlUi/pull/9

Considering that flax does not allow to preserve original extensions, this is more of a Flax limitation than of the plugin.


BlockId removal: refactor: BlockBackend::block|block_status

It changes the arguments of:

BlockBackend::block
BlockBackend::block_status

method from: BlockId<Block> to: Block::Hash
This PR is part of BlockId::Number refactoring analysis (paritytech/substrate#11292)
polkadot companion: paritytech/polkadot#6477
cumulus companion: paritytech/cumulus#2041

bot rebase

bot merge

bot merge


[WIP] Fix input type on android using SDL2 as window provider

This pull request allows the use of input_type and keyboard_suggestions properties to modify the keyboard displayed on Android. In summary, it uses the changeKeyboard function in PythonActivity.java (see kivy/python-for-android#2057). Additionally, keyboard_suggestions was moved from kivy/uix/textinput.py to kivy/uix/behaviors/focus.py, so it's more accesible to send to the  request_keyboard method.
This is ready to review. Note that you may encounter some bugs with these changes:

Inserting any emoji will crash the app in older Android versions, and a tofu will appear in latest versions.
Keyboard suggestions have a weird behavior. You won't see anything you type until you select the suggestion.

The details are in (kivy/python-for-android#2015).  Unless those bugs are solved, this PR shouldn't be merged.

Closing for https://github.com/kivy/kivy/pull/7231.

Closing for https://github.com/kivy/kivy/pull/7231.


fs: Define DT_xxx to number directly

Summary
and map DTYPE_xxx to DT_xxx like other OS
Impact
no real change
Testing
Pass CI

what's the point of this change? are you going to remove DTYPE_xxx?

what's the point of this change?

There is code which redefines DT_xxxx(e.g., http://www.aleph1.co.uk/gitweb/?p=yaffs2.git;a=blob;f=direct/yportenv.h;h=5a79f93583b963d715b0dee9a0b533363c1511e1;hb=HEAD#l52).  This change avoids the compiler generate the macro redefinition warning.

are you going to remove DTYPE_xxx?

No.

what's the point of this change?

There is code which redefines DT_xxxx(e.g., http://www.aleph1.co.uk/gitweb/?p=yaffs2.git;a=blob;f=direct/yportenv.h;h=5a79f93583b963d715b0dee9a0b533363c1511e1;hb=HEAD#l52). This change avoids the compiler generate the macro redefinition warning.

why don't you disable CONFIG_YAFFS_PROVIDE_DEFS and use definitions for nuttx?

Since iattr  and ATTR_xxx isn't defined in nuttx.

Since iattr and ATTR_xxx isn't defined in nuttx.

it's something you should provide as a part of nuttx glue logic, isn't it?
anyway, if yaffs2 is broken, i'd suggest to fix it instead.

Since iattr and ATTR_xxx isn't defined in nuttx.

it's something you should provide as a part of nuttx glue logic, isn't it?

Sorry, I don't think so. If NuttX can make the change to more compatible with 3rd party library and without any side effect. Why not do it?

anyway, if yaffs2 is broken, i'd suggest to fix it instead.

But it can compile without any warning with Linux which define these macros too since the compiler allow the same macro define multiple times if the late definition is same as earlier one.

Since iattr and ATTR_xxx isn't defined in nuttx.

it's something you should provide as a part of nuttx glue logic, isn't it?

Sorry, I don't think so. If NuttX can make the change to more compatible with 3rd party library and without any side effect like this patch. Why not do it?

anyway, if yaffs2 is broken, i'd suggest to fix it instead.

But it can compile without any warning with Linux which define these macros too since the compiler allow the same macro define multiple times if the late definition is same as earlier one.

for the most of macros in the file is defined as the following. i don't understand why these need to be different.
#ifndef XATTR_REPLACE
#define XATTR_REPLACE 2
#endif

@xiaoxiang781216 @yamt so what is the path to move forward here? I read that this change brings regression to yaffs2 and the natural step seems to be reverting of a change and re-evaluating it to a new solution that covers broken cases.

Sorry, I don't see there is anything reason to revert this patch.


Add 'javascript 6to5' syntax name

To lint files using 6to5-sublime's syntax, now that we are starting to see real ES6 support.

Ha! Thanks @gpbl I was about to make a PR for this :smile:

@roadhump Can you push a release with these changes please? Thanks!

Sorry, done now


Fix Python3.8 typing issues (revert to using Union/Optional instead of pipe-notation)

@tdadela brought this to my attention. I still yearn for the day when we drop support for everything prior to 3.10, but that day is not yet here...

Turns out it was actually fixable! #2548


Meme pool

One idea to get more engagement and fun is to have a meme section where users can upload memes to be displayed on the site.
To have some kind of sybil resistance an invoice of (TBD) sats would have to be paid.
Could be a good idea.
The memes must be related to the softfork in question and/or fork-explorer ("green/red squares").

bc1q38dwf2tnxn90autr94myx0a7948lp3cgthvhdz


Fix bin/setup modification failure in installation

Due to different content of bin/setup in different Rails versions, the earlier version of the generator couldn't modify this file properly in all circumstances.
This commit handles the following scenarios:

If there is a commented line for system('bin/yarn'), uncomment it.
Otherwise, regardless of using single or double quotations in different Rails versions, add system! 'bin/yarn' after the intended line.

I have manually checked the impact of this PR on the following Rails versions:

5.2.8: where we already have commented system('bin/yarn')
6.1.7: where we have system('bundle check') || system!('bundle install')
7.0.4: where we have system("bundle check") || system!("bundle install")

closes #226

@ahangarha I'll merge after you update the CHANGELOG.
However, I'm not convinced this modification regarding bin/yarn is even needed longer term.

@ahangarha I'll merge after you update the CHANGELOG.
However, I'm not convinced this modification regarding bin/yarn is even needed longer term.

@justin808 I updated the changelog.
If we don't need such modification at all, then we should remove it entirely.
I think it would be good to make a final decision about this matter before our next major release.


Can't add CSV attachment for Skype using node.js

I have no trouble with content types of image/xxx, but if I add a URL for a csv file as text/csv, it fails with the following stack trace:
Error: Request to 'https://smba.trafficmanager.net/v3/conversations/29%3A1p2kJbFW69eJhxBidUtKWdwrEA13GmqxLjUV5x4J21Ls/activities' failed: [400] Bad Request
at Request._callback (/home/ec2-user/mistrobot/node_modules/botbuilder/lib/bots/ChatConnector.js:434:46)
at Request.self.callback (/home/ec2-user/mistrobot/node_modules/request/request.js:186:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request. (/home/ec2-user/mistrobot/node_modules/request/request.js:1081:10)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at IncomingMessage. (/home/ec2-user/mistrobot/node_modules/request/request.js:1001:12)
at IncomingMessage.g (events.js:291:16)
at emitNone (events.js:91:20)
Any idea how to make this work?
Thanks

File sharing from a bot to a user or from a user to a bot is not supported in Skype today, but it is in our backlog as a feature request.


replace extension build tool make with rake to support platforms without make (e.g. windows)

Hi,
I had problems to install bond on windows+jruby without development kit: Although bond uses jrubys own readline, it creates a empty dummy makefile for jruby users. As windows has no make, installing the gem (even with the empty dummy make file) fails.
I switched from make to rake: as rake is installed by default with any ruby version, the rake command should be available on all systems.
Alternatively, you could drop the c extension completely. I think it is only necessary for <1.9 ruby versions. As ruby 1.8 is no longer supported, there is no reason to keep the c extension.

Thanks for the interest but I'm only looking to support cygwin windows or windows with dev kit. I'll update the readme to mention it. Once I drop 1.8 support then this won't be an issue


AspNet5 - AspNetIdentity sample

Hi,
I'm trying to wrap my head around IdentityServer3 and ASP.NET 5 at the same time (might not be the best idea haha). I would love to have a sample project that demonstrates the AspNetIdentity provider for IdentityServer3 in ASP.NET5. Maybe i'm just over complicating things and it's easy to set up using the pre-existing ones. The other examples are however a bit intimidating because they also set up a IdentityManager(?) and I don't know how that fits in.

I don't think IdMgr will work with AspId3.


Normalize the config file to minimize noise later

We will be scripting a number of changes to the track configuration.
This runs configlet fmt, which ensures that any further changes can be minimized.
See https://github.com/exercism/meta/issues/95

👍

There's a discussion happening in exercism/meta#95 about how this normalization degrades the readability of the configs.
That discussion has some good suggestions for improvements to the serializer.
I'd appreciate it if you would weigh in on that discussion with any suggestions for improving how we handle configs, consistency, and normalization.
Meanwhile, I'm going to close this and wait for that discussion to play out.
I'm sorry about the noise, and any extra work that I've caused you.


[WIP] ci: proposal to restructure github workflow files for portability

This commit is a proposal to move the execution code out of the
workflow files to scripts. This should allow for better portability,
keeping only github (and sometimes AWS) specifics in the workflow files.
This is work in progress
The reason for this proposal is to make easier enablement of Zephyr
CI systems outside of github.
This commit shows only one change (compliance.yaml), its sole
purpose is to start a conversation. Your feedback is welcome.
Signed-off-by: Yves Vandervennet<EMAIL_ADDRESS>

Any comment?

For the sake of transparency, here's a log of my discord chat with Stephanos:
yves — 08/29/2022
Hi, I saw your comment on github. Can you help me understand how reusable is this CI? And what do you mean by "nuanced"?
Thanks
stephanos — 08/29/2022
by "nuanced," I mean one or more of the following:

specific to how GitHub/GitHub Actions works

specific to environment (GitHub Actions virtual runner environment, docker image, ...)

specific to the upstream process

we will likely never accept approach like this upstream.
yves — 08/29/2022
Well, how can any of the runtime instructions be specific to github? References to github vars, etc I understand. But how can 'pip install ..." be specific to github? As it is today, that is my understanding, none of the runtime for CI is reusable. Companies may not be allowed to use github or maybe they have their own CI systems.
With the current structure of the workflow files, how can a company keep up with the upstream CI with workflow files providing so much CI runtime code?
stephanos — 08/29/2022
what do you think scripts/ci/check_compliance.py does?
the rest of it is really just glue code
yves — 08/29/2022
check compiance that's it
stephanos — 08/29/2022
you only need to call scripts/ci/check_compliance.py in your workflow/pipeline to make it work.
yves — 08/29/2022
Hmm, we may be misunderstanding each other here...
How about twister?
stephanos — 08/29/2022
scripts/twister?
the rest of the code is, once again, just glue code
https://github.com/zephyrproject-rtos/example-application/blob/main/.github/workflows/build.yml
this is possibly the simplest workflow running twister
really we don't need an extra script for this
yves — 08/29/2022
I am still not aligned, I'll explore some more.
I see that the notion of 'glue code' is different. Please understand I am not trying to make a big stink of all this. All I am trying to do is reuse what is run by the community because we want to run the same tests prior to submitting our PR's.
And by tests -> I mean what are defined as workflows....
stephanos — 08/29/2022
we already have all the logic outside the workflows. there are dedicated scripts for that.
we are not going to accept any changes that moves the code inside the workflows (what we call "glue code") out to a script unless you can provide a very good rationale for that.
yves — 08/29/2022
OK. Sorry if I appear 'pushy' or even 'thick' but how is the following glue code? It's setting up the env to run the rest....
      west init -l .  true

      west config --global update.narrow true

      west update 2>&1 1> west.update.log  west update 2>&1 1> west.update2.log

I am obviously off in my understanding
So let's not continue here, we might just go in circles...
stephanos — 08/29/2022
if you're talking about update.narrow, it's just telling west to do a shallow clone.
you, or anyone else downstream, may or may not want to do that.
once again, you can easily reproduce what the upstream CI does because we already provide the scripts for them.
what is in the workflow files is more or less specific to how WE (upstream) want to handle things, and also many things specific to upstream.
yves — 08/29/2022
OK. Thanks.
yves — 08/31/2022
Are you OK if I post some of your comments to github?
Just for other people to follow
stephanos — 08/31/2022
sure. I would suggest moving this discussion to a thread in #infrastructure channel so this is publicly visible
yves — 08/31/2022
Yes. I heard of one person who wants to chime in
I believe it will be over github.
So, I have to add one comment I have not made yet... I hear your comment about nuanced code, yet, a lot of it is common to any CI, i.e. west commands, etc
stephanos — 08/31/2022
I don't understand what you mean exactly
are you talking about refactoring common functions out?
yves — 08/31/2022
That is my goal, yes.
That is the spirit of what I am doing
stephanos — 08/31/2022
there are not that many common functions and each workflow tends to have slightly different requirements, and the amount of the common code is minimal so I would not put efforts into that.
yves — 08/31/2022
OK : common = common to all CI setups
or systems should I say
stephanos — 08/31/2022
if we really think something is worthy of deserving a generalised implementation, then we can write an "action" for it.
yves — 08/31/2022
That could be a "githuby" way  of going
stephanos — 08/31/2022
to my understanding, what you are doing is to implement your own CI for Zephyr
yves — 08/31/2022
But would this enable other CI systems??
Not that I know
stephanos — 08/31/2022
no. that is beyond the scope of the upstream CI.
stephanos — 08/31/2022
I would suggest implementing your own based on the upstream one first, instead of trying to introduce changes to the upstream CI to fit your needs.
there are many history and details involved in the upstream CI, also future roadmap/plans on how it's going to change.
yves — 08/31/2022
I get the recommendation. My purpose is to make it easier for downstream CI's to keep up with changes in the upstream CI
That is it
stephanos — 08/31/2022
you will be wasting a lot of time by trying to change the upstream CI without being heavily involved in the process.
yves — 08/31/2022
I wish we could talk to each other... What do you mean by that?
stephanos — 08/31/2022
it's not like we overhaul the upstream CI every month
there are tens of downstream users that implement their own Zephyr CI loosely based on the upstream process.
and they don't have any major issues.
yves — 08/31/2022
OK. I was not implying there would be a ton of issues... Perhaps I am thinking in too broad terms.
stephanos — 08/31/2022

Perhaps I am thinking in too broad terms.

I would say so. keeping your own (downstream) pipeline in sync with the upstream CI is really not much effort
in fact, you should almost never need to do it.
maybe once a year
the upstream CI is mostly just running twister (and maybe docs build). the rest is just specific to the upstream project process.
so you really don't need to care about the rest
yves — 08/31/2022
I see. Okey dokey, thanks for the chat.


Remembered password shouldn't be viewable

If remember password is set, someone using my PC could access encrypted content during the timeout. That makes sense and is expected.
What is not expected is that someone using my PC could access the password itself by clicking on the glasses icon while the password is remembered. The password is, in a way, the most private part of the encrypted note, since it opens access to the note and possibly other notes / accounts.
Thanks for this great plugin.

Oh, like if you give someone access to your note... But not having your password exposed by the click of a button... Makes sense.
I could add an option to hide the glasses icon in settings.
Although, someone with enough knowhow could still reveal the password from the input box. So, it's probably better to not have the passwords remembered at all in that case.
But yes, at least a settings option would make it harder to have a password exposed than simply clicking a button.

Indeed, that would be a good improvement. As a side note, another change would make this need obsolete:
In Lastpass, when it remembers my password, it doesn't ask me at all for that duration.
Ideally, this would mean that while a password is remembered:

if it matches an encrypted file I'm trying to access, I wouldn't even get a popup. (Maybe a flash message to mention that the remembered password was used).
if the password doesn't match, you just show the form as usual, without any password pre-filled.

Doing this would solve all of the problems mentionned in this issue so far and be a better experience for the user.

added in next release


Issue #89 persists - Duplicates

See #91 and #89

Could you provide steps to reproduce?
By the way, if notes were duplicated in the past. The plugin will not delete the duplicated notes.

Feel free to reopen this ticket if you encounter this problem again :)


nifcloud_customer_gateway: Add resource

Overview
Add a new resource nifcloud_customer_gateway.

Implemented in #27

Implemented in #27


Error events for ECONNREFUSED

Recently ran into a case were the connection refused because of a log limit being reached. Are there errors emitted by the module that would allow me to catch that error?

This happened to me as well and temporarily brought down a production box - would love to see this caught/catchable

Hey all, if you pull master, the final fix for this (#61) should now be in the code and will be released to NPM in the next week or two. Even without an error handler defined, connection errors now default to being output to the console but not affecting runtime.
If you pull master (or use an eventual 1.0.4 release, when it's out) and see any impact from connection errors, please open a new issue with the transcript and version in use.


Containers do not accept new settings when restarted

Any changes to config that affect the configuration of a container will not be applied until the container is destroyed and recreated.
Expected Behavior
Changing config and restarting containers should apply config changes
Current Behavior
Changing config and restarting containers keeps the old config
Possible Solution
It should be possible to force docker-compose to rebuild the containers with new settings from images when restarting
Steps to Reproduce (for bugs)

Start node
Change settings (e.g. log level)
Restart node
New settings are not applied

Context
Cannot reconfigure nodes
Your Environment

Version used:
Environment name and version (e.g. Chrome 39, node.js 5.4):
Operating System and version (desktop, server, or mobile):
Link to your project:

Fixed


Update apache-spark-overview.md

@Banani-Rath : Thanks for your contribution! The author, @hrasheed-msft, has been notified to review your proposed change.


Fix command injection and remove useless util.format

I have been notified that there is a command injection risk in the package.
Even if it seems very unlikely, the fix is simple enough.
I have also removed util.format while modifying commands, it does not seem necessary and Node documentation indicates it has an important overhead. It will maybe shave some micro-seconds off some CIs

@shazron are you still active? Would you mind taking a look?


Support for Django 3.2

Django 3.2 has relevant changes that are incompatible with the current release of wagtail-robots. The change in AutoField from django 3.1 to 3.2 LTS creates the behavior of migration that generates an ever-missing migration, and makemigrations want to create this AutoField change, and it will not go away without a release that addresses the new AutoField in django 3.2.
wagtail-robots seems to have drifted away from django-robots enough that attempts to migrate to django-robots will generate a catastrophic database migration path, given that they seem to use the same table names.
Django-robots commit https://github.com/jazzband/django-robots/commit/70da7606974b915d57e038f8bdf31c0b21be7e45 addresses and fixes this issue for them.

Will hopefully get a chance to take a look at that soon! Thanks for the link to how they handled it. :)


[feat] displayName for package

Describe the problem
This is probably nitpicking, but I am looking to have two separate "names" for my Tauri application.  Right now, I understand that in tauri.conf.json I can define package -> productName.  This is what is used to name installers, exe's, log files (if using the plugin), etc.
But it also is what is used for the "user-facing" display name, for example what it is called in the Start Menu on Windows.  So for my-app, if I want the user to have a "user-friendly" name to search for, I need to set productName to My App.  But then the underlying executable is called My App.exe, which just kind of irks me lol.  I think it should be my-app.exe.  It just seems more professional, and more in line with what I see in other apps I have installed on my system.
Describe the solution you'd like
Keep productName as the default way of naming your app.  But add an option in package called displayName, which determines the "user-facing" name of the application, while keeping file-system friendly productName for .exe's, etc.
Alternatives considered
I am thinking that this would be an app manifest thing on Windows.  Not sure about Linux and Mac.
Additional context
No response

x3, waiting for this feature.

Is there any progress? I really need this function

The PR is linked right above your comment -> https://github.com/tauri-apps/tauri/pull/9375
We can't backport that exact solution to v1 though because it's a breaking change.

Just a note that we have decided to add mainBinaryName option in https://github.com/tauri-apps/tauri/pull/10977 to control the main binary name, this makes productName essentially the displayName (which is what it was supposed to) and the new option for main binary name only.


Issue 29 - multiple nameservers

This should fix Issue #29 by allowing multiple nameservers to be specified in a CSV format. It's pretty dumb and just cycles through the namesevers until it either has no error, or all of them fail.

Would love this functionality. Any update @tonistiigi?

Done merged on develop


[MM-48175] Improve accessibility for settings modals

Summary
A big change to the settings modal and profile modal that addresses various accessibility tickets.

The sidebar now implements the tablist design pattern. Thus the user can tab into the sidebar, then use the up/down keys to switch tabs. Another tab press goes directly into the tabpanel instead of the next tab. This makes navigation by keyboard much faster.
Each "edit" button is tabbable. When clicked/pressed, the section is expanded and the first input is highlighted (in general), including selected radio inputs and unselected checkbox inputs. This reverts an old change (https://github.com/mattermost/mattermost-webapp/pull/3385) but I think it makes the accessibility much better. When the section is closed via enter key press, cancel, or submit button press, the "edit" button is automatically focused. It has an aria-expanded value of "false" so that screen readers will announce that the section has closed.

The end result is not perfect. I didn't want to fix everything in one PR because the end result would be a massive diff. This PR is merely for fixing the focus behaviour of the larger elements in the modal, i.e. the sidebar and panels. Fixing bugs within the panels can be done in later PRs.
In particular, some dropdowns are inaccessible because are using a library for them, so they can't improved other than by changing the library we use.
The theme chooser panel is very inaccessible. I have created a new ticket for this.
The modal itself is not perfect. It doesn't trap focus from going into the address bar, and the entire modal gets focused when the modal opens, rather than on the close button or header. This is confusing accessibility-wise, but is difficult to change because it's controlled by React-Bootstrap. Similarly, the nested modals, which also use React-Bootstrap, are confusing to navigate for the same reason. We can only fix these issues by using another modal library or implementing our own accessible modals, which can be done at a later point if desired.
Ticket Link
Fixes these:
https://mattermost.atlassian.net/browse/MM-48171
https://mattermost.atlassian.net/browse/MM-48170
https://mattermost.atlassian.net/browse/MM-48175
https://mattermost.atlassian.net/browse/MM-48176
https://mattermost.atlassian.net/browse/MM-48851
https://mattermost.atlassian.net/browse/MM-48852
Screenshots
https://user-images.githubusercontent.com/112951043/206749639-401022b9-eca0-4d74-987e-7f0a68de0459.mov
Release Note
Improved keyboard and screen reader accessibility for settings and profile modals.

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard


Add Thread Certification 9.2.17 to automated test.

Current coverage is 73.14% (diff: 81.48%)

Merging #786 into master will increase coverage by 0.54%

@@             master       #786   diff @@
==========================================
  Files           107        107
  Lines         15994      16017    +23
  Methods        2181       2182     +1
  Messages          0          0
  Branches       1901       1905     +4
==========================================
+ Hits          11612      11716   +104
+ Misses         3761       3693    -68
+ Partials        621        608    -13

Powered by Codecov. Last update 0754ac7...3f07b99

Will verify 9.2.17 and 9.2.18 on hardware soon.


Host mode SyncVar hooks aren't called the way they should be

note: this existed since day 1 in UNET. we currently have a workaround in master where we connect the host connection before calling SpawnObjects. that doesn't work with local connections that go over the transport though, which is why we need a better solution.
the problem:
when setting a SyncVar in OnStartServer, the hook will never be called for the host because the host isn't connected yet during OnStartServer AND once it does connect, ApplySpawnPayload->OnUpdateVars->OnDeserialize is never called, hence the SyncVarHooks aren't called.
at runtime, the only reason why they are called (even though OnDeserialize isn't) is because the weaver adds a special case to call them during SyncVar.set.
reproduce

use the planets example: https://github.com/vis2k/Mirror/pull/1249/
StartHost: move ConnectHost call to AFTER SpawnObjects
see how SyncVar hooks aren't called

current workaround
currently StartHost connects the host client connect BEFORE calling SpawnObjects. this however only works because of our fake local connection doesn't go through the network, it connects immediately. once it does go over the network we need to wait until NetworkServer.OnConnected(connId) finds the host connection, then spawn.
solutions
a) call ApplySpawnPayload on host too. BUT this will overwrite server state from 10ms ago to the one that was sent. it sucks.
b) call all SyncVar hooks once the host connected.
c) by design: assume that hooks aren't when modifying SyncVars in OnStartServer. just live with it and remove the ugly workarounds. this might be the way to do it.
d) separate host client and host server in memory. and call ApplySpawnPayload/OnDeserialize etc. unfortunately this is nearly impossible with the current design where GameObjects and Hierarchy are shared by host server and host client.
e) live with the workaround. accept that host mode will never be perfect.

See also #1151 and #1278

a) does not work with synclists/sets/dics.  So you will have to apply spawn payload but without the syncobjects.
b) well,  the goal of the PR was to make things simpler.
d) extremely complicated
There is another similar problem.   In master,  when OnStartServer is called in host mode, the property isClient is already set (for scene objects).   In your PR I don't believe it is set.

Does this need to remain open, or was it addressed in #1416 ?


fix: generate length prefix with encoded data

Problem
While dealing with the EBCDIC1047 encoding, some characters can be decoded from 1 byte to 2 bytes. It can cause an issue with the message packing.
For instance, this decodes EBCDIC1047 to UTF-8. it will transform 65 (0x41) to 2 bytes (0xc2, 0xa0).
When we pack this data again, the data length we got is 2 instead of 1.
How to reproduce
	spec := &field.Spec{
		Length:      5,
		Description: "Field",
		Enc:         encoding.EBCDIC1047,
		Pref:        prefix.EBCDIC1047.L,
	}

	str := field.NewString(spec)
	str.SetBytes([]byte{194, 160, 49})
	packed, err := str.Pack()
	size, err := str.Unpack(packed)

the Unpack will fail with the error failed to decode content: not enough data to decode. expected len 3, got 2.
Because the str.Pack() encode 3 as length prefix. The actual representation in EBCDIC1047 of []byte{194, 160, 49} has only 2 bytes (0x41, 0xf1)
How to fix
Encode the length prefix with encoded data, instead of original data.

Closed. Open a new PR https://github.com/moov-io/iso8583/pull/340 with another fork


Clean and review institution pages

Remove remaining unnecessary code in each review and create project, left from the split.
-- Update page routes
-- Update ftl
Create a component for the common institution editor
Update API to split create and update institution into individual calls
Update API to split getAllUsers and getInstitution users into individial calls
Use base64encoding for uploading file, eliminate form object.
Update UI
-- Only show delete on imagery which is owned by institution
-- Show project privacy
-- Show project status with red/yellow/green
-- Hide email list for non users
-- Hide pending members for non admins
-- Show user role for members
-- Style information block

OfGroups.java:

createInstitution() and updateInstitution() have not been updated to accept JSON data instead of MultipartForm objects.
--- Are we maintaining this database?  Im sure there are quite a few places where the functionality has not been updated.  I do not have a way to test any changes either.

collection.js:

Line 27: Why did you remove saveValuesButtonEnabled?
--- This value is calculated and no saved in the state

create-institution.js:

Line 39: Have you verified that this goes to the .catch() function when an error occurs?
--- Yes.  If we throw a reject, we also need a catch.  I also tested no reject, and it seems to be just as happy, nothing is passed to the next .then() if nothing is resolved.

home.js:

Line 558: Are you sure that the unmatched "i" tag is valid HTML?
---- any tag can be self closing in React.  However, I kind of glossed the whole "i" tag thing over, letting myself think i is image.  The i tag is probably not the most appropriate here in general, so I changed them all to span or div depending.

review-institution.js:
---  Sorry for making you review this, it looks like I missed a git push from my final review.

Line 609: Need to add a test for the error condition first: data === "" ? "" : ...
---  My way was intentional so the error condition will default to red, along with any other abnormal situations.  With the opposite, abnormal would end up as yellow. the opposite logic would look like:
boxShadow: data === "" || data.analyzedPlots === 0
? "0px 0px 8px 1px red inset"
:  data.unanalyzedPlots === 0
? "0px 0px 8px 1px green inset"
: "0px 0px 8px 1px yellow inset"

Line 750: Illogical test. Why would you test if this.props.userId === 1 here?
---- We have set up user 1 as the super user (admin@o----f---.org).  We also then hide user one from the users list API so we cant just check against the returned results

Line 774: Does this override the sort on line 773?
---- This seems to correctly order by role then email

load_ceo_functions.sql:

Line 1086: Is this change intended?
---- Yes, this now matches the JSON logic

isInstitutionMember() test is still illogical. You need to compare findUserByEmail(userEmail).id === 1 NOT this.props.userId === 1
---- You are correct.  I miss understood what was wrong with the code.

Line 777: Did you update SurveyCollection.js to take a selectedSampleId prop?
--- This is the merge error I referenced.  The prop is needed for highlighting answers.


IRGen: Set a "not bitwise borrowable" bit in value witnesses for @_rawLayout types.

For types like Atomic and Mutex, we want to know that even though they are technically bitwise-takable, they differ from other bitwise-takable types until this point because they are not also "bitwise-borrowable"; while borrowed, they are pinned in memory, so they cannot be passed by value as a borrowed parameter, unlike copyable bitwise-takable types. Add a bit to the value witness table flags to record this.
Note that this patch does not include any accompanying runtime support for propagating the flag into runtime-instantiated type metadata. There isn't yet any runtime functionality that varies based on this flag, so that can be implemented separately.
rdar://136396806

@swift-ci Please test

@swift-ci Please test


Add template with navbar & update app.py

closing issue #27

@lioramilbaum
Added route for subscribe


[SET_CERTIFICATE] Save certificate into SPDM context

https://github.com/DMTF/libspdm/blob/a27fe8164d8edcbe3143e5b9e65f0c378c2df77a/library/spdm_responder_lib/libspdm_rsp_set_certificate.c#L138-L147
If reset is not required, should the certificate chain be added into spdm_context?
Note: in case of AliasCert model, it might need to extract Alias cert from slot 0 and append the Alias cert to compose a complete certificate chain.

DeviceCert mode + reset needed: Not save to context
AliasCert mode + reset needed: Not save to context
DeviceCert mode + reset not needed: Can save to context <==
AliasCert mode + reset not needed: Not sure if it is valid?
Question: libspdm save the context? or Integrator save the context ?
Conclusion: It is easy that libspdm save the context.
We can let integrator save to the context by using SetData(), because the integrator can know the slot id and full cert chain data. But libspdm_write_certificate_to_nvm() does not have libspdm_context. It seems problematic. Maybe define a callback function?

Integrator saves Certificates into context seems a better solution.

libspdm_write_certificate_to_nvm() didn't have libspdm_context: could we pass spdm context to the function?
Anyways, the integrator should have that context. Otherwise the integrator won't be able to set Certificates during libspdm initialization.
current libspdm_write_certificate_to_nvm() returns bool, could we change it to return a status?
If integrator can't update the full Certificates into the spdm context, it should return SPDM_ERROR_CODE_RESET_REQUIRED or a specific error code. spdm_context->need_reset_to_set_cert is not necessary then.

Another special corner case, that a device may setup 2 spdm_context, such as PCI_DOE and MCTP.
If a certificate chain is setup from one context, do we need provision to the other context ?

Integrator saves Certificates into context seems a better solution.

libspdm_write_certificate_to_nvm() didn't have libspdm_context: could we pass spdm context to the function?
Anyways, the integrator should have that context. Otherwise the integrator won't be able to set Certificates during libspdm initialization.
current libspdm_write_certificate_to_nvm() returns bool, could we change it to return a status?
If integrator can't update the full Certificates into the spdm context, it should return SPDM_ERROR_CODE_RESET_REQUIRED or a specific error code. spdm_context->need_reset_to_set_cert is not necessary then.

Integrator saves Certificates into context seems a better solution.

libspdm_write_certificate_to_nvm() didn't have libspdm_context: could we pass spdm context to the function?
Anyways, the integrator should have that context. Otherwise the integrator won't be able to set Certificates during libspdm initialization.

No. We discussed in the meeting. The device secrete lib should be context independent.

current libspdm_write_certificate_to_nvm() returns bool, could we change it to return a status?
If integrator can't update the full Certificates into the spdm context, it should return SPDM_ERROR_CODE_RESET_REQUIRED or a specific error code. spdm_context->need_reset_to_set_cert is not necessary then.

No. We discussed in PR. need_reset should be a predefined attribute from the integrator. No need to return every time.

There probably needs to be two callbacks to the integrator. One for authorization and the other to populate the spdm context with the new certificate.

Integrator saves Certificates into context seems a better solution.

libspdm_write_certificate_to_nvm() didn't have libspdm_context: could we pass spdm context to the function?
Anyways, the integrator should have that context. Otherwise the integrator won't be able to set Certificates during libspdm initialization.

No. We discussed in the meeting. The device secrete lib should be context independent.

Would you elaborate more about " The device secrete lib should be context independent"?
I am okay with the principle but just curious what's the design consideration here.
Back to set certificate, why is this function in device secret lib?
Measurements and keys are device secret, but saving certificates into NV sounds more like a general callback function the integrator could register?

Would you elaborate more about " The device secrete lib should be context independent"?
I am okay with the principle but just curious what's the design consideration here.

non-libspdm modules that are provided by the integrator may be realized entirely in hardware, so it would be weird to pass the spdm_context to them. It provides a boundary between libspdm and the modules it depends on, and maintains the spdm_context as an opaque structure.

Back to set certificate, why is this function in device secret lib?
Now that its scope has increased "secret lib" may not be the appropriate name anymore. It's more like "subsystem within a Responder that provides confidentiality and integrity".

Would you elaborate more about " The device secrete lib should be context independent"?
I am okay with the principle but just curious what's the design consideration here.

non-libspdm modules that are provided by the integrator may be realized entirely in hardware, so it would be weird to pass the spdm_context to them. It provides a boundary between libspdm and the modules it depends on, and maintains the spdm_context as an opaque structure.

For this purpose actually we could use void * in the callback function, e.g.
void spdm_server_connection_state_callback(     void *spdm_context, libspdm_connection_state_t connection_state)
Current device secret lib functions doesn't need the spdm_context but when it's necessary, using void * doesn't seem to break the boundary to maintain spdm_context as an opaque structure.
Usually the integrator should already implement the code to compose/verify full cert chain (from provisioned certs) and then set data into spdm_context, e.g. https://github.com/DMTF/spdm-emu/blob/e85b78f5e0daec0632c5c6dfbf79d22548bc6cf2/spdm_emu/spdm_responder_emu/spdm_responder_spdm.c#L240-L241
It would make more sense to leave saving certchain into context for the integrator and allow integrator to decide reset is needed or not at run-time.


Add support to image and background's

Hi @jjfernandes87 sorry for the huge delay to answer! I'll review your PR asap :)
Thanks for the contribution!


Use CR definitions instead of configmap data

Hello,
I just would like to ask if it makes sense to use the catalog source CR instead of a configmap, since managing multiple CSVs and CRDs in a configmap field can become a bit messy is you have lots of those.
Does it make more sense to add that info into the catalog source object instead?
It could use the same three fields used in the configmap but they could each be a list of their relative CRs:
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  generation: 1
  name: custom-operators
spec:
  displayName: My Operators
  publisher: myself
  sourceType: embedded
  data:
    clusterServiceVersions:
      - csv-name1
      - csv-name2
      - csv-name3
    customResourceDefinitions:
      - crd-name1
      - crd-name2
      - crd-name3
    packages:
      - pkg-name1
      - pkg-name2
      - pkg-name3

It could also use some kind of label matching so it could scale a bit better (no need to list all dependencies in the catalog source cr):
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  generation: 1
  name: custom-operators
spec:
  displayName: My Operators
  publisher: myself
  sourceType: selector
  selector:
    matchLabels:
      catalog: custom-operators

@odra Thanks for your input! In your suggestion, would the manifests of the CRDs/APIServices/etc still be stored in a ConfigMap, or in the CatalogSource CR itself?
Just a heads up - we're already moving away from storing CatalogSource data in  ConfigMaps. Instead, CatalogSources will be backed by operator-registry containers.

In a CatalogSource resource so we don't need to store any data in a configmap object.
Good to know about operator-registry, I will take a look at it :)
Thanks for the quick response.


New version: Mattermost.MattermostDesktop version 5.9.0

Pull request has been created with komac v2.3.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978334957
2024-08-22 11:17:54.594 [CLI ] ShellExecute installer failed: 1633
MSI (s) (54:10) [11:17:54:354]: Product: Mattermost -- Installation failed.
This installation package is not supported by this processor type. Contact your product vendor.

Automated error analysis suggests -1978334957 may mean Package not supported by the system.
Automated error analysis suggests 1633 may mean ERROR_INSTALL_PLATFORM_UNSUPPORTED - This installation package is not supported by this processor type. Does this manifest have Architecture: x86? It might need to be x64.
(Automated response - build 888.)

Automatic Validation ended with:

2024-08-23T09:17:47.7928246Z Manifest Validation Failed
2024-08-23T09:17:52.8652444Z

(Automated response - build 888.)

Automatic Validation ended with:

Installation failed with exit code -1978334957
2024-08-27 09:42:01.383 [CLI ] ShellExecute installer failed: 1633
MSI (s) (7C:88) [09:42:01:210]: Product: Mattermost -- Installation failed.
This installation package is not supported by this processor type. Contact your product vendor.

Automated error analysis suggests -1978334957 may mean Package not supported by the system.
Automated error analysis suggests 1633 may mean ERROR_INSTALL_PLATFORM_UNSUPPORTED - This installation package is not supported by this processor type. Does this manifest have Architecture: x86? It might need to be x64.
(Automated response - build 888.)


fix: add version check for lockfile

We only support pnpm-lock.yaml version 6.x, which corresponding to pnpm 8.x

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.chao.guo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Iterator is in failed state

Hi,
I have set up a flow similar to the diagram on home page, and I'm getting the error:
" java.util.concurrent.ExecutionException: java.lang.IllegalStateException: Iterator is in failed state"
Any ideas?

Hi,
Can you post the full stack trace?
On Fri, May 1, 2015 at 23:28 Eugene Miretsky<EMAIL_ADDRESS>wrote:

Hi,
I have set up a flow similar to the diagram on home page, and I'm getting
the error:
" java.util.concurrent.ExecutionException:
java.lang.IllegalStateException: Iterator is in failed state"
Any ideas?
—
Reply to this email directly or view it on GitHub
https://github.com/RuckusWirelessIL/pentaho-kafka-consumer/issues/6.

Closed due to inactivity.


[markdown-it-shikiji]: Issues with line number highlights while using markdown-it-attrs

Describe the bug
You cannot highlight lines with the {1,3-4} syntax if you also have markdown-it-attrs added as a plugin, since it uses the same curly bracket notation elsewhere. This is more of a proposal than a bug report - is it worth adding a note to the docs about how to resolve this? I figured out that I can change the delimiter of markdown-it-attrs from { and } to other characters to fix this, and I think other people might encounter this as well. On the topic of changing delimiters, that could be something we consider for the markdown-it-shikiji line number syntax as well.
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

You could disable it via:
https://github.com/antfu/shikiji/blob/7620c7bc79783c6c2073596b3271d62b7e4b001e/packages/markdown-it-shikiji/src/core.ts#L7-L12
Would that be enough?

I think you misunderstood what I meant ahah. I want the highlightLines feature, but it wasn't working at first because I had also been using markdown-it-attrs. I figured out a way to change the delimiter of markdown-it-attrs, which fixed the line highlighting feature. My suggestion is to maybe add a note on the markdown-it plugin page about this compatibility issue and potential ways to solve it.

Sure, I agree it's nice to note the compatibility in the docs. PR welcome if you want to work on that :)

Great yeah, I'll make a PR in a sec :)


Backup/Restore ability for all users

In CassKop 1.0.0 we implemented a backup/restore solution. We started to look at Velero but found the following issues:

we needed to make some changes to the code to be able to only backup part of the filesystem
we needed to make some changes to be able to restore part of the backup too
See https://github.com/vmware-tanzu/velero/issues/2361

We then collaborated with Instaclustr, developed a new backup and restore controllers and provided input to Instaclustr for the enhancement and development of Icarus and Esop (we end up with one sidecar running on each pod). On the controllers side it's easy cause we have the ability to use a global request mode where we hit one of the nodes and it acts as a coordinator that talks to itself and all other nodes involved in the operation. It works with AWS, GCS and other cloud providers. It doesn't manage retention but we had in mind to propose the user to use life cycle management at the cloud provider's storage level to support it (https://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html, https://cloud.google.com/storage/docs/lifecycle)
What we propose here is to add a backup/restore feature for all users and it can be done simply by incorporating our controllers with the icarus sidecars. However we don't want to enforce any solutions and we could adapt our controllers to work with Icarus and any other solution that you'd like to promote. But it is a crucial requirement.
I can walk you through the code but here are some links if you wanna take a look at it

https://github.com/Orange-OpenSource/casskop/blob/master/deploy/crds/db.orange.com_cassandrabackups_crd.yaml
https://github.com/Orange-OpenSource/casskop/blob/master/deploy/crds/db.orange.com_cassandrarestores_crd.yaml
https://github.com/Orange-OpenSource/casskop/tree/master/pkg/controller/cassandrabackup
https://github.com/Orange-OpenSource/casskop/tree/master/pkg/controller/cassandrarestore
https://github.com/Orange-OpenSource/casskop/tree/master/pkg/cassandrabackup

Hi, here's another cloud based storage backup/restore approach.

https://github.com/nuvo/cain
https://github.com/helm/charts/blob/master/incubator/cassandra/templates/backup/cronjob.yaml
@jimdickinson Is it possible feasible solution in cass-operator? Thank you.

We've been working on fully integrated Reaper support as part of K8ssandra (cc @jsanda)
@johnsmartco can we update the docs to remove the text and point to K8ssandra's Reaper docs?

Hi @chienfuchen32
Please check out https://github.com/k8ssandra/k8ssandra. It is built on top of cass-opertor and provides additional functionality such as repair and backup/restore. You might be interested in the backup/restore docs at https://k8ssandra.io/docs/topics/restore-a-backup/.

Both repair and backup/restore are more broadly part of k8ssandra now, so I'm closing out this issue.  If there are specific functionality gaps in either of those features within K8ssandra we can open issues for those specific items.

Migrated to https://github.com/k8ssandra/k8ssandra/issues/951