Undoing a change in a texture region won't reflect in the region editor.

Operating system or device - Godot version:
Ubuntu Linux 16.04, Godot version fea1fb0925142c3279fd3afaf27e80e78cd2e1e8
Issue description (what happened, and what was expected):
Changing a texture region and then undoing it won't change the selection rectangle. Closing and opening the region editor again or changing to other tools in the bottom dock (animation editor/debugger/output) won't reflect the change as well. Only changing to another scene and back will show the change.
This could be misleading as it makes it seem like region changes aren't being undone unless one is aware of this bug.
Steps to reproduce:
Open a texture region editor and click somewhere to change the current region, then undo. Change to other tools in the bottom dock and back and it will still show the changes before undo. Change to another scene and return to the one with the undone region, now it refreshes properly.

@Hinsbart Looks like it's still happening after updating.

I include a video as demonstration (which also showcases a strange issue where apparently scene changes count towards undo buffer, I'll open a separate issue for it).
http://kuuv.io/i/EXxge2s.mp4

@hetdegon mhh, I can't reproduce this anymore.
And it looks like I'm doing the same as in your video: make changes to the region then press ctrl+z..
Will investigate this further.

Strange. If there's anything I can do to help, please let me know.


Contributor information is missing, compared to IETF’s misc source

As an example:

Here we have a contributor: https://github.com/ietf-tools/relaton-data-misc/blob/main/data/reference.W3C.xml-c14n.yaml
Here (seemingly the same resource) we don’t have any contributors: https://github.com/ietf-tools/relaton-data-w3c/blob/main/data/xml-c14n.yaml

Since I don’t think we’d somehow lose contributor info, I presume this is caused by missing data in authoritative data supplied by W3C?

See https://github.com/relaton/relaton-data-w3c/issues/6
This is resolved -- W3C has responded that they do NOT provide authoritative contributor and contact information from their API -- they do not store them. We should just omit them from now on.

This is a tricky situation for BibXML service. We could obsolete those misc items and map them to authoritative ones, but missing data makes it likely to cause complaints. Just as a note (@ronaldtse)

@strogonoff agree with your note. I just don’t know what the best way to deal with this is.
The problem only applies to the W3C references in the misc dataset, as the bibxml4 dataset does not provide contributor information anyway.
As a last resort, we can “merge” the data between misc and W3C’s data but we don’t really want to do this for many reasons.
I think we should just discourage people from using misc.

I think we should just discourage people from using misc.

Just for the record, BibXML service users don’t really choose a source to use. What we do is we check all available sources and we put together an item based on that data. So it’s on us if we want to not use misc (just we can’t do it when it contains data in excess to what authoritative sources make available).
Here’s how this entry looks: https://dev.bibxml.org/get-one/by-docid/?docid=W3C+xml-c14n&doctype=W3C. The info is built by combining both misc and w3c entries (per-source data at the bottom), since they are considered to represent the same resource. Same happens with xml2rfc path http://dev.bibxml.org/public/rfc/bibxml2/reference.W3C.xml-c14n.xml. As a result, users see the contributor that comes from misc, even though W3C doesn’t provide that data.

As a last resort, we can “merge” the data between misc and W3C’s data but we don’t really want to do this for many reasons.

The way the service works is more or less by merging the data when user requests it, it happens at runtime (not at source level) so I hope the reasons you had in mind don’t apply here?


change color of radar points in 3D panel

In my Webviz, the color of online radar points is only white with black background,
how could I change the color to "Rainbow" like the Demo from Webviz.
Ps, when the key "colorMode", which is copied from Webviz demo, was add into Json of panel setting , nothing changed.
"settingsByKey": {
"t:/rslidar_points": {
"colorMode": {
"mode": "rainbow",
"colorField": "ring"
}
}
}

@sky4133  if you color by ring, you'll need to make sure this field is actually available in the lidar data. Otherwise, you can always choose to color by other available fields.

thank you !!! it works


Support for local builds (fixes #33)

To activate, run ./gradlew downloadDependencies, then copy your local version of Xenon into the lib folder, then run ./gradlew localJar. This will create a build/libs/Xenon-examples-testing.jar. This way you can run the nightly build of Xenon in your tests.

Good stuff. FYI I described an other option here.


Playback Capture

Hi Nickolay,
First I really much appreciate you for such a great effort.
I am using your demo app for continuous speech recognition with Microphone. I experienced about 80% accuracy on Audio to Text transcribe from a video/audio playing in android device or outside. However in-person conversation, it shows much poor accuracy. How can I overcome this problem?
There are few other questions. Can you please entertain them?

Is there a role of accent? How can an accent be used like North American English Accent?
Is it possible to use audio input without a microphone.  Suppose we capture audio from other apps internally without microphone, how can we put this captured data (audio buffers) as input to Kaldi Android App to get transcribed info back?

Kind regards,
Muhammad Rashid

Is there a role of accent? How can an accent be used like North American English Accent?

Accuracy tuning for mobile device is complicated and might require analysis of the data, training of the model, etc. Current model is pretty basic and optimized for realtime. More advanced models could be more accurate. Also, realtime conversations are hard to transcribe, much harder than broadcast or dictation.

Is it possible to use audio input without a microphone. Suppose we capture audio from other apps internally without microphone, how can we put this captured data (audio buffers) as input to Kaldi Android App to get transcribed info back?

Yes, it is demonstrated in the code, see
https://github.com/alphacep/kaldi-android-demo/blob/e4053d67ff626f0e24e5e36fdcf1360c67b6199d/app/src/main/java/org/kaldi/demo/KaldiActivity.java#L235
https://github.com/alphacep/kaldi-android-demo/blob/e4053d67ff626f0e24e5e36fdcf1360c67b6199d/app/src/main/java/org/kaldi/demo/KaldiActivity.java#L115

Is there a role of accent? How can an accent be used like North American English Accent?

Accuracy tuning for mobile device is complicated and might require analysis of the data, training of the model, etc. Current model is pretty basic and optimized for realtime. More advanced models could be more accurate. Also, realtime conversations are hard to transcribe, much harder than broadcast or dictation.

Is it possible to use audio input without a microphone. Suppose we capture audio from other apps internally without microphone, how can we put this captured data (audio buffers) as input to Kaldi Android App to get transcribed info back?

Yes, it is demonstrated in the code, see
https://github.com/alphacep/kaldi-android-demo/blob/e4053d67ff626f0e24e5e36fdcf1360c67b6199d/app/src/main/java/org/kaldi/demo/KaldiActivity.java#L235
https://github.com/alphacep/kaldi-android-demo/blob/e4053d67ff626f0e24e5e36fdcf1360c67b6199d/app/src/main/java/org/kaldi/demo/KaldiActivity.java#L115

Thank you very much for your kind response.
Yes, I found your referred code. By going through it again (although before I thought it only works for audio file that already kept in raw/asset folder).
KaldiRecognizer rec = new KaldiRecognizer(activityReference.get().model);
InputStream ais = ... // It can be from any audio source either from other apps like Youtube audio or from file on SD card/Gallery/ or inside app in assets/raw directory.
if (ais.skip(44) != 44) {
return "";
}
byte[] b = new byte[4096];
int nbytes;
while ((nbytes = ais.read(b)) >= 0) {
rec.AcceptWaveform(b, nbytes);
}
So it means we can give any Input stream buffer from any audio playing either inside current app or capturing from other apps (YouTube etc) silently without microphone by using android's PlaybackCapture APIs (android 10 support only) or other third party APIs, etc.
Kinldy confirm?

Correct, but for longer file processing the work should be a bit different, it should use the voice activity detection as python API:
while ((nbytes = ais.read(b)) >= 0) {
    if (rec.AcceptWaveform(b, nbytes))
        System.out.println(rec.Result())
   else
        System.out.println(rec.PartialResult());
}
System.out.println(rec.FinalResult());

Okay, thanks a lot.

Feel free to reopen

Feel free to reopen

I am stuck with a scenario. I need your help.
I can get byte array of audio data continuously from playback. Each time I receive 1024 bytes. How can I pass this data continuosly to Kaldi Android Speech APIs in order to transcribe it. Suppose I am getting audio data inside app by using  android Visiualizer class.

I can get byte array of audio data continuously from playback. Each time I receive 1024 bytes. How can I pass this data continuosly to Kaldi Android Speech APIs in order to transcribe it. Suppose I am getting audio data inside app by using android Visiualizer class.

in constructor or some other init:
Model model = new Model(assetDir.toString() + "/model-android");
KaldiRecognizer rec = new KaldiRecognizer(model);

when you recieve bytes
    if(rec.AcceptWaveform(b, nbytes)) {
        Log.d(TAG, rec.PartialResult());
    } else {
        Log.d(TAG, rec.Result());
    }


optimize all ZST allocations into one single allocation

fixes #19
Visual confirmation in priroda. You can see that all the alloc_ids are 0 for zsts

Could you add a const for the ZST alloc ID instead of using 0 everywhere?

addressed all comments and rebased


docs: refactor to improve legibility

The use of "not more" with the reverse ordering of the sentence made this difficult to parse. After reversing the order and removing negation, the surrounding paragraphs were updated to match the style.
What issue does this pull request resolve?
None
What changes did you make?
Restructured some paragraphs in the docs
Is there anything that requires more attention while reviewing?
Please validate that this new reordering aligns with the functionality as I have only just begun using this tool.

Thanks for the contribution @blottn, I can see what you mean about the original wording. I will take a look at this and see, I'll also have to review the actual functionality to ensure it matches.


Get lighthouse score to 99+

Tested it again in an Incognito browser and it's a 100 :/

Tested it again in an Incognito browser and it's a 100 :/

Tested it again in an Incognito browser and it's a 100 :/

Tested it again in an Incognito browser and it's a 100 :/

But it takes Aaaages to load on mobile?!

But it takes Aaaages to load on mobile?!

DNS issue on namecheap


Separate gem directories for different Rubinius versions

It seems gems for all versions of Rubinius are put in ~/.gem/rbx/2.1.0. Would it make sense to separate them out a bit more?

In e9e81df20e9b821f3cdb13c946e8bdd368453e22 we added support for detecting RUBY_ENGINE_VERSION and use that in the GEM_HOME (falling back to RUBY_VERSION if RUBY_ENGINE_VERSION isn't present). I just need to work on releasing 0.4.0.


Build should use poetry-core

You are currently relying on the full blown poetry package in your build-system. The necessary components have however been extracted into poetry-core and you should migrate your pyproject.toml to use that.
Please see https://github.com/python-poetry/poetry-core#usage.

Thank you for reporting this issue.
It has been fixed with version 2.2.0 that I released on PyPI just now.


[Package Manager Window] Error adding package<EMAIL_ADDRESS>aborted

Hello!  I tried to install cesium for unity1.5.0 many times, but I always failed. The warning is"[Package Manager Window] Error adding package<EMAIL_ADDRESS>aborted"
I followed the official website guide to enter the relevant url and scope, and confirmed that I can access github.com normally. What could be the cause of the problem?

Perhaps your network requires a proxy to access github, and Unity isn't using it?
The direct link to the v1.5.0 package is here:
https://github.com/CesiumGS/cesium-unity/releases/download/v1.5.0/com.cesium.unity-1.5.0.tgz
I've just confirmed that it is working correctly. So you can always download and install it manually if you need to.
I'm closing this because I don't think there's anything actionable for us here.


Version 2.4 announcement blog post - picture issues

Where to find the issue
DE: https://www.coronawarn.app/de/blog/2021-06-24-cwa-version-2-4/
EN: https://www.coronawarn.app/en/blog/2021-06-24-cwa-version-2-4/
Describe the issue & Suggested change
For DE:

The screenshot https://www.coronawarn.app/assets/img/blog/2021-06-24 CWA 2.4 Testzertifikat/testzertifikat_geburtstag.png is broken. It should be replaced.

For EN:

One picture is missing. It should be added.
The screenshot https://www.coronawarn.app/assets/img/blog/2021-06-24 CWA 2.4 Testzertifikat/request-certificate-birthday.png is broken. It should be replaced.

@Ein-Tim

The strange birthday images are also in the screenshot section

https://www.coronawarn.app/assets/screenshots/2-4/en/ios/iPhone 11 Pro-submissionflow_screenshot_test_certificate_entered_birthday.png
https://www.coronawarn.app/assets/screenshots/2-4/de/ios/iPhone 11 Pro-submissionflow_screenshot_test_certificate_entered_birthday.png

For the missing picture in https://www.coronawarn.app/en/blog/2021-06-24-cwa-version-2-4/ the HTML is missing a filename

The equivalent code in https://www.coronawarn.app/de/blog/2021-06-24-cwa-version-2-4/ shows:

Another picuture issue:
The disease or agent targeted is named: Schneider, Andrea - but should be Sars-Cov-2, I guess...
DE:
https://www.coronawarn.app/assets/img/blog/2021-06-24 CWA 2.4 Testzertifikat/zertifikat-qr-code.png
EN:
https://www.coronawarn.app/assets/img/blog/2021-06-24 CWA 2.4 Testzertifikat/certificate-qr-code.png

😉

Maybe thats a new disease @vaubaehn? 😉
Thanks for spotting, I'll update the title of this issue so that it reflects that it's also about issues with the screenshots page and not only with the blog.

https://www.coronawarn.app/assets/screenshots/2-4/en/android/CertificatesFragment_pending.png
shows "Error during certificate retrieval" 🙁

The same problem in the German language screenshot
https://www.coronawarn.app/assets/screenshots/2-4/de/android/CertificatesFragment_pending.png

There is also a 6 week old issue with the screenshots in 2.2, 2.3 and now 2.4 https://github.com/corona-warn-app/cwa-website/issues/1257.
The 2.4 Android screenshot https://www.coronawarn.app/assets/screenshots/2-4/en/android/rat_2.png hardly matches the 2.4.2-RC0 app layout at all.

These issues persist even after the update of the screenshots with the release of version 2.5.

I consider this as obsolete and will open a new issue reg. the screenshot page soon.


add FileUrl type for file:// schemes, add host_required parameter

Change Summary

Add host_required parameter:True in AnyUrl, False in RedisDsn, and FileUrl (new Model).
Add relevant tests for AnyUrl, FileUrl
Document changes in docs

Related issue number
Fixes #1983 .
PR Discussion history in #2050 (Opened this as I assume closed PRs are not checked for updates)
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI & Coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

@vgerak Can you resolve conflicts please?

@vgerak Can you resolve conflicts please?

Done. Editor also removed some trailing white spaces from the file, but from my checks the resulting HTML is the same. I can revert those changes if needed.

@vgerak can we handle the JDBC URLs as part of this diff ? example using any URL like this ""jdbc:mysql://localhost/test" "invalid or missing URL scheme (type=value_error.url.scheme). Looks like having "jdbc:mysql:" multiple schemes causing this issue?

Thank you!


Create Front-End for Login/Registration functionality

Now back-end is implemented this is the next step. I plan on using React with Material UI to implement the front end of this project.

Frontend for login and registration is now complete, will need tweaks later on in development.


Convert-a-Card: Browse results feature needs a way of downloading matched/unmatched cards

This used to happen through the analysis server.

This will be handled in https://github.com/LibCrowds/vue-pybossa-frontend/issues/277


Demo is broken - Can't bind to 'options'.  SetTimeOut() doesn't compile

Demo is not working.  I'm using angular-cli.  I followed all of the instructions on the demo.  What is up with all of the demos for Angular2? They are all broken.  Yours, ng-upload by Valor software.  Even the stackoverflow's nice example referenced here is broken as well.  Is there something wrong with my angular-cli?  I can't get not one example on the web regarding angular2 and fileuploads to work.  Please help!  I'm using the vanilla out-of-box CLI provided on the Angular2's website.
Here is the response from Chrome:
Can't bind to 'options' since it isn't a known property of 'div'. ("
][options]="options"
(onUpload)="handleUpload($event)"
[ngClass]="{'file-over': hasBaseDro"): NgxUploaderComponent@2:6
Can't bind to 'options' since it isn't a known property of 'input'. ("
class="hidden"
ngFileSelect
[ERROR ->][options]="options"
(onUpload)="handleUpload($event)">
Browse
"): NgxUploaderComponent@11:11 ; Zone:  ; Task: Promise.then ; Value:

I got the same error
Unhandled Promise rejection: Template parse errors: Can't bind to 'options' since it isn't a known property of 'div'. ("
][options]="options"       (onUpload)="handleUpload($event)"       [ngClass]="{'file-over': hasBaseDro"): AppComponent@2:6 Can't bind to 'options' since it isn't a known property of 'input'. ("            class="hidden"            ngFileSelect            [ERROR ->][options]="options"            (onUpload)="handleUpload($event)">     Browse "): AppComponent@11:11 ; Zone: <root> ; Task: Promise.then ; Value: SyntaxError {__zone_symbol__error: Error: Template parse errors: Can't bind to 'options' since it isn't a known property of 'div'. ("<d…, _nativeError: ZoneAwareError, __zone_symbol__currentTask: ZoneTask, __zone_symbol__stack: "Error: Template parse errors:↵Can't bind to 'optio…ttp://localhost:4200/polyfills.bundle.js:6423:35)", __zone_symbol__message: "Template parse errors:↵Can't bind to 'options' sin…pload($event)">↵    Browse↵"): AppComponent@11:11"} Error: Template parse errors: Can't bind to 'options' since it isn't a known property of 'div'. ("
][options]="options"       (onUpload)="handleUpload($event)"       [ngClass]="{'file-over': hasBaseDro"): AppComponent@2:6 Can't bind to 'options' since it isn't a known property of 'input'. ("            class="hidden"            ngFileSelect            [ERROR ->][options]="options"            (onUpload)="handleUpload($event)">     Browse "): AppComponent@11:11     at SyntaxError.ZoneAwareError (http://localhost:4200/polyfills.bundle.js:6869:33)     at SyntaxError.BaseError [as constructor] (http://localhost:4200/vendor.bundle.js:64389:16)     at new SyntaxError (http://localhost:4200/vendor.bundle.js:5723:16)     at TemplateParser.parse (http://localhost:4200/vendor.bundle.js:17589:19)     at JitCompiler._compileTemplate (http://localhost:4200/vendor.bundle.js:47585:68)     at http://localhost:4200/vendor.bundle.js:47468:62     at Set.forEach (native)     at JitCompiler._compileComponents (http://localhost:4200/vendor.bundle.js:47468:19)     at createResult (http://localhost:4200/vendor.bundle.js:47350:19)     at ZoneDelegate.invoke (http://localhost:4200/polyfills.bundle.js:6211:26)     at Zone.run (http://localhost:4200/polyfills.bundle.js:6003:43)     at http://localhost:4200/polyfills.bundle.js:6590:57     at ZoneDelegate.invokeTask (http://localhost:4200/polyfills.bundle.js:6244:31)     at Zone.runTask (http://localhost:4200/polyfills.bundle.js:6043:47)     at drainMicroTaskQueue (http://localhost:4200/polyfills.bundle.js:6423:35) consoleError @ zone.js:522 handleUnhandledRejection @ zone.js:527 _loop_1 @ zone.js:562 drainMicroTaskQueue @ zone.js:566

me too

Hey guys, I had the same issue in Angular 2, and I solved it by importing the NgUploaderModule in the parent module, and not the grandparent module (relative to the module where I wanted to use the functionality of the file uploader).
My structure is as follows:
├ GrandparentModule - do not import here
├── ParentModule  - add to imports here
│----├── TargetModule - directives accessible here

@zerefel solution worked for me.

@zerefel's solution worked for me, too.

I still have this issue, @zerefel's solution didn't work for me. Anyone else have this problem?


Restructure the "Conf interval" dropdown list #99

Pull Request Testing

[x] Describe testing already performed for these changes:
Run test_line+plot.py, tested using UI

[x] Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]

[x] Do these changes include sufficient testing updates? [ No]

[x] Will this PR result in changes to the test suite? [No]
If yes, describe the new output and/or changes to the existing output:

Pull Request Checklist
See the METplus Workflow for details.

[x] Complete the PR definition above.
[x] Ensure the PR title matches the feature or bugfix branch name.
[ ] Define the PR metadata, as permissions allow.
Select: Reviewer(s), Project(s), and Milestone
[ ] After submitting the PR, select Linked Issues with the original issue number.
[ ] After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
[ ] Close the linked issue and delete your feature or bugfix branch from GitHub.

I updated line_expected.png. The test should pass

OK, I just approved it.
Thanks,
Minna
Minna Win
National Center for Atmospheric Research
Developmental Testbed Center
Phone:<PHONE_NUMBER>
Fax:<PHONE_NUMBER>
Pronouns: she/her
On Tue, Apr 13, 2021 at 8:46 AM Tatiana Burek @.***>
wrote:

I updated line_expected.png. The test should pass
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/dtcenter/METplotpy/pull/102#issuecomment-818794929,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4UJHTEFQ6RABR2SUA42IDTIRKNNANCNFSM42NHW2TA
.


[5.7][stdlib] Fix String indexing edge cases, anomalies & validation bugs

Cherry-picked from #41417 and #42385.

Explanation:  This addresses a multitude of index validation and semantic issues in the collection implementations of String, Substring, and their Unicode Scalar, UTF-8 and UTF-16 views, by implementing additional runtime index validation, as needed; this includes tracking the expected encoding of String.Index offsets within the index value itself.
Scope: String indexing and grapheme breaking. This changes the runtime behavior of code that passes invalid indices to methods of the types above. Code that previously resulted in unexpected traps, out-of-bounds memory accesses and/or nonsensical results will now behave more consistently, either gracefully substituting a suitable valid index or generating a clear, nondeterministic trap.
Issues: rdar://89482809
Risk: Medium/high. Care was taken to ensure backward/forward compatibility whenever practical (even including code that violates documented preconditions), but this is a large change.
Testing: Additional, extensive unit tests as well as local binary compatibility testing.
Reviewer: @milseman @Azoy @stephentyrone

For more detailed list of changes, see the original description of #41417, expandable here by clicking on the sections below.

MotivationMotivation
Swift String and its views generally work very reliably as long as we keep to only applying indices to each string view that come directly from it.
This PR fixes issues that happen when we don’t. There are three major sources of such issues:
SE-0180 String Index Overhaul
Unfortunately, back in Swift 4, SE-0180 unified the index types of string views, eliminating distinct indices and explicitly allowing an index from one view to be applied to any other (of the same underlying string), without limit.
The proposal (very loosely) defined the intended behavior to organically arise as if a new string was constructed from the underlying code units that are addressed by the indices given. This was never truly implemented — while we did get the unified String.Index type, the semantics of using a “lower-level” index on a “higher-level” collection (like using an arbitrary index in the UTF-8 view on the character-level String type itself) were never formally specified, and the behavior that actually emerged from the implementation does not match what the proposal intended (or any reasonable definition of expected behavior).
In Swift 5.1, character- and scalar-based views (String, Substring, String.UnicodeScalarView, Substring.UnicodeScalarView) started rounding indices that address sub-scalar positions down to the nearest scalar boundary, which addressed the most egregious correctness issues. (Such as the ability to create strings with invalid encodings.) However, we have not yet tackled the case where sub-character indices are applied to character views: the String implementation in Swift 5.6 is still full of unexpected/undesirable/nonsensical behavior in this area.
let s = "Hello,\r\nworld!"

let i = s.startIndex
let j = s.unicodeScalars.index(s.startIndex, offsetBy: 7) // between \r and \n

print(s.distance(from: j, to: i)) // -7
print(s.distance(from: i, to: j)) // 💥 Fatal error: String index is out of bounds

let ss = s[i ..< j]
print(ss.count) // 💥 Fatal error: String index is out of bounds

As discussed on the forums, the right way to fix these issues is to either trap when these indexing operations are given unaligned indices, or to automatically round every index down to the nearest Character boundary. The latter option seems less surprising and probably more compatible with existing code, so that's what this PR implements.
Accidental use of actually invalid indices
A separate source of issues in this area (unrelated to SE-0180) is the fact that indices don’t currently keep track of whether the numerical offset that they contain counts UTF-8 or UTF-16 code units. (Some strings bridged over from Cocoa can be encoded in UTF-16, while most others are in UTF-8.) This is usually not a problem, except when people mistakenly apply a UTF-16 index to a UTF-8 string (e.g., after a call to makeContiguousUTF8). This is always an error, as the index is definitely invalid in this case; however, this error is currently undiagnosed.
var str = (some UTF-16 string bridged over from Cocoa)
let i = str.firstIndex(of: “X”)!
str.makeContiguousUTF8() // documented to invalidate all indices
// str is now UTF-8 encoded
print(str[i]) // illegal, i isn’t valid any more — but it still tends to succeed.
              // For ASCII strings, it even returns a value that looks right!

This can stay undiagnosed for a very long time — until someone tries to run this code on a non-ASCII string, and gets surprised by getting a nonsensical result. The upshot is that there is a potentially large amount of Swift string processing code out there with dormant bugs of the form above.
The best way to improve this situation is to add bookkeeping to indices so that we record their encodings, allowing us to detect such problems and diagnose and/or recover from them. (For example, in the example above, we could either trap, or just emit a runtime warning and return the expected value by transcoding the string on the fly.)
This PR assigns two flag bits in each string index to track its encoding, and automatically transcodes UTF-16 indices if they are applied to an UTF-8 string, making the (still invalid!) code above produce consistently good results. No such conversion is done in the opposite direction, as we don't typically convert UTF-8 strings to UTF-16.
Small oversights
String has a large API surface area, and some entry points are a bit behind when it comes to index validation. For example:

String.replaceSubrange does not always fully validate/sanitize its input indices, allowing the creation of invalid strings
Substring.replaceSubrange does not always preserve the location of its startIndex/endIndex (when the substring is a UTF-16 string bridged over from Cocoa)
String.index(before:) may perform out of bounds access to memory
String.distance(from:to:) may perform out of bounds access to memory
String.UnicodeScalarView may perform out of bounds access to memory in indexing methods
too many similar issues to precisely list here

This PR fixes these by thoroughly reviewing every String API that takes an index and carefully adding missing validation steps, as needed.

Summary of the changes applied
Summary of the changes applied

The .index(after:), .index(before:), index(_:offsetBy:), index(_:offsetBy:limitedBy:), and distance(from:to:) methods on String and Substring now start by rounding their input indices down to the nearest Character boundary. This avoids SE-0180-related anomalies, such as distance not being well-defined on every pair of indices.

To prevent this from causing a significant performance regression, String.Index now has a flag bit that tracks whether the index is Character-aligned, i.e., whether it addresses a location that falls on an extended grapheme cluster boundary. This bit is set on indices that are returned from any method that guarantees Character alignment. (Such as the methods listed above.)

SE-0180 explicitly allows exotic Substrings whose startIndex isn't Character aligned, and (loosely) prescribes how they should behave. This PR finally implements this behavior, so exotic substrings now behave in a well-defined, predictable way: they are now always valid collections, containing characters that "arise organically by applying the usual Unicode grapheme breaking rules" to the scalars that they contain. (And only the scalars they contain -- meaning that no data outside the substring bounds is used to determine grapheme breaks within it. This means that exotic substrings sometimes do not share their characters with the base string.)

The Character-alignment bit in String.Index always reflects grapheme breaking results within the entire string. Exotic substrings cannot set or use this bit, as their grapheme breaks may not match with the base string. Therefore, exotic substrings always do a full alignment dance, which makes their indexing operations quite slow. (I expect they are currently about three times slower than regular substrings, although this can vary.) This is much preferable to random trapping or other nonsensical behavior.

String.Index now includes two extra flag bits that track whether the encoded offset value is measured in UTF-8 or UTF-16 units. This is used to detect if someone attempts to use a UTF-16 index on a UTF-8 string, or vice versa.

When a UTF-16 index is applied to a UTF-8 string, string operations now automatically transcode the offset value to UTF-8 units. This can be quite slow, but it produces consistently good results in the case of someone keeping indices around after mutating a bridged string. This is preferable to trapping, to avoid breaking (invalid) code that appeared to work correctly before.
We do trap if a UTF-8 index is applied to a UTF-16 string, as we don't implicitly convert strings in that direction. This case (from what I've seen so far) never happens "organically". This carries a slight risk of a binary compatibility issue -- if some Swift applications did get this wrong, then they will now crash. If this happens, we'll be able to adjust the trap to e.g. make it only happen if the app was built with a newer SDK.
Some indices may originate from older versions of the stdlib, in which case they won't have either of these bits set. In this case, we revert to assuming the index has the correct encoding, like before.
Some indices may have both their UTF-8 and UTF-16 flags set. This isn't an error -- some indices work in either encoding. For example, every startIndex is encoding-independent. (And so are indices in ASCII strings, although this PR doesn't actually make use of this.)

String's ABI allows, but the stdlib does not currently implement, non-contiguous UTF-8 encoded string forms. (We only have UTF-16 encoded foreign forms -- as used by some bridged NSString instances.) To continue allowing future versions of the stdlib to introduce UTF-8 foreign strings, this PR assigns a new flag bit in the large string representation that signals this potential future case. This bit is used by the (inlinable!) encoding validation logic above.
If in the future we decide to give up on the idea of UTF-8 foreign strings, we can then stop checking this bit in a future stdlib release, slightly simplifying logic. (However, this PR irrevocably assigns this bit in the ABI, so we won't be able to reclaim it for another use later.)

In each string view, methods that take indices now consistently perform the following index validation steps, in this precise order:

For each supplied index i, ensure that i's offset uses the expected coding units. Mitigate mismatches by transcoding the index or trapping, as described in point 5 above.
Perform bounds checking to ensure that i addresses a location within the string's storage.
[Only in String, Substring and their UnicodeScalarViews] Round down i to the nearest Unicode scalar boundary.
[Only in String and Substring] Round down i to the nearest Character boundary.
In index(before:), ensure that the resulting i is above the startIndex.

Of particular note is that bounds checking must come before scalar/character alignment, or the alignment operations may end up accessing out-of-bounds memory. index(before:) is a tricky edge case, as it needs an i > startIndex check that must not be done as part of regular bounds checking -- because alignment operations may move i to the startIndex, invalidating the result of the earlier check.

Performance impact
Performance Impact
Full index validation takes 2-5 steps and at least as many branches. As is often the case, ensuring that we do things correctly (and never access out-of-bounds memory) tends to slow things down a bit. I'm pretty sure the performance regressions can be mostly/entirely mitigated. This PR already implements some mitigations, with more likely coming later:

The new character-alignment bit in string indices avoids having to do a full random-access search for a grapheme break in the >99% case where the index simply comes from the same string view.

replaceSubrange needed to be rewritten in every range-replaceable string view to fix its behavior. The new implementations contain algorithmic improvements that dramatically boost performance compared to the previous versions, despite the additional index validation. (Especially for Substring and the two UnicodeScalarViews.)

The grapheme breaking algorithm was refactored to support exotic Substrings. As part of this work, some duplicated work was eliminated and the forward & backward directions now have their own standalone code paths, simplifying logic.

Higher-level indexing operations (distance(from:to:), index(_:offsetBy:), index(_:offsetBy:limitedBy:)) no longer delegate to generic implementations in BidirectionalCollection; rather they use hand-written implementations that are tailored to strings. This fixes some edge cases that are unique to strings, as well as allowing us to avoid index validation overhead while iterating over indices; this should make the new implementations just as fast or faster as the versions we had in <=5.6.

Some care was taken not to introduce unnecessary ARC traffic, with releasenone annotations added as needed.

To shortcut the number of steps needed to validate an index, I added direct fast paths that test for multiple index flags (encoding, scalar/character alignment) at once, and only going through the full validation procedure if the flags indicate that we aren't on the happy path.

@swift-ci test

I'll also add #42409 here to prevent slowing down CI test runs, especially in debug mode.

@swift-ci test and merge


Display edges metadata

Right now, there is no way to select an edge and show the associated metadata

https://github.com/skydive-project/skydive/pull/579

Closed: #602


Can't play the scene

Is it possible to upload a video tutorial where you explain how we run the program? I did step by step but I can't visualize anything when I press "Play".
Is it necessary to download the datasets from "https://github.com/sssabet/RoboflowSport" to work?

Hi @djneves ,
There is no video tutorial as of now, but I can add it soon.
The videos in the repo are the videos from the game.

Is it necessary to download the datasets from "https://github.com/sssabet/RoboflowSport" to work?
No you don't need to add it from that repo if you want the existing game, but if you want a new game yes you should run the python code and take the results to Unity.

One thing that is missing in the project is the models of the players, as of now there is only Ronaldo's model is available in the repo, but you can find other players for example in: https://3dpassion.net/product/3d-rigged-neymar-animation-al-hilal-2024/

@djneves also please make sure you are loading currect scene, load assets/scene/ar and then add the prefabs


Lock-in performance improvement from #25216 and #25156

run assembleDebug | largeAndroidBuild | RealLifeAndroidBuildPerformanceTest for 8.3 is now around 10% faster again:

@bot-gradle test and merge


Error creating table with uppercase letters

Creating table with uppercase letters gives an error saying "SQLActionException[table name "sch.myTable" is invalid.]"
CREATE TABLE "sch"."myTable"(id string primary key);

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/32941347-error-creating-table-with-uppercase-letters?utm_campaign=plugin&utm_content=tracker%2F505659&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F505659&utm_medium=issues&utm_source=github).

This is a limitation of Crate. Table names can't have uppercase characters. See naming restrictions

No I chose the table name, and yes I can switch to lower-case table names.


General Issue: "falcon" will be renamed as "cardinal"

Background Information
The "falcon" repo has already been renamed as "cardinal". Following the merge of https://github.com/pharmaverse/cardinal/pull/223, the name change will be 💯 complete.
Please update all references of "falcon" to "cardinal".

thanks Dinakar! i created https://github.com/pharmaverse/pharmaverse/issues/299 to make all the updates on website for this. will do that soon.

@telepath37 would you be able to tackle this or reassign? thanks

@telepath37
Is it possible to get this done by the end of the month?


Non recoverable error

Problem Description
Hello !
I received this error. It's using space exploration latest version and a few minor additions.
I don't know exactly how to reproduce the bug.
It happened when I played with copy-pasting the modules, but I don't know what condition triggered this.
It happened only once for now.
Factorio 1.1.94
1936.625 Error MainLoop.cpp:1391: Exception at tick 49700859: The mod Factory Planner (1.1.72) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event factoryplanner::on_gui_click (ID 1)
__factoryplanner__/util/clipboard.lua:14: attempt to index local 'object' (a nil value)
stack traceback:
        __factoryplanner__/util/clipboard.lua:14: in function 'copy'
        __factoryplanner__/ui/main/production_handler.lua:196: in function 'handler'
        __factoryplanner__/ui/event_handler.lua:157: in function <__factoryplanner__/ui/event_handler.lua:114>
1936.625 Error ServerMultiplayerManager.cpp:92: MultiplayerManager failed: "The mod Factory Planner (1.1.72) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event factoryplanner::on_gui_click (ID 1)
__factoryplanner__/util/clipboard.lua:14: attempt to index local 'object' (a nil value)
stack traceback:
        __factoryplanner__/util/clipboard.lua:14: in function 'copy'
        __factoryplanner__/ui/main/production_handler.lua:196: in function 'handler'
        __factoryplanner__/ui/event_handler.lua:157: in function <__factoryplanner__/ui/event_handler.lua:114>"
1936.626 Info ServerMultiplayerManager.cpp:814: updateTick(49700859) changing state from(InGame) to(Failed)
1938.128 Info ServerMultiplayerManager.cpp:154: Quitting multiplayer connection.
1938.128 Info ServerMultiplayerManager.cpp:814: updateTick(49700859) changing state from(Failed) to(Closed)

Nice work to you and thanks :)
Reproduction
No response

Thanks for the report, sadly with no detailed reproduction, which seemingly no one seems to have :( Same bug reported here #137, so I'll close this one, and will answer on the other one.


Add czech translation

Do I really want to translate word "seed" like a "sperm"? Just kidding ...

:+1:

@tomas-mraz provide me with your ARK address or contact me on Ark slack (boldninja) if you don't want to share it publicly.

It's me ... a08/2.


Remove CircleCI from Service Hooks integration

There was a time when we first migrated to the Webhooks API,
long ago, that we still accepted callbacks from hooks setup here.
We have since stopped accepting these hooks.
This is because there is no way to properly sign them here.
So the hooks the only way to use our service is with a signed hook which we created.
This has lead to some confusion, by users who accidentally delete our hook,
and try to recreate the hook themselves using this service.
We'd like to avoid support requests for these old hooks.
Please note: GitHub will only accept pull requests to existing services that implement bug fixes or security improvements. We no longer accept feature changes to existing services.

@zzak we don't currently have a way to remove a service that doesn't also remove all installations of that service. Presumably, you'd like things to continue to work for anyone who is currently using the CircleCI service?

Hello @kdaigle,
Thanks for your reply!
If by removing all installations of the service, you mean the service hooks from this screen?

Then I think that is OK, since we won't accept any requests sent via this webhook. Unless the hook is created on our end through the Webhooks API, where we can sign it, then we won't accept it.
Does that make sense?
Thank you for expressing caution in this :)

@kdaigle Yes, it is ok to remove all instances of this from repositories as well. Since we use web hooks, all instances of it are broken and therefore cause confusion.

Sorry for the delay in this. I'll be merging, deploying, and removing this service from existing repositories.

@gjtorikian Thank you very much!

@gjtorikian Thank you!! :bow:

No worries. I'll update this thread when it's live across the many servers of GitHub (later today, for sure).

This is now gone, gone, gone.


switch to glob-watcher 2.0

this relies on the recent breaking changes to glob-watcher being published to npm as 2.0
@contra this will cause vinyl-fs to require a 2.0 bump also.

Will bump vinyl-fs to 2 after I finish some other fixes

Sounds good to me :birthday:

I'm hitting an issue where vinyl-fs' version of<EMAIL_ADDRESS>has an issue when setting maxListeners: 0. It should set them to infinite but currently ignores the option (but fixed on 0.6.x and higher). I am passing in maxListeners as a workaround:
gulp.watch(files, { maxListeners: 999 }, ['taskName'])

@timelf123 You should open an issue on gaze and ask them to push a fix to the 0.5 branch as a patch release then.

Done: https://github.com/shama/gaze/issues/193

Is it possible to bump the version of gaze required since the issue has been fixed on 0.6? Seems silly to backport a fix when the next minor version took care of it

@timelf123 the 0.6 branch is full of bugs and doesn't work, this is all over the gaze project and the gulp project - 0.6 is broken, nobody can use it. It may have fixed some bugs but it introduced more issues than it solved.

My mistake, I didn't even test :P Just read that that specific bug was fixed. Thanks for clarifying


fix config file in $HOME dir and other refactors

In summary, I moved some functions to a config package to extract the main package's config responsibility.
I also added some logger config to help troubleshoot the config file locations, which will work like this:

It will use the first file found like this:

Feel free to suggest any necessary changes.
It may close #26.

also fixed the issue that passed the flag args to the git command:
❯ go run main.go git.go config.go -L debug -- -s -S
2024-03-20 03:07:57 DEBU checking for config file path=/Users/seba/projetos/github.com/sebastianwebber/meteor/.meteor.json
2024-03-20 03:07:57 DEBU checking for config file path=/Users/seba/projetos/github.com/sebastianwebber/.meteor.json
2024-03-20 03:07:57 DEBU found config file path=/Users/seba/projetos/github.com/sebastianwebber/.meteor.json
2024-03-20 03:07:57 DEBU loading config file path=/Users/seba/projetos/github.com/sebastianwebber/.meteor.json
[fix-config-file d6dc116] fix: ignore non-parsed args
 1 file changed, 1 insertion(+), 1 deletion(-)

ideally we could use cobra to handle the command line args, let me know if you would like a PR to handle this.

This looks good, I'll just need to get some time (hopefully this evening) to pull it down and give it a quick test. It may close #26, but this isn't the fix I had in mind for that issue. Obviously, if this does fix it then even better!
In regards to using Cobra to handle the command line arguments, I'd like to avoid adding unnecessary complexity to the tool as much as possible for now. If you can give me a good enough reason to make the move at this stage, then I'm all ears! But I feel like it's something I'd rather do when the complexity it adds is more justified


Build apk for each release

Is your feature request related to a problem?
Whenever a release is released, it would be nice for a sample apk to be generated so that you can get a general idea of the sample project.
Describe the solution you'd like
Use the github actions, which every time a release is released, a sample apk is generated.

Hi, @Angelk90 - this will unfortunately require both some work and resources (build server costs) that we haven't planned to do.

@chrfalch : I don't understand, the build will only be created when a new version is released.
Then the report is public, so I don't understand.


Equivalent to Slalom regressOut?

I've previously used slalom to regress out cell cycle effects, by doing
Y_corrected = FA.regressOut(terms=['S', 'G2M'], use_lm=True, Yraw=Y_raw.values)

on a trained model FA. Since slalom is no longer being updated, I was hoping to switch to MuVI. Is there a function in the new implementation that is roughly equivalent?

Hi @jpintar, indeed we have not implemented the regressOut function for MuVI. I have attempted to adapt the main part of the code from the old slalom repository for MuVI given your example:

def regress_out(model, factor_idx, view_idx="all", use_raw=True):

    zs = model.get_factor_scores(factor_idx=factor_idx, as_df=True)
    if use_raw:
        ys = model.get_observations(view_idx, as_df=True)
    else:
        ys = model.get_reconstructed(view_idx, as_df=True)

    ys_corr = {}
    for view_name, view_obs in ys.items():
        ys_corr[view_name] = view_obs.copy()
        for feature_name in ys[view_name].columns:
            lr = LinearRegression()
            lr_ys = view_obs.loc[:, feature_name]
            lr.fit(zs, lr_ys)
            ys_corr[view_name].loc[:, feature_name] = lr_ys - lr.predict(zs).astype(np.float32)
    return ys_corr

Thank you! I'll try it out!


Add support for elif

Description
Add support for an elif keyword in the compiler.
closes #2454
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request


new Formidable() or new Formidable.IncomingForm() ?

github readme says that form =  new Formidable();
but npm readme says  new Formidable.IncomingForm();
which one should we use?

form = new Formidable();
side note: github readme and npm readme will be out of sync until we publish a new release


Use the COPYFILE_FICLONE constant

For faster copy.
https://nodejs.org/api/fs.html#fs_fs_copyfile_src_dest_flags_callback

Just wondering how this would be implemented:

check if COPYFILE_FICLONE flag exists
if so, call fs.copyFile and emit progress 0, then progress 100% on completion

For the sync version, just add the flag if it exists
Right?

Let's wait a little bit with this. It has some issues: https://github.com/nodejs/node/issues/27273

Since the problem will always exist with the current mode versions, how about working around it keyed by version and platform?

Since the problem will always exist with the current Node versions

Current patch versions, you're right, but the Node.js team backports fixes all the time, so might be fixed in a patch/minor Node.js 8 version. I prefer to hold on for a bit and see if they'll do.

If anyone wants to work on this, see the initial attempt and feedback in https://github.com/sindresorhus/cp-file/pull/40.


feature(typescript_indexer): index binding element parameters

Currently we entirely skip over parameters that are defined via binding
elements, like
function foo({a, b: {c, d}}, [e, [f]]);

Implementing this is fairly straightforward. The existing parameter
visitor implementation is pulled out into its own method, and when we
encounter a set of parameter declarations they are recursively traversed
for their declarations in a binding expression.
Ideally, something these paramaters would be named a: 0.0, c: 0.1.0,
etc. to more accurately reflect how they are processed as arguments by
JavaScript/TypeScript. But Kythe doesn't support that and for the user
it makes more sense to think about them linearly.

cc @evmar


[BUG] Missing 'Filter by' functionality

Describe the bug
It's impossible to filter by owned, running, stopped or destroyed instances, as in the old UI.
To Reproduce
Steps to reproduce the behavior:

Go to 'Compute > Instances' - the 'Filter by' functionality is missing.

Expected behavior
There should be a way to filter by owned, running, stopped or destroyed instances, as in the old UI.
Screenshots

Desktop (please complete the following information):

OS: Windows 10 Pro x64
Browser: Chrome
Version: 80.0.3987.132 (Official Build) (64-bit)

Additional context
This filtering is missing also in the following pages:

Templates

Add filter by state in the state column for vm etc. cc @shwstppr (ListView component)


Bundle works fine on 8 but composer complains

Need this

Hi! Is there any chance to get this PR merged and released soon? PHP 8.0 has been released 7 months ago, and this PR has been opened for 2 months. Thanks a lot :pray:


leetcode.cn cant sign in

And are you sure that cn plug-in is enabled? Because by default it uses com and they don't share a database

Yes, you are right, I forgot to enable the cn plugin


Disabled web mode causes error 404 when leaving preview page.

Disabling web mode in majestic leads to error 404 while navigating from preview page to any other page in legacy web on port 85.
To reproduce:
killall majestic
yaml-cli -s .system.webAdmin disabled
majestic

open http://<IP_ADDRESS>:85/cgi-bin/preview.cgi
click openipc logo in header for going to homepage
get error 404 page, see error in majestic output.

killall majestic
yaml-cli -s .system.webAdmin enabled
majestic

open http://<IP_ADDRESS>:85/cgi-bin/preview.cgi
click openipc logo in header for going to homepage
page opens, no error in logs.

Could you please the same with curl http://<IP_ADDRESS>:85/cgi-bin/preview.cgi, not the browser?

preview.cgi.curl.txt
status.cgi.curl.txt

It seems that curl works as should, is it a browser glitch?
I couldn't reproduce it on my Chrome though

https://user-images.githubusercontent.com/1933140/221196356-fce66a0f-d812-434c-be64-c8cc57b4c97e.mp4
https://user-images.githubusercontent.com/1933140/221196376-a9ef5652-af72-41f8-aa54-a6f04720456b.mp4

As discussed in TG group it's probably httpd redirect issue


--- added support for BinaryFileResponse

I've changed the type declarations to mixed in f6b35e37ade0c06b250f5091ee0fb7c3a84c232a. Otherwise, this could become an endless list of types.
Thanks for your bug report and PR though!


Error while running SpaceTalk on windows. No windows compatible build for<EMAIL_ADDRESS>

After starting up the app encountered with the following error
[[[[[ C:\Users\dmitrijsbalcers\Documents\GitHub\SpaceTalk ]]]]]

=> Started proxy.
=> Started MongoDB.
=> Errors prevented startup:

   While checking for<EMAIL_ADDRESS>   error: No compatible binary build found for this package. Contact the
   package author and ask them to publish it for your platform.

=> Your application has errors. Waiting for file change.

The version of the package should be changed to the 3.1.1. At the moment, I cannot apply the fix due to an issue described here - https://github.com/SpaceTalk/SpaceTalk/issues/28

is this already fixed @dmitrijs-balcers ?

@dstollie No not yet. I've tried to run meteor update and it seems like app is running, and I can access it. But I do not know why, but there are no styles applied to the app.

Corresponding commit: https://github.com/dmitrijs-balcers/SpaceTalk/commit/7f2d28a5d3942357b63f8aaf7aca0e8ea27fe17a
File client/css/main.scss was altered after running the meteor command

Found the solution, will push fix soon

All issues related to Windows seems to be resoved


Support for data balancing

Data balancing is important for machine learning.
I would to propose the following feature:
[DATA]
balancing = True # default false
balancing_strategy = ros # options: ros, smote, adasyn

There is currently imbalanced-learn package that is contrib package of scikit-learn. However, no need to stick in this package (can be defined in balancing_strategy above).

yes, makes sense, i used to work with the imbalance learn package some years ago
i wanted to wait until my pal Uwe releases his stratification package, but that might take too long, so we could go ahead with imbalanced-learn

I guess that would be a special filter to be set in experiment class as a post-processing step to feature extraction

for shortness I'd prefer
[DATA]
balancing = ros # options: ros, smote, adasyn

Done with version 0.70.0


Remove deprecated CONNECTION_CLASS attribute in flow handler?

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
CONNECTION_CLASS is deprecated since since 2021.6.0
https://github.com/ludeeus/integration_blueprint/blob/1c5dcfdfb6472122c484ad5738d38d19550b94f3/custom_components/integration_blueprint/config_flow.py#L23
Kudos for a great template!
Describe the solution you'd like
Remove CONNECTION_CLASS
Describe alternatives you've considered
Keep it for backwards compatibility past 2021.6.0
Additional context
N/A

Removed in https://github.com/ludeeus/integration_blueprint/commit/b7a34be397bbb65b8b85c74e839dd0bf35b6b915 👍
Backward compatibility is not a concern for this repository.


Publish Python runtime to PyPI

Published test packages on test.pypi.org, real packages will go out with 0.2 release


Merlin doesn't treat duplicate modules as error

Given the following file:
module X = struct end
module X = struct end

Merlin (using syntastic) will not signal of any error. However, ocamlc will complain:
Error: Multiple definition of the module name X. Names must be unique in a given structure or signature.

This case is particularly hard to handle with the design of merlin incremental typechecker (it would mean duplicating the corresponding part of ocaml type-checker, has this occurs at the boundaries between "normal" and "incremental" type-checking).
I am considering closing this as WONTFIX, unless @trefis have another opinion?

2015-02-11 11:03 GMT+00:00 def-lkb<EMAIL_ADDRESS>
I am considering closing this as WONTFIX, unless @trefis have another opinion?

I agree, it doesn't seem like detecting that error is worth the trouble.

It could be done in a later pass by running the normal typechecker on the whole file.
It is also possible to check that a .ml satisfy the .cmi interface at this step.
However, this won't bring any benefit over running the compiler.


STORM-3075 fix NPE

It looks reasonable. But would like to understand more about it. Could you elaborate on in which case tc will be null?

@Ethanlm - I see tc being null whenever I start nimbus (at least with no topologies).

@Ethanlm - nice catch.  Will fix the source of the problem instead....

@Ethanlm - please take a look.  Thanks.

@Ethanlm - done.  Added a spelling fix.


Bugfix for: Cannot use object of type Predis\Response\Error as array #722

Bugfix for:
Cannot use object of type Predis\Response\Error as array #722

@kgasienica This is great, can you re-submit this change to the v1.1 branch please?

Sure :)
https://github.com/predis/predis/pull/724


powershell section is incorrect

[Enter feedback here]
The PowerShell part says that we will read the nic configuration and make the public IP Id value to be null and then update the nic.
We can't make the public IP id to $null
$nic.IpConfigurations.publicipaddress.id = $null
S C:\Users\xxxxx>  $nic.IpConfigurations.publicipaddress.id=$null
The property 'id' cannot be found on this object. Verify that the property exists and can be set.
At line:1 char:2

$nic.IpConfigurations.publicipaddress.id=$null

 + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
 + FullyQualifiedErrorId : PropertyAssignmentException

Here is the workaorund i followed.
$count= $nic.IpConfigurations.Name.Count
$i=0
    while ($i -le ($count-1)){
        $nic.IpConfigurations[$i].publicipaddress.id=$null
        $i++}

  Set-AzNetworkInterface -NetworkInterface $nic

This one works

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

ID: 6ae47d5d-6f92-4a81-eb24-843b360b7aaa
Version Independent ID: 0cedc411-cbc7-b877-4bad-a88b56a0e216
Content: Dissociate a public IP address from an Azure VM
Content Source: articles/virtual-network/remove-public-ip-address-vm.md
Service: virtual-network
Sub-service: ip-services
GitHub Login: @asudbring
Microsoft Alias: allensu

@dshiraj, Thanks for the feedback! We are taking a look into this and will get back to you soon.

@dshiraj As mentioned in the other Git issue, please share a snapshot of all the comands you give and the snapshot of the Public IP overview page so I can understand better. Thank you!

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


0.60.5    Duplicate resources

What went wrong:
Execution failed for task ':app:mergeReleaseResources'.

[drawable-mdpi-v4/node_modules_reactnative_libraries_newappscreen_components_logo] F:\RN\test01\android\app\src\main\res\drawable-mdpi\node_modules_reactnative_libraries_newappscreen_components_logo.png    [drawable-mdpi-v4/node_modules_reactnative_libraries_newappscreen_components_logo] F:\RN\test01\android\app\build\generated\res\react\release\drawable-mdpi\node_modules_reactnative_libraries_newappscreen_components_logo.png: Error: Duplicate resources
[raw/app] F:\RN\test01\android\app\src\main\res\raw\app.json  [raw/app] F:\RN\test01\android\app\build\generated\res\react\release\raw\app.json: Error: Duplicate resources

Go to your android/app/src/res/ ===> delete all drawable-hdpi,mdpi,xhdpi,xxhdpi,xxxhdpi and raw folders.
then run the below amd
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res

sorry, I was wrong about another step,thanks

hey @zhanglong11 ,
m facing the same issue could you tell how to fix it.
I just upgraded RN from 0.51.0 to 0.60.5.

Even i got same issue my problem was i had two images with same name background.png and background.jpg, the app was running fine in development, but throwing error while generating signed APK, once i deleted once of the duplicate image my issue got resolved.

I keep getting this error while trying to generate a signed apk release
[raw/app] /home/lenssd/Desktop/MashApp/masho/android/app/src/main/res/raw/app.json	[raw/app] /home/lenssd/Desktop/MashApp/masho/android/app/build/generated/res/react/release/raw/app.json: Error: Duplicate resources
I tried all the steps described above still no luck

@AnilKumarSamal  Please try to delete all drawable-hdpi,mdpi,xhdpi,xxhdpi,xxxhdpi and raw folders also do a gradlew clean

@SridharAlagirisamy Thank you for your reply I tried as suggested but I got a new error
Given final block not properly padded

This is how i solved this issue.
It was due to release build because it generate new assets whenever you run your app in release mode
so i made npm  pre-androidBuild  command  which
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res/ && sh ./scripts/clear-android-assets.sh
and here is my script
which clear run time generated assets of previous build
`#!/bin/sh
resPath='./android/app/src/main/res/'
ls $resPath | grep "drawable-" | while read -r folder ; do
path="$resPath$folder"
echo "Processing $folder"
ls $path | grep -E "node_modules_|assets_" | xargs -d "\n" -I % sh -c  "rm $path/%;"
done
`

Same error here
[drawable-xhdpi-v4/node_modules_reactnavigationstack_lib_module_views_assets_backicon] /Users/albert/Projects/mobile-app/android/app/src/main/res/drawable-xhdpi/node_modules_reactnavigationstack_lib_module_views_assets_backicon.png	[drawable-xhdpi-v4/node_modules_reactnavigationstack_lib_module_views_assets_backicon] /Users/albert/Projects/mobile-app/android/app/build/generated/res/react/release/drawable-xhdpi/node_modules_reactnavigationstack_lib_module_views_assets_backicon.png: Error: Duplicate resources
tried all @SridharAlagirisamy said but the errror persists

some solutions are provided here
https://github.com/facebook/react-native/issues/22234

You can add code in node_modules/react-native/react.gradle.After doFirst
doLast {
def moveFunc = { resSuffix ->
File originalDir = file("$buildDir/generated/res/react/release/${resSuffix}");
if (originalDir.exists()) {
File destDir = file("$buildDir/../src/main/res/${resSuffix}");
ant.move(file: originalDir, tofile: destDir);
}
}
moveFunc.curry("drawable-ldpi").call()
moveFunc.curry("drawable-mdpi").call()
moveFunc.curry("drawable-hdpi").call()
moveFunc.curry("drawable-xhdpi").call()
moveFunc.curry("drawable-xxhdpi").call()
moveFunc.curry("drawable-xxxhdpi").call()
moveFunc.curry("raw").call()
}

Why would be the fix to modify a react-native file within node_modules???? i can't believe all the fixes i've seen so far, suggests doing this instead of facebook pushing a real fix for this :S

This is how i solved this issue.
It was due to release build because it generate new assets whenever you run your app in release mode
so i made npm pre-androidBuild command which is
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res/ && sh ./scripts/clear-android-assets.sh
and here is my script
which clear run time generated assets of previous build
`#!/bin/sh
resPath='./android/app/src/main/res/'
ls $resPath | grep "drawable-" | while read -r folder ; do
path="$resPath$folder"
echo "Processing $folder"
ls $path | grep -E "node_modules_|assets_" | xargs -d "\n" -I % sh -c "rm $path/%;"
done
`

Bro im having issues with your script, it says that xargs -d isn't a valid param, what would i use? im on macos. Please help

My solution:
Delete all files in /your_project/android/app/src/main/raw/res.
It 's work for me !

@thaiphamvan that works thanks.
after that no problem occurs
watch out to your key and alias and ...

Anyone find a solution to this? Still having this issue...

Same errors for me.
> Task :app:mergeReleaseResources FAILED [drawable-hdpi-v4/node_modules_reactnavigationstack_lib_module_vendor_views_assets_backicon] F:\work\find-stuff\app\android\app\src\main\res\drawable-hdpi\node_modules_reactnavigationstack_lib_module_vendor_views_assets_backicon.png        [drawable-hdpi-v4/node_modules_reactnavigationstack_lib_module_vendor_views_assets_backicon] F:\work\find-stuff\app\android\app\build\generated\res\react\release\drawable-hdpi\node_modules_reactnavigationstack_lib_module_vendor_views_assets_backicon.png: Error: Duplicate resources

If this is still an issue in 0.61, please open a new issue and fill out the template.

This solved my problem (0.61) https://github.com/facebook/react-native/issues/26245#issuecomment-541490177

This solved my problem (0.61) #26245 (comment)

where the code is written specifically ?

By running: then run the below amd
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
generates those files and folder again and release build fails with duplicate resource again.
Version RN 61.5

Version RN 61.5

did you solved it???

Yeah, after removing drawable* folders and “raw” folder, don’t run ‘react-native bundle’ command when you want release, just create the signed bundle or apk directly from the Android studio. When it’s time to create a debug build, run the react-native bundle command. That will recreate drawable* and “raw” folders and debug build after that should succeed.

If you are getting this error at the time of making release apk you can use this command to generate the signed apk and the error will not occur
./gradlew assembleRelease -x bundleReleaseJsAndAssets
This command should be executed in android folder of your app

@mohit-brainizen , appreciate that it helped a lot!!

@thaiphamvan  im getting same error rn v 0.60.5 ,
where to add your code?
You can add code in node_modules/react-native/react.gradle. After doFirst
doLast {
def moveFunc = { resSuffix ->
File originalDir = file("$buildDir/generated/res/react/release/${resSuffix}");
if (originalDir.exists()) {
File destDir = file("$buildDir/../src/main/res/${resSuffix}");
ant.move(file: originalDir, tofile: destDir);
}
}
moveFunc.curry("drawable-ldpi").call()
moveFunc.curry("drawable-mdpi").call()
moveFunc.curry("drawable-hdpi").call()
moveFunc.curry("drawable-xhdpi").call()
moveFunc.curry("drawable-xxhdpi").call()
moveFunc.curry("drawable-xxxhdpi").call()
moveFunc.curry("raw").call()
}

my do last code is
  doLast {
                    def hermesFlags;
                    exec {
                        if (targetName.toLowerCase().contains("release")) {
                            // Can't use ?: since that will also substitute valid empty lists
                            hermesFlags = config.hermesFlagsRelease
                            if (hermesFlags == null) hermesFlags = ["-O", "-output-source-map"]
                        } else {
                            hermesFlags = config.hermesFlagsDebug
                            if (hermesFlags == null) hermesFlags = []
                        }
                        commandLine(getHermesCommand(), "-emit-binary", "-out", jsBundleFile, jsBundleFile, *hermesFlags)
                    }
                    if (hermesFlags.contains("-output-source-map")) {
                        ant.move(
                            // Hermes will generate a source map with this exact name
                            // NOTE: name coincides with jsOutputSourceMapFile
                            file: "${jsBundleFile}.map",
                            tofile: jsCompilerSourceMapFile
                        );
                        exec {
                            // TODO: set task dependencies for caching

                            // Set up the call to the compose-source-maps script
                            workingDir(reactRoot)
                            if (Os.isFamily(Os.FAMILY_WINDOWS)) {
                                commandLine("cmd", "/c", *nodeExecutableAndArgs, composeSourceMapsPath, jsPackagerSourceMapFile, jsCompilerSourceMapFile, "-o", jsOutputSourceMapFile)
                            } else {
                                commandLine(*nodeExecutableAndArgs, composeSourceMapsPath, jsPackagerSourceMapFile, jsCompilerSourceMapFile, "-o", jsOutputSourceMapFile)
                            }
                        }
                    }
                }

My solution:
Delete all files in /your_project/android/app/src/main/raw/res.
It 's work for me !

Worked for me too.

@masmai But don't we need these files there? These are the icons.

@thaiphamvan that was working for me, thank you very much

This is how i solved this issue.
It was due to release build because it generate new assets whenever you run your app in release mode
so i made npm pre-androidBuild command which is
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res/ && sh ./scripts/clear-android-assets.sh
and here is my script
which clear run time generated assets of previous build
#!/bin/sh resPath='./android/app/src/main/res/' ls $resPath | grep "drawable-" | while read -r folder ; do path="$resPath$folder" echo "Processing $folder" ls $path | grep -E "node_modules_|assets_" | xargs -d "\n" -I % sh -c "rm $path/%;" done

Bro im having issues with your script, it says that xargs -d isn't a valid param, what would i use? im on macos. Please help

xargs isn't valid in mac. You can try some alternative like suggested here.
https://superuser.com/questions/467176/replacement-for-xargs-d-in-osx

@SridharAlagirisamy by doing: => Go to your android/app/src/res/ ===> delete all drawable-hdpi,mdpi,xhdpi,xxhdpi,xxxhdpi and raw folders. - works!
By running: then run the below amd
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
generates those files and folder again and release build fails with duplicate resource again.

By running: then run the below amd
react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
generates those files and folder again and release build fails with duplicate resource again.
Version RN 61.5

It's worked for me

You can add code in node_modules/react-native/react.gradle. After doFirst
doLast {
def moveFunc = { resSuffix ->
File originalDir = file("$buildDir/generated/res/react/release/${resSuffix}");
if (originalDir.exists()) {
File destDir = file("$buildDir/../src/main/res/${resSuffix}");
ant.move(file: originalDir, tofile: destDir);
}
}
moveFunc.curry("drawable-ldpi").call()
moveFunc.curry("drawable-mdpi").call()
moveFunc.curry("drawable-hdpi").call()
moveFunc.curry("drawable-xhdpi").call()
moveFunc.curry("drawable-xxhdpi").call()
moveFunc.curry("drawable-xxxhdpi").call()
moveFunc.curry("raw").call()
}

thank

why this hasn't been fixed without involving people's coding?

My problem was solved by following the above @thaiphamvan  approach
You can add code in node_modules/react-native/react.gradle. After doFirst
doLast {
def moveFunc = { resSuffix ->
File originalDir = file("$buildDir/generated/res/react/release/${resSuffix}");
if (originalDir.exists()) {
File destDir = file("$buildDir/../src/main/res/${resSuffix}");
ant.move(file: originalDir, tofile: destDir);
}
}
moveFunc.curry("drawable-ldpi").call()
moveFunc.curry("drawable-mdpi").call()
moveFunc.curry("drawable-hdpi").call()
moveFunc.curry("drawable-xhdpi").call()
moveFunc.curry("drawable-xxhdpi").call()
moveFunc.curry("drawable-xxxhdpi").call()
moveFunc.curry("raw").call()
}

This Solution worked for me
Duplicate Resources Error- React Native for 0.60+
Go to android/app/src/main/res and delete all the directories starting with drawables. This is similar to what we did for earlier versions of React Native.
However, this time, also delete the directory named raw, which contains .json files, including app.json.  Before you do so, make sure none of your own assets (images, videos, etc) do not have the same name, since that would also yield a duplicate resources error.
Having done that, head to the terminal and change your directory to /android . It is always a good idea to run ./gradlew clean (skip the “./” if you’re a windows user) before you move on to generating the apk. The command deletes the build directory, so that you have nothing left from your earlier builds, be it a release build or a debug one.
Finally, run the command ./gradlew assembleRelease (once again skip the “./” for windows users) from the /android directory to generate the apk. This might take a while, but it should generate an apk file in your build/outputs directory.
article source :  https://shreyasnisal.medium.com/duplicate-resources-error-react-native-0-60-2200aa18d3e5

This Solution worked for me
Duplicate Resources Error- React Native for 0.60+
Go to android/app/src/main/res and delete all the directories starting with drawables. This is similar to what we did for earlier versions of React Native.
However, this time, also delete the directory named raw, which contains .json files, including app.json.  Before you do so, make sure none of your own assets (images, videos, etc) do not have the same name, since that would also yield a duplicate resources error.
Having done that, head to the terminal and change your directory to /android . It is always a good idea to run ./gradlew clean (skip the “./” if you’re a windows user) before you move on to generating the apk. The command deletes the build directory, so that you have nothing left from your earlier builds, be it a release build or a debug one.
Finally, run the command ./gradlew assembleRelease (once again skip the “./” for windows users) from the /android directory to generate the apk. This might take a while, but it should generate an apk file in your build/outputs directory.
article source :  https://shreyasnisal.medium.com/duplicate-resources-error-react-native-0-60-2200aa18d3e5

Any solution for this? Without changing react-native core node-modules???
I have assets in raw which I need to use in some native ui components I have in my projects (so deleting raw is not a solution for me)

Exactly. All these people recommending that you delete all resources in main/res must not have anything of value in there. In our case, we integrated React Native into an existing Android application so there are very important resources there that cannot just be deleted.
Thankfully, I simply removed the ones that had a conflict, which were ones that React Native's build.gradle must have generated and the issues seemed to go away.

for me i just had to migrate my project to a new 0.61 rn project from the ground up, and use react-native run-android --variant=Release to build the apk in release mode without any issue or duplicated files

I have write another script that delete build/res not the android/res. In case who needs.
doLast {
                println("currentBundleTask do last")
                // the folder is like drawable-ldpi
                def moveInRelease = {resFolder, resSuffix ->
                    if (!resFolder.exists()) {
                        return
                    }
                    files(resFolder.listFiles()).each {
                        def path = it.getAbsolutePath()
                        def dstPath = file("$buildDir/../src/main/res/${resSuffix}/${it.name}")
                        File dstFile = file(dstPath)
                        if (dstFile.exists()) {
                            it.delete()
                        }
                    }
                }

                def moveFunc = { resSuffix ->
                    File root = file("$buildDir/generated/res/react")
                    files(root.listFiles()).each {
                        println(it.path)
                        println(it.name)
                        if (it.isDirectory()) {
                            if (it.name == "release") {
                                File folder = new File(it.getAbsolutePath(), resSuffix)
                                moveInRelease.curry(folder, resSuffix).call()
                            } else {
                                files(it.listFiles()).each {
                                    if (it.name == "release") {
                                        File folder = new File(it.getAbsolutePath(), resSuffix)
                                        moveInRelease.curry(folder, resSuffix).call()
                                    }
                               }
                            }
                        }
                    }
                }
                moveFunc.curry("drawable-ldpi").call()
                moveFunc.curry("drawable-mdpi").call()
                moveFunc.curry("drawable-hdpi").call()
                moveFunc.curry("drawable-xhdpi").call()
                moveFunc.curry("drawable-xxhdpi").call()
                moveFunc.curry("drawable-xxxhdpi").call()
                moveFunc.curry("raw").call()
            }


Customizing dialing in HTTPS proxy

I'm more than happy to put a PR together, but wanted to get a sense of your thoughts before I wrote it up.
It's possible to override how dialing works for HTTP proxies by setting proxy.Tr.Dial. This is useful for e.g. setting custom connect timeouts.
There's no equivalent functionality for https proxying, because it just calls net.Dial directly, and I've run into clients that don't set a timeout while waiting for the 200 from the CONNECT method (Ruby's Net::HTTP has this problem)
Does it make sense to look at Tr.Dial from the https code? Do you have any thoughts on alternative ways to allow overriding the dialer behavior?

Hey,
What about it? We have to set Tr.Dial for each protocol. (HTTP/HTTPS).
This issue has been closed in 2014, and It's been 5 years ago. If you can solve this, we would like to use your library for our use case.
Thanks.


Enable CEE mixin to be used in XDM Summary Metrics class

https://jira.corp.adobe.com/browse/PLAT-130939

Created another PR with these changes.
https://github.com/adobe/xdm/pull/1658


Question: how to properly import pixi-particles 4.0.1 with webpack

Hi, I'm importing lib not from package.json, but in my script file like this:
import 'scripts/pixi-particles';
const myEmitter = new PIXI.particles.Emitter(...)
throws console error : PIXI.particles.Emitter is not a constructor
If I import it as :
import * as Particles from 'scripts/pixi-particles';
I have to access it :
const myEmitter = new Particles.PIXI.particles.Emitter(...)
Doesn't feel right. How should I be importing it correctly ?
Thank you

There are currently 3 exports defined in package.json:
"main": "lib/pixi-particles.js",
"module": "lib/pixi-particles.es.js",
"bundle": "dist/pixi-particles.js",

where main is Node/CommonJS exports, module is proper ES6 exports, and bundle createsPIXI.particles as a global namespace. Your situtation sounds like you are somehow getting the bundle imported but inside its own module or something. Perhaps you need to tweak resolve.packageMains or resolve.mainFields in your config, or you have some odd configuration that was needed for an earlier version of the library?

Solved. Thanks for pointing out on lib folder and es module, I was using dist

How was it solved? import ? as ? from ?

In general, using normal ES6 imports are the correct way to do things - import * as particles from 'pixi-particles' or import { Emitter } from 'pixi-particles'. The issue here was a custom configuration that wasn't aware of the correct file(s).

@andrewstart Thank you, normally I use the import {Emitter} from 'pixi-particles' approach. Which is working in some of my former pixi 4.x.x projects. In my recent proiect I am using pixi 5 and I am getting "Uncaught pixi-particles requires pixi.js to be loaded first" - no matter what import method I use. I have always found it a little confusing that I imported Emitter but never really used it as such - typical usage: const emitter = new PIXI.particles.Emitter(this._particlesContainer, this.pad.iconTexture, particleData); so importing Emitter somehow triggered pixi particles to put itself on the PIXI Object
Should I create a new issue btw?

That error has not been present since version 3.2.0. You need to upgrade to version 4 or higher, which actually supports Pixi 5 without deprecation warnings.

Sorry, didn't realise that my version was that old. I installed using npm install pixi-particles, but the old version must have already been in the project. Using 4.0.1 and pixi 5.3.2 I get "ReferenceError: PIXI is not defined"

It wasn't that old, in that 3.2.0 was the last version before 4.0.0, but newer is significantly better in this case.
That error would happen if your build process was pulling in the "bundle" version of the library (see my first post in this issue) that is intended for <script> usage. You'll need to fix whatever it is in your build settings that is pulling in that instead of the preferred "module" version.

This is how I build it (dev): `const path = require('path');
module.exports = {
mode: 'development',
watch: true,
devServer: {
    contentBase: path.join(__dirname, "./dist/"),
    port: 9000
},
entry: ["./src/app.js"],
module: {
    rules: [
        {
        test: /\.js$/,
        exclude: [/(node_modules)/,
                    path.resolve(__dirname, 'browser.js'),
                    path.resolve(__dirname, 'bootstrap.js')],
        use: {
            loader: "babel-loader"
        }
        }
    ]
},
devtool: 'eval-source-map',
output: {
    filename:   "bundle.js",
    path: path.resolve(__dirname + "/dist")
}

};`
I use gulp as a task runner with weppack-stream:
const webpackStream = require('webpack-stream'); const webpackConfig = require('./webpack.prod'); const webpackDevConfig = require('./webpack.dev'); [...] gulp.task('build:dev', ()=>{     return gulp.src('./src/app.js')         .pipe(webpackStream(webpackDevConfig))         .pipe(injectVersion({package_file: './config.json'}))          .pipe(gulp.dest('./dist/')); });
Besides the use of Gulp - I believe it is fairly standard webpack stuff, so I guess I should add something to webpack setup force it to use the lib/pixi-particles.es.js or I should use require in the code instead of import?


Create an action that outputs space-delimited issue numbers

Follow-up to #5
From @smockle in https://github.com/smockle/action-autolabel/issues/5#issuecomment-901143765:

…I’m planning another action (e.g. smockle/action-issue-filter) which would accumulate the issue numbers for issues with a specified label and provide them via outputs.

From @smockle in https://github.com/smockle/action-autolabel/issues/5#issuecomment-902124523:

…I’ll build several single-purpose actions (e.g. a complementary smockle/action-number-issues or smockle/action-filter-issues, as proposed above), and workflows can compose them together.

TODO

[x] Debug missing github context, which is causing runs to fail: https://github.com/smockle/action-filter-issues/actions/runs/1187884066
[x] Debug unexpected output ({} instead of "1"): https://github.com/smockle/action-filter-issues/runs/3499095716?check_suite_focus=true
[ ] Add pagination support (for repos with many issues)
[x] (Low priority) Skip the Publish workflow for Dependabot-initiated pushes to the main branch

smockle/action-filter-issues is very close to done. There are three known issues remaining:

[ ] Debug missing github context, which is causing runs to fail: https://github.com/smockle/action-filter-issues/actions/runs/1187884066
[ ] Add pagination support (for repos with many issues)
[ ] (Low priority) Skip the Publish workflow for Dependabot-initiated pushes to the main branch

(Low priority) Skip the Publish workflow for Dependabot-initiated pushes to the main branch

https://github.com/smockle/action-autolabel/commit/531a947da9282a34109cfa2f619bcc70ca08aa66 and https://github.com/smockle/action-filter-issues/commit/bca3969e938f9c25af76387a3c86daaf89c15a75 might resolve this (with a different approach).

From @smockle in https://github.com/smockle/action-autolabel/issues/9#issue-974952753:

[ ] Add pagination support (for repos with many issues)

Re: repos with many issues, I thought of a more efficient approach. Rather than retrieving all issues and then exclude/include filtering in JavaScript, instead retrieve issues for each label in include_filters, then intersect them, then filter the result with exclude_filters.

From @smockle in https://github.com/smockle/action-autolabel/issues/9#issue-974952753:

[x] Debug missing github context, which is causing runs to fail: https://github.com/smockle/action-filter-issues/actions/runs/1187884066

https://github.com/smockle/action-filter-issues/commit/7553338f12c0346d2ad1e27130abe6c26a7fdb64 resolves this. The issue is that—although repository in the github context is a string—repository in the webhook payload object is an object, and (TIL) github.context.payload is—despite what its name suggests—an instance of the latter, not the former. Applied an analogous fix in smockle/action-autolabel too: https://github.com/smockle/action-autolabel/commit/79b220c06836952e01fdbe1272ec0784c5c02809.

From @smockle in https://github.com/smockle/action-autolabel/issues/9#issue-974952753:

[x]  Debug unexpected output ({} instead of "1"): https://github.com/smockle/action-filter-issues/runs/3499095716?check_suite_focus=true

https://github.com/smockle/action-filter-issues/commit/25e94874e1c324d17e0aa4af212f859ed7e9f478 resolves this. This issue was a missing await, so the wrapped value was being sent via outputs. The latest run echo’d "1", as expected.

From @smockle in https://github.com/smockle/action-autolabel/issues/9#issue-974952753:

[x]  Add pagination support (for repos with many issues)

Added in https://github.com/smockle/action-filter-issues/commit/7b107a262c4b3a25cee2ecfa54be5781442e2450!


⚠ Thumbnails API Endpoint has degraded performance

In c1519ed, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1273 ms

Resolved: Thumbnails API Endpoint performance has improved in a4bab90 after 7 minutes.


fix(ollama): builders and their methods should be public (#1849)

Issue

Closes #1849
Change

Make methods for instantiating builders and their methods public
General checklist

[x] There are no breaking changes
[ ] I have added unit and integration tests for my change
[ ] I have manually run all the unit and integration tests in the module I have added/changed, and they are all green
[] I have manually run all the unit and integration tests in the core and main modules, and they are all green

[ ] I have added/updated the documentation
[ ] I have added an example in the examples repo (only for "big" features)
[ ] I have added/updated Spring Boot starter(s) (if applicable)

Checklist for adding new model integration

[ ] I have added my new module in the BOM

Checklist for adding new embedding store integration

[ ] I have added a {NameOfIntegration}EmbeddingStoreIT that extends from either EmbeddingStoreIT or EmbeddingStoreWithFilteringIT
[ ] I have added my new module in the BOM

Checklist for changing existing embedding store integration

[ ] I have manually verified that the {NameOfIntegration}EmbeddingStore works correctly with the data persisted using the latest released version of LangChain4j

I think this PR is a duplicate of #1843 . Also, not all builders and their methods shuold be public (some classes are package-private.)

Closing in favor of https://github.com/langchain4j/langchain4j/pull/1843.


Add orphaned resource cleanup application with scope of CFT sandbox

JIRA link (if applicable)

https://tools.hmcts.net/jira/browse/DTSPO-13983

Change description

Add DTSPO Orphaned Resource Cleanup application/service principal with scope limited to CFT sandbox management group and for use only by https://github.com/hmcts/dtspo-orphan-resources-cleanup

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Plan Result (prod_app_registrations)
Plan: 5 to add, 0 to change, 0 to destroy.

Create

module.this.azuread_application.this["DTS Orphaned Resource Cleanup"]
module.this.azuread_application_federated_identity_credential.this["DTS Orphaned Resource Cleanup-repo:hmcts/dtspo-orphan-resources-cleanup/tree/dxw/orphan-testing"]
module.this.azuread_application_federated_identity_credential.this["DTS Orphaned Resource Cleanup-repo:hmcts/dtspo-orphan-resources-cleanup/tree/master"]
module.this.azuread_service_principal.this["DTS Orphaned Resource Cleanup"]
module.this.azurerm_role_assignment.this["DTS Orphaned Resource Cleanup-Orphan Resource Cleanup Read/Delete-/providers/Microsoft.Management/managementGroups/CFT-Sandbox"]

Change Result (Click me)

  # module.this.azuread_application.this["DTS Orphaned Resource Cleanup"] will be created
  + resource "azuread_application" "this" {
      + app_role_ids                = (known after apply)
      + application_id              = (known after apply)
      + disabled_by_microsoft       = (known after apply)
      + display_name                = "DTS Orphaned Resource Cleanup"
      + id                          = (known after apply)
      + logo_url                    = (known after apply)
      + oauth2_permission_scope_ids = (known after apply)
      + object_id                   = (known after apply)
      + owners                      = [
          + "dad693c4-36ad-468f-94e9-76faa4bc844b",
        ]
      + prevent_duplicate_names     = false
      + publisher_domain            = (known after apply)
      + sign_in_audience            = "AzureADMyOrg"
      + tags                        = (known after apply)
      + template_id                 = (known after apply)

      + feature_tags {
          + custom_single_sign_on = (known after apply)
          + enterprise            = (known after apply)
          + gallery               = (known after apply)
          + hide                  = (known after apply)
        }
    }

  # module.this.azuread_application_federated_identity_credential.this["DTS Orphaned Resource Cleanup-repo:hmcts/dtspo-orphan-resources-cleanup/tree/dxw/orphan-testing"] will be created
  + resource "azuread_application_federated_identity_credential" "this" {
      + application_object_id = (known after apply)
      + audiences             = [
          + "api://AzureADTokenExchange",
        ]
      + credential_id         = (known after apply)
      + display_name          = "repo_hmcts__dtspo-orphan-resources-cleanup__tree__dxw__orphan-testing"
      + id                    = (known after apply)
      + issuer                = "https://token.actions.githubusercontent.com"
      + subject               = "repo:hmcts/dtspo-orphan-resources-cleanup/tree/dxw/orphan-testing"
    }

  # module.this.azuread_application_federated_identity_credential.this["DTS Orphaned Resource Cleanup-repo:hmcts/dtspo-orphan-resources-cleanup/tree/master"] will be created
  + resource "azuread_application_federated_identity_credential" "this" {
      + application_object_id = (known after apply)
      + audiences             = [
          + "api://AzureADTokenExchange",
        ]
      + credential_id         = (known after apply)
      + display_name          = "repo_hmcts__dtspo-orphan-resources-cleanup__tree__master"
      + id                    = (known after apply)
      + issuer                = "https://token.actions.githubusercontent.com"
      + subject               = "repo:hmcts/dtspo-orphan-resources-cleanup/tree/master"
    }

  # module.this.azuread_service_principal.this["DTS Orphaned Resource Cleanup"] will be created
  + resource "azuread_service_principal" "this" {
      + account_enabled             = true
      + app_role_ids                = (known after apply)
      + app_roles                   = (known after apply)
      + application_id              = (known after apply)
      + application_tenant_id       = (known after apply)
      + display_name                = (known after apply)
      + homepage_url                = (known after apply)
      + id                          = (known after apply)
      + logout_url                  = (known after apply)
      + oauth2_permission_scope_ids = (known after apply)
      + oauth2_permission_scopes    = (known after apply)
      + object_id                   = (known after apply)
      + owners                      = [
          + "dad693c4-36ad-468f-94e9-76faa4bc844b",
        ]
      + redirect_uris               = (known after apply)
      + saml_metadata_url           = (known after apply)
      + service_principal_names     = (known after apply)
      + sign_in_audience            = (known after apply)
      + tags                        = (known after apply)
      + type                        = (known after apply)

      + feature_tags {
          + custom_single_sign_on = (known after apply)
          + enterprise            = (known after apply)
          + gallery               = (known after apply)
          + hide                  = (known after apply)
        }

      + features {
          + custom_single_sign_on_app = (known after apply)
          + enterprise_application    = (known after apply)
          + gallery_application       = (known after apply)
          + visible_to_users          = (known after apply)
        }
    }

  # module.this.azurerm_role_assignment.this["DTS Orphaned Resource Cleanup-Orphan Resource Cleanup Read/Delete-/providers/Microsoft.Management/managementGroups/CFT-Sandbox"] will be created
  + resource "azurerm_role_assignment" "this" {
      + id                               = (known after apply)
      + name                             = (known after apply)
      + principal_id                     = (known after apply)
      + principal_type                   = (known after apply)
      + role_definition_id               = (known after apply)
      + role_definition_name             = "Orphan Resource Cleanup Read/Delete"
      + scope                            = "/providers/Microsoft.Management/managementGroups/CFT-Sandbox"
      + skip_service_principal_aad_check = (known after apply)
    }

Plan: 5 to add, 0 to change, 0 to destroy.