HADOOP-18590. Publish SBOM artifacts

Description of PR
This PR aims to publish SBOM artifacts.

https://cwiki.apache.org/confluence/display/COMDEV/SBOM

Here is an article to give some context.

https://www.activestate.com/blog/why-the-us-government-is-mandating-software-bill-of-materials-sbom/

Software Bill of Materials (SBOM) are additional artifacts containing the aggregate of all direct and transitive dependencies of a project. The US Government (based on NIST recommendations) currently accepts only the three most popular SBOM standards as valid, namely: CycloneDX, Software Identification (SWID) tag, Software Package Data Exchange® (SPDX).
This PR uses CycloneDX maven plugin, a lightweight software bill of materials (SBOM) standard designed for use in application security contexts and supply chain component analysis.
How was this patch tested?
Manually. For example, hadoop-auth-3.4.0-SNAPSHOT.jar will have hadoop-auth-3.4.0-SNAPSHOT-cyclonedx.xml and hadoop-auth-3.4.0-SNAPSHOT-cyclonedx.json SBOM files additionally.
$ mvn install -DskipTests
...

$ ls -l ~/.m2/repository/org/apache/hadoop/hadoop-auth/3.4.0-SNAPSHOT
total 960
-rw-r--r--  1 dongjoon  staff     373 Jan  6 12:47 _remote.repositories
-rw-r--r--  1 dongjoon  staff   84913 Jan  6 12:47 hadoop-auth-3.4.0-SNAPSHOT-cyclonedx.json
-rw-r--r--  1 dongjoon  staff   73722 Jan  6 12:47 hadoop-auth-3.4.0-SNAPSHOT-cyclonedx.xml
-rw-r--r--  1 dongjoon  staff   84457 Jan  6 12:47 hadoop-auth-3.4.0-SNAPSHOT-sources.jar
-rw-r--r--  1 dongjoon  staff  114087 Jan  6 12:47 hadoop-auth-3.4.0-SNAPSHOT-tests.jar
-rw-r--r--  1 dongjoon  staff  106678 Jan  6 12:47 hadoop-auth-3.4.0-SNAPSHOT.jar
-rw-r--r--  1 dongjoon  staff    8707 Jun  7  2022 hadoop-auth-3.4.0-SNAPSHOT.pom
-rw-r--r--  1 dongjoon  staff    1537 Jan  6 12:47 maven-metadata-local.xml

For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

cc @steveloughran , @sunchao , @snmvaughan

Thank you, @cnauroth !

Thank you, @sunchao !

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  4s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

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 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m  8s

trunk passed

+1 :green_heart:
compile
25m 35s

trunk passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
compile
21m 50s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
mvnsite
20m 12s

trunk passed

-1 :x:
javadoc
1m 26s
/branch-javadoc-root-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
root in trunk failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
7m 26s

trunk passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
shadedclient
140m 30s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
29m 57s

the patch passed

+1 :green_heart:
compile
24m 35s

the patch passed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04

+1 :green_heart:
javac
24m 35s

the patch passed

+1 :green_heart:
compile
21m 45s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
javac
21m 45s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
19m 55s

the patch passed

-1 :x:
javadoc
1m 13s
/patch-javadoc-root-jdkUbuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.txt
root in the patch failed with JDK Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04.

+1 :green_heart:
javadoc
8m 22s

the patch passed with JDK Private Build-1.8.0_352-8u352-ga-1~20.04-b08

+1 :green_heart:
shadedclient
56m 19s

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

_ Other Tests _

-1 :x:
unit
1112m  0s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
1m 41s

The patch does not generate ASF License warnings.

1390m 24s

Reason
Tests

Failed junit tests
hadoop.mapreduce.v2.app.TestRuntimeEstimators

hadoop.yarn.server.timelineservice.security.TestTimelineAuthFilterForV2

hadoop.hdfs.TestLeaseRecovery2

hadoop.tools.TestHdfsConfigFields

Subsystem
Report/Notes

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

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

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

uname
Linux d9dbdb3b1882 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 4f4b52f850ad2728a45948fbd35b7a2734b0fd82

Default Java
Private Build-1.8.0_352-8u352-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.17+8-post-Ubuntu-1ubuntu220.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_352-8u352-ga-1~20.04-b08

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

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

modules
C: . U: .

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

versions
git=2.25.1 maven=3.6.3

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

This message was automatically generated.

Apache Yetus(Jenkins) error: unit job seems to pass although it has a red-x mark.
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Apache Hadoop Main 3.4.0-SNAPSHOT:
[INFO]
[INFO] Apache Hadoop Main ................................. SUCCESS [  0.636 s]
[INFO] Apache Hadoop Build Tools .......................... SUCCESS [  2.289 s]
[INFO] Apache Hadoop Project POM .......................... SUCCESS [  0.747 s]
[INFO] Apache Hadoop Annotations .......................... SUCCESS [  1.687 s]
[INFO] Apache Hadoop Project Dist POM ..................... SUCCESS [  0.108 s]
[INFO] Apache Hadoop Assemblies ........................... SUCCESS [  0.120 s]
[INFO] Apache Hadoop Maven Plugins ........................ SUCCESS [  3.879 s]
[INFO] Apache Hadoop MiniKDC .............................. SUCCESS [ 11.639 s]
[INFO] Apache Hadoop Auth ................................. SUCCESS [02:53 min]
[INFO] Apache Hadoop Auth Examples ........................ SUCCESS [  1.478 s]
[INFO] Apache Hadoop Common ............................... SUCCESS [17:51 min]
[INFO] Apache Hadoop NFS .................................. SUCCESS [ 24.210 s]
[INFO] Apache Hadoop KMS .................................. SUCCESS [03:11 min]
[INFO] Apache Hadoop Registry ............................. SUCCESS [ 49.486 s]
[INFO] Apache Hadoop Common Project ....................... SUCCESS [  0.060 s]
[INFO] Apache Hadoop HDFS Client .......................... SUCCESS [02:04 min]
[INFO] Apache Hadoop HDFS ................................. SUCCESS [  06:27 h]
[INFO] Apache Hadoop HDFS Native Client ................... SUCCESS [  02:02 h]
[INFO] Apache Hadoop HttpFS ............................... SUCCESS [08:18 min]
[INFO] Apache Hadoop HDFS-NFS ............................. SUCCESS [02:47 min]
[INFO] Apache Hadoop YARN ................................. SUCCESS [  0.099 s]
[INFO] Apache Hadoop YARN API ............................. SUCCESS [ 37.699 s]
[INFO] Apache Hadoop YARN Common .......................... SUCCESS [05:02 min]
[INFO] Apache Hadoop YARN Server .......................... SUCCESS [  0.088 s]
[INFO] Apache Hadoop YARN Server Common ................... SUCCESS [02:50 min]
[INFO] Apache Hadoop YARN ApplicationHistoryService ....... SUCCESS [04:08 min]
[INFO] Apache Hadoop YARN Timeline Service ................ SUCCESS [01:13 min]
[INFO] Apache Hadoop YARN Web Proxy ....................... SUCCESS [ 51.925 s]
[INFO] Apache Hadoop YARN ResourceManager ................. SUCCESS [  01:42 h]
[INFO] Apache Hadoop YARN NodeManager ..................... SUCCESS [23:14 min]
[INFO] Apache Hadoop YARN Server Tests .................... SUCCESS [02:56 min]
[INFO] Apache Hadoop YARN Client .......................... SUCCESS [26:42 min]
[INFO] Apache Hadoop MapReduce Client ..................... SUCCESS [  0.983 s]
[INFO] Apache Hadoop MapReduce Core ....................... SUCCESS [06:37 min]
[INFO] Apache Hadoop MapReduce Common ..................... SUCCESS [ 44.306 s]
[INFO] Apache Hadoop MapReduce Shuffle .................... SUCCESS [ 25.382 s]
[INFO] Apache Hadoop MapReduce App ........................ SUCCESS [09:33 min]
[INFO] Apache Hadoop MapReduce HistoryServer .............. SUCCESS [05:05 min]
[INFO] Apache Hadoop MapReduce JobClient .................. SUCCESS [  02:14 h]
[INFO] Apache Hadoop Distributed Copy ..................... SUCCESS [44:58 min]
[INFO] Apache Hadoop Mini-Cluster ......................... SUCCESS [  2.013 s]
[INFO] Apache Hadoop Federation Balance ................... SUCCESS [20:21 min]
[INFO] Apache Hadoop HDFS-RBF ............................. SUCCESS [39:35 min]
[INFO] Apache Hadoop HDFS Project ......................... SUCCESS [  0.067 s]
[INFO] Apache Hadoop YARN SharedCacheManager .............. SUCCESS [ 25.708 s]
[INFO] Apache Hadoop YARN Timeline Plugin Storage ......... SUCCESS [04:44 min]
[INFO] Apache Hadoop YARN TimelineService HBase Backend ... SUCCESS [  0.061 s]
[INFO] Apache Hadoop YARN TimelineService HBase Common .... SUCCESS [ 13.852 s]
[INFO] Apache Hadoop YARN TimelineService HBase Client .... SUCCESS [ 17.091 s]
[INFO] Apache Hadoop YARN TimelineService HBase Servers ... SUCCESS [  0.053 s]
[INFO] Apache Hadoop YARN TimelineService HBase Server 1.7  SUCCESS [  4.283 s]
[INFO] Apache Hadoop YARN TimelineService HBase tests ..... SUCCESS [15:56 min]
[INFO] Apache Hadoop YARN Router .......................... SUCCESS [ 10.480 s]
[INFO] Apache Hadoop YARN TimelineService DocumentStore ... SUCCESS [ 30.523 s]
[INFO] Apache Hadoop YARN Applications .................... SUCCESS [  0.062 s]
[INFO] Apache Hadoop YARN DistributedShell ................ SUCCESS [21:52 min]
[INFO] Apache Hadoop YARN Unmanaged Am Launcher ........... SUCCESS [ 33.038 s]
[INFO] Apache Hadoop YARN Services ........................ SUCCESS [  0.054 s]
[INFO] Apache Hadoop YARN Services Core ................... SUCCESS [20:33 min]
[INFO] Apache Hadoop YARN Services API .................... SUCCESS [01:45 min]
[INFO] Apache Hadoop YARN Application Catalog ............. SUCCESS [  0.051 s]
[INFO] Apache Hadoop YARN Application Catalog Webapp ...... SUCCESS [ 39.140 s]
[INFO] Apache Hadoop YARN Application Catalog Docker Image  SUCCESS [  0.149 s]
[INFO] Apache Hadoop YARN Application MaWo ................ SUCCESS [  0.086 s]
[INFO] Apache Hadoop YARN Application MaWo Core ........... SUCCESS [  4.808 s]
[INFO] Apache Hadoop YARN Site ............................ SUCCESS [  0.049 s]
[INFO] Apache Hadoop YARN Registry ........................ SUCCESS [  0.666 s]
[INFO] Apache Hadoop YARN UI .............................. SUCCESS [03:30 min]
[INFO] Apache Hadoop YARN CSI ............................. SUCCESS [ 24.692 s]
[INFO] Apache Hadoop YARN Project ......................... SUCCESS [  1.431 s]
[INFO] Apache Hadoop MapReduce HistoryServer Plugins ...... SUCCESS [  5.340 s]
[INFO] Apache Hadoop MapReduce NativeTask ................. SUCCESS [11:01 min]
[INFO] Apache Hadoop MapReduce Uploader ................... SUCCESS [ 15.041 s]
[INFO] Apache Hadoop MapReduce Examples ................... SUCCESS [ 31.592 s]
[INFO] Apache Hadoop MapReduce ............................ SUCCESS [  1.447 s]
[INFO] Apache Hadoop MapReduce Streaming .................. SUCCESS [06:49 min]
[INFO] Apache Hadoop Client Aggregator .................... SUCCESS [  1.430 s]
[INFO] Apache Hadoop Dynamometer Workload Simulator ....... SUCCESS [ 42.545 s]
[INFO] Apache Hadoop Dynamometer Cluster Simulator ........ SUCCESS [  8.119 s]
[INFO] Apache Hadoop Dynamometer Block Listing Generator .. SUCCESS [ 31.750 s]
[INFO] Apache Hadoop Dynamometer Dist ..................... SUCCESS [  1.556 s]
[INFO] Apache Hadoop Dynamometer .......................... SUCCESS [  0.054 s]
[INFO] Apache Hadoop Archives ............................. SUCCESS [01:17 min]
[INFO] Apache Hadoop Archive Logs ......................... SUCCESS [ 39.592 s]
[INFO] Apache Hadoop Rumen ................................ SUCCESS [ 10.717 s]
[INFO] Apache Hadoop Gridmix .............................. SUCCESS [17:13 min]
[INFO] Apache Hadoop Data Join ............................ SUCCESS [ 17.154 s]
[INFO] Apache Hadoop Extras ............................... SUCCESS [ 49.855 s]
[INFO] Apache Hadoop Pipes ................................ SUCCESS [  8.419 s]
[INFO] Apache Hadoop Amazon Web Services support .......... SUCCESS [02:21 min]
[INFO] Apache Hadoop Kafka Library support ................ SUCCESS [  5.846 s]
[INFO] Apache Hadoop Azure support ........................ SUCCESS [01:43 min]
[INFO] Apache Hadoop Aliyun OSS support ................... SUCCESS [  3.311 s]
[INFO] Apache Hadoop Scheduler Load Simulator ............. SUCCESS [12:06 min]
[INFO] Apache Hadoop Resource Estimator Service ........... SUCCESS [ 22.317 s]
[INFO] Apache Hadoop Azure Data Lake support .............. SUCCESS [ 35.326 s]
[INFO] Apache Hadoop Image Generation Tool ................ SUCCESS [ 13.299 s]
[INFO] Apache Hadoop Tools Dist ........................... SUCCESS [  1.050 s]
[INFO] Apache Hadoop OpenStack support .................... SUCCESS [  0.063 s]
[INFO] Apache Hadoop Common Benchmark ..................... SUCCESS [  2.812 s]
[INFO] Apache Hadoop Tools ................................ SUCCESS [  0.082 s]
[INFO] Apache Hadoop Client API ........................... SUCCESS [  1.517 s]
[INFO] Apache Hadoop Client Runtime ....................... SUCCESS [  1.296 s]
[INFO] Apache Hadoop Client Packaging Invariants .......... SUCCESS [  0.304 s]
[INFO] Apache Hadoop Client Test Minicluster .............. SUCCESS [  1.074 s]
[INFO] Apache Hadoop Client Packaging Invariants for Test . SUCCESS [  0.101 s]
[INFO] Apache Hadoop Client Packaging Integration Tests ... SUCCESS [  0.169 s]
[INFO] Apache Hadoop Distribution ......................... SUCCESS [  0.430 s]
[INFO] Apache Hadoop Client Modules ....................... SUCCESS [  0.045 s]
[INFO] Apache Hadoop Tencent COS Support .................. SUCCESS [  2.952 s]
[INFO] Apache Hadoop OBS support .......................... SUCCESS [  3.610 s]
[INFO] Apache Hadoop Cloud Storage ........................ SUCCESS [  0.709 s]
[INFO] Apache Hadoop Cloud Storage Project ................ SUCCESS [  0.049 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  18:31 h
[INFO] Finished at: 2023-01-07T19:47:11Z
[INFO] ------------------------------------------------------------------------

Thank you so much, @cnauroth and @sunchao !

I merged this to trunk. I also cherry-picked to branch-3.3 and branch-3.2 after resolving a minor merge conflict. @dongjoon-hyun , thank you for the contribution! @sunchao , thank you for the code review. (Sorry, I forgot to mention you in the Signed-off-by tag.)

How does this work for shaded things the Hadoop build itself pulls in?
IMO this BOM should somehow be included in the released JARs as some well known resource name to allow some introspection at runtime....

FYI, here is Apache ORC 1.8.2 RC1 vote artifact, @steveloughran .

https://repository.apache.org/content/repositories/orgapacheorc-1064/org/apache/orc/orc-core/1.8.2/

got it. will add to 3.3.5 too as this will be our first release with this

Thank you, @steveloughran .

ok, verified the artifacts get into the local mvn repo. i do like the xml version BTW, including all the signatures. makes it easier to spot tampering, doesn't it?
also highlights how hadoop-common has way too many dependencies. we should see what we can do to prune back stuff, such as my #4996. every jar we cut saves many, many integration problems

ok, verified the artifacts get into the local mvn repo.

It's great. :)

i do like the xml version BTW, including all the signatures. makes it easier to spot tampering, doesn't it?

We already did like the other official Apache artifacts.  Please see the official Apache ORC 1.8.2.

https://repo1.maven.org/maven2/org/apache/orc/orc-core/1.8.2/


Updated PR to add Route 53 IPv6 dynamic DNS support

This PR adds a commit to the work in #3818 to make it mergeable with upstream changes.
I have submitted a signed CLA.

#3818 was already merged, can you fix this PR so it's only the difference between that PR and what you want to see, or is it all OK now? If it's OK in the repo now, this can be closed.


argument type of print_pairing_code_and_qr()

Hello there,
I have a suggestion regarding the print_pairing_code_and_qr() function. Currently, it accepts comm_data: &CommissioningData as an argument. However, according to section 5.1 of the Matter-1.0-Core-Specification, both MPC and QR Code require a passcode.
The CommissioningData has either VerifierOption::Password or VerifierOption::Verifier. In my understanding, passing VerifierOption::Verifier instead of VerifierOption::Password as an argument to print_pairing_code_and_qr() will result in a runtime error.
To avoid this issue, I recommend passing VerifierOption::Password as the argument to print_pairing_code_and_qr() instead.

@nevi-me @thekuwayama
TL;DR:
The issue applies to the no_std and sequential branches as well.
Long story:
I've not changed how the QR printing code works conceptually. I've only removed allocations from it and made sure that the aspects that do require Rust STD (the actual display of the QR code in the console) are not called / compiled-out for baremetal / no_std.
Related: ideally we should replace the qrcode lib which does need Rust STD with something that is no_std (and ideally - no-alloc - compatible.). Say - this one.

@thekuwayama Would you mind contributing a PR for this?

@ivmarkov OK! :+1: Could you assign me to this?

This is finally addressed, see #210


Cross validation does not� print any results out

I mean, during cross-validation demos in cross_validation.py pass but do not output anything like:
[iteration]  metric_name:mean_value+std_value
xgboost version 0.47 on Ubuntu
Tried both pip install and manual install, no effect
xgb.train(), on contrary, prints its progress

recent version prints these values.
Bug related to an old version, closing.


CI: K8sServicesTest Checks service across nodes Tests NodePort BPF Tests with vxlan Tests HostPort

The first curl on the IPv6 tftp target from this host times out with exit code 28 (failed: :29430/1=28):
20:39:17 STEP: Making 10 curl requests from pod (host netns) k8s2 to "http://<IP_ADDRESS>:8080"
20:39:17 STEP: Making 10 curl requests from pod (host netns) k8s2 to "tftp://<IP_ADDRESS>:6969/hello"
20:39:17 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://<IP_ADDRESS>:8080"
20:39:17 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://<IP_ADDRESS>:6969/hello"
20:39:18 STEP: Making 10 curl requests from pod (host netns) k8s2 to "http://<IP_ADDRESS>:8080"
20:39:18 STEP: Making 10 curl requests from pod (host netns) k8s2 to "tftp://<IP_ADDRESS>:6969/hello"
20:39:18 STEP: Making 1 curl requests from k8s1 to "http://<IP_ADDRESS>:8080"
20:39:18 STEP: Making 1 curl requests from k8s1 to "tftp://<IP_ADDRESS>:6969/hello"
20:39:23 STEP: Making 10 curl requests from pod (host netns) k8s2 to "http://[::ffff:<IP_ADDRESS>]:8080"
20:39:23 STEP: Making 10 curl requests from pod (host netns) k8s2 to "tftp://[::ffff:<IP_ADDRESS>]:6969/hello"
20:39:23 STEP: Making 10 curl requests from pod (host netns) k8s2 to "http://[::ffff:<IP_ADDRESS>]:8080"
20:39:23 STEP: Making 10 curl requests from pod (host netns) k8s2 to "tftp://[::ffff:<IP_ADDRESS>]:6969/hello"
20:39:24 STEP: Making 10 curl requests from pod (host netns) k8s2 to "http://[fd04::12]:8080"
20:39:24 STEP: Making 10 curl requests from pod (host netns) k8s2 to "tftp://[fd04::12]:6969/hello"
20:39:24 STEP: Making 10 curl requests from pod (host netns) k8s1 to "http://[fd04::12]:8080"
20:39:24 STEP: Making 10 curl requests from pod (host netns) k8s1 to "tftp://[fd04::12]:6969/hello"
FAIL: Request from k8s1 to service tftp://[fd04::12]:6969/hello failed
Expected command: kubectl exec -n kube-system log-gatherer-nd7np -- /bin/bash -c 'fails=""; id=$RANDOM; for i in $(seq 1 10); do if curl --path-as-is -s -D /dev/stderr --fail --connect-timeout 5 --max-time 20 tftp://[fd04::12]:6969/hello -H "User-Agent: cilium-test-$id/$i"; then echo "Test round $id/$i exit code: $?"; else fails=$fails:$id/$i=$?; fi; done; if [ -n "$fails" ]; then echo "failed: $fails"; fi; cnt="${fails//[^:]}"; if [ ${#cnt} -gt 0 ]; then exit 42; fi'
To succeed, but it failed:
Exitcode: 42
Err: exit status 42
Stdout:

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=58842
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/2 exit code: 0

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=41036
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/3 exit code: 0

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=38146
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/4 exit code: 0

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=40967
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/5 exit code: 0

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=60274
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/6 exit code: 0

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=46453
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/7 exit code: 0

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=35133
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/8 exit code: 0

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=50183
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/9 exit code: 0

	 Hostname: test-k8s2-79ff876c9d-hrwt6

	 Request Information:
	 	client_address=fd04::11
	 	client_port=42583
	 	real path=/hello
	 	request_scheme=tftp

	 Test round 29430/10 exit code: 0
	 failed: :29430/1=28

Stderr:
 	 command terminated with exit code 42

/home/jenkins/workspace/Cilium-PR-K8s-1.20-kernel-4.19/src/github.com/cilium/cilium/test/k8sT/service_helpers.go:1133

07410568_K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_vxlan_Tests_HostPort.zip
https://jenkins.cilium.io/job/Cilium-PR-K8s-1.20-kernel-4.19/751/testReport/junit/Suite-k8s-1/20/K8sServicesTest_Checks_service_across_nodes_Tests_NodePort_BPF_Tests_with_vxlan_Tests_HostPort/

This issue has not seen any activity since it was marked stale. Closing. Feel free to re-open a new issue if it is still persisting. Thank you.


Flow sometimes detects incorrect type in expressions involving && and ||

/* @flow */
class A {};
type B = {};

function foo(a: ?A, b: ?B) {
  var s: string = a && "X" || "Y"; // error
  var t: string = b && "X" || "Y"; // ok
}

Also, quite confusingly, the error is reported in parameter a of the function, instead of in the location where the parameter fails to typecheck: http://tryflow.org/#dd51333184c595d324852a62d95ed062

Wow, nice catch!
Here's a trace:
test.js:5:18,18: A
This type is incompatible with
test.js:6:10,15: string
Error path:
test.js:5:18,18: InstanceT [A]
test.js:6:10,15: ~> StrT [string] comes from
test.js:5:18,18: . InstanceT [A]
test.js:6:19,33: . ~> PredicateT [||] comes from
test.js:5:18,18: . . InstanceT [A]
test.js:6:19,33: . . ~> OrT [||] comes from
test.js:5:18,18: . . .     MaybeT [?A]
test.js:6:19,26: . . . . . . . ~> AndT [&&]

I think the issue is in Flow_js.filter_not_exists, which doesn't consider InstanceT to be truthy, but I haven't actually tested htis.

All right, I had to check out an old-ish rev to make the change and test it, but adding an InstanceT case to filter_not_exists does indeed resolve htis.

This also fails:
/* @flow */

declare class Foo {}

function test(x: ?Class<Foo>): string {
  return x && "" || "";
}

Glad you were able to solve it this fast!


Discounts apportionment issues

On the AmountOff discount type you are apportioning the discount over the lines:
https://github.com/lunarphp/lunar/blob/a8448755b5c89b2500c1eb11a585d569c392d6b9/packages/core/src/DiscountTypes/AmountOff.php#L80-L89
However on BuyXGetY this is not taking place which causes VAT calculation errors. HMRC rules say that discounts like this are a 'pack'... ie you treat the new price as purchasing of all the items, work out price which they would have been without the discount, then apportion the difference across all the items, that way VAT is disbursed correctly.
e.g.
You have item A at £10 and you need to buy 2 to get item B for free which normally costs £5.
Normal price = 2 x A (£10) plus 1 x B (£5) = £25
Discounted price = £20
New price (for Tax) = 2 x A (£8) plus 1 x B (£4) = £20
The customer would still see the price as the full price with a discount line, but for the purposes of taxation this needs correctly calculated.
[Update: I've noticed that FixedAmount discounts also suffer from this issue - in that the discount is spread across the number of items, not weighted according to the price of the items]

I'm happy with the calculation proposal.
In terms of the Cart UI, how would you propose we display it to the customer?

Can this be configurable in someways? There are situation that doesn’t need VAT/HMRC and just simply wants the free item to be $0
Currently can we replace the BuyXgetY/amountOff and substitute with own flavor?

For the end user I don’t want to show the apportioned price at all. But the warehouse system integration needs it to be apportioned
@wychoong what I’m suggesting won’t affect the existing implantation.

I am keen to ensure figures are correct for accounting purposes. I know this is specific to UK VAT, but my understanding is accounting principles are fairly standard.
@ryanmitchell how will you continue to show the item as free in the UI if we're changing the price totals?

I actually wonder if we need to change the approach a little and have a $line->apportionedTotals or something like that.
$line->apportionedTotals = [
   'subtotal' => x,
   'tax' => y,
];

That way you have options:

you can output the original values (eg £0 for the discounted item)
you have the discountTotal line if you want to show each line original total with a discount amount underneath
you have the subTotalDiscounted if you want to show each lines new subtotal inc discount
you have the apportioned totals if you want to show the apportionment totals

I guess it could work, but it's getting a little complex.

Worth checking how Shopify does it, and whether that conforms to HMRC requirements?

They dont seem to handle it until reporting, as they can get away with that sort of thing. I'll try some things and see what I can come up with to keep it as clean as possible, maybe we hide it behind a config variable so those that dont want it dont get it.

Ok, I've pushed some updates to the BuyXGetY branch I was working on: https://github.com/lunarphp/lunar/pull/881/commits/479f2993252a593a8583ce29f60d6148e82993a3
When an item is in a discount it works out what its 'share' of the discount is (based on its price percentage of the overall pack price before discount) and applies this to a new CartLine property apportionedDiscount.
This value would then allow developers to calculate what they want - eg subtotal - apportionedDiscount = taxableSubTotal
I've also added this property to FixedAmount discounts as it was calculating discount differently (based on qty not price).
There also doesn't seem to be any consideration given to multiple discounts applying to the same item - the discount amount gets reset each time, instead of compounded. This will definitely case issues. You'll see in BuyXGetY I've left some comments where this needs to be considered.
Anyway, the intention here is to spark thoughts, not that this is the final solution

There also doesn't seem to be any consideration given to multiple discounts applying to the same item - the discount amount gets reset each time, instead of compounded. This will definitely cause issues. You'll see in BuyXGetY I've left some comments where this needs to be considered.

Should this be a separate issue?

There also doesn't seem to be any consideration given to multiple discounts applying to the same item - the discount amount gets reset each time, instead of compounded. This will definitely cause issues. You'll see in BuyXGetY I've left some comments where this needs to be considered.

Should this be a separate issue?

Pulled it out separately as #885

After some Discord chat its looking like apportionment would need to be handled by the developer, so I've opened up https://github.com/lunarphp/lunar/pull/884 as a starting point for providing the information required for this to be calculated.

Closed by #884


Added Weekly #7

Current draft.
@diasdavid I need help with your contributions, I'm not sure about what to make of them.
@jbenet We should have a note about the MIT Media Lab // blockchain meetup. I don't know how you want to phrase that, or what exactly when on, as I came on at the tail end.
@whyrusleeping and @haadcode: thanks, looks good.

go-ipfs stuff LGTM. Thanks @RichardLitt

Add:
@jbenet gave a talk titled Datastructures In and On IPFS](http://www.infoq.com/presentations/data-ipfs-ipld) at last year's QCon SF. The video was released this week, so now you can all see it! The talk includes a typical introduction (skip if you know ipfs well), and then dives into datastructures, including Merkle Links, Mazieres links, how IPNS works, IPRS records, versioning, Keychain (PKI on ipfs), Persona (identity), and more.

The IPFS powered USB deaddrop at c-base was demonstrated at the LoganCIJ 2016 Symposium, in the Investigative Journalism conference. More pictures here. If you want to build your own IPFS USB deaddrops, check out the c-base project here: https://github.com/c-base/ipfs-deaddrop .

The IPFS Copenhagen Meetup organized by @NeoTeo had another meeting a few days ago. If you're in the area, sign up at [the Meetup.com page]((http://www.meetup.com/Copenhagen-IPFS-Meetup) so you don't miss the next one!
Several core IPFS developers will be in NYC from March 28th to April 8. We will be organizing an IPFS Meetup within that time frame. If you would like to come, please follow this github issue for the final details. If you would like to present, post in that issue.

Woo! That looks great! Will add.


Attribute application@allowBackup is also present at [com.github.satyan:sugar:1.3]

I getting this when try to compile
C:\dev\workspace\ContactLoggerApp\app\src\main\AndroidManifest.xml:25:9-36 Error:
Attribute application@allowBackup value=(false) from AndroidManifest.xml:25:9-36
is also present at [com.github.satyan:sugar:1.3] AndroidManifest.xml:12:9-35 value=(true)
Suggestion: add 'tools:replace="android:allowBackup"' to element at AndroidManifest.xml:23:5-106:19 to override
C:\dev\workspace\ContactLoggerApp\app\src\main\AndroidManifest.xml:26:9-43 Error:
Attribute application@icon value=(@mipmap/ic_launcher) from AndroidManifest.xml:26:9-43
is also present at [com.github.satyan:sugar:1.3] AndroidManifest.xml:13:9-45 value=(@drawable/ic_launcher)
Suggestion: add 'tools:replace="android:icon"' to element at AndroidManifest.xml:23:5-106:19 to override

Okay, updating to 1.3.1 solved the issue :)

Suggestion: add 'tools:replace="android:XXXX"' to element at AndroidManifest.xml to override
just replace XXXX with the attribute you are having problems with and add to the  element in your Manifest. This way you will override any value set by the library for those attributes.
For example:
<application
    tools:replace="android:icon"
    android:icon="@drawable/my_launcher"
    android:theme="@style/AppTheme"
    android:label="@string/app_name">

        <!-- your stuff here -->

</application>


Strange artifacts when wildcart (*) present in SMILES

Hi, I found a few artifacts when dealing with SMILES that contain the wildcard *, specially in rings. In the attached screenshot, you can see that a ring becomes a 'square' after encoding and decoding. This happens when converting from BRICS to SAFE.

Thanks for the quick response, it's working as expected now!


Bump JQ_VERSION to 1.6

My only reservation here is we're trying to land first-class arm support (in #758), and currently that includes switching to installing jq 1.5 via yum:
https://github.com/buildkite/elastic-ci-stack-for-aws/pull/758/files#diff-40214ac00fcda1e5241174fd97f51ea3697f17ebebe62f2065913cf79f2dfe78R51
Is there a feature in 1.6 that you're keen on?

Nah i just thought it would be good to update.


Suggestion : Collapsible groups

Hi,
I would like to suggest doing the same as asked in #28, collapsible groups when grouping by tags. That issue was closed but IMO the response given was a little beside the point.
This works really well in a case (such as mine) where you have a log of different paths (paths, not just operations) and that they are usually tagged accordingly to the department that uses/reviews them.
Our users currently use Swagger UI on the legacy apps and they are used to come to a fully-collapsed view, open the one group they need, and have a view of what is of interest for them.
I personally prefer RapiDoc for various reasons (thank you for a great tool !), among which the fact it's so easily hackable. Pretty neat.
But I see the lack of collapsible groups as a big usability issue.
So I would suggest an option to turn that on. Personally I would even make it collapsible by default.
And again, thank you for such a nice-to-use tool !

well, I am not just talking about supporting collapsible groups. The problem that we all are trying to address here is how to make a large doc easy to navigate and collapsible-groups may be one such feature that can take away some pain.
We have made few prototypes in the past to address this but none of them was up to our liking except one. That was to group all the paths by method. Released in version 5.3.0 but had to discontinue its support due to poor user feedback. Now we are again out of ideas :(
whats the problem with collapsible-groups ?  well, there are few cases that needs to be addressed in a way thats not confusing to the user

RapiDoc supports searching paths, so if I collapse a group of paths, the user will not be able to search it, which will be misleading
You can create hyperlinks to various paths in markdown. with a collapsible group, the link may not function
we expose a method scrollTo(path) that may not wok as expected with collapsible group

Having said all that, If I can get a basic pull request implementing collapsible-groups that addresses some of the above concerns we will work towards it to get it into the product.
We rely heavily on user contributions, and is one of our primary reason to keep our codebase small and simple. If any one is interested, please give it a try, IMHO any average developer will be in a position to contribute !!!
happy hacking

this feature contributed by @fbacker addresses the issue of collapsible groups
here is a test case / demo for it https://mrin9.github.io/RapiDoc/examples/collapsable.html


Update SQLite database on load

Couple ideas:
Have a webhook send me raindrops
Get raindrops after a date

Added a table to keep track of last time the app was started, then I retrieve bookmarks that were created after that date.


Pylint may invoke Python2 pylint

Description

Type: Bug
Priority: Major

Bug
Since https://github.com/ARMmbed/mbedtls/pull/3100, all.sh check_python_files fails on systems that have both Python 2 including pylint and Python 3 including pylint3. Python 2 is no longer upported, but it's too early to assume that everybody has uninstalled it.
For at least a few months, we should prefer pylint3 to pylint.

Are you sure @gilles-peskine-arm this isn't just an issue specific to your system? What is the default preferred version of Python on your machine? Is it Python 2 or 3?
Also, surely all.sh is a CI script to be executed in a specific controlled environment? Hence why the versions are so carefully selected.

My system is Ubuntu 16.04 or Ubuntu 18.04, which are the systems that the CI runs. Ubuntu 18.04 is the latest LTS release of Ubuntu (only for another month or so, granted). Ubuntu ships /usr/bin/pylint for Python 2 up to 19.04, and for Python 3 since 19.10.
Ubuntu follows PEP 394, which until April 2018 requires that python refer to Python 2. PEP 394 also requires that associated commands like idle and python-config are for python and python3-idle for python3, etc. It doesn't mention third-party commands like pip and pylint explicitly, but I'd expect them to follow the same guideline.
The current state of all.sh is fragile. It only works because the package pylint is not installed.


--version does not work when published as .NET 5/PublishSingleFile

Information

OS: Win 10
Version: 0.37.1-preview.0.12
Terminal: Any

Describe the bug
After publishing single file with .NET 5 (dotnet publish) --version stops working (shows ?).

To Reproduce
Create console app with:
<PropertyGroup>
  <OutputType>Exe</OutputType>
  <TargetFramework>net5.0</TargetFramework>
  <PublishSingleFile>true</PublishSingleFile>
  <RuntimeIdentifier>win-x64</RuntimeIdentifier>
  <Version><IP_ADDRESS></Version>
</PropertyGroup>

create dummy app:
class Program
{
	static void Main(string[] args)
	{
		var app = new CommandApp();
		app.Configure(config => config.AddCommand<RunCommand>("run"));
		app.Run(args);
	}
}

public class RunCommand: Command
{
	public override int Execute(CommandContext context) => 0;
}

build & publish it:
dotnet build
dotnet publish

run both:
.\bin\Debug\net5.0\win-x64\app.exe --version
.\bin\Debug\net5.0\win-x64\publish\app.exe --version

Observe one produces <IP_ADDRESS> (expected) while the other produces ?
Expected behavior
Both produce version (<IP_ADDRESS>)
Screenshots
Included above.
Additional context
So, my guess is it returns null from GetEntryAssembly() because of some publish single file related shenanigans.
Seems like Process.GetCurrentProcess().MainModule?.FileVersionInfo.ProductVersion works for 3.1 and 5.0 but not for 2.2. For 2.2 it returns... version of dotnet.exe. LOL.
Suggestion 1
Multi-targetting with conditional compilation (GetEntryAssembly() vs Process.GetCurrentProcess().MainModule)
Suggestion 2
Allow to override version (like SetApplicationName)
app.Configure(config => {
	config.SetApplicationName("App");
	config.SetApplicationVersion("<IP_ADDRESS>-overriden");
	config.AddCommand<RunCommand>("run");
});

Suggestion 3
Both ;-)
(I guess no 2 is trivial)

Thank you

Thank you

@MiloszKrajewski Great catch! Suggestion 3 sounds like a good approach!
Would you want to take a stab at this? Otherwise, I might be able to get around to it tomorrow evening or so (CET timezone).

@MiloszKrajewski Great catch! Suggestion 3 sounds like a good approach!
Would you want to take a stab at this? Otherwise, I might be able to get around to it tomorrow evening or so (CET timezone).

I can take a look, don't worry (I will let you know if I give up).

I can take a look, don't worry (I will let you know if I give up).

Update:

So the warning was always there when I was building single file exe:

warning IL3000: 'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.

System.Reflection.Assembly.Location returns empty string

Code below was never falling back to assembly?.GetName()?.Version?.ToString() it was always short-circuiting to exception handler straight away.
try
{
    var info = FileVersionInfo.GetVersionInfo(assembly.Location);
    return info.ProductVersion ?? assembly?.GetName()?.Version?.ToString() ?? "?";
}
catch
{
    return "?";
}

<Version> from csproj translates to AssemblyInformationalVersionAttribute
So consistent way to get full assembly version is assembly?.GetCustomAttribute<AssemblyInformationalVersionAttribute>()?.InformationalVersion

I'm attaching project showing possible ways to get version to show that I did my homework ;-)

Run test.cmd
GetAssemblyVersion.zip

PR comes in a minute

Update:

So the warning was always there when I was building single file exe:

warning IL3000: 'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.

System.Reflection.Assembly.Location returns empty string

Code below was never falling back to assembly?.GetName()?.Version?.ToString() it was always short-circuiting to exception handler straight away.
try
{
    var info = FileVersionInfo.GetVersionInfo(assembly.Location);
    return info.ProductVersion ?? assembly?.GetName()?.Version?.ToString() ?? "?";
}
catch
{
    return "?";
}

<Version> from csproj translates to AssemblyInformationalVersionAttribute
So consistent way to get full assembly version is assembly?.GetCustomAttribute<AssemblyInformationalVersionAttribute>()?.InformationalVersion

I'm attaching project showing possible ways to get version to show that I did my homework ;-)

Run test.cmd
GetAssemblyVersion.zip

PR comes in a minute


Serial as key for disk instead of name

As the name for a disk can change (Like when rebooting or replacing disks), maybe it would be better to use the serial as the key.

Hmm, yeah, that's a good point!  I will tackle that some time in the next few days, as it matters for my other project that depends on this, sdwilsh/hass-freenas


[RFC] opens in a new tab

How do you envision this feature/change to look/work like?
Firstly, thanks for making this framework
With Redux
Content scripting is not supported in the current version. I would like to have content scripting support (open in a new tab), and for data in multiple content script stores to be interoperable
What is the purpose of this change/feature? Why?

Make data in multiple content script stores interoperable
(OPTIONAL) Example implementations
No response
(OPTIONAL) Contact Details
No response
Verify canary release

[X] I verified that the issue exists in plasmo canary release

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

With Redux

Content scripting is not supported in the current version. I would like to have content scripting support (open in a new tab), and for data in multiple content script stores to be interoperable

The redux store should now sync using the chrome sync storage API.

I would like to have content scripting support (open in a new tab), and for data in multiple content script stores to be interoperable

Can you please elaborate? We have a tabs feature for that - CS are for modifying webpages: https://docs.plasmo.com/framework/tab-pages


Cairo runner: implement checkRangeCheckUsage

In order to check that there are enough trace cells to fill the entire range check range, we need to implement a checkRangeCheckUsage function inside the Cairo runner.
Reference for the function implementation

https://github.com/lambdaclass/cairo-vm/blob/4ea224a1068b43aaa3899d24e834475106e8a78f/vm/src/vm/runners/cairo_runner.rs#L744-L769

References for unit tests

https://github.com/lambdaclass/cairo-vm/blob/4ea224a1068b43aaa3899d24e834475106e8a78f/vm/src/vm/runners/cairo_runner.rs#L4102
https://github.com/lambdaclass/cairo-vm/blob/4ea224a1068b43aaa3899d24e834475106e8a78f/vm/src/vm/runners/cairo_runner.rs#L4125
https://github.com/lambdaclass/cairo-vm/blob/4ea224a1068b43aaa3899d24e834475106e8a78f/vm/src/vm/runners/cairo_runner.rs#L4149

assign me


Android SDK Integration Test fails

Android 8.0. Im tried to update dependence com.appsflyer:af-android-sdk:4.8.14@aar to 4.8.18 and 4.8.19 but nothing happened.

Same case here. The startTracking() and non-organic install verified tests are not passing on Android.
I'm using react-native-appsflyer versionn 1.4.2

I solved this issue by adding permission and receiver in AndroidManifest.xml as follow:
Permission:
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
Receiver:
<receiver android:name="com.appsflyer.SingleInstallBroadcastReceiver" android:exported="true">
	<intent-filter>
	    <action android:name="com.android.vending.INSTALL_REFERRER" />
	</intent-filter>
</receiver>
Reference: https://support.appsflyer.com/hc/en-us/articles/207032126-AppsFlyer-SDK-Integration-Android


When windows terminal is inactive, it resets transparency settings

Windows Terminal version
latest
Windows build number
No response
Other Software
No response
Steps to reproduce

Change opacity to 0.5, 0.25, etc
Look how that work (first screenshot)
Change your active window (second screenshot)

Json settings here:

Expected Behavior
No response
Actual Behavior
Transparency does not change when switching windows.

Please check the FAQ. This is by design. Acrylic only works on the foreground window. You may be interested in /dup #7158


Enhance README Documentation for Better User Experience

The current README provides a good starting point for understanding the project. However, there are several areas where it could be improved to provide a more comprehensive and user-friendly experience. Here are some suggestions:

Project Description: The project description could be expanded to include more details about the project's purpose, its features, and the problems it solves. This will help users understand what they can expect from using the project.

Installation Instructions: While the document mentions the need for a functional Python environment, it doesn't provide detailed instructions on how to set up and install the project. This should include any prerequisites needed to run the project and the exact commands to run the script.

Contribution Guidelines: If the project is open to contributions, include guidelines on how others can contribute. This could include information on how to submit issues, create pull requests, and the project's code of conduct.

License Information: Include information about the project's license. This helps users understand how they can use the project and any restrictions that might apply.

By implementing these changes, the README will provide a more comprehensive overview of the project, making it easier for users to understand and use.

Great feedback! I appreciate your suggestions for improving the README. Can you contribute to these enhancements? Your input would be valuable in making the project more user-friendly. Thanks!


chore(releases): add username to changelog

This PR resolves PHIRE-1265
Description

Adds github usernames to changelog output as suggested by @dblandin
Replaces ts-node with tsx to workaround this issue without additional config: https://artsy.slack.com/archives/C02BAQ5K7/p1727438708031879

~/C/eigen (brian/username-changelog|✚1) $ yarn generate-changelog ios-8.53.0-2<IP_ADDRESS>-submission main                                                                                (base)
yarn run v1.22.21
warning ../package.json: No license field
$ tsx scripts/changelog/generateChangelog.ts ios-8.53.0-2<IP_ADDRESS>-submission main

PRs with changelog entries:
- increase hitslop of section titles - mounir - MounirDhahri : Cross-platform user-facing changes : PR #10852
- handle some unable to load errors and improve error reporting - brian - brainbicycle : Cross-platform user-facing changes : PR #10854
- fix: add save icons back - daria - dariakoko : Cross-platform user-facing changes : PR #10859
- fix android status bar and bottom nav styling - brian - brainbicycle : Android user-facing changes : PR #10860
- fix back button not working in screens with modal - brian - brainbicycle : Android user-facing changes : PR #10862
- bring back artists card follow button - mrsltun - MrSltun : Cross-platform user-facing changes : PR #10864
- fix crash on iOS when tapping "Manage Saves" in the activity panel - mrsltun - MrSltun : Cross-platform user-facing changes : PR #10865
- change of the image size dimensions of an artwork rail card (behind a ff AREnableArtworkRailRedesignImageAspectRatio)- daria - dariakoko : Cross-platform user-facing changes : PR #10857
- attempt at solving undefined lot count - mounir - MounirDhahri : Dev changes : PR #10858
- (HomeView) Do not display urgency signals on the HomeViewSectionFeaturedCollection rail - daria - dariakoko : Cross-platform user-facing changes : PR #10868
- Fix pagination indicator on home view hero unit section — Roop - anandaroop : Cross-platform user-facing changes : PR #10869
- Cleanup Auction Lots For You rail - remove no longer use size prop - daria - dariakoko : Dev changes : PR #10866
- add AREnableArtworkRailRedesignImageAspectRatio echo flag, make it ready for release - daria - dariakoko : Dev changes : PR #10876
Change buy now copy to inquire for sales rail - dejuanito - egdbear : Cross-platform user-facing changes : PR #10877
- Ensure consistent touchable highlight for articles rail — Roop - anandaroop : Cross-platform user-facing changes : PR #10870
- Upgrade fastlane to v2.223.1 - mrsltun - MrSltun : Dev changes : PR #10871
added discover marketing collections to homeview - dejuan - egdbear : Cross-platform user-facing changes : PR #10873
- fix: collection prompt search results scroll - araujobarret - araujobarret : Cross-platform user-facing changes : PR #10881
- fix submission tags - brian - brainbicycle : Dev changes : PR #10888
- Respect safe area top inset on new home view — Roop - anandaroop : Cross-platform user-facing changes : PR #10892
- Fixes whitespace in home screen artist rail  — Roop - anandaroop : Cross-platform user-facing changes : PR #10889
- Add swipeable component to Eigen - mrsltun - MrSltun : Dev changes : PR #10879
- fix double tracking push tapped calls - brian - brainbicycle : Dev changes : PR #10884
- provide a way to recover from email verification failures - iskounen - iskounen : Dev changes : PR #10900
- run eigen tests when we open an echo deploy PR - gkartalis - gkartalis : Dev changes : PR #10906
- fix placeholders on the new home view - daria - dariakoko : Cross-platform user-facing changes : PR #10893

PRs with #nochangelog:
PR #10856: fix: artworks screen loading skeleton - MounirDhahri
PR #10863: chore: update metaphysics graphql schema - artsyit
PR #10855: chore: adjust assignees - MounirDhahri
PR #10872: chore: update metaphysics graphql schema - artsyit
PR #10874: chore: update metaphysics graphql schema - artsyit
PR #10875: chore: update metaphysics graphql schema - artsyit
PR #10878: chore: update metaphysics graphql schema - artsyit
PR #10882: chore: update metaphysics graphql schema - artsyit
PR #10887: chore: update version number - brainbicycle
PR #10891: chore: prepare for next release - artsyit
PR #10897: chore: update metaphysics graphql schema - artsyit
PR #10901: chore: update metaphysics graphql schema - artsyit
PR #10902: chore: update metaphysics graphql schema - artsyit

PRs without changelog entries:
PR #10861: feat(DIA-896): add an auth model method to identify email addresses - iskounen
PR #10746: feat(DIA-785): fuse signup and login flows into a single user experience - iskounen
PR #10885: docs(release-build): Update with screen cap and missing step - damassi
PR #10890: refactor(auth): Rework new auth flow for perf, etc  - damassi
PR #10895: refactor(auth2): More smoothing out of auth screens  - damassi
PR #10896: fix(auth2): Remove KeyboardAvoidingView to get around iOS 17 bug  - damassi
PR #10898: fix(auth2): PR follow-ups - damassi
PR #10899: fix(auth2): Fix misc validation issues - damassi
PR #10909: fix: add param to avoid running test-build-deploy - brainbicycle
PR #10904: feat(DIA-898): use shared password field for sign-up and login - iskounen

PR Checklist

[ ] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

add username to changelog - brian

Need help with something? Have a look at our docs, or get in touch with us.

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against 4eb7488da99d49008d141d1696c71a968b845866

Warnings
⚠
✅ No changelog changes
Generated by 🚫 dangerJS against 4eb7488

hmm


Switch to native pytest in tests/track

I'm doing this folder by folder, the other example being https://github.com/elastic/rally/pull/1387. I've used unittest2pytest and reversed the yoga conditions as assert a = 0 is invalid syntax. I find the result much clearer.

Only thing to be sure of (that doesn't require a review volley) is that we're intentionally going with the more human/explicit/verbose
    assert x is True

vs just assert x

I only did that in a series of nearly identical tests were a given value could be True, False or None. Since assert x works with truthy values and assert not x works with False I indeed preferred to be explicit in those tests. We even had a comment saying:

Explicitly check in these tests for equality - assertFalse would also succeed if it is None.

I could have left it.

However, in general there's no ambiguity and I do prefer the assert x form!

Failed with:
09:57:21 ____________________ test_docker_distribution[in-memory-it] ____________________
09:57:21
09:57:21 cfg = 'in-memory-it'
09:57:21
09:57:21     @it.random_rally_config
09:57:21     def test_docker_distribution(cfg):
09:57:21         port = 19200
09:57:21         # only test the most recent Docker distribution
09:57:21         dist = it.DISTRIBUTIONS[-1]
09:57:21         it.wait_until_port_is_free(port_number=port)
09:57:21 >       assert (
09:57:21             it.race(
09:57:21                 cfg,
09:57:21                 f'--pipeline="docker" --distribution-version="{dist}" '
09:57:21                 f'--track="geonames" --challenge="append-no-conflicts-index-only" --test-mode '
09:57:21                 f"--car=4gheap,basic-license --target-hosts=<IP_ADDRESS>:{port}",
09:57:21             )
09:57:21             == 0
09:57:21         )
09:57:21 E       assert 16384 == 0
09:57:21 E         +16384
09:57:21 E         -0
09:57:21
09:57:21 it/distribution_test.py:53: AssertionError
09:57:21 - generated xml file: /var/lib/jenkins/workspace/elastic+rally+pull-request/junit-py38-it.xml -

@elasticmachine test this please


Add CCITT32 algorithm and CMake coexisting with the GNU make build system in use

Add support for CCITT32 algorithm created by Mark G. Mendel based on makecrc
in http://github.com/dgilman/macutils to support POD files by Terminal Reality engines.

rename and update Makefile to Makefile.crc to make room for new CMake created one.
update INSTALL file with new instructions.
update docs and tests to support CCITT32.
modify GNU make file to support the new algorithm and function alongside the CMake.
add pkg-config support for the library

Pull request denied.
Reviewing it costs more then writing the code myself. The request contains more than one change which makes it impossible to selectively assess the code quality. I previously stated my doubts about cmake. And 4 additional PRs to fix omissions in the first PR are no sign of a quality review by the programmer.
Please read the following page for guidance.
https://www.atlassian.com/blog/git/written-unwritten-guide-pull-requests


general question: without using persistent volume can i share workspace  among tasks ?

I have trigger template like this
apiVersion: triggers.tekton.dev/v1alpha1
kind: TriggerTemplate
metadata:
  name: helmchart-template
  namespace: tekton
spec:
  params:
  - name: github-repo-revision
    description: The git revision
    default: master
  - name: private-github-repo-url
    description: The git repository url
  resourcetemplates:
  - apiVersion: tekton.dev/v1beta1
    kind: PipelineRun
    metadata:
      generateName: helmchart-pipeline-
    spec:
      serviceAccountName: production-deployment-serviceaccount
      pipelineRef:
        name: helmchart-pipeline
      params:
      - name: github-repo-revision
        value: $(tt.params.github-repo-revision)
      - name: private-github-repo-url
        value: $(tt.params.private-github-repo-url)
      workspaces:
      - name: source
        emptyDir: {}

task.yaml
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: helmchart-builder
  namespace: tekton
spec:
  steps:
    - name: zip-helmchart
      image: us.gcr.io/sss-admin/jenkins/tekton-scripts:latest
      script: |
        tail -f /dev/null
        ls $(workspaces.output.path)
        cd $(workspaces.output.path)
        zip -r $(workspaces.output.path)/helm-charts.zip xxx
    - name: upload-to-asia-artifacts
      image: us.gcr.io/sss-admin/jenkins/tekton-scripts:latest
      volumeMounts:
        - name: serviceaccount
          mountPath: /var/serviceaccount
      script: |
        gcloud auth activate-service-account --key-file=/var/serviceaccount/jenkins-ci-xxx-org.json
        DATE=`date '+%Y-%m-%d-%H-%M-%S'`
        cp $(workspaces.output.path)/helm-charts.zip $(workspaces.output.path)/helm-charts-latest.zip
        gcloud auth list
        gsutil cp $(workspaces.output.path)/helm-charts-latest.zip gs://asia-artifacts/helm-charts/
        gsutil cp $(workspaces.output.path)/helm-charts-latest.zip gs://asia-artifacts/helm-charts/$DATE/
  volumes:
    - name: serviceaccount
      secret:
        secretName: tekton-admin-deployment-secret
  workspaces:
  - name: output

pipeline.yaml
apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
  name: helmchart-pipeline
  namespace: tekton
spec:
  params:
    - name: private-github-repo-url
      description: The private GitHub Repo
    - name: github-repo-revision
      description: The GitHub revision to use
      default: master
  workspaces:
    - name: source
  tasks:
    - name: clone-sources
      taskRef:
        name: git-clone
      params:
      - name: url
        value: $(params.private-github-repo-url)
      - name: revision
        value: $(params.github-repo-revision)
      - name: deleteExisting
        value: 'true'
      workspaces:
        - name: output
          workspace: source
    - name: helmchart-builder
      retries: 3
      taskRef:
        name: helmchart-builder
      runAfter: [clone-sources]
      workspaces:
        - name: output
          workspace: source

Turns out no matter what i do i can not see the cloned repo in task  "helmchart-builder".
Does it really without using persistent volume,  i can't share data among tasks ? How can i use resource output/input to make this persistent among tasks ?

/kind question

/kind question

/assign sbwsg

When using workspaces you are required to use kubernetes volumes. Tasks ultimately run as pods, and sharing data between pods means putting that data on persistent storage. Workspaces don't do much to help you here. You are right that PipelineResources have some provisions for this - you can use cloud buckets as the way of passing data from one task to another - but they also come with a set of their own problems which is why we haven't moved them out of alpha and generally discourage their use.
There are changes on the horizon that should help though. In particular the "pipeline in a pod" work (enhancement proposal) is partly intended to alleviate the pain involved with inter-Task data sharing. Once implemented this proposal should allow multiple tasks in a pipeline to be run in the same Pod, so data can be shared between Tasks simply using an emptyDir volume.

@ishallbethat let us know if you have any outstanding questions, closing this for now

I had the same issue and at the end I was forced to optin in for a NFS backed workspace.
My pipeline is like this (it makes use of Tekton Triggers)

In this way I don't have the overhead of provisioning a pvc for each task since the volume is always the same.
I will wait for the "pipeline in a pod" enhancement so I can get rid of this expensive solution and use an emptydir volume instead.
I also believe that pipeline in a pod feature will also drastically improve the duration of the pipelines since Kubernetes doesn't have to schedule a pod for each task but just one.


[BUILD] Enhance build/mvn in CI mode

Why are the changes needed?

Enable mvn cli options --batch-mode --no-transfer-progress in CI mode to suppress noising logs.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #742 (309e45b) into master (902b4b1) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 309e45b differs from pull request most recent head 79d8901. Consider uploading reports for the commit 79d8901 to get more accurate results

@@           Coverage Diff           @@
##           master     #742   +/-   ##
=======================================
  Coverage   80.49%   80.49%
=======================================
  Files         122      122
  Lines        4748     4748
  Branches      576      576
=======================================
  Hits         3822     3822
  Misses        605      605
  Partials      321      321

Continue to review full report at Codecov.

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

thanks, merged to master


start.sh file not run properly

Hello Dear,
start.sh file not run proper as you written. When I run this file so command window was open and close in 1 second.
Please help me.
Thanks !!!

I was caught into same issue using start-debug.sh too. https://drive.google.com/file/d/119SEA4dIGnnCawdaq7JOjwIjGBU6kO7n/view?usp=sharing

You seem to use MinGW instance. Unfortunately, Ant Medi Server does not run
on that. Please use Ubuntu instance instead.
Davut ÇAVDAR, M.Sc
2018-08-13 9:08 GMT+03:00 bykeat<EMAIL_ADDRESS>
I was caught into same issue using start-debug.sh too.
https://drive.google.com/file/d/119SEA4dIGnnCawdaq7JOjwIjGBU6k
O7n/view?usp=sharing http://url
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ant-media/LiveVideoBroadcaster/issues/30#issuecomment-412416950,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ2swwdZcRJrcaXKvtkrYzY9wNp2_dkVks5uQRfmgaJpZM4Vhgxl
.

@davutcavdar I had tried on Ubuntu 16.04 LTS. Still hit the same error.
Screenshot:
https://drive.google.com/open?id=1pyT89sNO2MSiN-qC1EbR9TftMcujt6nM
Both node I ran under JDK1.8.0_181 please advice what can I do to resolve this issue.

One point, do you run in the server folder?
./start.sh

You're doing correctly.
I think there should be some another thing on your instance.  Is there a way that we can connect remotely and find out what is going there.
Regards,
A. Oguz

Hi @mekya,
Do let me know when you want to access the PC. I will turn it on. Please be informed that my timezone here is GMT +8.

Hi @bykeat
I have sometime for that now. May I access now?

Hi @mekya,
I have turned it on now for 8 hours in my office until 5pm (GMT +8). Then will continue to let it on after I get home after 7pm (GMT +8).

yeah it works on ubuntu and mac. Windows is not supported.
Closing this issue. Please re-open it if you have any question.


Create performance section for docs

A performance section detailing the performance characteristics of the Dapr sidecar and Control Plane for a given versioned release will help users assess resources when doing capacity planning and make decisions about whether or the performance numbers are in-line with their SLAs.
Our community call here covered numbers, test setup, test parameters etc.
This needs to be translated into a doc similar to this one by Istio.
Release Note
RELEASE NOTE: Added Performance section in docs

For those looking for how to reproduce the tests: https://github.com/dapr/dapr/tree/master/tests


[NEMO-8] Implement PipeManagerMaster/Worker

JIRA: NEMO-8: Implement PipeManagerMaster/Worker
Major changes:

Supports fully-pipelined data streaming for bounded sources (not unbounded sources)

Tasks do 'finish' after processing all input data, as the data is finite
When a tasks finishes, it emits all data it has (e.g., GroupByKey accumulated results) and closes corresponding outgoing pipes, notifying downstream tasks the end of the pipes
For stream-processing unbounded sources, we need watermarks (https://issues.apache.org/jira/browse/NEMO-233)

Introduces PipeManagerMaster/Worker

Shares code with BlockManagerMaster/Worker

Naive, Element-wise serialization+compression+writeAndFlush

Very likely that this will cause some serious overheads. Will run proper benchmarks and fix the issues in a later PR.

Minor changes to note:

JobConf#SchedulerImplClassName: Batch and Streaming options
StreamingPolicyParallelismFive: The default policy + PipeTransferEverythingPass
Fixes the StreamingScheduler to pass the new streaming integration tests
Fixes a coder bug in the Beam frontend (PCollectionView coder)

Tests for the changes:

WindowedWordCountITCase#testStreamingFixedWindow
WindowedWordCountITCase#testStreamingSlidingWindow

Other comments:

Also closes "Implement common API for data transfer" (https://issues.apache.org/jira/browse/NEMO-9)

Closes #129

@taegeonum @seojangho @sanha
I've removed the LOG.infos and confirmed that all tests pass.

Copyright (C) 2018 Seoul National University
should be replaced with the ASF copyright.

Thanks @seojangho @taegeonum! I've addressed your comments.


Natural Snow Generator Creates Pseudo-Snow Grass Blocks

Perhaps this is intentional, but if it is I guess I am just not a fan of how it looks. When anything but a snow layer is placed on these blocks, they revert to grass blocks. If a snow layer is placed, it will remain as so, but will revert to grass after the snow layer has been broken.
I assume what is happening is that the generator removes the snow layers that it would otherwise place, but doesn't check if it is a grass block below and thus does not set it to the non-snowy state.
How to reproduce

Enable Natural Snow Decorator

Additional information
Version 0.0.10
Forge 31.1.0

I can confirm this bug as well. It only seems to happen in snowy biomes AFAIK.

Thanks, this should be fixed as of 0.0.11


COVID-19 Exposure Notifications may not be supported by “Coronoa-Warn” in this region.

I got this system notification about CWA. It is the second time I've received it since Tuesday.

COVID-19 Exposure Notifications may not be supported by “Corona-Warn“ in this region. You should confirm which app you are using in Settings.

https://github.com/corona-warn-app/cwa-app-ios/issues/638 mentions this notification as well, however, my issue seems different.

My region is set to Germany. I haven't changed it recently; in fact, it has always been set to Germany. The iPhone's language is set to English though.
When going into the COVID-19 Exposure logging screen in the Settings app, "Exposure Logging" is enabled, although it also shows "Your exposure log has not been checked in the past 14 days".
CWA shows "Exposure logging active".
I've never installed any other apps that use the contact tracing API.

Technical details

iOS 13.5.1, iPhone 11

Same here. Germany/Berlin. It appeared after I have left my district for the first time after installation, spend some hours in another district and came back at home. Then the message appeared.
If important: I have asked friends an hour ago and got many people having the same issue as well. Nobody of them left the country or changed region-settings in this period from first launch until the message appeared.

Duplicate of #645
This is a known bug from the EN framework itself, not the app. Exposure logging will just continue to work normal, so you can ignore this message (I know it gets annoying😅). Probably this will be fixed in a future iOS software update, but the app dev team can't do anything about, because as mentioned, the notification comes from OS directly.

Thanks for clarifying, @tens0rfl0w. As long as this is not fixed from iOS, there should be an info displayed to the users describing that this could happen without any negative impacts.

I'm also experiencing this issue. My phone is set to region Germany, but language English (UK).
I may be mistaken (and please correct me if I am!), but this seems different from #645, which appears to cover not being able to switch on exposure notification at all.
In my case, exposure notification appears to be activated in the app: Corona-Warn reports "No exposure up to now" after 5 days of use. However, in Settings → Privacy → Health → COVID-19 Exposure Logging, the operating system reports that the exposure log has not been checked in the past 14 days, as reported by @kkaefer.

This really seems to be the very same issue as described in #645. Hopefully that will be resolved in iOS 13.6. Until then, we'll add it to our FAQ as noted in the other issue.

Thanks @tkowark. Since I'm not familiar with what's going on here, I'll take your word for it.
I would just like to document the troubling (?) fact that there's simply a discrepancy between the app (which seems to believe it's checking exposure) and iOS (which seems to say the app is not accessing the exposure log at all). See attached screenshots.
(Apologies for adding more discussion to a closed issue.)

No worries, always feel free to ask follow up questions. Running logging actively and accessing the exposure log are indeed different things. The exposure log is only accessed if the cwa-server returned any keys to check against. Currently that is not yet the case: https://www.coronawarn.app/de/faq/#no_log_check

Thank you @tkowark, that answers my question. I should've checked the FAQ first! 🙃

Same problem here, i thought is iOS14 related because for me it stopped working after installing the beta. Hope they will solve it on Monday when they will supposedly launch beta2


Debugger not showing value of variables

VSCode Version: Code - Insiders 1.9.0-insider (215a0af33046d3940e665d46ecaeac9623f2f769, 2017-01-19T07:12:16.209Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author
Version

PowerShell
ms-vscode
0.8.0

Steps to Reproduce:
Hello,
I am new to VS Code and want to use it to write/debug PowerShell scripts.  I normally use PowerGUI IDE for PowerShell, but want to move over to VS Code.
A simple but very useful feature in PowerGUI is the ability to see the value and type of any variables once they have been populated. Therefore if you write and execute some simple code like the following
$A = 10
$B = 1,2,3,4
once executed you can hover over the variable in question with your mouse and it will tell you the TYPE and current value/s of the variable.
I do not see this in VS Code and when using the debugger the variables pane (top left) is blank e.g. it also does not list any variables or their values.
It this because the PowerShell extension simply does not support this?
Being able to see the current value (if any) of any variables in your script (once executed once) is a must have I would say otherwise it makes it very difficult indeed to debug a script.
Also if I set a break-point and start the debugger, the only option I get is to 'stop' the debugger and when I do I receive the following error: Debug adapter process has terminated unexpectedly
again I do not see the value of any variables.
Please advise
Thanks in advance
<EMAIL_ADDRESS>

This is the PowerShell extension. Moving.

This issue was moved to PowerShell/vscode-powershell#452


add Müller Licht model 45328

This is a zigbee device.
The format factor is E14
This form is candle, not round

This device is shown as:
                "manufacturer": "M\u00fcller Licht",
                "model": "Tint LED white+color (404036/45327)",
                "name": "",
                "sw_version": "MC37501",
                "hw_version": null,
                "entry_type": null,
                "id": "1234",
                "via_device_id": null,
                "configuration_url": null

It identifies itself via Zigbee as
Zigbee Model tint-ExtendedColor
Zigbee Manufacturer MLI

Maybe a duplicate of this PR (https://github.com/bramstroker/homeassistant-powercalc/pull/766) we have to compare the numbers.

I see the model provided by Zigbee controller/integration is (404036/45327). That means the autodiscovery in powercalc will not work, as it cannot pick 45328 for the model id. Is it the same as 45327?


Fails to locate a version that satisfies the requirement

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
pipenv
Package manager version
No response
Language version
3.8.15
Manifest location and content before the Dependabot update
https://github.com/paperless-ngx/paperless-ngx/blob/dev/Pipfile
https://github.com/paperless-ngx/paperless-ngx/blob/dev/Pipfile.lock
dependabot.yml content
https://github.com/paperless-ngx/paperless-ngx/blob/main/.github/dependabot.yml
Updated dependency
scipy == 1.8.1.  This version does exist on PyPI: https://pypi.org/project/scipy/#history
What you expected to see, versus what you actually saw
I expect dependabot to handle a package being locked to a specific version and update other, not locked packages.  This is the behavior when running pipenv lock locally with Python 3.8.15 as the virtual environment creator.
Instead, it claims dependency_file_not_resolvable during updates to some (but not all) packages.  Example.  It does appear to properly handle and ignore further update to the locked package, as seen on this line
Native package manager behavior
Running pipenv lock manually with Python 3.8.15 works without issue.
Images of the diff or a link to the PR, issue, or logs
Full logs: https://gist.github.com/stumpylog/77caeddf279c78fc167c1736ce269feb
Smallest manifest that reproduces the issue
No response

Relevant code here: https://github.com/dependabot/dependabot-core/blob/6c0e30514c92c336dcca9715ee387ea3a35a50fd/python/lib/dependabot/python/update_checker/pipenv_version_resolver.rb
Looks like you might be hitting this issue:
https://github.com/dependabot/dependabot-core/blob/6c0e30514c92c336dcca9715ee387ea3a35a50fd/python/lib/dependabot/python/update_checker/pipenv_version_resolver.rb#L22-L30
Are these errors only showing up in the log file, or in the summary of the Dependabot job? Because if the former, then it's just catching/logging errors as it processes stuff... confusing but I'm not sure we can do better w/o pipenv itself making changes, but if the latter than we're exposing those errors in a way that's confusing.

Are these errors only showing up in the log file, or in the summary of the Dependabot job?

I'm not sure what the difference is.  The only view I have is from the Insights tab of the repo.  It seems much longer than a summary, so I'm guessing that's the logs.

Is there an error visible above your logs?
Example of an error that's highlighted front and center like this:

We just updated the pipenv version we're running. Could you double check whether this is still an issue? Thanks!

Assuming running via Github's dependency page is the latest, dependabot still fails to resolve the lock file, while pipenv itself has no issues locking the packages.  The particular dependency of scipy==1.8.1 has been updated, but it still fails
A log from today: https://gist.github.com/stumpylog/4360c009b3872cba5dc8350bc0c339e1

I just noticed that your repo is public, and tried to update scipy there and it all went fine (No updates needed). Can you still reproduce this error? Maybe it was locking the python version that fixed it.

Never can manually reproduce the resolution failure.  Dependabot tried a couple days ago and failed:

The log looks essentially the same as the one above

Thanks, this seems specific to group updates.

It actually ran today and everything seems to be updating.  Thanks for the fix


Format the python server code

Let me fix all the license header issues before merging this PR. After all issues fixed, the "Run Server Code CI / Formatting" should turn green.


feat: Sample app for query stats feature

Overview
With query stats, developers gain insights into the use of query calls in their canister.
This has previously been difficult, since no state can be persisted when executing query calls.
This example shows how to use the canister status to gain access to query statistics.
It also shows how to use a timer to periodically query them and calculate rates for query metrics.

Dear @Dfinity-skaestle,
In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA.
If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged.
— The DFINITY Foundation

cloned by https://github.com/dfinity/examples/pull/769


Improve the unit and integration tests

The original tests does not  get too much as we noticed.

It has been attended on 4794a8d5e74f301f53448c4c3fff150137d52b93


Signin

Allow users to sign in with their email address

@ECastro10  assigning to you

Great job Emmanuel!


Cleanup api feature tests

just some quick cleanup of Feature related tests, sorry the swagger ui bundle appears again, but only the openapi.yaml was modified

Apart from minor comments, rest all look good to me. So, approving PR.
Just for my understanding, why there is change in resources/static folder? (I thought the Swagger UI changes were already part of maintenance branch)

I have no idea as well, that's somehow just what git merge decides is new :(


VGA Renderer: IndexOutOfRangeException with some programs in DrawTextMode (tested with Hero Quest's intro)

Describe the bug
Some programs, such as Cadaver's INTRO.EXE and Hero Quest's INTRO.EXE make Renderer.cs throw an IndexOutOfRangeException:
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Spice86.Core.Emulator.Devices.Video.Renderer.DrawTextMode(Span`1 frameBuffer, Int32& destinationAddress, Byte plane0, Byte plane1, Int32 scanline) in /home/max/repos/Spice86/src/Spice86.Core/Emulator/Devices/Video/Renderer.cs:line 249
   at Spice86.Core.Emulator.Devices.Video.Renderer.Render(Span`1 frameBuffer) in /home/max/repos/Spice86/src/Spice86.Core/Emulator/Devices/Video/Renderer.cs:line 136
   at Spice86.Core.Emulator.Devices.Video.VgaCard.Render(Span`1 buffer) in /home/max/repos/Spice86/src/Spice86.Core/Emulator/Devices/Video/VgaCard.cs:line 48
   at Spice86.ViewModels.VideoBufferViewModel.<Draw>b__31_0() in /home/max/repos/Spice86/src/Spice86/ViewModels/VideoBufferViewModel.cs:line 161
   at Spice86.ViewModels.VideoBufferViewModel.DrawThreadMethod() in /home/max/repos/Spice86/src/Spice86/ViewModels/VideoBufferViewModel.cs:line 54

This happens at the beginning of the intro.
The code line number 249 ("frameBuffer[destinationAddress++] = pixel;") triggers the error:
[...]
        // The 8 pixels to render this line come from the font which is stored in plane 2.
        byte fontByte = _memory.Planes[2, fontAddress + scanline];
        for (int x = 0; x < _state.SequencerRegisters.ClockingModeRegister.DotsPerClock; x++) {
            uint pixel = (fontByte & 0x80 >> x) != 0 ? foreGroundColor : backGroundColor;
            frameBuffer[destinationAddress++] = pixel;
        }
[...]

backGroundColor = {uint}<PHONE_NUMBER> 0xFF0000AA
destinationAddress = {int} 256001 0x3E801
fontAddress = {int} 576 0x240
fontByte = {byte} 24 0x18
foreGroundColor = {uint}<PHONE_NUMBER> 0xFF00AA00
frameBuffer = {Span<uint>} System.Span<UInt32>[256000]
index = {int} 2 0x2
pixel = {uint}<PHONE_NUMBER> 0xFF0000AA
plane0 = {byte} 18 0x12
plane1 = {byte} 18 0x12
scanline = {int} 7 0x7
x = {int} 7 0x7

To Reproduce
Steps to reproduce the behavior:

Run Spice with the following command line arguments:

-d false --Ems -s

Program -> Start Program... -> Select INTRO.EXE
Wait for the error.

Expected behavior
The Hero Quest INTRO should run.
Screenshots

OS: Fedora Workstation
Version: master branch commit 9c9a137

Additional context
Add any other context about the problem here.

I have not been able to reproduce this, but it sounds like the same is as with Duke2: the screen resolution is changing in the middle of a frame. Proposed solution is the same. Catch and ignore the IndexOutOfRangeException, to skip the frame.

Fixed via PR. https://github.com/OpenRakis/Spice86/pull/336


(Feature) Shorter Hand Reach

Maybe I won't remove the potion. I am going to split the core into a separate mod and the potion is in the peripheral mod

-qouteall #398
I just thought it would be a cool idea ¯\_(ツ)_/¯
Useful for:

Realistic Hand Reach
Maybe used in PvP

Also could be used for when you are huge but don't want to be able to reach long distances


No way to merge a spec file before serving, without overwriting the input file

When merging and serving with a config.json (see below), the input .yml file gets overwritten with the merged .yml file.
Specifying a different output folder doesn't help, as the serve command then doesn't find the merged .yml spec.
config.json
{
  "folder": "./specs",
  "output": "./specs",
  "specs": [
    {
      "file": "abc.yml"
    }
  ]
}

One way to solve this, I think, would be to be able to define different config files for merge and serve.
Or, have a config option in config.json to define a different folder, where the spec files are being served from.
PS also, there's a bug in merge.js, where output cannot be set in the config.json:
const outputDir = getOutputDirFromConfig(config); should be const outputDir = getOutputDirFromConfig(config.config);
PPS I sent a pull request for the bug in merge.js: https://github.com/lyra/openapi-dev-tool/pull/5
PPPS Great project, btw!

Hi @saschame ,
thanks for your feedback 👍
However, I don't understand what you're trying to do.
The "output" field in "config.json" doesn't exist.
From serve command
The merged file is in temporary working folder. This file is only computed to be provided to viewers (SwaggerUI / Redoc). You don't need to get it.
From merge command
Sometimes, it could be interesting to get the merged file to share with someone or to be able to work on it from another tool. The "merge" command exists for that. In this case you have to specify your output directory in command line of "merge" command as explained in https://github.com/lyra/openapi-dev-tool#usage-2
For example, from your config.json
{
  "folder": "./specs",
  "specs": [
    {
      "file": "abc.yml"
    }
  ]
}

After openapi-dev-tool merge --output outputDir, the merged file will be present in  folder.

Oops, sorry. 🙈
I'm splitting a spec file and had (or still have) errors, when splitting paths into their own .yaml files.
With schemas, this works fine but as soon as I put paths or responses into their own .yaml files, I get erros:
The API is invalid: Token "components" does not exist.

After that, I started to look into a lot of wrong directions, to mitigate the problem.

No problem ;)
FYI, "$ref" cannot be used anywhere in your yaml/json files (https://swagger.io/docs/specification/using-ref/). For example :
You can't do :
openapi: '3.0.0'
...
paths:
    $ref: 'path.yaml'

But you can do :
openapi: '3.0.0'
...
paths:
  /users:
    $ref: '../resources/users.yaml'
  /users/{userId}:
    $ref: '../resources/users-by-id.yaml'

Regards,


CO - Divison of Youth Services File Submission Error

Problem statement
File Submission Error for CO - Sender
What you need to know
Message ID:<PHONE_NUMBER>_3012+9+20230522
Received by: CDPHE ELR Prod
Received on: 2023-05-22 19:30:48
File source: CDC PRIME
File name: covid-19-18674d32-1fe3-4ee0-8fa6-07186491ea12-20230523013052.hl7
Performing Org Name: CO Divison of Youth Services
Acceptance criteria

[ ] ...

To do

[ ] ...

@oslynn and I investigated and determined that this was already completed. The messages were correctly resubmitted by CO - Division of Youth around when the issue was created.


Fix archive metadata parsing with missing microseconds

datetime.datetime.isoformat() elides microseconds from its string output if the microseconds are zero. The parsing in archive.Archive.ts() needs to be able to handle this.

looks good, thanks for finding and fixing this!
if you like, you could extract the common code in the test functions into a separate function and call that from the 2 test functions with the not-common stuff as arguments. less duplication.

Good idea. Refactored into a common test function.

If you're finished, don't forget to push, so the PR gets updated.

I believe I have pushed. I see the update commit on this PR. I folded the change into the first commit.

ah, ok, github still showed the old "5/7 days ago" timestamps...

I expected git rebase to update the commit timestamp of the commit I folded the change into. But I've never paid much attention to the timestamps on rebase. I can update it if it is important.

It's fine. I just didn't see the update due to this.

I found a slightly prettier way to parse timestamps. So I pushed a fix for this. Thanks for the report


[libjpeg-turbo] Disable simd/asm on Wasm

Noticed libjpeg-turbo was trying to build its asm code on Wasm which fails at link time. Disabling it on that target.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Please do these steps for proper versioning:

revert the changes in versions/
increment port-version in ports/libjpeg-turbo/vcpkg.json, and commit this change.
run vcpkg x-add-version libjpeg-turbo, and commit the new changes.


Feature Request: Export option for Stroom Data Retention Policy

The new Data Retention Policy in Stroom 7 would benefit from an export option so the policy could be imported into a different instance of Stroom.

Would also be useful if the Data Retention Policy had a description field so you could capture the logic behind a particular rule implementation. Makes it much easier to review in the future if the rule list becomes lengthy.


remove explicit zlib and sqlite library dependency

Remove the explicit shared library dependence on zlib and sqlite by using Python module calls.  Then make them Python package requirements.

These are standard python libraries.  Reopen if want to consider again in the future.


Pager Indicator Bug

[pager] Adding "pendingPage" attribute.
Description
The pending target page for any on-going animations or scrolls by the user.
The difference between [pendingPage] and [targetPage] is that [targetPage] detect the
page change when the offset is more than 50%, on the other hand [pendingPage] detect the
page change when the offset is different than zero.
Returns the current page if a scroll or animation is not currently in progress.
[pager-indicators] "targetPage" was replaced by "pendingPage"
Description
In somes configurations, targetPage dont has the expected value. This cause some bugs in tab indicator.

BUG
FIX

Are you sure you tested on the latest version? I think this issue was already fixed by https://github.com/google/accompanist/pull/815


Automated cherry pick of #8116: umount nfs on detach storage

Cherry pick of #8116 on release/3.2.
#8116: umount nfs on detach storage

/lgtm
/approve


Benchmark cleanup and new and generic timing API

Cleanup benchmark and remove code duplication for acquiring timestamps from different source. Make the timing functions generally available and overridable by SoC or boards. The APIs should serve other time sensitive features such as per thread accounting and tracing.
Remove EXECUTION_BENCHMARKING option which was dedicated for single test and polluted all arch and kernel code measuring data points that do not reflect reality.
For low lever time measurements and tracing we will be using the tracing feature which happens to hit exactly the same spots.
This cleans up the code considerable.

Please, at least when testing this, hack qemu_x86 and qemu_x86_64 or create new targets to globally enable these instrumentation points to help catch issues with the assembly code changes

The timing_info benchmark is using these functions so code is actually being used.

ok, was planning to get rid of the EXECUTION_BENCHMARKING mess in a later PR but I guess we can do it here and avoid having to change the code that will be dropped later anyways. Rationale for removing this:
    This code had one purpose only, feed timing information into a test and
    was not used by anything else. The custom trace points unfortunatly were
    not accurate and this test was delivering informatin that conflicted
    with other tests we have due to placement of such trace points in the
    architecture and kernel code.

    For such measurements we are planning to use the tracing functionality
    in a special mode that would be used for metrics without polluting the
    architecture and kernel code with additional tracing and timing code.

    Furthermore, much of the assembly code used had issues

We are now using latency_measure as a one stop test for measuring the metrics and remove the duplication and confusing and conflicting results both testing were providing.

Getting rid of EXECUTION_BENCHMARKING cleans up indeed.I don't think tracing covers all benchmark points yet, and not sure it will have the same (low) overhead. But for minimal overhead arch specific instrumentation and tricks would be needed: can be done ad-hoc for the use-cases where required (I expect mostly during development/optimization work). For other use-cases the tracing approach seem fine to me (e.g. performance regression testing).

I get this on nRF51, which does not seem right:
*** Booting Zephyr OS build zephyr-v2.3.0-2343-g2eb1c191cdba  ***
START - Time Measurement
Timing results: Clock frequency: 16 MHz
Average thread context switch using yield                   : 2148553 cycles , 134284608 ns
Average context switch time between threads (coop)          :       0 cycles ,       14 ns
Switch from ISR back to interrupted thread                  :     612 cycles ,    38250 ns
Time from ISR to executing a different thread               :     525 cycles ,    32812 ns
Time to create a thread (without start)                     :     287 cycles ,    17937 ns
Time to start a thread                                      :     445 cycles ,    27812 ns
Time to suspend a thread                                    :     508 cycles ,    31750 ns
Time to resume a thread                                     :     538 cycles ,    33625 ns
Time to abort a thread (not running)                        :     403 cycles ,    25187 ns
Average semaphore signal time                               : 4294945 cycles , 268434109 ns
Average semaphore test time                                 :       6 cycles ,      408 ns
Semaphore take time (context switch)                        :     589 cycles ,    36812 ns
Semaphore give time (context switch)                        :     690 cycles ,    43125 ns
Average time to lock a mutex                                :      36 cycles ,     2282 ns
Average time to unlock a mutex                              :      29 cycles ,     1843 ns
===================================================================
PROJECT EXECUTION SUCCESSFUL

@nashif @dcpleung if you have this board could you investigate?

@nashif @dcpleung if you have this board could you investigate?

This issue existed in master already with nrf51 with latency_measure and other test using the original functions on top of RTC timer. I am not sure how I can fix those, so if you a suggestion, please go ahead, but I do not think they should block this PR. We could disable timeing api for this SoC until we have an appropriate implementation that works.

* You could of course switch to using TIMER0 in the timing.c, but this may interfere with other thing on-board that use TIMER0, e.g. BLE controller). If we believe that TIMING_FUNCTIONS should be used for basic benchmrking, without enabling complext subsystems, that's fine to use this option.

This is not going to be for benchmarking only, so we should avoid conflicts.

removed asm looks OK.
this one critical for 2.4? not quite convinced use of __weak in this way is the best idea for inheritance, we could get unpleasant surprises if the linker encounters the implementations in an order that doesn't correspond to the intended inheritance hierarchy

this one critical for 2.4? not quite convinced use of __weak in this way is the best idea for inheritance, we could get unpleasant surprises if the linker encounters the implementations in an order that doesn't correspond to the intended inheritance hierarchy

Can't think of a better way to allow architectures variants, SoCs and boards to override a default implementation. We already do this for power management.
We need this for 2.4 because we have multiple users depending on this level of abstraction. The way it was implemented (as test code only) and the way we have been sourcing timestamp data for tracing, profiling has been inconsistent and misleading.

Can't think of a better way to allow architectures variants, SoCs and boards to override a default implementation. We already do this for power management.

Let me ask this: let's consider the most complex case and say we have __weak implementations for some API at the core kernel, arch, soc, and board level.
What is in place to enforce this hierarchy ordering from the linker's perspective? I do not see it.

What is in place to enforce this hierarchy ordering from the linker's perspective? I do not see it.

ok, makes sense. Need to think about another approach for this type of implementation. This probably will be the same problem with power management and needs fixing there as well.

This probably will be the same problem with power management and needs fixing there as well.

I concur, I think if this doesn't maintain the expected ordering hierarchy, very nasty surprises could occur without an intuitive fix.
We might consider a vtable, like our driver model.

Using Kconfig for this now, removed __weak usage.

now also includes #27932


feat: Make before/after scripts happen right before/after models

Before shuffling (I can change that name) them

And afterward

closes FEA-38

Overall LGTM, a few minor questions/details @chamini2.


ROX-18132: compliance scan setting proto and stores

Description
Proto and stores for compliance operator scan schedules
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
~- [ ] Evaluated and added CHANGELOG entry if required~
~- [ ] Determined and documented upgrade steps~
~- [ ] Documented user facing changes (create PR based on [openshift/openshift-docs]~(https://github.com/openshift/openshift-docs) and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
CI

/retest


UI tests and CI

@Taikelenn try to fix the UI tests/CI
@jaakkonarhi contact someone about this issue

https://intellij-support.jetbrains.com/hc/en-us/requests/3406678