Secure hadoop integration with hue as proxyuser

Description
Hello!
I am working on integrating Hue with SecureHadoop as a ProxyUser.
I found that the behavior of ProxyUser in WebHDFS FileBrowser needs to be enhanced.
When "security_enabled" is true, only "read_url" method use delegation token.
I want to modify the code
so that a user who has been impersonated from Hue(a proxy user) can issue a Delegation Token when using WebHDFS.

Hi @SoniaComp, thanks for reaching out. :-)
Since Hue is open source you can clone the Hue repo and modify the code. If you want to share your changes and get them merged into the next Hue release you can create a PR with your changes.
See
https://github.com/cloudera/hue/blob/master/CONTRIBUTING
https://docs.gethue.com/developer/development/


[Dropdown] Add new feature Read-only (Disabled) dropdown input

[Dropdown] Add new feature Read-only (Disabled) dropdown input

oh sorry.. i just try:
$('.ui.selection.dropdown').dropdown();
$('.ui.selection.dropdown').addClass('disabled');
$('.ui.selection.dropdown').addClass('read-only');

it's work 👍

disabled class is making everything in dropdown greyish and hard to read. While read-only on other components is just blocking edition. How to make dropdown read-only?

Hi @panzupa, do you have SUI installed in your project, or do you use it from a CDN?

@Banandrew I have it installed. My workaround solution is to assign disabled class and set style opacity: 100. Works very well I guess :-)

@panzupa Ah, I just wanted to say that you could override the .disabled class via the source, but you already figured it out. 👍

nice tips! thanks @panzupa @Banandrew 👍


docs: fix update_service.md

PR summary

PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

:tada: This PR is included in version 0.39.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Device won't get kicked out

Checklist for submitting an issue to KickThemOut:

[x] I have carefully read the README file and haven't managed to resolve my issue.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] I am running the latest version of KickThemOut.

Hello,
I'm sorry that I can't give you information like the kernel version now because I'm not at home.
I have an Raspberry pi 3 B+ and I flashed the newest Kali version on it.
I've installed the kickthemout script and did the steps from the README.txt.
I tried to kick my mobile phone out of my home network and the script also detected everything.
My problem is that "spoofing started" was there for about 40 minutes but it didn't kicked my phone out.
Do you know what I could do?
Sorry for my bad English, it isn't my native language.
Thanks in advance
M1st3rN0Nam3

Hi there @M1st3rN0Nam3. Please have a look at my final response to issue #310. Thanks!

Hi there @M1st3rN0Nam3. Please have a look at my final response to issue #310. Thanks!

Thank you very much!
I'm sorry haven't seen that one :)


Suhiswap masterchef subgraph is dead

URL: https://thegraph.com/hosted-service/subgraph/sushiswap/master-chef

@NBFinanceTech Use this one: https://thegraph.com/hosted-service/subgraph/jiro-ono/masterchef-staging
That prod one above died, and don't think we'll be pushing a fix up for it since the mainnet subgraphs are gonna be sunset within a month or so.

Thx


Billing Address must have a Correct Format

Issue Description
When we check the Admin end where we check the sales details, there when we check the details of Billing Address which we found slightly unsystematic in order.
Bagisto Version

[ ] master branch
[ ] 1.3.3

Steps To Reproduce

Go to admin -> Sales -> Orders -> Actions
Now look at the invoice.
Check the address details. These details are not as required.

Actual Result

Expected Result
No abbreviations must be allowed at the state and city-related concerns.
The correct format must be :

NAME  2. Place or City 3. District 4. State 5. PIN Code 6. Country

The address format really depends on the country / area https://en.wikipedia.org/wiki/Address#Format_by_country_and_area
if we really want to optimize / change this, then i would like to suggest to make it possible to change the format from the admin panel instead of having to manually edit all the blade files

We will discuss this during a meeting and provide feedback.

Right @devansh-webkul @ghermans

@devansh-webkul, we had a meeting regarding this and agreed that the admin should have an option in the admin panel to configure the addresss format.


Add AAD authentication options to 'az network vnet-gateway'

Add feature requested in https://github.com/Azure/azure-cli/issues/10481

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

@MyronFanQiu  please help review.

@MyronFanQiu please help review.

@yonzhan Pending on service bug. No need to merge now, have to discuss implementation detail further based on service bug.

/azp run


Support spaces under asset names

It looks like it was an actual CR bug, closed in this PR: https://github.com/robocorp/robocloud-logic/pull/3695

Re-opening it as it improves testing. And I'll also make sure the + sign works with the way CR unquotes the URL, but I'll strip away from the PR any unnecessary refactoring.


Add python version that use elastalert

Please add in README.md python version that Elastalert use

Yes looks like so, but I'm start look at README.md file, yes I think it's my fault


Cors error from React Native App

Getting a ResultCode 009999 with following code from React Native App:
      MP.cardRegistration.init({
        cardRegistrationURL: response.CardRegistrationURL,
        preregistrationData: response.PreregistrationData,
        accessKey: response.AccessKey,
        Id: response.Id
      });

      var cardData = {
        cardNumber: "4706750000000017",
        cardExpirationDate: "0317",
        cardCvx: "123",
        cardType: "CB_VISA_MASTERCARD"
      };

      MP.cardRegistration.registerCard(
        cardData,
        function(res) {
            // Success, you can use res.CardId now that points to registered card
            console.log(res)
        },
        function(res) {
          console.log(res)
            // Handle error, see res.ResultCode and res.ResultMessage
        }
      );

Also I  use the same headers for all requests:
      headers : {
        'Content-Type' : 'application/json; charset=utf-8',
        'Authorization': `Basic ${hash}`
      },

I've also tried to POST via Axios lib but I get a 09101 error (these errors only happen with this request)
Any way to solve or workaround this issue?
See attached IMG with response from PreRegistrationData request.

Hey @abeauvois - you talk about an "attached IMG" but I don't see it - could you try uploading it again please?

Hi Hugo,
here is the devTool screenshot.
Alexandre
On Thu, Aug 4, 2016 at 6:09 PM, Hugo Bailey<EMAIL_ADDRESS>wrote:

Hey @abeauvois https://github.com/abeauvois - you talk about an
"attached IMG" but I don't see it - could you try uploading it again please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Mangopay/cardregistration-js-kit/issues/24#issuecomment-237601827,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAS4eLZS4MBq8UKVeGxE-_RVxIZ6-3qdks5qcg62gaJpZM4Jb_H2
.

Still no screenshot I'm afraid :-/

Curious because it was sent with attachment on my side.
Is it attached this time ?
---------- Forwarded message ----------
From: Alexandre Beauvois<EMAIL_ADDRESS>Date: Thu, Aug 4, 2016 at 6:39 PM
Subject: Re: [Mangopay/cardregistration-js-kit] Cors error from React
Native App (#24)
To: Mangopay/cardregistration-js-kit <
<EMAIL_ADDRESS>
Cc: Mangopay/cardregistration-js-kit <
<EMAIL_ADDRESS>Mention <
<EMAIL_ADDRESS>Hi Hugo,
here is the devTool screenshot.
Alexandre
On Thu, Aug 4, 2016 at 6:09 PM, Hugo Bailey<EMAIL_ADDRESS>wrote:

Hey @abeauvois https://github.com/abeauvois - you talk about an
"attached IMG" but I don't see it - could you try uploading it again please?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Mangopay/cardregistration-js-kit/issues/24#issuecomment-237601827,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAS4eLZS4MBq8UKVeGxE-_RVxIZ6-3qdks5qcg62gaJpZM4Jb_H2
.

No - please can you use the Github interface instead of sending it via email. Or alternatively email it to<EMAIL_ADDRESS>

Here it is:

OK, thank you. And could you confirm whether it happens during the POST creation of the card registration, or the later PUT update with the RegistrationData?

After I've created correctly the cardregistration and got the AccessKey and so on.
When I send the MP.cardRegistration.registerCard with CardData, I get the error.

OK, so the 2nd step (POSTing the data to the CardRegistrationURL) works correctly, and you receive back the "data=xxxxxx"?

Here is the request that fails:
      const formData = {
        data: response.PreregistrationData,
        accessKeyRef: response.AccessKey,
        cardNumber: "4706750000000017", //cardNumber)
        cardExpirationDate: "0217", //cardExpirationDate)
        cardCvx: "123", //cardCvx)
      }

      return this.request('post', {url: response.CardRegistrationURL}, formData)

Hi @abeauvois, coming back to this, it seems that our check for CORS support is incorrectly failing for React Native app (because it's based on a browser parameter which doesn't exist for React).

The security model for XMLHttpRequest is different than on web as there is no concept of CORS in native apps.

(Source)
We're going to look into this to see if there is a way to detect React apps, and therefore better handle this.

sounds good, I'm sure this will help many future react-native developers, thanks for your efficient support.

I came across the same problem and have dealt with it like this:
corsSupport: function() {

    // Test if runtime is React Native
    if (window.navigator.product === 'ReactNative') {
        return true;
    }

    // IE 10 and above, Firefox, Chrome, Opera etc.
    if ("withCredentials" in new XMLHttpRequest()) {
        return true;
    }

    // IE 8 and IE 9
    if (window.XDomainRequest) {
        return true;
    }

    return false;

}

window.navigator.product will return 'Gecko' for all other browsers. One disadvantage of this is that the product property is deprecated, so I'm not sure how long ReactNative will support it for.

Thanks @willmcneilly very much for the suggestion - that seems a very sensible approach.
We've discussed internally the fact that its deprecated, and they (the React Native team) added this navigator.product property specifically to make it possible to detect React Native run time in 3rd party JS libraries (like in this case) as discussed here and added here.
The other solution would be to remove the CORS check altogether and let it fail if it’s really not supported. With the legacy browser share dropping every year, perhaps we don’t need to try to detect the lack of CORS support in advance (and risking a false alert). The check is there only to give a specific error code. If we remove the check, the call will fail anyway with some less clear error message but only for very old browsers.

Mangopay React and React Native First JS Client library with card registration workflow.
https://www.npmjs.com/package/mangopay-client-react


Don't report unused diagnostics when the unused node has a parse error

Fixes #25591

Waiting for @mjbvz to verify

@andy-ms I'm still see the diagnostics when using the TS version from this PR, at least for the cases in #25591

Here's what it looks like to me:
typescript@next:

jake local on the noSuggestionDiagnosticsOnParseError branch:

@andy-ms You're right. I ran the wrong build command. Seems to be working well. I haven't notice any flickering or other odd behavior in my testing


fix: random meme generator play was breaking due to broken api url

Description
Random meme generator play was breaking due to broken API url.
Type of change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@murtuzaalisurti Please create an issue for it and attach.

@atapas yep, sure

fixes #1151

@atapas linked the issue, you can merge it now!


obsolete dependency github.com/mtrmac/gpgme

Libpod depends on github.com/mtrmac/gpgme which is an obsolete (unmaintained) fork of github.com/proglottis/gpgme.
Please consider using the original project -- https://github.com/proglottis/gpgme

@mtrmac PTAL

This was historically forked to avoid bringing in too recent GPG symbols, which broke builds on RHEL [67].
I’m keeping an eye on the upstream from time to time, there is AFAICS nothing (definitely no feature, and no bug fix that I can see) that we would get by updating.
Sure, ideally the fork should be dropped if/when the older GPGME versions are no longer a concern. This may already be the case. There’s no urgency to it that I can see; am I missing anything?

I don't know how urgent this problem is. Probably there is no emergency.
Obsolete fork must be dropped not to gain features but for hygiene and life cycle (support) purposes.
Needless forking is harmful. Suppose you've found a problem in the library -- where would you report a bug? mtrmac doesn't even have the issue tracker. Development of this library is clearly happens in one place and that's why only the original repository should be used (instead of a fork).
It is just common sense...

@mtrmac Any update on this issue?

No

@lsm5 is that something you could look into?
You could create a branch that replaces github.com/mtrmac/gpgme with github.com/proglottis/gpgme and build that in different RHELs.
Are we still support consumers of c/image in RHEL 6?

No we don't support any container code on RHEL6.   If we can get this built on RHEL7, then we should be fine.

Actually, I misremember — RHEL 6 was never a concern.
RHEL 7 was, though, and it ships with GPGMe 1.3.2, so we still need the extra commits in mtrmac/gpgme.
Meanwhile, there is a single bug fix in the upstream version (the rest is new functions we don’t call), and that bug fix is in a function we don’t call.
So, I’m still not all that inclined to rebase the commits, set up a RHEL 7 testing machine to ensure the result still builds, and possibly extend the revert commits on the private branch, for precisely zero benefit.

@mtrmac, I haven't checked the commits in the fork but is there any chance we could get them upstream?

See https://github.com/proglottis/gpgme/issues/6 .

@github-actions, I object to automatic closure. Even when the issue can not be fixed promptly it is still a valid issue and it does not hurt to keep it opened until it can be addressed.
Auto-closing issues is a bad practice.

@onlyjob, we configured it that way on purpose.

@onlyjob We have configured this to give us a wakeup and to attempt to rediagnose the issue.  As the issue list becomes longer and longer, we loose the signal overtime.  At least this causes us to revisit issues every 30 days and hopefully close some if they are fixed, or update the priority.


client/beefy: small code improvements

Following up with some improvements suggested in https://github.com/paritytech/substrate/pull/12124#pullrequestreview-1129442989

Thank you!


Establish a convention that plugins do not take construction arguments

Instead, I suggest keeping all necessary information in databases, like I did with cfg in #2589.
This eases reasoning on plugin construction.
For example, I have now idea how could I gather construction parameters from Scarb in an elegant way.
Additionally, test runner now uses get_default_plugins, because it can so.

Stack:

#2590 ⬅
#2589
#2588

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

@mkaput This works for our own plugins, but what about user plugins? They cannot modify the DB. What if they want to have configuration to their plugins?


Segmentation fault (core dumped)

Hi,
I am currently facing this issue on ubuntu 16.04, when i try to stream from multiple RTSP sources using Gstreamer kinesis_video_gstreamer_sample_multistream_app.
it works fine and i can see streams from sources in AWS kinesis console, when i run this app
AWS_ACCESS_KEY_ID=------- AWS_SECRET_ACCESS_KEY=----------- ./kinesis_video_gstreamer_sample_multistream_app MyRtspStreams rtspurlsfile
but after 5 mins process exists with the error message below.
[ERROR] [15-05-2020 09:28:48:137.398 GMT] postReadCallback(): Failed to get data from the stream with an error: 0x30000004
[WARN ] [15-05-2020 09:28:48:138.928 GMT] curlCompleteSync(): HTTP Error 408 : Response: (null)
Request URL: https://s-1e415f8b.kinesisvideo.us-east-1.amazonaws.com/putMedia
[DEBUG] [15-05-2020 09:28:48:139.027 GMT] putStreamCurlHandler(): Network thread for Kinesis Video stream: MyRtspStreams_0 with upload handle: 57 exited. http status: 408
[WARN ] [15-05-2020 09:28:48:139.480 GMT] putStreamCurlHandler(): Stream with streamHandle 10923184 has exited without triggering end-of-stream. Service call result: 408
[INFO ] [15-05-2020 09:28:48:139.536 GMT] kinesisVideoStreamTerminated(): Stream 0xa6acb0 terminated upload handle 57 with service call result 408.
[DEBUG] [15-05-2020 09:28:48:139.645 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
[DEBUG] [15-05-2020 09:28:48:139.729 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
[DEBUG] [15-05-2020 09:28:48:139.761 GMT] streamReadyHandler invoked
[DEBUG] [15-05-2020 09:28:48:139.810 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
[INFO ] [15-05-2020 09:28:48:139.937 GMT] putStreamResultEvent(): Put stream result event. New upload handle 60
[DEBUG] [15-05-2020 09:28:48:150.090 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
[INFO ] [15-05-2020 09:28:48:368.844 GMT] writeHeaderCallback(): RequestId: e731570f-28ff-ed37-b009-341a7846f367
[ERROR] [15-05-2020 09:28:48:369.083 GMT] postReadCallback(): Failed to get data from the stream with an error: 0x30000004
[WARN ] [15-05-2020 09:28:48:370.528 GMT] curlCompleteSync(): HTTP Error 408 : Response: (null)
Request URL: https://s-1e415f8b.kinesisvideo.us-east-1.amazonaws.com/putMedia
[DEBUG] [15-05-2020 09:28:48:370.582 GMT] putStreamCurlHandler(): Network thread for Kinesis Video stream: MyRtspStreams_0 with upload handle: 58 exited. http status: 408
[WARN ] [15-05-2020 09:28:48:370.713 GMT] putStreamCurlHandler(): Stream with streamHandle 10923184 has exited without triggering end-of-stream. Service call result: 408
[INFO ] [15-05-2020 09:28:48:370.738 GMT] kinesisVideoStreamTerminated(): Stream 0xa6acb0 terminated upload handle 58 with service call result 408.
[DEBUG] [15-05-2020 09:28:48:370.755 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
[DEBUG] [15-05-2020 09:28:48:370.806 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
[DEBUG] [15-05-2020 09:28:48:370.826 GMT] streamReadyHandler invoked
[DEBUG] [15-05-2020 09:28:48:370.874 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
[INFO ] [15-05-2020 09:28:48:370.947 GMT] putStreamResultEvent(): Put stream result event. New upload handle 61
[DEBUG] [15-05-2020 09:28:48:381.076 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
[INFO ] [15-05-2020 09:28:48:794.762 GMT] writeHeaderCallback(): RequestId: c79248bf-eb95-cb90-90aa-2baa2d1e99aa
[ERROR] [15-05-2020 09:28:48:794.842 GMT] postReadCallback(): Failed to get data from the stream with an error: 0x30000004
[WARN ] [15-05-2020 09:28:48:796.207 GMT] curlCompleteSync(): HTTP Error 408 : Response: (null)
Request URL: https://s-1e415f8b.kinesisvideo.us-east-1.amazonaws.com/putMedia
[DEBUG] [15-05-2020 09:28:48:796.265 GMT] putStreamCurlHandler(): Network thread for Kinesis Video stream: MyRtspStreams_1 with upload handle: 59 exited. http status: 408
[WARN ] [15-05-2020 09:28:48:796.424 GMT] putStreamCurlHandler(): Stream with streamHandle 10923192 has exited without triggering end-of-stream. Service call result: 408
[INFO ] [15-05-2020 09:28:48:796.469 GMT] kinesisVideoStreamTerminated(): Stream 0xa6acb8 terminated upload handle 59 with service call result 408.
[DEBUG] [15-05-2020 09:28:48:796.581 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
[DEBUG] [15-05-2020 09:28:48:802.966 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
[DEBUG] [15-05-2020 09:28:48:803.267 GMT] streamReadyHandler invoked
[DEBUG] [15-05-2020 09:28:48:803.316 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
[INFO ] [15-05-2020 09:28:48:803.412 GMT] putStreamResultEvent(): Put stream result event. New upload handle 62
[DEBUG] [15-05-2020 09:28:48:813.915 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
[INFO ] [15-05-2020 09:28:49:364.484 GMT] writeHeaderCallback(): RequestId: c20a7da9-d637-9d9a-9532-1ebf86e2d074
[ERROR] [15-05-2020 09:28:49:364.564 GMT] postReadCallback(): Failed to get data from the stream with an error: 0x30000004
[WARN ] [15-05-2020 09:28:49:365.713 GMT] curlCompleteSync(): HTTP Error 408 : Response: (null)
Request URL: https://s-1e415f8b.kinesisvideo.us-east-1.amazonaws.com/putMedia
[DEBUG] [15-05-2020 09:28:49:365.777 GMT] putStreamCurlHandler(): Network thread for Kinesis Video stream: MyRtspStreams_0 with upload handle: 60 exited. http status: 408
[WARN ] [15-05-2020 09:28:49:365.869 GMT] putStreamCurlHandler(): Stream with streamHandle 10923184 has exited without triggering end-of-stream. Service call result: 408
[INFO ] [15-05-2020 09:28:49:365.894 GMT] kinesisVideoStreamTerminated(): Stream 0xa6acb0 terminated upload handle 60 with service call result 408.
[DEBUG] [15-05-2020 09:28:49:365.912 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
[DEBUG] [15-05-2020 09:28:49:365.958 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000200, Next state: 0x0000000000000040
[DEBUG] [15-05-2020 09:28:49:365.980 GMT] streamReadyHandler invoked
[DEBUG] [15-05-2020 09:28:49:366.022 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000040, Next state: 0x0000000000000080
[INFO ] [15-05-2020 09:28:49:366.091 GMT] putStreamResultEvent(): Put stream result event. New upload handle 63
[DEBUG] [15-05-2020 09:28:49:377.148 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000080, Next state: 0x0000000000000100
[INFO ] [15-05-2020 09:28:49:668.169 GMT] writeHeaderCallback(): RequestId: fd1a5d0a-859a-eee8-aa22-3e1c4311bcd2
[ERROR] [15-05-2020 09:28:49:668.274 GMT] postReadCallback(): Failed to get data from the stream with an error: 0x30000004
[WARN ] [15-05-2020 09:28:49:669.290 GMT] curlCompleteSync(): HTTP Error 408 : Response: (null)
Request URL: https://s-1e415f8b.kinesisvideo.us-east-1.amazonaws.com/putMedia
[DEBUG] [15-05-2020 09:28:49:669.350 GMT] putStreamCurlHandler(): Network thread for Kinesis Video stream: MyRtspStreams_0 with upload handle: 61 exited. http status: 408
[WARN ] [15-05-2020 09:28:49:669.468 GMT] putStreamCurlHandler(): Stream with streamHandle 10923184 has exited without triggering end-of-stream. Service call result: 408
[INFO ] [15-05-2020 09:28:49:669.490 GMT] kinesisVideoStreamTerminated(): Stream 0xa6acb0 terminated upload handle 61 with service call result 408.
Segmentation fault (core dumped)

@usmanm259 It's not possible to tell what's going on with the short log you've attached. In this case the error 0x30000004 is a likely a consequence of bad data that was produced in earlier. Later, it seems that you hit network timeout 408.
Also, there is no information about the crash.
Recommend:

Using a single RTSP stream for now
Include detailed DEBUG logs
Include core dumps for the crash so we can tell what's going on

@MushMal Thanks for the reply.

Using a single RTSP stream:

I have tried the Gstreamer app for single RTSP stream but same response.

Include detailed DEBUG logs

Attaching detailed DEBUG logs
logs.txt

@MushMal Thanks for the reply.

Using a single RTSP stream:

I have tried the Gstreamer app for single RTSP stream but same response.

Include detailed DEBUG logs

Attaching detailed DEBUG logs
logs.txt

Your logs indicate that at times you have n observed bandwidth of 25Mbps but it’s not actually sufficient for the density of your stream. You get into a pogo-stick effect with the default latency handlers trying to reset the connection and eventually starting to drop frames.
Try configuring the rtsp source to have lower bitrate.

@MushMal Thanks, i will test with lower bitrate and let you know.

Hi,
So i tested with lower constant bitrate (CBR) (640 kbps) with Stream control configured on camera's sub stream, i successfully ingested stream to kinesis video streams for longer duration (9 hours).
After 9 hours there was some network issue which caused the application to drop stream, so once the network issue was gone and camera was  accessible with ping but the issue was that Gstreamer application was unable to stream again, was stuck in loop and trying again and again for hours.
When i killed the process and started application again, once again i was able to stream to kinesis.
So, if there is anything that can be done to make it work, when there is a network issue and after its gone, then application continues automatically streaming again.

The SDK default configuration is to retry. It seems that’s why it was trying to do. Could you please include the debug logs when it we “stuck”? If you are using KVS plugin with GStreamer rtsp plugin then there could be a number of things that might be wrong including the network link to the rtsp source

Resolving due to no further correspondence. Please re-open or cut a new issue if you need further assistance.

Hi @MushMal,
Sorry for not responding, i was testing streams with gstreamer kvs_gstreamer_multistream_sample app for longer duration.
The sample gstreamer app worked for more than 1 week continuously.
The issue that i am facing is that, when there is a network problem the gstreamer app stops streaming to kinesis video streams and gsteamer app is still running without exiting process.
When network problem is resolved, gstreamer app should continue with streaming from cameras but currently app gets stuck at the state, after restarting app, it again starts streaming.
I am running the app with linux systemd service, so the service status shows app is running for 4 days but when i check logs, app is stuck.
so my question is how can i resolve this issue, If the kvs_gstreamer_multistream_sample

After network issue is gone, App should continue with streaming from cameras but currently it gets stuck and no new logs are produced to check the status of app.

OR

App Doesn't exit process on failure then how can i restart linux systemd service on failure when app is still running at stuck state without streaming to kinesis.

Debug Logs
[DEBUG] [03-06-2020 12:44:02:022.915 GMT] fragmentAckReceivedHandler invoked
[ERROR] [03-06-2020 12:44:02:022.950 GMT] getKinesisVideoStreamData(): operation returned status code: 0x5200002f
[DEBUG] [03-06-2020 12:44:02:022.961 GMT] postReadCallback(): Wrote 6583 bytes to Kinesis Video. Upload stream handle: 190
[ERROR] [03-06-2020 12:44:02:023.019 GMT] getKinesisVideoStreamData(): operation returned status code: 0x5200002f
[DEBUG] [03-06-2020 12:44:02:023.030 GMT] postReadCallback(): Pausing CURL read for upload handle: 190
[DEBUG] [03-06-2020 12:44:02:915.284 GMT] Kinesis Video client and stream metrics
>> Overall storage byte size: 134217728
>> Available storage byte size: 134046901
>> Allocated storage byte size: 170827
>> Total view allocation byte size: 144080
>> Total streams frame rate (fps): 18
>> Total streams transfer rate (bps): 661696 (646 Kbps)
>> Current view duration (ms): 759
>> Overall view duration (ms): 1999
>> Current view byte size: 73800
>> Overall view byte size: 169339
>> Current frame rate (fps): 18.5827
>> Current transfer rate (bps): 661696 (646 Kbps)
[DEBUG] [03-06-2020 12:44:03:024.208 GMT] postReadCallback(): Wrote 65524 bytes to Kinesis Video. Upload stream handle: 190
[ERROR] [03-06-2020 12:44:03:025.025 GMT] getKinesisVideoStreamData(): operation returned status code: 0x5200002f
[DEBUG] [03-06-2020 12:44:03:025.055 GMT] postReadCallback(): Wrote 10721 bytes to Kinesis Video. Upload stream handle: 190
[ERROR] [03-06-2020 12:44:03:025.100 GMT] getKinesisVideoStreamData(): operation returned status code: 0x5200002f
[DEBUG] [03-06-2020 12:44:03:025.113 GMT] postReadCallback(): Pausing CURL read for upload handle: 190
[DEBUG] [03-06-2020 12:44:03:485.094 GMT] postWriteCallback(): Curl post body write function for stream with handle: MyRtspStream_0 and upload handle: 190 returned: {"EventType":"RECEIVED","FragmentTimec$
[DEBUG] [03-06-2020 12:44:03:485.191 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [03-06-2020 12:44:03:490.203 GMT] postWriteCallback(): Curl post body write function for stream with handle: MyRtspStream_0 and upload handle: 190 returned: {"EventType":"BUFFERING","FragmentTime$
[DEBUG] [03-06-2020 12:44:03:490.246 GMT] fragmentAckReceivedHandler invoked
[DEBUG] [03-06-2020 12:44:03:553.755 GMT] postWriteCallback(): Curl post body write function for stream with handle: MyRtspStream_0 and upload handle: 190 returned: {"EventType":"PERSISTED","FragmentTime$
[DEBUG] [03-06-2020 12:44:03:564.010 GMT] fragmentAckReceivedHandler invoked
[ERROR] [03-06-2020 12:44:03:564.073 GMT] getKinesisVideoStreamData(): operation returned status code: 0x5200002f
[DEBUG] [03-06-2020 12:44:03:564.084 GMT] postReadCallback(): Pausing CURL read for upload handle: 190
[WARN ] [03-06-2020 12:44:39:620.940 GMT] curlCompleteSync(): curl perform failed for url https://s-171c51c7.kinesisvideo.us-east-2.amazonaws.com/putMedia with result Timeout was reached: Operation too s$
[WARN ] [03-06-2020 12:44:39:621.264 GMT] curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-171c51c7.kinesisvideo.us-east-2.amazonaws.com/putMedia
Request Headers:
[DEBUG] [03-06-2020 12:44:39:621.335 GMT] putStreamCurlHandler(): Network thread for Kinesis Video stream: MyRtspStream_0 with upload handle: 190 exited. http status: 0
[WARN ] [03-06-2020 12:44:39:621.531 GMT] putStreamCurlHandler(): Stream with streamHandle 37746056 has exited without triggering end-of-stream. Service call result: 599
[INFO ] [03-06-2020 12:44:39:621.565 GMT] kinesisVideoStreamTerminated(): Stream 0x23ff588 terminated upload handle 190 with service call result 599.
[DEBUG] [03-06-2020 12:44:39:621.588 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200

@usmanm259 not sure what's going on with your case as I don't have any logs. From the snippet of the code it looks like the SDK is continuously retrying and is getting a timeout for PutMedia so there is no networking.
Generally speaking, the sample application will use continuous retry policy. This means that the SDK will just continue retrying to send the buffer. Even when the frames are dropped. The default logic will attempt to reset the connection as it hits the buffer pressures but in your case it won't help as you don't have network at all so eventually the frames will start dropping. The default continuous retry policy will also reset the stream (dump the buffer and retry) when we get any errors.
Your application can listen to the callbacks (like dropped frame, buffer pressure or error) and react accordingly.

@MushMal I agree with you but the issue is if application has continuous retry policy then why it starts working as soon as i restart the application and if i don't restart the app and wait for it to start streaming again then it just doesn't do that.
As you can see these logs are of June 3, 2020 ,the stream stopped after app produced these logs and i restart the app on June 4, 2020 , waited for the app to retry streaming but no success.
[DEBUG] [03-06-2020 12:44:03:564.010 GMT] fragmentAckReceivedHandler invoked
[ERROR] [03-06-2020 12:44:03:564.073 GMT] getKinesisVideoStreamData(): operation returned status code: 0x5200002f
[DEBUG] [03-06-2020 12:44:03:564.084 GMT] postReadCallback(): Pausing CURL read for upload handle: 190
[WARN ] [03-06-2020 12:44:39:620.940 GMT] curlCompleteSync(): curl perform failed for url https://s-171c51c7.kinesisvideo.us-east-2.amazonaws.com/putMedia with result Timeout was reached: Operation too s$
[WARN ] [03-06-2020 12:44:39:621.264 GMT] curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-171c51c7.kinesisvideo.us-east-2.amazonaws.com/putMedia
Request Headers:
[DEBUG] [03-06-2020 12:44:39:621.335 GMT] putStreamCurlHandler(): Network thread for Kinesis Video stream: MyRtspStream_0 with upload handle: 190 exited. http status: 0
[WARN ] [03-06-2020 12:44:39:621.531 GMT] putStreamCurlHandler(): Stream with streamHandle 37746056 has exited without triggering end-of-stream. Service call result: 599
[INFO ] [03-06-2020 12:44:39:621.565 GMT] kinesisVideoStreamTerminated(): Stream 0x23ff588 terminated upload handle 190 with service call result 599.
[DEBUG] [03-06-2020 12:44:39:621.588 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200

These are the logs of June 4, 2020,
WARN ] [04-06-2020 10:00:20:512.382 GMT] curlCompleteSync(): curl perform failed for url https://s-171c51c7.kinesisvideo.us-east-2.amazonaws.com/putMedia with result Timeout was reached: Operation too slow. Less than 30 bytes/sec transferred the last 30 seconds
[WARN ] [04-06-2020 10:00:20:513.040 GMT] curlCompleteSync(): HTTP Error 0 : Response: (null)
Request URL: https://s-171c51c7.kinesisvideo.us-east-2.amazonaws.com/putMedia
Request Headers:
[DEBUG] [04-06-2020 10:00:20:513.056 GMT] putStreamCurlHandler(): Network thread for Kinesis Video stream: MyRtspStream_0 with upload handle: 6 exited. http status: 0
[WARN ] [04-06-2020 10:00:20:513.212 GMT] putStreamCurlHandler(): Stream with streamHandle 29480328 has exited without triggering end-of-stream. Service call result: 599
[INFO ] [04-06-2020 10:00:20:513.233 GMT] kinesisVideoStreamTerminated(): Stream 0x1c1d588 terminated upload handle 6 with service call result 599.
[DEBUG] [04-06-2020 10:00:20:513.257 GMT] stepStateMachine(): State Machine - Current state: 0x0000000000000100, Next state: 0x0000000000000200
If there is network issue and the stream entered this state, why it is resolved by restarting app and not by retry policy

@usmanm259 It really comes down to libCurl timing out. If I were to guess, there is something wrong with the OS network stack/sockets. Try to troubleshoot your system by checking the available memory, opened sockets perhaps.
Recommend building debug version of libCurl, capture any output when this happens, open an issue with libCurl GitHub repository perhaps they can give better answers


Table layout

What is being submitted?

Is it a component, pattern, standard, or update?
describe the component, pattern, standard, or update you are proposing.

Why are you submitting?

What evidence do you have that it’s needed by multiple services across government?
What evidence do you have that it meets the needs of the users of those services?
Have you checked that it doesn’t already exist in the DIO Design System?

Examples, links, and research

Include examples, links, and research that will help clarify and support your proposal.

Considerations
Considerations

Buttons- inline(action buttons), “add new” line items
Status (incomplete, in-progress, denied…etc)
Read/Edit mode (Dropdown, Text…. etc)
Collapsable/ Expandable (Accordion)
Sub-sections

Anything else

Add any other context or screenshots about the feature request here.

Linnea, Ashifa & Graeme are working on this one!


Search Bar keyboard popup issue on Android

I've noticed an issue with the keyboard popping up when using the TabView on Android. It seems to happen on pages either side of the Search page and its the same issue as mentioned in this post: https://github.com/NativeScript/NativeScript/issues/6160. This is a Nativescript Angular project though.

Hi @marklanhamhc,
Thank you for cantacting us.
I would suggest keeping the conversation on an issue https://github.com/NativeScript/NativeScript/issues/6160 . You can add your comment on it if you would like to provide some additional info. Also, you can check the provided solution - https://github.com/NativeScript/NativeScript/issues/6160#issuecomment-412778200.


Adjust showing/validating address on Send fund

Disallow inputting general substrate address, all address input must be in its correct form relative to the chain

Note:
After send transaction, can remove receiver or sender account to check additional case

Version test:
Please check issues:

[ ] Update format Recent address/Address in the screens

Address book
"Send to" input field

[ ] Bug do not select image when change token

Version test: http://<IP_ADDRESS>:8900/s/mo93sf6nLmkimCR
Validation in cases:

Send token - single chain (check input - confirmation - history)

Select account in wallet
Input Substrate address
Input Network address
Input public key
Select Recent address
Select Saved contact
Scan QR code

Send token - cross chain (check input - confirmation - history)

Select account in wallet
Input Substrate address
Input Network address
Input public key
Select Recent address
Select Saved contact
Scan QR code

Send NFT (check input - confirmation - history)

Select account in wallet
Input Substrate address
Input Network address
Input public key
Select Recent address
Select Saved contact
Scan QR code


feat: Add mock for MessageClient interface

This allows the client to be mocked in unit tests that depend on the client
Signed-off-by: Leonard Goodell<EMAIL_ADDRESS>

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/go-mod-messaging/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?) N/A
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?) N/A
[ ] I have opened a PR for the related docs change (if not, why?) N/A

Testing Instructions
N/A
New Dependency Instructions (If applicable)
N/A

Codecov Report

Merging #135 (4e7dc27) into main (9cef39b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #135   +/-   ##
=======================================
  Coverage   82.37%   82.37%
=======================================
  Files          14       14
  Lines         539      539
=======================================
  Hits          444      444
  Misses         75       75
  Partials       20       20

Continue to review full report at Codecov.

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


ObjectclassViolationError

Hi,
great library, but seems that adding an element like :
var entry = {
objectClass: 'posixAccount',
objectClass: 'top',
objectClass: 'inetOrgPerson',
objectClass: 'mailUser',
objectClass: 'shadowAccount',
objectClass: 'sambaSamAccount',
...
};
ldapClient.add('uid=myuser,ou=Users,ou=example.comt,dc=support', entry, function(error) { ...
produces an "ObjectclassViolationError: no structural object class provided". Adding the same element with ldapadd works, and adding a "simple user" (without samba, mail and shadow support) works perfectly using the library.  I'm using Openldap server v. 2.4.23.   Thanks again, it works.


nginx example: Secret echoserver/echoserver-tls does not exists

Hi hello, I've followed this example on minikube. Checking the log of nginx-ingress-controller pod it's saying:
W0718 07:24:54.649166       1 controller.go:932] Secret echoserver/echoserver-tls does not exists

I think I've missed to create the secret object echoserver/echoserver-tls But I don't see it mentioned somewhere in the README. Do you have any suggestion ?

OK it has more clues when I check the log of kube-lego pod:
time="2017-07-18T07:52:55Z" level=info msg="process certificate requests for ingresses" context=kubelego
time="2017-07-18T07:52:55Z" level=info msg="Attempting to create new secret" context=secret name=echoserver-tls namespace=echoserver
time="2017-07-18T07:52:55Z" level=info msg="no cert associated with ingress" context="ingress_tls" name=echoserver namespace=echoserver
time="2017-07-18T07:52:55Z" level=info msg="requesting certificate for echo.example.com" context="ingress_tls" name=echoserver namespace=echoserver
time="2017-07-18T07:54:24Z" level=warning msg="authorization failed after 1m0s: reachability test failed: Get http://echo.example.com/.well-known/acme-challenge/_selftest: dial tcp: lookup echo.example.com on <IP_ADDRESS>:53: no such host" context=acme domain=echo.example.com
time="2017-07-18T07:54:24Z" level=error msg="Error while processing certificate requests: no domain could be authorized successfully" context=kubelego
time="2017-07-18T07:54:24Z" level=info msg="ignoring as has no annotation 'kubernetes.io/tls-acme'" context=ingress name=kube-lego-nginx namespace=kube-lego

It seems like the kube-lego controller can't reach echoserver app via echo.example.com URL

Hi there
What domain are you trying to obtain a certificate for, and is it pointed at your ingress controller?
tcp: lookup echo.example.com on <IP_ADDRESS>:53: no such host indicates that whatever domain you are using is not actually configured with DNS.
Have you changed the domain to obtain a certificate from echo.example.com to one of your own domains? (sorry to state the obvious if you have already!)

@munnerz Thanks for the response. Yeah I haven't configured any domain yet. I just tried kube-lego by running the example on minikube. Now if I understand correctly from the log of kube-lego pod, it needs to connect to http://echo.example.com/.well-known/acme-challenge/_selftest. Which target should I point echo.example.com to ? echoserver ?

@ngtuna How are they supposed to reach echo.example.com running on your local machine?


Update features descriptions on the landing page

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:
/area documentation

What this PR does / why we need it:
For consistency of the new messaging
Special notes for your reviewer:
Doesn't fix but related to #1003

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: aijamalnk, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Enhancements

Adds more reusable approach to serde
Allows API tokens to be assigned as connection admins

Superceded by #230


Show renamed names instead of "cryptic" ones in Integrations

Is your feature request related to a problem? Please describe.
I started using Meross LAN "in production" 🥰 and this is what I see in Integrations page:

But I already renamed that device to:

Describe the solution you'd like
I would really love to see "Presa studio (via LAN)" instead of "mss310r<PHONE_NUMBER>1046908074...".

Hehe,
well..doable..but in logic terms it would not be correct since the integration itself is a different concept than the device or even the entities it carries: it's just a configuration container.
Of course, in meross_lan we always (not really sure) have 1 integration <-> 1 device so the mapping could be always 'deterministic' but I'm not really motivated to enforce that because, like I said, they're two different concepts (and also because retrieving and updating the integration entry name might be easier said than done)
At any rate, you can edit it manually from the integration(s) UI  ;)

I fully understand 😃


Shank spacing documentation U-Tube

Hey,
when setting up a U-Tube, the documentation in DoubleUTube.py (or SingleUTube.py) is unclear to me.
What does this mean? :
D_s : float
Distance of the pipe until center [m]
I assume, that here the so-called shank spacing has to be entered.
This could be described as the distance between in- and outlet pipe, measured from center to center.
Is this meant by Distance of the pipe until center [m]? Entering only the distance from the pipe center to the borehole center leads to results that seem wrong to me.
Many thanks in advance,
Paul

Dear @p-klebo ,
D_s is exactly that: the distance from one pipe until the center, so its half of the shank spacing as you defined it.
What are the results that seem wrong to you?
Best,
Wouter

Dear @wouterpeere,
thanks for the response! I have set up the Example 4 from the EED-Tutorials in the GHETool. If I enter the shank spacing in D_s, GHETool gives a depth of 127 m (EED-Example is 120 m).
If I set D_s = half the shank spacing, GHETool gives 195 m.
I also compared GHETool to the GHEDesigner for some scenarios. It results in the same picture. The results do match for D_s = shank spacing quite well.
Not for D_s = half the shank spacing, in this case GHETool obviously suggest much deeper depths.
Best,
Paul

Dear @p-klebo
Can you perhaps attach the GHEtool document you created. I think something is wrong in your values ...
I entered all the values for the Rb* and I get 0.0741 mK/W (idem EED, see page 20 of the pdf document), when using half the shank spacing.

For using EED data for GHEtool projects, you can read this article on the topic: https://manual.ghetool.eu/en/latest/sources/tutorial/EED_to_GHEtool.html

Hey @wouterpeere,
many thanks for the response and the screenshot! It helped me to find, that my mass flow value was wrong!
Now, I get the same Rb* as in the EED-Tutorials. Btw, I've made a typing error, I have set up Example 5, not Example 4. But that doesn't matter...
Best regards, Paul

Hey @p-klebo !
Glad you found your problem!
I'll close this issue now!
Best,
@wouterpeere


I want display multiple cluster images based on markers data

Hi all,
I want to display cluster images based on marker data on the cluster, able to update the cluster image but it applies to all the clusters. Please see the bellow screenshot.

If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@VijaykumarPalakurthi Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

👍


Improve log messages on resident group validations

Improve log messages - details on the specific problematic key

Codecov Report

Merging #1274 (afb3a06) into master (fa7b943) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master    #1274   +/-   ##
=========================================
  Coverage     99.52%   99.52%
  Complexity     3291     3291
=========================================
  Files           502      502
  Lines          9939     9941    +2
  Branches        494      492    -2
=========================================
+ Hits           9892     9894    +2
  Misses            5        5
  Partials         42       42

Flag
Coverage Δ
Complexity Δ

unittests
99.52% <100.00%> (+<0.01%)
3291.00 <3.00> (ø)

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

Impacted Files
Coverage Δ
Complexity Δ

...tessera/privacygroup/ResidentGroupHandlerImpl.java
100.00% <100.00%> (ø)
10.00 <3.00> (ø)

Continue to review full report at Codecov.

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


libsrm: init at 0-unstable-2020-11-05

Description of changes
Fixes https://github.com/NixOS/nixpkgs/issues/297259

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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

[x] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/2050

Honestly I forget why I packaged it.


TypeScript imports

I'm trying to use BigNumber version 4.0.2 in a TypeScript program. I've created a stripped down example of a simple Node.js program written in TypeScript that uses BigNumber for this issue
https://github.com/naddison36/node-imports
I'm really struggling to get TypeScript 2.3.4 to pull in the type definitions for BigNumber. Does anyone know how to do this? Here's what I've tried https://github.com/naddison36/node-imports#attempts-to-get-the-bignumber-type-definitions-to-work
Ideally I'd like to simply run npm install bignumber.js --save, npm install @types/bignumber.js --save, us ES6 imports like import BigNumber from 'bignumber.js' and have TypeScript just work.
Any help would be appreciated
Nick

The following Stack Overflow question has a solution which is to change the Type Definition from a namespace to a module. https://stackoverflow.com/questions/44605322/typescript-type-definitions-for-bignumber
This worked well for my Node.js program but not sure of the impacts on browser side code.

I don't know enough about TypeScript definitions to help on this.
There are some other definitions at typed bignumber.js. See #97 for further discussion.
I'm thinking I should link to your comprehensive example from the README so other users, including myself, can quickly find out how to use this library with TypeScript.

@naddison36 please check out the definitions published in the latest version of bignumber. You can now import with import {BigNumber} from 'bignumber.js' or import BigNumber from 'bignumber.js'


make discovery base URL configurable

According to #3
Add three env for init leader detection and server peer communication etc.

DISCOVERY_ROOT_URL : default https://discovery.etcd.io
DISCOVERY_ORIGIN_ADDR : default http://<IP_ADDRESS>:4001
DISCOVERY_INIT_LEADER : default <IP_ADDRESS>:4001

I am going to make the root URL configurable. I think that the discovery service should run on a machine with a proxy or etcd running for now.
Thank you for the pull request though.


signal-hook-tokio Windows build broken?

I created a crate that's basically empty and depends on signal-hook and signal-hook-tokio:
https://github.com/davepacheco/signal-hook-windows-test/blob/main/Cargo.toml
I have GitHub Actions configured to build this on Ubuntu, Windows, and MacOS.  The Ubuntu one works, but the Windows one failed.  (The MacOS one was aborted because of the Windows failure.)  I've only tested this once here, but I see the same behavior in a bigger crate that uses these crates.
The error is here:
   Compiling signal-hook-tokio v0.3.0
     Running `rustc --crate-name signal_hook_tokio --edition=2018 C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg "feature=\"futures-core-0_3\"" --cfg "feature=\"futures-v0_3\"" -C metadata=3c6a7814b531fa0a -C extra-filename=-3c6a7814b531fa0a --out-dir D:\a\signal-hook-windows-test\signal-hook-windows-test\target\debug\deps -L dependency=D:\a\signal-hook-windows-test\signal-hook-windows-test\target\debug\deps --extern futures_core_0_3=D:\a\signal-hook-windows-test\signal-hook-windows-test\target\debug\deps\libfutures_core-a1626673b76c3bb9.rmeta --extern libc=D:\a\signal-hook-windows-test\signal-hook-windows-test\target\debug\deps\liblibc-aeda11fed0a8c75b.rmeta --extern signal_hook=D:\a\signal-hook-windows-test\signal-hook-windows-test\target\debug\deps\libsignal_hook-ac6b3a1d0c81f434.rmeta --extern tokio=D:\a\signal-hook-windows-test\signal-hook-windows-test\target\debug\deps\libtokio-a1fd3de27efaed30.rmeta --cap-lints allow`
error[E0433]: failed to resolve: could not find `iterator` in `signal_hook`
  --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:81:22
   |
81 | pub use signal_hook::iterator::backend::Handle;
   |                      ^^^^^^^^ could not find `iterator` in `signal_hook`

error[E0433]: failed to resolve: could not find `iterator` in `signal_hook`
  --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:82:18
   |
82 | use signal_hook::iterator::backend::{OwningSignalIterator, PollResult, SignalDelivery};
   |                  ^^^^^^^^ could not find `iterator` in `signal_hook`

error[E0433]: failed to resolve: could not find `iterator` in `signal_hook`
  --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:83:18
   |
83 | use signal_hook::iterator::exfiltrator::{Exfiltrator, SignalOnly};
   |                  ^^^^^^^^ could not find `iterator` in `signal_hook`

error[E0432]: unresolved import `tokio::net::UnixStream`
  --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:79:5
   |
79 | use tokio::net::UnixStream;
   |     ^^^^^^^^^^^^^^^^^^^^^^ no `UnixStream` in `net`

error[E0433]: failed to resolve: use of undeclared type `SignalDelivery`
   --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:115:21
    |
115 |         let inner = SignalDelivery::with_pipe(read, write, exfiltrator, signals)?;
    |                     ^^^^^^^^^^^^^^ use of undeclared type `SignalDelivery`

error[E0433]: failed to resolve: use of undeclared type `OwningSignalIterator`
   --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:116:17
    |
116 |         Ok(Self(OwningSignalIterator::new(inner)))
    |                 ^^^^^^^^^^^^^^^^^^^^ use of undeclared type `OwningSignalIterator`

error[E0433]: failed to resolve: use of undeclared type `PollResult`
   --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:153:13
    |
153 |             PollResult::Signal(sig) => Poll::Ready(Some(sig)),
    |             ^^^^^^^^^^ use of undeclared type `PollResult`

error[E0433]: failed to resolve: use of undeclared type `PollResult`
   --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:154:13
    |
154 |             PollResult::Closed => Poll::Ready(None),
    |             ^^^^^^^^^^ use of undeclared type `PollResult`

error[E0433]: failed to resolve: use of undeclared type `PollResult`
   --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:155:13
    |
155 |             PollResult::Pending => Poll::Pending,
    |             ^^^^^^^^^^ use of undeclared type `PollResult`

error[E0433]: failed to resolve: use of undeclared type `PollResult`
   --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:156:13
    |
156 |             PollResult::Err(error) => panic!("Unexpected error: {}", error),
    |             ^^^^^^^^^^ use of undeclared type `PollResult`

error[E0405]: cannot find trait `Exfiltrator` in this scope
  --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:92:27
   |
92 | pub struct SignalsInfo<E: Exfiltrator = SignalOnly>(OwningSignalIterator<UnixStream, E>);
   |                           ^^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `SignalOnly` in this scope
  --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:92:41
   |
92 | pub struct SignalsInfo<E: Exfiltrator = SignalOnly>(OwningSignalIterator<UnixStream, E>);
   |                                         ^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `OwningSignalIterator` in this scope
  --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:92:53
   |
92 | pub struct SignalsInfo<E: Exfiltrator = SignalOnly>(OwningSignalIterator<UnixStream, E>);
   |                                                     ^^^^^^^^^^^^^^^^^^^^ not found in this scope

error[E0405]: cannot find trait `Exfiltrator` in this scope
  --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:94:9
   |
94 | impl<E: Exfiltrator> SignalsInfo<E> {
   |         ^^^^^^^^^^^ not found in this scope

error[E0412]: cannot find type `Handle` in this scope
   --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:123:29
    |
123 |     pub fn handle(&self) -> Handle {
    |                             ^^^^^^ not found in this scope

error[E0412]: cannot find type `SignalOnly` in this scope
   --> C:\Users\runneradmin\.cargo\registry\src\github.com-1ecc6299db9ec823\signal-hook-tokio-0.3.0\src\lib.rs:132:32
    |
132 | pub type Signals = SignalsInfo<SignalOnly>;
    |                 -              ^^^^^^^^^^ not found in this scope
    |                 |
    |                 help: you might be missing a type parameter: `<SignalOnly>`

error: aborting due to 16 previous errors

Windows is kind of a secondary platform, since its support of signals is very limited. Parts of the crate are not available there as a result. You can turn these parts off by default-features = false and picking only the things you need.
You're right that it probably should build with the defaults and just have them unavailable there. I'll get around to fixing that eventually, but probably not right now. I'd suggest you use the workaround above in the meantime, but if you want to get involved and fix it, I'll be happy for a PR.
Thanks for reporting it.

No problem.  I understand it's best-effort.  My use case is very simple so I wound up using the ctrlc crate for now.

I'm looking into it right now. The signal-hook with default features builds OK on windows (well, with some warnings about unused imports, but :shrug:). But the signal-hook-tokio depends on the iterator feature and that one isn't ported to windows, so signal-hook-tokio is incompatible with windows.
I admit the error should be a bit better though, but I don't see a good way how to do it :-|.

https://github.com/helix-editor/helix/pull/464/checks?check_run_id=3093468552
We also get that on iterator, I think a workaround is remove signal-hook-tokio for windows.

Tokio now has a cross-platform ctrl-c signal handler, for those looking for a basic graceful shutdown feature: https://docs.rs/tokio/1.34.0/tokio/signal/fn.ctrl_c.html


STATUS change only on ground

[ ] I have read the README.md file and visited the Documentation to see if the information there helps.

Action description
sending messages when gpio connected to 3.3v
Previous attempts
if i connect ground to the gpio pin i get mqtt messges with on and off paylod.
but if i connect 3.3v (like the sensor iam using is doing it) i don't get a change.
Error messages and traceback
Paste any error messages and Python traceback if applicable.

Config
mqtt:
  host: *********
  port: 1883
  topic_prefix: octoPrint
gpio_modules:
  - name: raspberrypi
    module: raspberrypi
    cleanup: no
digital_inputs:
  - name: filament_l
    module: raspberrypi
    pin: 14
    on_payload: "ON"
    off_payload: "OFF"
    pullup: yes
    pulldown: no
  - name: filament_r
    module: raspberrypi
    pin: 27
    on_payload: "ON"
    off_payload: "OFF"
    pullup: yes
    pulldown: no

Hardware

Platform: Raspberry Pi
Connected hardware:  bigtreetech filament sensor

System:

OS: raspian with octoprint
Python version: 3.7.3
User you're running as: pi
Using a virtualenv?: no

Additional context
Add any other context about the problem here.

obsolete


Superagi

closing this seems like @incomeonpassive  accidentally opened this issue
if you have an issue please give explanation, logs etc.


Adding appveyor.yml for CI

appveyor.yml contains instructions to build and test Vipr.
Updating the build status badge in Readme.md

Sridhar, looks like this was blocked by AppVeyor. It looks like we have a task that is failing to complete. Can you take a look?

It seems one of the ProxyExtensions tests is timing out in the appveyor environment. I will take a look.

Jenkens CI system has been setup for Vipr. So this is no longer required.


Messages to a group

It would be an very nice feature if the adapter could send a message to a group not just a single phone number.
regards
Stefan

Hi Stefan,
at the moment, the CallMeBot API don't allow this. But I'm creating a workaround for that.


Updated validations.py.

Applied validation : Username must start with alphabet
Closes: #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Team 6 boss room spawner milestone #1 )  Implement the initial boss room spawner with basic functionality like a normal room

Implemented boss room spawner class which currently works like the main room spawner however only spawns 1 animal.. Will need to be extended later in the sprint to spawn animals based on the level in the game.

Converted to refactory mode and merged into #149


fix(backup): add sws pocket identifier when sending and retrieving backup

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


Doesn't load correctly

When loading in cmd it says that it was failed to inject so Fix it please

I think the game got updated thats why it doesn't work

its for me too

the game updated be patient


burpsuite - Failed to load module "canberra-gtk-module" and bump version to 2023.10

Describe the bug
I tried to run nix-shell -p burpsuite and, after the installation, on the shell, when I run burpsuite, I get:
Sep 05, 2023 11:17:06 PM java.util.prefs.FileSystemPreferences$1 run
INFO: Created user preferences directory.
Gtk-Message: 21:17:06.882: Failed to load module "canberra-gtk-module"
Gtk-Message: 21:17:06.883: Failed to load module "canberra-gtk-module"
Could not start Burp: java.lang.Error: Cannot load com.sun.java.swing.plaf.gtk.GTKLookAndFeel

Furthermore, please bump version to 2023.10.
Steps To Reproduce
Steps to reproduce the behavior:

nix-shell -p burpsuite
burpsuite

Expected behavior
Burpsuite running correctly.
Notify maintainers
@bennofs @stepech

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.4.12-zen1-1-zen, Athena OS, noversion, rolling`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - nixpkgs: `/home/athena/.nix-defexpr/channels/nixpkgs`

I'm getting the same error. Since I'm on Ubuntu 20.04, I tried running nixGLIntel burpsuite and it still fails.

I got a little further by installing libcanberra-gtk3 and running GTK_PATH=/nix/store/...-libcanberra-0.30/lib/gtk-3.0 burpsuite

I got a little further by installing libcanberra-gtk3 and running GTK_PATH=/nix/store/...-libcanberra-0.30/lib/gtk-3.0 burpsuite

Is it working?

Still fails to start.


Add thruster as dependency or mention it in README

I wanted to give it a try in a project that does not use thruster (yet) and it did not work out of the box.
I have followed README and rspec started to throw errors with scary stack trace at me. When I added the debug option, I got a simple bundler error that no thrust is installed and resolved the issue. However, that was not obvious to me at first.
I know this is a skill issue, but I probably won't be the only one to do it 🤷
My suggestion is to either add thruster as a runtime dependency (which I expected) or add a line in the README.
PS. Thank you for the gem!
Here is a stack error
#<Thread:0x0000000128a35ce0 /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/server.rb:76 run> terminated with exception (report_on_exception is true):
/Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `initialize': Address already in use - bind(2) for "<IP_ADDRESS>" port 61005 (Errno::EADDRINUSE)
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `new'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `add_tcp_listener'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:163:in `block in parse'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:146:in `each'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:146:in `parse'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/registrations/servers.rb:63:in `block (2 levels) in <main>'
        from <internal:kernel>:90:in `tap'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/registrations/servers.rb:62:in `block in <main>'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-thruster-0.1.0/lib/capybara/thruster.rb:24:in `block in <main>'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/config.rb:64:in `block in server='
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/server.rb:77:in `block in boot'
#<Thread:0x0000000128adc108 /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/server.rb:76 run> terminated with exception (report_on_exception is true):
/Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `initialize': Address already in use - bind(2) for "<IP_ADDRESS>" port 61005 (Errno::EADDRINUSE)
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `new'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `add_tcp_listener'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:163:in `block in parse'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:146:in `each'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:146:in `parse'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/registrations/servers.rb:63:in `block (2 levels) in <main>'
        from <internal:kernel>:90:in `tap'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/registrations/servers.rb:62:in `block in <main>'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-thruster-0.1.0/lib/capybara/thruster.rb:24:in `block in <main>'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/config.rb:64:in `block in server='
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/server.rb:77:in `block in boot'
F#<Thread:0x0000000128a93bd8 /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/server.rb:76 run> terminated with exception (report_on_exception is true):
/Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `initialize': Address already in use - bind(2) for "<IP_ADDRESS>" port 61005 (Errno::EADDRINUSE)
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `new'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `add_tcp_listener'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:163:in `block in parse'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:146:in `each'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:146:in `parse'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/registrations/servers.rb:63:in `block (2 levels) in <main>'
        from <internal:kernel>:90:in `tap'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/registrations/servers.rb:62:in `block in <main>'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-thruster-0.1.0/lib/capybara/thruster.rb:24:in `block in <main>'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/config.rb:64:in `block in server='
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/server.rb:77:in `block in boot'
#<Thread:0x0000000128b175a0 /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/server.rb:76 run> terminated with exception (report_on_exception is true):
/Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `initialize': Address already in use - bind(2) for "<IP_ADDRESS>" port 61005 (Errno::EADDRINUSE)
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `new'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:334:in `add_tcp_listener'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:163:in `block in parse'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:146:in `each'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/puma-6.4.2/lib/puma/binder.rb:146:in `parse'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/registrations/servers.rb:63:in `block (2 levels) in <main>'
        from <internal:kernel>:90:in `tap'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/registrations/servers.rb:62:in `block in <main>'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-thruster-0.1.0/lib/capybara/thruster.rb:24:in `block in <main>'
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/config.rb:64:in `block in server='
        from /Users/cezary/.rbenv/versions/3.2.3/lib/ruby/gems/3.2.0/gems/capybara-3.40.0/lib/capybara/server.rb:77:in `block in boot'

1st Try error in ./spec/features/multi_location_order_spec.rb:66:
Address already in use - bind(2) for "<IP_ADDRESS>" port 61005
undefined method `values_at' for nil:NilClass

Yeah, agreed - I just started trying this project this morning too, and hit the same issue.

Thanks for the report!
We cannot add truster as a dependency, 'cause the gem is assumed to be used with alternative thrust implementations, too (it's actually extracted from AnyCable Thruster). But we definitely need to handle the lack of thrust gracefully.


PR: Fix kite error when args in signature is None

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[ ] Included a screenshot or animation (if affecting the UI, see Licecap)

Add an if statement for checking that the arguments in the signature are not None
Issue(s) Resolved

Fixes #10352
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: Steff456

Looks good could you add a test for this to avoid regressions?

Looks good could you add a test for this to avoid regressions?

I think we are not able to create a test for this because we don't have tests for kite completions yet.

Hmm true then this is good to merge


Pictures in Twitter feeds are not shown in TinyTinyRSS

I am using RSS-Bridge for generating user-feeds from Twitter. These feeds are imported in TinyTinyRSS.
The problem is, that pictures in these feeds are not displayed at all in TinyTinyRSS. So I contacted the developer of TinyTinyRSS. In short he said that the feed, generated by RSS-Bridge, is bad:
in your feed enclosures both have wrong content type (application/octet-stream) and lead to a retarded URI which fails the check because of the suffix. so, in short, that feed is bad and whoever produced it should feel bad. my advice would be telling people at “rss bridge” to fix it.
The full conversation can be found here. There are also examples and more informations.
I did some workarounds in TwitterBridge.php and I can live with the result for now. But anyway, this is just quick-and-dirty as I am not a PHP-developer.
Maybe you can have a look at the problem? This would be very appreciated! Thank you in advance!

I did some workarounds in TwitterBridge.php
this is just quick-and-dirty as I am not a PHP-developer.

Just post these workarounds. If you resolved issue, share it in this thread for us to fix it. Nobody will throw rocks to you.

Basically it was all about removing the :thumb or :orig, additionally to *.jpg.
I changed in line 243:
$item['enclosures'] = array($image . ':orig');
to
$item['enclosures'] = array($image);
Changes in line 243:

to

Changes in line 249:
src="{$image}:thumb" />
to
src="{$image}" />
The same changes have to be done after line 280 again ("add embedded image to content").
So all the images are named as *.jpg now, not named as *.jpg:orig or *.jpg:thumb.
TinyTinyRSS is working with these changes; pictures in the feeds are not broken anymore (at least when using the Android-App, which is a frontend to the server-based TinyTinyRSS).
As I said: This is very quick-and-dirty, I am not a PHP-developer and for sure this looks really bad and ugly to you. Sorry for this. Anyway, I needed a quick solution and at least I get things working with these changes ;-)

Cross post: https://github.com/RSS-Bridge/rss-bridge/issues/812#issuecomment-444940310
My answer: https://github.com/RSS-Bridge/rss-bridge/issues/812#issuecomment-445306784

Basically it was all about removing the :thumb or :orig, additionally to *.jpg.

Those parameters are specified by Twitter in order to retrieve different sizes of the same image. Embedding the originally sized image in the feed looks garbage in some feed readers (i.e. they don't scale well).

The problem is, that pictures in these feeds are not displayed at all in TinyTinyRSS.

I'm not sure why this is a problem on your feeds. It works fine on my machines (using Android and iOS Apps as well as Firefox). That being said, my server runs an older release of tt-rss (commit 0cd4a88dc2e0dc0e9a155ad8e7714f9fc7d4a481)

So, I updated my instance to current master and it looks fine to me. What am I missing?
@ontheair81 Can you share a screen shot of what is wrong with your feed?

To simplify things, I am not using my "workarounded" version of RSS-Bridge, but https://bridge.suumitsu.eu/.
As an example, I will generate a feed from Twitter from the user "memes". Please note: I am using the TwitterBridge with "by username", not by keyword, hashtag or list.
So I am getting this feed URL: https://bridge.suumitsu.eu/?action=display&bridge=Twitter&u=memes&format=Atom
My browser shows the feed correct; the picture shown is *.jpg:thumb, linking to the full-res image *.jpg:orig:

In TT-RSS the feed is shown like this with an broken *.jpg:thumb:

In the App, no pictures at all are shown in the article list. All other feeds (when not using RSS-Bridge) are showing pictures in the article list:

When clicking to a tweet, then - and only then - the *.jpg:thumb is shown:

Now lets use my "workarounded" version of TwitterBridge.php. The pictires will be shown much bigger due to the changes:

The view in web-based TT-RSS is still the same (broken like above), but now the images are shown correctly in the list view of the app (which is most important to me):

This is exactly like it should be (in my opinion), so I am happy for now with my quick-and-dirty workaround ;-) Obviously its not nice that the images are still broken in the web-based view in TT-RSS.
I really dont have a clue, why this is working fine for you but not for me. Here are the activated (user-)plugins of TT-RSS; maybe there is a difference to your TT-RSS?

Thank you for the feedback and the detailed informations!

One more clue, do you have tracking protection enabled on your instance of tt-rss by any chance?

Thats it! Disabling tracking protection for tt-rss fixed things for the browser view. Thats great!
So there is just one problem left: The view in tt-rss via the app in Android.

Then again, my mobile phone has no issues whatsoever.

Your picture shows the content when clicking on an article, right? Could you please show a screenshot from the list view?
As you can see here, pictures are shown correct when clicking the article:

But still there are no images shown in the list view of the Twitter-feed (working fine in all other feeds):

How does it looks like in your list?

How do you get previews in the App?
This is my list (different feed, but they all look the same anyway):

How do you get previews in the App?

I am using the original App of tt-rss from the same developer (https://play.google.com/store/apps/details?id=org.fox.ttrss). On Android 7.1.2 with latest security patches.
There are picture previews in the list view of every single feed I am using, except in the Twitter-feed generated by RSS-Bridge. For example, here are some feeds with previews in list view:

All feeds from flickr.com
All feeds from tumblr.com
androidauthority.com
tagesschau.de (german news)
heise.de (german IT news)
golem.de (german IT news)
rfa.org (radio free asia)
and many more

This is my list (different feed, but they all look the same anyway)

Your screenshot looks very different. Maybe you are not using the original tt-rss-App by Andrew Dolgov but a clone or third-party-App instead?

Your screenshot looks very different. Maybe you are not using the original tt-rss-App by Andrew Dolgov but a clone or third-party-App instead?

Yes, I'm using https://play.google.com/store/apps/details?id=org.ttrssreader
which is a fork developed on GitHub: https://github.com/nilsbraden/ttrss-reader-fork

There are picture previews in the list view of every single feed I am using, except in the Twitter-feed generated by RSS-Bridge.

I see. Since the Twitter URIs are valid RFC 2396 and RFC 3986 URIs, something must be wrong with either caching or loading image files.
You also said that the images are displayed correctly in the article, just not in the preview. That is a strong indicator for some mistake in the App preview.
So...
Since I was interested in looking at an Android app anyway, here are my findings:
Here is the code they use to figure out media elements in an article: https://git.tt-rss.org/fox/tt-rss-android/src/master/org.fox.ttrss/src/main/java/org/fox/ttrss/types/Article.java#L69-L158
They also consider images with incorrect content type, which is why your article view works.
The image caching also looks good to me. Actually, images are stored on disk in encoded (MD5) form, so colons are no problem, even on Windows machines: https://git.tt-rss.org/fox/tt-rss-android/src/master/org.fox.ttrss/src/main/java/org/fox/ttrss/util/ImageCacheService.java#L91-L109
If I'm correct, the HeadlineFragment is responsible for displaying your missing images, but it looks fine to me (at least the small section of this long file): https://git.tt-rss.org/fox/tt-rss-android/src/master/org.fox.ttrss/src/main/java/org/fox/ttrss/HeadlinesFragment.java#L1133-L1416
The only thing I could come up with, is the possibility that Glide doesn't handle colons correctly (which I highly doubt, as it is a core library for Android Apps - and a quick search was not sucessful): https://git.tt-rss.org/fox/tt-rss-android/src/master/org.fox.ttrss/src/main/java/org/fox/ttrss/HeadlinesFragment.java#L1241-L1242
I suppose articles are working because they are embedded as HTML, which uses a different method for loading images (possibly): https://git.tt-rss.org/fox/tt-rss-android/src/master/org.fox.ttrss/src/main/java/org/fox/ttrss/ArticleFragment.java#L427-L550
Anyway, if the developers have no solution for this and we don't want to embed large images in all Twitter feeds, we could always add an option to disable image scaling in the feed. It is not a fix because it requires manual labor (activate a checkbox) on your end, but it's still better than broken feeds, right?

I am impressed by the lot work you are doing by checking this App! Thats highly appreciated.

we could always add an option to disable image scaling in the feed. It is not a fix because it requires manual labor (activate a checkbox) on your end, but it's still better than broken feeds, right?

This sounds like a good solution. It is better than broken feeds and better than my workaround ;-)

Fix added to master (see above commit). Let me know if it works for you.

Just tried and: It works perfect! Thank you very much for your effort!

Thanks for the feedback!


list index out of range

I am facing this error when converting an onnx model using ConvertModel function:
/usr/local/lib/python3.7/dist-packages/onnx2pytorch/convert/operations.py in convert_operations(onnx_graph, opset_version, batch_dim, enable_pruning)
    157
    158                 # check if next node Add to add bias
--> 159                 next_node = onnx_graph.node[i + 1]
    160                 next_params = [
    161                     weights[par_name]

IndexError: list index (74) out of range

my code:
onnx_model = onnx.load(load_model_path)
torch_model = ConvertModel(onnx_model)

There's a fix for this that's still in PR: #28 . Hopefully we'll have it merged in shortly, but until then you can use the code in that fork.


Fix for typo in class definition

 [Airbrake] uninitialized constant Clever::PreviousContact Did you mean?  Clever::PreviousStudent


Modify error list in Register Measurements dialog

Is your feature request related to a problem? Please describe.
The errors in the measurement registration dialog are not specific and don't help the user to recognise the issue.
Describe the solution you'd like
The errors should follow a common format:
Column header of the column containing the error : The error message. Solution suggesting an example of correct input.
For e.g.,QBiC Sample ID : Unknown sample with sample ID "Test". QBiC Sample ID should be in the format Q98KK007A1.
The error list must be a scrollable list after it exceeds a maximum of 4 entries.
Increase the dialog size to increase the spacing and readability of the information.
Additional context
#DM1178
Example: Users edit without measurementId -> for every measurement there is an error no measurement id found. It would be better to see a list of errors "measurement column missing" or "measurement  not found"

This is actually not trivial, since we currently don't distinguish between editing and registering measurements while parsing the header content. I'd suggest to work on this once the excel based upload is implemented
(https://github.com/qbicsoftware/data-manager-app/issues/677), since IMO we should completely distuingish between editing and registering measurements before the validation is even triggered

 <property name>:<reason for the failure>:<example or solution>


Tutorial adding command

Codecov Report

Merging #3 (78bc176) into master (1cc4863) will increase coverage by 0.46%.
The diff coverage is 78.04%.

@@             Coverage Diff              @@
##             master       #3      +/-   ##
============================================
+ Coverage     72.15%   72.62%   +0.46%
- Complexity      399      421      +22
============================================
  Files            70       73       +3
  Lines          1232     1293      +61
  Branches        125      131       +6
============================================
+ Hits            889      939      +50
- Misses          311      321      +10
- Partials         32       33       +1

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/seedu/address/ui/PersonCard.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
18.18% <7.14%> (-1.82%)
2.00 <1.00> (+1.00)
:arrow_down:

...c/main/java/seedu/address/model/person/Remark.java
75.00% <75.00%> (ø)
4.00 <4.00> (?)

...eedu/address/logic/parser/RemarkCommandParser.java
77.77% <77.77%> (ø)
2.00 <2.00> (?)

...java/seedu/address/logic/commands/EditCommand.java
97.05% <100.00%> (+0.04%)
12.00 <0.00> (ø)

...va/seedu/address/logic/commands/RemarkCommand.java
100.00% <100.00%> (ø)
11.00 <11.00> (?)

...a/seedu/address/logic/parser/AddCommandParser.java
100.00% <100.00%> (ø)
5.00 <0.00> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
100.00% <100.00%> (ø)
13.00 <0.00> (+1.00)

...ain/java/seedu/address/logic/parser/CliSyntax.java
85.71% <100.00%> (+2.38%)
1.00 <0.00> (ø)

...c/main/java/seedu/address/model/person/Person.java
97.77% <100.00%> (+0.15%)
22.00 <1.00> (+2.00)

... and 4 more

Continue to review full report at Codecov.

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

Cannot merge because of irrelevance to the project


feat(step-generation): blowOut emits before touchTip

closes AUTH-3, RAUT-581
Overview
One of the items for PD 8.1. Basically, we just want step-generation to swap the order in which blow out and touch tip are emitted if those settings are both turned on, in the advanced settings.
Digging through the code, looks like it is already in the correct order for mix and distribute when aspirating. So this fix only applies to transfer and consolidate
Test Plan
There is a cypress test that tests this change. But you can create a simple protocol with a transfer step, under advanced settings, add a touch tip and blow out to the dispense. Export the protocol and open the json file. See that the blow out is emitted first.
Changelog

swap order in compound commands
fix unit tests
fix cypress test

Review requests
see test plan
Risk assessment
low

Just FYI, here's the order we have documented for the Python API. I presume we want them to be the same.

Pick up tip
Mix at source
Aspirate from source
Touch tip at source
Air gap
Dispense into destination
Mix at destination
Touch tip at destination
Blow out
Drop tip


Remove duplication of menu

Hi guys,
I am facing an issue that my site has a lot of pages (~9k) so the generated menu part seems to be very big (~1.8MB). It is included into every single page, so you can guess the total duplicated size I have to put into the host.
Should we separate the menu part into single file then dynamically load it when a page is loaded?
Thanks

It's your themes task to do that, not Hugos. Have a look at partials and partialCached specifically: https://gohugo.io/functions/partialcached/#readout


docs: configure readthedocs

Summary of Changes

Basic configuration for Read the Docs

🦙 MegaLinter status: ❌ ERROR

Descriptor
Linter
Files
Fixed
Errors
Elapsed time

✅ JAVASCRIPT
prettier
1
0
0
0.54s

❌ MARKDOWN
markdown-link-check
3

2
8.76s

✅ PYTHON
bandit
1

0
0.7s

✅ PYTHON
black
1
0
0
0.5s

✅ PYTHON
flake8
1

0
0.44s

✅ PYTHON
isort
1
0
0
0.28s

✅ PYTHON
mypy
1

0
2.07s

✅ PYTHON
pylint
1

0
2.76s

✅ YAML
prettier
2
0
0
0.52s

✅ YAML
v8r
2

0
2.56s

✅ YAML
yamllint
2

0
0.25s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff
MegaLinter is graciously provided by


The method to_netcdf does not preserve chunks

What happened?
Methods to_zarr and to_netcdf behave inconsistently for chunked dataset. The latter does not preserve existing chunk information, the chunks must be specified within the encoding dictionary.
What did you expect to happen?
I expected the behaviour to be consistent for for all to_XXX() methods.
Minimal Complete Verifiable Example
import xarray as xr
import dask.array as da

rng = da.random.RandomState()
shape = (20, 20)
chunks = [10, 10]
dims = ["x", "y"]
z = rng.standard_normal(shape, chunks=chunks)
ds = xr.DataArray(z, dims=dims, name="z").to_dataset()
ds.chunks
# This one is rechunked
ds.to_netcdf("/tmp/test1.nc", encoding={"z": {"chunksizes": (5, 5)}})
# This one is not rechunked, also original chunks are lost
ds.chunk({"x": 5, "y": 5}).to_netcdf("/tmp/test2.nc")
# This one is rechunked
ds.chunk({"x": 5, "y": 5}).to_zarr("/tmp/test2", mode="w")

Frozen({'x': (10, 10), 'y': (10, 10)})
<xarray.backends.zarr.ZarrStore at 0x7f3669f1af80>

xr.open_mfdataset("/tmp/test1.nc").chunks
xr.open_mfdataset("/tmp/test2.nc").chunks
xr.open_mfdataset("/tmp/test2", engine="zarr").chunks

Frozen({'x': (5, 5, 5, 5), 'y': (5, 5, 5, 5)})
Frozen({'x': (20,), 'y': (20,)})
Frozen({'x': (5, 5, 5, 5), 'y': (5, 5, 5, 5)})

MVCE confirmation

[X] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[X] Complete example — the example is self-contained, including all data and the text of any traceback.
[X] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.
[X] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output
No response
Anything else we need to know?
I did get the same results for h5netcdf and scipy backends, so I am not sure whether this is a bug or not.
The above code is a modified version of #2198.
A suggestion: the documentation provides only examples of encoding styles. It would be helpful to provide links to a full specification.
 Here a confirmation :
In [43]: xr.open_dataset('SDUds202001010000004231000101MA.nc')['SDU'].encoding
Out[43]:
{'zlib': True,
 'szip': False,
 ..
 'contiguous': False,
 'chunksizes': (1, 1, 2600),
 ..
 'original_shape': (1, 2600, 2600),
 ..}

Rechunking and writing out
sdu20200101_rechunked = xr.open_dataset(
                                                                               'SDUds202001010000004231000101MA.nc',
                                                                               decode_cf = True,  # useful at this step ?
                                                                               chunks = {'time': 1, 'lat': 10, 'lon': 10}
)
sdu20200101_rechunked.to_netcdf('sdu20200101_rechunked.nc')
sdu20200101_rechunked.to_zarr('sdu20200101_rechunked.zarr')

Diagnosing
In [48]: xr.open_dataset('sdu20200101_rechunked.nc').chunksizes
Out[48]: Frozen({})

In [49]: xr.open_zarr('sdu20200101_rechunked.zarr')['SDU'].chunksizes
Out[49]: Frozen({'time': (1,), 'lat': (10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10), 'lon': (10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10)})

Maybe this should be rephrased as a usage question: why netcdf backends do not pull the chunk information from the variable? At least for my example I can make it work by adding
if 'chunksizes' not in encoding:
    encoding['chunksizes'] = tuple(max(c) for c in variable.chunks)

after else: statement on line 509 in https://github.com/pydata/xarray/blob/main/xarray/backends/netCDF4_.py#L509
I suspect there must be a reason why it can't be done.

By the way, I still cannot find a practical way using Python to rechunk data in a NetCDF. I can do so using the standard nccopy utility.


Add skyblock experience, Enderman and Blaze

Please describe changes
Add experience for SkyblockMember and added 2 slayer bosses Enderman and Blaze
Description

[x] I've added new features. (methods or parameters)
[x] I've added jsdoc and typings.
[ ] I've fixed bug. (optional you can mention a issue if there is one)
[ ] I've corrected the spelling in README, documentation, etc.
[ ] I've tested my code. (npm run test)

@Johannes7k75 Please update with main branch