Update cats-effect, cats-effect-std to 3.3.13

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-std

from 3.3.4 to 3.3.13.
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!

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

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

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

Superseded by #474.


feature: Evaluate FUNC9 Quine Mc Cluskey

Feature description
CCN: 17 selection<EMAIL_ADDRESS>Good; 75% test coverage... 26 misses

This seems feasible to work with

I got this one. Opened a new issue #17


[Bug]: Requests Routed to Unexpected Models Despite Configuration in .env

What happened?
I specified in the .env file to only use chatgpt-4o-latest, but through the Cloudflare AI Gateway, I detected that some requests were being sent to gpt-3.5-turbo-**** without my knowledge. This is really strange.
When using Anthropic, I’ve encountered similar issues where my queries were unknowingly handed over to older models for processing.
Steps to Reproduce
1.Configure the .env file to use chatgpt-4o-latest as the model. For example:
MODEL=chatgpt-4o-latest

Deploy LibreChat with the above configuration.
Send queries through the chat interface, expecting all requests to use the specified model (chatgpt-4o-latest).
Use Cloudflare AI Gateway to observe the outgoing API requests.
Notice that some requests are unexpectedly routed to gpt-3.5-turbo-**** instead of the configured model (chatgpt-4o-latest).

Additional Observations
Similar behavior has been observed with Anthropic models, where queries are sometimes routed to older models, contrary to the specified configuration.
The issue occurs intermittently and without clear patterns.

What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This happens at the beginning of a new conversation, the smaller model is used for the conversation title generation. You can configure the title models in the .env file


add release version management commands to release script

Changes:

manage old version or current version of release in settings.py file
manage new version of release in Release_Version file
Usage:
change new version in Release_Version file and run release.sh script to deploy new release on github and s3 buckets

I don't think create more file is a good idea, then we need to change 2 places when want to release, one in settings, one in release version. Can we make it some how to have 1 place only?


SLF4J Implementation in OSGi

The Hikari project is currently attached to a specific SLF4J implementation (artifact: slf4j-simple-1.7.10.jar). Hence, if the project using HikariCP uses a different SLF4J implementation then the artifact throws a warning SLF4J: Class path contains multiple SLF4J bindings. followed by the list of implementations found.
In the OSGi world, it is very common to replace one implementation by another, so if HikariCP could just use the available implementation rather that having a hard-coded implementation (slf4j-simple-1.7.10.jar), then that would be a major improvement for OSGi users.

Sure.  In my day job we're actually big OSGi users, but do be honest our product doesn't actually use HikariCP (we need JTA, and so use Bitronix, for which I'm also a developer).  I'll fixed up OSGi headers.

Ok, when you have it ready let us know in the release notes what release contains the fix. Thanks.

Now I'm confused.  At compile time HikariCP depends on slf4j 1.7.10, however the jar artifact produced does not have specific version dependency in the manifest.  The MANIFEST.MF contains this header:
Import-Package: org.slf4j;version="[1.6,2)"

which is a range of 1.6.2+ or greater.  If you are using a version older than that, either upgrade your dependency, or if you can demonstrate compatibility with older versions I can change the supported range.

I was receiving this warning message during some Unit Tests
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/D:/projects/lib/maven-repo/org/slf4j/slf4j-simple/1.7.10/slf4j-simple-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/D:/projects/lib/maven-repo/org/slf4j/slf4j-log4j12/1.5.11/slf4j-log4j12-1.5.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

but I am really not sure where that other implementation comes from because I use log4j-1.2.17 and I don't have it (the slf4j-log4j12) declared in the project dependencies. I have excluded that artifact slf4j-log4j12 from some dependencies but the warning keeps showing up. I'll investigate further and keep you posted.

Found the issue. It was this artifact org.jboss.arquillian.container:arquillian-container-osgi:1.1.1.Final which was causing the problem, it uses in a dependency of a dependency the artifact slf4j-log4j12, and causing a double slf4j implementation and the warning.
Just added an exclusion to the dependency and fixed the warning message:
<dependency>
  <groupId>org.jboss.arquillian.container</groupId>
  <artifactId>arquillian-container-felix-embedded</artifactId>
  <version>1.1.1.Final</version>
  <scope>test</scope>
  <exclusions>
    <exclusion>
      <groupId>org.slf4j</groupId>
      <artifactId>slf4j-log4j12</artifactId>
    </exclusion>
  </exclusions>
</dependency>


Allow configuring images in infra config

The infrastructure configs should allow overriding the image used for router, broker, agent and standard-controller.
This is a useful mechanism for the address space controller to detect that they should be updated and restarted.

The infraconfig already provides a pod-templates for each of these resources so it would be possible to allow the image to be overridden from there.  The disadvantage is that this forces the container names to be public, as the podtemplate comprises the container sections which must be named.


Fix 'See All' button on parametric modal when a date range filter is active.

Hiya,
Thanks so much for the bugfix!  Could you add a regression test, please?  Then we'll gladly pull this into develop and the current release branch.
Thanks!

:+1: thanks!


[Feature] Animated previews

Add animated token previews (these must be linked in tho and happen on hover) use data-tooltip="<img src='https://i.imgur.com/7wj8Eor.jpeg'>"
Must be linked from web so module doesn't get HOOG


Automate permissive traffic policy mode troubleshooting

Please describe the Improvement and/or Feature Request
https://github.com/openservicemesh/osm/issues/2855 suggests automating the troubleshooting guide for permissive mode. This issue is to track any automation to troubleshoot issues seen in permissive mode.
Scope (please mark with X where applicable)

New Functionality          [ ]
Install                    [ ]
SMI Traffic Access Policy  [ ]
SMI Traffic Specs Policy   [ ]
SMI Traffic Split Policy   [ ]
Permissive Traffic Policy  [ ]
Ingress                    [ ]
Egress                     [ ]
Envoy Control Plane        [ ]
CLI Tool                   [X]
Metrics                    [ ]
Certificate Management     [ ]
Sidecar Injection          [ ]
Logging                    [ ]
Debugging                  [ ]
Tests                      [ ]
CI System                  [ ]
Demo                       [ ]
Project Release            [ ]

Possible use cases
Automate troubleshooting of permissive mode.

Closing as the original issue https://github.com/openservicemesh/osm/issues/2855 is reopened.


text input field onfocus clears out existing states and rebuild the widget.

I have a page with 2 text input fields, when these are on focus , my widget was rebuilt, it cases issues of some other state changes being wiped out. these input fields works fine tho. Seems to only appear on this particular page which was pushed by a page route.
any idea what's happening?
titleFocus.addListener((){
      if(titleFocus.hasFocus){
        setState(() {
          widget.err = '';
        });
      }
    });

    expiryFocus.addListener((){
      if(expiryFocus.hasFocus){
        setState(() {
          widget.err = '';
        });
      }
    });

 CupertinoTextField(
                              controller: titleController,
                              focusNode: titleFocus,
                              padding: EdgeInsets.symmetric(vertical: 15, horizontal: 20),
                              decoration: BoxDecoration(color: Colors.white,borderRadius: new BorderRadius.all(const Radius.circular(10))),
                              keyboardType: TextInputType.multiline,
                            ),

CupertinoTextField(
                                        keyboardType: TextInputType.number,
                                        focusNode: expiryFocus,
                                        controller: expiryController,
                                        padding: EdgeInsets.symmetric(
                                            vertical: 15, horizontal: 20),
                                        decoration: BoxDecoration(color: Colors.white,
                                            borderRadius: new BorderRadius.all(
                                                const Radius.circular(10))),
                                      ),

 Navigator.push(
          context,
          CupertinoPageRoute(builder: (context) => NewInvite(uid, 'New Invite')), //change to widget.uid after refactor
        )

@comeonbuddy sorry I don't see how this is related to the Geolocator plugin (and out of the box I am also not sure what is causing your issue).
Maybe you should try on the Flutter repo: https://github.com/Flutter/Flutter?

sorry didn't meant to post it here :/


add focus selector on tabs

This is documented in comment on pull request #569

https://github.com/HTBox/allReady/pull/569#discussion-diff-53570426 to be precise.

@tonysurma Assign this to me

@mheggeseth was this taken care of in one of your PRs?  Thx

@tonysurma I'm pretty sure this isn't fixed yet. I'll do it real quick though. Been a while since I did a PR.


Issue

Returns this message several times:
- You must have a premium account to download this course
And I need to restart the download again and again...

This issue has been fixed
check llvd version 2.0.1

This issue has been fixed
check llvd version 2.0.1

I tested version 2.0.1 and it didn't solve the problem

I tested version 2.0.1 and it didn't solve the problem

What is the error this time ?

What is the error this time ?

the same problem continues

the same problem continues

I want to see the screenshot..Are you using it behind a proxy?

I want to see the screenshot..Are you using it behind a proxy?

I want a screenshot because I am printing the error in the code to help me understand the real issue

I want a screenshot because I am printing the error in the code to help me understand the real issue

After starting the download;
download many videos but not all;
after downloading many videos;
Returns this message;
------- You must have a premium account to download this course
And I need to restart the download again and again...;
I can download all the videos but I have to restart (login)/resume download several times

After starting the download;
download many videos but not all;
after downloading many videos;
Returns this message;
------- You must have a premium account to download this course
And I need to restart the download again and again...;
I can download all the videos but I have to restart (login)/resume download several times

This type of error is not in the updated version 2.0.1...Please uninstall llvd and reinstall again

This type of error is not in the updated version 2.0.1...Please uninstall llvd and reinstall again

how to uninstall?

how to uninstall?

pip uninstall llvd
if you get an error do so with powershell as an administrator.
To reinstall do pip install llvd=='2.0.1'

pip uninstall llvd
if you get an error do so with powershell as an administrator.
To reinstall do pip install llvd=='2.0.1'

This error is valid because you have a poor internet connection...requests package maximum retries when are reached llvd stops
You might want to try again
I am going to close this issue if there are no other issues.

This error is valid because you have a poor internet connection...requests package maximum retries when are reached llvd stops
You might want to try again
I am going to close this issue if there are no other issues.

My Internet conection is 5Mb/s (1.98MB/s)

My Internet conection is 5Mb/s (1.98MB/s)

That is weird

That is weird

I am grateful for the script and for you to respond so quickly, but do not use the word "poor", perhaps your country may not offend, but in other countries it may offend a lot for having other meanings.
Have a nice day.

I am grateful for the script and for you to respond so quickly, but do not use the word "poor", perhaps your country may not offend, but in other countries it may offend a lot for having other meanings.
Have a nice day.


Usage of focus and blur on input

Does the usage of focus and blur methods still exist for input component?? If yes, how can I make use of those methods.

In the latest update of react-toolbox, "react-toolbox": "2.0.0-beta.11", It did not have focus and blur as functions. Are you planning to have that back or permanently remove it?

Same here, just updated from beta8 to beta12 to get rid of PropTypes warnings, and my focus/blur calls won't work anymore.

Not sure what could be happening, I tested it in 2.0.0-beta.11, and passing onBlur and onFocus props to the <Input /> component it seems to work:
<Input
  // Other props
  onBlur={() => console.log('onBlur event')}
  onFocus={() => console.log('onFocus event') }
/>

@rubenmoya onBlur and onFocus are working totally fine. I'm looking for focus and blur methods for input.

Are you getting a Uncaught TypeError: Cannot read property 'focus' of undefined error?
This is in that method: 'DEPRECATED: To access the wrapped instance, you have to pass ' + '{ innerRef: fn } and retrieve with a callback ref style.'
I made it work using innerRef={(node) => { this.inputNode = node; }} and then a method with this.inputNode.focus();, but I don't know if that's the problem.

Thank you for the help. I tried this method, but I'm getting a warning like:  Unknown prop innerRef on  tag. Not sure how would I define that?

Hm, that should work. Can you show how you're using it?

If I have understood it right, within my input I have
<Input
......
innerRef={(node) => { this.myInput = node; }}
......
/>
and under componentDidMount have defined this.myInput.focus(). It does work right, but throws a warning saying Unknown prop innerRef

I believe react-css-themr should use (and remove) that prop before it's passed down to the RT Input component. You aren't using an outdated version of that package?

Hi. I am facing the same problem. here's my code:

render() {
   return (
     <Input
        type={type}
        {...input}
        disabled={disabled || !editable}
        icon={icon}
        theme={registrationTheme}
        className={registrationTheme.input}
        placeholder={placeholder}
        ref={(r) => { this.ref = r; }}
     />
   )
}

and I am trying to make the input field focus using:
makeFocus() {
  this.ref.getWrappedInstance().focus();
}

I'm using<EMAIL_ADDRESS>

Not sure what could be happening, I tested it in 2.0.0-beta.11, and passing onBlur and onFocus props to the <Input /> component it seems to work:
<Input
  // Other props
  onBlur={() => console.log('onBlur event')}
  onFocus={() => console.log('onFocus event') }
/>

That resolver my problem.


Fix column alignment in debug-service.md

Previously, the columns showing one of kubectl's output were misaligned and thereby confusing.

Hey @jacksgt  could you please sign the CLA first? Thanks!

I signed it!
Just had to go through all the emails and click all the things. :-)

/lgtm
/approve


Adding backup for manual install on FreeBSD

Will add the restore part later, although it is even easier

Thank you for your PR. CI fails here, doc preview cannot be built.
Additionally: As backup and restore is the most linked doc, I do not see adding steps for unsupported installation methods. People who choose manual installation should be able to transfer the steps themselves.
My suggestion: move to the manual installation instructions.


[Bug] [Service] Condition 'globalParamsMap != null' is always 'true'.

Purpose of the pull request
close #12383
fix condition 'globalParamsMap != null' is always 'true' .
Brief change log
Condition 'globalParamsMap != null' is always 'true' .
Verify this pull request
if (!globalParamsMap.isEmpty()) {
params.putAll(globalParamsMap);
}

Codecov Report

Merging #12384 (9bfaffd) into dev (cd5fb12) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                dev   #12384      +/-   ##
============================================
- Coverage     38.93%   38.92%   -0.01%
- Complexity     4175     4177       +2
============================================
  Files          1040     1040
  Lines         38802    38805       +3
  Branches       4462     4460       -2
============================================
- Hits          15107    15105       -2
- Misses        21927    21931       +4
- Partials       1768     1769       +1

Impacted Files
Coverage Δ

...inscheduler/service/expand/CuringGlobalParams.java
31.11% <0.00%> (ø)

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
55.12% <0.00%> (-1.29%)
:arrow_down:

...dolphinscheduler/plugin/task/datax/DataxUtils.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Thank you for your excellent open-source work. May I ask how to reproduce IFF Net? thanks

Hi, thanks for interest. Please see https://github.com/YUCHEN005/DPSL-ASR/blob/master/espnet2/layers/iff_net.py for network code of iffnet


node: upgrade to protobuf.js 6

WIP. Still need to fix some tests.
Fixes #8991.
Causes some API surface changes (async load, grpc loadObject returns a ProtoBuf.Root and is intended to be used with lookup).
Code is in place to ease the transition from old GRPC code targeting Protobuf.JS 5 internally and Protobuf.JS 6 GRPC code.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Hmmm @grpc-jenkins is going a bit haywire!

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Blockers:

[ ] https://github.com/dcodeIO/protobuf.js/issues/535
[ ] https://github.com/dcodeIO/protobuf.js/issues/534

load is now sync.

@murgatroid99 requesting a re-review.
Also, the only tests that are failing now are the interop tests. It seems that zeroBuffer is being called with undefined due to the request_length field being undefined on the response object. I'd love it if you could have a look.
Thanks!

Also, Jenkins: this is OK to test

Also, regarding the interop test failures: if Protobuf.js is outputting undefined values for fields that exist, that is an incorrect implementation of Protobuf 3. Any field not not provided in the serialized format should be deserialized to the default value.

Regarding undefined: Default values are on the respective message prototype now, so there shouldn't be any unexpected undefineds. This feature requires always using runtime messages (i.e. created from Type.create, which the decoder does automatically), because plain objects do not have anything special on their prototypes.

According to the Protobuf.Js docs:
There are no more null values marking unset fields. Instead, default values are on the prototype now and existence on the wire can be checked with Object#hasOwnProperty
@dcodeIO
Will double check

@dcodeIO In GRPC messages are deserialize using asJSON before being passed up to the caller. Iirc there was a option to put the default values on the resultant object. Is that correct?

@paralin: Yes, "defaults: true".

Blocked by:

[ ] https://github.com/dcodeIO/protobuf.js/issues/566

@murgatroid99 I've added some compatibility fillers to force the loadObject output to look the same as before. Let me know what you think.

@murgatroid99 @dcodeIO finished upgrades, all tests pass, loadObject output is nearly identical to before, load is sync, added loadAsync if someone wants to load asynchronously, fixed integration tests, etc.

@murgatroid99 Fixed.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Jenkins, I said this is OK to test
Also, now the .gitignore is conflicting.

@paralin Please resolve merge conflicts so that this can be merged

Thanks for your pull request. The automated tests will run as soon as one of the admins verifies this change is ok for us to run on our infrastructure.

Hi, what's the status on this PR? I took the liberty of fixing the tests https://github.com/paralin/grpc/pull/1, but I'm not sure what else needs to be done before this is ready to be merged.

What happened here is I was extensively using grpc in my own code, but suddenly switched to Go from Node and now have no pressure on me to get this merged from myself. As a result I haven't been updating it as I should.
I have actually already fixed most of these comments in here, I'll push the changes today. @lanttu thanks for the help!

This is a really pressing point, could you please let us know when this would be available ?

@murgatroid99 Rebased on master, fixed a bunch of bugs, tests pass. Should be ready to merge.

Bazel full build and tests is failing, but the failure looks unrelated to this PR.
Like this:
Running test custom_metadata
Feb 28, 2017 6:01:29 PM io.netty.util.internal.MacAddressUtil defaultMachineId
WARNING: Failed to find a usable hardware address from the network interfaces; using random bytes: d8:93:53:22:c3:d8:2f:9d
Exception in thread "main" io.grpc.StatusRuntimeException: INTERNAL: Connection closed with unknown cause

OK, that Linux portability test failure looks like it's caused by the ongoing Amazon S3 outage. Still, it's an Electron test, so I'd prefer to run it before merging this.

@murgatroid99 Funny, so much was affected by that. Respinning the tests.

I'm also a little worried about the interop failure in the previous run. The custom_metadata test was failing between a Node client and a Java server. It seems to be a real failure introduced with this change, but I can't figure out what caused it.

Alright, will look into it.
Ping @dcodeio

While conversion to camel case is the default now, there is still an option to keep casing when using protobuf.Root directly for loading:
var root = new protobuf.Root();
root.load("someFile.proto", { keepCase: true }, function(err, root) { ... });

Likewise, pbjs has the option --keep-case.

JavaScript style is camel case, so it makes sense to use camel case. However for compatibility I think we may need to add an option to protobufjs that enables some extra code to try converting to camel case from underscore case when the given property name does not match any camel case fields.
We could then accept underscore fields in the input for compatibility. Could add an option to grpc for camel case too, to use when loading a proto file.

I think the only way to be sure this change is non-breaking is to have all of the tests pass without modifying any existing tests. So, you should revert the changes to src/node/interop/interop_{client,server}.js and to src/node/test/common_test.js.
In addition, strictly speaking, grpc.loadObject should be able to load a Protobuf.js 5 reflection object like it currently does to maintain complete compatibility. I am willing to do that myself in a later PR, but it would be much appreciated if you could keep that capability here, either by adding a new function (e.g. loadProtobufJs6Object) or by doing some sort of check in the existing loadObject.

Here is an example on how to add custom getters/setters to runtime message prototypes: https://github.com/dcodeIO/protobuf.js/blob/master/examples/custom-get-set.js
Here, it keeps underscore (returned by toObject, toJSON etc.) and adds virtual camel cased fields.

Based on the work in this pull request, I have created my own implementation of this upgrade in #10204. I would appreciate your input there.
I am going to close this PR, but it can be reopened if in the future this seems like the better way to move forward with this change.


[FX-2211] Fair collections rail

The type of this PR is: Feature
This PR resolves FX-221
Description

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)

Looks good to me! #mergeongreen


Find out what to do with course_providers without organisation

"entity":{"composite":"otm-e833df18-8d40-4f61-966c-a6b8e72f3bec-
tuni-org-1010000006","coursecode":"otm-e833df18-8d40-4f61-966c-a6b8e72f3bec","organizationcode":"tuni-org-1010000006"}}}
updater fails to create course_provider for this, since tuni-org-1010000006 isn't an organization we have in our data


Cannot find module 'gl-matrix/vec3'

I've succesfully used gltfjsx in the past but suddenly today when I ran npx gltfjsx filename.glb I got the following error in my console:
Cannot find module 'gl-matrix/vec3'

<EMAIL_ADDRESS>/Users/xxx/.npm/_npx/24391/lib/node_modules/gltfjsx/src/utils/transform.js
/Users/xxx/.npm/_npx/24391/lib/node_modules/gltfjsx/src/gltfjsx.js
/Users/xxx/.npm/_npx/24391/lib/node_modules/gltfjsx/src/components/App.js
/Users/xxx/.npm/_npx/24391/lib/node_modules/gltfjsx/node_modules/import-jsx/index.js
/Users/xxx/.npm/_npx/24391/lib/node_modules/gltfjsx/cli.js

The package gl-matrix released a new version (3.4.0) which brakes this package (see https://github.com/toji/gl-matrix/issues/439). I assume they will fix it soon.
In the maintime you can add this to your package.json to continue.
"resolutions": {
    "gl-matrix": "3.3.0"
 }

I've pushed a new release of @gltf-transform/core pinned to<EMAIL_ADDRESS>which should resolve things for gltfjsx as well. See: https://github.com/donmccurdy/glTF-Transform/pull/378.


STORM-994 Close download clients and channels to avoid resource leaks

This pull request to fix STORM-994 to avoid resource leaks between nimbus and supervisors.
Could you please review ?
Thanks

Looks fine overall. +1


ENH: sosfreqz

I had no idea how close to mergeable @WarrenWeckesser's #4465 was. This should be ready for review/merge, I just rebased and tweaked the release notes.

Thanks for picking this up! I got sucked down a rabbit hole when trying to make this part of gh-6059, which I will now ramble on about:
Basically, I was thinking it would be good if proper SOS and ZPK frequency responses could just live behind (d)freqresp without needing to create more public functions. This led me to look into creating the SOS LTI objects classes which we definitely want; however, this breaks all of the functions with call signatures that count arguments to determine the filter representation.
I.e., we specify the SOS arrays as arrays of shape (N, 6), but functions like freqresp use their arguments to create an LTI object via lti(*args) which means lti(*sos) can look like a TF, zpk, or SS depending on N. So, we need to either deprecate those call signatures, or find a way to determine the difference between a (2,6) SOS array and length six (b, a) coefficients.
All this is to say: we probably do indeed need this, and the more accurate zpk version, to be public. We should also come up with a solution to the SOS LTI object issue sooner rather than later.

we probably do indeed need this, and the more accurate zpk version, to be public

Maybe just for now we do the SOS, and then someone else can make public the improved ZPK one?

We should also come up with a solution to the SOS LTI object issue sooner rather than later.

Yeah I would like to see that, too, but I worry about holding this one up to wait on it. Are you okay going forward with sosfreqz for now?

Yeah I would like to see that, too, but I worry about holding this one up to wait on it. Are you okay going forward with sosfreqz for now?

Sorry for being unclear, this is what I was getting at. I agree that this PR should happen sooner rather than later.

Eric, thanks for picking this up.  The changes look good; I made a few suggestions the code.
My PR was pretty close to ready.  The main issue (which I agree with) was the API.  I copied it from freqz just to be consistent, but it isn't a great starting point.  (worN is an awkward argument name, and if not for maintaining backwards compatibility, I'd remove the plot argument from freqz.)  Alternatives have been discussed elsewhere, but their implementation is not imminent, so perhaps it would be best to get sosfreqz in now, knowing that it might become obsolete with the next generation of the signal API.  The perfect is the enemy of the good and all that...

@WarrenWeckesser any idea how your changes could have broken some scipy.special tests for mpmath?

I removed the plot argument since I don't think it should really be there (even in freqz), but I kept the other arguments named the same so there is some compatibility with the existing function.

@endolith do you want to have a look since you have been involved in SOS?
@rgommers you've been involved with the API discussions, can you live with another function that isn't part of the grand-unified API?

@rgommers you've been involved with the API discussions, can you live with another function that isn't part of the grand-unified API?

Yes. One more or less is not going to make the difference, and this is functionality that is needed.

Also would it be worth showing a higher-order filter that becomes garbled with freqz?

Also would it make sense to have a parameter that makes it output the responses for each stage separately, so you can plot them individually?  https://en.wikibooks.org/wiki/Signals_and_Systems/Second_Order_Transfer_Function#Amplitude_Responses

Suggested changes in https://github.com/endolith/scipy/commit/b35fbc63b3e67483cd0a05a44afe8332b534886c

Thanks @endolith cherry-picked and updated.
Based on the comments I think this should be mergeable. If anyone else wants to look again (or wants me to wait) feel free, otherwise I'll put it in next week.

For testing, you could generate some high-order filters as SOS and then check that sosfreqz is within bounds for what the filter should do, like the plots and tests for these:

http://docs.scipy.org/doc/scipy-0.14.0/reference/generated/scipy.signal.cheb2ord.html
http://docs.scipy.org/doc/scipy-0.14.0/reference/generated/scipy.signal.cheb1ord.html
http://docs.scipy.org/doc/scipy-0.14.0/reference/generated/scipy.signal.ellipord.html
http://docs.scipy.org/doc/scipy-0.14.0/reference/generated/scipy.signal.buttord.html
https://github.com/scipy/scipy/blob/master/scipy/signal/tests/test_filter_design.py#L556-896

@endolith commit added, see if you're happy now

I started modifying the test cases to make them more extreme (so that sosfreqz could handle them but freqz couldn't) but one of them fails, and I don't now if it's sosfreqz or ellipord or ellip that's actually responsible:
N, Wn = ellipord(0.3, 0.25, .5, 150)
sos = ellip(N, .5, 150, Wn, 'high', output='sos')
w, h = sosfreqz(sos)
dB = 20*np.log10(np.abs(h))
w /= np.pi
plot(w, dB)

@endolith wrote:

I started modifying the test cases to make them more extreme (so that sosfreqz could handle them but freqz couldn't)

That's also what TestSOSFreqz.test_sos_freqz_against_mp() does--it verifies the correctness of an order 25 filter by comparing it to the result computed using mpmath.  The mpmath functions are in tests/mpsig.py.

anyway these are the checks I made:
        # from cheb2ord
        N, Wn = cheb2ord([0.1, 0.6], [0.2, 0.5], 3, 150)
        sos = cheby2(N, 150, Wn, 'stop', output='sos')
        w, h = sosfreqz(sos)
        dB = 20*np.log10(np.abs(h))
        w /= np.pi
        assert_allclose(dB[w <= 0.1], 0, atol=3.01)
        assert_allclose(dB[w >= 0.6], 0., atol=3.01)
        assert_array_less(dB[(w >= 0.2) & (w <= 0.5)], -149.9)

        # from cheb1ord
        N, Wn = cheb1ord(0.2, 0.3, 1, 150)
        sos = cheby1(N, 1, Wn, 'low', output='sos')
        w, h = sosfreqz(sos)
        dB = 20*np.log10(np.abs(h))
        w /= np.pi
        assert_allclose(dB[w <= 0.2], 0, atol=1.01)
        assert_array_less(dB[w >= 0.3], -149.9)

        # adapted from ellipord
        N, Wn = ellipord(0.3, 0.25, .5, 150)
        sos = ellip(N, .5, 150, Wn, 'high', output='sos')
        w, h = sosfreqz(sos)
        dB = 20*np.log10(np.abs(h))
        w /= np.pi
        assert_allclose(dB[w >= 0.3], 0, atol=.55)
        assert_array_less(dB[(w > 0) & (w <= 0.25)], -149.9)

        # adapted from buttord
        N, Wn = buttord([0.2, 0.5], [0.14, 0.6], 3, 100)
        sos = butter(N, Wn, 'band', output='sos')
        w, h = sosfreqz(sos)
        dB = 20*np.log10(np.abs(h))
        w /= np.pi
        assert_array_less(dB[(w > 0) & (w <= 0.14)], -99.9)
        assert_array_less(dB[w >= 0.6], -99.9)
        assert_allclose(dB[(w >= 0.2) & (w <= 0.5)], 0, atol=3.01)

Thanks @endolith added your tests (after making the problematic ellipord test use 147 instead of ~149 for the acceptable level), squashed and rebased.
If there are no other comments I'll merge in a couple of days.

Thanks for the reviews


Objective-C : backoff.c vs GRPCConnectivityMonitor stream reconnection issue

I'm trying to understand the reconnection algorithms for gRPC stream, and don't understand something :
There seems to be an automatic retry mechanism in place at the gRPC-Core implementation, like the "backoff.c" file suggest. This mechanism suggests that loss of connectivity will be automatically resumed once the connectivity is restored (or at least that the first time connection phase may succeed after some time).
BUT, the gRPC objective-c layer monitors each GRPCCalls using a GRPCConnectivityMonitor, with the following handler :
[_connectivityMonitor handleLossWithHandler:^{
    typeof(self) strongSelf = weakSelf;
    if (strongSelf) {
      [strongSelf finishWithError:[NSError errorWithDomain:kGRPCErrorDomain
                                                      code:GRPCErrorCodeUnavailable
                                                  userInfo:@{NSLocalizedDescriptionKey: @"Connectivity lost."}]];
      [[GRPCHost hostWithAddress:strongSelf->_host] disconnect];
    }
  }];

Which makes me wonder : how are we supposed to handle automatic reconnection of gRPC streams ?
EDIT: i'm not even sure the backoff mechanism is used once the connection is established to handle disconnections, but in any case, i don't understand how the two mechanisms can work together, even for a first time connection.

Streams in gRPC are tightly bound to the connection they're initiated on, with no built in support for resumption or migrating them to a different backend. If you need this you'll need to provide some application level logic to cover it.


PARQUET-433: Add TypedColumnReader template and templatize value decoders

Having the physical Parquet types available at compile time opens up many new avenues to simplify the code and make it easier to extend and refactor. Fewer switch statements, and the type_traits template pattern (see parquet/types.h) lets us associate value types and other stuff with the parquet::Type values at compile time. This also makes the decoder classes (especially dictionary encoding) much simpler. We'll reap the same benefits on the encoding / writing paths in the future.
This includes #18, #19, and #20, and I will rebase once those patches are completed and merged.

For the sake of my sanity (since I already refactored parquet_reader.cc) I'm going to address these comments in #23

Closing this PR in favor of #23 which has 1 commit per JIRA


Show vectors with correct precision

Describe the bug:
Currently, Attu always shows vector data as float64. For example, a value 0.001 is displayed as 0.0010000000474974513
Steps to reproduce:

create a collection
insert some data, load the collection
observe the "Data" page in Attu

Attu version:
2.3.8
Attu version:

I don't think attu should handle this.  milvus should handle this.


Fix 'sudo: [cmd]: command not found' when using _ alias

fix 'sudo: [cmd]: command not found' error when executing commands like _ ff somefile -print
(see http://superuser.com/questions/605417/ddg#605460)

Though it does not affect _ -u someuser somealias


How can I overwrite config.js?

Is it possible? Inside the code it looks like it's not possible, because the default config.js is required in a relative manner all over the place.

Hi,
yes, it's definetely possible.
You could override the default configuration setup, by setting the property in the configuration object as environment variable... take a look at config.js, this is the line that permit to override the default configuration:
Object.assign(config, process.env);

If you run your app on Heroku, (and probably even other similiar service) you could setting the environment variable directly from their website.

Thank you.


Exclude Thumbs.db in compiled bin

Is there a better way to implement this? I'm not sure we want to maintain a list of things to ignore (Thumbs.db, DS_Store, etc). Can we do something else to make sure Thumbs.db and friends don't appear?

Use .gitignore in some way, perhaps?

I like that idea much better.

Sure, sounds like a good idea. Would you like to do it?

Ok.


Handle missing values for delimited text files when Nullhandling is enabled

Fixes #8778 .
Description
For delimited text file inputs, empty and missing values are parsed as the same when -Ddruid.generic.useDefaultValueForNull=false is enabled.
The delimited and csv parsers are therefore modified to differentiate between missing and empty values.

This PR has:

[x ] been self-reviewed.
[x ] added unit tests or modified existing tests to cover new code paths.
[x ] been tested in a test Druid cluster.

@nishantmonu51 Could you please review this?

@jihoonson Would you have time to review this?

@a2l007 sorry for the delayed review. I can take a look today. Would you please fix the conflicts?

@jihoonson Oops yeah fixed them now.


is there MAUI support planned?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@gsgou it's not supported.
There was an attempt to add MAUI support - https://github.com/crowdin/xamarin-sdk/pull/5
Maybe, @bnoffer can shed some light on this.
Anyway, you can always utilize the Crowdin CDN endpoints described here - https://support.crowdin.com/content-delivery/#for-web-applications


HBASE-28216 HDFS erasure coding support for table data dirs

This is a draft because I expect it to fail for hadoop2. I want to take a stab at making it work on branch-2, but will need to iterate on some reflection stuff. Will convert to real once I'm ready.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 10s
branch-2 passed

+1 :green_heart:
compile
1m 55s
branch-2 passed

+1 :green_heart:
shadedjars
5m 45s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  5s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for patch

-1 :x:
mvninstall
1m 21s
root in the patch failed.

-1 :x:
compile
0m 28s
hbase-server in the patch failed.

-1 :x:
compile
0m 16s
hbase-shell in the patch failed.

-0 :warning:
javac
0m 28s
hbase-server in the patch failed.

-0 :warning:
javac
0m 16s
hbase-shell in the patch failed.

-1 :x:
shadedjars
3m 52s
patch has 48 errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 26s
hbase-server generated 1 new + 21 unchanged - 0 fixed = 22 total (was 21)

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-protocol-shaded in the patch passed.

-1 :x:
unit
6m 29s
hbase-client in the patch failed.

-1 :x:
unit
0m 29s
hbase-server in the patch failed.

-1 :x:
unit
0m 17s
hbase-shell in the patch failed.

29m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 954834810a8e 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 3d42cee028

Default Java
Temurin-1.8.0_352-b08

mvninstall
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-mvninstall-root.txt

compile
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-compile-hbase-server.txt

compile
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-compile-hbase-shell.txt

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-compile-hbase-server.txt

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-compile-hbase-shell.txt

shadedjars
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-shadedjars.txt

javadoc
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/diff-javadoc-javadoc-hbase-server.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-client.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-shell.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/testReport/

Max. process+thread count
254 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 12s
branch-2 passed

+1 :green_heart:
compile
4m  6s
branch-2 passed

+1 :green_heart:
checkstyle
1m  1s
branch-2 passed

+1 :green_heart:
spotless
0m 44s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 13s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 43s
the patch passed

+1 :green_heart:
compile
4m  2s
the patch passed

+1 :green_heart:
cc
4m  2s
the patch passed

+1 :green_heart:
javac
4m  2s
the patch passed

+1 :green_heart:
checkstyle
1m  2s
the patch passed

-0 :warning:
rubocop
0m  8s
The patch generated 5 new + 701 unchanged - 3 fixed = 706 total (was 704)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
hadoopcheck
1m 11s
The patch causes 48 errors with Hadoop v2.10.2.

+1 :green_heart:
hbaseprotoc
1m 27s
the patch passed

+1 :green_heart:
spotless
0m 43s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 45s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 30s
The patch does not generate ASF License warnings.

43m 58s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile cc hbaseprotoc prototool rubocop

uname
Linux 6ba71016a352 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 3d42cee028

Default Java
Eclipse Adoptium-11.0.17+8

rubocop
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-general-check/output/diff-patch-rubocop.txt

hadoopcheck
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-general-check/output/patch-javac-2.10.2.txt

Max. process+thread count
82 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3 rubocop=1.37.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 54s
branch-2 passed

+1 :green_heart:
compile
2m  1s
branch-2 passed

+1 :green_heart:
shadedjars
5m  2s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  8s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 42s
the patch passed

+1 :green_heart:
compile
2m  1s
the patch passed

+1 :green_heart:
javac
2m  1s
the patch passed

+1 :green_heart:
shadedjars
5m  1s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  6s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 36s
hbase-protocol-shaded in the patch passed.

-1 :x:
unit
6m 33s
hbase-client in the patch failed.

+1 :green_heart:
unit
220m 17s
hbase-server in the patch passed.

-1 :x:
unit
7m 59s
hbase-shell in the patch failed.

263m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 20c104faf17a 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 3d42cee028

Default Java
Eclipse Adoptium-11.0.17+8

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-client.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-shell.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/testReport/

Max. process+thread count
4346 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/1/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 29s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  1s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 19s
branch-2 passed

+1 :green_heart:
compile
4m  3s
branch-2 passed

+1 :green_heart:
checkstyle
1m  0s
branch-2 passed

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 23s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 53s
the patch passed

+1 :green_heart:
compile
4m  2s
the patch passed

+1 :green_heart:
cc
4m  2s
the patch passed

+1 :green_heart:
javac
4m  2s
the patch passed

-0 :warning:
checkstyle
0m 33s
hbase-server: The patch generated 8 new + 7 unchanged - 0 fixed = 15 total (was 7)

-0 :warning:
checkstyle
0m  6s
hbase-shell: The patch generated 3 new + 0 unchanged - 0 fixed = 3 total (was 0)

-0 :warning:
rubocop
0m  8s
The patch generated 5 new + 701 unchanged - 3 fixed = 706 total (was 704)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 53s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
hbaseprotoc
1m 30s
the patch passed

-1 :x:
spotless
0m 36s
patch has 63 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
4m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

43m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile cc hbaseprotoc prototool rubocop

uname
Linux a9613c1e6dfa 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a419b390cf

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-general-check/output/diff-checkstyle-hbase-shell.txt

rubocop
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-general-check/output/diff-patch-rubocop.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
83 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3 rubocop=1.37.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m 20s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 58s
branch-2 passed

+1 :green_heart:
compile
2m  2s
branch-2 passed

+1 :green_heart:
shadedjars
5m 13s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  8s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 49s
the patch passed

+1 :green_heart:
compile
2m  3s
the patch passed

+1 :green_heart:
javac
2m  3s
the patch passed

+1 :green_heart:
shadedjars
5m 10s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  6s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 35s
hbase-protocol-shaded in the patch passed.

-1 :x:
unit
6m 33s
hbase-client in the patch failed.

+1 :green_heart:
unit
222m 22s
hbase-server in the patch passed.

+1 :green_heart:
unit
8m  1s
hbase-shell in the patch passed.

270m  2s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 8248c406da49 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a419b390cf

Default Java
Eclipse Adoptium-11.0.17+8

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-client.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/testReport/

Max. process+thread count
4516 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 54s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 34s
branch-2 passed

+1 :green_heart:
compile
1m 46s
branch-2 passed

+1 :green_heart:
shadedjars
4m 40s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  3s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 17s
the patch passed

+1 :green_heart:
compile
1m 46s
the patch passed

+1 :green_heart:
javac
1m 46s
the patch passed

+1 :green_heart:
shadedjars
4m 38s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  2s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-protocol-shaded in the patch passed.

-1 :x:
unit
6m 39s
hbase-client in the patch failed.

-1 :x:
unit
231m 30s
hbase-server in the patch failed.

-1 :x:
unit
7m 50s
hbase-shell in the patch failed.

273m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 724f3d8347d0 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a419b390cf

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-client.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-shell.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/testReport/

Max. process+thread count
4156 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/2/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 18s
branch-2 passed

+1 :green_heart:
compile
4m 11s
branch-2 passed

+1 :green_heart:
checkstyle
1m  4s
branch-2 passed

+1 :green_heart:
spotless
0m 44s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 16s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 52s
the patch passed

+1 :green_heart:
compile
4m  4s
the patch passed

+1 :green_heart:
cc
4m  4s
the patch passed

+1 :green_heart:
javac
4m  4s
the patch passed

-0 :warning:
checkstyle
0m 35s
hbase-server: The patch generated 1 new + 7 unchanged - 0 fixed = 8 total (was 7)

-0 :warning:
rubocop
0m  8s
The patch generated 8 new + 701 unchanged - 3 fixed = 709 total (was 704)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 46s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
hbaseprotoc
1m 28s
the patch passed

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 39s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 30s
The patch does not generate ASF License warnings.

41m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile cc hbaseprotoc prototool rubocop

uname
Linux f3b39c633c58 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 5488acfeaa

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

rubocop
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/artifact/yetus-general-check/output/diff-patch-rubocop.txt

Max. process+thread count
80 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3 rubocop=1.37.1

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  4s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 27s
branch-2 passed

+1 :green_heart:
compile
1m 45s
branch-2 passed

+1 :green_heart:
shadedjars
4m 37s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  3s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 18s
the patch passed

+1 :green_heart:
compile
1m 44s
the patch passed

+1 :green_heart:
javac
1m 44s
the patch passed

+1 :green_heart:
shadedjars
4m 39s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  1s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 29s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
8m  4s
hbase-client in the patch passed.

-1 :x:
unit
230m 23s
hbase-server in the patch failed.

+1 :green_heart:
unit
9m 52s
hbase-shell in the patch passed.

274m 19s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a6ab2979596c 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 5488acfeaa

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/testReport/

Max. process+thread count
4452 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 42s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 58s
branch-2 passed

+1 :green_heart:
compile
2m  3s
branch-2 passed

+1 :green_heart:
shadedjars
5m 15s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  2s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 50s
the patch passed

+1 :green_heart:
compile
2m  2s
the patch passed

+1 :green_heart:
javac
2m  2s
the patch passed

+1 :green_heart:
shadedjars
5m 11s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  6s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 35s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
8m  6s
hbase-client in the patch passed.

-1 :x:
unit
228m 10s
hbase-server in the patch failed.

+1 :green_heart:
unit
8m  3s
hbase-shell in the patch passed.

276m 22s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3debd6bee7e9 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 5488acfeaa

Default Java
Eclipse Adoptium-11.0.17+8

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/testReport/

Max. process+thread count
4418 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/3/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 20s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 59s
branch-2 passed

+1 :green_heart:
compile
5m 18s
branch-2 passed

+1 :green_heart:
checkstyle
1m 50s
branch-2 passed

+1 :green_heart:
spotless
1m  2s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
7m  6s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  8s
the patch passed

+1 :green_heart:
compile
6m 33s
the patch passed

+1 :green_heart:
cc
6m 33s
the patch passed

-0 :warning:
javac
4m  4s
hbase-server generated 1 new + 194 unchanged - 1 fixed = 195 total (was 195)

-0 :warning:
checkstyle
0m 58s
hbase-server: The patch generated 1 new + 7 unchanged - 0 fixed = 8 total (was 7)

-0 :warning:
rubocop
0m 17s
The patch generated 21 new + 728 unchanged - 3 fixed = 749 total (was 731)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
14m 38s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
hbaseprotoc
2m 25s
the patch passed

+1 :green_heart:
spotless
1m  3s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
7m  3s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 48s
The patch does not generate ASF License warnings.

61m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile cc hbaseprotoc prototool rubocop

uname
Linux 516f06d635eb 5.4.0-166-generic #183-Ubuntu SMP Mon Oct 2 11:28:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 97974024a8

Default Java
Eclipse Adoptium-11.0.17+8

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/artifact/yetus-general-check/output/diff-compile-javac-hbase-server.txt

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

rubocop
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/artifact/yetus-general-check/output/diff-patch-rubocop.txt

Max. process+thread count
80 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3 rubocop=1.37.1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 39s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 11s
branch-2 passed

+1 :green_heart:
compile
1m 47s
branch-2 passed

+1 :green_heart:
shadedjars
5m 45s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 57s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 52s
the patch passed

+1 :green_heart:
compile
1m 52s
the patch passed

+1 :green_heart:
javac
1m 52s
the patch passed

+1 :green_heart:
shadedjars
6m 18s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 57s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 31s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
8m 33s
hbase-client in the patch passed.

+1 :green_heart:
unit
213m 55s
hbase-server in the patch passed.

+1 :green_heart:
unit
7m 41s
hbase-shell in the patch passed.

259m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 5ca6b5ffa6c3 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 97974024a8

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/testReport/

Max. process+thread count
4393 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 55s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 58s
branch-2 passed

+1 :green_heart:
compile
1m 57s
branch-2 passed

+1 :green_heart:
shadedjars
5m  5s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  6s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 53s
the patch passed

+1 :green_heart:
compile
2m  9s
the patch passed

+1 :green_heart:
javac
2m  9s
the patch passed

+1 :green_heart:
shadedjars
5m 20s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  8s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 31s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
8m 25s
hbase-client in the patch passed.

-1 :x:
unit
241m 33s
hbase-server in the patch failed.

+1 :green_heart:
unit
8m 10s
hbase-shell in the patch passed.

288m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 6fd72ae33876 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 97974024a8

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/testReport/

Max. process+thread count
4118 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/4/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

@NihalJain can you take a look? The guts of the change is the same, but I had to update much of ErasureCodingUtils to use reflection. The tests have been updated to work in both hadoop3 (verifying the EC management works) and in hadoop2 (verifying we throw an UnsupportedException)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 12s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 13s
branch-2 passed

+1 :green_heart:
compile
4m  5s
branch-2 passed

+1 :green_heart:
checkstyle
1m  4s
branch-2 passed

+1 :green_heart:
spotless
0m 46s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 20s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 54s
the patch passed

+1 :green_heart:
compile
4m  1s
the patch passed

+1 :green_heart:
cc
4m  1s
the patch passed

-0 :warning:
javac
2m 31s
hbase-server generated 1 new + 194 unchanged - 1 fixed = 195 total (was 195)

+1 :green_heart:
checkstyle
1m  1s
the patch passed

-0 :warning:
rubocop
0m 11s
The patch generated 13 new + 728 unchanged - 3 fixed = 741 total (was 731)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 54s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
hbaseprotoc
1m 28s
the patch passed

+1 :green_heart:
spotless
0m 42s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
4m 42s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 32s
The patch does not generate ASF License warnings.

42m  6s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile cc hbaseprotoc prototool rubocop

uname
Linux 07aa66e8002e 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 97974024a8

Default Java
Eclipse Adoptium-11.0.17+8

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/artifact/yetus-general-check/output/diff-compile-javac-hbase-server.txt

rubocop
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/artifact/yetus-general-check/output/diff-patch-rubocop.txt

Max. process+thread count
81 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3 rubocop=1.37.1

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 40s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 50s
branch-2 passed

+1 :green_heart:
compile
2m  3s
branch-2 passed

+1 :green_heart:
shadedjars
5m 14s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  6s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 44s
the patch passed

+1 :green_heart:
compile
2m  1s
the patch passed

+1 :green_heart:
javac
2m  1s
the patch passed

+1 :green_heart:
shadedjars
5m  9s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  6s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 35s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
8m  8s
hbase-client in the patch passed.

+1 :green_heart:
unit
223m 59s
hbase-server in the patch passed.

+1 :green_heart:
unit
8m  0s
hbase-shell in the patch passed.

269m 17s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 6e7d7aaa4815 5.4.0-169-generic #187-Ubuntu SMP Thu Nov 23 14:52:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 97974024a8

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/testReport/

Max. process+thread count
4395 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 15s
branch-2 passed

+1 :green_heart:
compile
1m 46s
branch-2 passed

+1 :green_heart:
shadedjars
4m 38s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 59s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 21s
the patch passed

+1 :green_heart:
compile
1m 47s
the patch passed

+1 :green_heart:
javac
1m 47s
the patch passed

+1 :green_heart:
shadedjars
4m 38s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
1m  1s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
0m 28s
hbase-protocol-shaded in the patch passed.

+1 :green_heart:
unit
7m 59s
hbase-client in the patch passed.

-1 :x:
unit
230m 40s
hbase-server in the patch failed.

+1 :green_heart:
unit
9m 40s
hbase-shell in the patch passed.

274m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5591

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 9678f842e218 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 97974024a8

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/testReport/

Max. process+thread count
4496 (vs. ulimit of 30000)

modules
C: hbase-protocol-shaded hbase-client hbase-server hbase-shell U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5591/5/console

versions
git=2.34.1 maven=3.8.6

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

This message was automatically generated.


Passing data into tests

This is awesome by the way...
I'm successfully running this inside an Express app. My aim is to integrate this into a small local service for testing and retesting various sites.  Some of those sites require u:p credentials to log in.  Although I can hardcode them into the tests (with casper.setHttpAuth()), I'd rather be able to pass these in from the outside.  Possible to do something like '--flowargs=...' or similar?  Essentially, I need to get something user-supplied from the node/Express app req.params into the individual tests... is this possible in the current setup, or a possible enhancement?
Many thanks,
Rob

casperArgs (string[]): optional arguments to pass into casper and PhantomJS, such as --ignore-ssl-errors=true


Stop if process_request/response fails the handshake.

Fix #1419.

Needs a changelog and perhaps tests.

Needs tests for sure because a new code path isn't covered.


mackerel-agent: 0.72.3 -> 0.72.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mackerelio/mackerel-agent/releases.
meta.description for mackerel-agent is: "System monitoring service for mackerel.io"
meta.homepage for mackerel-agent is: "https://github.com/mackerelio/mackerel-agent"
meta.changelog for mackerel-agent is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/2ky9g6kw03h3bgwbn8p80q42khwj45av-mackerel-agent-0.72.5/bin/.mackerel-agent-wrapped passed the binary check.
/nix/store/2ky9g6kw03h3bgwbn8p80q42khwj45av-mackerel-agent-0.72.5/bin/mackerel-agent passed the binary check.
2 of 2 passed binary check by having a zero exit code.
2 of 2 passed binary check by having the new version present in output.
found 0.72.5 with grep in /nix/store/2ky9g6kw03h3bgwbn8p80q42khwj45av-mackerel-agent-0.72.5
found 0.72.5 in filename of file in /nix/store/2ky9g6kw03h3bgwbn8p80q42khwj45av-mackerel-agent-0.72.5

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

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
docbookrx
mackerel-agent

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2ky9g6kw03h3bgwbn8p80q42khwj45av-mackerel-agent-0.72.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2ky9g6kw03h3bgwbn8p80q42khwj45av-mackerel-agent-0.72.5
ls -la /nix/store/2ky9g6kw03h3bgwbn8p80q42khwj45av-mackerel-agent-0.72.5/bin

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

1 package built:

mackerel-agent

Maintainer pings
cc @midchildan @kalbasit for testing.

Upstream is ahead already


ADD strict network policies to all core Anubis services

There are some network policies that are defined in network-policy.yml. These policies are only on the places where users have some level of execution on the Anubis cluster (like the theia pods and autograde pipelines).
We need to add policies to govern other places like the web and api deployments.
Use this tool for visualizing and editing network policies https://editor.cilium.io/

[ ] write network policies

[ ] API
[ ] WEB
[ ] RPC-default
[ ] RPC-theia
[ ] RPC-regrade

hi @wabscale, This issue seems to be a good initiation of my journey towards contribution to FOSS projects.
Can you please assign this to me?

Sure thing you can take this on. GitHub doesnt let me assign an issue to you until you have a commit on the main branch, but consider this yours.
I will write out the network map for you sometime in the next few days. You'll have a much better time with that


make headers optional in http check

Coverage increased (+0.2%) to 88.004% when pulling 3e8b906ccb1b9ea2e54b284d9b76ea43147fea2b on bugfix/optional-headers into 6783113fe0e7ba2a8f4614bf767699e128577f91 on develop.

Coverage increased (+0.2%) to 87.991% when pulling 5860f49bb11e92b5075733d3173e0c0369a8c371 on bugfix/optional-headers into 6783113fe0e7ba2a8f4614bf767699e128577f91 on develop.

Coverage increased (+0.2%) to 87.991% when pulling 5860f49bb11e92b5075733d3173e0c0369a8c371 on bugfix/optional-headers into 6783113fe0e7ba2a8f4614bf767699e128577f91 on develop.

Coverage increased (+0.2%) to 87.991% when pulling 761988966b3340e0487c3a57cc588b8975434aa4 on bugfix/optional-headers into 6783113fe0e7ba2a8f4614bf767699e128577f91 on develop.


xbursttools: add -fcommon workaround

Workaround build failure on -fno-common toolchains like upstream
gcc-10. Otherwise build fails as:
mipsel-unknown-linux-uclibc-ld: boothandler.o:(.bss+0x8): multiple definition of
  `start_addr'; main.o:(.bss+0x8): first defined here

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

xbursttools


GVIDEO not working

Please follow the guide below / Podążaj za przewodnikiem

Put an "x" into all boxes [ ] relevant to your issue (Wstaw "x" w każde pole [ ], które dotyczy twojego zgłoszenia)
Use Preview tab to see how your issue will actually look like (Użyj Perview aby sprawdzić, czy wszystko wygląda dobrze)

Kodi & OS

Kodi verison: _____
OS version: _____

Addon / Wtyczka

[ ] Filmy online - Mrknow
[ ] MrknowTV
[ ] Specto
[ ] FanFILM
Version / Wersja: _____

Issue / Zgłoszenie

[ ] Bug report / Błąd
[ ] Site request / Prośba o nową stronę
[ ] Feature request / Prośba o nową funkcję
[ ] Question / Pytanie
[ ] Other / Inne

Descryption / Opis
Put here every imported thing such logs, how to reproduce etc.
Wstaw tutaj każdą ważna rzecz, taką jak logi, jak wywołać błąd itp.

anyone know why GVIDEO wont work in Specto ?

Today all the sources I have are primewire but it seems disabling the ipv6 of kodi does the trick. At least it did til the gvideo sources disappeared

OK
Today I'll try to fix it

It's working great now thanks a lot appreciate your work
On Jan 28, 2017 4:13 PM, "MrKnow"<EMAIL_ADDRESS>wrote:

OK
Today I'll try to fix it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/737#issuecomment-275871629,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYMmrZgG9br4cu6nhyNn6dUWNPOSo2hCks5rW6FTgaJpZM4Lu9en
.


can i get epicgames worker?

What do you mean?

Can i be epicgames worker?
Kysune<EMAIL_ADDRESS>schrieb am Mi., 22. Apr. 2020, 14:18:

What do you mean?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SzymonLisowiec/node-epicgames-fortnite-client/issues/30#issuecomment-617744178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APISCCF65NZL7BNPWA4BDB3RN3OAPANCNFSM4MODUM6Q
.

This library and me isn't associated with EpicGames company.


Cube drops off Wi-Fi over a period of time

Initial debug seemed to be related to power management, and disconnect would happen within a minute or so of a reboot. WPA3 enablement seem to resolve. Rechecking after 12 hours, cube seems to have disconnected again, at 3:05am (many hours after any direct cube interaction).
Unifi network.

FYI -- saw it again today with current FW. Had it running all day, then tried to access cube. Local -- no go.


[material-ui] Add a Split Pane component

Summary
It would be so great to have MUI-native support for split-pane.
Seems like most libraries out there stopped updating and have many unresolved issues.
Examples
No response
Motivation
I would love to use something like https://github.com/neocturne/react-multi-split-pane built natively into MUI.
Search keywords: split-pane
Search keywords:

Thanks for the request, @MartinXPN! I've added the "Waiting for 👍" label to gauge the community's interest — this helps us prioritize. I do have a hunch, though, that as this is primarily a layout-type component, it would make a bit more sense to be stored in the MUI System product (which Material UI depends on). But we can discuss this later on!

@MartinXPN you could use this - https://react-resizable-panels.vercel.app

I was writing a new issue regarding Resizable Panels and I thankfully came across this, so I'll just add my input here.
This is a component that should definitely be included in the library, because the MD3 documentation does talk about resizeable windows: https://m3.material.io/foundations/layout/understanding-layout/overview
Note that drag handles have their own style that conforms to the look & feel of Material Design 3. It even has its own documentation section (and it should be taken into account when implementing it in Material UI). This is a big reason to have the component in the library and have it properly styled, as opposed to the alternative of using unstyled 3rd party resizeable panes that do not conform their drag handle style to Material Design. Small details such as this are noticeable and it's important to have proper styling all throughout the front end.
An example of a library that does provide its own resizeable panel component is shadcn: https://ui.shadcn.com/docs/components/resizable
Screenshots from the documentation:

There are more, but you get the idea.


struck at trying to create path /mesos in zookeeper

Hi,
I am running elasticsearch-mesos on playa-mesos vagrant vm. I have mesos master and slave running. When I try to run ./elasticsearch-mesos I am getting a message
I0107 12:18:33.608325  4570 group.cpp:385] Trying to create path '/mesos' in ZooKeeper
Then after waiting for a long time I am getting a time out message. Also elasticsearch is not listed under frameworks of mesos webUI.

👍

Did you ever find out how to resolve this? Currently stuck at this error too.


Add full Caddyfile examples for Google Auth and Multiple Hosts

+1 this would be super helpful. I'm literally doing the same thing, thanks!

@rspier , please updated this PR to match new syntax. The relevant documentation is here: https://github.com/greenpau/caddy-auth-portal#secure-prometheus and https://github.com/greenpau/caddy-auth-portal#shortcuts
However, please consider reviewing JWT plugin syntax too: https://github.com/greenpau/caddy-auth-jwt#plugin-syntax

Updated, sorry it took so long, July was a busy month.
The new syntax is definitely cleaner and simpler than the previous one.
It's a bit confusing how things are split between the two modules -- I understand why, but it requires a bit more knowledge to use properly.  Hopefully the example helps people.  It took a little bit of time to get things right, I had some expectations about how the syntax that would work that were totally wrong.

@rspier , please see Makefile for “make docs”. I do not update README.md directly.

Done.  Updated assets/docs/pages/... and ran make docs

Everything should now be tabified.  (And vscode is configured to show tabs now... that's what I get for not using my emacs config.)

Rebased against main.

@rspier , please rebase to a single commit and follow contributing.md for commit message.
additionally, instead of “else.example.com”, please use foo/bar/baz keywords for hosts, and admin/editor/viewer for roles.
also, please see @francislavoie comments.
E.g. the default router is just “route”, not “route *”

I'd addressed @francislavoie earlier, but never resolved the comment.  Commits updated.  I need to check something about the CLA signing and will get back to you soon.

@rspier , apologies! 😄 need one more change. Replace “jwt” with “authorize” directive. Renamed the plugin a few days ago. It is now “caddy-authorize”.

jwt -> authorize complete.

@rspier , migrated to https://authp.github.io/
Please re-submit PR there.
The Google OAuth is over here: https://authp.github.io/docs/authenticate/oauth/backend-oauth2-0002-google