multiple joysticks overlap

i'm teaching my 4yr old how to game and this takes it to the next level. thank you!!
with 2 pads & fixed positioning in the css ... both controllers are overlapped. this feels unintended rather than intentional ?

i rejigged things to match our quarantined physical world (logitech wireless rumblePad) nothing fancy. what you've done here is awesome. thanks again.

You converted it into a much more functional shape! 😃 I don't expect many people to be interested in overlays like this, so I am grateful for you finding it useful.
The code was meant for only one gamepad, because in the day I was writing it I didn't expect me to have any more than one gamepad at a moment. It was due to my short sight, I'd rather say. 😅

I am currently working on a new version, and although it has some features missing it's currently better than the last release at the moment, and will show multiple gamepads properly. So I suggest you to try the new version.
The striked line in the README has a 'hosted webpage' link, which actually goes to the new version in development.
For now it should be hosted before a user can use it, so you can download the repository then host it on a local server or use the link instead. I hid the link under a strikeline because it's basically unfinished, but for 'displaying multiple gamepads' it will be enough.
Thanks again for the interest and opening the issue! I hope this new version helps.


Covenant link enhancement

Encoding community values in the form of a covenant and requiring DAO members to publicly (on-chain) pledge themselves to follow these values is a compelling and unique feature of Gardens and it lies at the heart of Celeste. However, the current UI does not provide a visual signal to new users that indicates an elevated level of importance of the Covenant; at the moment it is in the same visual category as links that take users out of the Gardens app entirely (Get Tokens --> Honeyswap, Stake HNY --> Celeste).
Perhaps we consider enhancing it to appear like a button?
Mock using Fiore's latest UI changes from UX feedback:
https://www.figma.com/file/1ykTb399R03n9VKanUZHzK/Gardens-%2BCovenant-Button?node-id=0%3A1

Perhaps we could also have this button stay visible on smaller screens too

related https://github.com/1Hive/gardens/issues/274


Question about _put_file/upload

Hi Community,
I have questions about _put_file.
In the multipart upload of _put_file function, I noticed that we are sending a request at a time instead of sending all request at a single time and join them. The latter seems to be faster in my opinion. (I think the idea can also be applied to _get_file/download)
Is there any reason why we do this?
Would be happy to discuss and contribute, thank you!

It would be reasonable to write multiple pieces asynchronously. However, the pieces are necessarily large (otherwise a single call is enough), so I very much doubt there would be any time to be saved. The async route will require much more memory, since it would load many blocks of data at once.
Would you mind doing a speed-test to prove that async operation is clearly better?

Yes I agree with your point.
Only when the pieces are large enough, we will get performance improve. Also, async route will require more memory at a single time.
I can try to implement it and test the performance and we can have further discussion :)
Btw, what would be the typical way to test the upload/download speed? Should I directly use a S3 to test or there are other better ways?


Remove invalid scrape timeout from example config.

It can't be greater than the scrape interval. Let's just remove it.

:+1:


Use of deprecated function

I have noticed on https://firebase.google.com/docs/auth/ios/google-signin page under "Authenticate with Firebase" the use of a deprecated method while implementing the same in my iOS application
Here are snapshots:

Can we change the snippet code to new function?

@morganchen12 I'm unable to find the code snippet in this repostiroy, if you can help me find that then I would love to work on this.

Looks like these snippets aren't hosted on GitHub. I'll take care of it, thanks for reporting!

@morganchen12 do mention me once if it is done, I'm interested in contributing!

@morganchen12 can I know why they aren't hosted on GitHub?

Mostly because we haven't gotten around to it, honestly. I can look at moving these snippets to GitHub as well.

I'd love to contribute in any way I can if that's the case


Monitor functions in equations doesn't seem to monitor everything

monitor functions doesn't work with some mechanisms if put 'monitor functions' in equations.
however it does work if one writes "monitor functions" in each mech file, or  if one writes a monitor connectionMechName.functions for each mechanism as an equation. eg 'monitor iGABAa.functions, iAMPA.functions'

can't seem to replicate problem so I may have been mistaken.


ngff_zarr.to_ngff_zarr: "ValueError: path containing '.' or '..' segment not allowed"

Hi, thanks for this great package.
Just wanted to report here a problem I ran into when trying to read and write an example dataset available on https://idr.github.io/ome-ngff-samples/.
import ngff_zarr

ngff_multiscales = ngff_zarr.from_ngff_zarr(
    'https://uk1s3.embassy.ebi.ac.uk/idr/zarr/v0.4/idr0101A/13457537.zarr')

ngff_zarr.to_ngff_zarr('test.zarr', ngff_multiscales)

Reading from S3 works nicely, but while writing to disk zarr complains about

ValueError: path containing '.' or '..' segment not allowed

It seems that ngff_zarr.from_ngff_zarr doesn't like dataset paths at the top level (such as '0' and '1' in the example file).

@m-albert thank you for the kind words and report! :pray:
Addressed in https://github.com/thewtex/ngff-zarr/pull/58


List-Zipper

We need simple Zipper class for Lists, allowing efficient access of a focused area.

Added an implementation, but JavaDoc and tests are still missing

Good enough, I hope...

It looks good.

Almost. Travis CI fails on one of the Zipper tests.
https://travis-ci.org/DanielGronau/highj/builds/133240484
I'm sure its something minor. However I do not have time to look at it right now. I'll leave it with you.

Hmmm, I have problems fixing this from work, for some reason I get compiler errors in OS X, even after JDK update. Has to wait until evening.

More bug reports for Oracle :smile:

All fixed #34

Thank you!
Mental note: No more commits after midnight...


Add breakdowns for the 2324 season

This took so much less time than usual now that the app builds breakdowns from basic JSON schema.

@Techno11, @nholo1332 any updates on this PR?


getFeatures returns error when the layer is added but not yet rendered

Describe the bug
Calling getFeatures on a ol/layer/VectorTile that is not yet rendered but visible throws an error because this.renderer_ is not yet set.
https://github.com/openlayers/openlayers/blob/b6e7d617b5860aba7dd4dc8835085c415c64d731/src/ol/layer/Layer.js#L212-L214
This likely also happens with ol/layer/Vector.
To Reproduce
Steps to reproduce the behavior:

Go to https://codesandbox.io/s/getfeatures-error-after-load-qs14b?file=/main.js
After page is loaded move the mouse over the map until the layer is added
When the layer is added 3 seconds later you get an error

Expected behavior
There should be no error, it should always return a Promise.

Thanks for reporting this. Would you be able to provide a fix? Thanks!


Support For Providing A StartPosition With Track

Summary:
This adds support for providing a startPosition with a track. If a startPosition
is provided, the track will start playing from the specified position.
The position is in seconds.
I chose to name it startPosition because we may want to add support for providing
an endPosition as well in order to only play a sub-clip of a track. It’s not part of this
PR as it requires additional changes to SwiftAudio on the iOS side. ExoPlayer on the
Android side already supports this.
Test Plan:

verified on both iOS and Android with the example app
used a new sound file that counts in order to easily verify that startPosition works as expected

When I try this, on Android, it appears to affect the reported duration and position values such that the duration is the "clipped" duration instead of the entire duration.
For instance, if I have a track that has a total duration of 0:30, and I want to start at 0:10, the track starts and plays as expected at 0:10, however, the duration is reported as 0:20, and the position is 0:00 at the start.
This means that progress indicators and timeline seek controls are affected.
Is this what you intended, and found? It is different than the iOS behavior.

Maybe you had a different use case in mind? My intended use case for this feature would be to "resume" a track at a given time. Perhaps where a user left off in a previous listening sessions.

Yeah, it seems that clipping does not fit here - but I've found an example of setting initial position in expoplayer demo - https://github.com/google/ExoPlayer/blob/r2.10.4/demos/main/src/main/java/com/google/android/exoplayer2/demo/PlayerActivity.java#L447  - example just uses seekTo before setting a media source, probably that's the way?

I think that is probably the correct way as well. However, I don't feel I have a good enough grasp on the Android native code to suggest an exact implementation. :(

I can see multiple places that would work for adding this on "play". But I'm not seeing an obvious place to do a seek when the queue goes from one track to the next. In order to match the iOS implementation, you should be able to queue up multiple tracks, each with a start time, and have each of them start at the specified time.
Does prepare() get called when transitioning to the next track?

I had only tested it in the example app and it seemed to do the right thing. But yes, it does cause a problem with the duration.
The duration that is passed into a track (which the example didn't do), doesn't match with the actual length due to how it does the clipping.
Yes, for the first item setting seekTo before prepare on Android works but for subsequent tracks, I think the onPositionDiscontinuity listener could possibly be used. Both DISCONTINUITY_REASON_PERIOD_TRANSITION and DISCONTINUITY_REASON_SEEK may provide enough information to execute the seekTo at the point. I'll dig into tonight to see if that ensure resume of any number of tracks in the queue works.

So using onPositionDiscontinuity and setting the startPosition/initialTime there works.
It works best for DISCONTINUITY_REASON_SEEK as the position of the audio is always 0 and thus seeking doesn't cause an audible disturbance. This case is for the first track in a queue as well as if one uses the move to next / previous button / command.
However for DISCONTINUITY_REASON_PERIOD_TRANSITION which happens when you transition from one track to another, it has already re-loaded the next track is starting to play it. Because of this I log values between 20-40 ms and thus when seek is initiated, it is audible that it goes from playing to seeking to playing.
To make this work perfect as that it actually sets the seek before playing, the exoplayer has to be modified. There is already the notion of a startPosition (different from the one of the ClippingMediaSource) but as far as I can tell, it has to be exposed in order to use it for the case of resuming a track at a specific seek. That's how far I got last night.

@Guichaguri Do you have any guidance for us, as to how/where to implement a startPosition/initialTime in the Android?

I'd love to hear about your use case. I'm still confused about this PR, I can see two distinct features being mixed together:

Clipping/cutting the track (which is what you're doing on Android): Treats the track as it never had anything before the start position.

The duration changes, you can't seek to the start of the track, the track will always start from that position, like it was originally clipped.

Starting to play from a specific position (the same effect from loading and then seeking on Android)

The duration remains the same, you can still seek to the start of the track.

In case you want the latter, the proper way is to seek to the start position before playing.

Here's another question:

Track 1 is added with a start position of 0:10
Track 2 is also added
Track 1 starts to play from the start position
Track 1 ends and then Track 2 starts to play
The user skips to the previous track

Should the Track 1 start to play from 0:10 or 0:00?

currently the queue is hard to use ,why don't we let the js manage the queue? for gapless playback, emit a about to finish event,then js append the next track to preloading

I think the use case is number 2.  At least I know mine is. I want to start playing at a given time in order to resume where a user left off previously.
The reason we are trying to implement this feature is: await play() then ‘await seekTo()` (or other forms of the same idea)  doesn’t consistently work as expected on iOS. In certain cases the seek doesn’t happen because the native player is not in a state that allows it.
SwiftAudio provides the option to set an initialTime instead. As this PR shows. This works as expected every time.
Regarding skipping to previous track, no I would NOT want it to start at the specified time. I would expect it to start at zero. However, in my case this is irrelevant because I am managing my own queue and only have one track at a time in the native queue.
Maybe the better solution is some sort of playFromTime() method implemented across platforms? This would keep the track object as is, but allow you to effectively play and seek as a single action and not worry about the various thing that can go wrong if they are separate.

@gaodeng The reason why we manage the queue is to allow gapless playback. We already plan to add a player that doesn't have a managed queue in v2, but that's a subject for another issue.
@curiousdustin I totally agree with you, I think play() should accept an optional time parameter, which makes it play from that time. Most players work that way, I don't think react-native-track-player should be different.

@Guichaguri, leaving the alternate play(fromTime) plan aside for a moment, can you give us your thoughts on the effectiveness of doing the seek within onPositionDiscontinuity such as @thorbenprimke has done here: https://github.com/react-native-kit/react-native-track-player/pull/713/files/c8c260f8b80376c087ed9b9915533fd2abb2299d..147e216c30f3a389e54ee551d9caed6dd6cccd5b
Is this approach guaranteed to seek to the designated time without any chance of a tiny bit of audio playing before the seek happens?
Is onPositionDiscontinuity called in ALL cases when a new track is played?

@Guichaguri , I would possibly start a PR for the play(fromTime) feature, but the 1.1.x branch is currently broken, making it hard to have a good branching off point to start from. https://github.com/react-native-kit/react-native-track-player/issues/703

@curiousdustin - No, I don't think using onPositionDiscontinuity prevents a tiny bit of audio being played due to the nature of it being a callback. At least in my testing, audio is sometimes audible. This may be less of a case for prod builds but for debug builds with logging, it is noticeable.
In regards to your second question, I have found that it is called in the initial play, continued play as well as skipping cases. The logic that was already there detects if it's a track change.
@Guichaguri The goal of this PR was to add functionality that would allow providing an initialTime / initialSeek to any track. The use of ClippingMediaSource was incorrect (but this wasn't obvious at first with the example app).
The problem it addresses is that in a playlist, if more than one track was previously played, we need to set an initial seek not just for the first item in the playlist but also subsequent items.
A scenario is that someone has an item at position 0 in the playlist and it is played for x seconds. Now they change the order of the playlist and play a different track that is now at position 0 and is played for some time and stopped.
Now when the app is restarted, the playlist needs to be rebuilt and two tracks need an initial seek to properly resume the playing of each of the respective tracks.

Track 1 is at position 0 and is played to 15 seconds
Track 2 is added to position 1 and then moved to position 0
Track 2 is played for 20 seconds
Track 2 is paused and app closed.
App is reopened
Track 2 (in position 0) needs to have an initial seek of 20 seconds
Track 1 (in position 1) needs to have an initial seek of 15 seconds when playback is transition from Track 2 to Track 1

To answer your question as to what should happen if the user skips from Track 1 back to Track 2 (in the above example), Track 2 would play again from the previous initial seek based on both using onPositionDiscontinuity (with ExoPlayer) as well as initialTime (with SwiftAudio).
In our case we don't allow going backwards in the playlist if a track has finished as it is immediately removed (thus I'm less concerned with this).
However what should be happening (in my opinion) is that the track needs to be updated when the user skips from Track 2 (let say at 30 seconds) to Track 1 (starts at 15 seconds) forward and thus when the skip backwards, the initial seek time is actually the last played time of Track 2 (thus should play at 30 seconds instead of 20 seconds).
Since I'm not 100% happy with using onPositionDiscontinuity, I explored a solution in ExoPlayer to support this and to get guidance as how it might be implemented best. The thread is here and suggestion based on ExoPlayer current architecture is to create a wrapping MediaSource to allow for the initial seek. However it is mentioned that they have discussed this internally and may add better support for this in the future.

@FrankGoortani - I appreciate the vote of confidence but I'm not certain that we should move forward with the proposed solution. I'm using it internally for the time being but the proper solution should be to address this on ExpPlayer's side first (by adding support for this).

@thorbenprimke, did you end up finding or creating a solution that doesn't rely on onPositionDiscontinuity?

For those interested, I ended up creating a custom media source wrapper that allows setting a start time. It probably doesn't apply to all use cases but it seems to work for mine.
It does not rely on onPositionDiscontinuity, so it does not suffer from playing the start of the track.
It also allows seeking backward from the set starting point.
I followed the example given here by the ExoPlayer team. Had to modify quite a bit because things have changed, but the spirit remains the same.
https://github.com/google/ExoPlayer/issues/2403#issuecomment-330955125
Here are the relevant changes on my fork:
https://github.com/curiousdustin/react-native-track-player/commit/4e152e7640547212e1e4f5ff310270da06176312

So what's a workaround for this? I've tried calling seekTo() prior to calling play() and it plays from the start.

There are some hacks, but not a proper solution at the moment.
While @thorbenprimke solution works really well for regular streams, it breaks livestreams and some other edge cases.

Is there any update on this?
Currently I have to play() then seekTo, which means the user has to hear a second or two of the audio before it skips.
Any ideas?

Is there any update on this?
Currently I have to play() then seekTo, which means the user has to hear a second or two of the audio before it skips.
Any ideas?

Did you found a solution?

@thorbenprimke any movement on this? I know that you weren't 100% confident in this solution but TBH implementing the desired interface in this project regardless of if the the ExoPlayer/onPositionDiscontinuity implementation is perfect I think would be a good step forward. It seems like there are a lot of people struggling with this issue (I myself being one of them, see list below), and if the interface is solid then it seems to me that it would be 90% there, pending a proper implementation in ExoPlayer once there's something available for that (however, I may be missing a lot of the nuance).

https://github.com/react-native-kit/react-native-track-player/issues/981
https://github.com/react-native-kit/react-native-track-player/issues/387

I do feel that lacking this ability is a fairly critical flaw in an otherwise amazing project.

+1 struggling with this. I've made an interval that keeps trying to seek to get around it, but even that doesn't work.
Would highly appreciate getting this merged 🙏

+1...

I was able to successfully use this patch for just iOS: https://gist.github.com/gilbertl/82e3043fa5632ef653b274a2b86f59f2
On Android, I use a setInterval() and check if the seek() was successful if the new time is +/- 10sec of the seek time. This isn't a great solution, didn't work on iOS well, but it has been consistent on Android.

@thorbenprimke any movement on this? I know that you weren't 100% confident in this solution but TBH implementing the desired interface in this project regardless of if the the ExoPlayer/onPositionDiscontinuity implementation is perfect I think would be a good step forward. It seems like there are a lot of people struggling with this issue (I myself being one of them, see list below), and if the interface is solid then it seems to me that it would be 90% there, pending a proper implementation in ExoPlayer once there's something available for that (however, I may be missing a lot of the nuance).
* #981

* #387

I do feel that lacking this ability is a fairly critical flaw in an otherwise amazing project.

@curiousdustin @thorbenprimke pinging you guys on this again. Happy to help do some grunt work on this, however without oversite or merge ability I'm hesitant to start.

Thanks for the patience here, I'll try to take a look sometime this weekend or early next week!

@dcvz @bradleyflood it looks like there's some movement here. Is there anything I can do to help out?

@dcvz thank you for responding! I really do appreciate it.
FWIW the following interface would satisfy my requirements (effectively "Option 2" as I understand it):
interface TrackPlayer {
  public async play();
  public async skipToNext(initialPosition?: number);
  public async skipToPrevious(initialPosition?: number);
  public async skip(index: number, initialPosition?: number);
}

Also FWIW, the scenario of calling seekTo prior to play is currently having some issues on iOS.. But that's a separate issue and I agree that in theory that combined with the above interfaces solves our use-case.

Hi @dcvz ! Great work on this library :)
We are also in need of this functionality. Our use case is playing a queue of one or more tracks that has been previously started and then saved each tracks position.
This would fit option 1 more, I guess, as the queue should be able to run by itself and when a track ends, the next one should automatically start on the stored position for that track.
A patch from @gilbertl that uses the initialTime property for iOS makes our use case with option 1 doable with the current interface. As @jspizziri mentions, the seekTo before play works fine on Android, but not on iOS.

@martinmidtsund @dcvz ,
The way I see it "Option 1" could be layered on top of "Option 2". If that's the case and we all agree that Option 2 would be a useful set of functionality then perhaps we could implement it and implement the rest later?

I'd like to add my use-case to the mix, which I think tends towards needing Option 1 (which I do understand is a bit problematic from a multi-track queue perspective). In my case, I only ever add one track to the queue. If the user switches tracks, I always call reset before adding the new track. From my testing, I see that as soon as you add a remote (hls/dash) track to the queue and it is the "active" track, track-player will start buffering the track from the server. Yes I can seek immediately after adding, but there's still a bit of a delay, so track-player always starts buffering from position zero, even if I immediately seek afterwards.
When I opened my issue a while back (https://github.com/DoubleSymmetry/react-native-track-player/issues/1330) I mentioned this "waste of bandwidth" as the main problem.  It's honestly not really that big of a deal, but I just wanted to point it out in case it wasn't being considered.
My use-case is an audiobook app in which you only ever have one "active" book, and you tend to listen for a long period of time. Switching between books is when I reset the player and load in a different track, but I restore the previous position from the server. But I can see another argument for Option 1 being something like a podcast app, where you can add multiple "episodes" to your queue, but you still always want to restore the playback position, not start playing from the beginning.
Just my two cents! And thanks for this amazing library! ❤

@dcvz any thoughts on the comments of the folks who have chimed in?

Yeah, I've thought some more about it. I still think we should go with the option 2 approach. I think it still lends itself to being able to be used for the other use cases as well, albeit with a bit more work.
If you're up for that exploration @jspizziri lets do it! I think not being able to seek on iOS is a bug that should be fixed.

@dcvz I will put this in my schedule for next week, stay tuned!

Support for the discussed interface is largely functional on this PR. I've recommended that we close this PR in favor of the other.
With that said with the fix to iOS seek on load @dcvz  is hesitant to merge it as this might be a non-issue at this point with a reasonable solution out of the box.
There's an ongoing conversation around theoretical vs. actual performance that could use the input from the people on this thread. If you all could chime in and give your feedback or give the PR a test it would be helpful to determine what the future of the PR will be.

#1413 has been merged, and I believe this feature will land in v2.2.0-rc4 (which at the time of this writing does not exist).
@dcvz I think this issue can be closed.


Enable unit tests to generate coverage report

Codecov Report

Merging #574 into release-2.3.0 will decrease coverage by 0.01%.
The diff coverage is n/a.

@@                 Coverage Diff                 @@
##             release-2.3.0     #574      +/-   ##
===================================================
- Coverage            32.52%   32.51%   -0.02%
  Complexity            1220     1220
===================================================
  Files                  169      169
  Lines                14935    14935
  Branches              2364     2364
===================================================
- Hits                  4858     4856       -2
- Misses                9357     9359       +2
  Partials               720      720

Impacted Files
Coverage Δ
Complexity Δ

...p/searchindex/elasticsearch/ElasticSearchUtil.java
47.94% <0%> (-0.55%)
52% <0%> (ø)

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 4dabf7b...c6d4d47. Read the comment docs.


Kodi Adult add-ons real and up to date

Here's a list of all the adult add-ons available with Kodi Leia. Includes build info, repos and add-ons.

esteeeeee


Case validation with repeated labels

Fixes #2686

Update validation to handle the default case being mentioned multiple
times

new tests

It's been a while. Please rebase so we get an updated picture from the bots.


[Feature] Multiagent API in vmas

Implementation of #943 in vmas
The agent dimension has been moved outside the batch_size.
I will use this simulator to implement a multi-agent training example in torch rl

@vmoens  this should be ready.


So weird behavior

I call request one time but .end() is executed twice. And  .end() is executed twice only when the callback generated an exception.
http://prntscr.com/bta1qx
FYI: https://www.facebook.com/groups/228321510706889/permalink/488046104734427/?comment_id=488054721400232&reply_comment_id=488057098066661&notif_t=group_comment&notif_id=1468594595902645

FYI you can drag/drop the image into this github issue to make it show up.

Please try version 2.1, it includes a fix for doubled callbacks.


Upgrade Huawei Cloud Core SDK to version 3.1.60

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-test camel-huawei/camel-huaweicloud-common  camel-huawei/camel-huaweicloud-dms  camel-huawei/camel-huaweicloud-frs  camel-huawei/camel-huaweicloud-functiongraph  camel-huawei/camel-huaweicloud-iam  camel-huawei/camel-huaweicloud-imagerecognition  camel-huawei/camel-huaweicloud-obs  camel-huawei/camel-huaweicloud-smn


SRP server fails to send response to SRP client: "[server] send fail response: 5"

Describe the bug
SRP server fails to send response to SRP client: "[server] send fail response: 5"
To Reproduce
github/openthread (commit '686c0de5fa79d5afe5b3128fabdb61e05610607d') Dec-14
github/ot-br-posix (commit '72fa16e595af28d2f2a3fbd19c3da9f5c3d397de') Dec-15
Use avahi for DNS

Leader border router creates a network
Thread end node joins the network, and registers service with random name"NNN_MMM"
Thread end node does factory reset.
repeat step 2 , 100 interactions.

in some test cycles, (~15 of 100).  , the SRP server fails to send a response to the SRP client:
04-27 05:36:09.263 I/otbr-agent( 4426): [INFO]-MAC-----: Received IPv6 UDP msg, len:313, chksum:2694, from:0x8400, sec:yes, prio:normal, rss:-55.0
04-27 05:36:09.263 I/otbr-agent( 4426): [INFO]-MAC-----:     src:[fdba:be11:2aa3:0:80bd:2583:d2f5:a593]:49154
04-27 05:36:09.263 I/otbr-agent( 4426): [INFO]-MAC-----:     dst:[fdba:be11:2aa3:0:f051:f8f:393:442a]:53535
04-27 05:36:09.263 I/otbr-agent( 4426): [INFO]-SRP-----: [server] Received DNS update from fdba:be11:2aa3:0:80bd:2583:d2f5:a593
04-27 05:36:09.263 I/otbr-agent( 4426): [INFO]-SRP-----: [server] send fail response: 5
I noticed that in normal success operation, the accessory device sends SRP DNS update within 1 second after it got CHILD ID response. , but during the failure operation, the SRP DNS update arrives ~20 seconds later.
Expected behavior
The SRP server should be able to register the service.
Console/log output
Additional context
I found this, by using Matter (CHIP) application framework. (version TE8_rc3)
Amazon echo device as Matter controller (chip-tool alike).
nRF-DK board as matter light-bulb

@AlanLCollins , thanks for raising this issue. I believe this is related to https://github.com/openthread/ot-br-posix/issues/1272 and a fix was provided in https://github.com/openthread/ot-br-posix/pull/1273. Can you see if this fix addresses your issue?

Hello @jwhui , Thank you for the guidance!
I updated my repo to TOT for both openthread and ot-br-posix. The issue is no longer happening.
I will close this ticket.

Hello @jwhui , Thank you for the guidance! I updated my repo to TOT for both openthread and ot-br-posix. The issue is no longer happening. I will close this ticket.

@AlanLCollins , awesome to hear. Thanks for reporting back!


Fixed #26971 -- Prevented crash with non-UTF-8 incoming PATH_INFO

Reviewed for style only, if you want an opinion about the implementation, please ask someone else. :-)

@aaugustin and @loic come to mind...

Hi Claude, sorry I dropped the ball on this ticket, I saw your mentions when I was traveling and I forgot about it. I don't have all the details in mind anymore, but shouldn't we use utils.encoding.uri_to_iri() here?

It's worth double checking, but I suspect that by doing so this whole function can go away: https://github.com/django/django/blob/master/django/core/servers/basehttp.py#L133-L154.

shouldn't we use utils.encoding.uri_to_iri() here?
Current tests pass with uri_to_iri. I think that unquoting is sometimes done by the Web server. Is there any risk of double-unquoting the path? If not, then using uri_to_iri should be safe.

Unquoting isn't completely idempotent, because decoding the percent sign (%25) can lead to new percent encoded sequences. Is that confirmed that web servers sometime "helpfully" decode?

OK my understanding of http://www.ietf.org/rfc/rfc3875 section 4.1.5. is that PATH_INFO should already be percent decoded and I could confirm that both gunicorn and simple_server.WSGIServer perform the percent decoding. So your fix is good. And I believe we can still remove this snippet https://github.com/django/django/blob/master/django/core/servers/basehttp.py#L144-L152.

👍  LGTM


No camera feed and warning UNHANDLED ERROR

I just set up this in my Homebridge. Other devices (like switches) work fine and can be detected. Not the camera feed. Here is the error message in the logs.
UNHANDLED ERROR: Error: Received no partitions from Alarm.com
    at /volume1/homebridge/node_modules/homebridge-node-alarm-dot-com/src/index.ts:184:19
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

We don't support cameras, so that's why you're not seeing them. Pull requests welcome but I think due to the conversion work for the camera stream, it would need to be an additional plugin.
Curious about the error you're seeing. Do you have partitions on your system? ASAIK there is no way to have an alarm.com account without one...

Closing the camera issue as not supported. Please open a new issue if there are still problems with the partition error you list.


fixed always waiting navigate action when context canceled

I have been fixed issue that always waiting navigate action after context canceled.
This code to reproduce this issue.
thanks :D
// create context
ctx, cancel := context.WithCancel(context.Background())

// create chrome instance
chrome, err := chromedp.New(ctx,
	chromedp.WithRunnerOptions(runner.Headless),
)
if err != nil {
	return err
}

cancel()

time.Sleep(time.Second)

fmt.Println("finished sleep")

// infinity wait
return chrome.Run(ctx, chromedp.Tasks{
	chromedp.Navigate("https://google.com"),
})

Coverage increased (+0.02%) to 68.393% when pulling f20cd76b991a896bff3a4e7d48a0417f338016eb on Code-Hex:master into 39bd95c850a4a1a375c73469fc19e16ada435141 on chromedp:master.

Hi, and thanks for your patch!
We're currently working on a full refactor of the API and internal design. I'm fairly certain that you wouldn't have these issues with the new version; it's context-based at core, so it should be possible to stop it or cancel it at any point.
Consider having a look at https://github.com/chromedp/chromedp/tree/refactor, and trying to reproduce the same issue once we release an alpha in the coming weeks. I don't think it's worth trying to fix issues in the old codebase; we should instead focus on the better design from the ground up :)

@mvdan That's great!
However we are using current version as production stage. we hope this patch will be merged into the current version.
This patch is only single line, and I think it will not affect refactoring.
So please merge and release it :bow:

This piece of code is entirely gone from the upcoming version, and it would take some time to properly test the change for regressions, so I'm sorry but I disagree about its effect on the refactor.
I appreciate that you're using the stable version on production and want this patch, but you can do that without requiring that we merge and release the patch. For example, both Go modules and older dependency managers like dep allow replacing one dependecy with a forked git repository.
It's unfortunate that the master branch is in this transitional state, but we plan to end that soon. Hope that makes sense.

@mvdan Do you mean that we should use forked version using dep or modules?

Yes. See https://github.com/golang/go/wiki/Modules#when-should-i-use-the-replace-directive, for example. It should be easy to set up, and you can apply as many patches to chromedp as you want.


fix: issue 1615 - Switch formatting condition for dictionary

Description
Fixes issue #1615
A dictionary will return true when using not_iterable from snakemake.io. The elif condition is never reached/true in the original code. Swapping them will cause dictionaries to be formatted as expected by snakemake.
QC

[ ] The PR contains a test case for the changes or the changes are already covered by an existing test case.
[x] The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

I'm not sure how to test this, or if i break any other functionality by changing this.

Thank you so much, good catch!


fix for issue #346 textMask still have problem on ion-input

in ngAfterViewInit we need to check inputElement instead of textMaskInputElement.

I think lines 61-63 should also be wrapped with:
if !this.inputElement) {
...
}

Makes sense, let me add it to the PR

Added, and tested the changes on our ionic project.

Thanks folks!

Published as<EMAIL_ADDRESS>


Fix output duplication on escaped chunk boundaries

Closes #515

This is a serious bug, I will issue a bugfix release right away.


[BUG] reduced setup time in workflow "QA Integration Test" because of clang-format

Describe the bug
With Zephyr v3.2 the Python package clang-format will be installed within our "QA Integration Test" workflow. Reson is the follwoing line:
pip3 install --upgrade --requirement zephyr/scripts/requirements-extras.txt

--> https://github.com/zephyrproject-rtos/zephyr/blob/ed05fdf0e532d5a9747abde8a830872f3726badd/scripts/requirements-extras.txt#L13
Now, unfortunately, the ARM 64 bit architecture is not (yet) supported on PyPi with a wheel. So on a Raspberry Pi 4 this means an extremely long installation time, because a native C++ compile has to build the wheel from the sdist package first.
Do we really need all the extra Python packages for our "QA Integration Test" workflow?
To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build
python3 -m venv --clear --copies --prompt="$(basename $(pwd))[$(python3 --version)]" .env
source .env/bin/activate
pip3 install --upgrade pip
pip3 install --upgrade setuptools
pip3 install clang-format
And now wait multiple hours ... :-(

Expected behavior
Either we can skip Zephyr's extra packages or PyPi will provide an manylinux-aarch64 wheel in near future. As long the last choice will not happen we can only handle our Python cache carefully.
Monitor issue ssciwr/clang-format-wheel#64
Development Environment (please complete the following information):

OS: Linux on ARM 64 bit
Zephyr v3.2
Bridle next branch

Additional context
Non.

As long as Zephyr requires at least clang-format 1.13, we can try to use 14.0.6 as described in ssciwr/clang-format-wheel#49 – version 14.0.6 still provides an manylinux-aarch64 wheel: Solange Zephyr mindestens clang-format 1.13 benötigt, können wir versuchen, 14.0.6 zu verwenden, wie in Ausgabe 3 beschrieben.

Okay, the Python cache on the GHAR machine have catched the locally rebuilded wheel, see: https://github.com/tiacsys/bridle/actions/runs/4277988000/jobs/7454126471
But the workflow will run again into a long time rebuild when a new version will be released on PyPi!

solved by upstream


GH-35361: [C++] Remove Perl dependency from cpp/build-support/run-test.sh

Rationale for this change
Because Perl in conda doesn't work on Manjaro Linux.
What changes are included in this PR?

Use sed instead of perl.
Remove stacktrace_addr2line.pl. If we still need it, we can re-implement the addr2line filter in other language such as Python or shell later.

Are these changes tested?
Yes by hand on Manjaro Linux.
Are there any user-facing changes?
No.

Closes: #35361

@assignUser You can try this for TEST_DEFAULT=0 TEST_SOURCE=0 TEST_CPP=1 USE_CONDA=1 dev/release/verify-release-candidate.sh 12.0.0 0 with the following patch:
diff --git a/dev/release/verify-release-candidate.sh b/dev/release/verify-release-candidate.sh
index 779e71a38..334348a8f 100755
--- a/dev/release/verify-release-candidate.sh
+++ b/dev/release/verify-release-candidate.sh
@@ -599,6 +599,8 @@ test_and_install_cpp() {
     ARROW_CMAKE_OPTIONS="${ARROW_CMAKE_OPTIONS:-} -G ${CMAKE_GENERATOR}"
   fi

+  cp ${SOURCE_DIR}/../../cpp/build-support/run-test.sh ${ARROW_SOURCE_DIR}/cpp/build-support/
+
   cmake \
     -DARROW_BOOST_USE_SHARED=ON \
     -DARROW_BUILD_EXAMPLES=OFF \

I confirmed that the verification command passes with this change on the manjarolinux/base Docker image.

Yes checking out this PR and applying the patch does work :tada: Thanks for taking this on!

That's good to know. :-)
Could you share it on the vote thread too?


Update bodies (Dragging & Click to edit directive)

What's New?

Click to edit directive (currently set up with x & y positions)
Dragging bodies now works visually

What's Left?

[ ] Directive does not work with the unit filters, so some resolution is needed.

[ ] Updating positions in the simulator is set up but needs implementation.

@mkinsey It looks like you have some merge conflicts.

Wahoo!


Android R8 minimize fails with android-v11.2.0

Describe the bug
R8 Minimize fails with the latest version https://github.com/maplibre/maplibre-native/releases/tag/android-v11.2.0
Downgrading to version 11.1.0  works.
I guess it comes from https://github.com/maplibre/maplibre-native/pull/2714
See the logs :
AGPBI: {"kind":"error","text":"Missing class com.mapbox.android.gestures.AndroidGesturesManager (referenced from: com.mapbox.android.gestures.AndroidGesturesManager org.maplibre.android.plugins.annotation.DraggableAnnotationController$1.val$androidGesturesManager and 4 other contexts)\nMissing class com.mapbox.android.gestures.MoveGestureDetector$OnMoveGestureListener (referenced from: void org.maplibre.android.plugins.annotation.DraggableAnnotationController.<init>(org.maplibre.android.maps.MapView, org.maplibre.android.maps.MapLibreMap, com.mapbox.android.gestures.AndroidGesturesManager, int, int, int, int) and 1 other context)","sources":[{}],"tool":"R8"}

Ok, importing com.mapbox.mapboxsdk:mapbox-android-gestures:0.7.0 fixes the issue.
I guess it should still be managed by the plugin?

We need to update the plugin and make a new release.

I just published a new version of the annotations plugin (3.0.1-pre1).
Could anyone try it out?
https://central.sonatype.com/artifact/org.maplibre.gl/android-plugin-annotation-v9/versions

3.0.1 has been released. Please let me know if there are any problems.

Sorry I hadn't seen the update. Working properly, thanks!


Added service for ensuring system clock is plausibly set

Background
I'm using two Raspberry Pis at home running k3os as single node clusters and ran into the following issue:

The lack of a hardware clock means the Raspberry Pi relies entirely on an NTP server at boot to set the system clock
k3s is hard-coded to fail to start if the system time is set before 1980
There's no mechanism currently in k3os to wait for the clock to be validly set before starting k3s
After failing to start k3s some amount of times, it will no longer be retried

This means if, for whatever reason, the Pi is unable to update its system time quickly enough via NTP, it can go into a state that requires administrator intervention to recover.
In my case, these Pis are serving as the DNS servers for my network, so it's important to me that they are sufficiently robust that they will begin running Kubernetes soon after (e.g.) a network-wide power outage is restored. They're configured to sync time with a public NTP server, but my cable modem can sometimes take a few minutes to initialize Internet connectivity. The net result is that their clocks don't get synced for a few minutes when starting up, but by then k3s has failed to start enough times that it's no longer being retried.
TL;DR
I created this pull request to cause k3os to wait until the system time is set to 1980 or later before starting k3s. This based on the idea that there's no plausible circumstance under which one would want k3s to start without that happening, since it will definitively fail due to the hard-coded check.
Details
This should have no noticeable effect on any system with a functioning / set hardware clock.
I did set a configurable timeout for it in /etc/conf.d/clock-sane, although it is set to 0 (wait forever) by default.
The only other change here is to move sshd to the boot runlevel (instead of default). This was done to ensure sshd isn't delayed in coming up as a result of waiting for the system time to be set.

Thanks for your time in reviewing.
I just adapted this from the net-online service script already in this project. I don't know what other distros are using--they might not be doing anything. I suspect it's a little of a unique case with k3s being hardcoded to fail to start with the system time before 1980.
I'll review and try to resolve the issue with sshd start ordering without changing its runlevel. Thank you


cool cool mountain in tall tall mountain glitch

This was a temporary bug, when me and my friend were going to play sm64 js he spawned in cool cool mountain while everyone else spawned in tall tall mountain. we could interact with him and he could interact with us. As i said this was temporary he restarted the game and he was in tall tall mountain just wanted to let you know. also when he stood still his hat colors glitched out.
Thank you,
sm64jsfan

As a fellow fan of this project i find this interesting

probably a bad network packet finding its way in


Token contract source code not verified

Hi i have create my token with your code i have use
https://github.com/ConsenSys/Tokens/blob/master/contracts/eip20/EIP20.sol
end
https://github.com/ConsenSys/Tokens/blob/master/contracts/eip20/EIP20Interface.sol
i have create my token ETQ in https://remix.ethereum.org (Real not test )
Now i have to add link of my website and logo to do that i need to verify my source code
How i can do that ?
Where i can see my Constructor Arguments ABI-encoded ?
Please help me
My code in https://remix.ethereum.org
i have two file
EIP20Interface.sol
    // Abstract contract for the full ERC 20 Token standard
// https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20.md
pragma solidity ^0.4.18;

contract EIP20Interface {
    /* This is a slight change to the ERC20 base standard.
    function totalSupply() constant returns (uint256 supply);
    is replaced with:
    uint256 public totalSupply;
    This automatically creates a getter function for the totalSupply.
    This is moved to the base contract since public getter functions are not
    currently recognised as an implementation of the matching abstract
    function by the compiler.
    */
    /// total amount of tokens
    uint256 public totalSupply;

    /// @param _owner The address from which the balance will be retrieved
    /// @return The balance
    function balanceOf(address _owner) public view returns (uint256 balance);

    /// @notice send `_value` token to `_to` from `msg.sender`
    /// @param _to The address of the recipient
    /// @param _value The amount of token to be transferred
    /// @return Whether the transfer was successful or not
    function transfer(address _to, uint256 _value) public returns (bool success);

    /// @notice send `_value` token to `_to` from `_from` on the condition it is approved by `_from`
    /// @param _from The address of the sender
    /// @param _to The address of the recipient
    /// @param _value The amount of token to be transferred
    /// @return Whether the transfer was successful or not
    function transferFrom(address _from, address _to, uint256 _value) public returns (bool success);

    /// @notice `msg.sender` approves `_spender` to spend `_value` tokens
    /// @param _spender The address of the account able to transfer the tokens
    /// @param _value The amount of tokens to be approved for transfer
    /// @return Whether the approval was successful or not
    function approve(address _spender, uint256 _value) public returns (bool success);

    /// @param _owner The address of the account owning tokens
    /// @param _spender The address of the account able to transfer the tokens
    /// @return Amount of remaining tokens allowed to spent
    function allowance(address _owner, address _spender) public view returns (uint256 remaining);

    // solhint-disable-next-line no-simple-event-func-name
    event Transfer(address indexed _from, address indexed _to, uint256 _value);
    event Approval(address indexed _owner, address indexed _spender, uint256 _value);
}

End in Taouaf.sol i have this
/*
Implements EIP20 token standard: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-20.md
.*/

pragma solidity ^0.4.18;

import "./EIP20Interface.sol";

contract Taouaf is EIP20Interface {

    uint256 constant private MAX_UINT256 = 2**256 - 1;
    mapping (address => uint256) public balances;
    mapping (address => mapping (address => uint256)) public allowed;
    /*
    NOTE:
    The following variables are OPTIONAL vanities. One does not have to include them.
    They allow one to customise the token contract & in no way influences the core functionality.
    Some wallets/interfaces might not even bother to look at this information.
    */
    string public name;                   //fancy name: eg Simon Bucks
    uint8 public decimals;                //How many decimals to show.
    string public symbol;                 //An identifier: eg SBX

    function Taouaf(
        uint256 _initialAmount,
        string _tokenName,
        uint8 _decimalUnits,
        string _tokenSymbol
    ) public {
        balances[msg.sender] = _initialAmount;               // Give the creator all initial tokens
        totalSupply = _initialAmount;                        // Update total supply
        name = _tokenName;                                   // Set the name for display purposes
        decimals = _decimalUnits;                            // Amount of decimals for display purposes
        symbol = _tokenSymbol;                               // Set the symbol for display purposes
    }

    function transfer(address _to, uint256 _value) public returns (bool success) {
        require(balances[msg.sender] >= _value);
        balances[msg.sender] -= _value;
        balances[_to] += _value;
        Transfer(msg.sender, _to, _value);
        return true;
    }

    function transferFrom(address _from, address _to, uint256 _value) public returns (bool success) {
        uint256 allowance = allowed[_from][msg.sender];
        require(balances[_from] >= _value && allowance >= _value);
        balances[_to] += _value;
        balances[_from] -= _value;
        if (allowance < MAX_UINT256) {
            allowed[_from][msg.sender] -= _value;
        }
        Transfer(_from, _to, _value);
        return true;
    }

    function balanceOf(address _owner) public view returns (uint256 balance) {
        return balances[_owner];
    }

    function approve(address _spender, uint256 _value) public returns (bool success) {
        allowed[msg.sender][_spender] = _value;
        Approval(msg.sender, _spender, _value);
        return true;
    }

    function allowance(address _owner, address _spender) public view returns (uint256 remaining) {
        return allowed[_owner][_spender];
    }
}

My ABI
is
0000000000000000000000000000000000000000033b2e3c9fd0803ce80000000000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000c0000000000000000000000000000000000000000000000000000000000000000e4574686572205175616c6966656400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000034554510000000000000000000000000000000000000000000000000000000000

How i can put this code here https://etherscan.io/verifyContract?a=0x38f10839dcbf15936f79bee139ceaf484edaca46
to validate my TOKEN

Hi there, source code verification with etherscan is a tricky thing. We're not the experts in it though, so we can't help you here.
Have a look at this help article of theirs: https://etherscancom.freshdesk.com/support/solutions/articles/35000022165-contract-verification-constructor-arguments

Hi ryodoo, i saw your contract was Verifyed. How do u get it?

You have to change the code i have use this code
`pragma solidity ^0.4.4;
contract Token {
/// @return total amount of tokens
function totalSupply() constant returns (uint256 supply) {}

/// @param _owner The address from which the balance will be retrieved
/// @return The balance
function balanceOf(address _owner) constant returns (uint256 balance) {}

/// @notice send `_value` token to `_to` from `msg.sender`
/// @param _to The address of the recipient
/// @param _value The amount of token to be transferred
/// @return Whether the transfer was successful or not
function transfer(address _to, uint256 _value) returns (bool success) {}

/// @notice send `_value` token to `_to` from `_from` on the condition it is approved by `_from`
/// @param _from The address of the sender
/// @param _to The address of the recipient
/// @param _value The amount of token to be transferred
/// @return Whether the transfer was successful or not
function transferFrom(address _from, address _to, uint256 _value) returns (bool success) {}

/// @notice `msg.sender` approves `_addr` to spend `_value` tokens
/// @param _spender The address of the account able to transfer the tokens
/// @param _value The amount of wei to be approved for transfer
/// @return Whether the approval was successful or not
function approve(address _spender, uint256 _value) returns (bool success) {}

/// @param _owner The address of the account owning tokens
/// @param _spender The address of the account able to transfer the tokens
/// @return Amount of remaining tokens allowed to spent
function allowance(address _owner, address _spender) constant returns (uint256 remaining) {}

event Transfer(address indexed _from, address indexed _to, uint256 _value);
event Approval(address indexed _owner, address indexed _spender, uint256 _value);

}
contract StandardToken is Token {
function transfer(address _to, uint256 _value) returns (bool success) {
    //Default assumes totalSupply can't be over max (2^256 - 1).
    //If your token leaves out totalSupply and can issue more tokens as time goes on, you need to check if it doesn't wrap.
    //Replace the if with this one instead.
    //if (balances[msg.sender] >= _value && balances[_to] + _value > balances[_to]) {
    if (balances[msg.sender] >= _value && _value > 0) {
        balances[msg.sender] -= _value;
        balances[_to] += _value;
        Transfer(msg.sender, _to, _value);
        return true;
    } else { return false; }
}

function transferFrom(address _from, address _to, uint256 _value) returns (bool success) {
    //same as above. Replace this line with the following if you want to protect against wrapping uints.
    //if (balances[_from] >= _value && allowed[_from][msg.sender] >= _value && balances[_to] + _value > balances[_to]) {
    if (balances[_from] >= _value && allowed[_from][msg.sender] >= _value && _value > 0) {
        balances[_to] += _value;
        balances[_from] -= _value;
        allowed[_from][msg.sender] -= _value;
        Transfer(_from, _to, _value);
        return true;
    } else { return false; }
}

function balanceOf(address _owner) constant returns (uint256 balance) {
    return balances[_owner];
}

function approve(address _spender, uint256 _value) returns (bool success) {
    allowed[msg.sender][_spender] = _value;
    Approval(msg.sender, _spender, _value);
    return true;
}

function allowance(address _owner, address _spender) constant returns (uint256 remaining) {
  return allowed[_owner][_spender];
}

mapping (address => uint256) balances;
mapping (address => mapping (address => uint256)) allowed;
uint256 public totalSupply;

}
//name this contract whatever you'd like
contract ETQuality is StandardToken {
function () {
    //if ether is sent to this address, send it back.
    throw;
}

/* Public variables of the token */

/*
NOTE:
The following variables are OPTIONAL vanities. One does not have to include them.
They allow one to customise the token contract & in no way influences the core functionality.
Some wallets/interfaces might not even bother to look at this information.
*/
string public name;                   //fancy name: eg Simon Bucks
uint8 public decimals;                //How many decimals to show. ie. There could 1000 base units with 3 decimals. Meaning 0.980 SBX = 980 base units. It's like comparing 1 wei to 1 ether.
string public symbol;                 //An identifier: eg SBX
string public version = 'H1.0';       //human 0.1 standard. Just an arbitrary versioning scheme.

//
// CHANGE THESE VALUES FOR YOUR TOKEN
//
//make sure this function name matches the contract name above. So if you're token is called TutorialToken, make sure the //contract name above is also TutorialToken instead of ERC20Token
function ETQuality(
    ) {
    balances[msg.sender] =<PHONE_NUMBER>000000000000000000;               // Give the creator all initial tokens (100000 for example)
    totalSupply =<PHONE_NUMBER>000000000000000000;                        // Update total supply (100000 for example)
    name = "Ether Quality";                                   // Set the name for display purposes
    decimals = 18;                            // Amount of decimals for display purposes
    symbol = "ETQ";                               // Set the symbol for display purposes
}

/* Approves and then calls the receiving contract */
function approveAndCall(address _spender, uint256 _value, bytes _extraData) returns (bool success) {
    allowed[msg.sender][_spender] = _value;
    Approval(msg.sender, _spender, _value);

    //call the receiveApproval function on the contract you want to be notified. This crafts the function signature manually so one doesn't have to include a contract in here just for this.
    //receiveApproval(address _from, uint256 _value, address _tokenContract, bytes _extraData)
    //it is assumed that when does this that the call *should* succeed, otherwise one would use vanilla approve instead.
    if(!_spender.call(bytes4(bytes32(sha3("receiveApproval(address,uint256,address,bytes)"))), msg.sender, _value, this, _extraData)) { throw; }
    return true;
}

}`


unable to mmap ((os/kern) no space available)

I'm trying to dump apps but I'm getting "unable to mmap ((os/kern) no space available)".
Also when I'm trying to use frida-trace sometimes it shows me the top error massage.
What's the solution?

solution: Reinstall frdia tweak each time you get this error.


fix: updated github repository link

changed links to new sveltesociety-2021 github project

I feel like sveltesociety-2021 will age badly as a repository name and that we should rename the current sveltesociety.dev repo to something like sveltesociety-legacy and then rename this one to sveltesociety.dev, but that would have to be up to @kevmodrome

I think that makes sense @benmccann 👍

Sorted out. Thanks for the PR though! 🙏


fix(delete-user-data): storage bucket param

fixes #531
Here is a log of the {DEFAULT}/testext/{UID}.jpg being deleted:

I also spent some time trying to run the emulator for this extension. The cloud function emulator ran as expected, the auth emulator did not. I'll create an issue on the firestore-tools repository.

I've created three separate issues for the extension emulators:
https://github.com/firebase/firebase-tools/issues/2928
https://github.com/firebase/firebase-tools/issues/2929
https://github.com/firebase/firebase-tools/issues/2930


Update UserChangeEvent in base-events.ts

Summary
This PR completes the incomplete UserChangeEvent type to match https://api.slack.com/types/user as noted in the TODO in base-events.ts.
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Hi @Jordan-Loeser, thanks for taking the time to make this pull request. We would like to have this change in the next release! A few things we need to check before merging this are:

Some fields may not be always present. We may want to change some to optional.
Some fields are still missing (e.g., enterprise_user exists only for Enterprise Grid workspace).

I will do more research on these and get back to you soon!

It seems that the CI builds are failing. Can you run npx prettier -w src and commit the applied changes?
><EMAIL_ADDRESS>lint /home/runner/work/bolt-js/bolt-js
> prettier 'src/**/*.ts' --check && eslint --ext .ts src

Checking formatting...
[warn] src/types/events/base-events.ts
[warn] Code style issues found in the above file(s). Forgot to run Prettier?
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>lint: `prettier 'src/**/*.ts' --check && eslint --ext .ts src`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Test failed.  See above for more details.
Error: Process completed with exit code 1.

Hey @Jordan-Loeser, thanks for promptly updating this PR! It seems that there are still prettier failure in CI builds. Can you check my above comment?

Thanks for your contribution! Your changes are merged as https://github.com/slackapi/bolt-js/commit/8fac36586553fc6e6a8d94a96a5446b41d068afb


Changes from newlayout that didn't make into the merge yesterday

Probably this was not a good idea for me to use git rebase while merging branches, looks like some files dign't get through


How to response 204 using response.json()

Usually the DELETE request should return a 204 response. How can I send 204 response using sanic. I was trying something like below.
return response.json(
        None,
        status=204
    )

But it doesn't work, it response with null.

@alaminopu @ahopkins @r0fls This is happening because the json_dumps functions try to deserialize None which returns 'null' as a string, making this a response length of 4 even tho the HTTP code is 204 with no content, as I can see (maybe I'm incorrect) Sanic indeed returns 'null'.
So, technically returning None is correct as returns null, when you use the 204 code then tecnically there's no body (you can read this RFC for HTTP/1.1) this means the according to the specification:

The 204 response MUST NOT include a message-body, and thus is always
terminated by the first empty line after the header fields.
therefore the Header is proper, but the body is cut off.

I would propose to have a None response to have '' (empty string) as no content, instead of null (for all response codes)
What you think?

try this:
return response.json({}, 204}

@r0fls It is NOT a bug.  The status code 204 shows 'no content'.  It means we check status code first and ignore check it's content.
@alaminopu @abhishek7 json.dumps(None) and json.dumps('') isn't normal usage. consider this explicit statement json.dumps({})

@h-wei the fact that the content-length and the actual body length differ is a bug. Please see RFC 2616 and refrain from YELLING:

When a Content-Length is given in a message where a message-body is allowed, its field value MUST exactly match the number of OCTETs in the message-body.

closing per #1113


fix: update logging to log account,request_id and inventory_id

Update logging to log account,request_id and inventory_id

Use logstash_formatter to generate json format log records for default logger
Customize LogRecordFactory to record  account, request_id and inventory_id info in kafka

@csams
Now the insights-engine is running in below kind of image, so the version of python is 3.6.8. But the contextVar module was introduced in 3.7.1    So can not use contextVar.  I will update the code to use Filter +  shared dict without contextVar. Do you agree ?
Of course, I prefer to upgrade the python to 3.9 (yum install python39).  I will raise this topic and email to related teams for discussion. But the discussion takes time. After python upgrade, we can update the code to use contextVar.
Docker file:

FROM registry.access.redhat.com/ubi8/ubi:latest
RUN yum -y install git autoconf automake gcc libtool file diffutils make python3 python3-pip && yum clean all

@csams  The base image is updated to python 3.11 by MR https://github.com/RedHatInsights/insights-core-base/pull/10
So use filter and contextvar now. Please review again. Thanks.


GUI Gazebo didn't run

i have tried run make px4_sitl gazebo and gazebo opened with quad. But when i try to run that command again, it shows this

i have closed the gazebo and tried to make clean than compile again, but it still said PX4 already running.
Any suggestion? thx:)

i have solved it by restarting my laptop. i think it's because unproperly closing operation on gazebo


Upgrade to node 18

Migrating to node 18 will allow use to update to latest Jest.
Changes

Upgrade to node 18 from 16

Testing

PR checks should pass.
Update your local node via nvm install 18 && nvm use 18

Closing for now as https://github.com/cfpb/consumerfinance.gov/pull/7326 is blocked


[server-wallet] Remove unnecessary "handlers" code

We're moving away from having "handlers" and closer towards this architecture.

[ ] If UpdateChannelHandlerParams is used, it should be re-named and re-exported elsewhere.
[ ] UpdateChannelError should be re-exported elsewhere
[ ] If JoinChannelHandlerParams is used, it should be re-named and re-exported elsewhere.
[ ] JoinChannelError should be re-exported elsewhere

Originally posted by @andrewgordstewart in https://github.com/statechannels/statechannels/pull/2795#discussion_r515651464

stale

stale


ModuleNotFoundError: No module named 'Contour'

Describe the bug
I have downloaded all the package but still it gives me this error also i tried using different code editors but nothing seems to work can someone help me with this. I have downloaded the latest code from main branch

Though this library don't use any contouring features, try installing following:
pip install contour
Also, closing this issue as the particular requirement is not listed in Screeni-py's requirements.


Streak seems broken (screenshot)

As I understand this problem happens because cal-heatmap displays data in user's browser timezone. Streaks and completed challenge list dates are shown in server's time zone. Thus the difference.
To solve it I suggest showing all three components using client's timezone. I can see to ways doing this:

Store user's timezone in a cookie from client side and on the server side get cookie and calculate Streaks and show completed list in a timezone from cookie.
Store user's timezone in a user profile (persist to Mongodb) and on the server side use timezone from profile.

I would prefer second option. Maybe in the future there will change user settings functionality on FreeCodeCamp and user will be able to change timezone to one of her choice.
What do you think, guys? I could implement needed changes.

The problem with 1 is now everyone will see different results when viewing the same profile.

2 sounds viable

Well, @BerkeleyTrue, with option 2 everyone will see diff results as well, since there is no way to control timezone on cal-heatmap (as far as I know).
I think the main issue - inconsistency among several components on one page. Seeing someones profile in your timezone doesn't look that bad to me.

On the other hand, we could prep data before passing it to cal-heatmap using user's timezone.
@BerkeleyTrue, @QuincyLarson I need a second opinion, if I'm looking into another user's profile, should I see data represented in his timezone (so it would be the same for same user everywhere) or should it be in my timezone? I'm wondering how Github is doing it..

I guess I would be less worried about what other people saw that what I saw.  We get lots of complaints that user's don't see their streak, or it appears to be broken.  I can't imagine that we get many that complaints about viewing OTHER people's profiles.
Still, it would be nice to fix it "once and for all" ... even if it means "Xtream timezone maths!"

Can confirm this is still happening on my profile, though I'll assume that's because the fix hasn't been merged yet. :smile:

The streak is also showing zero days for camper @thebgar who completed a challenge today:


Excess console

What problem does this feature solve?
There is an extra conosle on line 112 of the "build .js" file in scripts
What does the proposed API look like?
There is an extra conosle on line 112 of the "build .js" file in scripts

wow, thats awesome!

It seems to be intentional, judging from the rest of the file. And this is not a valid feature request.


dependency scope setting issues

Hi,
We are developing a tool to check whether the dependencies' scopes in maven are set rightly and reasonably.
Our tools have found some issues in your project about scope setting in maven' pom.xml file.

in bootique-junit5\pom.xml, org.junit.jupiter:junit-jupiter-engine scope should be test  instead of compile.

Please help us confirm whether the above reports are right and explain why it should set like these.
Thanks a lot.

Guys, there is a reason for that scope. And I think it is a bit presumptuous to ask us as open source developers to spend time debugging your tool.

sorry for bothering


[EMM-1353] Certificat error while uploading the device cert to EMM portal on windows

Feature: MDM Client/Server Steps to Reproduce: 1) Get the deive certificate (keystore file) installed on the device 2) Log into EMM portal with credentials  3) Add the .pem file of the device to the EMM portal (Dashboard>>Configuration Management>>Certificate Configurations 4) On the menu bar, click on 'Add Certificate' 5) In the add certificate page, enter the device ID and upload the .pem file for that device Actual Value: Certificate error on the portal while uploading a .pem file for a device on windows. Works fine on Mac Expected Value:Reference: https://wso2.org/jira/browse/EMM-1353

@sameerawickramasekara will work on this.


Conv2_cd block with 3x3 instead of 1x1 convolution

Hi,
Given how I understand the paper that introduces the central difference convolution (https://arxiv.org/pdf/2003.04092.pdf) and its reference implementation (https://github.com/ZitongYu/CDCN/blob/master/CVPR2020_paper_codes/models/CDCNs.py#L58) we sum up the kernel of the original 3x3 convolution and use this sum to multiply it to the input via a 1x1 convolution (which is then subtracted from the output of the original 3x3 convolution).
However, your implementation here (https://github.com/clks-wzz/FAS-SGTD/blob/master/fas_sgtd_single_frame/util/util_network.py#L118) seems to suggest that you tile the sum to a 3x3 kernel, which would mean that you multiply it with the input using a receptive field of 3x3 instead of 1x1!
Can you comment on whether my understanding is correct and if so, what the reasoning behind this change is compared to the original approach?

Thanks for your reminding. The CDCN is under verification in this project. We have fixed the difference.

Thanks for letting me know!


API Specifications Weekly - February 14th, 2022

This is a weekly public meeting to discuss the top API specifications, including, but not limited to OpenAPI, AsyncAPI, JSON Schema, GraphQL, gRPC, and Websockets. Discuss ideas on how we can better cross-pollinate information across the communities, develop common extensions, as well as tooling, collections, and other resources that benefit the community.
Agenda:

Updates - Doc provides the updates across specs from the week.
OpenAPI - Review the projects currently occurring as part of OAI operations, the future of the marketing meeting, and any other relevant items.

Marketing (Repo)
Tooling (Repo) (Kanban)
Curation / Syndication - What can we do create a curation network of content and information.

AsyncAPI - Talk about how we can better showcase what they are doing, follow their lead, and energize other areas based upon what is happening.
JSON Schema - Understand how we invest more in JSON Schema, but also vocabularies for AsyncAPI and OpenAPI, but also forms and others.
API Spec Toolbox - Keep this in the conversation so we can make sure and use it as the central gathering for this work and discussion.

Resources: adoption, discussions, extensions, issues, learning, news, people, podcasts, projects, sectors, services, specifications, tags, taxonomy, tools, tweets, videos
Bookmarklets - Adding new resources via browser bookmarklets, posting to intake repository.
Intake - This will be the repo where all new resources get added and can be curated and made available for publishing.

Google Summer of Code (GSOC) - Come up with some projects for GSOC.

AsyncAPI - Possible projects from AsyncAPI.

Please add any agenda items you’d like to discuss below, and we will meet weekly, and push forward projects, stories, collections, and tools to support our work.
Meeting:

February 14th, 2022 - 8:00 AM PST
Zoom

Readme.io OpenAPI compatibility chart https://docs.readme.com/docs/openapi-compatibility-chart


[Bug] Key_Shared subscription could deliver messages late and totalNonContiguousDeletedMessagesRange could exceed managedLedgerMaxUnackedRangesToPersist

Search before asking

[X] I searched in the issues and found nothing similar.

Read release policy

[X] I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version
This issue is present in master, branch-3.0 and branch-3.3 branch.
It seems to be present in all released Pulsar versions since #7105.
Minimal reproduce step
Start Pulsar 3.3.1 in Docker:
docker run --name pulsar-standalone --rm -it -e PULSAR_STANDALONE_USE_ZOOKEEPER=1 -p 8080:8080 -p 6650:6650 apachepulsar/pulsar:3.3.1 /pulsar/bin/pulsar standalone -nss -nfw

Clone, compile & run the test app (source code) that reproduces the issue:
git clone -b key_shared_issue-2024-08-19 --depth=1 https://github.com/lhotari/pulsar-playground
cd pulsar-playground
./gradlew build
java -cp build/libs/pulsar-playground-all.jar com.github.lhotari.pulsar.playground.TestScenarioIssueKeyShared

The test takes over 7 minutes to run and the final log lines show the results:
2024-08-19T15:31:35,983+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Done receiving. Remaining: 0 duplicates: 0 unique: 1000000
max latency difference of subsequent messages: 53071 ms
max ack holes: 27103
2024-08-19T15:31:35,983+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Consumer consumer1 received 259642 unique messages 0 duplicates in 445 s, max latency difference of subsequent messages 52959 ms
2024-08-19T15:31:35,983+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Consumer consumer2 received 233963 unique messages 0 duplicates in 417 s, max latency difference of subsequent messages 50930 ms
2024-08-19T15:31:35,983+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Consumer consumer3 received 244279 unique messages 0 duplicates in 437 s, max latency difference of subsequent messages 53071 ms
2024-08-19T15:31:35,983+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Consumer consumer4 received 262116 unique messages 0 duplicates in 443 s, max latency difference of subsequent messages 52651 ms

What it tracked that there was a 53071 ms latency spike between 2 subsequent messages.
The maximum value of totalNonContiguousDeletedMessagesRange observed during the test was
27103, which is more than the default value of managedLedgerMaxUnackedRangesToPersist.
The test will use a random namespace name in the format test_ns1723788349510. use this command to find out the namespace name:
pulsar-admin namespaces list public

After that, you can check the stats and stats-internal:
pulsar-admin topics stats-internal persistent://public/test_ns1723788349510/test
pulsar-admin topics stats persistent://public/test_ns1723788349510/test

There's a large amount of "ack holes" seen in the totalNonContiguousDeletedMessagesRange stats metric of the subscription sub.
What did you expect to see?
In an application that uses Key_Shared subscription:

messages should be delivered without unnecessary delays.
there shouldn't be a reason that there's a large amount of "ack holes" (totalNonContiguousDeletedMessagesRange) in the subscription so that it exceeds the default managedLedgerMaxUnackedRangesToPersist of 10000

The test application, https://github.com/lhotari/pulsar-playground/blob/key_shared_issue-2024-08-19/src/main/java/com/github/lhotari/pulsar/playground/TestScenarioIssueKeyShared.java

acknowledges all messages in the received order
in processing of each message, it contains a random processing delay of 100ms with 3% probability (this seems to be necessary to amplify the problem)

What did you see instead?
In an application using Key_Shared subscription:

messages got delivered messages late without a proper reason. In the repro app, a latency spike of over 50 seconds later is compared while comparing the end-to-end latency (from producing to consuming) of subsequent messages.
there were a lot of "ack holes". totalNonContiguousDeletedMessagesRange could exceed managedLedgerMaxUnackedRangesToPersist which means that subscription state would be lost in broker restart or topic load balancing event

Anything else?
This problem seems to reproduce only in the backlogged cases where there's already an existing backlog or when consumers aren't able to keep up with the producer. The problem is resolved after the consumers catch up, but the intermediate state is that messages get delivered late and totalNonContiguousDeletedMessagesRange could exceed managedLedgerMaxUnackedRangesToPersist during the catch up time. This seems to be completely unnecessary.
I made an experiment where I reverted some of the #7105 changes in this commit: https://github.com/lhotari/pulsar/commit/5665b112e3d477c2afd49cd1b21f0fb35defc1e3.
Here's how to build and run pulsar-standalone for this experiment (instead of running pulsar-standalone in docker):
git clone -b lh-key-shared-experiment-2024-08-19 --depth=2 --single-branch https://github.com/lhotari/pulsar
cd pulsar
mvn -Pcore-modules,-main -T 1C clean install -DskipTests -Dspotbugs.skip=true -Dcheckstyle.skip=true -Dlicense.skip=true -DnarPluginPhase=none
rm -rf data
PULSAR_STANDALONE_USE_ZOOKEEPER=1 bin/pulsar standalone -nss -nfw 2>&1 | tee standalone.log

after this, it's possible to run java -cp build/libs/pulsar-playground-all.jar com.github.lhotari.pulsar.playground.TestScenarioIssueKeyShared as explained before.
The results for this experiment:
2024-08-19T15:48:49,718+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Done receiving. Remaining: 0 duplicates: 0 unique: 1000000
max latency difference of subsequent messages: 922 ms
max ack holes: 711
2024-08-19T15:48:49,718+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Consumer consumer1 received 259642 unique messages 0 duplicates in 449 s, max latency difference of subsequent messages 606 ms
2024-08-19T15:48:49,718+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Consumer consumer2 received 233963 unique messages 0 duplicates in 449 s, max latency difference of subsequent messages 922 ms
2024-08-19T15:48:49,718+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Consumer consumer3 received 244279 unique messages 0 duplicates in 449 s, max latency difference of subsequent messages 835 ms
2024-08-19T15:48:49,718+0300 [main] INFO  playground.TestScenarioIssueKeyShared - Consumer consumer4 received 262116 unique messages 0 duplicates in 450 s, max latency difference of subsequent messages 716 ms

The observed problem is resolved in the experiment. The maximum latency spike is 922 ms compared to 53071.
There is no ack hole problem since maximum amount of observed ack holes (totalNonContiguousDeletedMessagesRange) is 711 compared to 27103 ack holes.
However it's likely that the correct fix is a broader change in how replays are handled in Key_Shared subscription.
--
It's possible that the issue observed in this report is related to #21199 and #21657 / #21656.
The PR #21656 is related to replays with Key_Shared subscriptions.
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

One observation is that this random delay in processing amplifies the problem:
https://github.com/lhotari/pulsar-playground/blob/092584a01cfe70f086cdd4b7b8c7aeb6cf3a54c6/src/main/java/com/github/lhotari/pulsar/playground/TestScenarioIssueKeyShared.java#L308-L315
I haven't yet verified it, but it seems that the problem is reduced when a messageListener is used for processing the messages. One possible explanation is that there's yet another queue in the client side when a messageListener is used, it's the executor's queue. I'll have to continue experiments to understand why.

I also tested with PIP-299 feature dispatcherPauseOnAckStatePersistentEnabled=true. It seems that the PIP-299 feature doesn't work properly so that it would keep "ack holes" below 10000. I can see that the value exceeds 10000. The highest value I observed in the test was "nonContiguousDeletedMessagesRanges" : 11097 . (These are the topic stats and internal stats.)

Interestingly, there's a related problem description in another context written by @Shawyeok: https://github.com/apache/pulsar/issues/15445#issuecomment-1118334156 .


Create EasyLinks from a RESTfull API

create a RESTfull API allowing to:

create an easy link (simple get)
create an easy link with custom settings (POST)
ask for an easy link (GET)
get details of an easylink (GET)
get QR code of an easylink (GET)
get visibility details of an easylilnk (GET)

Implemented


Automated testing repositories not easy to find

wehre is the link of the repository on github?

For Python https://github.com/AaltoRSE/PyTestingExample and for R https://github.com/AaltoRSE/RTestingExample

I think this is in this episode: https://coderefinery.github.io/testing/continuous-integration/


Example for Max and Split operator

Hi,
I am new to Caffe2. I'm wondering if there is any example for Max() and Split() operator (i.e. how to get the output of split() and how to input max() operator)? Thanks!
Yours,
Shangxuan

HI @ShangxuanWu ,
Did you find out how to use them?


Write Blog post

Write blog post
publish on social media
link github project to blog
update section "publications"
PR to update awesome list
PR to update zeebe docs
Camunda Developer Newsletter

See Bringing Cloud Native Process Automation to the Micronaut Framework


static-property-placement reports violations on non-React classes

Version 7.21.5
A static-property-placement violation is reported on a non-React class e.g.
class Foo {
    static context: {};
}

Should it not check that the class extends React.Component?

Indeed it should - the rule is using our component detection, so I'm not sure why it's warning here.


Add Sumit-Thakur

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

Lgtm currently only reviewing on phone so I would leave it for another maintainer to merge :)


Support DID and verifier attesation schemes

This PR adds support for two additional client_id_scheme(s)

did
verifier_attestation

DID
To be used wallet needs to add to its configuration an instance of SupportedClientIdScheme.DID.
Effectually, to do so, it has to provide a way to lookup verifier's public key using a  DID URL via DID resolution.
The later is out of scope of the library
Verifier Attestation
To be used wallet needs to add to its configuration an instance of SupportedClientIdScheme.VerifierAttestation.
To do so, wallet has to provide a JWSVerifier capable of verifying the signature of verifier attestation JWT from trusted issuers.
Closes #244
Closes #126

@babisRoutis java.net.URI is not the best option to parse DIDs/DIDURLs. For instance check here how Example 6 did:example:123?service=agent&relativeRef=/credentials#degree from did-core is parsed.


Creating a resource control object for a stack uses stack name as resource id

Description
Adding a resource_control via api for a stack has no impact if you use the id returned when the stack is deployed. You have to use the stack name as the resourceId.
Steps to reproduce the issue:
curl
   --verbose
   --header  'Authorization: Bearer ey...'
   --header 'Content-Type:  application/json'
   --header 'Accept:        application/json'
   --data '{
      "ResourceID": "THE_STACK_ID", // DOES NOT WORK! USE THE STACK NAME!
      "Type": "stack",
      "AdministratorsOnly": false,
      "Teams": [
        THE_TEAM_ID
      ]
    }'
   --request POST
   http://myhost:9000/api/resource_controls

Why do you consider this to be a bug?
Because the id you receive if you create a stack should be the resourceId. Right?
What did you expect to happen instead?
If the documentation requires a resourceId it should be the id not the stack name.
Technical details:

Portainer version: 1.16.5
Target Docker version: 17.12.0-ce
Platform: linux
Command used to start Portainer: Inside of a compose file:

  portainer:
    image: docker.repo.my/portainer/portainer:1.16.5
    ports:
     - "9000:9000"
    volumes:
     - /var/run/docker.sock:/var/run/docker.sock
     - ${NFS_SHARE}/portainer:/data:rw
    command: -H unix:///var/run/docker.sock
    dns:
     - ${DNS1}
     - ${DNS2}
    deploy:
     placement:
        constraints:
          - node.role == manager
     mode: replicated
     replicas: 1

Target Swarm version (if applicable): Docker Swarm matching server version.
Browser: Firefox Quantum 59.0.2 (64-bit)

I would really appreciate if "stack" would be a valid type... :-)

Hi @anthraxn8b

Because the id you receive if you create a stack should be the resourceId. Right?

No, in order to inherit the access control policy all the stack resources (services, containers, volumes...) we need to relay on an identifier that we can find via the Docker API in each resource. This identifier is the stack name in that case because we can find this information in the labels of each resource.

I would really appreciate if "stack" would be a valid type... :-)

It is, documentation has been updated recently.


Restructure Code - serperate applications from Lib

Hi,
I like your library, but I would encourage you to seperate your applications (demo server / client) from your library code.
Maybe create a new Project? Add some tools for debugging purpose?
BR

thanks for your feedback.
the application (which I consider only a small supplement to the library) used to be a separate project but I saw no benefits in that.
What would be the benefits in your opinion?

Hi, sorry for off-topic. @vogt31337  can you please take a look at https://github.com/java-native/jssc/issues/39? I know you worked on java-simple-serial-connector but I saw now other way to contact you. I will delete this comment in a few days. Sorry again for stealing this issue for this!


Configuration Docs Debugging

For anyone trying to work out how to use processors it would be a good idea to mention the debug processor and link to the troubleshooting guide that tells you how to use it. https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/troubleshooting.md

Thanks, @Wraith2! We are currently working to build out the troubleshooting docs as part of #4192. The third PR, which addresses troubleshooting and the debug exporter, should be going up this week.

Thanks @Wraith2 , @tiffany76 !
@Wraith2 feel free to take a look at the PR #4192 already and provide your feedback if this will introduce what you are looking for

It looks like that PR includes the presence of debug and how to use it.


When the Component that StateMachine bind to has be destroyed, it will output error.

There only have stateMachineList.Add(fsm), but don't have stateMachineList.Remove(fsm) when component has be destroyed.

It will throw a NullReference error


Environments without DB still require 1GB DB capacity?

This may be a duplicate of https://github.com/MicrosoftDocs/power-platform/issues/413.
In the "Create an environment without a database" section, it states:

Prerequisites: You need 1GB available database capacity.

Is this correct? If so, where does the need for available database capacity come from if there is no new DB created?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 00543757-56fc-9709-49be-16970ffbb774
Version Independent ID: c2c1da0b-c7a4-1128-f9de-1f2fae684a11
Content: Create and manage environments in the Power Platform admin center - Power Platform
Content Source: power-platform/admin/create-environment.md
Service: power-platform
Sub-service: admin
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

Thanks for your comment, @VitalyMCT. This issue has been assigned to the doc author for review.

@VitalyMCT
1GB is required even for environments created without a database. We don’t want to prevent customers from creating a database after they have created an environment (due to lack of capacity at a later time).


Improvements to y axis. Fixes #29, fixes #49, fixes #20

Changing the name as combining a few things in this PR to avoid conflicts

Quickly tested this, and really nice new features. One suggestion: should we add 1 to the min/max rank values so that Min rank 1 actually means 1 (instead of 2). Seems confusing to non-techies.

Looks good otherwise

Yeah, the ranks are the ranks as displayed I think (not zero indexed) so all good 🙂


fixes for yarn lock

Hi Folks,
I tried building the docker image but it failed due to yarn dependency issues
This file works for the docker image
Let me know if you want me to change anything

@samelamin Thanks for your great efforts! The lock file should be ignored by git. We will find out the proper version of each package later.

@wannam2049  thanks for your kind words!
does that mean the current lock file needs to be deleted from Git?

@wannam2049 thanks for your kind words!
does that mean the current lock file needs to be deleted from Git?

Your PR could be helpful for some other developers to save their time.


About alberto98fx's "Error-input array"

I met the same kind of error when the queryImage(212x142) is larger than trainImag(215x133).
Traceback (most recent call last):
  File "D:/Download/PythonSIFT-master/template_matching_demo.py", line 55, in <module>
    newimg[hdif:hdif + h1, :w1, i] = img1
ValueError: could not broadcast input array from shape (142,212) into shape (0,212)

And I exchange the two Image, then it works smoothly. So it seems to be trainImage's size cannot be smaller than queryImage's(Logically, it really should be like this)
Thx for ur share, it helps me a lot!

I may make a false conclusion. The size of two Images isn't the cause of this error. Here are my two test Images, and the error is:
Traceback (most recent call last):
  File "D:/Download/PythonSIFT-master/template_matching_demo.py", line 55, in <module>
    newimg[hdif:hdif + h1, :w1, i] = img1
ValueError: could not broadcast input array from shape (1706,1117) into shape (0,1117)

These two Images were taken separately by iphone.
I will follow ur tutorial to learn more about SIFT and the code. Try to see if I can find the reason. I would be very grateful if you can provide help at your convenience.

Hi @YangLwBUAA, thanks for your interest in this repo!
Thanks for posting the images you used. I will look into this and try to get back to you within a few days.


Adding other payment gateways and addition of a chatbot for user interaction

Hi @Archiita,
As I have no longer be working on this project, I am giving you the rights to modify content and you can keep working on this repository. Thanks to being part of #Spreadfreeeducationeverywhere.


Feature-Request: Open Datepicker via Button / Icon (attribute mode?)

Nice datepicker, thank you for this!
It would  be nice when the picker could be opened via a datepicker-icon or a button.
If I could pass an selector of dom-element which then open the calendar I would be happy.

@tobigit
This is a angular directive, so you could use it in a button or a icon.

Hello @DanielYKPan, do you have an exemple how to do this behaviour ?
The following code doesn't work:
<md-icon (click)="datePicker1.click()" class="detailPickerIcon">date_range</md-icon>
<input #datePicker1 class="detailPicker" [value]="momentVariable | date:'medium'" [(ngModel)]="momentVariable" dateTimePicker [hourTime]="'12'"
      readonly [maxMoment]=pickerToday (onChange)="setMoment($event)" [disabled]="!printerService.isCurrentPrinter">

Thank you !

It seems like this doesn't work in the latest version... can anyone confirm this?

I made a simplified plunkr to reproduce this issue. Can you help me?

I fixed it by adding a button <button type="button" class="btn btn-default" (click)="departureTime.onInputClick($event);"> where departureTime is the reference to the datepicker. (#datePicker1 in your example, @lutchit )


Install the package before managing the $conf_dir for slave

Fix issue with rpmnew file
mesos-slave[23463]: Failed to load unknown flag 'work_dir.rpmnew'

Thanks!


Update PeerTaskInstancePriorityQueueTest.java

change TaskInstance taskInstanceMediumPriority = createTaskInstance("high", Priority.MEDIUM); to TaskInstance taskInstanceMediumPriority = createTaskInstance("medium", Priority.MEDIUM);

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

Merging #5314 (b225f46) into dev (87588ca) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #5314   +/-   ##
=========================================
  Coverage     48.43%   48.44%
+ Complexity     3814     3813    -1
=========================================
  Files           570      570
  Lines         24112    24112
  Branches       2798     2798
=========================================
+ Hits          11679    11681    +2
+ Misses        11350    11347    -3
- Partials       1083     1084    +1

Impacted Files
Coverage Δ
Complexity Δ

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

...er/master/processor/queue/TaskResponseService.java
71.23% <0.00%> (+4.10%)
8.00% <0.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 87588ca...b225f46. Read the comment docs.


The far member of PerspectiveProjection is irrelevant

The far member of PerspectiveProjection is irrelevant, because the far plane is at negative infinite Z
https://github.com/bevyengine/bevy/blob/989fb8a78d2ca6e3fe6fb1ccd7d79ea88868b8c7/crates/bevy_render/src/camera/projection.rs#L25

maybe related to https://github.com/bevyengine/bevy/pull/4457

We could still cull meshes to a fake far plane. I just chose not to to preserve behaviour at the time I think. I’m not sure whether we should or shouldn’t cull to a fake far plane. We do for point lights but not for meshes. We could make it optional but then I don’t know what the default should be. I kind of feel like we could make it an Option and if present then we cull to it, if not, we don’t.

Yeah I think providing optional configuration for people to cull at a given distance makes a lot of sense.

I've had a go at this in #5282
(The above is a bullet point because that's the only way I know to force github markdown to show the linked PR title.)

I have been thinking of culling smaller objects faster than large objects.  This way large buildings would still be visible, but smaller objects inside or around it wouldn't be rendered.
Would it be difficult to do that in the far-plane culling logic?

What do you mean by faster? All meshes are chilled against the visible volume every frame.

Sorry, by "faster" I mean at a closer distance.  A small object (scale dimensions < 1.0) will not be as visible (size on screen) at a distance of 50.0 from the camera vs a larger object (scale dim. > 1.0).
I have a 3d scene that has +40,000 objects (over 100,000 ECS entities).  The object meshes are generated from primitive profile/path parameters and can have different textures on different faces.   So right now one object could have multiple meshes.
I had tried enabling the far plane culling like in your PR to see if it would help with FPS.  It does, but there is a hard cut-off, where even large objects go invisible.
I am now using an adaptive culling based on distance and the Transform.scale of the mesh.  For the scene that I have tested with (large buildings with many smaller objects inside), it allows the buildings that are far away to still be visible while hiding the smaller objects that are not as noticable (even when the build has lots of windows).


How to set the tgt mask in the decoder of ARTRackv2?

How to set the tgt mask in the decoder of ARTrackv2 after removing intra-frame autoregression?

We have open the inference code of ARTrackV2, you can see that in the README, a Temporal Code is released. Then the mask of ARTrackV2 is in lib/base_backbone.py, the whole pipeline is in that py file.