libdrm-tegra-shim: replace to enable non-Tegra displays

In meta-tegra, the libdrm-tegra-shim takes the place of the normal
libdrm. The shim passes through all api calls directly to libdrm-nvdc,
and acts as a build-time dependency where libdrm-nvdc can not. This
approach works fine when the system only uses the Tegra display
drivers, but if a system has other, non-Tegra displays (such as evdi,
udl, or custom DRM drivers), this approach will fail since
libdrm-nvdc can't handle these non-Tegra drivers on its own.
As it turns out, libdrm-nvdc can work in the opposite way. This is
how it is deployed in the JetPack Ubuntu releases. If loaded first,
libdrm-nvdc will internally process calls to any DRM device with
the name tegra-udrm, drm-nvdc, or nvidia-drm (yes, the desktop
driver), but will pass through calls made to access devices with any
other name to the system libdrm.
To enable this functionality, we make sure that libdrm-nvdc is
loaded first by putting an entry in /etc/ld.so.conf.d, and installing
it in addition to libdrm. We let libdrm be the build-time dependency
of any package that needs it, and thus eliminate the need for the
libdrm-tegra-shim. Now Tegra and non-Tegra displays can coexist on
the system.

I like this idea, but I'll need to hold off on pulling it in until I sort out how to get weston to work without the shim.  That should be doable, too, based on a thread I saw on the Jetson forum.

That's funny -- this is something I checked was still working properly before I put together the change set. I'll double-check again with a fresh build on Monday.

Thanks.  I ran my test on a Nano, and while the sato image came up fine, weston had problems initializing.

Confirmed suspicions that Weston seems to be ignoring the ld config and getting drmOpen from the libdrm in /usr/lib:
(gdb) info sharedlibrary
From                To                  Syms Read   Shared Object Library
...
0x0000007fa0b3b5b0  0x0000007fa0b433d4  Yes         /usr/lib/libweston-7/../libdrm.so.2
...

root@jetson-xavier:/usr/lib# ldconfig -p | grep libdrm
	libdrm.so.2 (libc6,AArch64) => /usr/lib/tegra/libdrm.so.2
	libdrm.so.2 (libc6,AArch64) => /usr/lib/libdrm.so.2

Maybe you have some ideas on the top of your head. If not, I'll keep digging.

OK, I've figured out why this is happening. drm-backend.so has RPATH set to ${ORIGIN}/.. so that's taking precedence. I can get around this by adding chrpath --delete ${D}${libdir}/libweston*/drm-backend.so to do_install_append_tegra. I see something similar is done in the recipe for mesa, but for different reasons. Can you think of a better way to handle this, maybe across different recipes which might be doing something similar?

Native meson builds strip rpaths at install, but this is removed by an oe patch to meson (see openembedded/openembedded-core@98a76c3171f9080d6246aac0188ef05c40852adc). So the built libraries keep the rpath used during build, and this gets fixed up later by oe.
As such, another approach that works and is somewhat simpler is to add a weston path that sticks install_rpath: '../tegra' into the meson build for the drm-backend.
I don't think either approach smells too bad, but looking forward to feedback.
I was hoping to find something like adding an additional system-wide library path that gets used during build as well and would magically get picked up by meson (adding another rpath to BUILD_LDFLAGS didn't work). It would be nice to have something that could be added to the machine config, but I can't see how to do this.

Hmm.  BUILD_LDFLAGS would only affect native builds.  Did you try adding it to HOST_LDFLAGS (or TARGET_LDFLAGS)?

Ack, yeah. OK, well that could work. I do notice that TARGET_LDFLAGS no longer contains any rpaths like it used to, so this might be a bigger hammer than we need.
How about this... what about adding an rpath for ${libdir}/tegra to the pkgconfig for the system libdrm? This would fix up any build that leverages the pc for libdrm that doesn't get rpath stripped (like weston), and everything else will use the ld.so.conf.

That sounds like a good approach.

This is working with QT and Wayland. I am just now seeing that the eglstreams-kms-example is getting hung up in a strange way:
#0  __lll_lock_wait (futex=futex@entry=0x7fb7fa7f58, private=0) at lowlevellock.c:52
#1  0x0000007fb7b8ee58 in __GI___pthread_mutex_lock (mutex=0x7fb7fa7f58)
    at pthread_mutex_lock.c:80
#2  0x0000007fb7f826b0 in drmMalloc () from /usr/lib/tegra/libdrm.so.2
#3  0x0000007fb7a7dd28 in drmGetVersion (fd=7) at ../libdrm-2.4.99/xf86drm.c:866
#4  0x0000007fb7f86598 in ?? () from /usr/lib/tegra/libdrm.so.2
#5  0x0000007fb7f870a4 in drmGetVersion () from /usr/lib/tegra/libdrm.so.2
#6  0x0000007fb78cff70 in ?? () from /usr/lib/libnvidia-glsi.so.32.2.1
#7  0x0000007fb7911b7c in ?? () from /usr/lib/libnvidia-glsi.so.32.2.1
#8  0x0000007fb790494c in _nv017glsi () from /usr/lib/libnvidia-glsi.so.32.2.1
#9  0x0000007fb79e8c8c in ?? () from /usr/lib/libEGL_nvidia.so.0
#10 0x0000007fb799f884 in ?? () from /usr/lib/libEGL_nvidia.so.0
#11 0x0000000000401fa0 in GetDrmFd (device=device@entry=0x7fb7a13348) at egl.c:148
#12 0x0000000000401c2c in main () at main.c:46

This works on the JetPack release. I need to troubleshoot this and see what is going on here.

Well, that was fun to track down. It turns out JetPack Ubuntu builds by default (including libdrm) with the -Bsymbolic-functions linker flag. This flag makes sure libdrm's internally-defined non-static functions (like drmMalloc in the trace above) are resolved internally instead of possibly calling back into libdrm-nvdc (which is problematic). Here's an article I found very helpful to explain what this flag is doing: https://flameeyes.blog/2012/10/07/symbolism-and-elf-files-or-what-does-bsymbolic-do/
This is working everywhere I've tried now -- QT eglfs, Weston, gstreamer, and eglstreams-kms-example -- consistently for both drm-nvdc and my custom display driver.

Excellent work on tracking that down.  Thanks!


question about test on one class choice

I directly train the full dataset, then use this trained model to test on one class choice
but there was a problem:
RuntimeError: Error(s) in loading state_dict for DataParallel:
size mismatch for module.conv11.weight: copying a param with shape torch.Size([50, 256, 1]) from checkpoint, the shape in current model is torch.Size([4, 128, 1]).
I hope you can answer. Thank you very much！

If your model is trained with the full dataset, you can't test it with a single class in the test set.
If you really want to test its performance in one class, see #10.

Now I want to check the Miou, ACC and other information of each class. Is there any convenient way?
Thanks again

I think it may be impossible to calculate the mAcc and mIoU of a single class if your model is trained with full dataset. The label prediction of each point can be in anywhere of 50 labels. But you can still calculate Acc by using metrics.accuracy_score.

Then I can calculate the Miou of each class separately in the prediction, which is equivalent to modifying the calculation_ shape_ IOU, right?

Yes

Thank you very much


preview error txt files

Microsoft PowerToys version
0.66.0
Installation method
PowerToys auto-update
Running as admin
No
Area(s) with issue?
File Explorer: Preview Pane
Steps to reproduce

Preview error txt files Windows 11.txt
✔ Expected Behavior
Preview txt files expected.
Problem located in Monaco. Monaco - Off solves my problem en preview txt files is working again.
❌ Actual Behavior
An error occured. See included .jpg file and error txt file.
Other Software
.NET 5

/dup #23384


HADOOP-13126 Add BrotliCodec based on Brotli4j library

Adds BrotliCodec - a compression codec based on Google Brotli
This PR is a continuation on the work done by @rdblue at https://issues.apache.org/jira/browse/HADOOP-13126
In his patches it was based on jbrotli library but this library is not maintained since few years. My PR uses Brotli4j

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  3s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 3 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 33s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 28s

trunk passed

+1 :green_heart:
compile
27m 12s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
22m 26s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
checkstyle
3m 59s

trunk passed

+1 :green_heart:
mvnsite
2m  9s

trunk passed

+1 :green_heart:
javadoc
1m 37s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m  9s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+0 :ok:
spotbugs
0m 33s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
18m 58s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 38s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 19s

the patch passed

+1 :green_heart:
compile
26m 32s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

-1 :x:
javac
26m 32s
/results-compile-javac-root-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.txt
root-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 generated 4 new + 1918 unchanged - 0 fixed = 1922 total (was 1918)

+1 :green_heart:
compile
22m 36s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
22m 36s

the patch passed

+1 :green_heart:
blanks
0m  1s

The patch has no blanks issues.

-0 :warning:
checkstyle
3m 52s
/results-checkstyle-root.txt
root: The patch generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
mvnsite
2m  3s

the patch passed

+1 :green_heart:
xml
0m  3s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m 33s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
2m  9s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+0 :ok:
spotbugs
0m 29s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
18m 42s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 28s

hadoop-project in the patch passed.

+1 :green_heart:
unit
17m 56s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
0m 52s

The patch does not generate ASF License warnings.

221m 29s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2723

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml spotbugs checkstyle

uname
Linux b4b616a90fa4 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 93bcb41ef3f0f4a6fae42143d169a532977f15ba

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/1/testReport/

Max. process+thread count
2902 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 3 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 47s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m  0s

trunk passed

+1 :green_heart:
compile
23m 12s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
20m 33s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 27s

trunk passed

+1 :green_heart:
mvnsite
3m 26s

trunk passed

+1 :green_heart:
javadoc
3m  1s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
2m 33s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+0 :ok:
spotbugs
1m 26s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
23m 24s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 44s

Maven dependency ordering for patch

-1 :x:
mvninstall
0m 28s
/patch-mvninstall-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
compile
0m 53s
/patch-compile-root-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
root in the patch failed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.

-1 :x:
javac
0m 53s
/patch-compile-root-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
root in the patch failed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.

-1 :x:
compile
0m 47s
/patch-compile-root-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
root in the patch failed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.

-1 :x:
javac
0m 47s
/patch-compile-root-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
root in the patch failed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
4m 26s
/results-checkstyle-root.txt
root: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

-1 :x:
mvnsite
0m 32s
/patch-mvnsite-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
javadoc
0m 29s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
hadoop-common in the patch failed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.

-1 :x:
javadoc
0m 28s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-common in the patch failed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.

+0 :ok:
spotbugs
0m 23s

hadoop-project has no data from spotbugs

-1 :x:
spotbugs
0m 30s
/patch-spotbugs-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

-1 :x:
shadedclient
1m 45s

patch has errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 20s

hadoop-project in the patch passed.

-1 :x:
unit
0m 27s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch failed.

+1 :green_heart:
asflicense
0m 36s

The patch does not generate ASF License warnings.

141m 37s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2723

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint spotbugs checkstyle

uname
Linux 19f057b42df7 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 47f05930c2f5c576a6c25238c187bdf3409b8f23

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/2/testReport/

Max. process+thread count
761 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 3 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 55s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 28s

trunk passed

+1 :green_heart:
compile
23m 56s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
20m 37s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 28s

trunk passed

+1 :green_heart:
mvnsite
3m 26s

trunk passed

+1 :green_heart:
javadoc
2m 49s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
2m 35s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+0 :ok:
spotbugs
1m 26s

branch/hadoop-project no spotbugs output file (spotbugsXml.xml)

+1 :green_heart:
shadedclient
23m 36s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 39s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 27s

the patch passed

+1 :green_heart:
compile
22m  4s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

-1 :x:
javac
22m  4s
/results-compile-javac-root-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>.txt
root-jdkPrivateBuild-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> generated 4 new + 2879 unchanged - 0 fixed = 2883 total (was 2879)

+1 :green_heart:
compile
20m 35s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
20m 35s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
4m 19s
/results-checkstyle-root.txt
root: The patch generated 2 new + 0 unchanged - 0 fixed = 2 total (was 0)

+1 :green_heart:
mvnsite
3m 28s

the patch passed

+1 :green_heart:
javadoc
2m 55s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
2m 35s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+0 :ok:
spotbugs
1m 13s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
23m 42s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m  7s

hadoop-project in the patch passed.

+1 :green_heart:
unit
18m 27s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m 36s

The patch does not generate ASF License warnings.

236m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2723

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint spotbugs checkstyle

uname
Linux b9eb43b210c0 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f48cf205c451e724431db46947867a0fb316b7b3

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/3/testReport/

Max. process+thread count
3152 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-common-project/hadoop-common U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2723/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

What is the policy about using Object#finalize() in the compress package ?
The last check fails because of 4 new usages of finalize in the Brotli[De]Compressor` classes.
grep -rnHi finalize ./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/
./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/brotli/BrotliCompressor.java:251:  protected void finalize() throws Throwable {
./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/brotli/BrotliCompressor.java:252:    super.finalize();
./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/brotli/BrotliDecompressor.java:173:  protected void finalize() throws Throwable {
./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/brotli/BrotliDecompressor.java:174:    super.finalize();
./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/bzip2/CBZip2OutputStream.java:711:  protected void finalize() throws Throwable {
./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/bzip2/CBZip2OutputStream.java:713:    super.finalize();
./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/zlib/ZlibDecompressor.java:294:  protected void finalize() {
./hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/io/compress/zstd/ZStandardDecompressor.java:249:  protected void finalize() {

Colleagues,
I've taken the source code from this commit  https://github.com/apache/hadoop/pull/2723/commits/47f05930c2f5c576a6c25238c187bdf3409b8f23
made a jar of it, plugged it into my Spark cluster, launched a huge job with many transformations and actions, and found that there is a serious memory leak: executors consume RAM more and more (no matter that there is a limitation of 20GB, they consumed 40GB).
I've made my own version of Brotli codec (also based on brotli4j) by looking at how Snappy and others are made, and it works with no memory leaks.  Soon I'll post my PR.

@ibobak  If the change is small you can also tell me what to change and I can update this PR.
But it seems there is no much interest in having BrotliCodec. This PR is opened for almost 2 years ...

Update is big.   I am now testing my version of the codec in my organzation, until I am sure that it works fine and without memory leaks, I won't post a PR. I need a little bit more time.

What is pending more in this PR? I can try to help and get this merged.
Brotli4j maintainer here ^_^

@hyperxpro feel free to edit this PR or open a new one based on it.


Provide cats-effect integration

I know of how you feel of having Cats as dependency 🙂 but providing cats-effect integration in a different sub-project would be cool.
Consider that cool libraries like Monix, FS2, Http4s, Doobie and others now have cats-effect integration and would be usable with your Task implementation, if those type class instances are provided.
You also get tests for free via cats-effect-laws, so it would be a win at least for that 🙂

Hey @LukaJCB, I’m not working on it. It’d be great if you could give it a try!

I opened a PR :)

@LukaJCB thanks for working on this, it’s great for validation of the upcoming  Cats-Effect 1.0.0 👍


Fix movement after timer is over

The player should not be able to move after the turn is over
Set the turn duration to something low, then start jumping after the turn is over.

https://github.com/apetavern/sbox-grubs/commit/97a8f4cf73acc8aa293b0aaee072a5048be50759


Add pipeline level 3 - wait for end nodes

Sometimes it is not acceptable for any nodes in the flow to run concurrently with any nodes in another execution of that flow. For example, exclusive access to some shared resource, such as a staging table in a database, might be required.
This PR introduces a third level for the pipeline concurrency option in which none of the nodes in a flow can start until the end nodes in the concurrent execution have finished.

Pull Request Test Coverage Report for Build 4634

1 of 10 (10.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 38.764%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-exec-server/src/main/java/azkaban/execapp/JobRunner.java
1
10
10.0%

Totals

Change from base Build 4616:
-0.01%

Covered Lines:
11458

Relevant Lines:
29558

💛  - Coveralls

Cool, I also need this. @djaiswal83 @ypadron-in would someone be able to review & merge this in, please?

@djaiswal83 bump?

@toby-allsopp are you active on this one any more?
I tested this patch and found some issues:

It doesn't manage to block in some special cases:

I tested this with a flow that has 2 sub-flows + noop job: I launched 2 executions with pipeline level 3, so that in the first execution I disabled one of the sub-flows, and in the second execution I disabled the other sub-flow instead. The noop job enabled in both cases.
The 2nd execution was not blocked.
So it doesn't behave as documented ("none of the nodes in a flow can start until the end nodes in the concurrent execution have finished").

UI changes missing so can't pick Level 3 (very easy to fix though)

Sorry about that.I will take a look in a day or two.

There are no conflicts - maybe this could even be safe to merge. Any way, I can build a new PR on top of these commits with the additional fixes (rebased against latest master).

@toby-allsopp are you active on this one any more?

Sorry, no, I am no longer working with Azkaban. Please do whatever you like with these changes.

@juhoautio thanks for picking this up. Can you please create a new PR with this code change?
Also, can you update the documentation so that users can know about this feature?

I will. Thanks all.

I will. Thanks all.

This documentation page needs update as part of the PR
https://azkaban.readthedocs.io/en/latest/useAzkaban.html?highlight=pipeline#executing-flow

I guess you mean the Concurrent Options section of it, although for some reason didn't link to it directly?
https://azkaban.readthedocs.io/en/latest/useAzkaban.html?highlight=pipeline#concurrent-options

I guess you mean the Concurrent Options section of it, although for some reason didn't link to it directly?
https://azkaban.readthedocs.io/en/latest/useAzkaban.html?highlight=pipeline#concurrent-options

Yes!

Created the new PR. This can be closed now.


Reinstate and deprecate exception threading utility

NetflixOSS » Hystrix » Hystrix-pull-requests #49 FAILURE
Looks like there's a problem with this pull request


TypeError: guvectorize() missing 1 required positional argument: 'signature'

Hi, I face another problem when running the inference.py. The error is: TypeError: guvectorize() missing 1 required positional argument: 'signature', and the picture is provided below. According to the internet it said I am missing parameters in numba, but I still have no idea how to deal with it. How can I solve it? Thanks a lot!!!

It is likely a version issue. You can refer to #79 for the right versions of different packages. For example, use the following packages suggested by @daozhi0921
librosa==0.7.2
SoundFile
munch
pydub
pyyaml
click
tensorboard==2.12.0
numba==0.48.0
pip install setuptools==56.1.0
pip3 install torch==1.9.1+cu111 torchvision==0.10.1+cu111 torchaudio==0.9.1 -f

Hi, thank you for your suggestions!! I have checked my versions which are all the same as the packages you provided. However, I still face the same problem, is there any other way I could solve it?

Then it is a problem with your system. It seems like something is wrong with your librosa package, which is out of the scope of this repo. You may have to ask it in the librosa repo, or even ask ChatGPT for the solution.


Turbo fails on windows

What version of Turborepo are you using?
1.3.4
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Windows
Describe the Bug
Running yarn command returns this:
er dependency<EMAIL_ADDRESS>|| ^17.0.0".
[4/4] Rebuilding all packages...
[-/4] ⡀ waiting...
[-/4] ⡀ waiting...
[3/4] ⡀ esbuild
error C:\projects\javascript\tentree\zos\node_modules\turbo: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: C:\projects\javascript\tentree\zos\node_modules\turbo
Output:
C:\projects\javascript\tentree\zos\node_modules\turbo\install.js:42
    throw new Error(
          ^

Error: Expected "1.3.4" but got ""

Expected Behavior
to install turbo succesfully
To Reproduce
Just install in any project with turbo repo

If I skip install scripts, turbo won't work (will hand on the cli commands)

@darklight9811 are you still seeing this with the latest version of Turbo? Main thing I'd like to narrow down is if this is a Windows-specific issue or not, before moving forward

@mehulkar its working now

@mehulkar out of nowhere the bug started again...

[4/4] Building fresh packages...
[1/4] ⢀ turbo
[2/4] ⢀ core-js-pure
[-/4] ⢀ waiting...
error C:\projects\javascript\tentree\zos\node_modules\turbo: Command failed.
Exit code: 1
Command: node install.js
Arguments:
Directory: C:\projects\javascript\tentree\zos\node_modules\turbo
Output:
node:internal/errors:841
  const err = new Error(message);
              ^

Error: Command failed: node C:\projects\javascript\tentree\zos\node_modules\turbo\bin\turbo --version
    at checkExecSyncError (node:child_process:828:11)
    at Object.execFileSync (node:child_process:863:15)
    at validateBinaryVersion (C:\projects\javascript\tentree\zos\node_modules\turbo\install.js:25:6)
    at C:\projects\javascript\tentree\zos\node_modules\turbo\install.js:305:5 {
  status: 1,
  signal: null,
  output: [ null, Buffer(0) [Uint8Array] [], Buffer(0) [Uint8Array] [] ],
  pid: 5204,
  stdout: Buffer(0) [Uint8Array] [],

I'm trying to debug this because this broke my entire project and I need it back running urgently. From what I can tell, its crashing on the execFileSync because turbo.exe (for windows) is not returning anything.

If I try to run this execFileSync command directly it throws this:
C:\projects\javascript\tentree\zos\node_modules\turbo-windows-64\bin\turbo.exe:1
MZ�

SyntaxError: Invalid or unexpected token
    at Object.compileFunction (node:vm:352:18)
    at wrapSafe (node:internal/modules/cjs/loader:1033:15)
    at Module._compile (node:internal/modules/cjs/loader:1069:27)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47
    ```

I believe it may be something related to the node version (I'm currently using 16.16.0), turbo's window exe has an issue with it, now I need to find what node version this stops breaking

@darklight9811 As a workaround, can you pin the version of turbo to the version that was working for you?
And then we can investigate what is happening with the later version. Can you also confirm which versions are working vs giving you an error?

@gsoltis
actually I can't get any version of turbo to work. The issue seems on the turbo.exe file, node version 14.20.0 makes all those versions work (will test more node versions to see where it starts to break).

I suspect what is happening here is the following:

During post-install, turbo replaces the binary at bin/turbo with the native binary.
The restored version from the cache has been mutated to have that binary.
The version check here (from the post-install script) is now trying to run against the binary.

How to get back to a working state, two options:
A. Remove your Yarn cache (yarn cache clean). Remove your local node_modules. Remove any other node_modules cache sources (e.g. CI). Rerun install.
B. Use yarn install --ignore-scripts to ensure that turbo's post-install script is not run.

@nathanhammond actually already ran with a clean cache because I was toggling between node versions (with nvm, that makes me install yarn everytime, I'm not certain it clears its cache, so I will double check that).
But it runs on certain node versions, so that may be a combination of OS, node, yarn and turbo (and some other thing?)
And I can't ignore scripts because turbo doesn't work without postinstall.

@darklight9811 Sorry to hear that turbo didn't work out for you. If you end up finding out what dependency is causing an issue, I would appreciate it if you could let us know what piece of information would have been useful for turbo to surface to you so that you could debug more easily.

For me, the virus scanner (avira) detected a malware in turbo-windows-64/bin/turbo.exe, maybe that is the problem.


[Bug]: Tooltip for login policy "Username and Password" is wrong - passwordless login only not possible

Preflight Checklist

[x] I could not find a solution in the documentation, the existing issues or discussions
[ ] I have joined the ZITADEL chat

Environment
ZITADEL Cloud
Version
No response
Database
None
Database Version
No response
Describe the problem caused by this bug

The tooltip states that when disabling "Username and Password allowed" login with passwordless authentication is possible. In fact that's not the case at the moment, you can only login with an external IdP.
To reproduce

Configure Passwordless
Disable Username and Password allowed

--> you're locked out of your account
Screenshots
No response
Expected behavior
The description should reflect the actual implementation.
Operating System
No response
Relevant Configuration
No response
Additional Context
No response

@livio-a @muhlemmer @peintnermax from what i remember, the username password does only disable username password, and therefore allow external login, but i think passkey is not included here?
Please let me know if thats correct, in that case i can change the label so it is stated correct for the moment.
Or is that something that also changes from the current to the new login?

Passwordless login is available under the condition that it is allowed in the loginsettings. Same for IDPs where we use the setting External Login Allowed. The tooltip should state: "Allows username and password authentication. Check your other settings to ensure users are not locked out" to avoid confusion.
The new login will adapt the actual state of the login settings.


Enable nullable: System.Management.Automation.Language.TypeName

Follow-up to #14088, #14181.

@powercode Can you review?


Full scan results are not getting saved in output file.

Whenever we scan a custom list , this tool only saves cloudflare host only.
Please fix this so we can get full scan results saved as ip:host:status:server

https://github.com/aztecrabbit/bugscanner-go/issues/10#issuecomment-2159742270


Add support for user namespaces in Kubernetes discovery

Fixes 1951 (https://github.com/prometheus/prometheus/issues/1951)

:-1: Namespaces are already supported, by default services from all namespaces will be scraped. See my comment in #1951 for more information.

I don't think makes sense to add & it's not in the proposed SD updates that @fabxc is doing either.

Implemented in #2642.


RPM Clarification

Does RPM limit mean that there can be up to 800 concurrent users talking with the bot at the same time?
If yes, is there any way to notify users that they have to wait for a minute, because bot is very busy at the moment?
Does MS have plans to increase this limit or better strategy would be to create many different bots on different topics?
[Enter feedback here]

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

ID: 07c96368-89fa-6451-b091-d59ed754cd75
Version Independent ID: 140f2cc2-70d0-334a-8707-a1cde39fd75b
Content: Rate limits for chatbots - Power Virtual Agents
Content Source: power-virtual-agents/requirements-quotas.md
Service: power-virtual-agents
GitHub Login: @iaanw
Microsoft Alias: iawilt

Thanks for your feedback! The best place for product requests or troubleshooting is the Power Virtual Agents forum at https://powerusers.microsoft.com/t5/Forums/ct-p/pva_forums - if you repost your questions there an engineer, PM, or someone with a similar issue/solution should be able to help you.


Monokai Dimmed theme: LESS syntax highlighting colors very different in v1.86.0

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.86.0
OS Version: macOS 14.2.1

Steps to Reproduce:

Select the Monokai Dimmed theme
Open a .less file
Note that the syntax higlighting colors are very different to the previous release

This is what the less syntax highlighting looked like in v1.85.2 with the Monokai Dimmed theme enabled:

And this is what it looks like in 1.86.0:

The main problem is that property names are now the same color as property values that are keywords - e.g. hidden, flex & auto - but it's also a bit annoying that LESS variables are no longer a uniform color.
I've checked a few other color themes and they don't seem to have this problem.
This is a bit of a guess but maybe Monokai Dimmed needs to be updated following the changes introduced in #200043 ?

Yes, agree, this needs an update here: https://github.com/microsoft/vscode/blob/7c16d665f9be688f6e7528b3c1a066a09b86e11f/extensions/theme-monokai-dimmed/themes/dimmed-monokai-color-theme.json#L377


updated grammar and spelling for README

Just updated some grammar for the readme to make it easier to comprehend.

Thanks!


Fixing model binding, fixing createModel function

closes #70, #69

Coverage remained the same at 100.0% when pulling a9db81d00af0a3c37b2cd0ff91f81df5a8c9994e on ktutnik:master into 795607cc00fb25ab2218db3bf7518d3e2e1f52e1 on kambojajs:master.


No protocol tests for @uniqueItems

The repository used to contain protocol tests for set shapes e.g.:

RestJsonMalformedSetDuplicateItems
RestJsonMalformedSetNullItem
RestJsonMalformedSetDuplicateBlobs

In a7a16dfd13426f712934108f46cce3a3bb9d61b4, sets were deprecated in favor of lists with @uniqueItems, and the name of these tests changed.
In July, in 1b5737a873033a101066b3d92b9e11d4ed3587c7, the tests were removed cc @gosar:

For now, removing these tests to unblock smithy 1.22.0 release.

Re-adding the tests would be nice to ensure smithy-rs is compliant (e.g. same validation error message).
As an aside, shouldn't we also add protocol tests for set shapes, not only list shapes with @uniqueItems? While deprecated in IDL v2, users can still use them. In addition, don't we still have to support IDL v1? In which case we need to ensure we return SerializationExceptions if the model was an IDL v1 model, and ValidationException in case it was an IDL v2 (?). Alternatively, since in smithy-rs we've never supported @uniqueItems or the semantics of set shapes:

we could abort if we detect a set shape in an IDL v1 model when running the server SDK generator, and instruct the user to update their model.
we could apply a model transformation to convert set shapes to list shapes with @uniqueItems, and print a warning saying we will be returning ValidationException.

Guidance is appreciated on this.

Yeah, let's add uniqueItems tests.
I don't think we need set tests though. Sets were completely removed in IDL v2. The Rust code generator should treat sets from IDL v1 exactly like a list + uniqueItems, and that's easy to do since a uniqueItems trait is added to every IDL v1 set shape automatically (we document that in the 1.0 spec too).

Validation protocol tests for @uniqueItems were added in https://github.com/awslabs/smithy/pull/1622.


chore: session max age note

I've added a note and example since it is not obvious that maxAge of the session is not the same as maxAge of the cookie

Hi @patrick-hofmann
Actually we use maxAge to set the cookie expiration, see https://github.com/unjs/h3/blob/7324eeec854eecc37422074ef9f2aec8a5e4a816/src/utils/session.ts#L141
As the session is stored in the cookie, it expires at the same time the cookie expires.

Hi @atinux
you are right, indeed session and cookie lifetime are equal in the current example. Nevertheless this documentation PR also shows why I've created the two PRs
#255 - cookies shall live as short as possible and lifetime should extend while in usage (this could also be achived with a kind of session rotation)
and
#257 - the session lifetime shall end immediately when the user is logged out.
Best regards!


bug: offline ollama/llama3.2 doesn't get any files. Only gets promt.

Describe the bug
I have plugged in llama3.2 on Ollama with following setup as described
        ollama = {
          __inherited_from = "openai",
          api_key_name = "",
          endpoint = "http://<IP_ADDRESS>:11434/v1",
          model = "llama3.2",
        },

It seems it didn't pick up files in an ask mode:
> explain me this code

I'd be happy to help explain the code. However, you haven't provided any code yet. Please go ahead and share the code with me, and I'll do my best to break it down and explain what each part does.

**Generation complete!** Please review the code suggestions above.

Files are shown in Selected files. Tried different things: f.e. adding additional files.
Btw all other providers (ChatGPT, Claude and Perplexity) works great.
Installation method
return {
  {
    "yetone/avante.nvim",
    event = "VeryLazy",
    lazy = false,
    version = false, -- set this if you want to always pull the latest change
    opts = {
      -- provider = "openai", -- Recommend using Claude
      provider = "ollama",
      openai = {
        endpoint = "https://api.openai.com/v1",
        model = "chatgpt-4o-latest",
        timeout = 30000, -- Timeout in milliseconds
        temperature = 0,
        max_tokens = 4096,
      },
      claude = {
        endpoint = "https://api.anthropic.com",
        model = "claude-3-5-sonnet-20241022",
        timeout = 30000, -- Timeout in milliseconds
        temperature = 0,
        max_tokens = 8000,
      },
      vendors = {
        perplexity = {
          __inherited_from = "openai",
          api_key_name = "PERPLEXITY_API_KEY",
          endpoint = "https://api.perplexity.ai",
          model = "llama-3.1-sonar-large-128k-online",
        },
        ollama = {
          __inherited_from = "openai",
          api_key_name = "",
          endpoint = "http://<IP_ADDRESS>:11434/v1",
          model = "llama3.2",
        },
      },
    },
    init = function(_, opts)
      local config_path = vim.fn.stdpath("config")

      local file = io.open(config_path .. "/tools/anthropickey.txt", "r")
      if file then
        local key = file:read("*all"):gsub("%s+", "") -- Remove whitespace
        file:close()
        -- Set environment variable
        vim.env.ANTHROPIC_API_KEY = key
        print("OpenApiKey" .. key)
      end

      file = io.open(config_path .. "/tools/perplexitykey.txt", "r")
      if file then
        local key = file:read("*all"):gsub("%s+", "") -- Remove whitespace
        file:close()
        -- Set environment variable
        vim.env.PERPLEXITY_API_KEY = key
        print("OpenApiKey" .. key)
      end

      local wk = require("which-key")
      wk.add({ "<leader>a", group = "AI" })
    end,
    build = "powershell -ExecutionPolicy Bypass -File Build.ps1 -BuildFromSource false", -- for windows
    dependencies = {
      "stevearc/dressing.nvim",
      "nvim-lua/plenary.nvim",
      "MunifTanjim/nui.nvim",
      --- The below dependencies are optional,
      "hrsh7th/nvim-cmp", -- autocompletion for avante commands and mentions
      "nvim-tree/nvim-web-devicons", -- or echasnovski/mini.icons
      -- "zbirenbaum/copilot.lua", -- for providers='copilot'
      {
        -- support for image pasting
        "HakonHarnes/img-clip.nvim",
        event = "VeryLazy",
        opts = {
          -- recommended settings
          default = {
            embed_image_as_base64 = false,
            prompt_for_file_name = false,
            drag_and_drop = {
              insert_mode = true,
            },
            -- required for Windows users
            use_absolute_path = true,
          },
        },
      },
      {
        -- Make sure to set this up properly if you have lazy=true
        "MeanderingProgrammer/render-markdown.nvim",
        opts = {
          file_types = { "markdown", "Avante" },
        },
        ft = { "markdown", "Avante" },
      },
    },
  },
}

Environment
NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1713484068
Windows 11

I think this is related with ollama's OpenAI-compatible API
By default, ollama run models with 2k context length and there is no error or warning when prompts exceeds the length. (max_tokens parameter does not change context length)
You can solve this issue in 2 ways

make new model with simple Modelfile (ollama docs)
implement ollama API call (avante docs)


need assistance with custom PACE code on my site

The freeware script I'm running uses this code to submit data after everything is filled out:
<input name="submit_step2" value="{lang next}" type="submit" class="button2">

But PACE doesn't work for this and doesn't show up until an actual page change.  How can I get it to work?  The above "request" takes about 10-15 seconds hence why I want to show a loading bar.
Thanks!

is it ajax form? like using jquery-forum plugin.
if yes then use Pace restart(); or Pace start() :smile:

On submit does the form make a POST request?
Try putting these settings before you include the pace.js file.

@rajlaksh It doesn't use any AJAX, @Friss it didn't work, I tried adding 'SUBMIT' to it and we'll see! :)

@Friss On submit does the form make a POST request?
I don' t think so...


[ADD] add RequestID

We're currently processing your upload.  This comment will be updated when the results are available.


"Unhandled exception in concurrent task" repeats in log after CLN 24.05 upgrade

After upgrading to CLN 24.05, running clboss v0.13.1, I'm seeing the following entries in the CLN logs repeating exactly every 10 minutes:
Jun 06 09:04:47  lightningd[510666]: Unhandled exception in concurrent task!
Jun 06 09:04:47  lightningd[510666]: Incorrect type.
Jun 06 09:04:47  lightningd[510666]: ...main loop continuing...

Set the CLN log-level=io hoping to get more information, but that didn't help. @ksedgwic pointed to the following on Discord:
https://github.com/ZmnSCPxj/clboss/blob/df51d5486b05acbeca16cb9e42d18fa082e6079a/Ev/concurrent.cpp#L19-L29
I'm happy to provide more information if provided with tips to extract more data.

The 10 minutes suggests it's one of:
ChannelFinderByPopularity.cpp:181:		bus.subscribe< Msg::Timer10Minutes
ListfundsAnnouncer.cpp:24:	bus.subscribe< Msg::Timer10Minutes
ListpeersAnnouncer.cpp:51:	bus.subscribe<Msg::Timer10Minutes
OnchainFeeMonitor.cpp:342:		bus.subscribe<Msg::Timer10Minutes>([this](Msg::Timer10Minutes const&) {
SelfUptimeMonitor.cpp:71:		bus.subscribe<Msg::Timer10Minutes
SendpayResultMonitor.cpp:130:		bus.subscribe<Msg::Timer10Minutes
SwapManager.cpp:71:		bus.subscribe<Msg::Timer10Minutes
TimerTwiceDailyAnnouncer.cpp:34:		bus.subscribe<Msg::Timer10Minutes
PeerComplaintsDesk/Main.cpp:143:		bus.subscribe<Msg::Timer10Minutes

There's a good chance that https://github.com/ZmnSCPxj/clboss/pull/198 will fix this, it fixes a large number of code locations which were using a now deprecated API version ...
How risk adverse are you with this node?  The above fix and some others are in master.  I've been happily running on several testnet instances w/o problem.

@ksedgwic It's a production node, with some value, but I like to live on the edge every now and then. You suggest I consider running the master branch directly, then?

I am running clnboss on my nodes without any problem, but I think I am running the master with the https://github.com/ZmnSCPxj/clboss/pull/198 included

You suggest I consider running the master branch directly, then?

Why you should not @aaroncarlucci ? for cln is always good run the master

@ksedgwic @vincenzopalazzo I've joined with you in the ranks of frontline warriors running master. So far, the startup BROKEN log entry that I pasted Ken in Discord has disappeared, and after 20 minutes uptime, no log messages as reported in the original issue description.
I'll check in on it  tomorrow AM to be sure, but things look encouraging so far. Not sure if this is the behavior for other users after upgrading to CLN 24.05, but IMHO, it might be time to consider another point release.
Thanks for the support!

No issues overnight. I'm happy to close this. Thanks again.


oauth 1 not working with httpx

i am currently making oauth 1 signed requests using the requests-oauthlib library.
from requests_oauthlib import OAuth1Session

self.session = OAuth1Session(
    OAUTH_CONSUMER_KEY, OAUTH_CONSUMER_SECRET,
    oauth_token, oauth_token_secret,
    signature_type='auth_header', realm='http://api.twitter.com'
)
self.session.headers = self.default_headers
self.session.verify = self.verify
self.session.proxies.update(self.proxies)

Using this i can successfully make oauth 1 requests. But I need http 2 and would like to use async io. Thats why i am trying to switch to httpx with authlib.
from authlib.integrations.httpx_client import OAuth1Client

self.session = OAuth1Client(
    OAUTH_CONSUMER_KEY, OAUTH_CONSUMER_SECRET,
    oauth_token, oauth_token_secret,
    http2=True,
    headers=self.default_headers,
    proxies=self.proxies,
    verify=self.context
)
self.session.auth.realm = 'http://api.twitter.com'

With requests-oauthlib i can make signed requests without a problem. But when i try to do the same with httpx i get this response:
{
	"errors": [{
		"code": 32,
		"message": "Could not authenticate you."
	}]
}

If i take a look with a web debugger i can verify that the authentication header got all the right keys but somehow the request fails while using httpx. Does anyone have any suggestions on how to resolve this issue or how to debug this properly? Thanks in advance :)

I'm not sure if you are using the library correct. Here is the documentation:

https://docs.authlib.org/en/latest/client/oauth1.html
https://docs.authlib.org/en/latest/client/httpx.html

We have a demo with starlette framework, which is using the httpx oauth client. It works well: https://github.com/authlib/demo-oauth-client/tree/master/starlette-twitter-login
I can not guess what is wrong with your code if you can't provide a minimal reproducible demo.

My guess is that you need to pass realm in OAuth1Client or OAuth1Client.fetch_request_token.


How to handle branches for LDAS?

This is mainly a policy thread for @tclune to comment on, but I need his advice/expertise/opinion.
@weiyuan-jiang and @JustinPerket would like a branch and tag of ESMA_env where the MPI stack is Open MPI because that gives them better performance. This is fine, but the question I have is: What should we call this branch and tag?
For the branch, I'm thinking something like ifort-openmpi might be best for the branch as it seems to define the reason for it (compiler-MPI)? But maybe this is too much/not enough. It's not like it needs to be dev/ldas since it's a change in MPI stack more than anything LDAS specific.
As for the tag, hmm. I'm not sure. v1.3.0 is what we have for master currently, so would this be v1.3.0+openmpi3.1.1 or something like that? I'm not sure what the correct semver way to refer to something that is essentially identical to the original save for a change in an MPI stack? I don't want to call it v1.3.1 as that would mean it's newer and frankly, I don't think it is. And I'd prefer not to put LDAS, say, in the tag.
Advice please @tclune.

Also note that it's possible we'd need something long-lived as if we go to Intel 18.0.5 well then I'd want to provide an Intel 18.0.5 Open MPI environment to LDAS with ifort-openmpi. So should I instead do something like baselib-compiler-mpi-python as the branch name to be completist?
5.1.7-ifort18.0.3-openmpi3.1.1-sivopyd

??

It is better for us to have a branch without GEOSldas's name in it, so it can be used by other fixtures and GEOSldas group don't have to maintain it.


anathematical, casted

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[a,c]

/trunk merge


Change log level for external-secrets and calico

External-secrets service and calico service produce a lot of logs message, we need to change log-level for these services.

For Calico: https://github.com/maddevsio/aws-eks-base/blob/ad56666308fe15419f2e5f2d8812c68fe0c692d3/terraform/layer2-k8s/templates/calico-values.yaml#L27
For external-secrets: https://github.com/maddevsio/aws-eks-base/blob/ad56666308fe15419f2e5f2d8812c68fe0c692d3/terraform/layer2-k8s/templates/external-secrets-values.yaml#L6


params are doubled

At least POST requests seem to double their params in a way like that:
params = { params, model_name => { params } }

Bndy debugged, could be at QueryInterface::Client::API.request
https://github.com/rs-dev/query-interface-client/blob/master/lib/query-interface-client/api.rb#L28

thank you wrap_parameters.rb, not a query-interface-issue

Thanks for investigating, @armins.


[llvm] adding patch to fix the bug of clang_getCursorKind

Is your feature request related to a problem? Please describe.
Please refer to this llvm issue.
The patch is available from this post.
Proposed solution
The solution is provided above.
Describe alternatives you've considered
No response
Additional context
No response

Actually I believe this IS a general bug of clang itself, which perhaps isn't really suitable to fix it here. But as this problem has been issued decade ago, simply adding a patch here could save quite of time if user decide to fix it (like via overlay port, which led to rebuilding).

Fixed by https://github.com/llvm/llvm-project/commit/7091ca1ae3a87479b6febdf1c3a324d707c633d9.


Launch breaks first round if not owner

Whenever running 'launch' at the start of a game when you're not the host, it will bug the lever

Added check wether the player is the host or if it's a player that has joined more or equal than 1 day ago.
This variable gets reset upon rejoining.
-Worked in my testing-

When testing with friends, can never launch

Tested the following with 3 accounts on a lan server:

tried launch on #1 --> Didn't work --> 0 days on
launched with #0 --> worked
launched back into space with #1 --> worked, 1+ day
launched back onto moon with #2 --> worked 1+ day
launched back into space #1 --> worked, 1+ day
left on #2
tried launching on #1 --> worked 1+ day
restarted game with host (could not join during game, even when morecompany was installed?)
launched with #1,#2 --> did not work, 0 days

So it should be fixed and the counter resets if you leave as far as I am concerned, issue will be reopened if this is not the case. I'd like this to be compatible with morecompany or another mod like this


Artboard size

So, there is no artboard size specified that will generate the icons of the correct size. I tested for android, and the correct artboard size is 96 x 96 px. It should be specified somewhere in the README

I'm not sure what you are asking here. What icons are you talking about? The baseline used is xhdpi, so your xhdpi image will be matched up with your artboard size.

Oh, I see, my mistake =)


Patch for #2813

@alexanderdean thanks for fixing #2813
If I use the default configuration file for the EMR runner provided by snowplow:
...
buckets:
      assets: s3://snowplow-hosted-assets
...

...the S3 locations are not generated as expected. The reason for this is, that config[:aws][:s3][:buckets][:assets] seems to always to have a trailing slash included and so the string comparison fails in your new created function.
Code to clearify:
logger.debug "custom_assets_bucket CHECK"
logger.debug config[:aws][:s3][:buckets][:assets]
logger.debug STANDARD_HOSTED_ASSETS
logger.debug self.class.get_hosted_assets_bucket(config[:aws][:s3][:buckets][:assets], config[:aws][:emr][:region])
logger.debug self.class.get_hosted_assets_bucket(STANDARD_HOSTED_ASSETS, config[:aws][:emr][:region])

Output
D, [2016-07-28T11:34:49.487000 #12410] DEBUG -- : custom_assets_bucket CHECK
D, [2016-07-28T11:34:49.490000 #12410] DEBUG -- : s3://snowplow-hosted-assets/
D, [2016-07-28T11:34:49.491000 #12410] DEBUG -- : s3://snowplow-hosted-assets
D, [2016-07-28T11:34:49.494000 #12410] DEBUG -- : s3://snowplow-hosted-assets/
D, [2016-07-28T11:34:49.502000 #12410] DEBUG -- : s3://snowplow-hosted-assets-eu-central-1

Output patched version
D, [2016-07-28T12:38:09.485000 #12814] DEBUG -- : custom_assets_bucket CHECK
D, [2016-07-28T12:38:09.490000 #12814] DEBUG -- : s3://snowplow-hosted-assets/
D, [2016-07-28T12:38:09.494000 #12814] DEBUG -- : s3://snowplow-hosted-assets
D, [2016-07-28T12:38:09.498000 #12814] DEBUG -- : s3://snowplow-hosted-assets-eu-central-1/
D, [2016-07-28T12:38:09.502000 #12814] DEBUG -- : s3://snowplow-hosted-assets-eu-central-1/

Without this fix, the EMR step Elasticity Scalding Step: Enrich Raw Events fails at the step
2016-07-28T10:00:14.395Z INFO Ensure step 2 jar file s3://snowplow-hosted-assets/3-enrich/scala-hadoop-enrich/snowplow-hadoop-enrich-1.7.0.jar
This is basically the same problem like fetching the boostrapping files from another region.

Thanks @philsch ! Can you sign our CLA?

@alexanderdean done

Confirmed! Thanks

Thanks @philsch - your code will be fixed up into the relevant commit (it's now in the branch), closing...


Next.js Static Generation Issue with Layout Cookies and Dynamic Routes

Description
When a higher-level layout uses cookies and a nested dynamic route page ([locale]/test/[code]/page.tsx) with an empty generateStaticParams() is accessed, a DYNAMIC_SERVER_USAGE error occurs. Interestingly, accessing [locale]/page.tsx does not trigger this error.
Detailed Observations
Accessing cookies in the top-level layout (src/app/layout.tsx)
Scenario 1: Page with Empty generateStaticParams()

Error: DYNAMIC_SERVER_USAGE
Occurs when accessing src/app/[locale]/test/[code]/page.tsx

Scenario 2: Root Page

No error
Accessing src/[locale]/page.tsx works normally

Attempted Solutions

Returning a non-empty array in generateStaticParams()
Using export const dynamic = 'force-static' - Enables successful static build

Build Log Details
When running pnpm build -d, the build log shows:

"Static generation failed due to dynamic usage on /en, reason: cookies", ...
Applies to all static pages

Questions

What causes the DYNAMIC_SERVER_USAGE error in nested dynamic routes?
Why does force-static resolve the build issue?
Why do build logs indicate dynamic usage due to cookies even after using force-static?

Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
https://github.com/LoganBaek97/next-intl/tree/main/examples/example-app-router
Reproduction description
Steps to reproduce:

Open reproduction
Clone project
See src/app/[locale]/test/[code]/page.tsx, src/app/[locale].tsx and src/app/layout.tsx (using cookies)

Expected behaviour

Successful static generation for all pages
No dynamic usage warnings when using layout-level cookies

Hmm, for me it seems to work in your repro:

Strangely even if I move cookies() to app/[locale]/layout.tsx. Not sure if there's a bug here in Next.js.
If I remove generateStaticParams in app/[locale]/layout.tsx, then the result looks more like what I'd expect:

This is somewhat related: https://github.com/vercel/next.js/discussions/64616. I hope that rootParams brings some improvements here, at least the case of a static layout + dynamic child is covered in the tests in the PR.

@amannn
During the build log, the page appears to be generated statically. However, when running pnpm build -d (to view detailed build logs), an error message is displayed: "Static generation failed due to dynamic usage on /en (and other pages too) , reason: cookies". By rendering new Date().toISOString() on the pages where static generation failed, we can confirm that the static build is indeed unsuccessful (the time changes with each page refresh and is not fixed). I expected this might be a Next.js issue and hope it can be resolved quickly. Thank you.

Error occurred prerendering page "/en". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Route /[locale] with dynamic = "error" couldn't be rendered statically because it used headers. See more info here: https://nextjs.org/docs/app/building-your-application/rendering/static-and-dynamic#dynamic-rendering


feat: initial new enclave manager

Description:
This PR contains the beginnings of the new enclave manager ui. Specifically it adds a new project in enclave-manager/web. Notable inclusions:

Continuing to use Chakra as a component libary, the KurtosisThemeProvider injects components themed based on the mocks.
The enclave manager sdk cllient is refactored into authenticated (remote) and local versions, and provided to react components with useKurtosisClient by the KurtosisClientProvider. This provider blocks loading the application (with a spinner) until it's configured the client to use.
react router is used to compose the application.
react-table is used to create a (reusable) table for showing the enclaves list.

Demo (WIP)
https://github.com/kurtosis-tech/kurtosis/assets/4419574/c026a1d9-313d-4e73-944a-2814399e039a
Is this change user facing?
NO (this is not yet part of the build/deploy process)
References (if applicable):
This PR is rebased on top of https://github.com/kurtosis-tech/kurtosis/pull/1595 which should be merged first.

One more thing: can you add a build script (put it under scripts/build.sh to be consistent with our normal practice) and perhaps add a section the readme on what needs to built to actually run this project (like the protobuf definitions). Or better yet, just add it to the build script so it's always generated.

Thanks for the extra comments and chatting last night @adschwartz . I've updated this PR with all of the feedback we discussed to change now.
I'm going to go through the design changes now in a fresh branch from this one.


application-revision deployments fail when lots of instances are deployed simultaneously

Version: main
UI: dev-d4bedf4
Commit ID: 8f7ced5963979c432a3953e24c49434c916b5853
Env: Ubuntu 22.04 amd64, aws EC2 c5.xlarge, 4C8G
Test Steps:

Setup seal by docker-compose.

version: '3.6'
services:
  seal:
    image: "sealio/seal-server:main"
    restart: always
    privileged: true
    container_name: seal
    command:
      - "seal"
      - "--log-debug"
      - "--log-verbosity=4"
      - "--conn-burst=250"
      - "--conn-qps=200"
      - "--enable-authn=true"
    environment:
      - SERVER_DATA_SOURCE_DATA_ENCRYPTION=xxx
      - K3S_RESOLV_CONF=
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - 'sealapp:/var/run/seal'
volumes:
  sealapp: {}

Deploy 80 instances at the same time.


subComponent hijacks internal onClick of buttons

Using the Sub Component code demo of the component, add a button with an onClick and an appropriate handler. In this case, its just a simple alert.
https://react-table.js.org/#/story/sub-components
When the row item is expanded, the onClick of the button is fired and the onClick fails on the button when clicked on.
import React from "react";
import { render } from "react-dom";
import { makeData, Logo, Tips } from "./Utils";

// Import React Table
import ReactTable from "react-table";
import "react-table/react-table.css";

const columns = [
  {
    Header: "Name",
    columns: [
      {
        Header: "First Name",
        accessor: "firstName"
      },
      {
        Header: "Last Name",
        id: "lastName",
        accessor: d => d.lastName
      }
    ]
  },
  {
    Header: "Info",
    columns: [
      {
        Header: "Age",
        accessor: "age"
      },
      {
        Header: "Status",
        accessor: "status"
      }
    ]
  },
  {
    Header: "Stats",
    columns: [
      {
        Header: "Visits",
        accessor: "visits"
      }
    ]
  }
];

class App extends React.Component {
  constructor() {
    super();
    this.state = {
      data: makeData()
    };
  }
  onClicker(){
    alert("click error");
  }
  render() {
    const { data } = this.state;
    return (

        <ReactTable
          data={data}
          columns={columns}
          defaultPageSize={10}
          className="-striped -highlight"
          SubComponent={row => {
            return (

                  You can put any component you want here, even another React
                  Table!

                <button onClick={this.onClicker()}></button>

                <ReactTable
                  data={data}
                  columns={columns}
                  defaultPageSize={3}
                  showPagination={false}
                  SubComponent={row => {
                    return (

                        Another Sub Component!

                    );
                  }}
                />

            );
          }}
        />

        <Tips />
        <Logo />

    );
  }
}

render(<App />, document.getElementById("root"));

This feature/issue has been tagged as one that will likely be fixed or improved in the next major release of React-Table. This release is expected to be completed in the next 6 - 8 months. Please see #1143 for more detail. If you believe this feature can be easily fixed, we invite you to fork the project, attempt the fix, and use it until the latest version is available. If the fix is simple enough, we will also consider it as a PR to the current version.


REF: Split dottable-dict logic into separate class.

Added to this PR: Log messages used to refer to mongo IDs. Now they refer to our globally unique uid.

The intention of this PR as changes (see updated title).


rancher/agent:latest is not rancher/agent:v1.2.10

Rancher versions:
rancher/server: v1.6.17
rancher/agent: v1.2.8(latest, doesn't work) v1.2.10(works)
Docker version: (docker version,docker info preferred)
Docker version 18.03.0-ce, build 0520e24, also tested on 17.12.1-ce.
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
$ cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1745.0.0
VERSION_ID=1745.0.0
BUILD_ID=2018-04-11-2324
PRETTY_NAME="Container Linux by CoreOS 1745.0.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

$ uname -r
4.15.15-coreos

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
GCE
Steps to Reproduce:
$ docker pull rancher/agent:latest
latest: Pulling from rancher/agent
Digest: sha256:e5a9cd17ceb29eab2749428a6ed49a85f3457d080d76ea9ec3c6d943e1cbf313
Status: Image is up to date for rancher/agent:latest

$ docker pull rancher/agent:v1.2.10
v1.2.10: Pulling from rancher/agent
Digest: sha256:5618f36cdb6c6fe25baa3e72977f3a226d43ffd1d74dda6a8860e32b73a1e171
Status: Image is up to date for rancher/agent:v1.2.10

$docker pull rancher/agent:v1.2.9
v1.2.9: Pulling from rancher/agent
Digest: sha256:c21255ac4d94ffbc7b523f870f2aea5189b68fa3d642800adb4774aab4748e66
Status: Image is up to date for rancher/agent:v1.2.9

$ docker pull rancher/agent:v1.2.8
v1.2.8: Pulling from rancher/agent
Digest: sha256:e5a9cd17ceb29eab2749428a6ed49a85f3457d080d76ea9ec3c6d943e1cbf313
Status: Downloaded newer image for rancher/agent:v1.2.8

So, as you can see rancher/agent:latest is actually rancher/agent:v1.2.8, and since rancher/agent:v1.2.8 doesn't boot on Docker 17.12.1-ce or Docker 18.03.0-ce the agent won't boot unless I specify the version manually.
Results:
Found container ID: 415a4528bef4bff2abcefd8d8fbdfe82b481ee4bac23feee5428e27d3c75806f
Checking root: /host/run/runc
Checking root: /host/var/run/runc
Checking root: /host/run/docker/execdriver/native
Checking root: /host/var/run/docker/execdriver/native
time="2018-04-09T19:57:25Z" level=fatal msg="Failed to find state.json"

We don't recommned ever using the latest tag for agent as each Rancher server is specifically compatible with a specific version of Rancher agent. Relying on latest can get you into situations where the server will not work with agent.
WIth that being said, I've updated the latest tag for rancher agent.


Modularize test dependencies, build for 2.13.0-RC1

Drops some test dependencies so this project doesn't have to wait on those, and those might someday depend on this.
Moves tests into cross-built modules so libraries can be tested where available.

main tests are tested on all crossbuilds with artisanally handcrafted lazy monad
cats syntax is tested in own module against all Scala versions that cats currently supports
pcplod is dropped in 2.13, where no longer supported

Adds build for 2.13.0-RC1

One 2.13.0-RC1 test is failing:
[info] - emits no map(_ => ()) if prev. operation resulted in Unit *** FAILED ***
[info]   com.olegpy.bm4.MapCalled:
[info]   at com.olegpy.bm4.MapCheck.map(TestNoMap.scala:28)
[info]   at com.olegpy.bm4.TestNoMap.$anonfun$new$4(TestNoMap.scala:53)
[info]   at com.olegpy.bm4.TestNoMap.$anonfun$new$4$adapted(TestNoMap.scala:52)
[info]   at com.olegpy.bm4.MapCheck.flatMap(TestNoMap.scala:29)
[info]   at com.olegpy.bm4.TestNoMap.$anonfun$new$3(TestNoMap.scala:52)

The 0.3.0-M4 tag doesn't build on 2.13 due to the dependencies, so I couldn't easily test whether it worked previously or whether my mini cats clone is to blame.

In 2.12.8, the tree of the mapped unit is:
Function(List(ValDef(Modifiers(PARAM), termNames.WILDCARD, TypeTree(), EmptyTree)), Literal(Constant(())))

In 2.13.0-RC1, it is:
Function(List(ValDef(Modifiers(PARAM | SYNTHETIC), TermName("x$1"), TypeTree(), EmptyTree)), Match(Typed(Ident(TermName("x$1")), TypeTree().setOriginal(Annotated(Apply(Select(New(Select(Ident(scala), scala.unchecked)), termNames.CONSTRUCTOR), List()), Ident(TermName("x$1"))))), List(CaseDef(Ident(termNames.WILDCARD), EmptyTree, Literal(Constant(()))))))

@rossabaker thanks for your efforts on this. I'll try to get the updated version published for 2.13-RC1 in a day.


User is seen as idle when a long scroll or touch event begins

User is seen as idle when a long scroll or touch event begins. Proper solution would be to turn the debounced into throttled calls.

Using throttle instead of debounce.


NuttX TCP/IP handshake is failing

During the 3-way handshake the server refuses to accept NuttX connection:
1    0.000000000    <IP_ADDRESS>    <IP_ADDRESS>    DNS    72    Standard query 0x1ea4 A mqtt.tago.io
2    0.038974140    <IP_ADDRESS>    <IP_ADDRESS>    DNS    104    Standard query response 0x1ea4 A mqtt.tago.io A <IP_ADDRESS> A <IP_ADDRESS>
3    0.040266049    <IP_ADDRESS>    <IP_ADDRESS>    TCP    60    4098 → 1883 [SYN] Seq=0 Win=5488 Len=0 MSS=536
4    0.189729115    <IP_ADDRESS>    <IP_ADDRESS>    TCP    58    1883 → 4098 [SYN, ACK] Seq=0 Ack=0 Win=65535 Len=0 MSS=0
5    0.190332031    <IP_ADDRESS>    <IP_ADDRESS>    TCP    60    4098 → 1883 [ACK] Seq=1 Ack=1 Win=5488 Len=0

After many hours debugging and sniffing the network I figure out that the issue is happening because NuttX always starts with TCP sequence number equal 0. According to https://datatracker.ietf.org/doc/html/rfc1948 the initial value should be random:
   The initial sequence numbers are intended to be more or less random.
   More precisely, RFC 793 specifies that the 32-bit counter be
   incremented by 1 in the low-order position about every 4
   microseconds.  Instead, Berkeley-derived kernels increment it by a
   constant every second, and by another constant for each new
   connection.  Thus, if you open a connection to a machine, you know to
   a very high degree of confidence what sequence number it will use for
   its next connection.  And therein lies the attack.

@acassis https://github.com/apache/incubator-nuttx/pull/6154 randomize port number, you can apply the similar approach for the sequence number.

Perfect! Thank you @xiaoxiang781216 ! I will do it and submit a PR


Seems to work bad with my sensor.....

Dear Hugo,
I'm using a wemos d1 mini32 board and one sensor plate with a maximun resistance of 42540,9 ohms.
I modify your code with the following values:
  resistor_value: "9.78kOhm"

  # TODO: Handle case where resistance higher than max_resistance

 # Skip the value not in the range
  min_resistance: "1000"
  max_resistance: "42540.8"

  # Value of the resistance at which a significant change is considered
  # to occur
  rain_detection_threshold: "4000"

  # If the resistance increases by this value, the sensor is considered
  # to be dry
  dry_detection_threshold: "4000"

  # When booting, if the resistance is lower this value, assume sensor is wet
  wet_resistance_when_booting: "20000"

But the problem is when I put a water drop on the plate, the systems starts to read the Rain Detector Resistance with a speed less than 30000 mili seconds, then the plate is starting to rust....
It seems to detect that is raining and put the Rain detector raining in ON and Rain Detector drying in OFF, but continues to reading the resistance quickly. When the plate starts to dry and arrive to the max resistance, the sensors Rain detector raining continues in ON and Rain Detector drying continues in OFF:

Something is wrong in my configuration, but  I can't understand......
Any idea?.
Thanks in advance,

Solved, I forgot to include on_boot sentences......


Environment is a mess

Description

the build/ folder is committed so that the application is available upon push on heroku
for the convenience of development, the frontend and backend are hosted in different locations and communicate via CORS; for this to work, all occurrences offetch('/path', ...) need to be changed to fetch('http://<IP_ADDRESS>:5000/path', ...) during development and the other way around when deploying

Proposal

move package.json to top-level, so that we can use heroku's nodejs buildpack
in React, test if process.env.NODE_ENV !== "production" and modify the fetch location accordingly

building via heroku ps:exec doesn't persist after dyno refreshes.


flutter pub add version - doesn't add anything to pubspec.yaml

Running flutter pub add version doesn't add anything to pubspec.yaml.  Like adding any other package, an entry should automatically be made in pubspec.yaml.
Sure, the actual download of the version package completes (you can confirm this with flutter pub deps and seeing
|-- version 3.0.2

listed but it turns out that
  version: ^3.0.0

needs to be added manually to pubspec.yaml in order for imports to not have red lines under them in vscode etc.
Perhaps the name of the version package conflicts with the version keyword of the pubspec.yaml?


Make discover-files the only mode for sanitize repo.

After thorough thought, we think that the file-list command is not very useful and should be removed.
Instead it could be replaced with a "DONT sanitize these files" solution, in the future

Fixed as of #84


Why only selfsigned certificates

This article is missing the instructions for pki certificates. please fix.

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

ID: 8e95ba48-8d07-d390-d49b-801d70730bae
Version Independent ID: 047d2736-f14e-610c-7396-89d2eae0f9cc
Content: Create a certificate for package signing - MSIX
Content Source: msix-src/package/create-certificate-package-signing.md
Product: msix
GitHub Login: @dianmsft
Microsoft Alias: diahar

Check the Prerequisites section.  Your PKI administrator should know how to get you a code signing certificate that works.


ThriftClientConfig copy constructor

Since ThriftClientConfig is mutable, it's convenient to have a copy constructor for easily making a defensive copy.

No code should hold on to Airlift config objects, so I'm not sure why this is needed.


nixos/gitlab: Fix registry port

Fixes #350428
Things done
The option services.gitlab.registry.port was unused and the service always exposed on port 5000, I applied the option.

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

@ofborg eval

Oops I think I should have ping the package maintainers: @globin @krav @talyz @yayayayaka


Please kindly share either documentation or  the Java code sample for custom-ui

my Best Friends,
This is friendly reminder for Please kindly share either documentation or  the Java code sample for custom-ui same as following Kotlin Samples,
https://github.com/PierfrancescoSoffritti/android-youtube-player/tree/master/custom-ui/src/main/java/com/pierfrancescosoffritti/androidyoutubeplayer/core/customui

Thanks for consideration,
truly yours,
All the Best,
Kindest and Warmest Regards,
Sincerely,
Pooya M (Ryan)

We have documentation for the custom-ui module.


Error when processing more than 500 files in the directory

It is known that telegra.ph the article is able to handle a certain limit, the main problem is the error output from the side telegra.ph because the number of files is limited to five hundred files at a time.
The main solution that I have reached at the moment is to create a variable that is responsible for the number of files in each of the submerged directories.
As an alternative, I also considered adding a timeout using the time.sleep() function when processing the "try again later" error, but I do not yet know how to solve error 10054 (The remote host forcibly terminated the existing connection) after the time of the operation.

you can create a variable MAX_FILES_TO_PROCESS and add a couple of lines to def analyze_folder_content():
max_files_to_process = MAX_FILES_TO_PROCESS
__file_names = __file_names[:max_files_to_process]

It is known that telegra.ph the article is able to handle a certain limit, the main problem is the error output from the side telegra.ph because the number of files is limited to five hundred files at a time.

There is no such thing as files in an article, since the API does not support linking media to a page.  Each object is uploaded to the server independently and is in not referenced with other objects uploaded under the same token.  Actually you don’t have to create an article at all, but simply keep the files.  The limitation you are observing is a default shaping of the server load. It has a time-defined basis.  That is, you can download a certain number of objects in half an hour or a certain number of bytes in half an hour.
You can, of course, make the script in such a way that it works without interruption, but I was not able to find out the exact shaping conditions. In addition, they seem to be dynamic.


StartService does not return exception and waits for timeout before failing

When calling StartService("serviceName", "computer", "timeout") from a cake script the status of the service is set to StartPending. Then after a few seconds, starting the service fails, and the status of the service is back to Stopped. The script however, is still actively waiting for the service to reach the Running status, and will not report that starting the service has failed. Only when the timeout is triggered will the script be notified, but then with a timeout exception and not the exception from the start process. Is there a way around this problem, to let the script fail immediately when starting the service fails in addition to propagating the error to the script output?
Simplified script:
#addin "nuget:?package=Cake.Services&version=0.3.2"
#addin "nuget:?package=Cake.Powershell&version=0.4.2"

Task("Default").Does(() =>
{
   StartService("serviceName, "", 1800000);
});

RunTarget("Default");

Possibly by changing the underlying implementation of WaitForStatus from the external library "System.ServiceProcess". Happy to accept a PR for this.


Wrapper: Offline 1.4.0 not installing Flash Player

Bug Description
So, I uninstalled AFP from my PC, and the W:O installer is trying hard to get Flash Player back, but It never does. It says to restart the installer, so I do it, and now I'm stuck in an infinite installation loop.
To Reproduce
To reproduce the steps:

Install any version of W:O in the installer
If AFP isn't installed, continue the installation
It will write the Web Request Stream, then AFP never installs

Desktop (please complete the following information):

OS: Windows 10+
Version: Beta

https://user-images.githubusercontent.com/107278351/189249404-61f5e271-da35-473e-843c-95cbd5d8f3d0.mp4

I have the same problem

I downloaded the main 1.3.0 version manually from GitHub and used WinRAR to extract it...It just isn't the same

@GoTest334 do u know a solution to this problem