Issue when installing packages inside studio folder

Steps to reproduce the error:

Run npm install in the root folder
Run cd studio && npm install

The following error occurs:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@sanity/icons
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/groqd-playground
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /Users/shreyas/.npm/_logs/2024-08-16T04_56_22_979Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /Users/shreyas/.npm/_logs/2024-08-16T04_56_22_979Z-debug-0.log

I ran npm install --force and it fixed the issue temporarily and I'm able to run the project just fine. But don't know if this will cause any issues in the future during development.

Same issue

I removed groqd-playground from the studio; there was a peer dependency issue. It should be fixed now.


Support request based reply timeout in ReplyingKafkaTemplate

Hi,
ReplyingKafkaTemplate (2.2.7-RELEASE) should be setup as a singleton. This means I can only define my reply-timeout once and all my interactions with th etemplate will use this setting. I want to set the timeout per request (replyFuture) so I can still re-use the template but have a different timeout per request.
Thx,
Kees Broenink
<EMAIL_ADDRESS>

Thanks a lot!

@garyrussell
Is it possible to use the change using a pre-release?

You can get spring-kafka-2.3.0.BUID-SNAPSHOT from https://repo.spring.io/snapshot
It's scheduled to be released next week.


Sh/api version updates

What does this PR do?
Updates mdapi:deploy, mdapi:retrieve, source:deploy, source:retrieve, source:push, and source:pull to use the API version event data from SDR to output an accurate message of what is being used for the deploy or retrieve.  Updates all libraries involved.
A sample message for retrieve will look like this:
"Retrieving v54.0 metadata from<EMAIL_ADDRESS>using the v57.0 SOAP API"
The mdapi:deploy commmand is the only one that will not specify the API version of the source since we don't read the package.xml contents (or unzip and read it) so that will look like this:
"Deploying metadata to<EMAIL_ADDRESS>using the v57.0 SOAP API"
What issues does this PR fix or reference?
@W-12146873@

QA notes: this was mostly QA'd on
https://github.com/forcedotcom/source-deploy-retrieve/pull/797
https://github.com/forcedotcom/source-deploy-retrieve/pull/791
✅  Deploying metadata to<EMAIL_ADDRESS>using the v56.0 SOAP API
✅ ../../plugin-source/bin/dev force:source:deploy -x mdapiOut/package.xml (v53 manifest)
Deploying v53.0 metadata to<EMAIL_ADDRESS>using the v56.0 SOAP API
✅ manifest beats project.json
../../plugin-source/bin/dev force:source:deploy -x mdapiOut/package.xml --apiversion 51.0
✅ Deploying v53.0 metadata to<EMAIL_ADDRESS>using the v51.0 SOAP API
../../plugin-source/bin/dev force:source:retrieve -x mdapiOut/package.xml --apiversion 51.0
✅ Retrieving v53.0 metadata from<EMAIL_ADDRESS>using the v51.0 SOAP API
with 48 on project.json
../../plugin-source/bin/dev force:source:retrieve -p force-app/main/default/classes --apiversion 51.0
✅ Retrieving v48.0 metadata from<EMAIL_ADDRESS>using the v51.0 SOAP API


snactor-generated scripts do not support Unicode

When no file encoding is specified, Python 2 regards .py files as ascii, compared to Python 3's utf-8. This leads to a fatal error in case of non-ascii characters, for example with the following actor body...
    def process(self):
        self.show_message("表ポあA鷗ŒéＢ逍Üßªąñ丂㐀𠀀")

...this error is thrown when trying to run the actor:
Process Process-1:
Traceback (most recent call last):
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 258, in _bootstrap
    self.run()
  File "/usr/lib64/python2.7/multiprocessing/process.py", line 114, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/python2.7/site-packages/leapp/repository/actor_definition.py", line 26, in inspect_actor
    definition.load()
  File "/usr/lib/python2.7/site-packages/leapp/repository/actor_definition.py", line 139, in load
    self._module = importer.find_module(name).load_module(name)
  File "/usr/lib64/python2.7/pkgutil.py", line 246, in load_module
    mod = imp.load_module(fullname, self.file, self.filename, self.etc)
  File "/root/Message/actors/message/actor.py", line 16
SyntaxError: Non-ASCII character '\xe8' in file /root/Message/actors/message/actor.py on line 16, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details
Inspection of actor in actors/message failed

Expected output:
表ポあA鷗ŒéＢ逍Üßªąñ丂㐀𠀀

@bocekm i guess this rather is a thing for best practices don’t you think? Not really a bug per se

Right, this behaviour is inherent to Python 2 (https://docs.python.org/2/howto/unicode.html). So I wouldn't probably even mention it in best practices.
The actor's code is supposed to be Python 2 and 3-compatible.  The solution is to add # -*- coding: utf-8 -*- to the first or second line of the source file. But even better, use ASCII only.
Even though I'm closing this issue, @drehak, you're welcome to write down counter-arguments. We can always reopen it.

The question is: Do we want people to write actors in UTF-8 or choose their local encoding?
Our expectation should be reflected in the template, so if we "want" UTF-8, then the generated files should be UTF-8 ready, ie. if we also expect people use python2, then the line should already be there.  (You don't necessarily even need to address that in best practices, assumption that everyone uses UTF-8 seems pretty safe these days.)
IMHO we should definitely want UTF-8.  I'm not even sure how python behaves if the file is unmarked; if it merely inherits runtime locale's encoding, then we could end up with mess of files that were written and tested with whatever locale, but are not marked.  So better ask for UTF-8 explicitly.

how python2 behaves if the file is unmarked

well, Dominik actually mentions that in this case it was ascii, although I would not be 100% sure this is the whole story (programs are sometimes "smart" wrt encodings; it could be affected by LC* envvars and stuff).

https://docs.python.org/2/howto/unicode.html: "If you don’t include such a comment, the default encoding used will be ASCII. ... Python 2.5 and higher are stricter and will produce a syntax error." - that's the syntax error @drehak has copied.

Yeah, adding the # -*- coding: utf-8 -*- to the template is an option. Let's discuss it at Cabal.

Actually that was what we have been thining earlier - to put the line into the template. However, from this point, the issue with non-ascii characters is effectively caught by CI (we can point the users or in case we will report it in future, they will be able to even fix that by them own). About the template - we do not want to put this line there by default (yes, keep it for cabal, just telling what we discussed with @vinzenz already). S no, we do not want to enable to people using of non-ascii encoding unless there is real reason for that - and in such case review, irc, mails,... works.

Have you reached any consensus on this?

@drehak nope, the cabal last week was skipped due to lack of topics. This one topic wasn't enough, we have another one planned for tomorrow.

@drehak we decided that we will not support non-ascii characters in source code by default. Actually, we haven't found real big benefit to do such thing.


composer doesn't find quant-php/quant

Good evening,
While trying to install quant-php/quant, I'm getting that it composer can't find the package.  If you have an update to get this working, please let me know.
Sincere,
Brian D Swan
-- Output from command listed below:
brianswan@Mac-minibash 08:22 PM -> [~/Sites/test-app-001]$ sail composer require  quant-php/quant
In PackageDiscoveryTrait.php line 368:
Could not find a matching version of package quant-php/quant. Check the package spelling, your version constraint and that the package is available in a stability which matches your minimum-stability (stable).
require [--dev] [--dry-run] [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--fixed] [--no-suggest] [--no-progress] [--no-update] [--no-install] [--no-audit] [--audit-format AUDIT-FORMAT] [--update-no-dev] [-w|--update-with-dependencies] [-W|--update-with-all-dependencies] [--with-dependencies] [--with-all-dependencies] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--prefer-stable] [--prefer-lowest] [--sort-packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--] [...]
brianswan@Mac-minibash 08:22 PM -> [~/Sites/test-app-001]$

@briandswan  Thanks for your feedback, let me check this...

Fixed with v1.0.0. The homepage had it right (https://quant-php.dev/docs/installation/), the README.d had it wrong!


tester报错：TypeError: Passing coroutines is forbidden, use tasks explicitly.

您好，我是一个新手，在跑tester的是否有上述报错，请问这是什么问题呢？该如何解决呢？

您好，我已收到您的邮件，我将尽快给您回复。Hello, I have received your email, I will reply to you as soon as possible.

我也有这个，看不太懂哈哈


Whitelisting Facebook domains for Facebook like on /es

Whitelisting Facebook domains for Facebook like on /es
Changes

Modified cfgov/cfgov/settings/base.py to whitelist Facebook like requirements.

Testing

http://localhost:8000/es/ and verify you can use the like button.

Screenshots

Before

After:

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated
[ ] Reviewers requested with the Assignee tool :arrow_right:

It appears that these like buttons were already present on /es and CSP broke their functionality. I 100% agree with @Scotchester's point that we should avoid inclusion of these types of scripts whenever possible, but in this case we should probably restore the previous functionality. Removing these dynamic buttons should definitely be something we take on in future Spanish site work, however.


HADOOP-18055. Async Profiler endpoint for Hadoop daemons

Description of PR
Async profiler (https://github.com/jvm-profiling-tools/async-profiler) is a low overhead sampling profiler for Java that does not suffer from Safepoint bias problem. It features HotSpot-specific APIs to collect stack traces and to track memory allocations. The profiler works with OpenJDK, Oracle JDK and other Java runtimes based on the HotSpot JVM.
Async profiler can also profile heap allocations, lock contention, and HW performance counters in addition to CPU.
This PR provides Async profiler endpoint for Hadoop daemons.
More analysis on CPU and memory overhead:

https://github.com/jvm-profiling-tools/async-profiler/issues/14
https://github.com/jvm-profiling-tools/async-profiler/issues/131

How was this patch tested?
Locally. Screenshots:

For code changes:

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 46s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint 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 _

+0 :ok:
mvndep
13m  1s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m 36s

trunk passed

+1 :green_heart:
compile
22m 17s

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

+1 :green_heart:
compile
19m 18s

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

+1 :green_heart:
checkstyle
3m 40s

trunk passed

+1 :green_heart:
mvnsite
2m 21s

trunk passed

+1 :green_heart:
javadoc
1m 49s

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

+1 :green_heart:
javadoc
2m 25s

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

+0 :ok:
spotbugs
0m 43s

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

+1 :green_heart:
shadedclient
22m 40s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 29s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 12s

the patch passed

+1 :green_heart:
compile
22m 39s

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

+1 :green_heart:
javac
22m 39s

the patch passed

+1 :green_heart:
compile
20m  0s

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

+1 :green_heart:
javac
20m  0s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

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

+1 :green_heart:
mvnsite
2m 19s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

-1 :x:
javadoc
1m 10s
/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.txt
hadoop-common in the patch failed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04.

+1 :green_heart:
javadoc
2m 23s

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

+0 :ok:
spotbugs
0m 38s

hadoop-project has no data from spotbugs

-1 :x:
spotbugs
2m 42s
/new-spotbugs-hadoop-common-project_hadoop-common.html
hadoop-common-project/hadoop-common generated 1 new + 0 unchanged - 0 fixed = 1 total (was 0)

+1 :green_heart:
shadedclient
22m 26s

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

_ Other Tests _

+1 :green_heart:
unit
0m 37s

hadoop-project in the patch passed.

+1 :green_heart:
unit
17m 34s

hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m  0s

The patch does not generate ASF License warnings.

213m 38s

Reason
Tests

SpotBugs
module:hadoop-common-project/hadoop-common

The field org.apache.hadoop.http.ProfileServlet.profilerLock is transient but isn't set by deserialization  In ProfileServlet.java:but isn't set by deserialization  In ProfileServlet.java

Subsystem
Report/Notes

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

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

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

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

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b1edcc0cdc1ad867f2262b74cc8a516410ce8a7b

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

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

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

@aajisaka @jojochuang @tasanuma Could you please take a look?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m 18s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint 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 _

+0 :ok:
mvndep
13m 22s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
28m 31s

trunk passed

+1 :green_heart:
compile
28m 53s

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

+1 :green_heart:
compile
25m 57s

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

+1 :green_heart:
checkstyle
4m 15s

trunk passed

+1 :green_heart:
mvnsite
2m 34s

trunk passed

+1 :green_heart:
javadoc
1m 48s

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

+1 :green_heart:
javadoc
2m  7s

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

+0 :ok:
spotbugs
0m 36s

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

+1 :green_heart:
shadedclient
29m  3s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 26s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 20s

the patch passed

+1 :green_heart:
compile
27m 39s

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

+1 :green_heart:
javac
27m 39s

the patch passed

+1 :green_heart:
compile
24m 45s

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

+1 :green_heart:
javac
24m 45s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 25s

the patch passed

+1 :green_heart:
mvnsite
2m 32s

the patch passed

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
1m 58s

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

+1 :green_heart:
javadoc
2m 30s

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

+0 :ok:
spotbugs
0m 39s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
28m 57s

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

_ Other Tests _

+1 :green_heart:
unit
0m 33s

hadoop-project in the patch passed.

-1 :x:
unit
18m 58s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch passed.

+1 :green_heart:
asflicense
1m  0s

The patch does not generate ASF License warnings.

260m  3s

Reason
Tests

Failed junit tests
hadoop.ipc.TestIPC

Subsystem
Report/Notes

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

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

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

uname
Linux ab158d71c1c4 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / f8945ccc6e4d5ad0a4584abc87744e4bbf211caa

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

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

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

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

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

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Requesting review from @ayushtkn @liuml07 as well, nothing urgent, as per your convenience.

Thank you @virajjasani for your patch. This feature looks very helpful for us to investigate the root cause of some performance issues. I'll build and deploy Hadoop cluster and test this feature.
Now I have one comment: We need to add an additional access control for this servlet like ConfServlet. In addition, we need to update the document of hadoop.security.instrumentation.requires.admin.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint 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 _

+0 :ok:
mvndep
11m 26s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 45s

trunk passed

+1 :green_heart:
compile
24m  5s

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

+1 :green_heart:
compile
20m 37s

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

+1 :green_heart:
checkstyle
3m 53s

trunk passed

+1 :green_heart:
mvnsite
3m 26s

trunk passed

+1 :green_heart:
javadoc
2m 42s

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

+1 :green_heart:
javadoc
3m  6s

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

+0 :ok:
spotbugs
0m 32s

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

+1 :green_heart:
shadedclient
23m 22s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 24s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 54s

the patch passed

+1 :green_heart:
compile
23m 22s

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

+1 :green_heart:
javac
23m 22s

the patch passed

+1 :green_heart:
compile
20m 28s

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

+1 :green_heart:
javac
20m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 46s

the patch passed

+1 :green_heart:
mvnsite
3m 25s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 40s

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

+1 :green_heart:
javadoc
3m  9s

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

+0 :ok:
spotbugs
0m 29s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
23m 17s

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

_ Other Tests _

+1 :green_heart:
unit
0m 27s

hadoop-project in the patch passed.

+1 :green_heart:
unit
17m 13s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m 36s

hadoop-kms in the patch passed.

+1 :green_heart:
unit
8m 55s

hadoop-hdfs-httpfs in the patch passed.

+1 :green_heart:
asflicense
0m 50s

The patch does not generate ASF License warnings.

244m 58s

Subsystem
Report/Notes

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

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

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

uname
Linux 3192cf072bbf 4.15.0-142-generic #146-Ubuntu SMP Tue Apr 13 01:11:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / ab6ee9dd7d03473ddf8a89e576836171459001e2

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

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

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

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

modules
C: hadoop-project hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-httpfs U: .

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint 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 _

+0 :ok:
mvndep
11m 22s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 41s

trunk passed

+1 :green_heart:
compile
23m 57s

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

+1 :green_heart:
compile
20m 26s

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

+1 :green_heart:
checkstyle
3m 56s

trunk passed

+1 :green_heart:
mvnsite
3m 28s

trunk passed

+1 :green_heart:
javadoc
2m 41s

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

+1 :green_heart:
javadoc
3m 10s

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

+0 :ok:
spotbugs
0m 31s

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

+1 :green_heart:
shadedclient
23m 42s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 22s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 53s

the patch passed

+1 :green_heart:
compile
23m  6s

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

+1 :green_heart:
javac
23m  6s

the patch passed

+1 :green_heart:
compile
20m 20s

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

+1 :green_heart:
javac
20m 20s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 50s

the patch passed

+1 :green_heart:
mvnsite
3m 26s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 38s

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

+1 :green_heart:
javadoc
3m  9s

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

+0 :ok:
spotbugs
0m 28s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
23m 28s

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

_ Other Tests _

+1 :green_heart:
unit
0m 26s

hadoop-project in the patch passed.

-1 :x:
unit
17m 24s
/patch-unit-hadoop-common-project_hadoop-common.txt
hadoop-common in the patch passed.

+1 :green_heart:
unit
3m 37s

hadoop-kms in the patch passed.

+1 :green_heart:
unit
7m 49s

hadoop-hdfs-httpfs in the patch passed.

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

243m 52s

Reason
Tests

Failed junit tests
hadoop.ipc.TestIPC

Subsystem
Report/Notes

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

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

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

uname
Linux b2453d9dceca 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 02cc4d65a6d8673a7c42d309be474f8e4ccf7842

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

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

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

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

modules
C: hadoop-project hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-httpfs U: .

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
markdownlint
0m  0s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 55s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m 41s

trunk passed

+1 :green_heart:
compile
22m 19s

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

+1 :green_heart:
compile
19m 24s

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

+1 :green_heart:
checkstyle
3m 41s

trunk passed

+1 :green_heart:
mvnsite
4m  1s

trunk passed

+1 :green_heart:
javadoc
3m 20s

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

+1 :green_heart:
javadoc
3m 45s

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

+0 :ok:
spotbugs
0m 42s

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

+1 :green_heart:
shadedclient
22m 13s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 30s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m  2s

the patch passed

+1 :green_heart:
compile
21m 24s

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

+1 :green_heart:
javac
21m 24s

the patch passed

+1 :green_heart:
compile
19m 26s

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

+1 :green_heart:
javac
19m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 32s

the patch passed

+1 :green_heart:
mvnsite
3m 59s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
3m 18s

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

+1 :green_heart:
javadoc
3m 46s

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

+0 :ok:
spotbugs
0m 38s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
20m 55s

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

_ Other Tests _

+1 :green_heart:
unit
0m 37s

hadoop-project in the patch passed.

+1 :green_heart:
unit
17m 32s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m 46s

hadoop-kms in the patch passed.

+1 :green_heart:
unit
6m 18s

hadoop-hdfs-httpfs in the patch passed.

+1 :green_heart:
asflicense
1m  1s

The patch does not generate ASF License warnings.

237m  7s

Subsystem
Report/Notes

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

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

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

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

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 8501c77edb9c3b4d8a82b11e95459fa0322abac9

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

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

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3824/5/testReport/

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

modules
C: hadoop-project hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-httpfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3824/5/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

does it support async profiler 1.x and 2.x? Better to document that somewhere.

Yes, updated AsyncProfilerServlet.md. Thanks

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 55s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
markdownlint
0m  1s

markdownlint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+0 :ok:
mvndep
12m 52s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
24m 28s

trunk passed

+1 :green_heart:
compile
24m  5s

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

+1 :green_heart:
compile
20m 28s

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

+1 :green_heart:
checkstyle
3m 52s

trunk passed

+1 :green_heart:
mvnsite
3m 27s

trunk passed

+1 :green_heart:
javadoc
2m 41s

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

+1 :green_heart:
javadoc
3m 11s

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

+0 :ok:
spotbugs
0m 32s

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

+1 :green_heart:
shadedclient
23m 25s

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

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 23s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 54s

the patch passed

+1 :green_heart:
compile
23m  9s

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

+1 :green_heart:
javac
23m  9s

the patch passed

+1 :green_heart:
compile
20m 30s

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

+1 :green_heart:
javac
20m 30s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
3m 49s

the patch passed

+1 :green_heart:
mvnsite
3m 23s

the patch passed

+1 :green_heart:
xml
0m  3s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
2m 38s

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

+1 :green_heart:
javadoc
3m  8s

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

+0 :ok:
spotbugs
0m 29s

hadoop-project has no data from spotbugs

+1 :green_heart:
shadedclient
23m 27s

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

_ Other Tests _

+1 :green_heart:
unit
0m 27s

hadoop-project in the patch passed.

+1 :green_heart:
unit
17m 43s

hadoop-common in the patch passed.

+1 :green_heart:
unit
3m 36s

hadoop-kms in the patch passed.

+1 :green_heart:
unit
8m 17s

hadoop-hdfs-httpfs in the patch passed.

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

246m 19s

Subsystem
Report/Notes

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

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

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

uname
Linux 40466c6b26ec 4.15.0-163-generic #171-Ubuntu SMP Fri Nov 5 11:55:11 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 49bff7c57c7c6dae21573752f0ae81fadf858f8b

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

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

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3824/6/testReport/

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

modules
C: hadoop-project hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs-httpfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3824/6/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.


Error message in the debug / logs tab

Description
Devnet 9280a08.
A clear description of the bug is:
The error isn't shown as an error, and some strings aren't supposed to be shown, like %c and timeout color.

WIP:
still investigating...

@samaradel their is an issue to update the debug tab UI. To not have a color, boxes, and all of that, so maybe check it first if you want, saving time on doing this issue if it is going to be removed anyway.

@A-Harby as per discussion with @AhmedHanafy725 it will not be removed, maybe it should move somewhere else, so it's ok to be fixed.

Work completed:
Used console.error instead of console.log and rephrased error msg in both load vms function & load k8s.

verified on devnet
version : e1cdba0
the log is now shown as error

but the  }at the end which follows the vm name log shall be removed also so error can be more clear

Work Completed:
Remove an extra } from logs when deployment fails

verified and fixed on devnet
version : ff9d79e


Error: You must specify a number of files greater than 1 to split your tests across.

Trying to integrate this (without setting parallel on circle first) causes this error. However I think this is undesired as circle may only provision 1 container for you if they are being used elsewhere
You must specify a number of files greater than 1 to split your tests across.
Error: You must specify a number of files greater than 1 to split your tests across.
    at TestsOptionsValidator._getShouldSplit (/home/ubuntu/platform/node_modules/ember-exam/lib/utils/tests-options-validator.js:26:13)
    at CoreObject.module.exports.TestCommand.extend.run (/home/ubuntu/platform/node_modules/ember-exam/lib/commands/exam.js:63:23)
    at CoreObject.superWrapper [as run] (/home/ubuntu/platform/node_modules/core-object/lib/assign-properties.js:32:18)
    at CoreObject.<anonymous> (/home/ubuntu/platform/node_modules/ember-cli/lib/models/command.js:224:19)
    at tryCatch (/home/ubuntu/platform/node_modules/rsvp/dist/rsvp.js:538:12)
    at invokeCallback (/home/ubuntu/platform/node_modules/rsvp/dist/rsvp.js:553:13)
    at publish (/home/ubuntu/platform/node_modules/rsvp/dist/rsvp.js:521:7)
    at flush (/home/ubuntu/platform/node_modules/rsvp/dist/rsvp.js:2370:5)
    at _combinedTickCallback (node.js:370:9)
    at process._tickDomainCallback (node.js:425:11)

ember exam --silent --reporter "xunit" --split=$CIRCLE_NODE_TOTAL --partition=`expr $CIRCLE_NODE_INDEX + 1` > $CIRCLE_TEST_REPORTS/junit/junit.xml returned exit code 1

Here is part of my circle.yml
test:
  override:
    - mkdir -p $CIRCLE_TEST_REPORTS/junit:
        parallel: true
    - ember exam --silent --reporter "xunit" --split=$CIRCLE_NODE_TOTAL --partition=`expr $CIRCLE_NODE_INDEX + 1` > $CIRCLE_TEST_REPORTS/junit/junit.xml:
        parallel: true

I don't have much familiarity with Circle. The number of nodes available to run your tests is variable per-run?
If so, I would recommend parallelizing within a given node instead of  across the variable number of nodes. It will give you more consistent results and make debugging easier (less environmental variables).

I'm not super familiar with it either, but this is my understanding.
You pay for containers, and all of your projects share these. If one is used it waits until another opens up. You can set it on a per repo(project) setting to use more if available. I only have 2 containers available, if a different project uses one (and is only provisioned one) then my ember project only has one available and this will happen (I think)
I found this blog post so hopefully someone else will run into this with circle who is more familiar

If so, I would recommend parallelizing within a given node instead of across the variable number of nodes. It will give you more consistent results and make debugging easier (less environmental variables).

How would I go about this?

After working with the author of that blog post we confirmed that it is indeed working (once I switched to 2 containers for my project) and it is splitting the tests up correctly. To check this open the Artifacts tab in circle and click on the xml files to verify they are running different tests

However the issue still arises, I think if split does get passed 1, it should just run it as if it wasn't split rather than failing the tests

I think if split does get passed 1, it should just run it as if it wasn't split rather than failing the tests

I suppose I can relax this to just be a warning. The intent was to make sure developers know when they're actually splitting/reducing the number of tests being run, but an exception may be a bit too disruptive.

How would I go about this?

Use the --parallel option. In general I recommend this over trying to use multiple node/boxes/processes as it is overall less resource intensive.

@Frozenfire92 we haven't had any issues using exam on Circle. Here's our circle.yml:
general:
  branches:
    only:
      - master
      - /.*_ci$/
machine:
  node:
    version: 4.7.0
dependencies:
  cache_directories:
    - "/opt/circleci/nodejs/v4.7.0/lib/node_modules"
    - "/opt/circleci/nodejs/v4.7.0/bin"
    - "node_modules"
    - "bower_components"
  pre:
    - type ember || npm -g install ember-cli
    - type bower || npm -g install bower
  override:
    - npm install
    - bower install
test:
  override:
    - mkdir -p $CIRCLE_TEST_REPORTS/ember:
        parallel: true
    - node_modules/ember-cli/bin/ember exam ci --split=$CIRCLE_NODE_TOTAL --partition=$((CIRCLE_NODE_INDEX+1)) --reporter xunit --silent > $CIRCLE_TEST_REPORTS/ember/junit$CIRCLE_NODE_INDEX.xml:
        parallel: true
        timeout: 1200

Ah you're saying the error message is unhelpful? I think it's fine, as you'd configure the circle.yml per project, and you'd add containers per project anyway based on your Circle plan?
Basically in the case of single containers you'd just use ember test ci anyway?

👍  to this a warning, so that we can do e.g.
ember exam --parallel --split=$NUMBER_OF_PROCESSORS
without extra conditional logic

This has been changed in 0.6.2.


[stable/metallb] Add PSP

What this PR does / why we need it:
Add support for PSP in MetalLB
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped

/lgtm

it seems to me that are you not actually setting up a rolebinding to let the metallb-speaker serviceaccount use this new psp being defined, so basically you're defining a psp but haven't set anyone to be allowed to use it :-(

@aleks-mariusz PR welcome.


No input in Win10 Asyncio

See code below.
I get the prompt. But I cannot enter any test into it...
import asyncio
from prompt_toolkit import prompt
from prompt_toolkit.patch_stdout import patch_stdout

async def my_coroutine():
    while True:
        with patch_stdout():
            result = await prompt('Say something: ', async_=True)
        print('You said: %s' % result)

if __name__ == "__main__":
    loop = asyncio.get_event_loop()
    loop.run_until_complete(my_coroutine())

Thanks for noticing this! The code looks fine and I can reproduce this issue. I'll have a look.

Hi @sander76,
The problem here was that prompt_toolkit didn't know it had to use the asyncio event loop. It was still using the internal loop which wasn't running.
Try calling use_asyncio_event_loop() at the start of your application, like here:
https://github.com/jonathanslenders/python-prompt-toolkit/blob/2.0/examples/prompts/asyncio-prompt.py#L61
Does that work?

👍


JS Frameworks links updates

Update Angular link to point to latest version website.
Update JS Frameworks comparison link to point to a more recent comparison of different frameworks.

@CESARDELATORRE Can you look at and review this PR?

@ardalis can you please look at this?


Update Turkish translations

Coverage remained the same at 59.277% when pulling d21f3dfa7f2cb400ed395779a87778df20ae5efb on bitigchi:locale-tr into 7fccaf10e49ffb4678b3ec7e931f6eb7fc7fe3d7 on newsboat:master.

Thanks!


New external service to check stats documentation

@xuanxu @maelle I'm pretty sure you can both ignore this one. Implementation should just work.
@noamross Idea here is to implement a command for pre-submission stats enquiries, @ropensci-review-bot check srr, which will report on standards compliance to report total number of standards complied with, and confirm that that is > 50%. Any thoughts or comments?

We don't want buffy to send any message here. Is that done with message: -> empty body?

No need for an empty body, if there is no message: param nothing will be sent

We also don't want buffy to deliver any response from the external service; how do we ensure that? The service itself will dump the response (which may take some minutes).

For this you can use the silent param: silent: true will do

Thanks @xuanxu, i think i've got everything in place now, including the external service spec via the above PR, but the command was not recognised. Any ideas why not?

Is the command listed if you run @ropensci-review-bot help ?

Nope

I saw the problem: the external_service is repetead in the config file, defined multiple times. All external services should be declared as an array under the same external_service entry

@xuanxu (I've been away on holidays, but now back and still trying to get this to work ..) The new config file with the external service matrix is this:
https://github.com/ropensci-org/buffy/blob/dbbc066cdaaaf401f7cd4255328b8078dafad10c/config/settings-production.yml#L107-L140
The requests as sent to the external service then look like this:
GET /editorcheck ?data_from_issue%5B%5D=repo&data_from_issue%5B%5D=repourl&data_from_issue%5B%5D=issue_id&secret 200 0.002
GET /srrcheck ?data_from_issue%5B%5D=repo&data_from_issue%5B%5D=repourl&data_from_issue%5B%5D=issue_id&secret 200 0.002

so it seems buffy is sending an empty data_from_issue parameter instead of actually parsing the array for the variables and values. Does that seem right to you?

:wave: @mpadge I've open a PR to fix the problem: https://github.com/ropensci-org/buffy/pull/83

Can this be closed or are there remaining problems?


Docker API is unreachable

Hi there,
I started running into an issue bringing up the reward svc and/or environments
I've been using the reward tool for some months now and it's been working very smoothly until today
Windows 10 Pro
Docker Desktop 4.8.2 (79419)
WSL2 using Ubuntu 22.04 Jammy Jellyfish
Docker is working as expected within WSL2 (i.e docker or docker-compose throw no errors for other projects)
As seen in the below image the only debug output is
INFO[0000] docker api is unreachable

If you need further information please let me know

Closing issue, turned out to be a system config issue where "Use Docker Compose V2" had been enabled after an update.
Once I disabled this option, I rebooted and all was well with the world


Add option to qinfo to print task IDs

Adding the option to qinfo to print IDs (PIDs) of running clusters provides an easy way for scripts and process managers to fetch their PID(s).

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

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

3 files (not in diff) in django_q/brokers were modified. more

Misses +82
Hits -82

1 files (not in diff) in django_q were modified. more

Misses +76
Hits -76

@@             master       #173   diff @@
==========================================
  Files            40         40
  Lines          2725       2734     +9
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           2633       2477   -156
- Misses           92        257   +165
  Partials          0          0

Powered by Codecov. Last updated by [2e062a2...d66209d][cc-compare]
[cc-base-branch]: https://codecov.io/gh/Koed00/django-q/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/Koed00/django-q/compare/2e062a2ba9e32efd2ba35ca8ad03f1331625aabb...d66209de2998751963c177fec9ab3b91e075a5c6
[cc-pull]: https://codecov.io/gh/Koed00/django-q/pull/173?src=pr

I like the idea , it's simple enough.
Unfortunately I just deprecated optparse for argparse, to be compatible with Django 1.9 and 1.10.
Do you mind changing that?
I'll add a test when you're done.

Thanks! I added this option as a convenient way to reference the PIDs of running clusters from the management scripts I've written to run django_q as a service on FreeBSD. The scripts create a pid file when a cluster starts, then use the --ids option to easily check for running clusters when stopping/restarting the service. Works like a charm.
I've committed the change from optparse to argparse.

Is this still on track to be merged for inclusion in the next release?
Thanks.

Sure. Thanks for reminding me. I'll merge it to master when I can.
The release itself will have to wait till the weekend.


fix(crud): set default extra value when adding database

SUMMARY
When adding a new database via the new React CRUD, the connection times out due to the extra field not being prepopulated with default values (they were only shown as a placeholder).
TEST PLAN
Local testing
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

Codecov Report

Merging #11262 into master will decrease coverage by 5.87%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11262      +/-   ##
==========================================
- Coverage   65.57%   59.70%   -5.88%
==========================================
  Files         831      393     -438
  Lines       39514    24809   -14705
  Branches     3598        0    -3598
==========================================
- Hits        25913    14811   -11102
+ Misses      13492     9998    -3494
+ Partials      109        0     -109

Flag
Coverage Δ

#cypress
?

#javascript
?

#python
59.70% <ø> (-1.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
31.91% <0.00%> (-59.58%)
:arrow_down:

superset/db_engine_specs/hive.py
53.90% <0.00%> (-30.08%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/presto.py
69.76% <0.00%> (-12.32%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.59% <0.00%> (-12.25%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/api.py
81.38% <0.00%> (-7.98%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/views/database/validators.py
78.94% <0.00%> (-5.27%)
:arrow_down:

... and 454 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 cd7392e...15681e7. Read the comment docs.


Permissions error on Marshmallow

When targeting API level 23 and attempting to use Google+ for signing in, I'm getting this error message:

With this stacktrace:
E/com.auth0.lock.LockActivity: Failed to authenticate user
E/com.auth0.lock.LockActivity: java.lang.SecurityException: Missing android.permission.GET_ACCOUNTS
E/com.auth0.lock.LockActivity:     at android.os.Parcel.readException(Parcel.java:1599)
E/com.auth0.lock.LockActivity:     at android.os.Parcel.readException(Parcel.java:1552)
E/com.auth0.lock.LockActivity:     at com.google.android.gms.plus.internal.zzd$zza$zza.getAccountName(Unknown Source)
E/com.auth0.lock.LockActivity:     at com.google.android.gms.plus.internal.zze.getAccountName(Unknown Source)
E/com.auth0.lock.LockActivity:     at com.google.android.gms.internal.zzpn.getAccountName(Unknown Source)
E/com.auth0.lock.LockActivity:     at com.auth0.googleplus.FetchTokenAsyncTask.doInBackground(FetchTokenAsyncTask.java:63)
E/com.auth0.lock.LockActivity:     at com.auth0.googleplus.FetchTokenAsyncTask.doInBackground(FetchTokenAsyncTask.java:46)
E/com.auth0.lock.LockActivity:     at android.os.AsyncTask$2.call(AsyncTask.java:295)
E/com.auth0.lock.LockActivity:     at java.util.concurrent.FutureTask.run(FutureTask.java:237)
E/com.auth0.lock.LockActivity:     at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
E/com.auth0.lock.LockActivity:     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
E/com.auth0.lock.LockActivity:     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
E/com.auth0.lock.LockActivity:     at java.lang.Thread.run(Thread.java:818)

This is because the GET_ACCOUNTS permission is required, and this is granted at runtime in Android Marshmallow. I could request this permission before starting LockActivity, but I'd argue it's far better UX for the user to be prompted for this permission only if they click on the G+ icon. Could you add this functionality?

It's in our TODO, but low priority. Meanwhile you could just compile targeting API 22


cjs export is broken

Importing this library and calling any of the function fails in node js.

For ex:
Both code snippets fails with error: encode is not a function
import bs58 from "bs58";

bs58.encode(...)

import * as  bs58 from "bs58";

bs58.encode(...)

Import statements only work in esm modules (if you have "type": "module" in package.json). For CJS can you try this instead?
const bs58 = require("bs58").default;

bs58.encode(Buffer.from("test", "utf8"));

in typescript the error persists if using cjs and require pattern is not desired

Sure I'll make a repo later in the week with reproduction. Using "typescript": "5.6.3",, the following error persists when importing bs58 with import bs58 from 'bs58':
The current file is a CommonJS module whose imports will produce 'require' calls; however, the referenced file is an ECMAScript module and cannot be imported with 'require'. Consider writing a dynamic 'import("bs58")' call instead.
  To convert this file to an ECMAScript module, change its file extension to '.mts', or add the field `"type": "module"` to '/code/rhino-core/packages/dvf-bridge-api-spec/package.json'.

For now I've reverted to v5 which does not have this issue

What is the NodeJS version?
Are you using external tools like bun or deno or something?
Even though bs58 is marked as an ESM, it contains the require exports for CJS inside package.json... so something in your build pipeline is so old that it can't comprehend the exports key of package.json...
We can look into this when you give us a small repository to try it out with.

Repository to reproduce the issue: https://github.com/arijoon/bs58-53

@Nesopie Said he'll work on it.
re: https://github.com/microsoft/TypeScript/issues/50466

Thanks, there's also a module-sync available with more recent versions of node, we're patching some of our deps to add this and it gets rid of the dual package issue at least on node https://nodejs.org/en/blog/release/v22.10.0

@arijoon Please review #56 and see if it fixes the issue.


update version to 3.1.3

What problem does this PR solve?
update version to 3.1.3

/run-all-tests

/run-all-tests

/run-all-tests

/merge


Add decimal_to_binary_ip.py

(Put an X inside the [ ] to denote check mark [X].)

[x] If creating a new file :

[x] added links to it in the README files ?
[x] included tests with it ?
[x] added description (overview of algorithm, time and space compleixty, and possible edge case) in docstrings ?

[ ] if done some changes :

[ ] wrote short description in the PR explaining what the changes do ?
[ ] Fixes #[issue number] if related to any issue

[ ] other

@goswami-rahul we are going to automate this soon with sphinx, so no need to sweat it.

@keon Thanks for the update. :+1:

Pull Request Test Coverage Report for Build 588

23 of 23 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 69.587%

Totals

Change from base Build 573:
0.1%

Covered Lines:
3272

Relevant Lines:
4702

💛  - Coveralls

Thanks!


Adding branch name

I'm not sure if this project is still maintained but I would love to get this last PR merged. Thanks.

Thank you. Published version 0.0.2


USB connection failed

I download this in my head unit and try to link with LivioSdlTester in my android mobile. Wifi/TCP link can be setup. However , I can't setup link in USB. Can anyone tell me how to link SDL in USB？
As @ilikegithubcom mentioned in other thread, he had an Android  App (Android proxy testing tool)  that connects HU with usb successfully.  Did anyone know where can I get it?

I have one more question, How to enable log to see USB related message ? I have tried to modified
elseif(CMAKE_SYSTEM_NAME STREQUAL  "Android")
....  set(ENABLE_LOG OFF)
to
elseif(CMAKE_SYSTEM_NAME STREQUAL  "Android")
....  set(ENABLE_LOG ON)
then try to cmake, however I cannot cmake successfully. Could anyone tell me how to enable log correctly?

Please verify that head unit supports libusb and has read and write permissions (default not read and write permissions).
At present, the log4cxx library of sdl_android_port can not work normally, please implement log function yourself.
Please implement testing tools yourself based on android_proxy.

thank you @ilikegithubcom , according to my log as below, it seemed there is permission issue at libusb. Could you have any suggested solution  on this permission issue ?
My log is as listed below:
transport_manager::transport_adapter::TcpTransportAdapter::Restore() [15:03:41][/mnt/SmartDesign/SDL/hmi_sdl_android/sdl_core/src/components/transport_manager/src/transport_manager_impl.cc][AddTransportAdapter][Line:310]Add device adapter 0x68fc25c0[sdl-usb-aoa] [15:03:57][/mnt/SmartDesign/SDL/hmi_sdl_android/sdl_core/src/components/transport_manager/src/usb/libusb/usb_handler.cc][ArrivedCallback][Line:261]libusb device arrived (bus number 2, device address 7) [15:03:57][/mnt/SmartDesign/SDL/hmi_sdl_android/sdl_core/src/components/transport_manager/src/usb/libusb/usb_handler.cc][DeviceArrived][Line:127]libusb_reopen failed: LIBUSB_ERROR_ACCESS [15:03:57][/mnt/SmartDesign/SDL/hmi_sdl_android/sdl_core/src/components/transport_manager/src/usb/libusb/usb_handler.cc][DeviceArrived][Line:127]libusb_reopen failed: LIBUSB_ERROR_ACCESS [15:03:57][/mnt/SmartDesign/SDL/hmi_sdl_android/sdl_core/src/components/transport_manager/src/usb/libusb/usb_handler.cc][DeviceArrived][Line:127]libusb_reopen failed: LIBUSB_ERROR_ACCESS [15:03:57][/mnt/SmartDesign/SDL/hmi_sdl_android/sdl_core/src/components/transport_manager/src/usb/libusb/usb_handler.cc][DeviceArrived][Line:127]libusb_reopen failed: LIBUSB_ERROR_ACCESS


pod install issue

When running pod install from any of the feature directories, I get the following error:

[!] CocoaPods could not find compatible versions for pod "Firebase/Core":
In snapshot (Podfile.lock):
Firebase/Core (= 5.7.0)
In Podfile:
Firebase/Core
None of your spec sources contain a spec satisfying the dependencies: Firebase/Core, Firebase/Core (= 5.7.0).
You have either:

out-of-date source repos which you can update with pod repo update or with pod install --repo-update.
mistyped the name or version.
not added the source repo that hosts the Podspec to your Podfile.

Note: as of CocoaPods 1.0, pod repo update does not happen on pod install by default.

I'm using Cocoapods 1.5.3. Running pod repo update before running pod install does fix the issue, but if that is the command we want developers to run by default, we should update the README to reflect this. Otherwise we should update the Podfile.lock files.

I think it's best to use pod install --repo-update here, since

People are most likely cloning this repo for the first time and installing pods, and
The Podfile.lock is always updated to the latest Firebase pods, increasing the likelihood that anyone forking the repo doesn't have those specs yet.

Created #540 to fix this.


Feature request: enable indentation style configuration

Hi 👋
Currently this formatter uses a fixed indentation Style: Allman.
My request is to enable the customization of this indentation style, at the bare minimum allowing OTBS as a valid style.
Appreciate any input in this request 🤗

Aah this option already exists! It's just not documented 😄
I was configuring Pretty JSON by reading the documentation in this repo and adding the configuration keys in Sublime Text's settings file. This works, but you can also press cmd + shift + p and type in json and select the Preferences: Pretty JSON Settings to see all the settings available. This is as close to the most up-to-date documentation you'll find 😄


pipeline not working

i created a pipeline in the es and specified pipeline="my-pipeline" in the river.toml config file.
But the indexed document does not seem to be processed by the pipeline. Please advise.
I am using the master branch.

I tried both es v6.8 and es v7.5. docs can be indexed but pipeline not working.

@siddontang 哥，pipeline这个功能可以用不？

目前发现table名称启用wildcard时，pipeline不起作用


Parsing of unused variables in pySHiELD

Describe the bug
DaCe orchestration failing when unused variables in pySHiELD microphysics module parsed. Specifically the sedimentation and icloud methods were passed unused variables, d0_vap, lv00, and cracw which would result in a ValueError. Variables have been since removed in PR 15
To Reproduce
Replace d0_vap and lv00 into sedimentation method and calls, and cracw into icloud method and calls. Make sure to use a dace backend, with the FV3_DACEMODE environment variable set to BuildAndRun to enable orchestration and running of the model in pace. To start run use:
mpirun -n X python -m pace.run <config yaml>
Expected behavior
DaCe should be able to use orchestration regardless of variable usage.
System Environment
Describe the system environment, include:

OS: RHEL 8.9
Backend used: dace:cpu
Environment variables set: FV3_DACEMODE=BuildAndRun
Compiler(s): gcc/12.3.0, python/3.11,
MPI type, and version: openmpi/5.0.0
netCDF Version: netcdf/4.9.2
If this bug came from a model run, which model: baroclinic_c12_orch_cpu.yaml

Another case popped up of the same issue: unused variables create a parsing issue in orch:dace:X.
Digging the issue lives in the gt4py/dace bridge.
In orchestration the StencilFactory uses a lazy_stencil (code) to defer build at JIT time. This system refers to the DaCeLazyStencil (code).
1/ When DaCe takes over to move the code under the SDFG IR, the __sdfg__ function gets executed. The stencil get packed into an unexpanded version which signature is given here as a simple list of the declared arguments.
2/ Later on as orchestration progresses, DaCe will turn the OIR  (GT last IR) into SDFG (here). The bug manifests here where the bridge attempts to build the inputs/outputs using the node.params list.
The bug is that by then the GT pipeline might have culled the parameter that existed in 1/ because it's unused. But 1/ promised to the system this parameter. Meanwhile, because 2/ listens to the OIR the parameter doesn't exist: bug.
To fix we need to have 1/ and 2/ agree. The issue is 1/ doesn't know what kind of operation will happen next and 2/ is logically looking at the "truth" coming out of the pipeline, neither one are wrong per se or have access to the right info.
One way to deal with would be to try and deactivate the optimization pass (skip attribute here] that culls unused parameters, but this might have side effect on performance. A better fix is to see if 1/ or 2/ can be changed without breaking both stencil and orchestration pipeline.


YARN-2300

Can one of the admins verify this patch?

need to merge YARN-1713 and YARN-2233 before to apply this one.


PytorchStreamReader failed reading zip archive: failed finding central directory

Anyone know how to issue this exception?

I have tried use_new_zipfile_serialization=False, but it doesn't work:

did you find some way to fix this?

Anyone know how to issue this exception?
I have tried use_new_zipfile_serialization=False, but it doesn't work:

did you find some way to fix this?

I met the same issue

i found the problem is because of the corrupt tmp weights file. you can check if there is something simliar.


Revert "create entities if missing"

This change reverts 096b0a2 as we originally made a conscious decision to not create entities via rpc_maas.  These entities should be created at provisioning time and a lack of existence could indicate a problem with host provisioning.  Also, the rpc_maas role fails to run with this commit in place.   It looks like the entity_count var gets re-registered even when the task is skipped resulting in there being no stdout field. In this case it would probably be best to just re-issue the count task again without a when condition.
This reverts commit 096b0a2a2bf679e326bbc9b75933c901ca3241c5.
Closes issue #149

Per comments in #147 I can be :+1: on this revert but created issue #155 to track the need to capture the reasoning for those decisions for future clarity.

Fair comments @stevelle -- thanks for raising.  I'd be more than happy to revisit if we want to create these missing entities but in light of the PR causing additional breakage I figured we could revisit this once rpc-extras is stable.  I'd be happy to get w/ you, @prometheanfire, and @git-harry to discuss.

we do need the allow for no swift and maas commit though, that's separate.
other then that, sure :D

@prometheanfire - based on the commit message, I think the purpose of this is to prevent the swift monitoring from being setup if swift is not deployed. The commit itself only appears to be preventing the remote checks/alarms from being created. If that is all correct I think it would be more appropriate for the guard to be in the main.yml task file.

Looking at it I can agree with @git-harry about moving the when to main.yml and will be an easy thumbs up on that patch.
Relatedly I find the roles/rpc_maas/tasks/main.yml file to be a little messy, currently. I would like to see the host tasks pulled out into their own include so I created a PR for this ( #168 ). It is not required for any of this work, but I will offer it as a quick refactor.

@git-harry that commit is needed for mass to run at all in a non-swift env.  If you have another fix to use instead I'm all ears, but don't revert that fix please (there's a reason it was in a separate commit).

treating this PR as now depending on #169 thx @git-harry

@prometheanfire I've removed the revert of 13ddcb5 as I think commit https://github.com/rcbops/rpc-openstack/pull/169/files is going to introduce initial issues. Once this PR goes through I'll look at https://github.com/rcbops/rpc-openstack/pull/169/files to see how we can ensure that swift.yml is only applied when we know swift is in the environment.

+1

Looks like commit 13ddcb5 doesn't even work (defined x should be x is defined), but rather than re-remove the commit from this PR I've created https://github.com/rcbops/rpc-openstack/pull/173.

+1 Merging.


[Event Request] Codeunit::1255 "Match Bank Payments" - Function Code - OnAfterCode

Could You please, add the following event to the codeunit 1255 "Match Bank Payments"
Object: Codeunit 1255 "Match Bank Payments"
Function: Code
Publisher Event: OnAfterCode
Reason: To implement custom business logic
Where is the event placed (see image attached)?:

At the end of the function Code
Insert the call to the event
OnAfterCode(BankAccReconciliationLine);
Event Code:
[IntegrationEvent(false, false)]
local procedure OnAfterCode(var BankAccReconciliationLine: Record "Bank Acc. Reconciliation Line")
begin
end;
Thanks in Advance

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Examples will not work

The examples won't work unless I use:
include GeoJSON
include GeoJSON::Coordinates

Error without this:
In lib/geojson/src/geojson/geometry/pseudo_geometry.cr:42:22

 42 | contents = CoordinateTree.new parser
                 ^-------------
Error: undefined constant CoordinateTree

The bigger problem is that the includes have to be at the top-level, and I'd rather not have it mixed into my whole environment.

I've not had time yet to test this, but my inclination is that I probably missed a require or include somewhere. I'll try to look into it soon.

@manveru Please take a look at the pull request if you get a chance. This is my first open-source project that I've released, and I want to learn as much as possible about both designing/improving a library interface and managing an open-source project.


complete-docs on type member

Bug Report

TSLint version: 5.12.0
TypeScript version: 3.2.2
Running TSLint via: CLI

TypeScript code being linted
class Foo {
  private someField?: { bar(): void };
}

with tslint.json configuration:
    "completed-docs": [
      true,
      {
        "classes": true,
        "enums": true,
        "functions": {
          "visibilities": [
            "exported"
          ]
        },
        "methods": {
          "privacies": [
            "public"
          ]
        },
        "interfaces": true,
        "namespaces": true
      }
    ],

Actual behavior
Documentation must exist for methods.

on the bar function.
Expected behavior
The type is not an interface but a type. I don't expect tslint to complain about it.

@buu700 mentioned in #4398:

Edit: Adding "locations": "all" to "methods" and "properties" fixed this. Is this expected?

💀 It's time! 💀
TSLint is deprecated and no longer accepting pull requests other than security fixes. See #4534. ☠
We recommend you instead use typescript-eslint to lint your TypeScript code with ESLint. ✅
👋 It was a pleasure open sourcing with you!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


How to pass all the values of the form to validate function

❓Question
I need two inputs together, so I have to pass form values to the validate function. Is there any way to do so as I tried few things and didn't get a response. I have my fields set in a js file like so
postal_code: {
    name: "postal_code",
    validate: (value) => {
      return postalCodeValidator(value, {
        required: false,
      });
    },
    inputProps: {
      seperator: "-",
      seperationCount: 5,
      length: 10,
      placeholder: "123456789",
    }
  },
The value passed in here is just the input value
And I'm rendering it in the following component
return (
    <>

      {React.cloneElement(props.children, {
        onChange: (e) =>
          setFieldValue(
            field.name,
            props.field.isHtmlInput ? e.target.value : e
          ),
        name: field.name,
        value: field.value,
      })}
      {meta.error ?
{meta.error}
 : null}
    </>
if the info is not enough please let me know.
I would greatly appreciate any help :)
Seriously, for immediate help, just ask your question on the #formik channel on Reactiflux.

@SobhanAminnejad if you put together a small codesandbox, I can take a look for you. Looking at the code above is a little difficult to see how the form is working together.

You might want to look into using Yup for validation, which can handle what it sounds like you're looking for and fits in very nicely with Formik.


Need react and es2015 to compile.

Got and error
ERROR in ./src/index.js
Module build failed: SyntaxError: /Users/fro/Learn/map-test/src/index.js: Unexpected token (5:16)
  3 | import App from './App';
  4 |
> 5 | ReactDOM.render(<App />, document.getElementById('root'));

I've added react and es2015 presets.

These are set in .babelrc aren't they?

Yeah, they are in .babelrc already.
Any chance you copied the boilerplate without the dotfiles?


Commands: Show full log

We discussed #6643 in a design meeting and decided on a different approach.
Instead of using IReportedLogState, we will whitelist the event IDs we want reported when --verbose isn't specified. If needed, we'll allow providers to add to the whitelist, but this is probably YAGNI.
Specifying --verbose will ignore the whitelist and report all events Debug and higher. (Or just all events depending how noisy it is.)

I started implementing this, and it is rapidly growing into something far more complex than where we started. Reverse Engineer has a significant amount of provider-specific messages that we would want to show on the default verbosity. We don't have a good way letting the providers tell us which messages they want us to show (this is what drove us to use a well-known category in the first place). Having operation-specific whitelists also adds additional complexity.
I'm coming to the conclusion that we should just show all the log messages in the tools. Logging is general-purpose and we've set the levels according to what we believe consumers are generally interested in. Our tools, like Kestrel, should be just another consumer. Specifying --verbose will merely lower the level of messages we show (from Information to Trace).
This has the added benefit of making warnings more visible to users. Currently, they only see things like model building warnings if they happen to be using Kestrel or explicitly turn on logging. This will expand that audience to anyone using Migrations.
If we find any of the levels inappropriate for the tools, we should question whether the level is appropriate in general. If we think it is generally right, but not right for the tools, we can fix up the level  in the tools.

@bricelam It looks like RE is logging warnings at the Warning level. Don't we just want to always output anything at that level? I.e. Logging at Information usually means LogLevel >= LogLevel.Information.

Yep. And I'm saying we should also output anything at Information level too--no more filtering of log messages.

I'm fine with that. I think we are still able to do ad-hoc filtering by eventId if we choose. E.g. SQL comes out at Information by default, but we could choose to only display it in verbose mode in the tool.

+1

👍


Use dataclasses with local_zone

It would be nice if load_zone would instead take a Python dataclass rather than a yaml string. This would cut down on the pyyaml pip requirement being needed.
If yaml functionality is still required, it for example could be moved into a separate method called load_zone_yaml, which would allow for the pip requirement to marked as an optional install for the users who want to use it. Also the loaded yaml data could be converted into a dataclass.
Example dataclass:
from dataclasses import dataclass
from typing import List

@dataclass
class LocalZone:
    name: str
    type_: str = "static"
    records: List[str] = []

Does that mean you will allow "load_zone" to take dataclass and a separate  "load_zone_yaml" function that takes in yaml? Or is it required to only have one function "load_zone"?

Just for backwards compatibility,
can you kept the load_zone like that and create a new one for the dataclass support ?

I can make the load_zone method take both yaml and the dataclass. That would keep the backwards compatibility.
Also is it possible to make the pyyaml requirement optional, so if you wanted yaml support you would install the pip package like this: pip install unbound_console[yaml]?

good for me if some documentations exits :)


Fix root value and context getter types

Description
This PR updates the ASGI and Django view to use the same return types as all other integrations (instead of just Any).
Unfortunately, as with the other integrations, we have to use # type: ignore for the default context we provide.
This will stay like that until we dictate a base class for contexts (or use PEP 696?).
Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[x] Enhancement/optimization
[ ] Documentation

Summary by Sourcery
Update the return types of get_root_value and get_context methods in ASGI and Django views to align with other integrations, enhancing type consistency. Add a release note documenting these changes.
Enhancements:

Update ASGI and Django view return types for get_root_value and get_context methods to be consistent with other integrations.

Documentation:

Add a RELEASE.md file documenting the changes in return types for get_root_value and get_context methods.

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

In this release, the return types of the get_root_value and get_context
methods were updated to be consistent across all view integrations. Before this
release, the return types used by the ASGI and Django views were too generic.
Here's the tweet text:
🆕 Release (next) is out! Thanks to @NucleonJohn for the PR 👏

Get it here 👉 https://strawberry.rocks/release/(next)


Add model: roberta-base-danish

Noticed that the model:
https://huggingface.co/DDSC/roberta-base-danish
was missing.

I see it in there? Can you double check?

ahh, you are right. I was looking for:
https://huggingface.co/flax-community/roberta-base-danish
But it seems like the model has been renamed. Should have noticed when I copied in the link.


Created an Index Page for importation and exportation

@Saber1Y you made a new commit without fixing this issue. Please kindly check and rectify


Version 6 404'in from UNPKG

Seems to be version 6 is 404'in from UNPKG

Also having issues with that. Using one of these solved the issue
`

`
Hope it helps!

yes, https://unpkg.com/swiper/css/swiper.min.css is down.
I'm using this as an import in a lot of projects, all sliders broken

What is the issue? There was a major release, which assumes braking changes. Check changelog or read the docs


Cannot read property 'timeout' of undefined when a describe() is nested directly inside another describe()

Hi there!
I have been writing dozens of Protractor tests for my current angular project and they all work.
I pasted tests to create a new set of tests, and noticed that if there is a describe nested directly inside another describe, I get a Cannot read property 'timeout' of undefined error and Protractor exits with code 100.
If I remove the nested describe, it works right away.
If there is an it before the nested describe, that works... so all of it seams extremely strange to me.
Here is the test and the error:
Code
/* eslint max-len: 0 */
/* eslint-env es6 */
'use strict';

var chai = require('chai');
var expect = chai.expect;
var chaiAsPromised = require('chai-as-promised');
var config = require('../../../../gulp/config');

chai.use(chaiAsPromised);

describe('Compléter la reception de l\'offre d\'acquisition', function describe() {
  var localhost = config.e2e.localhost;

  this.timeout(15000);

  describe('View mode:', function () {
    it('Should redirect the user to the /tableauoffre page when clicking on "Quitter"', function it() {
      browser.get('/tableauoffre');

      browser.waitForAngular()
        .then(function getFirstRow() {
          return element(by.id('table-0'))
            .all(by.css('tbody tr'))
            .get(0);
        })
        .then(function click(row) {
          return row
            .all(by.css('a'))
            .get(0)
            .click();
        })
        .then(function redirect() {
          return browser.getCurrentUrl();
        })
        .then(function click() {
          return element(by.id('quitter-btn'))
            .click();
        })
        .then(function url() {
          return browser.getCurrentUrl();
        })
        .then(function test(url) {
          expect(url).to.equal(`${localhost}/tableauoffre`);
        });
    });
  });
});

Error:
[11:21:24] Starting 'protractor'...
Using ChromeDriver directly...
[launcher] Running 1 instances of WebDriver
[launcher] Error: TypeError: Cannot read property 'timeout' of undefined
    at describe (/Users/[user-name]/Documents/banq/trunk/app/modules/views/assigner.offre/assigner.offre.e2e.js:15:7)
    at Suite.describe (/Users/[user-name]/Documents/banq/trunk/app/modules/views/assigner.offre/assigner.offre.e2e.js:21:3)
    at context.describe.context.context (/Users/[user-name]/Documents/banq/trunk/node_modules/mocha/lib/interfaces/bdd.js:47:10)
    at Object.<anonymous> (/Users/[user-name]/Documents/banq/trunk/app/modules/views/assigner.offre/assigner.offre.e2e.js:12:1)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
[launcher] Process exited with error code 100

/Users/[user-name]/Documents/banq/trunk/gulp/tasks/protractor.js:24
      throw err;
      ^
Error: protractor exited with code 100
    at ChildProcess.<anonymous> (/Users/[user-name]/Documents/banq/trunk/node_modules/gulp-protractor/index.js:63:27)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

Extra info:

Node Version: 4.4.5
Protractor Version: 2.2.0
Browser(s): Chrome
Operating System and Version Mac OS X El Capitan 10.11.5
Your protractor configuration file

'use strict';

exports.config = {
  allScriptsTimeout: 11000,
  baseUrl: 'http://localhost:3000/',
  directConnect: true,
  capabilities: {
    browserName: 'chrome',
    platform: 'ANY'
  },
  framework: 'mocha',
  jasmineNodeOpts: {
    onComplete: null,
    isVerbose: false,
    showColors: true,
    includeStackTrace: true,
    defaultTimeoutInterval: 30000
  }
};

At first glance it looks like this is the problem:
describe('Compléter la reception de l\'offre d\'acquisition', function describe() {

Describe has two parameters, a string and a callback function. Without trying your test out, it should probably look like:
describe('Compléter la reception de l\'offre d\'acquisition', function() {

Similarly for your it block:
it('Should redirect the user to the /tableauoffre page when clicking on "Quitter"', function it() {

should probably look like:
it('Should redirect the user to the /tableauoffre page when clicking on "Quitter"', function() {

Maybe also use beforeAll or beforeEach.
describe(‘some cool feature’, function() {
  beforeEach(function() {
     // go to a url
  });
  it(‘should not be able to buy something’, function() {
  });

  describe(‘with credentials’, function() {
    beforeAll(function() {
      // login
    });
    afterAll(function() {
      // logout
    });
    it(‘should be able to buy something’, function() {
    });
});

I am closing this issue. This sounds like a support question and hopefully these suggestions help. If you have additional questions please use StackOverflow, Google Group discussion list, or Gitter.

Also you shouldn't have to call waitForAngular. This function is executed for you to synchronize interactions, finding elements, etc.

@cnishina , naming a callback function is best JavaScript practice and helps debugging big call stacks... it does not change a thing in how code is executed if you remove the callback name.
Also, beforeAll or beforeEach does not make it work.
It seams that putting an it() function before the nested describe() works, but not if there is only a nested describe().

Well this depends, you defined a callback called "describe" then you are nesting the "describe" from the testing framework. I am surprised this is not causing an error.
❯ protractor conf_chrome.js
[16:30:21] I/hosted -  Using the selenium server at http://localhost:4444/wd/hub
[16:30:21] I/launcher -  Running 1 instances of WebDriver
Started
F

Failures:
1) restart check encountered a declaration exception
  Message:
    RangeError: Maximum call stack size exceeded
  Stack:
    RangeError: Maximum call stack size exceeded
        at describe (/usr/local/google/home/cnishina/src/protractor-examples/protractor/config_spec/spec.js:1:44)

here's my spec using the nested describe named function
describe('restart check', function describe() {
  describe('some random describe', function describe2() {
  beforeEach(function beforeEach() {
    browser.get(browser.baseUrl);
  })
  it('should greet the user', function() {
    element(by.model('yourName')).sendKeys('Julie');
    var greeting = element(by.binding('yourName'));
    expect(greeting.getText()).toEqual('Hello Julie!');
  });

Huh... you are actually right... If I remove or change the name of my parent callback to something other than describe, I no longer get the error... I didn't know that it had an actual impact. I was always under the impression that it was a "hidden" name.

Had the same issue, changing the parent callback name to something other than describe also solved it


Fix Rectangle instanitation with RAYGUI_CLITERAL

This makes creating a Rectangle use the RAYGUI_CLITERAL to fix some broken Windows builds.

@RobLoach Good catch! Thanks!


Details

Could you give some lighten about this project to quickly understand.

I'd love to give more details, but please be more specific what lighten is missing? The readme explains the desire for maintaining bare-metal k8s cluster using fence devices and monitoring for healthiness to recover stateful pods and re-join defected nodes to cluster.

I started to read about statefulset from https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/
I am able to understand basic usage of statefulset interms of reserving few resources to pods.
if node goes to not ready state, will automatically reboot it as per this node fencing.
correct me if i am wrong.

When node goes to not-ready the monitor will start fence flow which consists of 3 steps, each step contains method to run, reboot is one of them.
The node probably runs pods, part of them can relate to stateful set deployments - means that the scheduler won't start new instances until the node responsive again. Instead of waiting for the default eviction treatment, after rebooting\fencing the node successfully, the monitor will destroy those pods to trigger the re-scheduling

Hi @bronhaim @rootfs , Thanks for creating this project.
I wanted to know the current status of this project and if it is still in active development? There is not much activity on this project recently.
I am really interested fencing implementation for Kubernetes as its a big bottleneck to migrate Legacy application architecture.


Cannot use touch keyboard with password fields

See main issue at https://github.com/electron/electron/issues/13832 for details
It looks like the main Chromium project is already working on the fix for this problem, caused by a breaking change in Windows 10 1803 (https://chromium-review.googlesource.com/c/chromium/src/+/946928).
I've tried to backport it, but it looks like the patch refers to a new feature that has been introduced after the version currently embedded in Electron.

@conteit This should live over in electron/electron#13832, if someone gets some free time to tackle that patch they can look at it.


Update Tact to 1.0.0

https://t.me/tondevnews/81

Tact production ready is released. It is good thing, because we can be first project on Tact in production. Let’s do it!


Add the element to the event object (#653)

Always have the element available in the event object as the target can sometimes be the child of the element. Linked to issue #653

You can use srcEvent to get the original target, but the events and use and nature of these events do need improved.  This is not the correct Event API we'll be working towards.
Closing in favor of #807


Possible fix for Page Transition between [..uri].vue

I had an issue with my query's on the [...uri].vue in Nuxt 3, where the pages between the uri already loaded and after that they transitioned.
Changing the query from useFetch to useLazyFetch
Think this would also work for useAsyncData to useLazyAsyncData
I think the thing about it is that Fetch immediately takes the query up to the next frame, and with Lazy you have a well lazy moment.
Hope this fixes for everyone who encounters it.
Don't think it really is a bug/issue, rather then just a query which is very quick ;)
Originally posted by @TinyLightBold in https://github.com/nuxt/nuxt/issues/4132#issuecomment-1551655487

Thank you for the suggestion!
I'm going to close this as I think it's not something we can implement within Nuxt, either as a fix or an enhancement...

Unfortunately it gives an error on page change to [...uri].vue. When you refresh on that url after, then it loads in without issue and you can change pages as well with no problem.
title is in script setup
      useHead({
          title: data.value.title + ' - ProjectX'
      })

  Uncaught (in promise) TypeError: Cannot read properties of null (reading 'title')     at setup ([...uri].vue:338:29) setup @ [...uri].vue:338 Promis

Well, that's the point with LazyFetch, it render the page automatically.
It doesn't wait for the data. So you are trying to print to set a value which is still a pending promise there.


submemory_desc() and reshape() documentation and/or sample

Hi,
I'm trying to channelwise split-up a tensor, wich is in 99% of the cases in a blocked nChw8c or nChw16c format, in two equal parts to serve as the source of two depthwise convolutions.
I know i have to use the submemory_desc() with the desired dimensions and offsets but I don't how to
correctly create the memory and I don't find enough documentation or good sample on how to accomplish this in a efficient manner.
thanks

Hi @zulma46,
Submemory allows you to describe a sub-part of a memory. Submemory doesn't do any data copy or move -- it is solely a view of a bigger memory. BTW, in Intel MKL-DNN v0.x submemory was exactly called view.
Rough sketch of what should be done is:
// a big memory, that contains two slices
memory::desc input_md({n, c, h, w}, data_type, ...); // md for memory desc
memory input(input_md, ...);

// create submemory descriptors for the slices
memory::desc slice1_md = input_md.submemory({n, c/2, h, w}, offset={0,   0, 0, 0});
memory::desc slice2_md = input_md.submemory({n, c/2, h, w}, offset={0, c/2, 0, 0});

// conv for slice 1
memory::desc conv1_src_any_md({n, c/2, h, w}, data_type, memory::format_tag::any);
convolution_forward::desc conv1_d(conv1_src_any_md, ...);
convolution_forward::primitive_desc conv1_pd(conv1_d, engine);
memory::desc conv1_src_md = conv1_pd.src_desc(); // query what convolution wants

memory conv1_src = input; // in case the reorder is not required
                          // conv1_src would be simply the original (big) input
if (conv1_src_md != slice1_md) { // check, if reorder is required (most likely it is)
  conv1_src =memory(conv1_src_md, engine); // allocate buffer for conv1_src
  // emit reorder between the slice of the input and conv1_src
}

Please also check #306 and #69.

I don't find enough documentation or good sample on how to accomplish this in a efficient manner.

Yeah. We have plans to add some tutorials for submemory, but haven't done that yet :(

Thanks a lot!
Now it all make sense to me.


Beautify new fluxcd.io after docsy move

As indicated in #114 we will have some cleaning up and beautification to do once all content blocks are brought back.

[ ] bring back terminal
[ ] make project.html background color properly configurable

Regarding auto-headings: not sure it's easily possible: https://discourse.gohugo.io/t/front-matter-override-for-goldmark/26125/3 ... :man_shrugging:
It'd be great if we could use markup.goldmark.parser.autoHeadingID: false everywhere, but not on _index.md?

@hiddeco  I tried bringing back the terminal, but didn't quite manage.

I managed to remove the auto-headings on the landing page.

Regarding colours of blocks, e.g. project, according to https://www.docsy.dev/docs/adding-content/shortcodes/#shortcode-blocks we should be able to:

The block will be assigned a color from the theme palette if not provided, but you can set your own if needed. You can use all of Bootstrap’s color names, theme color names or a grayscale shade. Some examples would be primary, white, dark, warning, light, success, 300, blue, orange. This will become the background color of the block, but text colors will adapt to get proper contrast.

Project sections now have configurable background colours, etc.
Just needs to be prettier!


feat: Use reusePort when available.

Fixes #3604.

CI is not happy

Vite is still not happy: https://github.com/platformatic/platformatic/actions/runs/12280682345/job/34267840503?pr=3656

The last test failing could not pass on Win due to a fastify-vite bug, like all others Vite test using SSR. Disabled.

@ShogunPanda https://github.com/platformatic/platformatic/actions/runs/12293133941/job/34305319180?pr=3656#step:6:86 seems relevant


Use data from poedb instead of wiki

Data on wiki is often outdated, so better use datamined
https://poedb.tw/skilltree.php?c=keystone
or https://poedb.tw/us/json.php/Skilltree/keystone_list

This data is being used for notables and keystones. It doesn't contain the regular nodes unfortunately, which is why the Wiki is used for those.


feat(flow)!: More triggers

BREAKING CHANGE: more triggers

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


⚠ Bofrost.fr has degraded performance

In 16335d6, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 813 ms

Resolved: Bofrost.fr performance has improved in e9e3e83 after 7 minutes.


Cannot show subflow on touch devices

i.e. on iPad long-press on subflow (either nodes pane or flow editor) does not bring up any option to show the subflow contents.

I have the dame issuebon my android tablet

Lots of touch-related issues with subflows were fixed in 1.1.0 (and earlier). You can dbl click a subflow instance node and then click the 'edit subflow template' button in the edit dialog to access the subflow template.