(Feature)Planner: core and service update, matchmaker bugfix

@rosogon can you review this please?
In order to test it be sure to have a running discoverer and sla-core and provide their urls to the planner configuration.
The PR fixes a bug in the matchmaker, provide an updated version of the dam generator with monitor and sla generators and improves DAM conformance.
@andreaturli: in order to be deployed the bom must be changed. Since you asked me to not update the bom, please contact me if you need help updating it.

I get this exception with a wrong file.
 Please, try this:
curl -X POST http://localhost:1234/planner/plan -d@"planner/aamwriter/src/main/resources/examples/web-chat_a am.yml"
The exception (once avoid the NPE) is :
ERROR [2015-11-26 17:16:58,956] eu.seaclouds.platform.planner.service.PlanResource: Context: null
Problem: mapping values are not allowed here
Note: null
Start: null
End  : null
! alien4cloud.tosca.parser.ParsingException: Context: null
! Problem: mapping values are not allowed here
! Note: null
! Start: null
! End  : null
! at alien4cloud.tosca.parser.YamlParser.parseFile(YamlParser.java:76) ~[planner-service-0.8.0-SNAPSHOT.jar:na]

! at alien4cloud.tosca.parser.YamlParser.parseFile(YamlParser.java:50) ~[planner-service-0.8.0-SNAPSHOT.jar:na]

! at alien4cloud.tosca.parser.YamlParser.parseFile(YamlParser.java:37) ~[planner-service-0.8.0-SNAPSHOT.jar:na]

! at eu.seaclouds.common.tosca.ToscaSerializer.fromTOSCA(ToscaSerializer.java:82) ~[planner-service-0.8.0-SNAPSHOT.jar:na]
! at eu.seaclouds.platform.planner.core.Planner.plan(Planner.java:150) ~[planner-service-0.8.0-SNAPSHOT.jar:na]

with web-chat_aam.yml AAM i get these ADPs

@szenzaro I think you have to change the seaclouds-planner item in the bom file. I asked you to not modify the applications inside the bom, that use the items.
It is really important that the PRs follow strictly our CONTRIBUTING guide. In particular, each developer MUST run 'mvn verify -pl qa -Pintegration' as unfortunately travis cannot do that reliably.
I think we should publish the result of that 'mvn verify' - maybe in the description of each PR - otherwise the PR will be automatically rejected.
What do you think @kiuby88 @MicheleGuerriero @rosogon @adriannieto @PaoloCifariello @perezp?

I think it's a good way to be sure that everything is OK.
By the way I'm going to enable health checks on  the dashboard, this means that if an endpoint is failing dropwizard will not start, but to achieve this I need to be sure that at least we get everything on green at deployment time.
El 27 nov. 2015 7:07 a. m., Andrea Turli<EMAIL_ADDRESS>escribió:@szenzaro I think you have to change the seaclouds-planner item in the bom file. I asked you to not modify the applications inside the bom, that use the items.
It is really important that the PRs follow strictly our CONTRIBUTING guide. In particular, each developer MUST run 'mvn verify -pl qa -Pintegration' as unfortunately travis cannot do that reliably.
I think we should publish the result of that 'mvn verify' - maybe in the description of each PR - otherwise the PR will be automatically rejected.
What do you think @kiuby88 @MicheleGuerriero @rosogon @adriannieto @PaoloCifariello @perezp?
—Reply to this email directly or view it on GitHub.

@szenzaro : You are right. My fault. That's why REST interfaces should log their inputs ;)
I'll test it again.

Hi @szenzaro : I finally got the ADPs :)
Please, how do I test now the DAM Generation?

@rosogon POST /damgen with the ADP in body or GET /damgen with adp as query parameter

+1: Generates ADPs and DAMs. I assume the DAM generation will need to be polished in a later PR. @szenzaro : please, squash into 1 commit.

@rosogon done. Thank you.


Change andHaving to andWhere for consistency

Change andHaving to andWhere for consistency -- we use andWhere elsewhere in the code (getCount) to filter results to the user's own accessible organizations. I believe in this case, either will have the same effect.

Merged into #940.


Switching Vert.x app to RestEasy Reactive, fails debugging session

I have a patch that ports the Vert.x test app to contemporary Quarkus 3.x suggested API, RestEasy Reactive.
quarkus_3.x.reactive.patch.txt
It fails debugging session:
"Cannot execute this command while the selected thread is running"
[ERROR] Failures:
[ERROR]   DebugSymbolsTest.debugSymbolsQuarkusContainer:396->carryOutGDBSession:501 There were errors in the GDB session. Note that commands in the session might depend on each other. Errors:
Command 'bt' did not match the expected pattern in time '.*at org/acme/vertx/Fruit.java:48.*'.
Output was:
"bt
""Selected thread is running.
"^error,msg="Selected thread is running."(gdb) ,
Command 'list' did not match the expected pattern in time '.*48.*return client.query\("SELECT id, name FROM fruits ORDER BY name ASC.*'.
Output was:
"list
""1     org/graalvm/compiler/replacements/BoxingSnippets.java: No such file or directory.
"^done(gdb) ,
Command 'c&' did not match the expected pattern in time '.*Continuing.*'.
Output was:
"c&
""Cannot execute this command while the selected thread is running.
"^error,msg="Cannot execute this command while the selected thread is running."(gdb)  ==> expected: <true> but was: <false>
[INFO]
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0

Hello, @zakkak, I will use our version support in GDBSession class to create a compatible debug flow, but I wonder what would be expected here. Do I list threads and select the one that hit the breakpoint or can I tell that to gdb to do it automatically? :(
https://sourceware.org/gdb/current/onlinedocs/gdb.html/All_002dStop-Mode.html

@Karm I am not sure I get what the issue is.
My understanding of the error you are seeing is that another comment failed earlier. We should only issue bt after we expect the app to hit a breakpoint.
If you set a breakpoint and it's reached gdb automatically selects the thread that hit the breakpoing if I am not mistaken so there is nothing special to do.

@Karm You can use commands gdb command to run something based on a set breakpoint number. See: https://sourceware.org/gdb/current/onlinedocs/gdb.html/Break-Commands.html


Cannot get property 'link' of undefined.

info: The url return a wrong status code. Maybe the website is down for the moment.
info: [object Object]
(node:1001) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'link' of undefined
    at Object.stream (/home/runner/ahega0/node_modules/@justalk/anime-api/src/animeland/search.js:32:74)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Promise.all (index 0)
    at async Object.stream (/home/runner/ahega0/node_modules/@justalk/anime-api/src/index.js:35:13)
    at async Command.callback [as _callback] (/home/runner/ahega0/commands/ani.js:30:18)
(node:1001) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1001) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
info: The url return a wrong status code. Maybe the website is down for the moment.
info: [object Object]

Code I am calling:
const stream = await animeapi.stream('naruto shippuden', 387);

const embed = new MessageEmbed()
.setColor('#FFB6C1')
.setTitle(`Results for Naruto Shippuden | Episode 100`)
.setDescription(stream);

I has a sumilar issue
{} // this is the response I get from video
info: The url return a wrong status code. Maybe the website is down for the moment.
info: [object Object]

the code I'm using is:

const animeapi = require("@justalk/anime-api");
const video = animeapi
.download("black clover", 100)
.then((video) => video)
.catch((error) => error);
return video;

Welcome to this project,
I will look at it. The problem is some of those websites change quite often their dns origin, so it's a bit hard to keep up with them.


[WIP] Update dependencies

HikariCP 2.6.3 -> 2.7.2
finagle-mysql 7.0.0 -> 7.1.0
finagle-postgres 0.4.2 -> 0.4.3
orientdb-graphdb 2.2.21 -> 2.2.29
scalatest 3.0.3 -> 3.0.4
Checklist

[ ] Unit test all changes
[x] Update README.md if applicable
[x] Add [WIP] to the pull request title if it's work in progress
[ ] Squash commits that aren't meaningful changes
[ ] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

Oops, didn't notice [WIP] :)
Feel free to open new PR if this one wasn't finished

@mentegy all ok, thanks for merge. Usually i set [WIP] until travis tests wouldn't be green.


resolve error if  "Server provided by Martin 'd0wn' Albus"

Hello,
if I am useing server from d0wn, than some websites (e.g. wiki.debian.org) could not resolve. I am useing following setup:
pi-hole on port 53 with server <IP_ADDRESS>#40 and <IP_ADDRESS>#41, dnssec enabled
dnscrypt-proxy port 40 and 41
My local domain is .zz
If I use another server from d0wn, than I have the same problem. If I use a server from another person, that all works fine.
So maybe someone can help me, so that I can use the server from d0wn?
Sorry If that is the wrong place, it's my first issue.

Hi,
debian.org is signed, and maybe this doesn't work reliably with dnsmasq (or at least with whatever version pi-hole ships with).
Can you resolve dnscrypt.org?

Hey,
that's it! Thank you so much. If I disable dnssec in dnsmasq,  it works and I am able to resolve dnscrypt.org and other signed sites.  Now I try to found the "real" error. Thank you so much!


HDFS-17217. Add lifeline RPC start up log when NameNode#startCommonServices

Description of PR
https://issues.apache.org/jira/browse/HDFS-17217
If start up the lifeline RPC server in NameNode and need add lifeline RPC start up log when NameNode#startCommonServices

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

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.

+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 30s

trunk passed

+1 :green_heart:
compile
1m 25s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
1m 22s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 14s

trunk passed

+1 :green_heart:
mvnsite
1m 30s

trunk passed

+1 :green_heart:
javadoc
1m 10s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 40s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 22s

trunk passed

+1 :green_heart:
shadedclient
35m 22s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 11s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
1m 14s

the patch passed

+1 :green_heart:
compile
1m  9s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
1m  9s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  3s

the patch passed

+1 :green_heart:
mvnsite
1m 17s

the patch passed

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 27s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 17s

the patch passed

+1 :green_heart:
shadedclient
35m 41s

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

_ Other Tests _

+1 :green_heart:
unit
219m 12s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 51s

The patch does not generate ASF License warnings.

357m 42s

Subsystem
Report/Notes

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

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

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

uname
Linux 354c82f069a0 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 116ff0747aa3b85338a10b33850ac4d557b6fc39

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Hi @slfan1989 @zhangshuyan0 @tomscut please help me review it again when you have free time. Thanks a lot~

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

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.

+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 39s

trunk passed

+1 :green_heart:
compile
1m 25s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
1m 23s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 14s

trunk passed

+1 :green_heart:
mvnsite
1m 29s

trunk passed

+1 :green_heart:
javadoc
1m  6s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 39s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 19s

trunk passed

+1 :green_heart:
shadedclient
36m 14s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 18s

the patch passed

+1 :green_heart:
compile
1m 20s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
1m 20s

the patch passed

+1 :green_heart:
compile
1m 15s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
1m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  7s

the patch passed

+1 :green_heart:
mvnsite
1m 22s

the patch passed

+1 :green_heart:
javadoc
1m  0s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 30s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 31s

the patch passed

+1 :green_heart:
shadedclient
36m 54s

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

_ Other Tests _

-1 :x:
unit
220m 48s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 56s

The patch does not generate ASF License warnings.

361m 53s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.fsdataset.impl.TestFsDatasetImpl

Subsystem
Report/Notes

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

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

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

uname
Linux 3da39de11270 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5f5a1ecddd8c4efeaabacd2941c9fb6cad2d6ba6

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 28s

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.

+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
31m 38s

trunk passed

+1 :green_heart:
compile
0m 55s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
0m 50s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 47s

trunk passed

+1 :green_heart:
mvnsite
0m 58s

trunk passed

+1 :green_heart:
javadoc
0m 50s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 15s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
2m  0s

trunk passed

+1 :green_heart:
shadedclient
22m 11s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 45s

the patch passed

+1 :green_heart:
compile
0m 48s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
0m 48s

the patch passed

+1 :green_heart:
compile
0m 43s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 43s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 34s

the patch passed

+1 :green_heart:
mvnsite
0m 50s

the patch passed

+1 :green_heart:
javadoc
0m 39s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m  5s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m 53s

the patch passed

+1 :green_heart:
shadedclient
21m 54s

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

_ Other Tests _

+1 :green_heart:
unit
194m 56s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

287m 53s

Subsystem
Report/Notes

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

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

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

uname
Linux 1762f88ad65c 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / e5a0024c1d8913ca32db6ee84b4a4a20e4b39854

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

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

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

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

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.

+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
45m  6s

trunk passed

+1 :green_heart:
compile
1m 19s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
1m 19s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 13s

trunk passed

+1 :green_heart:
mvnsite
1m 20s

trunk passed

+1 :green_heart:
javadoc
1m 11s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 40s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 13s

trunk passed

+1 :green_heart:
shadedclient
35m 18s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m  9s

the patch passed

+1 :green_heart:
compile
1m 15s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
1m 15s

the patch passed

+1 :green_heart:
compile
1m  9s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
1m  9s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m  0s

the patch passed

+1 :green_heart:
mvnsite
1m 17s

the patch passed

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
1m 29s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 12s

the patch passed

+1 :green_heart:
shadedclient
35m 41s

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

_ Other Tests _

+1 :green_heart:
unit
219m 32s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 56s

The patch does not generate ASF License warnings.

361m  6s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6154/4/artifact/out/Dockerfile

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

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

uname
Linux 6efe8168e215 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 1ef4c8278613c4ab06680957362f29b844a5b86c

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6154/4/testReport/

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

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6154/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Thanks @zhangshuyan0 @slfan1989 @tomscut help me review and merge it.


add outro properties to article graph query

Ref #3363
Adds the outro fields to the GraphQuery.
Seems to be working. Just add ?toggles=outro:true and refresh.

@davidpmccormick it was put in as a WIP to be continued with.
I haven't actually done any extensive checking on this.


"Discovered accessory on network" but "Could not register accessory, skipping"

I have 4 key lights in my office, 2 at my computer, and 2 at my writing desk.
All 4 are seen, but cannot be registered.
This is what I see in the HB log:
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Discovered accessory on network: Elgato Key Light Air 70D3
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Could not register accessory, skipping Elgato Key Light Air 70D3

[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Discovered accessory on network: Writing Desk Left
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Could not register accessory, skipping Writing Desk Left

[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Discovered accessory on network: Elgato Key Light Air Left
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Could not register accessory, skipping Elgato Key Light Air Left

[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Discovered accessory on network: Writing Desk Right
[3/3/2022, 7:18:54 AM] [Elgato Key Lights] Could not register accessory, skipping Writing Desk Right

I have rebooted HomeKit.
I have rebooted the key lights and made sure they are on the latest firmware.
I can access them via "http://ip.address.of.keylight:9123"
I installed Homebridge specifically for this. Any help would be appreciated.

Do you have any kind of "special" network equipment, like a Ubiquiti Dream Machine or an USG?
This kind of error is usually seen when the mDNS resolution is not working correctly.
Can you try and check what happens if you enable the UseIp setting in the plugins configuration?

Ooh! That did it. Thanks! I have an eero set for my network, maybe that did it. IP did the trick. Thanks!


luigi.toml file generating error with 2.8.11, but works with 2.8.9

My luigi.toml file is just this...
[logging]
version = 1.0
disable_existing_loggers = false

[logging.handlers.console]
level = "DEBUG"
class = "logging.StreamHandler"

when using luigi 2.8.9, my task (luigi --module tasks.test Test --local-scheduler) runs just fine.
However, if I upgrade to 2.8.11, I get the following error:
Traceback (most recent call last):
  File "/Users/jamesh/.pyenv/versions/3.7.6/lib/python3.7/logging/config.py", line 563, in configure
    handler = self.configure_handler(handlers[name])
  File "/Users/jamesh/.pyenv/versions/3.7.6/lib/python3.7/logging/config.py", line 697, in configure_handler
    formatter = config.pop('formatter', None)
AttributeError: 'FrozenOrderedDict' object has no attribute 'pop'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/jamesh/depot/test/test_env/lib/python3.7/site-packages/luigi/retcodes.py", line 75, in run_with_retcodes
    worker = luigi.interface._run(argv).worker
  File "/Users/jamesh/depot/test/test_env/lib/python3.7/site-packages/luigi/interface.py", line 211, in _run
    return _schedule_and_run([cp.get_task_obj()], worker_scheduler_factory)
  File "/Users/jamesh/depot/test/test_env/lib/python3.7/site-packages/luigi/interface.py", line 145, in _schedule_and_run
    InterfaceLogging.setup(env_params)
  File "/Users/jamesh/depot/test/test_env/lib/python3.7/site-packages/luigi/setup_logging.py", line 83, in setup
    configured = cls._section(opts)
  File "/Users/jamesh/depot/test/test_env/lib/python3.7/site-packages/luigi/setup_logging.py", line 48, in _section
    logging.config.dictConfig(logging_config)
  File "/Users/jamesh/.pyenv/versions/3.7.6/lib/python3.7/logging/config.py", line 800, in dictConfig
    dictConfigClass(config).configure()
  File "/Users/jamesh/.pyenv/versions/3.7.6/lib/python3.7/logging/config.py", line 571, in configure
    '%r' % name) from e
ValueError: Unable to configure handler 'console'

I checked and it works with 2.8.10 as well. The bug appears in 2.8.11.

This is very much related to issue 2879. The standard library logging module expects a mutable dict, but the config for TOML was changed to use in internal FrozenOrderedDict
There are two ways to slove it. Ignore the freezing of the logging section in TOML configs, or create an unfreeze method and call it before passing the dict to the logging config.


Current version doesn't support GitLab client version 1.41

Component
agent
Describe the bug
As the title states, running any CI job just cancels it with the agent tossing up this error
{"level":"error","error":"rpc error: code = Unknown desc = Proc finished with exitcode 1, Error response from daemon: client version 1.41 is too new. Maximum supported API version is 1.40","time":"2021-12-12T08:59:46Z","caller":"/woodpecker/src/github.com/woodpecker-ci/woodpecker/pipeline/rpc/client_grpc.go:91","message":"grpc error: wait(): code: Unknown: rpc error: code = Unknown desc = Proc finished with exitcode 1, Error response from daemon: client version 1.41 is too new. Maximum supported API version is 1.40"}

Woodpecker is running on docker along one agent with an exposed port mapped to a DNS via nginx. The target is a repo on GitLab (non self-hosted).
System Info
{"source":"https://github.com/woodpecker-ci/woodpecker","version":"next-4cbdacb2"}

Docker-compose:

version: '3'

services:
  woodpecker-server:
    container_name: woodpecker
    image: woodpeckerci/woodpecker-server:latest
    volumes:
      - woodpecker-server-data:/var/lib/woodpecker/
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=${WOODPECKER_HOST}
      - WOODPECKER_GITLAB=true
      - WOODPECKER_GITLAB_CLIENT=${WOODPECKER_GITLAB_CLIENT}
      - WOODPECKER_GITLAB_SECRET=${WOODPECKER_GITLAB_SECRET}
      - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}

  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:latest
    command: agent
    restart: always
    depends_on:
      - woodpecker-server
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WOODPECKER_SERVER=woodpecker-server:9000
      - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}

  woodpecker-nginx:
    build: ./nginx
    container_name: woodpecker_nginx
    ports:
      - 9000:80

volumes:
  woodpecker-server-data:

Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A join our Discord Chat Server.

Thanks for reporting.
Note: Update go-gitlab to v0.52.2


Use common Console interface for logging

Closes: https://github.com/metarhia/metasql/issues/164

[x] tests and linter show no problems (npm t)
[x] tests are added/updated for bug fixes and new features
[x] code is properly formatted (npm run fmt)
[x] description of changes is added in CHANGELOG.md
[x] update .d.ts typings

Landed in https://github.com/metarhia/metasql/commit/cf4cf1cf570473c48c470afd5e3b41e8dd12baad


example colab notebook

this is an example notebook with chainlit on colab

This looks awesome. Will test it locally tomorrow and then merge!


⚠ BCR Bot has degraded performance

In 9888256, BCR Bot (https://bcr.alternativasinteligentes.com/BCRApi/web/chatbot) experienced degraded performance:

HTTP code: 200
Response time: 1168 ms

Resolved: BCR Bot performance has improved in adf2e51.


OMPT detected regions have incorrect sync-time

Running geopmbench with stream-unmarked, the OMPT defined region has significantly more sync-runtime than runtime in the report.

Also check MPI time.

This seems to be fixed in 8.0 version of OpenMP.


Should this API also be called for DFx Power Up?

Per https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/wdm/nc-wdm-po_fx_directed_power_up_callback,
it is stated this API should also be called for the DFx PowerUp API.
Can that info be added here for clarity?

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

ID: 6105b0cb-abf9-8568-a6c4-2fb08b038d96
Version Independent ID: 90feb8b7-a698-1158-cf33-9dcab9b099f5
Content: PoFxCompleteDirectedPowerDown function - Windows drivers
Content Source: wdk-ddi-src/content/wdm/nf-wdm-pofxcompletedirectedpowerdown.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

Hi @tzimmer1, apologies for the delay.  Thanks for spotting an error in the docs.  The power up callback should actually call PoFxReportDevicePoweredOn to complete the callback.  I've just made the change, and it should propagate to https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/wdm/nc-wdm-po_fx_directed_power_up_callback within the hour.


Fix SQL export filename

Hi,
The browser CSV export is a bit broken because the filename passed in headers was mangled. Example :
Content-Disposition: attachment; filename="postgres_"schema"."table".sql.gz"
This PR fixes this.

Thanks !

Thanks !

Great, thanks.
When do you plan to make a new release ?

There's another pg_dump related bug that i need to finish first, then i can cut a new release.
Could do that on friday.

Excellent news !
Don't hurry, I was just wondering for your releases lifecycle : )

Ha, my release lifecycle is pretty much whatever i feel like.


Fix mavlink forwarding issue.

Fix #4816 Mavlink forwarding not working on master.
PX4 master introduce mavlink v2.0 from v1.3.2, but mavros still use mavlink v1.0.
It will cause compatibility problem when forwarding mavlink v1.0 message.
MAVLINK_NUM_HEADER_BYTES always represents mavlink v2.0 header bytes regardless of mavlink v1.0 or v2.0 message to forward.
mavlink api _mavlink_resend_uart can distinguish v2.0 from v1.0.

Thanks!


Ability to add new directories and files

it would be great if the explorer lets us create directories and allows dropping files from desktop into the Explorer at given path.

Proper DevTools support is coming (see https://crbug.com/1284595), so this extensions, which was meant as an intermediate solution, won't get any more features. Please comment on the Chromium bug to add the feature suggestion there.


fix: #1667 Added placeholder image

What

-Added placeholder image when no internet
Screenshot

https://user-images.githubusercontent.com/46121493/166314629-723264c1-dee4-4963-9828-a41f036c69df.mp4
Fixes bug(s)

Fixes: #1667

Hi @vik4114,
Here are a few comments on your PR:

You provide an image of 1200x1200, but only use 1000px. The image should be at the right size
You only give a "1x" image. You should also do the same with 2x & 3x (@ see https://docs.flutter.dev/development/ui/assets-and-images)
Please follow our guidelines in terms of filenames

Codecov Report

Merging #1733 (e592586) into develop (2ea0da3) will decrease coverage by 0.76%.
The diff coverage is 0.66%.

@@            Coverage Diff             @@
##           develop   #1733      +/-   ##
==========================================
- Coverage     8.86%   8.09%   -0.77%
==========================================
  Files          161     168       +7
  Lines         6623    7350     +727
==========================================
+ Hits           587     595       +8
- Misses        6036    6755     +719

Impacted Files
Coverage Δ

...h_app/lib/cards/category_cards/abstract_cache.dart
0.00% <0.00%> (ø)

...p/lib/cards/category_cards/asset_cache_helper.dart
0.00% <0.00%> (ø)

...p/lib/cards/category_cards/raster_async_asset.dart
0.00% <0.00%> (ø)

...oth_app/lib/cards/category_cards/raster_cache.dart
0.00% <0.00%> (ø)

..._app/lib/cards/category_cards/svg_async_asset.dart
0.00% <0.00%> (ø)

...smooth_app/lib/cards/category_cards/svg_cache.dart
0.00% <0.00%> (ø)

...th_app/lib/cards/data_cards/image_upload_card.dart
0.00% <0.00%> (ø)

...t_cards/knowledge_panels/knowledge_panel_card.dart
0.00% <0.00%> (ø)

...t_cards/knowledge_panels/knowledge_panel_page.dart
0.00% <0.00%> (ø)

...knowledge_panels/knowledge_panel_summary_card.dart
0.00% <ø> (ø)

... and 64 more

Continue to review full report at Codecov.

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

New Screenshot


Datepicker Selection off by 1 day IF the year is 1964 and below.

Bug, feature request, or proposal:
Bug
What is the expected behavior?
When you click on a date, the input value should be the day you click
What is the current behavior?
If you select a date that is BOTH in the year 1964 or below AND the day is AFTER the 10th then the date displayed in the input box shows the day before the selected date. (But the calendar shows the correct date)
What are the steps to reproduce?
Enter the date 9/12/1963 into the input box
Open the calendar and select 9/15/1963
Notice the input box says 9/14/1963
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
https://material.angular.io/components/datepicker/overview
You can use the material demo site to reproduce.
No coding required! Yeah.
What is the use-case or motivation for changing an existing behavior?
Old people get frustrated when they cant select their birth date 🥇
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular: 4.1.2
Material: 2.0.0-beta.8
Doesn't work on ->Chrome OS: Version 60.0.3112.101 <-
It works just fine on -> Microsoft Edge 40.15063.0.0  <-
Is there anything else we should know?

Keep it up!

If I reproduce your issue, the date states 14/09/1963 (09 February 1964 if counting), while at first it was 09/12/1963 (12 September 1963).
The focus on the particular date in 1963 is also gone, see attachment. It jumps back to 2017.

It depends on the locale and it affect daylight summer time in past dates when they don't follow today's dst rules. #5747 corrects it and will be available in the next release.

closing since this has been fixed by #5747


Call to fill out Changelog!

This is mainly a place for discussion, etc. from @rmontuoro and @gmao-esherman. Namely, I recently added the Changelog enforcer on GOCART since, well, if you have a Changelog, you should use it!
But, when I recently "created" a good-ish Changelog in main, I didn't really fill out much in the Unreleased section as I don't know GOCART well enough. But, comparing develop to main shows there are a lot of updates not yet in main:
https://github.com/GEOS-ESM/GOCART/compare/main...develop
I don't think this needs to be too detailed, but at least cover the major differences/fixes/etc. that distinguish GOCART develop from GOCART v1.0.1
So, if @rmontuoro and @gmao-esherman can maybe list things they think should be added from past commits here, I can work on making a Changelog update to develop so that we only have a single PR we need to get it up-to-date.
Thanks!

There were only structural changes with GOCART, right? GOCART from develop should zero-diff with GOCART v1.0.1. Maybe we can just say the changes were only structural.

There were only structural changes with GOCART, right? GOCART from develop should zero-diff with GOCART v1.0.1. Maybe we can just say the changes were only structural.

Well, I guess I mean all the GOCART2G things you've done. And all the UFS-y stuff that Raffaele has done. GOCART1G is "static" really in develop. But 2G has changed!


Fix free-courses-en.md structure

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Improve Repo
This PR proposes a fix in the free-courses-en.md file structure:

Remove repeated Sails.js entry from the index (it's already under JavaScript)
Change Assembly content position to place in alphabetical order

Thanks, and welcome to free-programming-books!


Add ability to set model instance in relationship methods

According to these ideas : laravel/ideas#1652 and laravel/framework#27278
I propose to allow passing instance of Model to relationship declaration methods. This can be useful to set a specific configuration (connection, table name, ...) for a given relationship.
Example :
public function superCustomer()
{
    $related = new Customer();
    $related->setTable('super_customers');

    return $this->belongsTo($related, 'id_customer', 'id_customer');
}

Unfortunately the change to the newRelatedInstance method is a breaking change. This PR is probably best sent to master. Thanks! :)


feat: column profiling

Partially addresses: #1258, #1256.
Closes #1260

This looks great! I wont pretend I absorbed the whole profiling logic yet though 😅
One general remark, but more of an open question - I am a bit concerned that Scan will grow too much and know too much of the domain logic and not be just an orchestrator/runner of everything, I like how the actual run is separated in its own class, but the run methods for profiling and for automated monitoring in scan also contain a bit of logic which IMHO is not ideal. Saying that, I understand that it needs things from scan and data_source_scan so with current state it seems there is no clever way around it.

Thanks for having a look @m1n0
Regarding the profiling logic, do you think there is anything I can do to help you understand? Would you prefer someone else to review that part or do we trust it?
For Scan becoming too domain specific. I assume you refer to this kind of stuff here: https://github.com/sodadata/soda-core/pull/1307/files#diff-f8f837bc68ee2608ac96d36a4aed01276f8cb946d8cf810ef30247743a5d89c4R404-R436
If so, I also indeed feel like there is a little bit of domain logic in there. I think there should be a way to build a more factory-like thing but I don't really have a perfect and clear idea in mind right now. So I was thinking maybe to get it in as it is now, and make sure it works so we can start allowing some end to end testing and we can take some time to look into whether we can restructure things a bit.
Do you think involving someone else in the core team would help us in achieving this maybe or should we say let's just try to go back to it a bit later?

CI should run again once https://github.com/sodadata/soda-core/pull/1316 is merged and this branch is rebased

@bastienboutonnet  can you check the tests? The other PR you mentioned is merged.

@vijaykiran Can you review the (dev-)requirements.txt updates?   Are those in line with the package structure we have in place?


Support for mlx file creation, saving, opening and running

Is your feature request related to a problem? Please describe.
As we all know, Matlab Live Script is often used for interactive scripting, it is very convenient to show the demo case entry file, and more and more cases are developed in this way, can the VScode plugin support this feature as soon as possible?
Describe the solution you'd like
This extension is better to support create,save,open and running for Matlab Live Script.
Describe alternatives you've considered
Currently, it has been the ".m" file that has been used for the replacement programme.

Thanks for capturing this! This is something we would like to add support for.

This would be extremely helpful.

Hope for early support.


CMake: Set LAPACK libs as public

lapack/cblas libs are needed through the dlib/matrix/lapack headers
it can be verified on the optimization example:
https://github.com/jschueller/dlib-cmake-example

What's the issue exactly?  I don't totally follow.  All the stuff I know about compiles fine how it is on master.  The example you linked to just looks like the examples in dlib's repository. But something is different?

the problem the executable fails to link if I dont artificially link to LAPACK (comment the target_link_libraries):
[ 25%] Building CXX object CMakeFiles/optim_ex.dir/optimization_ex.cpp.o
[ 50%] Linking CXX executable optim_ex
/usr/bin/ld: CMakeFiles/optim_ex.dir/optimization_ex.cpp.o: undefined reference to symbol 'cblas_dger'
/usr/bin/ld: /usr/lib/libcblas.so.3: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status

Are you sure you are using the current version of dlib for this?

yes, master, but I should add that this only happens for shared libs (dlib defaults to static isnt it ?)

Sure.  Can you post exactly the commands to reproduce this?  I tried building and install dlib as a shared library on ubuntu and building https://github.com/jschueller/dlib-cmake-example.  It all built and ran fine.  I git cloned the current master dlib though.

Sorry, I meant to say I also deleted that line when I tested it.  So what’s the exact set of commands to reproduce this?On Mar 9, 2024, at 3:39 AM, Julien Schueller @.***> wrote:
yes, the example works because I manually link LAPACK; you can comment lines 14-15 to see the error:
https://github.com/jschueller/dlib-cmake-example/blob/main/CMakeLists.txt#L14
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

maybe you are using static lapack libs in dlib, in that case it wont show either, as ubuntu provides both, I'm using the shared ones

anyway, here is how to reproduce from a clean ubuntu install:
FROM ubuntu:22.04
ENV DEBIAN_FRONTEND=noninteractive MAKEFLAGS="-j8"

RUN apt-get -y update && apt-get install -y git g++ cmake liblapack-dev libjpeg-turbo8-dev libpng-dev zlib1g-dev

WORKDIR /tmp
RUN git clone --depth 1 https://github.com/davisking/dlib.git && cd dlib && cmake -B build -DBUILD_SHARED_LIBS=ON . && make install -C build -j12

RUN git clone https://github.com/jschueller/dlib-cmake-example.git && cd dlib-cmake-example && sed -i "s|LAPACK_LIBRARIES|skip|g" CMakeLists.txt && cmake . && make

Huh yeah, sorry for the late reply.   And thanks for the PR :)


wireguard: Fix invalid bits when agent init

This commit modifies the correct CIDR mask when wireguard agent init.
Fixes: https://github.com/cilium/cilium/issues/19106
Signed-off-by: Ye Sijun<EMAIL_ADDRESS>

Thanks! I wonder if we should backport this to v1.10 and v1.11? I understand that it doesn't impact functionality by accident, but might still be better to backport it given the size of the patch. What do you think @brb?


Add  component to react-router-dom

This PR should make it easier to make react-router-dom apps more accessible. This is pretty much a copy of the same component that I use for Curi and I think that this approach works well.
Focus uses a render-invoked prop to assign a ref to the component that should be focused when the location changes
import { Focus } from "react-router-dom";

<BrowserRouter>
  <Focus>
    {ref => (
      <main tabIndex={-1} ref={ref}>
        <Switch>...</Switch>
      </main>
    )}
  </Focus>
</BrowserRouter>

// or even pass the ref to route components (using React.forwardRef()/innerRef)

<BrowserRouter>
  <Focus>
    {ref => (
      <Switch>
        <Route
          exact
          path="/"
          render={match => <Home ref={ref} {...match} />}
        />
        <Route
          exact
          path="/about"
          render={match => <About ref={ref} {...match} />}
          />
      </Switch>
    )}
  </Focus>
</BrowserRouter>

The ref component is only re-focused when the location changes, so non-location change re-renders will not trigger this.

@timdorr I don't think it's necessary. Files entries are deprecated. There is not reason to add the new one.

Uh, I didn't hit submit on those review comments. refined-github goofed 😖

This is interesting! 😃 🎉 I don't quite have the time at the moment to do a full review but I wrote a big 'ol document about our experience making a React app with RR v4 accessible: https://github.com/folio-org/stripes-components/blob/master/docs/patterns/AccessibleRouting.md
We tried a couple of different methods, one of them looks similar to what the <Focus /> component here is doing. I hope to come back to this sometime over the weekend!

A review of this PR from you would be invaluable, @Robdel12. If you can spare the time, I'd really appreciate it :)

Just read through that doc, @Robdel12. I like the shouldFocus HOC you came up with.
In your example, the HOC gives you an extra degree of control through the shouldFocus prop. Do you think something like that would be important to include in the <Focus> API we are discussing here? Maybe something like a <Focus when> prop?
With that prop, you could write your HOC like this:
/**
 * Higher order component that, when given the prop
 * `shouldFocus={true}`, will focus the component's DOM node on mount
 * and on update when the prop is toggled from `false` to `true`.
 */
export default function shouldFocus(Focusable) {
  return class extends Component {
    static propTypes = {
      shouldFocus: PropTypes.bool
    };

    render() {
      return (
        <Focus when={this.props.shouldFocus}>
          {ref => (
            <Focusable {...this.props} ref={ref} />
          )}
        </Focus>
      );
    }
  };
}

// and use it like this:
const CustomInput = shouldFocus(
  React.forwardRef((props, ref) => (
    <div>
      <input ref={ref} />
    </div>
  ))
);

<CustomInput shouldFocus={true} />

Would that work for you?

I should have some free time later tonight / tomorrow morning! 😃

@mjackson yes! So much yes :)

This should also be fairly straightforward to implement as a hook eventually.
function App() {
  const ref = useFocus({ preventScroll: true });
  return (
    <main tabIndex={-1} ref={ref}>
      {/* ... */}
    </main>
  );
}

Commented on outline: none implications

@stowball commented where?

@stowball you mean just for the outline: none style, correct? Not that the user necessarily should attach the ref to a interactive element, but you don't see an accessibility issue if someone were to do this:
<Focus>
  {ref => (
    <input ref={ref} />
  )}
</Focus>

it may be relevant to this discussion that there is an rfc currently being actively discussed for some focus management features to be provided by react-dom:
https://github.com/reactjs/rfcs/issues/104
https://github.com/devongovett/rfcs-1/blob/patch-1/text/2019-focus-management.md


Epic: Prepare for 1.0.0 release

[x] fix deprecation warning #163
[x] fix configuration issues
[x] get basic version of BrokenLinksChecking to work
[x] add some PlantUML diagrams to documentation (for WJAX presentation)

still missing:

ignore-hosts configuration for broken-links checker
improved smoke-test (htmlSanityCheckConsumer needs additional tests)
improve readme ("user-documentation")


Error occured while trying connect rigid body and rope

Hi
I want to bulid a simulation system that one end of cable connceted with robot end-effector and another end connceted with a fixed box.
I have generate cable and box in mujoco, and succeed in connect cable to the effector.
However, when i'm trying to connect another end of cable to the box, the connection was builld successful but the end connected with a point with nothing there and away from box.

you can find the main script of the env. I connect object by equality-connect function, current order of body 1 and body2 is the only avaiable order i tested, the cable would be crazy as long as i change the connect order.
I guess the reason is wrong anchor value? but when i change the anchor pos, system become unstable.
123.txt
Could you please give any suggestions?
Best Regards.

Hi,
Your model does not load. Please attach a loadable model (as a zip file, including all assets) if the suggestion below does not solve you problem.
From inspection of your image, it seems like possibly your constrained points do not overlap at qpos0? As described here, connect constraints are by default defined with respect to the null configuration of your model (model->qpos0). If this is the case, you would need to rotate your rope so that the two constrained points overlap at the null pose. This is of course just a guess since I cannot load your model.

Hi ,
I saw you said the qpos0, but i don't know how to set it in xml file. Should I change it by mujoco-py?
I have been submit the loadable model. you can find it in zip file and run the connect_by_rope.xml to recurring the error.
could you please help me to see any problems cause the unwilling result?
for update.zip
Also, I'm trying to connect the box and robot ee by tendon, It succeed, the tendon is attached like what i want. Does the cable can be like this?  you can also see the tendon-connected case by running conect_by_tendon.xml.

Best Regards.

A tendon is a good solution if you are not interested in modeling the dynamics of the cable.
Regarding qpos0 this is simply the configuration that you see when you first load the model. Right now your rope is pointed sideways. I should point down, so that the tip touches the point where you want to connect it.
Also, I noticed you gave your rope a free joint. It will probably be more stable if you made it a child of the robot or of the object.


Paper-tabs in Flexbox

When using paper-tabs (Polymer 1.0) inside a flexbox without a specific width, they disappear in IE (10 as well as 11).

This is flex

  <paper-tabs>
    <paper-tab>Paper</paper-tab>
    <paper-tab>Tabs</paper-tab>
  </paper-tabs>

Any solution as I guess I should be able to use it this way (I'm very new to Polymer).

@Dyljyn
Did you tried the universal CSS fix for IE?
zoom: 1;

auto-moving this issue to PolymerElements/paper-tabs#29 and closing this one


Update API explorer links to open in new tab

Update API explorer links to open in new tab in following markdown files:

Quick Start Guide
Payment Overview
API Reference
Integration details
Refunding payments

@roryjhs I've amended the link text in line with guidance from Alistair Duggin (head of accessibility); each link now clearly states that it will open in a new window.


Fixed Endpoint and tag Typos

Typos fixed :

Tag  reprodubility to reproducibility
Endpoint /content/osre24/projecs.md to /content/osre24/projects.md
Expserience to Experience
additioinal to additional

@carlosmalt, could you please review it

Thank you, @Vishalk91-4 !


BUG: Bug in the returned Series.dt.components index was reset to the default index (GH9247)

closes #9247

yep, looks good!


Transfer to julia-actions

Codecov Report

Merging #20 (0bd2364) into master (4595c76) will decrease coverage by 0.98%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #20      +/-   ##
=========================================
- Coverage    5.15%   4.16%   -0.99%
=========================================
  Files           5       4       -1
  Lines          97      96       -1
=========================================
- Hits            5       4       -1
  Misses         92      92

Impacted Files
Coverage Δ

src/MassInstallAction.jl

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 4595c76...0bd2364. Read the comment docs.


version 7 and PKCE?

according to the doc, code flow and PKCE is supported from version 8, so for angular 7 app, it's out of luck?

You could try to use version 8 of this lib with Angular 7. There is a big chance, this works, b/c as a rather technical lib it does not use much features of Angular.


updated arm gcc Cortex-M memory barrier

I agree HvUtils.h is a better place for platform specific code.

#define hv_sfence() was put in HvLightPipe.c because it's specific to that file. @pingdynasty What's the reason to put it into HvLightPipe.h?

It would seem to me that it would be easier to keep track of 1 file, rather than multiple when it comes to making changes for the OWL platform.

@pingdynasty Who defines ARM_CORTEX? Does the compiler itself define that?

(this conversation is in so many places!)
I'm afraid the compiler does not, it has to be defined by the build environment and that may not be standard.
I think this should work in a standard way: #elif defined (__GNUC__) ie the condition is: defined __arm__ && defined __GNUC__
I will test.

I like where you're going with this @pingdynasty. Another question (sorry for so many), you're backing based on which compiler is being used, but you use it to specify an architecture specific command. Is there any way to check for the architecture instead? E.g. __CORTEX_M.

I wish there was but I haven't found one.
Maybe __ARM_ARCH_PROFILE == 77 but I've not dug deep enough in the docs to know if that works across the board.
Apparently dmb is available to all ARMv7 architectures [1] so maybe  __ARM_ARCH >= 7?
Come to think of it the issue at this point is not so much architectural (already determined by __arm__) but how to produce the correct assembly macro, which does relate to the compiler.
Regarding crashes, I found this comment in HvLightPipe.h:
This pipe assumes that there is only one producer thread and one consumer thread. This data structure does not support any other configuration.
Does that mean that calls to hv_scheduleMessageForReceiver() must be consecutive, never concurrent?
[1] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0489c/CIHGHHIE.html

Ahh ok, that's a good point regarding getting the compiler to produce the correct assembly.
Regarding the HvLightPipe, the comment is correct. However it is used in conjunction with a spinlock in the context of Heavy, which protects it from the producer side (i.e. sending in messages). See the HV_SPINLOCK_* macros in HvUtils. Perhaps those aren't working for you?

@pingdynasty FYI I have merged this change into the dev channel. I will close this PR, but we can continue to use it to discuss any crashes that you may be experiencing.

The crashes happen because the device gets stuck in a spinlock loop.
Having thought about it, spinlocks won't work with interrupt triggered events because the interrupt will not be suspended at any point, it just keeps running and the main 'thread' along with the lock stays blocked.
Since we don't use pre-emptive tasks, there's no real way around this apart from perhaps a lock-free queue.

Right! If you can guarantee in your system that you only ever have one (message) producer thread and one audio thread, then the system will work without the need for spinlocks. HvLightPipe takes care of that case.

How do I enable this?
And what about messages produced within the audio thread?

The number of message producing threads is a function of your application, not of heavy, so you would know that better than I.
The messages produced on the audio thread and sent out of the context are sent on the audio thread itself.

So I enable the last spinlock option in HvUtils.h:
#define hv_atomic_bool volatile bool #define HV_SPINLOCK_ACQUIRE(_x) _x = true; #define HV_SPINLOCK_RELEASE(_x) _x = false;
This so far appears to work as long as I lock the process when sending messages:
  volatile bool busy = false;
  void buttonChanged(PatchButtonId bid, uint16_t value, uint16_t samples){
    if(busy)
      return;
    if(bid == PUSHBUTTON){
      hv_sendFloatToReceiver(context, receiverHash[8], value ? 1.0 : 0.0);
    }else if(bid >= MIDI_NOTE_BUTTON){
      // send message to notein object
      static const unsigned int hash = 0x67E37CA3; // __hv_notein
      float note = (float)(bid - MIDI_NOTE_BUTTON);
      float velocity = (float)(value>>5);
      float ms = 1000.0f*(samples+getBlockSize())/getSampleRate(); // delay in milliseconds
      // create note in message
      HvMessage* notein;
      notein = (HvMessage*)alloca(hv_msg_getByteSize(5));
      hv_msg_init(notein, 5, 0.0);
      // notein expects: note, velocity, channel, command, port
      hv_msg_setFloat(notein, 0, note);
      hv_msg_setFloat(notein, 1, velocity);
      hv_msg_setFloat(notein, 2, 1.0f); // channel
      hv_msg_setFloat(notein, 3, value ? 0x90 : 0x80); // command
      hv_msg_setFloat(notein, 4, 0.0f); // port
      hv_scheduleMessageForReceiver(context, hash, ms, notein);
    }
  }

  void processAudio(AudioBuffer &buffer) {
    float paramA = getParameterValue(PARAMETER_A);
    float paramB = getParameterValue(PARAMETER_B);
    float paramC = getParameterValue(PARAMETER_C);
    float paramD = getParameterValue(PARAMETER_D);
    float paramE = getParameterValue(PARAMETER_E);
    float paramF = getParameterValue(PARAMETER_F);
    float paramG = getParameterValue(PARAMETER_G);
    float paramH = getParameterValue(PARAMETER_H);
    busy = true;
    hv_sendFloatToReceiver(context, receiverHash[0], paramA);
    hv_sendFloatToReceiver(context, receiverHash[1], paramB);
    hv_sendFloatToReceiver(context, receiverHash[2], paramC);
    hv_sendFloatToReceiver(context, receiverHash[3], paramD);
    hv_sendFloatToReceiver(context, receiverHash[4], paramE);
    hv_sendFloatToReceiver(context, receiverHash[5], paramF);
    hv_sendFloatToReceiver(context, receiverHash[6], paramG);
    hv_sendFloatToReceiver(context, receiverHash[7], paramH);
    busy = false;
    float* outputs[] = {buffer.getSamples(LEFT_CHANNEL), buffer.getSamples(RIGHT_CHANNEL) };
    hv_owl_process(context, outputs, outputs, getBlockSize());
  }

Note that buttonChanged() is called on an interrupt and has to be abandoned if lock is on.
Regarding messages on the audio thread: will they clash with messages scheduled from the interrupt? Do I need to have the lock on while hw_owl_process is running?
There can be both internal messages and outgoing ones, right?

This is the kind of thing that Heavy does internally. Take a look in the e.g. hv_sendFloatToReceiver function and the heavy process function.
I'm glad that this approach is working for you, but in theory heavy should already be handling this.

Wait a minute... try replacing HV_SPINLOCK_ACQUIRE with this:
#define HV_SPINLOCK_ACQUIRE(_x) \
while (_x) {} \
_x = true;

Key difference is that when locked, the interrupt abandons the task instead of waiting.

the interrupt abandons the task instead of waiting
Is that a bad thing if you have to wait a few cycles? (I honestly have no idea, I'm not familiar with the details of the OWL)

That's my point: the interrupt is never suspended, it keeps spinning - and the lock is never unlocked.
What I need to know is if I also have to lock during hw_owl_process.

ahhhh, so it's the case there are no threads per se, but that there is the main (audio) thread and when an interrupt comes it must finish because the main thread never continues to release the spinlock?
In that case, yes, your solution is the only way right now. We could make a function available which will let you query the state of the internal spinlock. That might make your life easier.

correct!

We could make a function available which will let you query the state of the internal spinlock

Yes that could work really well.
The alternative for me is to do all message scheduling outside of the patch. I can do this but it is fairly complex and expensive in memory and cpu.

I'll add a function get the state of the spinlock.

I'm having apparent success with an extern lock which I define in my wrapper code:
#define HV_SPINLOCK_ACQUIRE(_x) { extern volatile bool _msgLock; _msgLock = true; }
#define HV_SPINLOCK_RELEASE(_x) { extern volatile bool _msgLock; _msgLock = false; }

Would be even nicer to get the state. I was trying to get it from the context with context->base.msgLock but of course the context is not fully declared to the client code. Including the generated HvContext_owl.h didn't work out at all, so I went with the extern solution.
Now I just need to contrive a patch which is really busy in the locked sections... I'll let you know if any problems occur.

I was thinking about it and I was wondering it what would be best and most technically correct would be to give you:
hv_lock_acquire()
hv_lock_try()
hv_lock_release()

Where for your application you would use hv_lock_try() and hv_lock_release(). I fear that the problem with giving you the lock state directly, while entirely feasible, wouldn't be useful, as the state might change as soon as you get it!

That looks really good, I can see how that would be useful in many thread-based scenarios too.
So hv_lock_try() would return a boolean? Do you need to define some way of testing it, since the hv_atomic_bool type could be, well, anything?
I guess any reasonable type of hv_atomic_bool could be cast to bool.

the state might change as soon as you get it!

The state might change but testing the instance directly will always work if it has been declared volatile.
Still hv_lock_try() seems cleaner and better: the api won't be dependent on how hv_atomic_bool is defined.

FYI hv_lock_try() has been added to the dev channel. Give it a try!


File comment

Is your feature request related to a problem? Please describe.
using vscode 1.85, C++, and document generator 1.4.0, how do I insert a "file" comment? Using /** as the trigger I get generic comment, is there a special trigger to insert doxygen file comment?
Describe the solution you'd like
Something in the documentation to explain how to get file comment generated, if this is indeed possible. I've played around trying various things e.g. /** on first line in file

I also had same issue, my env like:

ext version: v1.4.0
vscode ver: 1.89.1
OS: MacOS Ventura 13.6.6

I solved this problem by adding configuration in settings.json:
{
  "doxdocgen.c.triggerSequence": "/**"
}

But I don’t think it’s elegant for users to add it manually.


Improve javascript implementation performance by reducing code duplication

To make the code shorter (and thus faster to import and parse) we can avoid lots of code duplication we have in the Go port
Since JS doesn't care about strict types, we no longer need several signatures for similar functions and can use the same implementation, just pass additional args
This is worth the performance improvement (in the Go implementation it doesn't matter since it's pre-compiled)

Consider doing this with an automated tool like: https://developers.google.com/closure/compiler/


Build: abs added

Changelog: https://github.com/lballabio/QuantLib/releases
License: https://github.com/lballabio/QuantLib/blob/master/LICENSE.TXT
Requirements:

https://www.quantlib.org/install.shtml
https://www.quantlib.org/install/cmake.shtml
https://github.com/lballabio/QuantLib/blob/QuantLib-v1.29/CMakeLists.txt

Actions:

Add abs.yaml: disable uploading to the target channel before the PR's approvals; the empty build_parameters: - "" will be needed if the artifacts will exist in the target channel, it will allow rewriting them by newer ones.
Reset build/number to 0
Remove autotools & make on unix
Add ninja-base on unix. It looks like the build process is faster with ninja locally and on Prefect
Update build.sh & bld.bat
Move the test command on unix to build.sh
Fix home url
Fix description

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_8e_asav_f0/clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_8e_asav_f0/clone/recipe/meta.yaml:29: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_0brnkqvnex/clone/recipe/meta.yaml:25: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_0brnkqvnex/clone/recipe/meta.yaml:26: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_0brnkqvnex/clone/recipe/meta.yaml:32: missing_tests: No tests were found.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_1fhnhyurgo/clone/recipe/meta.yaml:25: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1fhnhyurgo/clone/recipe/meta.yaml:26: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_1fhnhyurgo/clone/recipe/meta.yaml:32: missing_tests: No tests were found.
Errors were found

An error on s390x:
The following tests FAILED:
	  1 - quantlib_test_suite (Failed)
FAILED: CMakeFiles/test.util

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_4aek04m512/clone/recipe/meta.yaml:36: missing_tests: No tests were found.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_a4lkaiblym/clone/recipe/meta.yaml:32: missing_tests: No tests were found.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_52xrcjv8h6/clone/recipe/meta.yaml:32: missing_tests: No tests were found.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_88v_3jbtpt/clone/recipe/meta.yaml:33: missing_tests: No tests were found.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_2a0wp3jtbw/clone/recipe/meta.yaml:33: missing_tests: No tests were found.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_01u3kh8j74/clone/recipe/meta.yaml:33: missing_tests: No tests were found.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_17elwt6y60/clone/recipe/meta.yaml:33: missing_tests: No tests were found.
Errors were found


No type inference for element when using for in loop

Looping over static arrays, dynamic arrays, slices, maps, and strings using a for in loop doesn't infer the type of the element and its index and causes auto completion and hover to not work
Simple reproducible code
package main

main :: proc() {
    slice := []int{1, 2, 3, 4, 5}

    for elem in slice {
    }
}

Fixed in #339


[MOB-3910] null clicked url for triggered events

🔹 JIRA Ticket(s) if any

MOB-3910 (https://iterable.atlassian.net/browse/MOB-3910)

✏ Description
This pull request includes adding the clicked url to the trackInAppClose function call.

Good find and fix 👍


Deprecate use of broken or risky MD5 hash function

Tracking issue for:

[ ] https://github.com/rlwhitcomb/utilities/security/code-scanning/1

The security vulnerability is now closed by the CodeQL analysis.  Closing this issue.


Various improvements to logging

Fixes https://github.com/daisy/xproc-maven-plugin/issues/5 and some other things
Blocked on https://github.com/daisy/xprocspec/pull/47

@rdeltour @josteinaj Does this look good to you? I'd like this to be merged as soon as possible because the longer it takes the more time I loose while running tests.

xproc-engine-calabash could use an updated version of calabash. I think that might help with some issues I'm having when trying to run the xproc test suite with xprocspec. But maybe it's easier to keep xproc-engine-calabash in sync with the calabash version used in xproc-engine-daisy-pipeline.

I assume the xprocspec version referenced is the one on the master branch of xprocspec? The test_very_big takes a lot of time to run so I had to comment it out, but the rest of it builds fine.
Using 1.0.1-SNAPSHOT of xproc-maven-plugin and xproc-engine-calabash to run the tests in xprocspec works fine.

xproc-engine-calabash could use an updated version of calabash. I think that might help with some issues I'm having when trying to run the xproc test suite with xprocspec. But maybe it's easier to keep xproc-engine-calabash in sync with the calabash version used in xproc-engine-daisy-pipeline.

The calabash versions don't have to be the same, but it is probably a bit easier planning-wise to update at the same time as we do https://github.com/daisy/pipeline-tasks/issues/85.

I assume the xprocspec version referenced is the one on the master branch of xprocspec?

The xprocspec version referenced is the one from daisy/xprocspec#47.

The test_very_big takes a lot of time to run so I had to comment it out, but the rest of it builds fine.

OK

By the way, if you want to try a newer version of xprocspec, try its dev branch. There's only a few more issues I want to have a look at before I can merge and release that branch.


Add Volume page should show the storage pool name

If you have created a storage pool and want to add a volume from the storage pool page, the Add Volume page should show which storage pool the volume will be added to.

n/a to 2.0


Can't access camera(s)

Cameras are not found for any device on which I run the UI.
I'm running zwavejs in a container (docker.io/zwavejs/zwave-js-ui:latest) on a remote (LAN) server. I'm accessing the UI directly via exposing port 8091; SSL is disabled. I've tried Firefox and luakit (WebKit) on a Linux laptop, and Firefox on an Android phone. In all cases, no camera is found, and the JS console reports:
[QrReader] Error: No available camera found
    initialize http://media.lan:8091/assets/QrReader-bfce9e2b.js:1
[index-822e6be1.js:59:1869](http://media.lan:8091/assets/index-822e6be1.js)
    d http://media.lan:8091/assets/index-822e6be1.js:59
    createDefaultHandler http://media.lan:8091/assets/index-822e6be1.js:59
    invoke http://media.lan:8091/assets/index-822e6be1.js:59
    error http://media.lan:8091/assets/index-822e6be1.js:59
    initialize http://media.lan:8091/assets/QrReader-bfce9e2b.js:1

I do not get a camera access pop-up from Firefox, and there is no rule denying access to the site in the prefs. The camera is available to other web apps (e.g. meet.jit.si).
I'm certain this is user error in how I'm running the container, or something; I'm at a loss on how to proceed. I've found no tickets that seem similar, and web search engines turn up no results.
If I port forward over ssh and access the web page through the forward, it does work; on my phone (with termux):
ssh -L 8091:localhost:8091

and then access http://localhost:8091 on my phone, the camera is found and I can scan QR codes. It's only accessed remotely that fails. The only thing I can think of is a firewall interference; port 8091 is open, and for good measure I tried opening the API port (3030, mapped to port 3000 in the container), but exposing the API port didn't help.
Any ideas?

Thank you.


Expose combined stdout and stderr

Add a Command#output method that combines #stdout and #stderr. Be sure that they're interleaved properly. This may require backing Command#run with Open3.popen3 rather than with Open3.capture3.

It seems as though this is impossible, and this feature is vital to Command as a whole, so I think we should deprecate this entire library.


The collision broke

the correct collision for popsplit and linesplit is totally broken , linesplit and popsplits not working totally

We are aware of this and @Barbosik has made a note of it many times before.


[proposal] KoordRuntimeProxy support both Fail/Ignore FailurePolicyType

What is your proposal:
Currently,  KoordRuntimeProxy supports two kinds FailurePolicyType, including Fail & Ignore.
but only Ignore policy is supported under containerd scenario while only Fail is supported under docker scenario.
KoordRuntimeProxy should support both Fail/Ignore under both containerd and docker scenario.
Why is this needed:
Is there a suggested solution, if so, please add it:

Supported feature.
/close


Fix history command test locale

Environment
Liquibase Version: N/A
Liquibase Integration & Version: N/A
Liquibase Extension(s) & Version: N/A
Database Vendor & Version: N/A
Operating System Type & Version: N/A
Pull Request Type

[x] Bug fix (non-breaking change which fixes an issue.)
[ ] Enhancement/New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Include 2 small fixes:

Remove an used and possibility failing import. Build may fail on some Java environment as the useless import is a Sun class.
Fix HistoryCommandTest to use Locale.US for DateTimeformat

Steps To Reproduce

Build project on IntelliJ IDEA with OpenJDK 11.
Run tests on system where default locale is not US.

Actual Behavior

Build fails on IntelliJ IDEA with OpenJDK 11, with the following message:

/home/toilal/projects/liquibase/liquibase-core/src/main/java/liquibase/ui/DefaultInputHandler.java:4:33
java: package sun.reflect.generics.tree does not exist

HistoryCommandTest fails because date format doesn't match expected date format.

Expected/Desired Behavior
Project should compile, tests should pass.
Fast Track PR Acceptance Checklist:

[x] Build is successful and all new and existing tests pass
[ ] Added Unit Test(s)
[ ] Added Integration Test(s)
[ ] Added Test Harness Test(s)
[ ] Documentation Updated

Need Help?
Come chat with us on our discord channel
┆Issue is synchronized with this Jira Story by Unito

Hi @Toilal Thanks for providing this PR.
Here’s what happens next:
A member of the Liquibase team will take a look at your contribution and may suggest:

Changes based on guidelines for PR submission
Additional tests (unit and/or integration) and/or Test Harness Tests
Provide other feedback, like requesting changes.

The PR will be prioritized according to our internal development and testing capacity.
We’ll let you know when it’s ready to move to the next step or if any changes are needed.

Hi @Toilal Thanks for providing this PR.
Here’s what happens next:
A member of the Liquibase team will take a look at your contribution and may suggest:

Changes based on guidelines for PR submission
Additional tests (unit and/or integration) and/or Test Harness Tests
Provide other feedback, like requesting changes.

The PR will be prioritized according to our internal development and testing capacity.
We’ll let you know when it’s ready to move to the next step or if any changes are needed.

These same changes were applied independently as part of 4.4.0.
Thanks for pointing out the issues.


Internal States

Is there any api to get the internal states of the model, e.g. hidden states of the ppo?

What do you mean by internal states of ppo?


Typechecking failed after update from 0.2.2 to 0.2.3

See this workflow run.
After update to 0.2.3 I got many errors like this:

Error: packages/renderer/src/components/Options/ColorScheme.vue(5,7): error TS2322: Type '"system" | "light" | "dark"' is not assignable to type 'Booleanish | undefined'.
  Type '"system"' is not assignable to type 'Booleanish | undefined'.

Example of affected component:
https://github.com/cawa-93/anime-library/blob/7173ca67072c7025ab354f9b08003e549fdea03b/packages/renderer/src/components/Options/ColorScheme.vue

This is upstream problem. See #57, #58, https://github.com/vuejs/vue-next/issues/4321, https://github.com/vuejs/vue-next/issues/4322.
You can lock vue-tsc to 0.2.2 and lock vscode-vue-languageservice to 0.26.14 for now.

Is there a way to ignore this error for now? I couldn't find a way to put @ts-ignore inside v-model…

@zigomir vue already resolved it in 3.2.3! But Evan point out radio v-model prop incorrect in volar, I will fix it soon.

@zigomir vue already resolved it in 3.2.3! But Evan point out radio v-model prop incorrect in volar, I will fix it soon.

Fix in vscode-vue-languageservice 0.27.2.

@johnsoncodehk Could you, please, release new vue-tsc with that fix?

@cawa-93 you can delete yarn.lock / package-lock.json and reinstall to update vscode-vue-languageservice.


Installation failure on local machine

Followed the instructions to install with git clone.
git clone https://github.com/x1unix/go-playground.git
cd go-playground
make
sudo make install

Any ideas why when I run make I get the error below? Thanks
~/goproj/go-playground (master)$ make
:: Cleanup...
:: Checking and installing dependencies...
Ambiguous Syntax Error: Cannot find which to pick amongst the following alternatives:

  0. yarn install [--json] [--immutable] [--immutable-cache] [--check-cache] [--inline-builds] [--mode #0]
  1. yarn install [--json] [--immutable] [--immutable-cache] [--check-cache] [--inline-builds] [--mode #0]

While running --cwd=./web install --silent
make: *** [build.mk:43: preinstall] Error 1
~/goproj/go-playground (master)$

@wyattbiker probably you have more than yarn packages installed on your system.
I recommend using Docker container to run the service locally.

https://github.com/x1unix/go-playground/pkgs/container/go-playground%2Fgo-playground
https://hub.docker.com/r/x1unix/go-playground

@x1unix hmmm, don't know how it happened. Did a global find and I got this.
~$ which yarn
/usr/local/bin/yarn
~$ whereis yarn
yarn: /usr/local/bin/yarn

file:///usr/local/bin/yarn
file:///usr/share/nodejs/yarn
file:///home/user1/.cache/node/corepack/yarn
file:///usr/share/nodejs/yarn/bin/yarn
file:///usr/local/lib/node_modules/corepack/shims/yarn
file:///usr/local/lib/node_modules/corepack/shims/nodewin/yarn

Was trying to avoid running a docker process though.  I may go with the docker option.

@wyattbiker If you still wish to avoid using Docker, try to remove global yarn installation (nowadays people use npx ... to run local packages).
npm uninstall -g yarn


Add support for text gdiplus v2

New version of OBS uses text_gdiplus_v2 for text sources... old script won't work without adding support for v2

Thanks for the notice 👍


Fix ruby/romaji not display after change text.

Sometimes ruby/romaji not change after set value.

Need to think about how to implement because framework hide the update invalidate(true) into private.

Also should fix not adding extra position if not have ruby or romaji.


SceneInspector : viewing of ExternalProcedural and Light parameters.

I had this sitting around on a branch I'm working on in my spare time, but Chris' email made me think it'd be worth merging first on its own.

I tried merging this, but something funny happened in GitHub... it seems like the commits are already on master, but it's telling me this is still open and can't be auto-merged...
I'm going to close it, on the assumption that my view on the commits is more accurate than my view on the PR...


Partners list is in different height is fixed

1.In the list of partners, the container size varies depending on the logo size. If the logo is large, the container height increases, and if the logo is smaller, the container height decreases accordingly -set with a fixed height
2.the partners logo is curved on the left Corners, removed the curves
Fixes #276
On the partners page, the banner is displayed at full width and aligned properly.
Fixes  #278


[otbn,dv] FIPS error doesn't produce error if RND is unused

While we are requesting RND from EDN if the word packages don't have FIPS flag high, we produce a recoverable error (see https://docs.opentitan.org/hw/ip/otbn/doc/#Reg_err_bits). However, inside otbn_rnd we are not catching the FIPS flag being low correctly. The reason is probably that we are enabling the flop with rnd_data_en and also gating the error with rnd_req_complete (which actually signals if we read RND or not).
Gating the error part also suggest that if the RND_PREFETCH is enabled, we could get a non-compliant RND data stored and not set the FIPS error because we haven't used RND yet.
For a quick reprodcuing:

Force FIPS input of RND on the testbench to 1b'0 (1'b1 as default)https://github.com/lowRISC/opentitan/blob/c663c108c51ff3179395eb36a69b675bbd075af5/hw/ip/otbn/dv/uvm/tb.sv#L145
run command util/dvsim/dvsim.py hw/ip/otbn/dv/uvm/otbn_sim_cfg.hjson -i otbn_reset --reseed=1 --fixed-seed=1882593666 --tool=xcelium -w

Please let me know if you need more details.

This
https://github.com/lowRISC/opentitan/blob/c663c108c51ff3179395eb36a69b675bbd075af5/hw/ip/otbn/rtl/otbn_rnd.sv#L162
together with this
https://github.com/lowRISC/opentitan/blob/c663c108c51ff3179395eb36a69b675bbd075af5/hw/ip/otbn/rtl/otbn_rnd.sv#L83
indeed means that rnd_fips_err_o is only 1 if the FIPS bit was 0 and there is a read from the RND register.
I don't know if this is intended by design, but the specification of the RND_FIPS_CHK_FAIL recoverable error currently states

The random numbers received via the RND EDN interface have been generated from entropy that at least partially failed the FIPS health checks in the entropy source.

which I would also interpret as "the error will raise as soon as a random number that fails FIPS is received on the EDN interface" rather than "the error will raise as soon a random number that fails FIPS is read from the RND register".

Thanks for raising this issue. It's indeed intended behavior to only signal the error if the value is actually read from the RND register. The reason is that in the current OTBN design, all recoverable errors are synchronous, i.e., they can only happen during OTBN program executing. If we were instead signaling the error upon receiving the non-FIPS entropy, the error could also be triggered after/before OTBN execution which would lead to ugly corner cases in the error handling.
The correct thing to do here is to align the documentation accordingly. I can do that.


Include “original exceptions” that are referenced in some exceptions

This is meant for PowerAuthErrorException.
A real-world example from a client:

Tries to call addBiometryFactor
On the native layer, PowerAuthErrorException is caught with code NETWORK_ERROR
The error is reported to the JS layer as such (NETWORK_ERROR)

The problem is, that in this case, a FailedApiException caused this and is accessible via the getCause() method, but this information (endpoint that was called and what was the actual networking error), is lost as it's not propagated to the JS layer.

OK, this particular case was improved in #55 / #58. The developer no longer needs to dig deeper into exceptions to determine the exact reason of the failure. I'll keep it open for possible improvements, but IMHO, from the functionality point of view, it's enough for developers to have NETWORK_ERROR, RESPONSE_ERROR and AUTHENTICATION_ERROR.

☝🏻  I agree, this was a result of a direct question by the client (who was complaining that he doesn't see the response during the development) and cannot determine, what is wrong.
Maybe there could be a debug option to print all exceptions thrown (including the nested one), to the JS console / native log for easier debugging.

I don't have any idea how to more improve this. There's already new possibility to trace failed native calls (see #116) so I close this ticket now.


ollama serve

Sorry to bother you. I followed the link you provided, used the ollama serve command, then in another terminal, I entered ollama run llama3.1, and finally, in a third terminal, I ran python run.py. However, I encountered the same issue as before. Could you kindly provide a more detailed step-by-step guide whenever you have the time? Thank you for your help.

Please follow this (website)[https://github.com/modelscope/agentscope/blob/main/scripts/README.md#ollama] and try to run the example code successfully first.

Try pip uninstall agentscope? It seems the program is trying to load agentscope in the environment.

I have completed the example from the link. Could you provide a detailed tutorial?

Try pip uninstall agentscope? It seems the program is trying to load agentscope in the environment.

Maybe you can try this?

I have tried, but it returned this error.

The agentscope module is located in agentscope-main/src/agentscope. Just make sure this path is included in your working directory or in your Python path to resolve the ModuleNotFound error.

I have confirmed that the path is correct, and my error occurred because I uninstalled agentscope using pip uninstall agentscope. However, I still can't get it to run. Do you have a more detailed guide?

I recommend testing if you can run agentscope, as agentscope-main was cloned directly from the AgentScope GitHub Repo. Navigate to cd agentscope-main, then create a test file containing the example provided in AgentScope's documentation and try running it.

This issue is solved in #5


Bring candles from the broker

Why not bring the candles from a Forex broker to do the analysis? Opening an account at a broker is free and can you open "demo" accounts and use the "Metatrader 5" library for python for this?

https://www.mql5.com/en/docs/python_metatrader5

Broker Forex with metatrader 5. https://roboforex.com/en/


"Dealu Bajului" is listed in the drop-down menu

Description:
When user writes "Dealu Bajului" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Dealu Bajului"

Expected results
The location appears in the drop-down menu as "Dealu Bajului, Alba (Arieșeni)"


Custom Feign RequestInterceptor for Spring OAuth2

This PR adds a new RequestInterceptor complementing the existing Feign implementation of a Basic one.
For now it is a simple class to easy use for users to create RequestInterceptors Beans and register, since the main goal for this kind of support is the selective interceptors, see spring-cloud-netflix/issues/288.
This fixes gh-56

Any updates on this ?

Did you fill in the Contributor's Agreement (link in README)?

Yes, I already signed.
On Sat, Oct 17, 2015, 7:54 AM Dave Syer<EMAIL_ADDRESS>wrote:

Did you fill in the Contributor's Agreement (link in README)?
—
Reply to this email directly or view it on GitHub
https://github.com/spring-cloud/spring-cloud-security/pull/75#issuecomment-148907271
.


Has it stopped working for someone else too ?

Gem is not returning info about price etc. on send anymore and the message doesn't actually come either...

it was my mistake, sorry


Bad recovery with missing } after use

use symbols::{SymbolBuilder, SymbolTable, Symbol

// some code

gives syntax errors for almost every token.

That's a tricky one, because we maintain the invariant that { are balanced in the syntax tree.

Presumably same as https://github.com/rust-analyzer/rust-analyzer/issues/3434, closing.


Tasks: apostrophe:clear-cache task is missing (0.6)

Implement #198 in 0.6

@boutell is still a thing we need?

Yeppers
On Tue, Jun 20, 2017 at 5:53 PM, Stuart Romanek<EMAIL_ADDRESS>wrote:

@boutell https://github.com/boutell is still a thing we need?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/punkave/apostrophe/issues/240#issuecomment-309902711,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB9fTFj2OvJPur4kPeIMa6NPZDHmL5eks5sGD9NgaJpZM4EISGq
.

--
*THOMAS BOUTELL, *SUPPORT LEAD
P'UNK AVENUE |<PHONE_NUMBER>  |  punkave.com

This was implemented.


Fix the indeterminate test issue.

Description
This pull request fixes the indeterminate test issue causing builds to fail randomly. I finally got to the bottom of what was causing it. The issue was with the minitest spec tests. A couple of the describe blocks didn't have the word "decorator" in them. This prevented minitest from registering the spec type as Draper::TestCase. Since the tests weren't registered as a Draper::TestCase, it wasn't including Draper::TestCase::ViewContextTeardown which defines teardown to clear the view context. Since the view context wasn't being cleared after these tests, the next test that called a helper on ViewContext.current blew up.
Testing
Once merged, we should not longer see builds fail randomly. You can test locally by:

$ cd spec/dummy
SEED=8910 rake should fail repeatedly on master.
Switch to this branch and run the above command and the test suite should pass.

To-Dos
None
References

GitHub Issue 784

wtf...
Great job 👍


Adds new method on URL called droppedScheme

Resolves: #464

Checklist

[ ] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 4.
[x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[ ] I have added a changelog entry describing my changes.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 490 tests, with 0 failures (0 unexpected) in 3.434 (4.000) seconds

:book:
tvOS: Executed 460 tests, with 0 failures (0 unexpected) in 1.967 (2.374) seconds

:book:
macOS: Executed 332 tests, with 0 failures (0 unexpected) in 1.163 (1.428) seconds

  Generated by :no_entry_sign: Danger

@sammy-SC Can you also fix the swiftlint warning pointed by danger :))

@LucianoPAlmeida fixed.

Thank you for contributing to SwifterSwift! I've invited you to join the SwifterSwift GitHub organization - no pressure to accept! If you'd like more information on what that means, check out our contributing guidelines. Feel free to reach out if you have any questions! 😃


emacs: enable native-comp

Description of changes
cc @adisbladis
Things done

Built on platform(s)

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

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

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

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

[X] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[X] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 176780 run on x86_64-linux 1

1 package built:

emacs-nox

Result of nixpkgs-review pr 176780 run on x86_64-linux 1

2 packages built:

emacs
emacs-nox

Also, I've had problems building emacs packages on aarch64 in the past, package builds would crash. Let's run a couple packages through ofborg to make sure this is fixed, and if not only enable it on x86 by default.
@ofborg build emacsPackagesNg.magit emacsPackagesNg.counsel emacsPackagesNg.vterm

That looks fine, so that only leaves the async question :) the reason should probably be documented in the release notes which we already have.

Hm, I'm sure I made another comment in here somewhere improving the wording of the release notes. Never mind though, let's just merge this and get the functionality in.


minor edits for clarity

@cartermp Please review

Since you're now editing this topic, I'll make some suggestions. Can't add a line note since you haven't touched some of these lines:

Throughout the topic:
NET CLI -> .NET Core CLI
OSX -> OS X
fbbonacci -> Fibonacci
Line 5:
read the overview -> read the .NET Core SDK overview
Line 27: link to the command page like the other commands in the topic are doing
Line 84: .net core -> .NET Core
Line 91: remove duplicate from
Line 103:
creat -> create
64 bit Windows 10 and the 64 bit version of Mac OSX -> 64-bit version of Windows 10 and the 64-bit version of OS X

@mairaw done

Thanks @tdykstra! LGTM

👍 Thanks!


Please update the gem after Release yajl commit

I noticed that the gem has a runtime dependency yajl-ruby ~> 1.2.0 in rubygems, but in source code there is a dependency 'yajl-ruby', '>= 1.2.0'.
Maybe you forgot update the gem after release yajl commit. Please, republish the gem 🙏

@simonoff could you please help with the issue?

Thanks, God! I have found a solution. Here the link to a fork and also it fixes CVE-2017-16516