[2] Cloud provider documentation

There is no mention of cloud provider integration. To minimize the risk of bad surprises it would be good to mention explicitly what to expect. I.e. either we say that it is up to the user to tweak the variables for things like this, or we actually provide config that does this and mention it in the docs.
Definition of done: The readme has a note regarding what to expect with the default values from this repo, and an example of how to edit the variables.
Bonus: Sample configuration for each cloud provider. Upon init, the relevant sample is used to generate the defaults so that we automatically get cloud provider integration.

It is currently unclear how our documentation would complement CKA. We need to re-evaluate this task at a later time.

Having re-interpreted this task, it seems that this is already done: https://github.com/elastisys/compliantkubernetes-kubespray/tree/main/config.
@viktor-f Will update the text in the README to reflect this:

flavor will determine some default values for a variety of config options. Supported options are default.


[GitHub Action] Call analysis doesn't work for go projects with go version > 1.22.8

Currently call analysis doesn't work for go projects with go version > 1.22.8, which is the go version of the latest osv-scanner-action image (v1.9.1).
When a new vulnerability is detected call analysis fails with:
Failed to run code analysis (govulncheck) on '/app/tools/src/buf/go.mod' because govulncheck: loading packages: err: exit status 1: stderr: go: go.mod requires go >= 1.23.3 (running go 1.22.8; GOTOOLCHAIN=local)

(the Go toolchain is required)

I suggest one of the following:

Release a new osv-scanner version and osv-scanner-action version when a new golang version is available. Currently there is an open PR with alpine based image update, which also updates go version to latest.
Add support in github action to install and run osv-scanner on machine instead of inside container, thus allowing the consumer to install go itself, similar to golangci-lint-action.

Can you please merge the PR for now and release a new version?

Good idea to support using the host osv-scanner rather than fully relying on a containerised version. We'll release a new version of osv-scanner soon to fix the govulncheck issue as well.

We have made a fix release for this issue: https://github.com/google/osv-scanner/releases/tag/v1.9.2


不能用了，很多编译错误

$ go get github.com/siddontang/redis-failover
# github.com/siddontang/redis-failover/failover
siddontang\redis-failover\failover\raft.go:104: cannot use peers (type []net.Addr) as type []string in argument to raft.AddUniquePeer
siddontang\redis-failover\failover\raft.go:104: cannot use a (type *net.TCPAddr) as type string in argument to raft.AddUniquePeer
siddontang\redis-failover\failover\raft.go:104: cannot use raft.AddUniquePeer(peers, a) (type []string) as type []net.Addr in assignment
siddontang\redis-failover\failover\raft.go:112: cannot use peers (type []net.Addr) as type []string in argument to raft.AddUniquePeer
siddontang\redis-failover\failover\raft.go:112: cannot use a (type *net.TCPAddr) as type string in argument to raft.AddUniquePeer
siddontang\redis-failover\failover\raft.go:112: cannot use raft.AddUniquePeer(peers, a) (type []string) as type []net.Addr in assignment
siddontang\redis-failover\failover\raft.go:153: cannot use peers (type []net.Addr) as type []string in argument to r.peerStore.SetPeers
siddontang\redis-failover\failover\raft.go:163: cannot use peer (type net.Addr) as type string in argument to raft.AddUniquePeer
siddontang\redis-failover\failover\raft.go:233: cannot use peer (type *net.TCPAddr) as type string in argument to r.r.AddPeer
siddontang\redis-failover\failover\raft.go:243: cannot use peer (type *net.TCPAddr) as type string in argument to r.r.RemovePeer

$ go version
go version go1.7 windows/amd64

$ go env
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\vibriohu\work
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1

seem hashicorp updates its raft.
can you help me fix it, maybe we should use a vendor.

Sorry for late, I'm busy these days...
I'll work on this tomorrow.


3 digits after the decimal point is better

I think 3 digits after the decimal point is better.

If you make change,i'll be happy to merge this.

I change 1 digits  after s, would you like the change ?


[BUG] RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:5 and cuda:6!

执行如下代码报错，是什么情况呢
from transformers import AutoTokenizer, AutoModelForCausalLM
model_path = "/mmu_cd_ssd/zhangce07/MLLM/Qwen/Qwen-VL-Chat/"
qwen_model = AutoModelForCausalLM.from_pretrained(model_path, device_map="auto", trust_remote_code=True).eval()
query = qwen_tokenizer.from_list_format([
{'image': 'xxx'}, # Either a local path or an url
{'text': "xxx"},
])
response, history = qwen_model.chat(qwen_tokenizer, query=query, history=None)
print(response)
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:5 and cuda:6!

@fyabc 可以帮忙看看吗

same error here.

same error here.


creating multiple controller objects in sequence create a socket "Address in use error"

Hi!!
thank you so much for putting this out there. This library is pretty awesome.
While playing around with it I noticed that if you create more than one controller at a time for some reason the socket connection is not built separately. It seems like a valid socket connection is given to only one of the controllers, I would have expected each object to be an independent separate socket.
Here's a specific example :

device_ip_list = ["<IP_ADDRESS>", "<IP_ADDRESS>"]
for controller_ip in device_ip_list:
    ctrl_list.append(HighControlInterface(controller_ip))

The code will run, but the socket builds will fail. Specifically if ctrl_obj is each of the elements in ctrl_list then :
ctrl_obj._udpclient.handle is resulting in OSError: [Errno 48] Address already in use at least for one of the items (i've tried a total of 2 so far).
I also tried using the MultiHighControlInterface class but it seems to be directed at setups joined at the twinkly app level and I'm using each set differently.
Thanks again for this awesome library. Appreciate any help!

in case it helps :
xled==0.7.0
xled_plus==0.1.35

python 3.10

Hi,
I remember this issue from a couple of years ago. I see that the latest xled package released (0.7.0) is from 2021, and I think this may have been fixed in 2022. One thing to try is to download the latest xled version from git instead of using "pip install", then you will get the latest version. (Alternatively you can download just the "udpclient.py" file from the xled package and let it replace the old file.) The reason is that the old udpclient.py hogged a receiving port on the local machine, even when, as in this case, no messages are received. Therefore several UDP clients would try to use the same port.
If the above does not help, I may be able to provide a workaround, but try the above first.
Best Regards
Anders Holst

appreciate the speedy response!! thank you so much!!
I went code diving and realized that this is an issue indeed in the original xled package. The library is written such that the source port is forced to be the same as the destination port ( 7777 ). For now I've had to overload the way the udp client handle is created. It is ugly but it works.
Here's what found so far:

xled hard-code of 7777 for source / destination ports
instantiation of the local socket using the hard coded port
handle object binding the socket to the same port

for now the way I've gotten away with it is with the following:
for count, (controller_ip, src_port) in enumerate(zip(settings.default.twinkly_controller_ip_list,
                                   settings.default.twinkly_controller_src_ports)):
    ctrl_list.append(HighControlInterface(host=controller_ip))

    ctrl_list[count].udpclient
    if count == 0:
        while ctrl_list[count]._udpclient._handle == None:
            ctrl_list[count].udpclient.handle
            logger.debug("Waiting for default Xled connection to build so we can close it")
        ctrl_list[count]._udpclient._handle.close()
        while ctrl_list[count]._udpclient._handle._closed == False:
            logger.debug("Waiting for default Xled connection to close so we can assign new ones")
    else:
        while ctrl_list[count]._udpclient == None:
            ctrl_list[count].udpclient
            logger.debug("Waiting for default Xled connection to build so we can close it")

    ctrl_list[count]._udpclient._handle = None
    ctrl_list[count]._udpclient._handle = socket.socket(socket.AF_INET, socket.SOCK_DGRAM, socket.IPPROTO_UDP)
    ctrl_list[count]._udpclient._handle.bind(("", src_port))
    # wait this time in seconds before starting to send data
    logger.info(f"Connection configured. Waiting {settings.default.connection_settling_time} seconds for it to settle")
    time.sleep(settings.default.connection_settling_time)

where the tuple  (controller_ip, src_port) is something i provide with a config file.

happy to take other suggestions, but it would be great to have this be configurable. On the plus side it would also allow running different instances of the xled-plus derived code to better multiprocess if we can set the port up front.
I'm guessing this is looking more like an xled issue than an xled-plus issue? should I be asking there?
Thanks again for this awesome library and all the work that has gone into it !

as a side note i did notice that there are changes in the developer branch per your suggestion. will take a look at it too.


Memory leak?

Over about ten to twelve days, RSS size went from around 30M to over 120M with no comments processed.  I'm running a cloned copy of this repo, straight without using docker.  It could be upstream's issue or yours, you're in a better position to judge I imagine, but I'm reporting it here since it is this version I'm running.

Thanks for the report! I will try and do some profiling to figure out what is being left open.

If it's possible, please could you capture your heap by using the latest commit, the dev version (make devel rather than make prod) and then curl http://<server>/debug/pprof/heap before and after the potential memory leak and email it to me?
This should help narrow down exactly what's causing this issue :)

Hi! Just wondered if you had any updates on this issue? :)


Update image crate

This PR updates the image crate to version 0.25.
This version changes the webp encoder from binding library to a pure rust native webp encoder and also changes jpeg-decoders in favor of more performant zune-jpeg package.
BTW, maybe it's a good time to introduce the dependabot alerts for updating repo dependencies?

Ugh, I've just noticed the wl-clipboard-rs got an update today as well, and my previous PR with introducing rustix will make wayshot's dependency tree benefit from it... Maybe I should just update everything not breaking in this PR, will it be OK?


GraphQL HoC doesn't re-render with data.error set when GraphQL error occurs

Intended outcome:

To access data.error inside a graphQL HoC wrapped component to do error handling.
Actual outcome:

The data.error prop is never passed to the child as expected. I did a little digging and it appears that the logic to prevent unnecessary re-renders in the graphql HoC doesn't take the error state into consideration and uses stale data props.
How to reproduce the issue:

I've updated your Apollo 2.0 Client example to illustrate the issue: https://codesandbox.io/s/pyp1zw702q
See the use of data.error in list.js. I console log when an error occurs using the apollo-link-error setup in index.js
Version

<EMAIL_ADDRESS><EMAIL_ADDRESS>

➤ Mattias Ewers commented:
This is an issue for me as well.

➤ Jim Kynde Meyer commented:
This issue appears to be more critical than I initially thought.
I'm now seeing stale data.props that are out of sync with what is in the InMemoryCache after mutations. See the attached screenshot which demonstrates a customer name being out of sync.

➤ mitjade commented:
Same problem for me.

➤ Niklas von Hertzen commented:
Experiencing same issue, the error prop never seems to return anything else than undefined, and when a component that was supposed to have an error gets unmounted, it throws an Unhandled error error right after.
Using apollo-client 2.0.1 and react-apollo 2.0.0

➤ Nepomuk Seiler commented:
This test should validate that this actually works. Is the error field only for non-graphql errors (e.g. network failure, 5xx responses, etc.)?

➤ Jim Kynde Meyer commented:
As far as I can tell, the test doesn't cover the optimization logic in render: https://github.com/apollographql/react-apollo/blob/master/src/graphql.tsx#L604-L622
It focuses mainly on componentWillReceiveProps which is no guarantee that the wrapped component will be given the right props during render.

➤ mitjade commented:
With apollo-client 2.0.2 the error now get's correctly set for me, but I still get the Unhandled error error right after.


'Open a file to fix an issue' error

Type: Bug
I opened GitHub Copilot chat, and in the middle of conversation it randomly got stuck saying Open a file to fix an issue despite having a file open and being used as a reference in the chat
Extension version: 0.22.0
VS Code version: Code 1.95.0 (912bb683695358a54ae0c670461738984cbb5b95, 2024-10-28T20:16:24.561Z)
OS version: Windows_NT x64 10.0.26100
Modes:

System Info

Item
Value

CPUs
13th Gen Intel(R) Core(TM) i9-13950HX (32 x 2419)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
63.76GB (23.98GB free)

Process Argv
--crash-reporter-id cf9415b4-c817-4426-ade6-306b6f4ebb69

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
01bff139:31013167
dvdeprecation:31068756
dwnewjupyter:31046869
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
iacca2:31156134
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013

I first got the problem a few minutes ago so I clicked on my already-open editor then clicked 'Retry' and that fixed it temporarily, but now the error has become more persistent and displays any time I retry my most recent query.
The first query was an @workspace /fix message with my file attached as a reference, that was the one that was fixed via 'Retry'.
The second query was also an @workspace /fix message except it was one of the hyperlinked suggested questions above the chat window. After clicking on that, the issue now persists regardless of 'Retry'
Just now I opened a new chat to try to replicate the problem and used @workspace /fix with the same file and it gave me the error, I clicked 'Retry', and it functioned correctly again, can't reproduce consistently since


Switch order of parameters in from_fourier_basis

This PR is not ready for review yet as there needs to be tests added for convert_to_gamma_beta function.

@rajgane07, would you mind reviewing when you get a chance? If it looks good to you, feel free to merge.


Unable to connect Fuel Wallet with DApps in browser after reinstallation and clearing cookies

What version of Wallet are you using?
Version: 0.40.0
What is happening?
The Fuel Wallet is not being detected by any decentralized applications (DApps) in my browser. Despite reinstalling the wallet extension and clearing browser cookies, the DApps fail to recognize or connect to the wallet. This issue persists across multiple DApps, and I am unable to interact with any of them using Fuel Wallet.
steps to reproduce
Install the Fuel Wallet extension in the Brave browser (Version 1.71.114).
Open any decentralized application (DApp) that supports Fuel Wallet.
Attempt to connect the Fuel Wallet to the DApp.
Observe that the DApp does not detect the wallet.
Clear cookies and cache in Brave (Version 1.71.114), then reinstall the Fuel Wallet extension.
Attempt to connect to the DApp again, but the wallet is still not detected by the DApp.
How it should behave?
The Fuel Wallet should be detected by decentralized applications (DApps) in the Brave browser (Version 1.71.114) immediately upon attempting to connect. After clicking the "Connect Wallet" button within the DApp, the wallet should appear as an option for selection, allowing the user to authorize the connection and interact with the DApp seamlessly.
What os are you seeing the problem on?
Windows Desktop
What browser?
Brave
What is your browser version?
Version 1.71.114

@Pepichain Have you tried using different browser extensions for each wallet? or it been solved already?

@Pepichain Have you tried using different browser extensions for each wallet? or it been solved already?

the connection problem has been solved, thank you.


Testing and functionality to ensure catalog CLI output can be piped into follow-up operations

Currently most/all commands read jsonlines data from file. Need to ensure that these commands can read from stdin.

Functionality added via datalad-next's ValidatedInetrface in https://github.com/datalad/datalad-catalog/pull/309


Validate limits (string and ID bound)

This change ensures that a string literal length does not exceed the
given limit by checking the string is null-terminated.

It also checks that all IDs are withing the ID bound specified in the
SPIR-V header. A unit test has been added for this and passes successfully.

Note: This change currently breaks one unit test since that test is
manually forcing an ID (64) that is out of bound. It seems that test was crafted to fix a specific issue in the past, so I need to talk to David about what's the best way to resolve that failure.

This change will not be pushed as is. The failure in the "test_val_capability" unit test must be resolved first.

Right.  The failing test should be modified to override the Id bound to make it bigger than the 64 in the faked Id.

Suggesting std::memchr.

Yes, a good idea to just check the one thing in this PR.
Still requesting changes though.  This can be simplified further.

Be sure to update the commit comment to reflect the reduced scope.

Squashed and pushed into master as bd5b0bfca1bf


Update Cascadia Code to 2102.25

This update fixes some issues in Cascadia Code's February update:
microsoft/cascadia-code#406 - updated anchor type to lock with the other equals-related ligatures
microsoft/cascadia-code#408 - corrected component used for glyph to align with Unicode
microsoft/cascadia-code#412 - updated locl features removing iacute_j ligature and Catalan substitution
microsoft/cascadia-code#414 - increased overlaps of middle glyph for arrow ligatures
microsoft/cascadia-code#415 - reduces width of macronbelow
microsoft/cascadia-code#416 - rolls back name ID 4 modification as JetBrains cannot process it correctly
microsoft/cascadia-code#428 - rolls back variation of the underline to prevent MVAR table generation
Full changelist:

Repositioned tilde in related ligatures. Previously it was higher than the standard one.
Added missing vietnamese anchors on acute and grave (futureproofing).
Corrected / made consistent greater & less positioning in </> and <$> related ligatures.
Otherwise reviewed hinting

@msftbot merge this in 1 minute


Activating the display mode widget causes a need for a second activation

Follow-up to #3592 which @RatMoleRat may be working on and figuring out:

That didn't fix the problem with activating widgets after changing the display mode, though. It only happens after something is selected from the display mode dropdown, not after something is selected from any other dropdowns, which is strange, but I'll keep trying to fix it.

On a semi-related note I noticed shift-tab doesn't reverse the tabbing order - was that working at some point or am I just imagining things?

Shift tabbing was indeed working when the pain PR was merged. We should probably add investigating and fixing it to this issue


Work Package wp-fw.csv

Result of Phase 1
wp-fw-results.csv

Manually pushed this into the next workflow step. Please use workflow phrases next time. ;)

Results of Phase 1 :
wp-fw-results.csv

I would like to work on this please!

Results of phase 2
wp-fw-results.csv

I completed this work package.

Results of phase 2-
wp-fw-results.csv


Implements most of the C api for decompression.

Got most of the C API implemented. The remaining problem is returning the output.
Discovered that sharing a stream (i.e. Queue) between readers and writers is not currently possible because the current code doesn't have a way to not allow readers past writers. This is needed because in a block, a writer is kept at the beginning of  the block, and then "backpatches" the size once it is known. Solved the problem by implementing a "Pipe" that uses two streams: an input and an output stream. The input stream is written to. As pages are filled in the input, and have no writers, they are copied to the output stream.
In addition, I discovered that we can't use a "write" cursor to fill an input stream. The reason is that writeFill() always created a new page (to reduce the number of calls to grow the stream). The code was modified to accept an argument for fill size. This allows the "write" cursor to  cause the stream to only grow as data is available.
Also simplified the C api for decompression, simplying the implementation.

Closing. Forgot to add some new files.


loginPopup and acquireTokenPopup not always working as expected (popup not closing)

We are having an intermittent issue with loginPopup and acquireTokenPopup. Sometime, the popup will not close after a successful login but will instead load the application inside the popup (unauthenticated). The opener window will have the session storage key "msal.error" with a value of "Invalid_state".
This is not always reproducible. Some scenarios will work 99 times out of 100 while other scenarios will always fail. We tried to build a project that would reproduce the issue as often as possible and this is what we came up with, using project https://github.com/Gimly/simpleAngularAzureB2C as a starting point (note that we actually connect to Azure Ad instead of AzureB2C):
https://github.com/Gimly/simpleAngularAzureB2C was created for issue #150 so it might actually be the same problem

git clone https://github.com/Gimly/simpleAngularAzureB2C (as of commit b26bd80746fd0660948fffce6d7f263638aead5e)
Register an application at "apps.dev.microsoft.com"

Add a Web platform with "http://localhost:4200/" as the Redirect Url

Modify the file /src/app/authentication.service.ts of the simpleAngularAzureB2C project

replace line 8 (starting with "private authority =") with the following 3 lines:

  private authority = 'https://login.microsoftonline.com/[yourtenantname.onmicrosoft.com]';
  private clientId = '[your_client_id]';
  private scopes = [this.clientId];

replace line 15 ("environment.clientID,") with "this.clientId,"
replace line 21 ("this.clientApplication.loginRedirect(environment.b2cScopes);") with "this.clientApplication.loginPopup(this.scopes);"
replace line 37 ("return this.clientApplication.acquireTokenSilent(environment.b2cScopes)") with "return this.clientApplication.acquireTokenSilent(this.scopes)"
replace line 43 ("return this.clientApplication.acquireTokenPopup(environment.b2cScopes)") with "return this.clientApplication.acquireTokenPopup(this.scopes)"
Run the project

npm install
npm update
npm start

Reproduce the issue

Start fresh by closing all instances of Chrome and reopening Chrome
disable popup blocker
navigate to http://localhost:4200
click the Login button
follow the login process

The application should now be loaded inside the popup and the popup will remain open

We were able to reproduce the issue multiple times using the steps above.
When the issue occurs, we can see that the function UserAgentApplication.prototype.handleAuthenticationResponse (the instance inside the popup window) will get its msal configuration/state using window.opener.msal. If we look at this msal object, we see that the property _interactionMode is set to "redirect" when it should be "popUp".

This might actually be an issue with version 0.1.2.
I made a new repro using what I think is an official Microsoft sample: https://github.com/Azure-Samples/active-directory-b2c-javascript-angular2.4-spa
This sample uses version 0.1.1 of msal. By simply cloning the repo and updating msal to version 0.1.2, we get the behavior describe above when login in. However, the sample works correctly with version 0.1.1.
Note that I also changed the tenantConfig and authority to use Azure Ad instead of Azure B2C

@mathlesp I was able to clone the sample and reproduce the issue using 0.1.2. Interestingly, the samples in our repo were working fine for popup scenarios. There was a timing issue in using msal with the angular sample. I have made a fix for it in the dev branch. You can now just replace the msal.js file from the node_modules/msal/out folder in the angular sample with msal.js from the dist folder in the dev branch to resolve the issue. We will be releasing a new version of msal next week and these fixes along with support for commonjs and es-6 modules will be part of the release.

I am still having this issue on version 0.1.3.

I am also facing this issue randomly. Mostly it comes for the first time. It redirects to the [redirect url]/null.

This problem still occurs. Please reopen issue

this problem still occurs, with version 1.0.0 and 1.1.0.
please reopen issue

and 1.1.2 also not working

I've reproduced/workaround the problem by simply changing the execution scope of new Msal.UserAgentApplication...
In the code above, if the line init() is executed on page load (i think in the window scope) all works fine (show login popup, and back to app windows). But if I comment this line and execute init() inside of click event of a button, then it fails (show login popup, and reload app in popup window).
<!DOCTYPE html>

    <title>LOGIN MICROSOFT TEST</title>
    <meta charset='utf-8' />

    <button onclick="init();">INIT</button>

    <button onclick="login();">LOGIN</button>


Please reopen issue 1483

Issue 1483 was closed and marked as ships in a future update, but in the latest build i downloaded only the OnAfterFAJnlPostLine event was added...there is still no OnBeforeFAJnlPostLine.  Please reopen.

Alexander replied to #1483. Sounds like you're good to go. Closing issue.


Missing include for minify flag

When I try to create a minified build, I receive a message that
source/javascripts/all_nosearch.bundle.inc not found

The source/javascripts directory has

all_nosearch.inc
all.bundle.inc

but not all_nosearch.bundle.inc.  Is this something we should create ourselves?

Please continue the discussion over on slant if still an issue (slant uses a different build system).


Hi, i am get error report pls fix

This error:
Game name: (please, specify the game name)
Engine version: (specify engine version, if known)
Platform: (specify platform, if known)
Error message: Не удается загрузить DLL "fmod": Не найден указанный модуль. (Исключение из HRESULT: 0x8007007E)
Stack trace:    в FMOD.Factory.FMOD_System_Create(IntPtr& system)
в FMOD.Factory.System_Create(System& system)
в uTinyRipperGUI.Exporters.AudioConverter.ConvertToWav(Byte[] data)
в uTinyRipperGUI.Exporters.AudioAssetExporter.Export(IExportContainer container, Object asset, String path)
в uTinyRipper.Project.AssetExportCollection.Export(ProjectAssetContainer container, String dirPath)
в uTinyRipper.Converters.ProjectExporter.Export(String path, GameCollection fileCollection, IEnumerable1 files, ExportOptions options)    в uTinyRipper.GameStructure.Export(String exportPath, Func2 filter)
в uTinyRipperGUI.MainWindow.ExportFiles(Object data)
i am not understanding russian fix pls

Hello
uTinyRipper has been abandoned, but AssetRipper is actively being developed with the intent to recover Unity games as best as possible. I encourage you to help out if you're able and willing. Code contributions can be submitted via pull requests.
Development Progress
These are some of the notable things I've implemented since taking over development.

2020 - 6 support
APK, XAPK, and IPA reading with SharpZipLib
Dummy shaders (so everything isn't pink when you open the project)
IL2Cpp support via an integration of Cpp2IL
Better game platform support
Full script decompilation with the ILSpy decompiler
Cross-platform support
Multiple configuration options
Numerous performance improvements
Support for all asset types
Lightmap Recovery
High-quality 3D model export with SharpGltf
Prefab Outlining
Hybrid Script Export

This is not (at all) a comprehensive list. There are so many other things that could not be included here. They have all been made possible with the support of my generous sponsors.
Future Plans
This is a list of notable improvements planned for the future.

Mesh preview
Scene preview
Child State Machines
Dynamic Zip File Loading

Sponsorship
If you like the work I've done and want to see it continue, please consider sponsoring me. It really helps with development, more than you know.

GitHub Sponsors
Patreon
Paypal

A Patreon subscription gives access to AssetRipper Premium, which has additional features:

Static Mesh Separation
Asset Deduplication
User Defined Package Export


Add bower support for Falcor

Add support for installing Falcor via bower by adding a bower.json file to the root and defining the main file.
I have registered the fork as falcor-fix in bower so you can check behavior via
bower install falcor-fix#0.1.16-alpha3

Once you add this bower.json future release tags will become available for install via bower.
Image of what gets installed

I don't see any reason not to include a bower package config for falcor.
I'm not too familiar with some of the real-world aspects of how to ideally package modules for bower, but a couple of thoughts, worth flushing out before we merge this in:

Would it be easier to explicitly include files, as opposed to ignore/blacklist files.
Do we need to give some thought to breaking up modules? Right now users get the falcor dist in it's entirety when you bower install falcor. Is this ideal? Or just a starting point, and we can consider more granular modules later if there's demand?
Do we need to roll up publishing to npm and bower as a combined publish task/step so semver versions stay in sync?

Bower works by registering a name (in this case falcor) to a github repository (in this case https://github.com/Netflix/falcor/). It then detects the semver Git tags (see releases) and each tag becomes an installable version. When you perform the install (without version number) it finds the latest release tag and grabs the repository state for that tag and downloads it to the users system.
See: http://bower.io/docs/creating-packages/#register

The bower config only allows adding ignored files/folders. It follows the .gitignore syntax so there may be a way to 'exclude everything except'. bower file spec

I'm currently not sure when I'd want to use falcor.all vs falcor.browser, but the bower config only allows specifying one main file for each type. If you wanted to establish a more granular system, for example: falcor -> falcor.browser falcor-all -> falcor.all you could follow the example from the AngularJS team. They have a separate public repository, bower-angular and have the bower registry pointed at that repo. In this way you can control the set of files that are installed for each command w/o any effect on your main repository (this also helps with 1 above). You would have to modify your CI job to push the dist to that repository and keep its tags up to date however.

Since Bower works off the tags in the git repo, so if those are currently insync w/ npm bower will be in-sync as well. If you want to pursue settings up individual bower-falcor repositories (re: 2 above) you would need to update the bower-falcor repository at the same time as publishing to npm to keep them in sync.

@sdesai if you are ok with merging this, feel free to hit the merge button.  I'll defer to you.

Then, of course, close #709 when you are finished here.

@sdesai is not around, so I'll just assume that he agrees with this PR.


Release 1.2.1

Coverage decreased (-0.07%) to 99.927% when pulling 06a1c20786fcab684f5847913c0fce0289d4c349 on develop into 8a066a9a7690557d9b1b6ed54b7d1a1502ba59e3 on master.


feat(l1_provider): add L1ProviderContent

Follows the same pattern and API style as MempoolContent.

This change is


support for Raise/Lower button on ra3 sunnata keypads?

Hi there,
First I really appreciate the effort here by bringing in RA3 support. I am finally able to integrate Phillips Hue onto the Sunnata keypads!
The question is around R3 sunnata keypads Raise/Lower buttons. They are not showing in the entities. Is there a plan to bring the support for these 2 little things? Thank you!

Hi @centrino66
These buttons are supported as Device Triggers for automations.
If you create an automation
Click "+Add Trigger"
Select "Device"
Choose your Sunnata 3BRL Keypad from the list
On the trigger dropdown, you will see all the buttons, including the raise and lower buttons
The entities you are seeing in your attachment represent the LEDs associated with the first 3 buttons.  They are "switches" and you can turn the LED light on/off using those entities.
There is a future update coming that will allow you to press the buttons too (including the raise/lower buttons)

All the features required for these Keypads have already been implemented in pylutron-caseta.
Can you please close the issue?
Thanks.

Ah I see, thanks for the explanations. Closing the ticket.


Update grpc-netty-shaded to 1.54.1

About this PR
📦 Updates io.grpc:grpc-netty-shaded from 1.54.0 to 1.54.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.grpc", artifactId = "grpc-netty-shaded" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.grpc", artifactId = "grpc-netty-shaded" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #717.


Tests not compatible between inline and sidebar

NOTE: Currently blocked by upstream VS Code extension issues!
Tests in the sidebar are handled by the Rust Test Explorer extension, while the inline test codelens is provided by Rust Analyzer. These two extensions do not have any interoperability, unfortunately.
Tests in the sidebar...

can be run.
save their state (whether they were passing or failing as of the last run).
cannot be debugged

Tests inline in the codelens...

can be run.
cannot save their state
can be debugged.

Sidebar tests were removed. Closing.


really drop python<=3.7 support

Change Summary
Filter all code over pyupgrade --py38.
Related issue number
N/A
Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[ ] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

I believe the v1 code should be left as is

Indeed, @Viicos is right! Let's leave the V1 code as is. Happy to review again once that's changed - thanks!

OK .. however I'm not sure about you are talking about so please close this PR and to it by yourself or merge than correct what still should be rolled back 😋
If it anything wrong what have been filtered incorrectly by pyupgrade please report that on https://github.com/asottile/pyupgrade

Basically the v1 folder is a port of Pydantic V1 so that even in Pydantic V2, the v1 code can be imported under pydantic.v1. But this code should be identical to what is available on the 1.x branch.

Could you please remove the unused typing.Dict and typing.Optional imports? That should fix the pipeline for good!

In updated PR are only changes in tests/ and I see in that new diff any fiddling around imports 🤔

In updated PR are only changes in tests/ and I see in that new diff any fiddling around imports 🤔

All good, I made the fixes. Thanks!

OK now I see about what it was 😋
How did you font that? Using ruff? 🤔

@kloczek,
Yep, you can use ruff. The issue was also reported in our lint jobs

Thank you because I had again I've had opportunity to learned few small new details 👍 😄


length_delimited should allow using a custom Codec

I can't find a way to use a custom Codec in conjuction with length_delimited. I'm currently working on a PR to implement varint support for length_delimeted (an untested work in progress can be found here). The usecase is to use protobuf with a varint length delimiter. With length_delimited::Framed only implementing Stream and Sink, but not AsyncRead and AsyncWrite, it's not possible to chain a Codec with AsyncRead::framed on it in order to deserialize the returned BytesMut / serialize items into BytesMut before length-delimiting them.
My suggestion would be to either implement AsyncRead and AsyncWrite on Framed, and respectively on FramedRead and FramedWrite.
Another idea is to be able to add a custom Codec to Builder, which will be invoked after a full frame has been read into BytesMut for deserialization, and for serialization in order to create the BytesMut which needs to be length-delimited.

Here is an example: https://github.com/carllerche/tokio-serde-json/blob/master/src/lib.rs
The strategy is to "map" the Stream<Item=Bytes> -> Stream<Item=MyTime. Basically you can use regular stream combinators instead of something custom.

I think that this is a lot of overhead and work to write for every possible serialization format possible. Would it be possible to offer this in a more generic way? For the read part it's easy enough to use and_then:
let length_delimited = Builder::new()
    .varint()
    .new_framed(stream);
let (write, read) = length_delimited.split();
let read = read.and_then(decode);

fn decode(buf: BytesMut) -> io::Result<Item> { ... }

But for the write part it's rather hard to wrap encoding around the sink. Instead, I need to wrap it around a stream which produces items / manually call encode / write bloaty code like it's done in tokio-serde-json.
I think that from a user experience point of view the idea of tokio_io::codec::Framed is pretty nice. You just need to write a codec and automatically have the whole stream wrapped. Using this kind of approach in conjunction with length_delimited would be even better because you don't need to take care about manually length-prefixing the message and to verify the correct length of a frame. Therefore, I think it would be a nice user interface to be able to provide an implementation of a Codec to length_delimited which both the stream and sink will automatically get wrapped with just like it's done with tokio_io::codec::Framed.

You probably wouldn't split, and you can use Sink::with to do the mapping.
It would be easier if map and with took types vs. functions... That said, if you want to explore this idea further, you can do so in a standalone git repo like I did w/ tokio-serde / tokio-serde-json. Once it gets fleshed out, we can consider if there is anything worth merging into tokio-io.

Given Sink::with and Stream::map / Stream::and_then I guess this issue is resolved. The idea of taking types instead of functions sonuds very interesting and could even be implemented in a non-breaking way (implementing the type for functions). Unfortunately I don't have the time currently to dig into that rabbit hole.
Anyway, thanks for your help.


README should say more about what this software does & include a contact email

This repo is deprecated now! https://github.com/data-8/nbgitpuller is what is now going to be used.


mothur hang when using cluster.split

Hi,
I'm using mothur version 1.44.1 and when running cluster.split I got this error:
Running command: dist.seqs(fasta=stability.paired.trim.contigs.good.unique.good.filter.unique.precluster.abund.pick.pick.pick.fasta.187.temp, processors=44, cutoff=0.03)

Using 44 processors.
/******************************************/

Sequence	Time	Num_Dists_Below_Cutoff
0	0	0
1	0	1

It took 0 secs to find distances for 2 sequences. 1 distances below cutoff 0.03.

Output File Names:
stability.paired.trim.contigs.good.unique.good.filter.unique.precluster.abund.pick.pick.pick.fasta.187.dist

[ERROR]: Could not open stability.paired.trim.contigs.good.unique.good.filter.unique.precluster.abund.denovo.vsearch.pick.pick.pick.pick.count_table.16.temp

and then the programs hangs forever.
Can you help me, please?

You can follow responses to this question here, https://github.com/mothur/mothur/issues/739


Fix #3507: Trino connector, support optional database field

Describe your changes :

See #3507
Implementation details
Presto and Trino should share most of the code of the connector.
I have replaced the obsolete Trino code with the Presto code.
Follow-up

[ ] Update the manual to explain how to use params.
[ ] rename options to params in Presto connector and test it.

Test of params
Check that the queries are executed by bar and not user.
{
  "source": {
    "type": "trino",
    "config": {
      "service_name": "local_trino",
      "host_port": "localhost:8080",
      "username": "user",
      "catalog": "tpcds",
      "generate_sample_data": "false",
      "database": "tiny",
      "params": {
        "sessionUser": "bar"
      }
    }
  },
  "sink": {
    "type": "metadata-rest",
    "config": {
    }
  },
  "metadata_server": {
    "type": "metadata-server",
    "config": {
      "api_endpoint": "http://localhost:8585/api",
      "auth_provider_type": "no-auth"
    }
  }
}

Type of change :

[x] Bug fix

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have performed a self-review of my own.
[x] I have tagged my reviewers below.
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

All changes requested have been addressed.


Hyperledger Iroha v1.0 beta-5 version

We are happy to introduce various improvements of Hyperledger Iroha for Beta-5 release and tell you more about what we accomplished together.
There were several major features implemented or prepared…
Multi-signature Transaction (MST) is ready for use!
Now you can request several signatures to verify the transaction. And transactions can receive 2 more statuses: MST_PENDING for transactions waiting for more signatures and ENOUGH_SIGNATURES_COLLECTED for transactions that have already received the number of signatures requested ( https://github.com/hyperledger/iroha/pull/1649).
We have made MST possible with the following changes:
- adding Storage for Pending Transactions: https://github.com/hyperledger/iroha/pull/1598
- fixed sending batches to the Storage and retrieving them:  https://github.com/hyperledger/iroha/pull/1661
- fixed retrieval of pending MST transactions: https://github.com/hyperledger/iroha/pull/1661
- MST batches: https://github.com/hyperledger/iroha/pull/1642 and client tests for them: https://github.com/hyperledger/iroha/pull/1652
and other improvements.
Here is the example of MST use case: Alice and Bob are performing exchange between bitcoin and dogecoin using MST to perform exchange only when both partcipants agreed on the transfer https://github.com/hyperledger/iroha/pull/1761
Important note: MST is functional. However, there is a known issue: when user sends a completed MST transaction it's version without all signatures is not removed from MST storage, so when one asks for his pending transactions he will still see it. As a temporary workaround, you can remove all signatures after getting pending transactions and then sign them with your signature and send to Iroha.
New fully BFT On-Demand Ordering Service is almost ready (only needs some finishing touches)!
Impressive preparations were made for later assembly of fully BFT (Byzantine-fault tolerant) Ordering service. We already prepared:

BFT OS algorithm and interfaces: https://github.com/hyperledger/iroha/pull/1670
on-demand ordering gate: https://github.com/hyperledger/iroha/pull/1675
the transport: #1635  and on-demand connection manager: https://github.com/hyperledger/iroha/pull/1645
the synchroniser: https://github.com/hyperledger/iroha/pull/1647
BFT OS components: https://github.com/hyperledger/iroha/pull/1703
Consensus Round as Key in YacStorages: https://github.com/hyperledger/iroha/pull/1729
BFT YacGate: https://github.com/hyperledger/iroha/pull/1731

**Important note: ** at the moment Iroha uses old version of Ordreing Service, which will be obsolete in the next release
Replaced builders with factories
Now the code runs faster with changed design of its components.
Here are our new factories within the code:

factory for a block: https://github.com/hyperledger/iroha/pull/1622
factory for transaction status creation: https://github.com/hyperledger/iroha/pull/1717
factory for query responses and tests: https://github.com/hyperledger/iroha/pull/1724
abstract factory for creating batches from transactions: https://github.com/hyperledger/iroha/pull/1743
transport factory: https://github.com/hyperledger/iroha/pull/1750

Query Error Responses
Real error reasons for real people using Iroha - introducing Query Error Responses so you could know why the query failed: https://github.com/hyperledger/iroha/pull/1770
And some of the smaller though very important ones…
Optimised command and query SQL
A complex work was done to optimise the work of SQL for both commands and queries: https://github.com/hyperledger/iroha/pull/1605
Consensus Cache in Block Loader and YAC Gate
We constantly move towards faster Iroha.
Now there is no need for a node to wait time to ask another node for synchronisation thanks to the consensus cache. So let us say good-bye to load_delay: https://github.com/hyperledger/iroha/pull/1627
SWIG-free Iroha library for Python
Platform independent. Lighter.
Better solution if you want to use Python with Iroha: https://github.com/hyperledger/iroha/pull/1761
SubtractAssetQuantity command
Was not previously implemented in Iroha-cli but now works correctly with AddAssetQuantity: https://github.com/hyperledger/iroha/pull/1713
Benchmarks to measure performance
We are introducing a benchmark that executes GetAccount query and a benchmark that executes AddAssetQuantity command to have more information on the performance: #1651  and #1648
Empty Roles
The purpose of append role command is to promote an account to some created role in the system, where a role is a set of permissions account has to perform an action (command or query). It was impossible to add a role without permissions to account. Now it is possible: https://github.com/hyperledger/iroha/pull/1654
reducedHash
reducedHash wrapper is now visible to libraries and can be called by clients: https://github.com/hyperledger/iroha/pull/1659
TransactionBatchParser
Splits a list of transactions by possible adjacent batches: https://github.com/hyperledger/iroha/pull/1750
Genesis Parser
It will generate a nice md file with tables of accounts, permissions and other parameters of the genesis block: https://github.com/hyperledger/iroha/pull/1775
Improved tests
Here are some of the most influential results:

the ability to send transaction sequences to the ITF and check stateless valid/invalid status: https://github.com/hyperledger/iroha/pull/1660
ITF feature of checking all the specified statuses: https://github.com/hyperledger/iroha/pull/1720

Fixes
Please also make sure to check out some important fixes and see if your Iroha is not affected by them:

freeConnections method, which disposes all currently used connections was fixed: https://github.com/hyperledger/iroha/pull/1727
send tx sequence method: https://github.com/hyperledger/iroha/pull/1685

DevOps news
CMake version
Minimum CMake version requirement is now 3.11.2 to use cool new features of it in Iroha: https://github.com/hyperledger/iroha/pull/1667
Iroha on Kubernetes cluster
Now Iroha can be run on Kubernetes: https://github.com/hyperledger/iroha/pull/1697

If there are any questions on the release or if you would like to help us with the next one, please check out our contacts under the “Need help” paragraph: https://github.com/hyperledger/iroha#need-help

Is closed since this branch has failed DCO checks


pnpm executable not there with github-action@v5 + the docker cypress/browsers image

github workflow:
jobs:
  cypress:
    runs-on: default-visable
    container:
      image: cypress/browsers:node16.17.0-chrome106
    env:
      GITHUB_TOKEN: ${{ secrets.PACKAGES_READ_ONLY_TOKEN_GITHUB }}
    steps:
      - name: Define proper Checkout REF
        shell: bash
        run: echo "ref=$(echo ${GITHUB_HEAD_REF:-${GITHUB_REF}})" >> $GITHUB_OUTPUT
        id: extract_ref
      - uses: actions/checkout@v3
        with:
          ref: "${{ steps.extract_ref.outputs.ref }}"
      - name: setup github packages authentication
        run: 'echo "//npm.pkg.github.com/:_authToken=${{ secrets.PACKAGES_READ_ONLY_TOKEN_GITHUB }}" > ~/.npmrc'
      - uses: cypress-io/github-action@v5
        id: cypress
        with:
          install-command: pnpm install --frozen-lockfile
          build: pnpm build
          start: pnpm start
          browser: chrome
          wait-on: 'http://localhost:3000'
      - name: cleanup repo files
        if: always()
        run: find . -mindepth 1 -delete

Run cypress-io/github-action@v5
  with:
    install-command: pnpm install --frozen-lockfile
    build: pnpm build
    start: pnpm start
    browser: chrome
    wait-on: http://localhost:3000
    record: false
    publish-summary: true
    component: false
  env:
    GITHUB_TOKEN: ***
/bin/docker exec  db[2](https://github.com/visable-dev/requests-frontend/actions/runs/5325024291/jobs/9645162231#step:6:2)cd8fa41abf165a55298e54cd4ab5d[3](https://github.com/visable-dev/requests-frontend/actions/runs/5325024291/jobs/9645162231#step:6:3)dec9e9e96fc5f87a[4](https://github.com/visable-dev/requests-frontend/actions/runs/5325024291/jobs/9645162231#step:6:4)9da[6](https://github.com/visable-dev/requests-frontend/actions/runs/5325024291/jobs/9645162231#step:6:6)0a[8](https://github.com/visable-dev/requests-frontend/actions/runs/5325024291/jobs/9645162231#step:6:8)ed36d21 sh -c "cat /etc/*release | grep ^ID"
install command command "pnpm install --frozen-lockfile"
current working directory "/__w/requests-frontend/requests-frontend"
Error: Unable to locate executable file: pnpm. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.

@gkatsanos
Please refer to the documentation
https://github.com/cypress-io/github-action#pnpm
for using pnpm.
You will need to add
      - name: Install pnpm
        uses: pnpm/action-setup@v2
        with:
          version: xx

where xx is your preferred version of pnpm.
You should not need
install-command: pnpm install --frozen-lockfile
as github-action will automatically execute this command if it finds pnpm-lock.yaml
See https://github.com/cypress-io/github-action/blob/master/.github/workflows/example-basic-pnpm.yml for a working example (although this is not with a Docker container).
Are you using Docker to have the explicit Node.js 16.17.0 chrome106 environment or are you flexible about which version of Node.js / Chrome you are using? If you only need to tie down the version of Node.js you can use actions/setup-node@v3 instead of using a Docker image.

I see from issue https://github.com/cypress-io/cypress-docker-images/issues/903 that you are having an additional problem and it looks like you are using a self-hosted runner runs-on: default-visable.

I confirmed that the following workflow executes successfully as expected on a GitHub-hosted runner runs-on: ubuntu-22.04:
  basic-pnpm-ubuntu-22-docker:
    runs-on: ubuntu-22.04
    container: cypress/browsers:node16.17.0-chrome106
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Install pnpm
        uses: pnpm/action-setup@v2
        with:
          version: 8

      - name: Cypress tests
        uses: ./
        with:
          working-directory: examples/basic-pnpm
          build: npx cypress info

@MikeMcC399  thank you - indeed, the pnpm/action-setup worked fine.
With regards to the other issue, I think it's something on the docker images, as this issue disappears when using :latest : https://github.com/cypress-io/cypress-docker-images/issues/903#issuecomment-1599193290 I hope we can get a more specific Docker image (without FF/EDGE for example) after which this was handled

It is not clear if the issue is coming from the Docker image since cypress/browsers:node16.17.0-chrome106 worked on a GitHub-hosted runner and not on your self-hosted runner. That would need further investigation, however it does not seem to be caused by github-action, so this issue should stay closed.


Target class [Illuminate\Database\Eloquent\Factory] does not exist.

Hello. I have fresh LV8 project. When trying to use the package on any mail i get the following error:
Illuminate\Contracts\Container\BindingResolutionException
Target class [Illuminate\Database\Eloquent\Factory] does not exist.

Following https://github.com/barryvdh/laravel-ide-helper/issues/1047#issuecomment-689484210 , i think this is the same problem.
The bug is in MailViewer.php, in this use i think:
use Illuminate\Database\Eloquent\Factory as EloquentFactory;

Same here. Installing the laravel/legacy-factories package fixed it for me, as a temporary workaround.

Same here. Installing the laravel/legacy-factories package fixed it for me, as a temporary workaround.

Hi, This package has been archived and will no longer be maintained/updated. The reason being Laravel now itself provides a really convenient way to preview mailables in the browser. Have updated the readme to indicate this.


MAPREDUCE-6752: Bad logging practices in mapreduce

Changed the log level of the method that is only used for debugging purpose as discussed here:
https://issues.apache.org/jira/browse/MAPREDUCE-6752

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
38
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1074
trunk passed

+1
compile
33
trunk passed

+1
checkstyle
20
trunk passed

+1
mvnsite
33
trunk passed

+1
shadedclient
679
branch has no errors when building and testing our client artifacts.

+1
javadoc
22
trunk passed

0
spotbugs
57
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
56
trunk passed

_ Patch Compile Tests _

+1
mvninstall
29
the patch passed

+1
compile
29
the patch passed

+1
javac
29
the patch passed

+1
checkstyle
16
the patch passed

+1
mvnsite
30
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
743
patch has no errors when building and testing our client artifacts.

+1
javadoc
19
the patch passed

+1
findbugs
59
the patch passed

_ Other Tests _

+1
unit
589
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
31
The patch does not generate ASF License warnings.

3568

Subsystem
Report/Notes

Docker
Client=18.09.8 Server=18.09.8 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/1/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux 891cddc2103a 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 7f1b76c

Default Java
1.8.0_212

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/1/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
40
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1109
trunk passed

+1
compile
31
trunk passed

+1
checkstyle
20
trunk passed

+1
mvnsite
33
trunk passed

+1
shadedclient
682
branch has no errors when building and testing our client artifacts.

+1
javadoc
21
trunk passed

0
spotbugs
57
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
54
trunk passed

_ Patch Compile Tests _

+1
mvninstall
30
the patch passed

+1
compile
28
the patch passed

+1
javac
28
the patch passed

+1
checkstyle
16
the patch passed

+1
mvnsite
31
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
739
patch has no errors when building and testing our client artifacts.

+1
javadoc
20
the patch passed

+1
findbugs
60
the patch passed

_ Other Tests _

+1
unit
587
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
26
The patch does not generate ASF License warnings.

3591

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/2/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux 823d36168677 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 62efb63

Default Java
1.8.0_212

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/2/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
47
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1125
trunk passed

+1
compile
33
trunk passed

+1
checkstyle
25
trunk passed

+1
mvnsite
37
trunk passed

+1
shadedclient
693
branch has no errors when building and testing our client artifacts.

+1
javadoc
20
trunk passed

0
spotbugs
60
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
57
trunk passed

_ Patch Compile Tests _

+1
mvninstall
30
the patch passed

+1
compile
29
the patch passed

+1
javac
29
the patch passed

+1
checkstyle
17
the patch passed

+1
mvnsite
31
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
734
patch has no errors when building and testing our client artifacts.

+1
javadoc
19
the patch passed

+1
findbugs
68
the patch passed

_ Other Tests _

+1
unit
590
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
31
The patch does not generate ASF License warnings.

3663

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/3/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux 76f7073f998a 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e872ceb

Default Java
1.8.0_212

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/3/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
83
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1275
trunk passed

+1
compile
30
trunk passed

+1
checkstyle
26
trunk passed

+1
mvnsite
35
trunk passed

+1
shadedclient
823
branch has no errors when building and testing our client artifacts.

+1
javadoc
22
trunk passed

0
spotbugs
62
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
60
trunk passed

_ Patch Compile Tests _

+1
mvninstall
32
the patch passed

+1
compile
28
the patch passed

+1
javac
28
the patch passed

+1
checkstyle
19
the patch passed

+1
mvnsite
26
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
828
patch has no errors when building and testing our client artifacts.

+1
javadoc
22
the patch passed

+1
findbugs
72
the patch passed

_ Other Tests _

+1
unit
642
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
26
The patch does not generate ASF License warnings.

4139

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/4/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux a56a043a540d 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 00b5a27

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/4/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/4/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
84
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1287
trunk passed

+1
compile
46
trunk passed

+1
checkstyle
28
trunk passed

+1
mvnsite
38
trunk passed

+1
shadedclient
846
branch has no errors when building and testing our client artifacts.

+1
javadoc
27
trunk passed

0
spotbugs
61
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
58
trunk passed

_ Patch Compile Tests _

+1
mvninstall
34
the patch passed

+1
compile
28
the patch passed

+1
javac
28
the patch passed

+1
checkstyle
21
the patch passed

+1
mvnsite
29
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
857
patch has no errors when building and testing our client artifacts.

+1
javadoc
23
the patch passed

+1
findbugs
73
the patch passed

_ Other Tests _

+1
unit
629
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
29
The patch does not generate ASF License warnings.

4220

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/5/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux 9b1a71e1d8b1 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / e356e4f

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/5/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/5/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
36
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1200
trunk passed

+1
compile
39
trunk passed

+1
checkstyle
29
trunk passed

+1
mvnsite
40
trunk passed

+1
shadedclient
860
branch has no errors when building and testing our client artifacts.

+1
javadoc
28
trunk passed

0
spotbugs
65
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
63
trunk passed

_ Patch Compile Tests _

+1
mvninstall
35
the patch passed

+1
compile
28
the patch passed

+1
javac
28
the patch passed

+1
checkstyle
21
the patch passed

+1
mvnsite
29
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
901
patch has no errors when building and testing our client artifacts.

+1
javadoc
26
the patch passed

+1
findbugs
72
the patch passed

_ Other Tests _

+1
unit
654
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
34
The patch does not generate ASF License warnings.

4164

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/6/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux 15cf6df351fa 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 4cb22cd

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/6/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/6/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
38
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1240
trunk passed

+1
compile
33
trunk passed

+1
checkstyle
23
trunk passed

+1
mvnsite
35
trunk passed

+1
shadedclient
793
branch has no errors when building and testing our client artifacts.

+1
javadoc
22
trunk passed

0
spotbugs
60
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
56
trunk passed

_ Patch Compile Tests _

+1
mvninstall
38
the patch passed

+1
compile
29
the patch passed

+1
javac
28
the patch passed

+1
checkstyle
21
the patch passed

+1
mvnsite
31
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
861
patch has no errors when building and testing our client artifacts.

+1
javadoc
22
the patch passed

+1
findbugs
65
the patch passed

_ Other Tests _

+1
unit
610
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
27
The patch does not generate ASF License warnings.

4027

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/7/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux 0e2e93c772f7 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 63c295e

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/7/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/7/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
50
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1206
trunk passed

+1
compile
30
trunk passed

+1
checkstyle
24
trunk passed

+1
mvnsite
36
trunk passed

+1
shadedclient
715
branch has no errors when building and testing our client artifacts.

+1
javadoc
27
trunk passed

0
spotbugs
57
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
56
trunk passed

_ Patch Compile Tests _

+1
mvninstall
32
the patch passed

+1
compile
27
the patch passed

+1
javac
27
the patch passed

+1
checkstyle
20
the patch passed

+1
mvnsite
29
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
783
patch has no errors when building and testing our client artifacts.

+1
javadoc
23
the patch passed

+1
findbugs
60
the patch passed

_ Other Tests _

+1
unit
612
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
32
The patch does not generate ASF License warnings.

3855

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/8/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 3329257

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/8/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/8/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
43
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

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

_ trunk Compile Tests _

+1
mvninstall
1104
trunk passed

+1
compile
32
trunk passed

+1
checkstyle
26
trunk passed

+1
mvnsite
33
trunk passed

+1
shadedclient
775
branch has no errors when building and testing our client artifacts.

+1
javadoc
23
trunk passed

0
spotbugs
54
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
53
trunk passed

_ Patch Compile Tests _

+1
mvninstall
31
the patch passed

+1
compile
25
the patch passed

+1
javac
25
the patch passed

+1
checkstyle
20
the patch passed

+1
mvnsite
28
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
795
patch has no errors when building and testing our client artifacts.

+1
javadoc
23
the patch passed

+1
findbugs
60
the patch passed

_ Other Tests _

+1
unit
602
hadoop-mapreduce-client-app in the patch passed.

+1
asflicense
28
The patch does not generate ASF License warnings.

3789

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-285/9/artifact/out/Dockerfile

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

JIRA Issue
MAPREDUCE-6752

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

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

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 915cbc9

Default Java
1.8.0_222

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/9/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-285/9/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 39s

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

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 20s

trunk passed

+1 :green_heart:
compile
0m 39s

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

+1 :green_heart:
compile
0m 36s

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

+1 :green_heart:
checkstyle
0m 31s

trunk passed

+1 :green_heart:
mvnsite
0m 42s

trunk passed

+1 :green_heart:
javadoc
0m 35s

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

+1 :green_heart:
javadoc
0m 30s

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

+1 :green_heart:
spotbugs
1m  2s

trunk passed

+1 :green_heart:
shadedclient
19m 18s

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

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.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_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
0m 27s

the patch passed

+1 :green_heart:
blanks
0m  1s

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-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
0m 22s

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

+1 :green_heart:
spotbugs
1m  1s

the patch passed

+1 :green_heart:
shadedclient
18m 50s

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

_ Other Tests _

+1 :green_heart:
unit
8m 21s

hadoop-mapreduce-client-app in the patch passed.

+1 :green_heart:
asflicense
0m 33s

The patch does not generate ASF License warnings.

89m 41s

Subsystem
Report/Notes

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

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

JIRA Issue
MAPREDUCE-6752

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

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

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 1915e20b0e5739b11cd05fa5b8f5aede1f8ae513

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

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

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

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 56s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 59s

trunk passed

+1 :green_heart:
compile
0m 37s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
0m 33s

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

+1 :green_heart:
checkstyle
0m 28s

trunk passed

+1 :green_heart:
mvnsite
0m 37s

trunk passed

+1 :green_heart:
javadoc
0m 34s

trunk passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 27s

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
21m 28s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 33s

the patch passed

+1 :green_heart:
compile
0m 31s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
0m 31s

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 24s

the patch passed

+1 :green_heart:
mvnsite
0m 27s

the patch passed

+1 :green_heart:
javadoc
0m 23s

the patch passed with JDK Ubuntu-11.0.13+8-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
0m 20s

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

+1 :green_heart:
spotbugs
1m 10s

the patch passed

+1 :green_heart:
shadedclient
21m  5s

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

_ Other Tests _

+1 :green_heart:
unit
8m 16s

hadoop-mapreduce-client-app in the patch passed.

+1 :green_heart:
asflicense
0m 32s

The patch does not generate ASF License warnings.

96m 12s

Subsystem
Report/Notes

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

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux d2cc505f6539 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 1915e20b0e5739b11cd05fa5b8f5aede1f8ae513

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-11.0.13+8-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-285/1/testReport/

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 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.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  1s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
45m 55s

trunk passed

+1 :green_heart:
compile
0m 32s

trunk passed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2

+1 :green_heart:
compile
0m 26s

trunk passed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

+1 :green_heart:
checkstyle
0m 33s

trunk passed

+1 :green_heart:
mvnsite
0m 36s

trunk passed

+1 :green_heart:
javadoc
0m 38s

trunk passed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2

+1 :green_heart:
javadoc
0m 31s

trunk passed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

+1 :green_heart:
spotbugs
1m  2s

trunk passed

+1 :green_heart:
shadedclient
33m 13s

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

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s

the patch passed

+1 :green_heart:
compile
0m 25s

the patch passed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2

+1 :green_heart:
javac
0m 25s

the patch passed

+1 :green_heart:
compile
0m 23s

the patch passed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

+1 :green_heart:
javac
0m 23s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 23s

the patch passed

+1 :green_heart:
mvnsite
0m 26s

the patch passed

+1 :green_heart:
javadoc
0m 24s

the patch passed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2

+1 :green_heart:
javadoc
0m 22s

the patch passed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

+1 :green_heart:
spotbugs
1m  1s

the patch passed

+1 :green_heart:
shadedclient
33m  9s

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

_ Other Tests _

+1 :green_heart:
unit
8m 38s

hadoop-mapreduce-client-app in the patch passed.

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

131m 19s

Subsystem
Report/Notes

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

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

JIRA Issue
MAPREDUCE-6752

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

uname
Linux c65538322a76 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 1915e20b0e5739b11cd05fa5b8f5aede1f8ae513

Default Java
Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

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

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

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app

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

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.


Adds a docker image for the domain decomp tool

The point is that a user can use the tool to partition a given grid without going to the hassle of installing Zoltan and other prerequisites. It works well enough as is, even if the syntax is not the most obvious (but I added a section in the README.md file).
The only sore point is that I used COPY . /decomp in the Dockerfile, which triggers a rebuild of the tool every time the Docker image is built after modifying any file in the root directory. The alternatives are to select which files to copy or to pull everything from GitHub. Pulling from GitHub seems a bit much since the source is already there, and copying select files means updating the list if the project changes. So I went for what I considered the least bad solution.
Closes #69

I needed this, so I did it :)


Problematic Ternary-Expression Formatting Inside JS String Interpolation

VSCode Version: 1.46.1
OS Version: Fedora 32, Linux x64 5.6.19-300.fc32.x86_64

Steps to Reproduce:

manual breaking of a long line of a ternary expression within template string interpolation  ${ condition ? true : false }
running native formatter messes up the indentation for every possible correct format

Screenshots
Before:

After:

Before:

After:

So, the problem specifically seems to be in the way the formatter determines the indentation level to which it normalizes the rest of ternary expression body. The above screenshots show that it ignores the indentation level of the opening brace, and even the lines before it, adjusting itself to the first line indentation level.

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

Please share the text of the code along with screenshots

Please share the text of the code along with screenshots

updated.


Update http4s-server to 0.23.15

Updates org.http4s:http4s-server from 0.17.6 to 0.23.15.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Scalafix Migrations

org.http4s:http4s-.*:0.22.0 (created no change)

github:http4s/http4s/v0_22?sha=series/0.22

org.http4s:http4s-.*:0.21.5 (created no change)

dependency:v0_21@org.http4s:http4s-scalafix:0.21.5
Documentation: https://github.com/http4s/http4s/releases/tag/v0.21.5

org.http4s:http4s-.*:0.20.0 (created no change)

github:http4s/http4s/v0_20?sha=v0.20.11
Documentation: https://github.com/http4s/http4s/blob/v0.20.0/docs/src/main/tut/upgrading.md

Files still referring to the old version number
The following files still refer to the old version number (0.17.6).
You might want to review and update them manually.
build.sc

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s", artifactId = "http4s-server" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.http4s", artifactId = "http4s-server" }
}]

labels: library-update, early-semver-major, semver-spec-minor, scalafix-migrations, old-version-remains, commit-count:1

Superseded by #2536.


Sample code

This project looks interesting and may be exactly what I need. I was wondering, do you have some sample code that shows how to use the REST API, especially how to start a node application with arguments, i.e. 'node app myargs' through the REST API. That would help me a lot. Also, I assume it's possible to start a node application from within another node application (without using the REST API) with your package, right? What is the javascript syntax to start an application, again with arguments? Thanks for any help you can provide!

Hi,
All you need is in this file : https://github.com/oOthkOo/supervizer/blob/master/bin/supervizer-client
Cheers


Add '#buildwithklima' banner at the top of the carbon dashboard

Include banner text similar to what was utilized on the main Klima website for promoting the DCM webinar with a link to our RA documents to increase the awareness of these resources.

we did the Onset webinar banner, so going to close this ticket in favor of a more specific ticket to add some CTA (call-to-action) links to the sidebar - maybe direct people to Carbonmark to browse specific projects


Could you please provide a sample pose sequence

I was trying to follow insturctions bellow.
To animate a certain subject, say rp_carla_posed_004, prepare a pose sequence (.npz files containing the pose and transl parameters) under the directory data_scans/rp_carla_posed_004/test/
I don't know what the pose sequence(.npz files) should be like. Could you please provide a sample pose sequence?
Thanks very much!

Hi. The detailed description of what these .npz files should be can be found in Data Preparation for Training under the section The Whole Pipeline in the README. Note that for inference only two keys (pose and transl) are needed.
You can use the pose sequences in CAPE, whose format is consistent with ours. However, we cannot directly provide them due to copyright restrictions.

Thanks you for your prompt reply!
Besides, I generate the T-pose SMPL mesh by setting pose and shape parameters to zero. Is this correct?

Besides, I generate the T-pose SMPL mesh by setting pose and shape parameters to zero. Is this correct?

Yes, the T-pose SMPL should have zero pose parameters. But I am not sure about using zero shape parameters. The shape should match your training data. Normally this can be obtained by keypoints-based SMPL fitting methods.
In our work, we have used the ground truth SMPLX meshes provided in ReSynth, and applied the SMPLX-to-SMPL transfer model here to obtain shape and pose parameters.


fix(chat): publication mobile change overlap (Issue #1620)

Description:
Change path form should be open on click on Change link only, not to any place inside text box
Issue also should be fixed for select folders in Manage Attachments
Expected result: Open select folders form on click Change link only, not to any area in text box
Issues:

Issue #1620

UI changes

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review

/deploy-review

/deploy-review


Secure channel - Script has to be updated as per Test plan

From chip-test-scripts created by Rajashreekalmane: CHIP-Specifications/chip-test-scripts#648
Description:
Secure channel - Script missed to add the PICS_MCORE_ICD for below mentioned test cases.

[ ] TC-SC-4.1
[ ] TC-SC-4.3

Test-Plan Reference :
https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/securechannel.adoc#tc-sc-4-1-commissionable-node-discovery-dut_commissionee

@Rajashreekalmane We will fix the script once the test-plan issue 3439 got fixed

Waiting for https://github.com/CHIP-Specifications/chip-test-plans/issues/3440 to land . @akrithika27 FYI

closing this issue, DOP : https://github.com/project-chip/matter-test-scripts/issues/186

@raju-apple
I am implementing a test plan for mater 1.3.
I would like to know why PICS “MCORE.ICD” cannot be defined.
Has this problem already been fixed?


Enable learning rate scheduling

Enable learning rate scheduling for:

[ ] tensorflow/keras
[ ] pytorch
[ ] darknet (? @avanetten)

Issue moved to CosmiQ/solaris #27 via ZenHub


CORA Node Classification example fails on old cpus

When the CORA Node Classification example is run on old cpus (eg. madmax), the line that loads the dataset pyg_dataset = Planetoid('./cora', name, transform=T.TargetIndegree()), throws a Illegal instruction (core dumped) error

Hi frg100, this looks like a pytorch geometric problem instead of a deepsnap problem.