Fix leak in HttpResponseDecoderTest

Motivation:
The HttpResponses produced can carry data, and thus needs to be disposed.
Modification:
Dispose of the http responses we get from EmbeddedChannel.readInbound(). They will not be closed by the channel.finish() because we've read them.
Result:
No more leak from HttpResponseDecoderTest

Looks like something has broken SocketSslClientRenegotiateTest in main. It's ignored for BoringSSL builds, which is what we typically use locally, so that's probably how it snuck past.


Loss and Accuracy functions select the wrong index

The loss and accuracy functions in utils use the utils.select() function to select the logit of the RNN after processing a (variable-length) sentence.  This is currently done by selecting the output at the batch['index'] time-step, but this is wrong by one.  Since batch['index'] is equal to the length of the sentence, we actually want to select the batch['index'] - 1 element.
To illustrate, if the sentence is
word0, word1, word2,
then the network outputs will be (here F is the network function)
F(word0), F(word0,word1), F(word0,word1,word2),
So if the length of the sentence is 3, as it is in this case, we want to select the output in position 2 (zero-indexed).
We'll fix this by modifying the accuracy and loss functions in utils.py.

Was fixed in commit #30


make acids hurt more to drink

About the PR

Buffs the damage that the three acids do when you drink or inject them. The numbers were pretty lackluster beforehand. They are all still weaker than amatoxin but now you can't chug an incredibly caustic acid and walk away with minor injuries.


Backstage integration.

Purpose
This is the introduction of the IDP Backstage to the Azure Samples Platform Engineering Repo. This is to provide a cloud native developer portal serving to extend the end to end story of AKS Platform Engineering. The changes made in this repository use a helm chart to deploy Backstage with the appropriate environment variables all dynamically set based on the terraform. The Backstage image source code is included under the folder "backstage". I have added a document explaining some additional information on backstage as well as the steps to both create a container image from the source code and also run the backstage deployment itself. I have not added these to the main docs as I would like input on placement or mentions of backstage. The helm chart can be reused and the image changed to allow for modifications.
Additions:

Backstage source code and helm chart:

Entra login and automatic onboarding of users from tenant.
Catalogexample item to create new cluster resources in both CAPZ and Crossplane folders for argo to reconcile
Self signed certs deployment
Updated backstage backend architecture (v2).

Terraform changes including:

Postgres flex server for backstage data
App registration for Entra Auth on backstage image
Flag build_backstage. (Default true)
K8S resources for backstage including namespace and role bindings.
Dedicated public IP creation and assignment for backstage service.

Does this introduce a breaking change?

[ ] Yes
[X ] No

Pull Request Type
What kind of change does this Pull Request introduce?
[ ] Bugfix
[ X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test
terraform apply -var infrastructure_provider=crossplane -var build_backstage=< True or False> -var gitops_addons_org=https://github.com/owainow -var github_token=<PAT_TOKEN> --auto-approve
What to Check
Verify that the following are valid

The build_backstage flag works as expected.
Backstage service is deployed with self-signed certificates.
Documentation for backstage image creation  is correct.

Other Information
Prior to merge two outstanding items:

Backstage image in helm chart is currently my own ACR. Image needs to be hosted centrally.
Documentation at root of repository to reflect inclusion of backstage and explanation of resources created to allow users to make informed decision on whether to deploy. e.g App Registration with admin credentials and external postgress db. I would like  input on how & where we feel is best to add this to the README.

Overall, looks good! I was able to get Backstage running using your image.
However, when I go to try and login I get: Sign in using Microsoft request to https://<IP_ADDRESS>:7007/api/catalog/entities?filter=kind%3Duser%2Cmetadata.annotations.microsoft.com%2Femail%3Ddtzar_hotmail.com%23EXT%23%40azurehybrid.onmicrosoft.com failed, reason: Hostname/IP does not match certificate's altnames: IP: <IP_ADDRESS> is not in the cert's list:
Will people have to build their own custom image in order to login?

Have you got a screenshot of the error? The cert mismatch is interesting. It should be using the public IP assigned to Backstage. Can you screenshot the error and perhaps your redirect on the App Registration too, I will need to refresh my memory. I will make the other changes as I get some time.

@owainow Unfortunately, I don't have a screenshot of the error.  How about you fix some of the other things mentioned above and I'll give it another round of testing and if the issue still exists, I'll post the screenshot?

Realised the issue with the cert mismatch. Good news is people don't need a custom image for login. Bad news is there is an extra step required for the time being as I don't have the time before your on leave to automate the fix explained below:
I thought the <IP_ADDRESS> would solve this but actually its going to require in its current incantation the user recreating the certs with the public IP. I have added the steps required to do this post deployment. This could also be done in the tf with some local exec commands to:

Pass the output of the dedicated public IP that is already created pre-cluster creation to a local exec module
Within a local exec module modify the openssl.cnf file to add the public IP that has been assigned.
Run a sep local exec file to execute the following command " openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout tls.key -out tls.crt -config openssl.cnf"
Create the tls secretes on the cluster with the output of the above.

I don't have time to do this today but the steps are pretty clear. One to pick up in the future for ease of deployment. I have written up the steps as step 3 in getting started.

Changes mentioned above and indicated with thumbs up emoji found in this commit. https://github.com/Azure-Samples/aks-platform-engineering/pull/102/commits/1c8fbd498a23b35a1b72e7f4d8bd6505135c7881

Additional changes made on local build guidance including yarn config commands and changes to local-app-config.yaml. Verified build steps and build.


[Bug fix] check out code from main / remove installing FaaSr package in the base image.

Check out code from main - checkout@v4 -> @v3
Remove installing FaaSr package in the base image.

Closing because I fixed these issues on a separate commit.


Fix compatibility with clone J-Link devices

Closes #2593
Old firmware needs some additional setup that we did not do. This PR fixes clone J-Link with firmware J-Link ARM-OB STM32 compiled Aug 22 2012 19:52:04. The config bits aren't necessary I think but they also doesn't really hurt - except for the fact where they can't be read as exactly 256 bytes for some reason, which requires the mess in read() to work around.

@Yatekii this PR would allow me to add an RP2040 to my tester setup, PTAL :)

Hi, this seems to break my J-Link v9.
Before this commit:
DEBUG probe_rs::probe::jlink: J-Link returned interface Fine, which is not supported by probe-rs.
DEBUG probe_rs::probe::jlink: J-Link returned interface Pic32Icsp, which is not supported by probe-rs.
DEBUG probe_rs::probe::jlink: J-Link returned interface Spi, which is not supported by probe-rs.
DEBUG probe_rs::probe::jlink: J-Link returned interface C2, which is not supported by probe-rs.
TRACE probe_rs::probe::jlink: write 1 bytes: [d4]
TRACE probe_rs::probe::jlink: read 4 bytes: [28, 10, 1, 0]
DEBUG probe_rs::probe::jlink: J-Link max mem block size for SWD IO: 69672 byte
DEBUG probe_rs::probe::jlink: Attaching to J-Link
DEBUG probe_rs::probe::jlink: Attaching with protocol 'JTAG'
TRACE probe_rs::probe::jlink: write 2 bytes: [c7, 0]
TRACE probe_rs::probe::jlink: read 4 bytes: [1, 0, 0, 0]
DEBUG probe_rs::probe::jlink: J-Link: Capabilities: CapabilityFlags(GetHwVersion | WriteDcc | AdaptiveClocking | ReadConfig | WriteConfig | WriteMem | ReadMem | SpeedInfo | GetMaxBlockSize | GetHwInfo | SetKsPower | ResetStopTimed | MeasureRtckReact | SelectIf | RwMemArm79 | GetCounters | ReadDcc | GetCpuCaps | ExecCpuCmd | Swo | WriteDccEx | Register | Indicators | TestNetSpeed | GetCapsEx | HwJtagWrite)
TRACE probe_rs::probe::jlink: write 1 bytes: [1]
TRACE probe_rs::probe::jlink: read 2 bytes: [70, 0]
TRACE probe_rs::probe::jlink: read 112 bytes: [4a, 2d, 4c, 69, 6e, 6b, 20, 56, 39, 20, 63, 6f, 6d, 70, 69, 6c, 65, 64, 20, 4d, 61, 79, 20, 20, 37, 20, 32, 30, 32, 31, 20, 31, 36, 3a, 32, 36, 3a, 31, 32, 0, 43, 6f, 70, 79, 72, 69, 67, 68, 74, 20, 32, 30, 30, 33, 2d, 32, 30, 31, 32, 20, 53, 45, 47, 47, 45, 52, 3a, 20, 77, 77, 77, 2e, 73, 65, 67, 67, 65, 72, 2e, 63, 6f, 6d, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
 INFO probe_rs::probe::jlink: J-Link: Firmware version: J-Link V9 compiled May  7 2021 16:26:12

After this commit:
DEBUG probe_rs::probe::jlink: J-Link returned interface Fine, which is not supported by probe-rs.
DEBUG probe_rs::probe::jlink: J-Link returned interface Pic32Icsp, which is not supported by probe-rs.
DEBUG probe_rs::probe::jlink: J-Link returned interface Spi, which is not supported by probe-rs.
DEBUG probe_rs::probe::jlink: J-Link returned interface C2, which is not supported by probe-rs.

Caused by:
    0: An error which is specific to the debug probe in use occurred.
    1: A USB transport error occurred.
    2: unknown error

it seems that the error happened in read_registration_response:
    fn read_registration_response(&mut self) -> Result<u16, JlinkError> {
        const REG_HEADER_SIZE: usize = 8;
        const REG_MIN_SIZE: usize = 76;
        const REG_MAX_SIZE: usize = 512;

        let mut response = [0; REG_MAX_SIZE];
        tracing::info!("Reading registration response");   // <++++++++++++
        self.read(&mut response[..REG_MIN_SIZE])?;
        tracing::info!("Read registration response");   // <++++++++++++

leads to:
TRACE probe_rs::probe::jlink: write 14 bytes: [9, 64, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
 INFO probe_rs::probe::jlink: Reading registration response
Error: Failed to open the debug probe.

Caused by:
    0: An error which is specific to the debug probe in use occurred.
    1: A USB transport error occurred.
    2: unknown error

This issue does not happen after reverting commit 9b97265f61f07b6dc8765b9f2daf0ac64b86b0c9 .

@showier-drastic thanks! If you could please try #2821 and tell me if it does the trick for you, that would be great


Suggested directions to the Santa Monica location

Hey @kpearson!  Here's the directions with links.

@pivotaljohn Thank you so much ❤ 🎊


Tweak some samples for clarity and better behavior in playgrounds

Use viewport dimensions instead of document title
Since most framework playgrounds output into an <iframe>, their document.title properties end up being the empty string unless set by the component code. This made the samples look broken when loaded into playgrounds, so instead this uses runtime properties that every <iframe> can’t help but have.
Simplify traffic light logic
The lightIndex selection logic can be simplified, which seems like a net win for the goal of this site; less attention on the non-framework-specific parts means more attention on the differences between components.
Use mixed checkbox instead of .focus() for DOM refs
When opening the existing elementRef.focus() examples in their frameworks’ playgrounds, the call to .focus() would be ignored because of <iframe> reasons or something. This change no longer seems like it’s broken when attempting to view it, and as a bonus it gets rid of the ambiguity between which frameworks used type="text" and which omitted it (Was it because the framework needs explicit attributes with default values, or because some example authors preferred to leave it off?)

These are some things that bothered me enough to try improving them while working on adding Marko to the framework comparison. If you’re down with the changes, I can quickly follow this up with that, but if you’d rather not, I’ll update the eventual Marko PR to stay consistent.

I chose document.title and .focus methods for the following reasons:

well known for web developers
used in real world apps
simple to use

It bothers me that it does not work well in playgrounds... Sacrificing readability and therefore comprehension to work inside an iframe is not worth it... Not sure which well know apis to use to make it work in playgrounds and CP snippet requirements.
viewport and indeterminate apis are not well known, that's a hard dilemma.
I'll make some search to find a possible other solution.

About on mount example, I was thinking about this:
<script>
  import { onMount } from "svelte";

  onMount(() => {
    console.log(document.getElementById("website").value)
  });
</script>

<input id="website" value="Component Party" />

But it's not a recommended way to use the DOM, and it's mixing with dom ref examples.
I'm thinking about the localStorage API being quite popular.

I agree with your point about indeterminate, but are viewport dimensions that obscure? Finding the dimensions of a web page in JS seems like a pretty reasonable question for newbies, and even if they’re unfamiliar with the concept, every page having a width and height doesn’t seem onerous to ask them to imagine.
For the DOM ref example purposes, one way to go would be a property/method that interacts with the element that isn’t settable as an HTML attribute. Some possibilities:

playbackSpeed on <audio> or <video>
showModal() on <dialog>
setCustomValidity() on form elements
select() on form elements (this one might break in playgrounds too, haven’t checked)
<canvas> in general

Like you, I would be very happy that Marko is featured in CP.
Just to move forward, I got 2 proposals:

Totally disable playground feature for Marko (easy)
Disable playground for examples that don't work well in the playground (harder)

What do you think ?

I’m happy to change the Marko code samples to match the others to get it in. (Sorry about how long this is taking — I got laid off by eBay shortly after I opened these PRs.)
To be clear, the issues with focus and document.title affect most of the playgrounds, not just Marko’s — it seemed like a confusing experience to show demo code that then appears to not work at all when taken for a test drive.


security on switching mode

greetings everyone,
i'm using this plugin since 8 months now, and it's almost perfect, thanks for working on this.
but sometimes, i'm accidentally switching the mode of one of my unit, and so it's screwing up all my system. let me explain :
in the home app, the modes are in this order : off, heat, cool.
when i'm on the "cool" mode, and i want an unit to turn off, i have to scroll up to "off", but sometimes i'm doing something wrong with my fingers and it's actually selecting "heat".
and then it's screwing everything up. i don't know why, but all the temperatures are changing, and my whole system is reversing (which is terribly bad). i have to go back to the airzone app and revert everything.
so, i was wondering if it could be possible to add something to enable a security, that would block any change from "heat" to "cool". to make it as the only way to switch from those two, is from the airzone app.
the only possible change would be from the initial mode, to "off", and from "off", to that initial mode.
for me it's not that stupid, because i personally switch between those two modes two times a year, and it would prevent those kind of accidents.
thanks for reading this, have a great day! :)

hello,
sorry for the late answer. unfortunatly, or maybe fortunatly, it's not doing the weird things on temperatures anymore.
but it could still be great to implement this security feature.
it would be great for exemple to disable the mode we're not using, and to let only the "off" mode, and the mode we're using.
the only way to switch would be on the airzone app if we use this security. even if we would have to restart the plugin each time we switch, as he can get and register the mode in the home app, I think this improvement is necessary when you have a whole system running. I don't want all my system to reverse because I missclicked the button in the home app.
also, the improvement suggested in the issue #8 is great and maybe necessary in some cases. that would be awesome if you implement this in the plugin!


refactor(test): remove tap from expirables

As mentioned in https://github.com/Cadienvan/expirables/pull/36 tap is changing a lot of things and license too. I decided to migrate the whole test code base from tap to Node Test Runner using the current ts-node/esm loader.
I kept also the c8 for the coverage

Temporary removed Node 20 from the CI, please don't merge @Cadienvan 🙏


OptionalBinder bound constants are not converted during Binding Resolution

guice4-beta5
Ubuntu 14.04
(Using Oracle java)
$ java -version
java version "1.7.0_76"
Java(TM) SE Runtime Environment (build 1.7.0_76-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.76-b04, mixed mode)
This smells like it might be a bug, but I am only a few days into learning about/using guice so take all I say with a big "new guy doesn't know what he's talking about" grain of salt.
According to
https://github.com/google/guice/wiki/BindingResolution

... 5. Convert constants. If there is a constant string bound with the same annotation, and a TypeConverter that supports this type, use the converted String.

Based on my source code reading, this is the mechanism that makes Names.bindProperites work for converting a string value to an integer.
However - OptionalBinder.setDefault and OptionalBinder.setBinding do not appear to adhere to Binding Resolution rule/step  number 5 (as a normal, non-optional binding does). Instead, it the binding is ignore and I get an error like

No implementation for java.lang.Integer annotated with @com.google.inject.name.Named(value=simpleInt) was bound.
while locating java.lang.Integer annotated with @com.google.inject.name.Named(value=simpleInt)
for parameter 0 at Simple.(Simple.java:16)
at SimpleTest$1.configure(SimpleTest.java:33)

Following is a simple class demonstrating that an OptionalBinder String binding (setDefault or setBinding) does not apply to an int @Named.
Simple.java
import com.google.inject.AbstractModule;
import com.google.inject.Inject;
import com.google.inject.Key;
import com.google.inject.multibindings.OptionalBinder;
import com.google.inject.name.Named;
import com.google.inject.name.Names;

public class Simple {
    private final int simpleInt;

    @Inject
    public Simple(@Named("simpleInt") int simpleInt) {
        this.simpleInt = simpleInt;
    }

    public int getSimpleInt() {
        return simpleInt;
    }

    public static AbstractModule getDefaultsModule() {
        return new AbstractModule() {
            @Override protected void configure() {

                //This works
                /*OptionalBinder.newOptionalBinder(binder(), Key.get(Integer.class, Names.named("simpleInt")))
                        .setDefault().toInstance(12345);*/

                //This does not work
                OptionalBinder.newOptionalBinder(binder(), Key.get(String.class, Names.named("simpleInt" )))
                        .setDefault().toInstance("12345");
            }
        };
    }
}

SimpleTest.java
import com.google.inject.*;
import com.google.inject.multibindings.OptionalBinder;
import com.google.inject.name.Names;
import org.junit.Test;

import static org.junit.Assert.*;

public class SimpleTest {

    @Test
    public void testGetSimpleIntDefault() throws Exception {
        Injector inj = Guice.createInjector(Simple.getDefaultsModule());
        Simple s = inj.getInstance(Simple.class);

        assertEquals(42, s.getSimpleInt());
    }

    @Test
    public void testGetSimpleIntBinding() throws Exception {
        //Not overriding default since default itself doesn't work to begin with
        //Injector inj = Guice.createInjector(Simple.getDefaultsModule(), getTestModule());
        Injector inj = Guice.createInjector(getTestModule());
        Simple s = inj.getInstance(Simple.class);

        assertEquals(111, s.getSimpleInt());
    }

    //Not sure if a String constant setBinding should override an Integer setDefault. Probably not, not testing

    private Module getTestModule() {
        return new AbstractModule() {
            @Override protected void configure() {
                bind(Simple.class);

                Binder skippedBinder = binder().skipSources(Names.class);

                //Works
                //OptionalBinder.newOptionalBinder(skippedBinder, Key.get(Integer.class, Names.named("simpleInt"))).setBinding().toInstance(111);

                OptionalBinder.newOptionalBinder(skippedBinder, Key.get(String.class, Names.named("simpleInt"))).setBinding().toInstance("111");
            }
        };
    }
}

Unfortunately, I don't think there's any reasonable way to make this work.  The binding resolution is intended as a straight 1:1 conversion if the strings were bound using bindConstant or toInstance.  In this case you're going through OptionalBinder and it does a lot of internal magic to make everything work -- so the rest of Guice doesn't see it as a constant binding and can't pull the value out of it.
Instead, you could write a small wrapper over Names.bindProperties (called, say, Names.bindPropertiesAsActualTypes that scans the values and binds them as both the string & the actual type.
OTOH, if you're looking for the reverse:  a user binds a String normally & an OptionalBinder picks that up if it can convert... that might be possible, but I'm not sure it's a great idea.  The TypeConverter system is OK because it's so constrained.  Hooking it into more things could cause a lot of confusion.

No problem - I can work around this behaviour, it just struck me as odd and running counter to the documentation so I thought I'd bring it up.
Feel free to close this as you see fit.


Fixes + Tweaks

Fixes #395
WinUI Tweaks:

[x] Removed Apply button for SyncLyricRow. Lyric will be automatically updated as the text box changes
[x] Make add sync lyric a flyout instead of showing new ContentDialog
[x] See where else flyouts can be used instead of full ContentDialogs

@kissthermite Could you test this build: https://github.com/NickvisionApps/Tagger/actions/runs/6776895782

sure! will let you know in a moments

Using custom format string /%albumartist%/%album%/%artist% - %title% with Limit File Name Characters setting turn on does work as expected for others limited characters except /

tag to file name conversion with aforementioned format string with limited character being :

will give this output: /Kotono Nagase (CV_Mirai Tachibana)/song for you(Kotono version)/Kotono Nagase (CV_Mirai Tachibana) - song for you(Kotono version).flac

tag to file name conversion with aforementioned format string with limited character being /

will give this output: /SQUARE ENIX MUSIC/NieR Gestalt & NieR Replicant Original Soundtrack/SQUARE ENIX MUSIC - Song of the Ancients /Devola.flac

tag to file name conversion with aforementioned format string with limited character being /

Well now with the new algorithm / means new directory. But you want it where if the / was contained in a tag property and now the format string, to not count as a new directory, correct?
I think I can do that.

But you want it where if the / was contained in a tag property and now the format string, to not count as a new directory, correct?

Correct indeed.

@fsobolev If you could make sure the algorithm in this commit still holds: https://github.com/NickvisionApps/Tagger/pull/396/commits/325b0f408260cd0d5a69dfc756fda2e213346a14

But you want it where if the / was contained in a tag property and now the format string, to not count as a new directory, correct?

Correct indeed.

@kissthermite Try this build: https://github.com/NickvisionApps/Tagger/actions/runs/6779510126?pr=396
P.S. Thanks for testing and sorry for messing up your library structure with these tests 🫠

But you want it where if the / was contained in a tag property and now the format string, to not count as a new directory, correct?

Correct indeed.

@kissthermite Try this build: https://github.com/NickvisionApps/Tagger/actions/runs/6779510126?pr=396
P.S. Thanks for testing and sorry for messing up your library structure with these tests 🫠

Sorry I lied, please try this build: https://github.com/NickvisionApps/Tagger/actions/runs/6779656223/job/18427058390
If a tag property contains /, regardless of using Limit Filename Characters, it will not create a new directory. Only if the format string explicitly contains a /, then it will.

P.S. Thanks for testing and sorry for messing up your library structure with these tests 🫠

Don't worries my actual music library are stored on /var/home/kissthermite/Jellyfin Server Media/Music

The one on Downloads folder are just a copy for testing purpose XD.

If a tag property contains /, regardless of using Limit Filename Characters, it will not create a new directory. Only if the format string explicitly contains a /, then it will.

Just tested and indeed it does behave the way you said whether File Name Characters turn on/off. Good job @nlogozzo! and enjoy your well deserved rest tonight.

Just tested and indeed it does behave the way you said whether Limit File Name Characters turn on/off. Good job @nlogozzo! and enjoy your well deserved rest tonight.

Yay, glad it's working as expected now! Once @fsobolev approves of the rest of this PR, I will release a beta.
If you have any other issues/feature requests please try to report them before Wednesday that way I can implement them all on Wednesday and then get a stable out by Friday 😅

If you have any other issues/feature requests please try to report them before Wednesday that way I can implement them all on Wednesday and then get a stable out by Friday 😅

Actually there's one thing.

With Limit File Name Characters turn on, Tagger ignored space before, between & after that limited characters, is that the intended behavior?

With Limit File Name Characters turn on, Tagger ignored space before, between & after that limited characters, is that the intended behavior?

Hmm...no it's not intended. Will take a look at it tomorrow to see what's going on.

With Limit File Name Characters turn on, Tagger ignored space before, between & after that limited characters, is that the intended behavior?

@kissthermite Can't reproduce...
Here's WinUI:

Here's GNOME:

I think it just seems every small in GNOME but the space is indeed there.

Yeah. My bad just check it again and indeed it's just a very tiny space.

I was going to release a beta but decided against it since it's almost Friday and if any bugs come up before then I will fix them and just release stable. Since your issue was confirmed to be fixed, no need for a beta.


JavaOne session presentation

Just a marker for presentation for this session:
Game On! Exploring Microservices with a Text-Based Adventure Game [CON1559]
Erin Schnabel, Senior Software Engineer, IBM
Creating a single microservice is easy, as walkthroughs everywhere show. See? Add a few annotations, invoke this command to build it, and you have a running microservice! Ta-da! But what happens next? Game On! is an interactive text adventure written as a collection of microservices to help people answer that very question. This session covers how the speaker and her colleagues used service composition and discovery, API definition and versioning, security (authentication, authorization, and identity propagation), the 12 factors, and a combination of lightweight protocols to build the game. The presentation also discusses what they learned from building it and from others extending it.
Conference Session
Thursday, Sep 22, 2:30 p.m. - 3:30 p.m. | Parc 55 - Embarcadero

http://www.slideshare.net/ErinSchnabel/con1559-javaone-2016-game-on-exploring-microservices-with-a-textbased-adventure-game


spin up --follow-all no longer supported

This command is used in multiple SDK instructions. What's the guidance going forward?
https://github.com/fermyon/spin-dotnet-sdk#building-the-hello-world-sample
https://github.com/fermyon/spin-js-sdk/tree/main/examples/javascript/hello_world#running-the-example

Thanks for the spot.  That pesky option seems to have got everywhere.  The guidance going forward is to leave it out - it's now the default behaviour of Spin.  I will update the docs!

Another place it appears is README on Bartholomew template project.
$ spin up --follow-all
Serving HTTP on address http://<IP_ADDRESS>:3000
Available Routes:
  bartholomew: http://<IP_ADDRESS>:3000 (wildcard)
  fileserver: http://<IP_ADDRESS>:3000/static (wildcard)

Instead of this, I would recommend using:
$ spin watch --skip-build


[bug] @unocss/transformer-variant-group not working with HMR with @unocss/nuxt

I'm using @unocss/nuxt in nuxt3 with vite on node v17.6.0
I'm using @unocss/transformer-variant-group to use group variants like this

    {{ $t('hello') }}

    {{ $t('welcome', { name: 'world' }) }}

as expected styles are being transformed to on reload or initially

after making changes to the file, transformation doesn't work on HMR it pushes classes as written

Getting Failed to parse bg-xy-100-0) Error: Unbalanced parenthesis error on output log on vscode

I think this might be linked to https://github.com/unocss/unocss/issues/954. I am also experiencing this issue.
Here's a repro: https://stackblitz.com/edit/github-qz67ei?file=pages/index.vue

Hi all 👋🏻
I have solved mine #954 by adding configDeps option in UnoCSS config
configDeps: ['../anu-vue/src/presets/theme-default/index.ts'],

index.ts is a single preset file where I make changes and it resolved my issue.
Please let me know if works for you.

I think you are right this happens for the page only. Components Used on page works as expected.


feat(ado-ext-telemetry): update canary release pipeline to allow an extension version override

Details
This allows for the canary release pipeline version to be overridden.  Before this, even if the versionOverride parameter was set, it would look at the ado-extension-canary variable group and throw it out.  This allows us to upgrade the canary version by overriding the default 'ignore-if-canary' parameter in the build.
We need this to be able to upgrade the major version of Canary as we prepare to merge in breaking changes.
Motivation
Feature work
Context

Pull request checklist

[n/a] Addresses an existing issue: Fixes #0000
[n/a] Added relevant unit test for your changes. (yarn test)
[n/a] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
[x] Ran precheckin (yarn precheckin)
[ ] (after PR created) The Accessibility Checks (pull_request) check should fail. All other checks should pass.

Codecov Report

Merging #1093 (ef7e207) into main (be245d4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1093   +/-   ##
=======================================
  Coverage   89.65%   89.65%
=======================================
  Files          54       54
  Lines        1286     1286
  Branches      151      151
=======================================
  Hits         1153     1153
  Misses        133      133

Continue to review full report at Codecov.

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


Need to produce strong/weak dill for non-nullable experiment/web

Commit 06de567811be0cb4eaf05254f0615ba819bb673c
Input:
C:\Users\Jonah\flutter\bin\cache\dart-sdk\bin\dart.exe --disable-dart-dev
C:\Users\Jonah\flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-root
C:\Users\Jonah\flutter\bin\cache\flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names
-Ddart.developer.causal_async_stacks=true --output-dill
C:\Users\Jonah\AppData\Local\Temp\flutter_tools.57e8833f\flutter_tool.f7d77af3\app.dill --libraries-spec
file:///C:/Users/Jonah/flutter/bin/cache/flutter_web_sdk/libraries.json --packages .packages -Ddart.vm.profile=false
-Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions --enable-asserts --track-widget-creation --filesystem-root
C:\Users\Jonah\AppData\Local\Temp\flutter_tools.57e8833f\flutter_tools.13504d14 --filesystem-scheme org-dartlang-app
--initialize-from-dill build\cache.dill.track.dill --platform
file:///C:/Users/Jonah/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk.dill --enable-experiment=non-nullable

Error:
[   +5 ms] <- compile org-dartlang-app:/web_entrypoint.dart
Error: Unable to read the 'libraries.json' specification file:
  No library specification for target "none".

this might be just due to a missing strong mode dill, it might be fixed by the engine roll

The latest engine update did not resolve the situation

We need to produce both a weak and strong mode dill in the engine build, and conditionally switch based on the experiment.

Blocked on dart:_engine migration.

The dart_engine migration has landed, now waiting on https://github.com/flutter/engine/pull/19162 to land and roll

Fixed via https://github.com/flutter/engine/pull/19386


⚠ ClamAV has degraded performance

In 14cd01d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: ClamAV performance has improved in 8b82347.


open viewlet on showPreview (#10474)

open viewlet on shoePreview

on showPreview reveal explorer

This port fixes #10469

@MaddyDev, I don't see the approved tag on the bug. Can you check on teams if this issue was approved or not?


How can I choose the subdirectory?

Hi,
How can i choose subdirectory,
define('LAZER_DATA_PATH', '../db/') or define('LAZER_DATA_PATH', realpath(__DIR__).'/../db/')
not working.
Thanks.

here is the solution
define('LAZER_DATA_PATH', $_SERVER['DOCUMENT_ROOT'].'/kernel/db/');

There 1% mistake in your code: corrected below:
define('LAZER_DATA_PATH', realpath(__DIR__ . '/../db/'));

You can also define ROOT constant on index.php and supply it in realpath function.

Thanks so much.


xls-workshop-openlane: add diy section

add diy section for people to work on their own design

TEST=https://colab.research.google.com/github/proppy/silicon-notebooks/blob/workshop-diy/xls-workshop-openlane.ipynb
@shige-compit @t-sasatani do you think we need something like this?

I think it'll be better to have that (although we can probably ask re-using or copying the multiplier code blocks)

@t-sasatani what would be the Japanese equivalent? 自由研究?

I think just English is ok for that part because there's no real equivalent word (also 自由研究 makes me feel like I need to submit a report!)

rebased and added japanese equivalent.

@shige-compit reviewed offline and suggested the rewording


entropy grid doesn't show in Preview

if you choose a pattern at the very bottom of the entropy grid, it doesn't show in the Preview

We need to have to scale down and keep it in the same proportion to view in preview.

Resolved,

Verified this on Tribe app v 2.2.7(606)


Not able to add a user.

Alarmo Version
version v1.9.0
HA Version
Home Assistant 2021.11.5
Bug description
After selecting "Code" enable "Use disarm code" >> "New User" the page loads to the option for "Create new user" but there is no field to enter "Name, code, confirm code".
So I'm basically stuck at this point.
Please Help!
Steps to reproduce
Setting Alarmo Panel
Relevant log output
No response

You need to update HA to use Alarmo.

What are the steps to update please?
I don’t have the supervisor option.

See https://github.com/nielsfaber/alarmo#updating


$.before(...) & $.after(...)

Sometimes you only have a fragment of HTML and you want to add content to from or back of it.

Wait, aren't there already .before() and .after() methods?

So I've run into a case where I don't know what the html is, but I want to add elements in front of it or behind it.
In jQuery, I could do $(document).prepend('
Hi
'), but currently there isn't a way to query the root element.

Would $(":first").prepend("
Hi
") or $("html").prepend("..") work? This would get the root html element and let you append or prepend whatever.

Hm... the first one might work.. what about fragments that don't include the  tag

I think $(":first") should work just about anywhere, regardless of tag.

Now all you need to do is:

$(":root").append(...); // append as a child of the root element
$(":root").prepend(...); // prepend as a child of the root element

Hmm.. I like this functionality but I think it should be moved to cheerio-soupselect. The selector engine should function without cheerio, and while :root may make sense in cheerio, but what about selectors like :even, :nth-child. If we keep adding features like these to cheerio, the soupselect library lags behind in functionality.

I'll close this ticket, because the ongoing discussion doesn't really relate to before() and after(), but where the code should be placed.

I've already implemented all the basic selectors in soupselect. Things like :first, :even, :odd etc are baked in. :root needs to be in cheerio because there is no way to reference the cheerio.root object from soupselect.


Fix optimistic updates of lists

closes https://github.com/refinedev/refine/issues/3652
Self Check before Merge
Please check all items below before review.

[x] Corresponding issues are created/updated or not needed
[x] Docs are updated/provided or not needed
[x] Examples are updated/provided or not needed
[x] TypeScript definitions are updated/provided or not needed
[x] Tests are updated/provided or not needed
[x] Changesets are provided or not needed

Hello @fuunnx code looks good, we have a CI failure caused by us. We'll fix it and merge your PR ASAP.

@fuunnx We've merged the test fixes, can you rebase your PR with origin and generate changeset?
https://refine.dev/docs/contributing/#changeset

Done :heavy_check_mark:


TypeScript validity

When importing import getCatalog from "@catalogs"; in _app.tsx TSlint shouts "Cannot find module<EMAIL_ADDRESS>Is there a way how to import catalogs more explicitly so there is no problem within checks?

@cJayyy You can try this in your typings/index.d.ts :

```js
declare module "@catalogs" {
  const content: any;
  export default content;
}


Build Failure: Git Clone Error for Dependency in Virtual Environment Setup

The build process fails during the setup of a virtual environment due to a git clone error when attempting to install the download_link_replacer package from a GitLab repository. The error indicates that the connection to https://gitlab.tudelft.nl was refused, likely due to network, server, or repository access issues?
Run python -m venv .venv
  python -m venv .venv
  source .venv/bin/activate
  python -m pip install -r requirements.txt
  echo "$VIRTUAL_ENV/bin" >> $GITHUB_PATH
  echo "VIRTUAL_ENV=$VIRTUAL_ENV" >> $GITHUB_ENV
  shell: /usr/bin/bash -e {0}
  env:
    GITHUB_TOKEN: ***
    GH_TOKEN: ***
    PRIMARY_BRANCH: main
    BEHAVIOR_PRIMARY: redirect
    BRANCH_ALIASES:
    BRANCHES_TO_DEPLOY: *
    BRANCHES_TO_PREPROCESS:
    BRANCHES_ARCHIVED:
    pythonLocation: /opt/hostedtoolcache/Python/3.11.11/x64
    PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.11.11/x64/lib/pkgconfig
    Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.11/x64
    Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.11/x64
    Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.11/x64
    LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.11/x64/lib
    WEEK: 50
Looking in indexes: https://pypi.org/simple, https://gitlab.tudelft.nl/api/v4/projects/11239/packages/pypi/simple
Collecting download_link_replacer@ git+https://gitlab.tudelft.nl/mude/sphinx-download-link-replacer (from -r requirements.txt (line 15))
  Cloning https://gitlab.tudelft.nl/mude/sphinx-download-link-replacer to /tmp/pip-install-03k7rwll/download-link-replacer_a97904fdc13749cda64af655ef1b0a3e
  Running command git clone --filter=blob:none --quiet https://gitlab.tudelft.nl/mude/sphinx-download-link-replacer /tmp/pip-install-03k7rwll/download-link-replacer_a97904fdc13749cda64af655ef1b0a3e
  fatal: unable to access 'https://gitlab.tudelft.nl/mude/sphinx-download-link-replacer/': Failed to connect to gitlab.tudelft.nl port 443 after 197 ms: Connection refused
  error: subprocess-exited-with-error

  × git clone --filter=blob:none --quiet https://gitlab.tudelft.nl/mude/sphinx-download-link-replacer /tmp/pip-install-03k7rwll/download-link-replacer_a97904fdc13749cda64af655ef1b0a3e did not run successfully.
  │ exit code: 128
  ╰─> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× git clone --filter=blob:none --quiet https://gitlab.tudelft.nl/mude/sphinx-download-link-replacer /tmp/pip-install-03k7rwll/download-link-replacer_a97904fdc13749cda64af655ef1b0a3e did not run successfully.
│ exit code: 128
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

Notice:  A new release of pip is available: 24.0 -> 24.3.1
Notice:  To update, run: pip install --upgrade pip
Error: Process completed with exit code 1.

thanks @anmpahwa !! This was because the TU Delft gitlab site was down this morning. It is not as reliable as GitHub, but we haven't been able to move all of our tools over to github yet. Should be OK now since GitLab is back online.

Actually, @anmpahwa we have moved the sphinx download link replacer over to GitHub, along with a few other tools. You can take a look at the requirements.txt file in the template to see our up-to-date list of things we have moved. We haven't come up with a good way for users to find out about this, let us know if you have ideas!
https://github.com/TeachBooks/template/blob/main/requirements.txt


clarity on behaviour of ports in network policies

This is a Feature Request
What would you like to be added
Add clarity around the behaviour of ports
On this page I think it could be made clear that, for example.
  egress:
    - to:
        - ipBlock:
            cidr: <IP_ADDRESS>/24
      ports:
        - protocol: TCP
          port: 5978

allows traffic to <IP_ADDRESS>/24 on port 5978.
While
  egress:
    - to:
        - ipBlock:
            cidr: <IP_ADDRESS>/24
    - ports:
        - protocol: TCP
          port: 5978

allows traffic to: <IP_ADDRESS>/24 on any port
and also allows traffic to: anywhere on port 5978.
Comments
Happy to pick this one up myself

/language en
This is partly about ports, but more around understanding the difference between a (YAML) collection of two rules and a (YAML) collection of one rule.

Yeah it took me a little while to even see why the two had different behaviour. I don't know that clarifying on this page alone will be very useful. @sftim or open question: would a page similar to https://docs.ansible.com/ansible/latest/reference_appendices/YAMLSyntax.html help at all? Or would that not be a meaningful addition to our docs?

I think we can definitely explain the gotcha, perhaps with a clear hint to go and learn YAML for all the details about collections.
It's an easy mistake to make with a NetworkPolicy whereas it's not something you'd commonly get wrong with a set of (say) init containers. What we should try hard to avoid is repeating “here's how YAML works, from the bottom up”.

Good point, I like the idea of linking to somewhere useful like w3schools to learn more about yaml if they arent experienced users

I think there's a point about the api behaviour as well. In my opinion the page isn’t fully clear that the api does not require a to block under ingress. Either a to block, a ports block or both are equally valid.
This only becomes clear when you look at the reference docs: https://kubernetes.io/docs/reference/kubernetes-api/policy-resources/network-policy-v1/ - keen to get other's thoughts on this though.

I think the point underneath that talks about ingress and egress makes that evident no? Ingress allows traffic that matches the from and ports sections, and egress allows traffic that matches the to and ports sections.


 Don't understand what I'm saying? Try yourself.
The reason why I'm doing this is because it makes me motion sick

Will be fixed in V.2.7.1.


Some tweaks needed for the walkthrough

Hi everyone,
Here are a few things we should implement in the onboarding (remember that the first impression is essential).

[ ] The language picker is really small => add some Padding

[ ] The country picker is confusing:

We should add a title to remember what we ask the user
I wonder if some dividers wouldn't be nice here
There is no scrollbar

[ ] #4235

[ ] We don't understand what's that cut card

[ ] The line height in the description is smaller than the other parts of the app on the permission's page

https://github.com/openfoodfacts/smooth-app/assets/39344769/98c15c6c-9514-4b95-8c0a-c1d414360848

We should remove hungergames from this card

Either hide the compare to category or just Show a tooltip like the preferences icon on this card

We don't understand what's that cut card

I agree, we should make it expanded by default (remove the small version)

We can move the preferences to the next Page, a full Page for this major features isn't to much. I expect a lot of people to never scroll to them

@g123k @M123-dev The rationale for having the prefs card on the same page as the prefs toggle was to see your match evolve in real time as you tweaked it. What if we moved it to an overlayed bottom panel or something ?

@g123k @M123-dev The rationale for having the prefs card on the same page as the prefs toggle was to see your match evolve in real time as you tweaked it. What if we moved it to an overlayed bottom panel or something ?

Interesting. I never understood that this page was interactive this way.
I won't speak for everyone, but if I don't understand the pattern, I'm pretty sure I'm not the only one here.
The goal of this issue was to quick fix the onboarding with minor changes.
This particular case requires more work. So, what could be the "minimal changes" for this screen?

Expand the card by default?
Hide the Robotoff Widget?

And after, let's take some time to really improve the page

Yes, I have never bothered to scroll down, I think most don't know that that's possible.

This particular case requires more work. So, what could be the "minimal changes" for this screen?

Expand the card by default?
Hide the Robotoff Widget?
And after, let's take some time to really improve the page

Sounds good


Style for table support

@tobiju It would be great to have a table style with the following features:

Table width 100%
Table Borders
thead/tfoot > th should have a light background color

What do you think?

I think we need now some javascript to handle the table in responsive layout. We should add the default table class per js and add some wrapper div with overflow auto.


Bump deps

itertools 0.9 -> 0.10
unicode-segmentation 1.0.0 -> 1.9.0
regex 1.0 -> 1.5
term 0.6 -> 0.7
env_logger 0.8 -> 0.9
unicode-width 0.1.5 -> 0.1.9
dirs 2.0.1 -> 4.0.0
ignore 0.4.17 -> 0.4.18
annotate-snippets 0.8 -> 0.9
lazy_static 1.0.0 -> 1.4.0

Thanks for your first contribution to the project and for helping to keep the dependencies up to date! Looks good to me!

Thanks for this. I've been meaning to take a look at the deps for a while, but there's some subtle complexity that only surfaces upstream in rust-lang/rust where rustfmt and other tools are consumed as git submodules or subtrees. There was one that's always a pain but I can never seem to remember which one it is.
I suspect this will be fine but need to do a little digging first before proceeding

I think it's rls.
❯ rg --fixed-strings 'git+' --type toml
src/tools/rls/Cargo.lock
129:source = "git+https://github.com/rust-lang/cargo?rev=1c034752de0df744fcd7788fcbca158830b8bf85#1c034752de0df744fcd7788fcbca158830b8bf85"
134: "cargo-platform 0.1.2 (git+https://github.com/rust-lang/cargo?rev=1c034752de0df744fcd7788fcbca158830b8bf85)",
196:source = "git+https://github.com/rust-lang/cargo?rev=1c034752de0df744fcd7788fcbca158830b8bf85#1c034752de0df744fcd7788fcbca158830b8bf85"
204:source = "git+https://github.com/rust-lang/cargo?rev=1c034752de0df744fcd7788fcbca158830b8bf85#1c034752de0df744fcd7788fcbca158830b8bf85"
289:source = "git+https://github.com/rust-lang/rust-clippy#496f26c2297c0117a24c3d26172fd72b5f9ad927"
310:source = "git+https://github.com/rust-lang/rust-clippy#496f26c2297c0117a24c3d26172fd72b5f9ad927"
370:source = "git+https://github.com/rust-lang/cargo?rev=1c034752de0df744fcd7788fcbca158830b8bf85#1c034752de0df744fcd7788fcbca158830b8bf85"
1875:source = "git+https://github.com/rust-lang/rustfmt?rev=5056f4cfb311a084420f1828cd58af94d143f5e0#5056f4cfb311a084420f1828cd58af94d143f5e0"
1885:source = "git+https://github.com/rust-lang/rustfmt?rev=5056f4cfb311a084420f1828cd58af94d143f5e0#5056f4cfb311a084420f1828cd58af94d143f5e0"

compiler/rustc_codegen_gcc/Cargo.lock
44:source = "git+https://github.com/antoyo/gccjit.rs#0672b78d162d65b6f36ea4062947253affe9fdef"
52:source = "git+https://github.com/antoyo/gccjit.rs#0672b78d162d65b6f36ea4062947253affe9fdef"

compiler/rustc_codegen_cranelift/Cargo.lock
14:source = "git+https://github.com/bjorn3/rust-ar.git?branch=do_not_remove_cg_clif_ranlib#de9ab0e56bf3a208381d342aa5b60f9ff2891648"

I think it's rls.

Nah that's not what I was thinking of. There used to be a ceiling on one of these due to the workspace hack but I think that may have been sorted. I'm waiting for a couple PRs to land in rust-lang/rust before syncing the subtree over here as they have some relevant changes. Apologies in advance as there's a decent change that will introduce some merge conflicts for this PR, but it's been too long since I've done a sync and I need to get the upstream changes incorporated here.
Will drop a note when that's done so you'll know when to rebase and deal with any conflicts

Upstream changes have been pulled in, happy to move forward with this after you rebase and address conflicts :+1:

rebased and make the deps sorted


fix issue 1007 Rate send email limit

/claim #310 If any changes please pin me

Make sure to re-read the issue and emulate how the GitHub integration handles this issue.


How to hide the pagination dots?

i've recently working on a product display menu
<carousel :items-to-show="3" :navigation="false" :pagination="false">  <slide v-for="slide in 1" :key="slide">

   </slide>
i already try to make  it false but it doesn work.
anyone have idea?

Do you have more information about your code ?
With the example, I don't have navigation

<template>
  <Carousel :items-to-show="1">
    <Slide v-for="slide in 10" :key="slide">
      {{ slide }}
    </Slide>

    <template #addons>
      <Navigation />
    </template>
  </Carousel>
</template>

You can simply remove the Navigation addon component and display only the slides.
<template>
  <Carousel :items-to-show="1">
    <Slide v-for="slide in 10" :key="slide">
      {{ slide }}
    </Slide>
  </Carousel>
</template>


Neuron version?

Are you using neuron v1 or the development version?

I am using neuron v1

I am using neuron v1

Thanks -
I'm messing around with your code, to make it work with my setup using neuron 1.9
You're welcome to take a look at my 'develop' branch
Cheers 👍

Thanks -
I'm messing around with your code, to make it work with my setup using neuron 1.9
You're welcome to take a look at my 'develop' branch
Cheers 👍

I have started using the development version of neuron. I merged your branch into my unstable branch. You are welcome to make prs to it.

I have started using the development version of neuron. I merged your branch into my unstable branch. You are welcome to make prs to it.

Fantastic! Let's make something great

Fantastic! Let's make something great

I was having some issues to get neuron.nvim to work a week or so ago, I think that may have been do to version problems. The first I've heard about neuron and this style of notetaking was from this repo, so I didn't know exactly how to get it working. I'll try again and mess around with different versions.

I was having some issues to get neuron.nvim to work a week or so ago, I think that may have been do to version problems. The first I've heard about neuron and this style of notetaking was from this repo, so I didn't know exactly how to get it working. I'll try again and mess around with different versions.


fix: trying to access addressable settings while editor is compiling

Its documented limitation of AddressableAssetSettingsDefaultObject.Settings will return null if being accessed while Editor is compiling or updating.  This provides a workaround to remove the null Settings error.

Closes #65

This works for AddressablesChangeListener. However, the generator also has the same problem, but the solution there won't be as simple. I want to figure out a solution there and merge the two together with this PR.

I've updated this patch and used the same word-around for the SceneAssetProcessor (which is the other culprit of calling SceneDataMapsGenerator.Run() too soon).

Yeah, what worries me is batchmode builds, because if quit flag is given, delays may misbehave. We need some rigorous testing there.

May be superseded by #87.

Superseded by #87.


Added menu and action bar interactions

New features

Interactions with options menu
Interactions with action bar

Sample code

Created activity with options menu and action bar

Tests

Added 3 tests to validate new features
All tests passing, except for 2 which are already failing in develop

@cs-bruno-silva what do you think?


Errors are needed when referring to local things outside of the project

See original issue on GitLab
In GitLab by [Gitlab user @tristanvb] on Jan 16, 2018, 13:29
This currently includes:

Referring to local plugins from project.conf using relative paths which lead outside of the project directory
Referring to files or directories which lead outside of the project directory in local source path: configuration

Also relevant, is usage of symlinks in a project directory which lead outside of the project, but are in any way required to build the project, this can happen for both of the above mentioned cases (using proper paths which refer to symlinks which instead attempt to crawl out of the project directory).
In any of these cases, BuildStream should abort early with an error message.

In GitLab by [Gitlab user @tristanvb] on Jan 17, 2018, 13:05
Note, the same must be checked on the project's element-path.

In GitLab by [Gitlab user @tristanvb] on Jan 17, 2018, 13:06
mentioned in merge request !181

In GitLab by [Gitlab user @juergbi] on Feb 12, 2018, 10:01
mentioned in merge request bst-external!9

In GitLab by [Gitlab user @tristanvb] on Jul 17, 2018, 09:06
Note that in order to avoid breaking builds, we need to wait for https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/229 to be fixed in order to properly police and enforce the expected project behavior.

In GitLab by [Gitlab user @jjardon] on Jul 17, 2018, 10:11
[Gitlab user @tristanvb] No need to wait for us: we depend on a specific version of bst, so no build will be broken, see https://gitlab.com/freedesktop-sdk/freedesktop-sdk/issues/229#note_88422229

In GitLab by [Gitlab user @tristanvb] on Jul 27, 2018, 07:14
Some additional implementation notes:

This needs a low level private API to do the grunt work of asserting a project path

A project path must not escape the project
A project path must not have symlink components which maliciously escape the project
This function might raise an exception, or return a boolean

For best convenience of plugin authors and user experience, we should add a public method to Plugin

This belongs to the YAML node manipulation family, something like Plugin.node_load_project_path()
This behaves similarly to calling Plugin.node_get_member() when loading a string, except that it additionally validates the string using the private utils function mentioned above
If the project path is not a valid one, it raises a PluginError() with the appropriate Provenance (see Plugin.node_provenance() etc)

local source needs to use the new Plugin API to load it's path
patch source needs to do the same
ostree source needs to do the same (for the loading of it's gpg file for validation)
_project.py needs to also validate some paths, using a private utility

The element-path
Paths related to local plugin loading locations

Since we always raise the error when extracting the string from the YAML dictionary nodes, maybe we want the private API to be in _yaml.py instead, or have a layer there at least; whichever makes more sense. Point being that we also want the Provenance (filename, line, column) information for any error we encounter at load time.

In GitLab by [Gitlab user @tacgomes] on Jul 27, 2018, 11:29
assigned to [Gitlab user @tacgomes]

In GitLab by [Gitlab user @tacgomes] on Aug 1, 2018, 12:10
mentioned in merge request !593

In GitLab by [Gitlab user @tacgomes] on Aug 2, 2018, 12:39
mentioned in merge request !598

In GitLab by [Gitlab user @tacgomes] on Aug 2, 2018, 14:28
closed

In GitLab by [Gitlab user @toscalix] on Aug 3, 2018, 08:59
reopened

In GitLab by [Gitlab user @toscalix] on Aug 3, 2018, 09:14
closed

In GitLab by [Gitlab user @tchaik] on Sep 2, 2018, 13:44
mentioned in commit tchaik/gnome-build-meta[Gitlab user @107d3d4293cf34e001e0e34e7045bab740a590e6]

In GitLab by [Gitlab user @bochecha] on Sep 17, 2018, 11:15
mentioned in commit 48cca433b0ab5ca0d49b49ec5e7099ddfd9c8873

In GitLab by [Gitlab user @tristanvb] on Mar 6, 2019, 08:15
marked this issue as related to #946


dealing with $0 in receive name in [comment]

I'm trying to include something like the  iemgui_init_sym2dollararg  function from iemguis into [comment]. This is used to enable saving a GUI object with a receive name containing an unexpended '$0", so it gets saved as something like "$0-x" instead of something like "1003-x".
This is the code...
https://github.com/pure-data/pure-data/blob/418428350f6a3f4aebf8b378dbefea39c38b4ee5/src/g_all_guis.c
/* initialize a single symbol in unexpanded form.  We reach into the
binbuf to grab them; if there's nothing there, set it to the
fallback; if still nothing, set to "empty". */
static void iemgui_init_sym2dollararg(t_iemgui *iemgui, t_symbol **symp,
int indx, t_symbol *fallback)
{
if (!*symp)
{
t_binbuf *b = iemgui->x_obj.ob_binbuf;
if (binbuf_getnatom(b) > indx)
{
char buf[80];
atom_string(binbuf_getvec(b) + indx, buf, 80);
*symp = gensym(buf);
}
else if (fallback)
*symp = fallback;
else *symp = gensym("empty");
}
}

If I get it right, binbuf_getvec(b) creates an atom with the arguments inserted in the object, then             atom_string is used to copy a specific argument string. Seems easy.
So put something in the save code that's like:
t_atom *a = binbuf_getvec(x->x_ob.ob_binbuf);
char buf[80];
atom_string(a + 3, buf, 80);
receive = gensym(buf);

problem is that I get an error when trying to save which says "consistency check failed: atom_string".
Funny enough, if I try this outside the save code, somewhere else I invented, called comment_getarg, I dont get the error.
Anyway, this is the very last thing I wanted to do for the final release...

see: https://github.com/porres/pd-cyclone/blob/master/cyclone_objects/binaries/control/comment.c
lines 405 include comment_getarg
and 414 starts comment_save

The receive message is also not working with "$0" as it works in iemguis

this is done with a few commits up to https://github.com/porres/pd-cyclone/commit/90d6db1089e2b708a896907bf95f878089747870


On initial load fetch latest assets for user who has already visited website

Thanks for the great plugin. I'm new to SW, wanted to ask a quick question:
Consider a user who has already visited opens website after a few days. Initially old assets from SW will be loaded and then latest assets will be downloaded in the background. Once new version is downloaded an update dialog can be shown to user.
I think its apt to show dialog box for user who is active on site for a while.(using autoUpdate feature)
I find it strange in showing the dialog to the user who is visiting after long time, completed a initial webpage load and then showing update dialog to refresh page again. Is it possible to load the latest version for these users?
I have read through docs and couldn't find anything related to this. Let me know if I'm missing something.

Just apply update without dialog and reload the page.

I wrote that assuming you already know how to handle offline-plugin events and already showing a dialog to the users. So pretty much you just need to detect your case somehow (user came back after some time) and just reload the page after update.

Thanks for the reply. I tried what you have mentioned earlier and found that page refreshes twice. Can it be possible to do in a single reload?

Nope. It has to update and then reload to has the update to take effect. When users load page they just load it from the cache, so not possible in one load.
You may try to set responseStrategy: 'network-first', in this case all requests first will be trying to get content from the network and if that fails, they will fallback to the cache.

Cool, I will try that out. Thanks for helping out!

@NekR responseStrategy: 'network-first' is what I was looking for! works like a charm :)

Great :-)


Add option to readback and verify written flash

It would be nice to have something like --verify which reads back all written flash and checks it was written correctly. In GDB you can do this with compare-sections for example.

This has been fixed in #1694 I believe


Angular Material 2 shows errors in node_modules

Bug, feature request, or proposal:
What is the expected behavior?
What is the current behavior?

What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
typescript version - 2.2.0
VSCODE version - 1.6.1

Can you show your package.json?

@WonderfulNature do you get the same errors when you try to compile outside of vscode? Also package.json as @Chan4077 mentioned

This is caused by using a version of TypeScript less than 2.2. Be sure you clear your node_module and package-lock.json before reinstalling.


screenshot: don't take a screenshot while the Notifier is flashing

Close #12309
This change adds isFlashing() to the Notifier class and has the ScreenShotOverlay only take screenshots when the Notifier isn't flashing.

Didn't mean to approve was trying to leave a comment. Did anything ever come of this?


stake-pool: Refresh blockhash more often on update tests

Problem
The stake pool tests still fail CI randomly.  This may be due to a known issue of transactions short-circuiting if they have the same signature, e.g. doing the same transfer twice with the same blockhash.  This might be causing some tests to timeout in CI.
Solution
Refresh the blockhash more often in the update_validator_list_balance* tests.

One day, this will be totally stable.  Until then, we fix CI errors!


Add PerformanceObserver

https://developer.mozilla.org/en-US/docs/Web/API/PerformanceObserver
Used for monitoring performance. Currently seems to work only in Firefox 49 and Chrome 52

https://w3c.github.io/performance-timeline/#the-performanceobserver-interface

Available at https://caniuse.com/#feat=mdn-api_performanceobserver


add ToggleableOutputPin to the prelude

Should StatefulOutputPin also be in the prelude? It seems to me that is_set_{low,high} are less common than toggle, but those two methods were in the v0.1.x prelude because they were part of OutputPin and OutputPin was in the v0.1.x prelude.

Should StatefulOutputPin also be in the prelude? It seems to me that is_set_{low,high} are less common than toggle, but those two methods were in the v0.1.x prelude because they were part of OutputPin and OutputPin was in the v0.1.x prelude.

I can't think of a good reason why it shouldn't be in there.

StatefulOutputPin is definitely needed! (For example for 1-wire protocol implementations using an open drain output pin.)


[BEAM-6597, BEAM-6467] Add support for reporting monitoring infos to the Java SDK harness.

This also exposes a requestProgress API on the RemoteBundle allowing runners to request progress.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @ajamato
CC: @boyuanzz @ananvay

Run Java PreCommit

Run Java PreCommit

Looks like this broke the Go Portable Postcommit tests on Flink and Spark
https://builds.apache.org/job/beam_PostCommit_Go_VR_Spark/3093/
https://builds.apache.org/job/beam_PostCommit_Go_VR_Flink/3155/

Taking a look.

Initial look doesn't seem

Looks like this broke the Go Portable Postcommit tests on Flink and Spark
https://builds.apache.org/job/beam_PostCommit_Go_VR_Spark/3093/
https://builds.apache.org/job/beam_PostCommit_Go_VR_Flink/3155/

I took a look and ran the test on my pre-merged branch called metrics and the test passed. It looks like another change may have broken them.


Change print() to logging.info() #48

Replaced print statements with logging in various files to improve logging consistency, clarity, and debugging capabilities.
Updated logging statements in the following files:

./data_io/UnBinnedData.py
./data_io/ReadTraTest.py
./data_io/BinnedData.py
./threeml/COSILike.py
./spacecraftfile/SpacecraftFile.py

@krishnatejavedula I went over all the changes in this PR and everything looks good. I tested the code for the dataIO using new unit tests that I've prepared locally, and everything works fine. I also tested the dataIO tutorial notebook with no problems.
The only issue is that with the current (default) configuration, all of the logging info is effectively lost, i.e. it's not printed to terminal, nor saved to file. However, it is highly beneficial to have both. The terminal output is needed to update users on the flow of the analysis (when running from command line or in a notebook), and writing to a log file is useful for future reference.
Only the root logger needs to be configured, since all the lower level loggers at module level eventually forward their messages to its handlers. I think a good place for the root logger is in cosipy/config/configurator.py. So in this file I would suggest that you add the following lines:
import sys
logging.basicConfig(filename='cosipy.log', level=logging.INFO)
logging.getLogger().addHandler(logging.StreamHandler(sys.stdout))

This will print all logging info to stdout, and save it to a log file called cosipy.log (in the working directory). Note that by default, the logging level will be INFO. In the future we can set this as an input, e.g. to allow users to set it to DEBUG if needed, or a lower verbosity (ERROR) if they don't want any logging info for some reason.
I'll get @israelmcmc in the loop here to see what he thinks, b/c this ultimately relates to issue #26, and having a standard logging across all modules.
After making the above changes, I think this PR can be merged.

Note that DataIO.py already reads the input yaml file using Configurator(), and so it automatically uses its logger config.

Actually will need to think about how to setup the root logger somewhere.

Thanks for reviewing @ckarwin!
TL;DR: I think this one can be merged now.
It's best practice that the root logger is not configured by the library but by the user (discussed here). Cosipy can be used as part of an even larger codebase, and who knows what they want to do then. This flexibility and customizability by the final user is actually the main reason to use logging instead of print statements.
By default, only warnings are printed to stderr (discussed here). The rationale, I assume, is that good code works like a black box, and you only want to be bothered if something goes wrong and needs attention. Also, the default is stderr and not a file because that way the user can redirect all the logs to a single place without having to worry about what the internal pieces of code are doing do.
That said, I agree that using the INFO level is beneficial for most of our purposes, especially at this point in the development. We can simply add the following to the notebooks and our executable scripts (applications):
import logging
logging.basicConfig(level=logging.INFO)

Our applications should have a -v option that controls the verbose, which will be translated to e.g. 0 = warning only, 1 = info, 2 = debug.
I rather not output to a file by default, because then:

You won't see the result in a jupyter notebook cell, which is awkward when working with interactive notebooks
For an executable scripts, you lose the ability to redirect stderr to a file of your choice with 2> in the command line.

It would be convenient for our application to have an optional flag to save the logs to a file though.
This should all be part of the global config yaml file as well.
And yeah, I should write all of this down in a style guide so it can be discussed and followed.
In any case, I think this is all for future PRs, I think this one can be merged now.

Yeah, maybe outputting to both a file and stderr is a good idea. I guess we care more about reproducibility than the regular software, and this might be a saver.

Thank you @israelmcmc and @ckarwin for your feedback. This helps a lot. I am glad the PR is merged. I will be working on the rest of files mentioned in #48 and open a PR for them shortly so the issue could be closed.


chore(finish): write documentation

#149448565 write api documentation
#### What does this PR do?
#### This PR adds documentation

#### Description of Tasks to be completed
#### N/A

#### How should this be manually tested?
#### N/A

#### Any background context you want to provide?
#### No

#### What are the relevant pivotal tracker stories?
#### Write API Documentation

#### Screenshots (if appropriate)
#### None

#### Questions:
#### None

Coverage decreased (-1.0%) to 87.234% when pulling 8951b4ae5e3f77192abdaa0a1701f3e6a1c36655 on chore/149448565/write-documentation into 502d1861974b5502ac2a353d304caa8dad4a1c48 on master.


bitcoincash:// URL not supported

Bitcoin-com-wallet-3.6.0 on Android 6.0
Tried to send BCC from Bitcoin.com Android wallet to "Electron-Cash" desktop wallet, but FAILED: because protocol URL specified is "bitcoincash://" which Bitcoin.com wallet is unable to parse. I tried via QR code "scan" method.
Manually editing the URL address worked. So I was able to send and receive.
Electron-Cash, when generating receive address, adds bitcoincash:// URL prefix.
Bitcoin.com wallet should handle it.
-Technologov, 02.09.2017.

Voting for support here

Similar problem on hitbtc when trying to send (ios)

Looks like macOS app installs handler for bitcoin: but not bitcoincash:


Make gh-page/docs locale ready

I think making RDND docs localized would help not only spreading the word but making it more accessible for non-English speakers.
There's a PR #676 addressing l10n for Chinese and I'm sure there are other people willing to translate into their own language. Making it's in on our own repo will make maintenance/contributions easier.
There's a library for that https://github.com/l20n/l20n.js/ and if we accept going this way I can help implementing.
/cc @darthtrevino @DetweilerRyan @gaearon @john-ziegler @kesne @theTechie

It's definitely a good idea to add localization support for docs. Anyone of you interested in taking this forward? @darthtrevino @john-ziegler @kesne @DetweilerRyan
I glanced at https://github.com/l20n/l20n.js/, but seems complicated to use. Have you used this before? @cezaraugusto
I also looked into alternative solutions about doing this and found https://github.com/untra/polyglot. This would also require us to convert our gh-pages to use Jekyll.
This seems like a simple solution where we can maintain separate docs per language and use Jekyll to redirect to appropriate ones based on locale. (But, it might be tricky to maintain different versions and ensuring they are in sync when we update our docs; we will have to think about the workflow for updating across languages)

I'd prefer an approach like l20n over jekyll, it seems like it would probably be less intrusive to the existing structure.

@darthtrevino Is there any way to contribute localization now?

We still need a good approach for this. It's not something I've dealt with before. Any suggestions?


refactor kernel

Signed-off-by: Gregory Hill<EMAIL_ADDRESS>This PR makes the kernel structure more modular. When Tendermint isn't configured this enables non-consensus (closing #1026) with rapid transaction throughput.

@silasdavis I've cleaned up the configuration a bit more, though I think there is possibly a nicer way to arrange the kernel services in core/server.go. What do you think?


Add RenderCon Kenya 2024 to Conferences

This pull request adds RenderCon Kenya 2024 to the list of upcoming conferences

Hello @harish-sethuraman,
Your assistance with this will be highly appreciated


Is there a plan to support the Unreal DX12 RHI?

Hi, we'd like to consider using Rive, but we're limited to the DX12 RHI in Unreal due to some key aspects of Lumen/Nanite only being compatible with DX12.
Do you have plans to support the DX12 RHI?

Hi @delscorcho, there is planned support for DX12 that the team is actively working on. We'll integrate to the UE plugin once ready

Sounds good, thanks!
On Fri, Mar 15, 2024, 5:44 PM Voulz @.***> wrote:

Hi @delscorcho https://github.com/delscorcho, there is planned support
for DX12 that the team is actively working on. We'll integrate to the UE
plugin once ready
—
Reply to this email directly, view it on GitHub
https://github.com/rive-app/rive-unreal/issues/57#issuecomment-2000827338,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABVZUDU6S6GQEMG7M6JG5WTYYOIYRAVCNFSM6AAAAABEUV47KGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBQHAZDOMZTHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


antctl.exe supportbundle command doesn't support path flag on Windows

Describe the bug
In Windows, running antctl.exe supportbundle -d reports an error. The antctl tool is expected to support the -d (path) flag according to https://github.com/antrea-io/antrea/blob/main/docs/antctl.md#collecting-support-information, but it is not working on Windows.
To Reproduce

Run the following command in Windows:

.\antctl.exe supportbundle -d C:\var\log\antrea\

The following error is observed:

Error: unknown shorthand flag: 'd' in -d

Expected
The command should allow the user to specify a path to save the support bundle file on Windows using the -d flag.
Actual behavior
An error is thrown when trying to use the -d flag in Windows:
Error: unknown shorthand flag: 'd' in -d
Versions:
Antrea V2.1

Hi @luolanzone @rajnkamr, recently @wenyingd and I found two bugs with antctl on Windows(https://github.com/antrea-io/antrea/issues/6688 https://github.com/antrea-io/antrea/issues/6687). While they are not urgent, we believe they should be addressed eventually. Please feel free to assign them to anyone interested or needing familiarity with the antrea Windows/antctl modules. Thanks!

After investigation, I found supportbundle -d flag is only available outside pod in the controller mode. https://github.com/antrea-io/antrea/blob/18e9111d67ff391d0bd344799546f7c839b16f5e/pkg/antctl/raw/supportbundle/command.go#L109. When this command is run in the pod, the -d flag is not supported, and the file is saved to a fixed path.https://github.com/antrea-io/antrea/blob/18e9111d67ff391d0bd344799546f7c839b16f5e/pkg/antctl/raw/supportbundle/command.go#L160
On Windows, there is a slight difference. The reason why antctl supportbundle -d may still fail on a remote node is that if the server API token exists at the Windows path C:\var\run\antrea\apiserver, the current implementation sets InPod and agent mode to true. As the result, antctl supportbundle always saves the file to the fixed path in this mode. https://github.com/antrea-io/antrea/blob/18e9111d67ff391d0bd344799546f7c839b16f5e/pkg/antctl/runtime/runtime.go#L61-L67
Perhaps we can discuss potential changes to the documentation to prevent misunderstandings. cc @luolanzone @wenyingd

Close this issue as it‘s not a bug, we will track other feature changes of supportbundle in #6687 .


Use vernemq.conf.local if it exists

For #48
This is untested, I should have some time later tonight to try it out.  Then again, it's an if and cp, what can go wrong? ;)

Works for me!

@theasp thanks for the contribution!


[run_sk_stress_test] update stress-tester xfails for master -> main rename and new issues

@swift-ci please test

@swift-ci please test

@swift-ci please test

Looks like the source compat suite build is busted at the moment: https://ci.swift.org/view/Source Compatibility/job/swift-main-source-compat-suite/5503/console
@shahmishal could we force-merge this? The stress tester xfails aren't covered by CI testing anyway.


use provenance from configuration and put URIs into identifiers

This PR fixes #169, but it requires the user to configure their instance to include a locale file with geo_concerns.institution.uri in it. Maybe we need to put that in a generator?

@drh-stanford I think adding the locale file to the generator is a good idea.

I added the locale config into the generator. I'm not sure whether I need to delete it from the root though (I copied it to the generator templates)...

Makes sense to delete it from the root, otherwise you have to duplicate changes you make to it in the future.

Ok, I deleted it from the config root. Should be ready to go now...


Enable riscv64 ci jobs in pkgci.yml.

ci-exactly: build_packages, test_riscv64

I sent you an invite to iree-org so the checks can run automatically when you push.

I’m not sure what happened. We missed the iree-compile and iree-flatcc-cli and some others tools. However, we passed the checks using iree_import_binary, and we can actually see the tools when using ls -al...

I’m not sure what happened. We missed the iree-compile and iree-flatcc-cli and some others tools. However, we passed the checks using iree_import_binary, and we can actually see the tools when using ls -al...

I think it caused by version mismatch of some *.so.
We remove the docker flow, and it works well now.

I’m not sure what happened. We missed the iree-compile and iree-flatcc-cli and some others tools. However, we passed the checks using iree_import_binary, and we can actually see the tools when using ls -al...

I think it caused by version mismatch of some *.so. We remove the docker flow, and it works well now.

Nice! I did also just create https://github.com/iree-org/base-docker-images/, so new Dockerfiles could go there as needed. I'll be migrating / deleting https://github.com/iree-org/iree/tree/main/build_tools/docker soon.

This looks ready to merge now. Do you want to port any of the other configurations from here? https://github.com/iree-org/iree/blob/56ecef7fe060c4b108e0bb44568e519a0aeea079/.github/workflows/ci.yml#L252-L269
We can start to remove the commented out code there too.
That can happen either in this PR or future PRs.

Do you want to port any of the other configurations from here?
I prefer to send another PR to enable riscv32 ci jobs if we need it.

We can start to remove the commented out code there too.
Sure. riscv64 has been removed.


Add CustomWriter to allow user-specified formatting and filtering

I'm not sure if this is something you'd like as part of this project, but I wrote this up with @valarissa as a simpler way of defining user-specified formatting and filtering, and thought I'd send it in to see if it was useful to you.
I'm happy to incorporate any feedback if you think this is a worthwhile idea.
Thanks!

This is failing on 1.9.3, but I think it might just have been a glitch. I've restarted the build, but tend to forget to check back when I'm at conferences (which is the rest of the week).

@shawnacscott Sorry for the long delay on this.  I don't have the context about the change that @kytrinyx does, so I'm not really able to suggest a way forward.  But I will suggest that if you merge the latest master into your branch, that should take care of the build failure.

Oh my goodness. This completely dropped off my radar :( I am so sorry.

@shawnacscott @Valarissa Is this still something you're interested in pursuing?  I'm just trying to get up to speed on this, but it looks like there was an alternate approach you were going to explore.  Is that the case?

Hi! Sorry, I disappeared into a black hole of conference organizing, and am only now just emerging. Yes, I'm interested in exploring that alternative. I'll try and take a pass at it tonight and see if I can get it up to speed, and without conflicts.

This is failing on the tip of Ruby, which I think is probably fine. I'm going to make a PR that allows failures for tip so we can discuss it there.

Actually, I'm not convinced allowing failure is the right way to go. This is failing to compile the native extension for the json gem, and it's also failing on master. I'll jump in the travis IRC and see if someone knows what's going on.

Posted an issue on travis-ci/travis-ci: https://github.com/travis-ci/travis-ci/issues/6630

@kytrinyx The failure on the latest Ruby seems to be that the version of the json gem we're using hasn't yet been adapted to the merging of the Fixnum and Bignum classes into Integer that is happening in Ruby 2.4.
Doing some research, that support was added in json 2.0.0 (see https://github.com/flori/json/blob/master/CHANGES.md).  The problem is, that version also drops supports for Ruby versions < 2.0, and our .travis.yml file still builds for 1.9.2 and 1.9.3.
So it seems we have the following options:

Don't support Ruby 2.4 yet
Drop support for Ruby < 2.0
Find another solution for dealing with JSON.

In one sense, dropping support for unsupported Ruby versions (i.e., those < 2.0) makes sense.  But given that this is a tool that is ideal for getting legacy code into shape, we may not want to do that just yet.
For reference, Justin Searls' suture gem, also a tool designed for working with legacy code, supports Ruby back to 1.8.7.
For now, I think it makes sense to configure Travis to allow pre-release Ruby versions to fail.  But this is something we'll have to think about soon-ish.

Yeah, in the case of this gem it totally makes sense to support older rubies.
I'm going to submit a PR for allowing build failures on ruby-head.

I wonder if we can define use a different json gem version for different versions of ruby.

We've had luck on Calagator using the Appraisals gem for running different dependencies per version: https://github.com/thoughtbot/appraisal

I replied to @kytrinyx over on #78 to try to move the conversation there.  It seems more relevant to that PR than this one, and I didn't want to clutter this one up with marginally-related conversation.
@shawnacscott: does appraisals work in production, or is mostly for testing on CI?  In this case, I think we need support in production, because this dependency issue is going to affect people trying to use this gem on different Ruby versions.

Thank you so much, @shawnacscott!


Fitting url for webview，support read file from assets.

Fitting url for webview，support read file from assets.

#1206


DatePicker - Issue in Karma

The DatePicker is not rendering / behaving as expected in karma.
Please see the screenshot below.

I am also facing above issue

Hello,
There is a date format issue. Your date format set to IST. because in latest version date format is changed. So your format set in Wed Mar 06 21:00:00 IST 2014.
Thanks

@dharmeshpipariya Please help us

We have fixed the issue with release<EMAIL_ADDRESS>comment here if you have an issue


Bug in plotting comparison plots

There are gaps in the lines (https://oscovida.github.io/html/Germany-Niedersachsen-LK-Leer.html).

We also have similar gaps in the data for Pinneberg:
https://oscovida.github.io/html/Germany-Schleswig-Holstein-LK-Pinneberg.html

:shrug:  Seem to be no longer reproducible, at least on the oscovida site pages. We might have changed something accidentally.


fix Use of uninitialized value in bitwise

In very rare cases, the following error occurs
Unexpected warning: Use of uninitialized value in bitwise and (&) at Nanoid.pm line 47.

Perhaps $mask has a value, but $bytes->[$idx] may return undef.
Also, if you look closely, the JavaScript implementation adds an empty character in this case, and the behavior was slightly different.
In this PR, we have rewritten the logic to be as identical as possible to the original JavaScript implementation.
https://github.com/ai/nanoid/blob/9b748729f8ad5409503b508b65958636e55bd87a/index.js#L60-L62

Thank you @AnaTofuZ.  I wasn't aware that this was the case.


Add individual page for Duong

Missing newline.
I've added it (append + to the last line) and proceeded to merge the PR.


Update 04-data-model.mdx

Describe this PR
Edit the paragraph to match the expample it refers to:
model User {
  id        Int     @id @default(autoincrement())
  firstName String
  lastName  String
  email     String  @unique
  isAdmin   Boolean @default(false)
  @@unique([firstName, lastName])
}

Changes
I have changes the number of attributes from two to three, and added the missed @unique attribute and its reference.

What issue does this fix?
The documentation content

Any other relevant information

Thanks so much @emadunan !


Add section headers to each PPP

Closes #34

Overall, LGTM! However, why don't you keep the heading level for:

Contributions to the Developer Guide (Extracts)
Contributions to the User Guide (Extracts)

the same as the other ones in the Summary of Contributions part?


Update tr.txt

fixes some typos

@volkanto Volkan, thank you very much for the fixes! Could you please take a look at help-tr.txt also? There were some untranslated phrases


async_simple  do not have  execurtors folder

Xmake Version
2.8.8
Operating System Version and Architecture
debian12 x64
Describe Bug
async_simple  do not have  execurtors folder, so:
error: src/async_simple/ReadFiles.cpp:157:5: error: ‘executors’ has not been declared
  157 |     executors::SimpleExecutor executor(4);

Expected Behavior
add execurtors folder,
Project Configuration
xmake lib of demo_example
Additional Information and Error Logs
no

thanks! @star-hengxing ,it works after delete package and reinstall your new package.

issued.


Playground: fix all more menu icons

Pixel Point's more menu icons were exported incorrectly, with background, border, padding etc. All have now been fixed to only include the actual icon content, with the background/border/spacing now created by the more menu. This also allows pin and unpin icons to adopt text-success and text-destructive to better highlight their actions.
https://github.com/user-attachments/assets/68838aa4-881e-4434-aa37-a02f89589a41

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


When i capture image from camera, orientation of UIImage changed on server after uploading.

I have captured image from camera, it display properly in device but when i upload image to server then the image and thumbnail both images orientation are changed. I think this is an issue with image exif. there are several solutions available in swift and objective c both. I have implemented it like below but i am facing random memory issues, But i am not sure it's because of this changes. I have make some changes in my project to resolve protocol and closure based memory leaks, so now it's not crashing but i need to double check it.
In IQCaptureSession.m
-(UIImage *)fixOrientation:(UIImage *)image{
    // No-op if the orientation is already correct
    if (image.imageOrientation == UIImageOrientationUp) return image;

    // We need to calculate the proper transformation to make the image upright.
    // We do it in 2 steps: Rotate if Left/Right/Down, and then flip if Mirrored.
    CGAffineTransform transform = CGAffineTransformIdentity;

    switch (image.imageOrientation) {
        case UIImageOrientationDown:
        case UIImageOrientationDownMirrored:
            transform = CGAffineTransformTranslate(transform, image.size.width, image.size.height);
            transform = CGAffineTransformRotate(transform, M_PI);
            break;

        case UIImageOrientationLeft:
        case UIImageOrientationLeftMirrored:
            transform = CGAffineTransformTranslate(transform, image.size.width, 0);
            transform = CGAffineTransformRotate(transform, M_PI_2);
            break;

        case UIImageOrientationRight:
        case UIImageOrientationRightMirrored:
            transform = CGAffineTransformTranslate(transform, 0, image.size.height);
            transform = CGAffineTransformRotate(transform, -M_PI_2);
            break;
        case UIImageOrientationUp:
        case UIImageOrientationUpMirrored:
            break;
    }

    switch (image.imageOrientation) {
        case UIImageOrientationUpMirrored:
        case UIImageOrientationDownMirrored:
            transform = CGAffineTransformTranslate(transform, image.size.width, 0);
            transform = CGAffineTransformScale(transform, -1, 1);
            break;

        case UIImageOrientationLeftMirrored:
        case UIImageOrientationRightMirrored:
            transform = CGAffineTransformTranslate(transform, image.size.height, 0);
            transform = CGAffineTransformScale(transform, -1, 1);
            break;
        case UIImageOrientationUp:
        case UIImageOrientationDown:
        case UIImageOrientationLeft:
        case UIImageOrientationRight:
            break;
    }

    // Now we draw the underlying CGImage into a new context, applying the transform
    // calculated above.
    CGContextRef ctx = CGBitmapContextCreate(NULL, image.size.width, image.size.height,
                                             CGImageGetBitsPerComponent(image.CGImage), 0,
                                             CGImageGetColorSpace(image.CGImage),
                                             CGImageGetBitmapInfo(image.CGImage));
    CGContextConcatCTM(ctx, transform);
    switch (image.imageOrientation) {
        case UIImageOrientationLeft:
        case UIImageOrientationLeftMirrored:
        case UIImageOrientationRight:
        case UIImageOrientationRightMirrored:
            // Grr...
            CGContextDrawImage(ctx, CGRectMake(0,0,image.size.height,image.size.width), image.CGImage);
            break;

        default:
            CGContextDrawImage(ctx, CGRectMake(0,0,image.size.width,image.size.height), image.CGImage);
            break;
    }

    // And now we just create a new UIImage from the drawing context
    CGImageRef cgimg = CGBitmapContextCreateImage(ctx);
    UIImage *img = [UIImage imageWithCGImage:cgimg];
    CGContextRelease(ctx);
    CGImageRelease(cgimg);
    return img;
}

Method: - (void)takePicture
NSData *imageData = [AVCaptureStillImageOutput jpegStillImageNSDataRepresentation:imageDataSampleBuffer];

                NSURL *outputImageURL = [[self class] defaultImageStorageURL];

                UIImage *capturedImage = [[UIImage alloc] initWithData:imageData];

                imageDataSampleBuffer = NULL;
                imageData = NULL;

                UIImage *image = [self fixOrientation:capturedImage];
                [UIImageJPEGRepresentation(image, 1.0) writeToURL:outputImageURL.filePathURL atomically:YES];

I'll check and try to fix it.


I18N - Convert strings in views

As of 3/9/15 (does not include pending PRs):
$ find -name '*.html.erb' | wc -l
0
$ find -name '*.html.haml' | wc -l
713

100% done

@dclarizio this issue can be closed


[stable/lvm]: add custom priorityclass template for lvm deployments

Signed-off-by: prateekpandey14<EMAIL_ADDRESS>Pull Request template
What this PR does?:
PR add prioirityClass template and update the LVM StatefulSet and Daemonsets to use these custom priorityclass instead of using the k8s inbuilt one.
Does this PR require any upgrade changes?:
NO
Checklist:

[x] Fixes #openebs/charts/issues/236
[ ] PR Title follows the convention of  <type>(<scope>): <subject>
[ ] Has the change log section been updated?
[ ] Commit has unit tests
[ ] Commit has integration tests
[ ] (Optional) Are upgrade changes included in this PR? If not, mention the issue/PR to track:
[ ] (Optional) If documentation changes are required, which issue on https://github.com/openebs/openebs-docs is used to track them:

@prateekpandey14 let us update the operator yaml also in this PR.


Kubernertes -> Kubernetes

Fixes a few typos in the AKS docs.

@chlowell : Thanks for your contribution to the Azure documentation! The author, @neilpeterson, has been notified to review your proposed change.

@chlowell thanks.
#sign-off