Attempt to fix the permred "PostCommit Java IO Performance Tests - another attempt

A follow-up of PR (#32736)

remove setup-gcloud as they are not in java_tests and python_tests.

I see the following exception with the latest run(https://github.com/apache/beam/actions/runs/11278385415/job/31366711759):
org.apache.beam.it.gcp.bigtable.BigTableIOLT > testBigtableWriteAndRead FAILED
    org.apache.beam.it.gcp.bigtable.BigtableResourceManagerException at BigTableIOLT.java:120
        Caused by: com.google.api.gax.rpc.UnauthenticatedException at ApiExceptionFactory.java:116
            Caused by: io.grpc.StatusRuntimeException at Status.java:533

So sadly my proposed fix does not work...


Rename acronyms to camelcase

OTS, OD, EGTF, ACC, CACC, ASM, TrafCOD, XML, etc.

Renamed all classes in all projects. There might still be inner classes that have not yet been converted. We can convert them when we encounter one of the classes. The comments that point to the classes (e.g., a class javadoc descriptor) might still mention the old class name. A separate issue has been opened (Issue #17) to make the comments consistent.
For now, this issue about the renaming of the class names is closed.


Add regression test for https://github.com/Expensify/App/issues/15627

Coming from https://github.com/Expensify/App/issues/15627
Please add the following regression test:

Go to any workspace that doesn’t have an avatar
Go offline
Click on the Workspace avatar and upload any image
Navigate back
Go online
Verify the workspace avatar is not changed to a default/placeholder image

@applausebot Huh... This is 4 days overdue. Who can take care of this?

@applausebot Still overdue 6 days?! Let's take care of this!

@applausebot 12 days overdue. Walking. Toward. The. Light...

@applausebot 12 days overdue now... This issue's end is nigh!


update serde_bytes requirement from 0.10 to 0.11

Updates the requirements on serde_bytes to permit the latest version.

Release notes
Sourced from serde_bytes's releases.

0.11.5

Allow Cow<[u8]> and Cow<Bytes> to deserialize from owned bytes (#23)

Commits

7f2e508 Release 0.11.5
088a64c Add a clippy build in CI
8ac8657 Disable some clippy lints
bdc2336 Improve naming in ByteBufVisitor::visit_seq
65ac8a9 Merge pull request #25 from serde-rs/cow
0ed0ae6 Forward Cow<Bytes> de impl to Cow<[u8]>
737a915 Allow deserializing Cow<[u8]> to produce owned bytes
363c3c8 Update build status badge to GitHub Actions
7ae4832 Remove Travis configuration
9664706 Merge pull request #22 from serde-rs/actions
Additional commits viewable in compare view

Thanks!


Check vehicle state without waking vehicle

Problem: calling .vehicle_state() or other .vehicle_xxxx() wakes vehicle.
Solution: call .vehicles() first, and call .vehicle_state() or other .vehicle_xxxx() only if state is not 'asleep'
This should be documented in the README

Further to @apgodshall's comment, my brief poke suggested vehicles['state'] can also report online, unknown & offline. I think @apgodshall's suggestion is good but suspect you'd need to note that power=0 and leave the car alone or it will never sleep - so the logic is good but needs refining

Thanks, zmsp!


in website console give error message that show termination error in line two from jason

Environment (please complete the following information):

OS (e.g., Windows 10):
Extension version (e.g., 1.2.3):

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

Closing as incomplete. Please feel free to add more information if you have any and we can re-open the issue.


Implement "Total supply" graph

Currently, the "Native coin circulating supply" graph is not calculated correctly. It can be seen from the nature of the chart itself that it should have monotonically increased till the EIP-1559 was introduced and then started decreasing. Below is the mainnet graph, which does not follow this pattern.

Postponed for now

I think it shouldn't be complex, stats api gives the correct circulating supply, but graph shows incorrect supply,
This is total supply;
https://scan.parex.network/api?module=stats&action=ethsupply
And this is our burn address;
https://scan.parex.network/address/0x000000000000000000000000000000000000dEaD
And this is the circulating supply;
https://scan.parex.network/api?module=stats&action=coinsupply
Everything is OK, but stats & chart graph show wrong number,  I think it gets circulating supply from  address_coin_balances_daily table, and it also collects the balance of the burning address in this table, when I sum that table including burn address I get the same result with graph (by the way we changed burn adres before we compiled the code)


Adding additional flag to ignore show domains banner

Hi,
Because of the banner we can't really do cat domains | read.......sublert.py $domain -u as the banner pop-ups after scan.
It's hectic to add bunch of domains manually.

Hi,
Sublert doesn't support batch importing of domains yet but it's in the roadmap. I'll also add an option to skip the message whether you want to display the list of subdomains or not when you add a new domain to monitor.
Thank you for bringing it up.

On the other hand, you can add a bunch of domains by manually editing domains.txt but be careful of the newline character.

Hi,
This is now fixed. You can append "-q true" to your command to skip the user input question.
Thanks!


BUG: pixi keeps adding global package to %PATH% until it's too long

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
echo %PATH%
# do something with git
echo %PATH%
# notice duplication

Issue description
I recently started using pixi-controlled git for my (global) git setup on windows, and ran into a problem pretty soon:
E:\upstreams\scipy>git log
The input line is too long.
The syntax of the command is incorrect.

E:\upstreams\scipy>@SET "PATH=C:\Users\[...]\.pixi\envs\git\bin:%PATH%"

The last line provides a clue - it seems that pixi will add itself to the path for every invocation of git, leading eventually to a path that breaks windows' max size allowed for variables.
Expected behavior
Do not add %HOME%\.pixi\envs\<global>\bin to path on every invocation of a globally installed package.

Thanks! I think adding setlocal and endlocal fixes this. Will open a PR shortly.


Put Blob Upload return code should be 201

The spec defines the return type from a PUT Blob operation to be a 204 https://github.com/opencontainers/distribution-spec/blob/master/spec.md#put-blob-upload, but this disagrees with the conformance test https://github.com/opencontainers/distribution-spec/blob/master/conformance/03_blob_upload_monolithic_test.go#L29-L37.
As the conformance test agrees with existing implementations, and the 204 code seems inconsistent with other areas of the spec (e.g. PUT manifest returns a 201), I suggest the spec should be changed to show a 201 return.

This seems to be addressed. See current table of endpoints and status codes: https://github.com/opencontainers/distribution-spec/blob/master/spec.md#endpoints


Explicitly split distro/streamid

We still support a convenient "stream ID string" but it's now
fcos-stable and rhcos-4.8 i.e. an explicit 2-tuple of <distro>-<streamid>
intead of guessing fcos if it doesn't start with rhcos-.
Closes: https://github.com/coreos/stream-metadata-rust/issues/2

I don't think this completely addresses #2, because it still tries to combine the OS and stream name into one string.  We don't do that anywhere else: not in coreos-installer, not in stream-metadata-go, not in any of the build or release tooling.  Looking at the diff, I think it makes the most sense to remove stream_url_from_id() entirely, and have callers directly use something like the current fcos::StreamID::from_str(stream).

We don't do that anywhere else: not in coreos-installer, not in stream-metadata-go, not in any of the build or release tooling.

Yes, but I want to because it is convenient.

Looking at the diff, I think it makes the most sense to remove stream_url_from_id() entirely, and have callers directly use something like the current fcos::StreamID::from_str(stream).

So let's take kola today which has -b/--distro and -s/--stream.  Basically I feel the ergonomics would be nicer to type -s rhcos-4.8 instead of -b rhcos -s 4.8.  And leaves open some ambiguity around what happens if you just type -s.  Today most of our tools default to fcos - and there's nothing wrong with that inherently.  But...
When working on the dehydrator I want to clearly support both fcos/rhcos and it is just IMO clearer to not have a default.

Yes, but I want to because it is convenient.

It is always possible to combine unrelated things into a larger, complicated thing.  It's usually a bad idea.

When working on the dehydrator I want to clearly support both fcos/rhcos and it is just IMO clearer to not have a default.

I'm 100% okay with not having a default.  I also think it's fine for individual tools to expose this sort of hybrid argument if they want.  That tool is then responsible for splitting out the stream base URL and stream name.  (Big caveat though: users can create their own stream metadata if they want, e.g. for local mirroring, so there should be syntax for specifying the base URL explicitly.)  The objection is to inventing a hybrid thing called the "stream ID" and supporting it in core code, because that encourages tools to treat a slightly complex thing as simpler than it really is.

But you didn't quite offer an alternative. Are you arguing in favor of a kola-like separate --b/--distro and -s/--stream arguments?

I'd still prefer separate arguments, yes.  It avoids a bunch of parsing and unparsing, and having to think about syntax that's generic over distroname+stream and baseURL+stream.

I'm not totally sure I agree on separate vs concatenated...will think more about it.
But anyways this is obsoleted by https://github.com/coreos/stream-metadata-rust/pull/4


Question : What are events raised after condition test execution ? (VisibilityChanged...)

Hi,
I want to update UI after condition test execution.
It seems that I can suscribe only to "onVisibleChanged", unfortunately this event is raised, as indicated by his name, olny when the question visibility changes.
I would like to be notified any time.
Thanks for all,
Pascal

My problem will not be resolved only with an event raised after condition test execution. I have to wait that the question render execution is done to update UI.


Series' from_group filter merging instead of overwriting values

Expected behaviour:
Setting a from_group filter under a grouped series entry to use only that value.

Actual behaviour:
from_group tries to merge the Settings Group value with the specific show value.
If both the settings group's and shows' from_group are:

Lists: the values are merged, meaning we can't exclude a release group defined in the settings group (Show 2 in the example below will match both Group A and Group B. One would expect to only match Group B)
Mixed: If the from_group values defined in the show and the setting group have different formats (Show 3 in the example below), Flexget crashes (see Log below)
Single string: Works as intended, as in the specific value overrides the setting group's. Had I defined Group B under myshows, Show 1 would match Group B, Show 3 would match Group A as specifically defined (assuming Show 2 hadn't mixed formats to cause a crash as mentioned above)

Steps to reproduce:

Step 1: Have a series settings group
Step 2: Define from_group in the settings
Step 3: Assign a series to the settings group
Step 4: refine the series' setting with its own from_group

Config:
mytask:
  series:
    settings:
      myshows:
        from_group:
          - Group A
          - Group B
    myshows:
      - Show 1
      - Show 2:
          from_group:
            - Group B
      - Show 3:
          from_group: Group A

Log:

(click to expand)
2019-10-12 14:13 CRITICAL task          mytask BUG: Unhandled error in plugin configure_series: u"Merging key from_group failed, conflicting datatypes 'list' vs. 'unicode'."
Traceback (most recent call last):
  File "c:\python27\lib\site-packages\flexget\task.py", line 522, in __run_plugin
    return method(*args, **kwargs)
  File "c:\python27\lib\site-packages\flexget\event.py", line 23, in __call__
    return self.func(*args, **kwargs)
  File "c:\python27\lib\site-packages\flexget\components\series\configure_series.py", line 93, in on_task_prepare
    self.merge_config(task, series_config)
  File "c:\python27\lib\site-packages\flexget\components\series\series.py", line 327, in merge_config
    native_series = self.prepare_config(task.config.get('series', {}))
  File "c:\python27\lib\site-packages\flexget\components\series\series.py", line 294, in prepare_config
    config = self.apply_group_options(config)
  File "c:\python27\lib\site-packages\flexget\components\series\series.py", line 268, in apply_group_options
    merge_dict_from_to(group_settings, series_settings)
  File "c:\python27\lib\site-packages\flexget\utils\tools.py", line 181, in merge_dict_from_to
    % (k, type(v).__name__, type(d2[k]).__name__)
MergeException: u"Merging key from_group failed, conflicting datatypes 'list' vs. 'unicode'."

Additional information:

FlexGet version: 2.21.25
Python version: 2.7.16
Installation method: pip
Using daemon (yes/no): yes
OS and version: W10
Link to crash log:

Example 1 👍
Will overwrite the setting, accepting only GroupC.
The intended behavior as described in the wiki

Series may override any settings specified in group settings.

Config:
  mytask:
    mock:
      - title: '[GroupA] Cool Show - 01 [1080p]'
      - title: '[GroupB] Cool Show - 01 [720p]'
      - title: '[GroupC] Cool Show - 01 [360p]'
    series:
      settings:
        my_shows:
          from_group: GroupB
      my_shows:
        - Cool Show:
            qualities: ['1080p', '720p', '360p']
            from_group: GroupC

Log:
VERBOSE  details       mytask          Produced 3 entries.
VERBOSE  task          mytask          ACCEPTED: `[GroupC] Cool Show - 01 [360p]` by series plugin because quality wanted
VERBOSE  details       mytask          Summary - Accepted: 1 (Rejected: 0 Undecided: 2 Failed: 0)
WARNING  task          mytask          Task doesn't have any output plugins, you should add (at least) one!

Example 2 👎
In list format, from_group settings are merged instead of overwritten.
Config:
  mytask:
    mock:
      - title: '[GroupA] Cool Show - 01 [1080p]'
      - title: '[GroupB] Cool Show - 01 [720p]'
      - title: '[GroupC] Cool Show - 01 [360p]'
    series:
      settings:
        my_shows:
          identified_by: sequence
-          from_group: GroupB
+          from_group:
+            - GroupB
      my_shows:
        - Cool Show:
            qualities: ['1080p', '720p', '360p']
-           from_group: GroupC
+           from_group:
+             - GroupC

Log:
VERBOSE  details       mytask          Produced 3 entries.
VERBOSE  task          mytask          ACCEPTED: `[GroupB] Cool Show - 01 [720p]` by series plugin because quality wanted
VERBOSE  task          mytask          ACCEPTED: `[GroupC] Cool Show - 01 [360p]` by series plugin because quality wanted
VERBOSE  details       mytask          Summary - Accepted: 2 (Rejected: 0 Undecided: 1 Failed: 0)

Example 3 ⚠
Flexget crashes with mixed and matched value types.
Config:
  mytask:
    mock:
      - title: '[GroupA] Cool Show - 01 [1080p]'
      - title: '[GroupB] Cool Show - 01 [720p]'
      - title: '[GroupC] Cool Show - 01 [360p]'
    series:
      settings:
        my_shows:
          identified_by: sequence
-         from_group: GroupB
+         from_group:
+           - GroupB
      my_shows:
        - Cool Show:
            qualities: ['1080p', '720p', '360p']
            from_group: GroupC

Log:
CRITICAL task          mytask          BUG: Unhandled error in plugin series_db: u"Merging key from_group failed, conflicting datatypes 'list' vs. 'unicode'."
CRITICAL manager       mytask          An unexpected crash has occurred. Writing crash report to crash_report.2<IP_ADDRESS>923473000.log. Please verify you are running the latest version of flexget by using "flexget -V" from CLI or by using version_checker plugin at http://flexget.com/wiki/Plugins/version_checker. You are currently using version 2.21.30
WARNING  task          mytask          Aborting task (plugin: series_db)

Debug:
CRITICAL task          mytask          BUG: Unhandled error in plugin series_db: u"Merging key from_group failed, conflicting datatypes 'list' vs. 'unicode'."
Traceback (most recent call last):
  File "~\flexget\.install\lib\site-packages\flexget\task.py", line 522, in __run_plugin
    return method(*args, **kwargs)
  File "~\flexget\.install\lib\site-packages\flexget\event.py", line 23, in __call__
    return self.func(*args, **kwargs)
  File "~\flexget\.install\lib\site-packages\flexget\components\series\series.py", line 1099, in on_task_start
    config = self.prepare_config(task.config['series'])
  File "~\flexget\.install\lib\site-packages\flexget\components\series\series.py", line 294, in prepare_config
    config = self.apply_group_options(config)
  File "~\flexget\.install\lib\site-packages\flexget\components\series\series.py", line 268, in apply_group_options
    merge_dict_from_to(group_settings, series_settings)
  File "~\flexget\.install\lib\site-packages\flexget\utils\tools.py", line 181, in merge_dict_from_to
    % (k, type(v).__name__, type(d2[k]).__name__)
MergeException: u"Merging key from_group failed, conflicting datatypes 'list' vs. 'unicode'."

Adding list to these tuples solves the use-case above.
https://github.com/Flexget/Flexget/blob/ea11cdccce95c6513d8be9978bdd9d0baeb88b7b/flexget/utils/tools.py#L173-L174
Any immediate thoughts on what kind of issues this could incur on other plugins?


Remove indirection in notifying rummager

When a bet/query is updated we need to send the changes to rummager. Currently this is done via a MessageBus class that calls listeners with the attributes of the query.
This commit removes the MessageBus system in favour of calling the RummagerNotifier directly. This reduces the complexity and size of the code significantly without losing functionality.
This PR was started after researching an issue with a best bet in the search index (trello: https://trello.com/c/dvzAnQ80) which was slowed down due to having to understand the current process. This refactor will hopefully make things easier for other developers.

:clap: :tophat:


add missing colon

Proposed changes:

add missing colon
use better entity names in the example

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[x] updated the documentation
[ ] updated the changelog
[ ] reformat files using black (please check Readme for instructions)

I'm actually this passed the tests bc I don't think that should have correctly parsed as yaml? 🤔


Improve instructions for docker volumes

Pull requests:

https://github.com/Senzing/docker-init-container/pull/333


Mirrored repository doesn't overwrite changes pushed by users during mirroring

When a commit is pushed to a mirrored repository, the expectation is that any changes made by users are overwritten during the next mirroring process. However, this is not happening as expected.
The root cause lies in Central Dogma's limited check, which solely examines the stored local revision—unchanged by the user's commit—against the remote head.
https://github.com/line/centraldogma/blob/03540a1aee5ac7ee24c4b78ae04336706190ed74/server-mirror-git/src/main/java/com/linecorp/centraldogma/server/internal/mirror/AbstractGitMirror.java#L356

Hello @minwoox, I would like to take this issue, but still confused. Could you give me an example of what is expected and the current status, so I can try to reproduce it?

Say, there is Git repository A mirrored to Central Dogma repository B.
The content of A and B should be the same except for mirror_state.json. If some content is pushed to B repository, it should be overwritten by the content of A.
Currently, the changes pushed to B do not update mirror_state.json so the head revision comparison can't detect new commits in B.
We may solve the problem by storing the latest revision of B mirrored to mirror_state.json.

Thanks @ikhoon, I will try


Regression with v0.4.0

The issues described at https://github.com/minishift/minishift/issues/2380 and https://github.com/kubernetes/minikube/issues/1942 appear to now re-occur with the latest version when installing from Homebrew, although installing 0.3.3 manually works fine.

If you are looking to downgrade to 0.3.3_1 using brew, the following seems to work
https://raw.githubusercontent.com/Homebrew/homebrew-core/467aa378d7370a893d2af820384ff11cef4b9ff1/Formula/docker-machine-driver-xhyve.rb

@looselytyped
Error starting the VM: Error creating the VM. Error with pre-create check: "Virtual Box version 4 or lower will cause a kernel panicif xhyve tries to run. You are running version: 6.0.8r130520\n\n\t Please upgrade to version 5 at https://www.virtualbox.org/wiki/Downloads"

with your fix method. asks to upgrade virtualbox from major version 6 to major version 5

+1

AFAICT this is caused by backwards-incompatible configuration change introduced in #195 where the semantics of the Virtio9p driver config was changed from a bool to a []string.
If you recently updated via Homebrew you would have picked up this incompatible change. I suppose the change should have introduced completely new flags vs. reusing the same flag name and breaking existing machines.
I tried modifying ~/.docker/machine/machines/default/config.json to reflect the change but found it easier to blow away the machine and recreate it via docker-machine rm -f and docker-machine create.


Proxy

Updated proxy settings
Updated proxy settings README

I'm against proxy configurations in Vagrantfile. I believe we should document how to configure proxy settings (or just link vagrant-proxyconf documentation) and keep the main file as clean as possible, considering proxy problems are environment specific.

I agree and I think we've a bit on this way on README.
I hope this PR has a litle improvements in this way.
asap @gutocarvalho will merge it.


Extend graphql

Created custom resolvers in type graphql with validate-able arguments
Documented functions and types
Added some additional scripts
Removed artifacts

Close issues #28, #35


Build errors on Apple M1

Output of 'strings libarm_compute.so | grep arm_compute_version':
N/A
Platform:
MacBook Air (M1, 2020)
Operating System:
macOS Big Sur (11.2)
Problem description:
I am trying to build the Arm Compute Library on my Apple M1 MacBook Air with the following command (ACL v21.08, SCons 4.2.0 and Apple clang 12.0.5.):
scons Werror=1 -j8 neon=1 opencl=0 os=macos arch=arm64-v8a build=native

However I get the following compilation error:
src/cpu/CpuContext.cpp:31:10: fatal error: 'malloc.h' file not found
#include <malloc.h>
         ^~~~~~~~~~
1 error generated.
scons: *** [build/src/cpu/CpuContext.os] Error 1
scons: building terminated because of errors.

I was able to fix it by removing the include to malloc.h and using posix_memalign() instead of memalign(), but now I get this error:
ar rc build/libarm_compute_core-static.a
ar: no archive members specified
usage:  ar -d [-TLsv] archive file ...
	ar -m [-TLsv] archive file ...
	ar -m [-abiTLsv] position archive file ...
	ar -p [-TLsv] archive [file ...]
	ar -q [-cTLsv] archive file ...
	ar -r [-cuTLsv] archive file ...
	ar -r [-abciuTLsv] position archive file ...
	ar -t [-TLsv] archive [file ...]
	ar -x [-ouTLsv] archive [file ...]
scons: *** [build/libarm_compute_core-static.a] Error 1
scons: building terminated because of errors.

Thank you in advance.

Hi @keichi
On MacOS it looks like the AR tool fails if given an empty list of files.
To fix this please try the patch below:
iff --git a/SConscript b/SConscript
index 6420f31cf..04301fd3e 100644
--- a/SConscript
+++ b/SConscript
@@ -539,7 +539,14 @@ if env['os'] != 'bare_metal' and not env['standalone']:
     Export('arm_compute_so')

 # Generate dummy core lib for backwards compatibility
-arm_compute_core_a = build_library('arm_compute_core-static', arm_compute_env, [], static=True)
+
+if env['os'] == 'macos':
+       arm_compute_core_a = build_library('arm_compute_core-static', arm_compute_env, [lib_files], static=True)
+else:
+       arm_compute_core_a = build_library('arm_compute_core-static', arm_compute_env, [], static=True)
+
+
+
 Export('arm_compute_core_a')

Hope this helps.

Thanks for your advice but now I get:
scons: Reading SConscript files ...
NameError: name 'lib_files' is not defined:
  File "/Users/keichi/Projects/ComputeLibrary/SConstruct", line 409:
    SConscript('./SConscript', variant_dir=build_path, duplicate=0)
  File "/opt/homebrew/Cellar/scons/4.2.0_1/libexec/lib/python3.10/site-packages/SCons/Script/SConscript.py", line 660:
    return method(*args, **kw)
  File "/opt/homebrew/Cellar/scons/4.2.0_1/libexec/lib/python3.10/site-packages/SCons/Script/SConscript.py", line 597:
    return _SConscript(self.fs, *files, **subst_kw)
  File "/opt/homebrew/Cellar/scons/4.2.0_1/libexec/lib/python3.10/site-packages/SCons/Script/SConscript.py", line 285:
    exec(compile(scriptdata, scriptname, 'exec'), call_stack[-1].globals)
  File "/Users/keichi/Projects/ComputeLibrary/SConscript", line 519:
    arm_compute_core_a = build_library('arm_compute_core-static', arm_compute_env, [lib_files], static=True)

Hi @keichi
The code in the master dev branch has changed a bit, if you are using the code from GitHub you need to use core_files instead of lib_files
diff --git a/SConscript b/SConscript
index 02a9f45f4..669bbfb9d 100644
--- a/SConscript
+++ b/SConscript
@@ -515,7 +517,11 @@ if env['os'] != 'bare_metal' and not env['standalone']:
         Export('arm_compute_hp_so')

 # Generate dummy core lib for backwards compatibility
-arm_compute_core_a = build_library('arm_compute_core-static', arm_compute_env, [], static=True)
+if env['os'] == 'macos':
+       arm_compute_core_a = build_library('arm_compute_core-static', arm_compute_env, [core_files], static=True)
+else:
+       arm_compute_core_a = build_library('arm_compute_core-static', arm_compute_env, [], static=True)
+

Hope this helps.

Yes I am using the master branch from GitHub. After changing lib_files to core_files I was finally able to build the library. Thanks!

Fixed in next release with:
https://review.mlplatform.org/c/ml/ComputeLibrary/+/6706


Package won't install with Node LTS version

Bug Report
What is the issue?

As of 21/10/2019 Node.js LTS version is 12.x. current package lock has our version of node-sass which is used by gulp-sass locked to an incompatible version.
What steps are required to reproduce the issue?
Clone the repo
Using Node.js 12.13.0 run npm install
Installation fails due to incompatible node-sass with Node v12.x
What was the environment where this issue occurred?

NHS.UK frontend package version: 2.3.2
Node version: v12.13.0
npm version: 6.12.0

This has been fixed in https://github.com/nhsuk/nhsuk-frontend/pull/548
Thanks for raising and fixing @tomdoughty ⭐


US#233Task#240 Create a high level class diagram for unified-lms

@mrgutie8  Thank you for catching that. it was a missed change.


Reuse persistent HTTP connections

I noticed recently we don't reuse HTTP connections.  A new TCP/TLS/HTTP connection every request may add up to an order of magnitude speed difference:
https://bibwild.wordpress.com/2012/04/30/ruby-http-performance-shootout-redux/

[ ] HawkularClient creates a new RestClient instance for every single call.

[ ] Kubeclient does cache RestClient instance, but RestClient itself doesn't support connection reuse!
https://github.com/rest-client/rest-client/issues/453

[?] Net::HTTP when used directly does support persistent connections in limited scenarios (passing a block to .start).   I believe we use it through MiqFs for image scanning, not sure how exactly.

[?] @yaacov also told me one of the client libs (maybe in python though?) does API discovery anew before every single action.

After some reading, for fresh developement, httpclient or excon could be better than restclient, on several aspects.
For our existing code, https://github.com/drbrain/net-http-persistent (co-authored by tenderlove :-) sounds a good start.  I propose trying quick&dirty patch to use it in RestClient (and MiqFs), measuring how much we stand to gain, and working with RestClient to add at least opt-in option.

Further ahead, given connection reuse, could gain even more from HTTP/2, should keep it in mind when choosing gems.

@miq-bot add-label providers/containers, providers/hawkular, performance
/cc @lucasponce
Probably happens with other providers, a quick search through Gemfile.lock shows only excon used by fog & OpenstackHandle, httpclient used by WinRm.

does API discovery anew before every single action.

@cben 👍 , the ruby and python clients ask for the hawkular version each time they create a new connection object, and since we do not have a good way to reuse ( and stay updated, and not timeout, and ... ) the connection object is recreated almost(*) each new query.
(*) we do try to reuse when we can, clients are usually global and created using @client ||= Clinet.new(...)

(*) https://github.com/hawkular/hawkular-client-ruby/blob/02041e319eabc6851d0a5adf2319af3b83643ad9/lib/hawkular/base_client.rb#L40-L41
Would be an easy fix, not important without persistence in RestClient...
(and depending on implementation, connections could become cached across RestClient instances too)

=> Refresh is much better than I feared :-).  Not much point optimizing (until we get into targeted / watching refresh).

We do 1 GETs per entity type, eg. get_pods without args => /api/v1/pods, returning one huge json.
We do one /api/v1 and one /oapi/v1 discovery at start of refresh, probably from ems.with_provider_connection.  Perfect.

Tip: running under env RESTCLIENT_LOG=/tmp/rest.log is handy!
@yaacov when you have a chance doing metric collections / live metrics, do you mind setting RESTCLIENT_LOG and getting an idea how many requests total we do in that area?
@moolitayer same when you get a chance running Hawkular events/alerts polling?

@cben 👍
p.s.
you can look at the VCR recordings:
https://github.com/ManageIQ/manageiq/blob/master/spec/vcr_cassettes/manageiq/providers/kubernetes/container_manager/metrics_capture/capture_context_pod_metrics.yml

@miq-bot move-issue manageiq-providers-kubernetes


If webpack_public_path is a list, attempt each in order

What kind of change does this PR introduce?
It changes the behavior of the chunk loader, so that the onerror handler of the

Temporarily withdrawing this implementation while working through a bug in it.

Hi @micahcatlin, just wondering what ended up happening with this PR? I've been searching for a while for exactly this functionality. Thanks, David


#384 npm to install only prod dependencies for bundling

Description/Comments
#384
Checklist before opening PR

[x] Issue / PR description provided
[x] This feature has test coverage
[x] This feature has documentation (gcdt/docs)
[x] The changelog has been updated (CHANGELOG.md)

Contributor License Agreement
gcdt is an open-source project that is licensed very permissively (see LICENSE). This means that software, and other contributions to the project are released to the public to be freely used, modified, remixed, and even sold without anyone’s permission. In order to protect this freedom, contributors must agree to waive their rights to their contributions BEFORE contributing them.
By submitting a pull request to gcdt you agree to this Contributor License Agreement, you are waiving your rights to the intellectual property that you contribute to the gcdt project. You agree to put your contribution under MIT license.

Build triggered. sha1 is merged.

Build started sha1 is merged.

All is well

Hi Mark,
It's a nice feature and it will save some amount of time!
But as I mentioned here, as a lambda function developer I want to have a flag that skips node and packages installation at all because it takes a huge amount of time. While I develop, I have node and yarn(instead of npm) on a local machine and I use them for development as well as for building production bundle.

@Tonkonozhenko you refer to a different issue and I believe I answered to that already.


[CodeCompletion] SR-943 'self' for dot expressions

May dot expressions finally have a 'self' completion.
Resolves SR-943.

@xedin Was about to ask where the tests are.

What is the purpose of the -NOT, -DAG, -NEXT suffixes? Also, sometimes there is an end completions line, sometimes not, and it seems alright.

As for -NOT et al, see https://llvm.org/docs/CommandGuide/FileCheck.html#the-check-next-directive.
As for End completions line, I think there's no good reason unless it's CHECK-NEXT.

@rintaro Thank you. Is this alright as well (Not written by me)? (Note '7 items')
// FOO_OPTIONAL_1: Begin completions, 7 items
// FOO_OPTIONAL_1-DAG: Decl[InstanceMethod]/CurrNominal/Erase[1]: ?.myFunction({#(foobar): Bar#})[#Void#]; name=myFunction(foobar: Bar)
// FOO_OPTIONAL_1: Keyword[self]/CurrNominal: self[#Foo<Bar>?#]; name=self
// FOO_OPTIONAL_1: End completions

@benlangmuir can you help to understand how results are ordered?

Don't worry about reviewing the test files too much – I simply added the self or .self completion everywhere it was expected.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - c88e1c983fdf70318ced0de64663ffe83ed58f55

Build failed
Swift Test OS X Platform
Git Sha - c88e1c983fdf70318ced0de64663ffe83ed58f55

Wierd...I just ran the tests on the failed files and they passed.

How are SourceKit tests related to code completion?

SourceKit's completion is built on top of the code in lib/IDE.

My apologies, I did not suspect that I also needed to run sourcekitd-test.

@benlangmuir could you trigger the tests please?

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 7b41a41fb6d41be350211d03843635fb839a4888

Build failed
Swift Test Linux Platform
Git Sha - 7b41a41fb6d41be350211d03843635fb839a4888

In case you're not too busy, any nitpicks, @benlangmuir?

Nope, looks good.  Thanks!


python312Packages.qcodes: 0.49.0 -> 0.50.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.qcodes is: Python-based data acquisition framework
meta.homepage for python312Packages.qcodes is: https://qcodes.github.io/Qcodes/
meta.changelog for python312Packages.qcodes is: https://github.com/QCoDeS/Qcodes/releases/tag/v0.50.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.50.0 with grep in /nix/store/mg0h3kaqjaal9bpsml82srn58i0xlfs4-python3.12-qcodes-0.50.0
found 0.50.0 in filename of file in /nix/store/mg0h3kaqjaal9bpsml82srn58i0xlfs4-python3.12-qcodes-0.50.0

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

python311Packages.qcodes
python311Packages.qcodes-contrib-drivers
python312Packages.qcodes
python312Packages.qcodes-contrib-drivers

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mg0h3kaqjaal9bpsml82srn58i0xlfs4-python3.12-qcodes-0.50.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.qcodes https://github.com/r-ryantm/nixpkgs/archive/c97217a5ebc094c4bb86f3010489ca91a7176106.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c97217a5ebc094c4bb86f3010489ca91a7176106#python312Packages.qcodes

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mg0h3kaqjaal9bpsml82srn58i0xlfs4-python3.12-qcodes-0.50.0
ls -la /nix/store/mg0h3kaqjaal9bpsml82srn58i0xlfs4-python3.12-qcodes-0.50.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 8 packages built:

python311Packages.qcodes
python311Packages.qcodes-contrib-drivers
python311Packages.qcodes-contrib-drivers.dist
python311Packages.qcodes.dist
python312Packages.qcodes
python312Packages.qcodes-contrib-drivers
python312Packages.qcodes-contrib-drivers.dist
python312Packages.qcodes.dist

Maintainer pings
cc @evilmav for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

updated in https://github.com/NixOS/nixpkgs/pull/359127


Store authoritative copy of packages on Azure Blob Storage instead of self-hosted web server for faster uploads to CDN

Currently, the network architecture of this repository is Raspberry Pi → Azure CDN → self-hosted origin web server.

Pros: Free to operate, simple to program
Cons: Initial upload from origin to CDN is sort of fast but could be faster, and traffic is low enough that most requests are cache misses

A potential improvement is to move the authoritative source of the repo files from the self-hosted web server to Azure Blob Storage (like S3), which has a very fast connection to Azure CDN. Estimated additional hosting costs are about $0.25/month USD. Raspberry Pi → Azure CDN → Azure Storage ← repo generator.

Pros: Faster responses during CDN cache misses, theoretically higher reliability and less storage space used although these haven't been issues yet
Cons: Tiny cost, new and more complicated repo generation logic, blob storage does not generate HTML default index pages if you want to manually browse the directories

I've already created a blob storage account and container, and manually uploaded the most recent packages and metadata files for .NET 8.0.4.
Changes required to make repo generator program use blob storage directly

Assume no packages or metadata files are stored locally (easy)
Get rid of the most recently seen JSON file, we don't need that any more (easy)
Download current .NET release index JSON files from Microsoft (done)
Download all 6 uncompressed Packages metadata index files from Blob Storage: architectures [armhf, arm64] × Debian versions [10, 11, 12] (easy)
Parse Packages metadata index files (slightly complicated but fairly easy)
Generate each package locally that does not exist in blob storage already (mostly done)
Upload each new package to blob storage container, capped at # concurrent uploads using DataFlow, with correct content-type value (easy)
Generate updated package index files, including new and unchanged packages, and excluding outdated packages (mostly done)
Generate updated release index files based on updated package index files, and sign them (mostly done)
Upload updated package and release index files to blob storage, also with correct content-type headers (easy)
Purge CDN (done)
Delete outdated package files from blob storage (easy)
Delete local temporary working files like upstream SDK downloads, packages, and any index files, unless configured otherwise (easy)

Regular expression patterns to split and extract key-value pairs from package metadata control or index files:
\n{2,}

/(?<key>[\w-]+): (?<value>.+?)(?:\n(?! )|$)/gs

Azure CDN (Classic) by Microsoft does not have CDN preloading, unlike the EdgeIO CDN that I don't want to use because it's related to Verizon. Manual preloading by requesting each file would increase the billable traffic, take a long time, and would also probably only cache each file on one CDN edge server closest to the preloading client instead of all CDN servers, so any Raspberry Pis in different regions probably wouldn't benefit from the preloading.

Tutorial on accessing storage blobs programmatically

Repo regenerated fresh and uploaded to blob storage successfully.
Pointed Raspberry Pi 3 running Bookworm ARM32 at the test CDN host. It updated an existing .NET Runtime 8 installation successfully, as well as installing the .NET 8 SDK, and compiling and running a program.

Need to see if this can successfully perform a delta update on an existing repository in Blob Storage for a new .NET version, like the 8.0.8 update that was released after the repo was last built.

Uploaded partial repository regeneration to Blob Storage for .NET 8.0.8 update.
Migrated production CDN https://raspbian.aldaviva.com to point to Blob Storage instead of my on-premises server, so blob-backed repo is now live.

Will address cleanup later in a different task.


WIP : Add environment:getenv command

I am currently working on environment variables for Prestashop and I need an easy command to make my development / tests easier.
This command is under work but I let it there to receive comments or ideas for improvements ;)
If it is a problem, I can close it :)

Thanks for contribution 🎉
Looks fine but :

The command name / service name / classname must be consistent ( https://github.com/friends-of-presta/fop_console/runs/6364780235?check_suite_focus=true) - Currently there no tool to help you naming it, you should look at the existing ones to get information (#212) - (This should also be written in our contributing file).
just a question : how does it behave it an env value is not defined ?

Thanks for contribution tada
Looks fine but :
* The command name / service name / classname must be consistent ( https://github.com/friends-of-presta/fop_console/runs/6364780235?check_suite_focus=true) - Currently there no tool to help you naming it, you should look at the existing ones to get information ([DevTool : command to generate Class name, service name from a command name. #212](https://github.com/friends-of-presta/fop_console/issues/212)) - (This should also be written in our contributing file).

* just a question : how does it behave it an env value is not defined ?

Sorry it is still a draft but yes I will make it safier (testing if parameter exists before getting it)
Ok, I will add some comments/descriptions to the command ^^
For naming / standards, I'll try to understand and fix problem returned by CI ^^

@tom-combet do you have a minute for the service name ?
It looks correct but failed ... (I'll check too, later).

@SebSept It should be get_env instead of getenv.

@MeKeyCool Thanks for contribution!
I'll review it next week, too busy right now sry...

service name must be fop.console.environment.get_env.command (you overwrote my commit 😭 😄 ).

Thanks @MeKeyCool for you first contribution :) The command works fine and the parameters are in the help message, that's all good :)
Undefined values are spotted with a red background, that good. I suggest, you do the same for boolean values. Currently it's not possible to know if a configuration is false or an empty string, maybe you can render the boolean true and false with or style.
The other point it that it's can be better to have a try/catch block to avoid unclear errors that may happen (but will probably never happen). (not mandatory, but better imo)

I updated output styling.
I don't care strange errors cause in command line I don't think this problem would be critical nor hard to solve.


Add Tolerations and Affinity support

Hi there 👋
We were testing the project internally and noticed including Tolerations and Affinity support would be nice.
Hopefully this PR will do the trick.
Thanks for the great project!

Thanks for the PR. We do need this since adding taints for GPU nodes is common.
I did an initial review but let's wait for @nstogner to review too.

The quickstart e2e test CI is failing because kubeAI scaled down to 0:
[events -w] 0s          Normal   Killing                   pod/kubeai-56485ff664-mqpjg                Stopping container kubeai
[events -w] 0s          Normal   SuccessfulDelete          replicaset/kubeai-56485ff664               Deleted pod: kubeai-56485ff664-mqpjg
[events -w] 0s          Normal   ScalingReplicaSet         deployment/kubeai                          Scaled down replica set kubeai-56485ff664 to 0 from 1

@vlameiras Thanks for the PR! We were missing unit tests for the modified function so I added a PR into your branch to add those in as well as update the integration tests: https://github.com/vlameiras/kubeai/pull/1

Thanks for the quick replies and for the detailed comments!

Please ignore my previous comment about e2e quickstart CI failing. It was flaky and I have fixed the flakiness here: https://github.com/substratusai/kubeai/pull/205

I think we are good to merge once the changes to the default values.yaml file are reverted: https://github.com/substratusai/kubeai/pull/204#discussion_r1754920576


ddim sampler using /ai/generation-image API not working properly on nai-diffusion-v3.

If sampler set to ddim for /ai/generation-image with nai-diffusion-v3, it generates noised image.

On web page, it generates properly. but in EXIF, sampler shows as "Euler a" on parameters and "ddim_v3" on Comment.

It seems using ddim sampler via API needs more settings or something, but I cannot get additional settings or params for ddim from code.
I checked,

Euler a sampler generates different image.

I didn't check,

sending sampler as "ddim_v3".
sending "ddim" with other models.

By the way, on web page, if SMEA+DYN is checked with other sampler then change sampler to DDIM,
the generation costs 28 anlas, not 20 anlas even though DDIM cannot use SMEA or SMEA+DYN.

Fixed with 0f62c89c1fde1f50fb422a2886d1ed0320f22f4f


endSuite hook is called without matching startSuite hook

I'm creating this ticket due to ticket https://github.com/webdriverio/webdriverio/issues/13013
The summary of the linked issue is that endSuite might be called without a matching startSuite if a describe is used that has no tests. This can happen when dynamically generating its.
I'm not sure if it is strictly necessary for hooks to always be called pairwise (start + end) but it makes coding any state dependent hooks much easier.
Here is the diff that solved my problem:
diff --git a/node_modules/mocha/lib/runner.js b/node_modules/mocha/lib/runner.js
index 60a19f0..9103d9b 100644
--- a/node_modules/mocha/lib/runner.js
+++ b/node_modules/mocha/lib/runner.js
@@ -854,14 +854,13 @@ Runner.prototype.runSuite = function (suite, fn) {
   var total = this.grepTotal(suite);

   debug('runSuite(): running %s', suite.fullTitle());
+  this.emit(constants.EVENT_SUITE_BEGIN, (this.suite = suite));

   if (!total || (self.failures && suite._bail)) {
     debug('runSuite(): bailing');
     return fn();
   }

-  this.emit(constants.EVENT_SUITE_BEGIN, (this.suite = suite));
-
   function next(errSuite) {
     if (errSuite) {
       // current suite failed on a hook from errSuite
@@ -903,6 +902,7 @@ Runner.prototype.runSuite = function (suite, fn) {
     // remove reference to test
     delete self.test;

+    debug('done(): ending %s', suite.fullTitle());
     self.hook(HOOK_TYPE_AFTER_ALL, function () {
       self.emit(constants.EVENT_SUITE_END, suite);
       fn(errSuite);

This issue body was partially generated by patch-package.

Interesting find! Could you / someone please post an isolated reproduction we can take a look at here? One that doesn't require knowing other downstream tools like webdriverio. Thanks!
https://antfu.me/posts/why-reproductions-are-required


Debug email providers with native tiki-capture-receipt-capacitor

As a developer
I need to ensure that the email providers works with tiki-capture-receipt-capacitor
so that I can add them in the UI.
What it is now
The options are available but manual tests are not passing.
What it should be
The issues that doesn't allow the tests to pass are corrected in the native side and manual tests pass.
Acceptance criteria
Email login works for yahoo and AOL (Google and Outlook will work with OAuth)

The Outlook is crashing the app after click in "link account".

The Aol and Yahoo are falling into errors from microblink (Bad Email and Bad Password) when the credentials are wrong. When the credentials are correct, microblink throw error "unknown" and does not logs in.

We will use the POC app to test these issues https://github.com/tiki/tiki-capture-receipt-capacitor/issues/235


latest version not compatible with swift 2.3, 0.6.0 does not support crop heights.

@swaroopgs I am sorry but Fusuma does not support Swift2.3 now.


HDFS-16555. rename mixlead method name in DistCpOptions

Currently method in DistCpOptions withCRC was used as the following
withCRC(true) means check without crc
withCRC(false) means check with crc

which mislead the developer when we pass the paramter, we can rename the method to clear that.after that it should be:
withSkipCRC(true) means check without crc
withSkipCRC(false) means check with crc

so it will be more understandable.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
18m 12s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
42m 28s

trunk passed

+1 :green_heart:
compile
0m 42s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 39s

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

+1 :green_heart:
checkstyle
0m 38s

trunk passed

+1 :green_heart:
mvnsite
0m 44s

trunk passed

+1 :green_heart:
javadoc
0m 43s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 35s

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

+1 :green_heart:
spotbugs
1m 11s

trunk passed

+1 :green_heart:
shadedclient
23m 56s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 28s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
compile
0m 27s

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

+1 :green_heart:
javac
0m 27s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 20s

the patch passed

+1 :green_heart:
mvnsite
0m 29s

the patch passed

+1 :green_heart:
javadoc
0m 23s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 22s

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

+1 :green_heart:
spotbugs
0m 53s

the patch passed

+1 :green_heart:
shadedclient
23m 11s

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

_ Other Tests _

+1 :green_heart:
unit
47m 19s

hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

166m 15s

Subsystem
Report/Notes

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

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

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

uname
Linux 85b0f39e035c 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / a1637b1066309705f166914bd169b0fb4c8c837f

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

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

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

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4216/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.

api is tagged as @InterfaceAudience.Public;; we can't remove the existing method. you could add a new one with the better name and mark the old one as deprecated

api is tagged as @InterfaceAudience.Public;; we can't remove the existing method. you could add a new one with the better name and mark the old one as deprecated

Cool..Thanks @steveloughran  for your nice advice ,have just add the older method as deprecated and pushed

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  0s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
46m 17s

trunk passed

+1 :green_heart:
compile
0m 41s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 39s

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

+1 :green_heart:
checkstyle
0m 41s

trunk passed

+1 :green_heart:
mvnsite
0m 43s

trunk passed

+1 :green_heart:
javadoc
0m 44s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 36s

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

+1 :green_heart:
spotbugs
1m 11s

trunk passed

+1 :green_heart:
shadedclient
23m 26s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s

the patch passed

+1 :green_heart:
compile
0m 29s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 29s

the patch passed

+1 :green_heart:
compile
0m 26s

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

+1 :green_heart:
javac
0m 26s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

-0 :warning:
checkstyle
0m 20s
/results-checkstyle-hadoop-tools_hadoop-distcp.txt
hadoop-tools/hadoop-distcp: The patch generated 3 new + 6 unchanged - 0 fixed = 9 total (was 6)

+1 :green_heart:
mvnsite
0m 29s

the patch passed

-1 :x:
javadoc
0m 24s
/results-javadoc-javadoc-hadoop-tools_hadoop-distcp-jdkUbuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04.txt
hadoop-tools_hadoop-distcp-jdkUbuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04 with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04 generated 2 new + 41 unchanged - 0 fixed = 43 total (was 41)

-1 :x:
javadoc
0m 23s
/results-javadoc-javadoc-hadoop-tools_hadoop-distcp-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07.txt
hadoop-tools_hadoop-distcp-jdkPrivateBuild-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07 generated 2 new + 41 unchanged - 0 fixed = 43 total (was 41)

+1 :green_heart:
spotbugs
0m 54s

the patch passed

+1 :green_heart:
shadedclient
23m 18s

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

_ Other Tests _

+1 :green_heart:
unit
48m 20s

hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

153m 34s

Subsystem
Report/Notes

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

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

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

uname
Linux 6cdf3794faed 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 780054b20e18032271e986172cc3c9fc6cbdf53f

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

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

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

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4216/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.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  6s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 36s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 38s

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

+1 :green_heart:
checkstyle
0m 41s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 43s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 35s

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

+1 :green_heart:
spotbugs
1m  8s

trunk passed

+1 :green_heart:
shadedclient
23m 20s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 28s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
compile
0m 26s

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

+1 :green_heart:
javac
0m 26s

the patch passed

-1 :x:
blanks
0m  0s
/blanks-eol.txt
The patch has 1 line(s) that end in blanks. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

-0 :warning:
checkstyle
0m 20s
/results-checkstyle-hadoop-tools_hadoop-distcp.txt
hadoop-tools/hadoop-distcp: The patch generated 3 new + 6 unchanged - 0 fixed = 9 total (was 6)

+1 :green_heart:
mvnsite
0m 29s

the patch passed

+1 :green_heart:
javadoc
0m 25s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 23s

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

+1 :green_heart:
spotbugs
0m 53s

the patch passed

+1 :green_heart:
shadedclient
22m 59s

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

_ Other Tests _

+1 :green_heart:
unit
46m 55s

hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

147m 12s

Subsystem
Report/Notes

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

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

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

uname
Linux 555da745c2eb 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 5cfc52bf31b7e73ba8250d083ddedd69648f4a75

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

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

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

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4216/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
1m  8s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

-1 :x:
mvninstall
18m 25s
/branch-mvninstall-root.txt
root in trunk failed.

+1 :green_heart:
compile
0m 48s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 31s

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

+1 :green_heart:
checkstyle
0m 32s

trunk passed

+1 :green_heart:
mvnsite
0m 38s

trunk passed

+1 :green_heart:
javadoc
0m 37s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 29s

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

+1 :green_heart:
spotbugs
1m  5s

trunk passed

-1 :x:
shadedclient
8m 34s

branch has errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
compile
0m 27s

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

+1 :green_heart:
javac
0m 27s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 19s

the patch passed

+1 :green_heart:
mvnsite
0m 29s

the patch passed

+1 :green_heart:
javadoc
0m 24s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 23s

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

+1 :green_heart:
spotbugs
0m 54s

the patch passed

-1 :x:
shadedclient
8m 15s

patch has errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
50m 18s

hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

97m 15s

Subsystem
Report/Notes

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

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

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

uname
Linux d1ba26b9514f 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / dab1bbcd0cbb265c40fdebb1b344bece08884e9e

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

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

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

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4216/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
1m  1s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 35s

trunk passed

+1 :green_heart:
compile
0m 43s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 38s

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

+1 :green_heart:
checkstyle
0m 40s

trunk passed

+1 :green_heart:
mvnsite
0m 44s

trunk passed

+1 :green_heart:
javadoc
0m 44s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 35s

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

+1 :green_heart:
spotbugs
1m 10s

trunk passed

+1 :green_heart:
shadedclient
23m 41s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 29s

the patch passed

+1 :green_heart:
compile
0m 30s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 30s

the patch passed

+1 :green_heart:
compile
0m 26s

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

+1 :green_heart:
javac
0m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 20s

the patch passed

+1 :green_heart:
mvnsite
0m 29s

the patch passed

+1 :green_heart:
javadoc
0m 24s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 23s

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

+1 :green_heart:
spotbugs
0m 53s

the patch passed

+1 :green_heart:
shadedclient
23m 21s

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

_ Other Tests _

+1 :green_heart:
unit
48m 33s

hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

149m 32s

Subsystem
Report/Notes

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

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

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

uname
Linux 20e7a97b137b 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 587aba641dbf194a0d974d0387a30fe500c0a5e7

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

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

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

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4216/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.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
19m 30s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
40m 57s

trunk passed

+1 :green_heart:
compile
0m 43s

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

+1 :green_heart:
compile
0m 39s

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

+1 :green_heart:
checkstyle
0m 39s

trunk passed

+1 :green_heart:
mvnsite
0m 45s

trunk passed

+1 :green_heart:
javadoc
0m 44s

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

+1 :green_heart:
javadoc
0m 36s

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

+1 :green_heart:
spotbugs
1m 13s

trunk passed

+1 :green_heart:
shadedclient
23m 16s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 28s

the patch passed

+1 :green_heart:
compile
0m 32s

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

+1 :green_heart:
javac
0m 32s

the patch passed

+1 :green_heart:
compile
0m 26s

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

+1 :green_heart:
javac
0m 26s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 20s

the patch passed

+1 :green_heart:
mvnsite
0m 30s

the patch passed

+1 :green_heart:
javadoc
0m 23s

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

+1 :green_heart:
javadoc
0m 23s

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

+1 :green_heart:
spotbugs
0m 54s

the patch passed

+1 :green_heart:
shadedclient
22m 42s

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

_ Other Tests _

+1 :green_heart:
unit
47m 16s

hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 44s

The patch does not generate ASF License warnings.

165m 20s

Subsystem
Report/Notes

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

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

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

uname
Linux 7072f516dc64 4.15.0-175-generic #184-Ubuntu SMP Thu Mar 24 17:48:36 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 68e501c931618a65d46a9eebc2b12ffd0dabadc5

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

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

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

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4216/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.

merged to trunk and branch-3.3. thanks

Thanks @steveloughran for your review and merge~


Update of deck-gl versions to 8.9.34 with fixed CI and drop EOL Python 3.6 and 3.7

About
this is https://github.com/plotly/dash-deck/pull/20 with my changes that fix CI and an update to deck.gl 8.9.34
Description of changes

Pre-Merge checklist

[ ] The project was correctly built with npm run build.
[ ] If there was any conflict, it was solved correctly.
[ ] All changes were documented in CHANGELOG.md.
[ ] All tests on CircleCI have passed.
[ ] All Percy visual changes have been approved.
[ ] Two people have :dancer:'d the pull request. You can be one of these people if you are a Dash Deck core contributor.

Reference Issues

Closes #[issue number]
Other comments

@graingert-coef FYI, I was about to make a release (tentatively 0.1.0 but I'm tempted to call it 1.0.0 if we get it fully working) but noticed some errors running demos/usage-events.py:

I didn't try with just this PR so it's possible #26 caused this, though that one should be fairly uncontroversial. My hunch is the structure of certain events got more complex with the new deck.gl version, but it's not clear to me which events are causing this. I also haven't tried any of the other demo apps yet. v0.0.1 does not have this issue.


feat(Project): Advanced datatable

Add sorting
Add searching
Use CustomElement
Add nested object support
Remove pagination

Add LICENSE (you can copy it from aurelia-api)
add CONTRIBUTING (you can copy it from aurelia-api)

Running gulp lint results in errors.

To allow the key spacing you have to add the following rule to your .eslintrc
{
  "extends": "./node_modules/aurelia-tools/.eslintrc",
  "rules": {
    "key-spacing": 0
  }
}


Support for MongoDB built with SSL

I have been creating a Scala Play application and would like to use ReactiveMongo, but as far as I can tell there isn't any way to provide SSL options when creating a database connection.  Are there any plans to add support for connecting to a MongoDB that has been built with SSL support?

What's the status on this? Is there a fork/branch compatible with <IP_ADDRESS>.akka23?

Hi guys. Those interested could give a try to SSL support on master #286 .

Can we please have a release with this patch? SSL support if pretty important to wait till 0.11 release.

The milestone 0.11.0-M1 can be used (published on Maven central repo).

@cchantep thanks for releasing a milestone. Can you tell me what is in 0.11.0-M1 over and above this fix?

0.11.0-M1 is feature complete : new command API, SSL support, MongoDB 3 support, new streaming API, convenient collection operations (count, runCommand).
No change is planned for the driver from M1 to release (still some work on the Play plugin), but documentation.

excellent! and thanks

Awesome! Thanks a lot!

Is it now available in 0.11.4 ? Because I am using this very latest version and I still get this warning when trying to connect to a Mongo URI with SSL:
Some options were ignored because they are not supported (yet): ssl

@epot I suggest you have a look at the documentation to check which SSL options are available. For more question, then please use the MailingList. Best regards.


Chef 12.7.2 && omnitrucker.rb

After update to chef 12.7.2 got this error
Recipe: custom_cb::default
  * chef_gem[chef-sugar] action upgrade (up to date)

  ================================================================================
  Recipe Compile Error in /var/chef/cache/cookbooks/custom_cb/recipes/default.rb
  ================================================================================

  NameError
  ---------
  uninitialized constant Chef::REST

  Cookbook Trace:
  ---------------
    /var/chef/cache/cookbooks/omnibus_updater/libraries/omnitrucker.rb:84:in `url'
    /var/chef/cache/cookbooks/omnibus_updater/recipes/downloader.rb:27:in `from_file'
    /var/chef/cache/cookbooks/omnibus_updater/recipes/default.rb:25:in `from_file'
    /var/chef/cache/cookbooks/custom_cb/recipes/_packages.rb:9:in `from_file'
    /var/chef/cache/cookbooks/custom_cb/recipes/default.rb:23:in `from_file'
    /var/chef/cache/cookbooks/custom_cb/recipes/default.rb:12:in `from_file'

  Relevant File Content:
  ----------------------
  /var/chef/cache/cookbooks/omnibus_updater/libraries/omnitrucker.rb:

   77:        if(url_or_node.is_a?(Chef::Node))
   78:          url = build_url(url_or_node)
   79:          node = url_or_node
   80:        else
   81:          url = url_or_node
   82:          raise "Node instance is required for Omnitruck.url!" unless node
   83:        end
   84>>       request = Chef::REST::RESTRequest.new(:head, URI.parse(url), nil)
   85:        result = request.call
   86:        if(result.kind_of?(Net::HTTPRedirection))
   87:          result['location']
   88:        end
   89:      end
   90:
   91:    end
   92:  end
   93:

All was ok on Chef Client, version 12.6.0

See discussion here: https://github.com/hw-cookbooks/omnibus_updater/pull/94

I would encourage you to also raise this issue with Chef (possibly the Chef Board of Governance), as it seems it was introduced with the release of 12.7, which should not have broken existing functionality (from the Contributing doc):

X is a major release, which may not be fully compatible with prior major releases
Y is a minor release, which adds both new features and bug fixes
Z is a patch release, which adds just bug fixes

We're looking to address this in this cookbook asap; however, at this time the cookbook may only be compatible with chef =< 12.6.

with the pull request merged can we get this version with the fix added to the chef supermarket?

@Stromweld #94 was merged and released in omnibus_updater version 1.0.6 .. it is available on the supermarket.


Kalman filter fails in low speed scenario

Hi , in you papars, says Kalman filter fails in autonomous driving scenario.
So Which motion Filter should using ??

I have the same question.

I think the paper said you need ReID models. Did you guys try particle filter?

I think the paper said you need ReID models. Did you guys try particle filter?

Not tried yet. Will it be better than Kalman filter in autonomous driving scenario?


Delete the line 'npm install'

This is already done by the command 'vue init ..' which installs the node_modules/

True, this is relatively new with the upgrade. I should actually revisit these docs now, thanks for the reminder.


[improve][io] Upgrade Debezium to 1.9.7

Motivation
Upgrade debezium to 1.9.7 final to pick up latest fixes.
Modifications
Dependency upgrade
Verifying this change

[ ] Make sure that the change passes the CI checks.

Does this pull request potentially affect one of the following parts:

[X] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: https://github.com/dlg99/pulsar/pull/5

Codecov Report

Merging #18465 (c4cdc15) into master (dcf0b60) will decrease coverage by 10.66%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             master   #18465       +/-   ##
=============================================
- Coverage     47.24%   36.58%   -10.67%
+ Complexity    10440     1939     -8501
=============================================
  Files           697      208      -489
  Lines         67974    14383    -53591
  Branches       7276     1573     -5703
=============================================
- Hits          32116     5262    -26854
+ Misses        32284     8546    -23738
+ Partials       3574      575     -2999

Flag
Coverage Δ

unittests
36.58% <ø> (-10.67%)
:arrow_down:

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

Impacted Files
Coverage Δ

...he/pulsar/client/impl/PartitionedProducerImpl.java
30.34% <0.00%> (-5.13%)
:arrow_down:

...va/org/apache/pulsar/client/impl/ProducerImpl.java
15.84% <0.00%> (-1.17%)
:arrow_down:

.../pulsar/client/impl/ProducerStatsRecorderImpl.java
84.04% <0.00%> (-0.62%)
:arrow_down:

...ar/broker/transaction/util/LogIndexLagBackoff.java

.../pulsar/broker/service/BrokerServiceException.java

...rg/apache/bookkeeper/mledger/impl/OpReadEntry.java

...ansaction/buffer/TransactionBufferClientStats.java

...mledger/impl/cache/RangeEntryCacheManagerImpl.java

...ersistentStickyKeyDispatcherMultipleConsumers.java

...d/jcloud/impl/BlobStoreBackedReadHandleImplV2.java

... and 482 more


option to expose graphql api + visualizer with ingress

so that we can use it for visualizer.
currently, it's set to this one: https://github.com/kusaridev/helm-charts/blob/9f53560e1df0a79c7fe9db0239a15a83d4856acf/charts/guac/templates/guac-cm.yaml#L26
which is not accessible by visualizer

Pending review and merge of https://github.com/guacsec/guac-visualizer/pull/23, which will allow graphql api endpoint to be configurable.

@sunnyyip is this issue closed?

Not yet, now that we put a proxy in front of the visualizer to workaround how it finds the gql server, we can create ingress as the subject suggests.


Bump version: 0.2.1 → 0.2.2

Codecov Report

Merging #180 (044313c) into main (30f5aef) will decrease coverage by 0.13%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #180      +/-   ##
==========================================
- Coverage   76.85%   76.72%   -0.13%
==========================================
  Files         110      110
  Lines        5513     5513
  Branches      715      715
==========================================
- Hits         4237     4230       -7
- Misses       1118     1128      +10
+ Partials      158      155       -3

Impacted Files
Coverage Δ

tributary/_version.py
100.00% <100.00%> (ø)

... and 3 files with indirect coverage changes


Support Open Developer Tools command

Right now VS Code supports

Is it possible to support "Open (non-webview) Developer Tools" as well? It seems under the hood it
s already supported, just not exposed to users:
https://github.com/microsoft/vscode/blob/f74e473238aca7b79c08be761d99a0232838ca4c/src/vs/platform/electron/electron-main/electronMainService.ts#L461
To briefly describe my use case, I'm developing a VSC extension where I would like users to see Developer Tools window when the extension is activated. Right now since we only have the "toggle" operation, if the devtools is already opened, it would close the devtools window.

Can you explain a bit more on why your extension wants to open the devtools ?
this is possible technically but I will let @bpasero drive the discussion about if this needs to be supported. Having more context about your extension and use case will help drive the discussion. Thanks!

Sure. I'm working on an extension that logs runtime information and visualize how each variable changed during execution. When users hover on a node (think of it as a variable at a specific point of execution), we use console.log to print that value in console so users can inspect it.
I decide to use the console to display values because:

It is not a debugger so displaying values in tree view is not so easy (I could be wrong)
More importantly, I find that the output of console.log is nicely formatted, and is scalable to show data sturcture with a large number of elements (compared to values displayed in tree view and popup, which are not able to show every element due to not having enough space).

Therefore, I would like to open the devtools window when extension launches, so users don't have to do it themselves.
From the API design perspective, it is more intuitive if consistency is kept. Therefore even without specific use cases (though I'm pretty sure there are many), having webview/non-webview devtools expose the same APIs, IMHO, is better than exposing different APIs.

This is an abuse of the developer tools. The developer tools should only be used for development of VS Code or for development of extensions, they should never be shown to users.
Instead, try using VS Code's debug console or output channels or finding some other way to surface this information in VS Code itself. Don't use the developer tools
Closing as the use case is invalid, even if the feature request for a new command is innocuous on its own.

I respectfully disagree. The debug console serves a different purpose and it is not capable of doing what the devtools console can do.
First, the debug console is designed to support user interactions, but merely serves as a way to show logs.
Second, the debug console is not able to display large data sturctures, like a list with thousands of elements.
The usage shouldn't be considered an abuse because currently there is no way of achieving the same behavior in VS Code. If it is not supported natively, I would have to ask users to open the devtools window themselves, as the debug tools is not capable of serving the purposes I need.
Meanwhile, I see no reason to support Open Webview Dev Tools but not Open Dev Tools. I hope the decision can be reconsidered.

If the current VS Code apis don't offer what you need, please file a feature request. Again, the developer tools are only for VS Code development. They will not work on web versions of VS Code and it is not a good user experience to pop up the chrome dev's tool of the editor instance itself in order to show logs

By "Visual Studio Codespaces" do you mean codespaces?
I will file a feature request.


General.Implementation of valid text for all pages

https://projects.invisionapp.com/share/K48TJ5C86#/screens/193951621/comments
https://projects.invisionapp.com/share/FB5TXXJ6J#/screens/131899239 - services

Main page:
WANT TO WORK WITH US
Would you like to discuss how Valor Software can help with your software needs?
Should be:
WANT TO WORK WITH US?
Discuss how Valor Software can help with your software needs.
Main page: They are people and organizations with ambitious missions. They want to unleash the power of software for their cause or business. We help them envisage, design and deliver.
Should be: We work with individuals, startups, and large organizations, who want to unleash the power of software for their cause or business. We help them envisage, design and deliver.

Main page:
Was: Our UI/UX designers produce the most eye-catching designs for your product
Should be: Our UI/UX designers produce the most attractive and polished designs for your product
Approach:
Was: Listen. Agile. Deliver
Should be: Listen. Align. Deliver
Was: We help enterprises accelerate software-to-market by building collaborative relationships, using lean requirements and Agile methodologies. We guarantee value to our clients with our UX and engineering expertise.
Should be: We help enterprises accelerate software-to-market by building collaborative relationships, using lean requirements and effective methodologies. We guarantee value to our clients with our UX and engineering expertise.
Was: We're letting the client decide the priority of feature implementation, so the team knows what’s most important for the customer’s business, this way we provide the best business value.
Should be: We're letting the client decide the priority of feature implementation, this way we can provide the best business value.
Was: We always provide an opportunity to refine and re-prioritize the overall product backlog. New or changed items can be can be properly planned for the next iteration to introduce changes within a few weeks.
Should be: We always provide an opportunity to refine and re-prioritize the overall product backlog. Our team will properly plan the next iteration to introduce changes within a few weeks.
Was: We define the vision and the scope of the project. Iterations, roadmaps, all goes here to make sure further steps will go buttery-smooth.
Should be: Defining the vision and the scope of the project in order to make sure further steps will go buttery-smooth.
Was: Our developers are doing their code magic to develop the most refined product to make our clients and their customers happy!
Should be: Our developers are doing their code magic to develop the most refined product to make sure our clients are happy!
Was: Our DevOps specialists will deploy the production-ready product on the reliable and stable environment. (P.S We're also good at support and maintenance)
Should be: Our DevOps specialists deploy, support and maintain production-ready product on the reliable environment.
Footer:
Was: WANT TO WORK WITH US
Should be: WANT TO WORK WITH US?
Contact:
Was: To discuss how Valor Software can help with your ambitious software needs fill the form below to get in touch!
Should be:  Fill the form below to discuss how Valor Software can help with your ambitious software needs!
Was: Let's chat
Should be: We'd love to hear from you!
Was: WE ARE AT SOCIAL
should be: WE ARE SOCIAL
Services:
Was: Producing engaging content is not enough, but making eye-catching organization and showing care about the reader will do the magic!
Should be: Engaging content is not enough, but making eye-catching organization and showing care about the reader will do the magic!
Was: Regardless of the browser, which is used by your client, he will receive the same experience in any of them. We're always up to date with cross-browser testing.
Should be: Regardless of the browser, everyone will receive same experience in any of them. We're always up to date with cross-browser testing.
Was: Your website will be created using best practices for search engine discoverability along with deep Google Analytics integration.
Should be: Enhancing and improving website search engine discoverability along with deep Google Analytics integration.
Was: All platforms have their own user experience guidelines and rules. To align them with your project, we develop a proof of concept, an interactive visualization of the app.
Should be: To align user experience guidelines with your project, we develop a proof of concept, an interactive visualization of the app.
Was: We're always trying to be up to date with latest technologies and development techniques, to create the most quality mobile applications for our clients..
Should be:  To develop modern mobile applications for our clients, we constantly learning new technologies and techniques.
Was: With in-depth testing experience with nearly every operating mobile system, focus on delivering QUALITY apps to everyone of our clients is in our DNA
Should be: Focus on delivering quality apps to every one of our clients is in our DNA.
Was: Node.js is designed for high-load projects, it handles all requests in a single process, due to the evented model, as a result, it being able to handle thousands of concurrent requests..
Should be: Node.js is designed for high-load projects, it is able to handle thousands of concurrent requests.
Was: We go hand in hand with technology and using Node.js, which is one of the fastest-growing projects on the Internet , we can do more for you!
Should be: We go hand in hand with technology and by using Node.js, we can do more for you!
Was: Due to modular nature of Node.js, it is really easy for us to support and maintain your application or service in future. We tend to build future-proof projects!
Should be: We tend to build future-proof projects. With Node.js modularity support and maintenance is a piece of cake!
Was: Look at it (wut?)
Should be: See

Vacancies:
Sales Manager
Description
The sales analyst is responsible for leads generation process, analyzing sales force realignment requests, acting as liaison on sales automation issues, developing distribution capability for promotional materials, designing and maintaining sales reports, and evaluating third-party solutions for appropriate sales operations functions.
Responsibilities

Lead generation (from gathering information about responsible person till the first contact)
Ability to work with Hubspot CRM
Ability to work in team (the full project lifecycle in an Agile/SCRUM environment)
Make an analysis of funnel sales at first levels of interaction with leads
Ability to write cold e-mails and calls
Creating Proposal presentation decks (PowerPoint), presenting proposals to customers
Communication with foreign customers
Willing to bear a comprehensive liability for result

Requirements

One year of IT sales experience;
Strong written and oral English to catch the customer idea from title of e-mail
Identify needs of potential business partners
Conduct an analysis and be aware of the latest tendencies of market
Figure out customer’s value and form their interests to our company’s services according to with regular interaction with them
Basic technical knowledge in IT

Benefits
Competitive salary depending on experience and skills;
Timely salary payment;
Partial grant of the cost of certification and IT conferences;
The possibility of professional growth and growth of skills;
Friendly and relaxed atmosphere;
Flexible working hours;
Good coffee;)))
Ability to play futsal:)
QA
Description
We are looking for a Quality Assurance Engineer to develop and execute exploratory tests as well as automated tests in order to ensure product quality.
QA engineer responsibilities include estimating, planning, and coordinating testing activities. You will also ensure that quality issues and defects are appropriately identified, documented, tracked, and resolved. Our testing approach assumes tight integration with development process itself.
REQUIREMENTS
2+ years of manual testing / automation testing experience;
Web Applications and UI testing in projects developed by Company;
Good software testing background;
Good knowledge of test automation approaches;
Experience with Test documentation: test cases, test plans, estimations and status reporting;
Client side knowledge - HTML, CSS, JavaScript;
Fluent knowledge of tools for testing automation;
Experience with version control systems (git);
Knowledge of continuous integration servers (CI\CD);
Familiarity and understanding of Agile methodologies;
Excellent written and verbal communication skills;
Good level of responsibility, flexibility, communication;
Excellent written and spoken English is necessary
Responsibilities
Participating in the development and delivery of testing including functional testing, integration testing, and regression testing as well as automated testing and UAT;
Automate manual test cases;
Build robust test suites that run stable in any environment
Automation test case creation and execution;
Extending and maintain of existing testing framework;
Bugs reporting and bug fix verification;
Preparation of testing result reports;
Work planning and estimation.
NodeJS / Angular2 Developer
Description
REQUIREMENTS
• Minimum 2 years of experience in a similar position
• Backend development experience (Node.JS/Express/MongoDB)
• Solid understanding in Object Oriented and Functional Programming preferably in Javascript
• Experience with npm||Webpack||Gulp and associated modules
• Experience and knowledge of web services (REST||GraphQL)
• Strong ability to learn and undertake
• Candidate must have a strong understanding of general web principles and standards
• Languages: Intermediate English (written and oral)
would be a plus
• Master degree in Computer Science or equivalent
• Problem-solving mindset
• Autonomous team-player
• Having knowledge in an Angular2 (or similar), Typescript (ECMA Script 6,7), frontend

having knowledge of eslint\tslint rules

Responsibilities
• Write well designed, testable, efficient code by using best software development practices
• Work closely with other members of the team to ensure timely completion of deliverables

https://docs.google.com/document/d/1_mEGeOYQ-WRKu7iyivw2p2W7wOjYZAVoweGeGfkhnLU/edit?usp=sharing
Texts for our projects portfolio.
Implement these texts and later on everyone will double-check the facts. I bet i made some mistakes due to not-knowing those projects and everyone involved, so sorry if i forgot someone :)


Insulin Purified Beef

UMLS:C0304866 is listed in nameres with the preferred name of "Insulin Purified Beef".  But if I look here: http://linkedlifedata.com/resource/umls/id/C0304866 it looks like the name is "Insulin, Beef"

Good news: this is fixed in Babel 2023may18 (currently at dev: http://name-resolution-sri-dev.apps.renci.org/docs), where Insulin, Beef is the preferred label and Insulin purified beef is one of the synonyms.
Bad news: the new NodeNorm algorithm prefers UMLS:C0304866 over PUBCHEM.COMPOUND:90478612 (bovine insulin) and doesn't combine those, which we should probably look into.


chore(merge-back): 1.20.1

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-6Jw05QLuWWwe
Commit ID: 75c50897484a51029cc86f94a2ed4029655fbd0b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Release Google.Cloud.WebRisk.V1 version 2.4.0

Changes in this release:
No API surface changes; just dependency updates.

Created release for Google.Cloud.WebRisk.V1-2.4.0


Adding output support to Behat plugin.

Contribution Type: New Feature
Primary Area: Plugins
Description of change: Adds an output block to the Behat plugin, which lists the name of each feature file and the line number of the scenario.
Screenshot:

If I try run behat -format junit --out xml (where an xml directory exists), I get the following:
[Behat\Testwork\Output\Exception\FormatterNotFoundException]
junit formatter is not found or has not been properly registered.
So it appears at the very least this isn't available out-of-the-box on OS X? https://github.com/Behat/Behat/issues/358 seems to suggest it's not implemented in 3.0 whilst https://github.com/Behat/Behat/pull/676 points to it happening any day now. I'd be happy to revisit and parse the junit output (for starters, that would mean being able to display the name of the failing scenario), but for now, I think this is the best we can do - and I'd argue, better than no output at all.

Additionally, I'm seeing an issue where (with 100ish scenarios), the Build Log is getting truncated half way through the tests - I assume due to the length of the database field. @mavimo, how would you or anyone else using Behat feel about changing the log output to be progress, rather than pretty, so this doesn't occur?

@jfi about log length I suppose is already fixed in #777 what version of PHPCI are you using?

The upgrade sorted that - missed it had been merged in.

Mergeded.