TLS handshake error

What happened:
I am running IRSA setup on our k8s (kops) with  amazon-eks-pod-identity-webhook. So our custom kops cluster with IRSA seems to be working fine, I get the token and assume the role as expected but I keep getting this message in pod-identity-webhook log:
2020/11/25 12:17:16 http: TLS handshake error from <IP_ADDRESS>:51822: remote error: tls: bad certificate
2020/11/25 12:18:16 http: TLS handshake error from <IP_ADDRESS>:52536: remote error: tls: bad certificate
2020/11/25 12:19:16 http: TLS handshake error from <IP_ADDRESS>:53262: remote error: tls: bad certificate
2020/11/25 12:20:16 http: TLS handshake error from <IP_ADDRESS>:53966: remote error: tls: bad certificate
What you expected to happen:
I am not sure as seems that few other mention this finding in
https://github.com/aws/amazon-eks-pod-identity-webhook/issues/5#issuecomment-534100083
and
https://github.com/aws/amazon-eks-pod-identity-webhook/issues/33#issue-554198843
but I don't see any real answer.
So I guess I expect not to see this error as it seems that everything is working as expected.
Anything else we need to know?:
I am just not sure if this should work without csr and approval, but it obviously works as people are using it without it.
Environment:

K8s: v1.17.11
Webhook Version: latest, but it's the same on other tags/versions also

I figure it out, prometheus scraping caused this errors, by default it tries to scarp, but it needed CA/truested certs and those were self signed. That's why everything was working as expected.


Custom HTML5 Web Components and value attribute

I created this components library. The components support a value attribute like a standard <input>. Seems like LemonadeJS is giving some special treatment to this attribute and my custom components always render an empty string as the value instead of the actual value. For example:
<g-knob value="{{self.gainValue}}"></g-knob>
self.gainValue = 0.25
Always renders to:
<g-knob value=""></g-knob>
This patch fixes the issue by replicating the fallback code path in setAttribute() when the attribute key is 'value' and the element is neither a select, checkbox, radio, etc.

Unfortunately, this PR will crash several components and cannot be accepted. We need to find an alternative solution for that.

What about allowing to disable the automatic processing of attribute value on a component basis? so it gets treated just like any other attribute. My knowledge of LemonadeJS is very limited, not sure I can provide further ideas for a general solution.

@lucianoiam value is a very special attribute, for example is the basis of all @bind attribute, which should work for real HTML and lemonade HTML components. I don't know exactly what you trying to archieve, but one way to handler value in a custom way:
You can do something like that.
https://jsfiddle.net/p60xvkaz/10/

Thanks for the example.
I revisited my widgets code and they already react to changes to the value property. So in theory this line in LemonadeJS should work without the proposed patch: https://github.com/lemonadejs/lemonadejs/blob/496ad4a6c446aa7637dfdf30877d0818dad15c6e/dist/lemonade.js#L143
Is it correct to conclude custom HTML5 must not define their own value property because that is incompatible with LemonadeJS?
Trying to understand whether I hit an edge case or there is something inherently wrong with my widgets

This is how I wrapped one of the custom elements:

export class GKnob extends lemonade.component {

    render() {
        return `<g-knob
                    min="{{self.min}}"
                    max="{{self.max}}"
                    value="{{self.value}}"
                    oninput="self.value=this.value">
                </g-knob>`;
    }

    constructor() {
        super();

        this.min = 0;
        this.max = 1;
        this.value = 0;
    }

}

Your component should react to that the same way input.value = 123
yourcomponent.value = 123 - should present the value 123 wherever needs to be.
LemonadeJS only set the value of your component, internally your component should handle that.

This part can be replace for @bind
                value="{{self.value}}"
                oninput="self.value=this.value">

render() {
    return `<g-knob
                min="{{self.min}}"
                max="{{self.max}}"
                @bind="self.value">
            </g-knob>`;
}

Components already react to changes in the value property, please see last line in https://jsfiddle.net/Lsyef6tp/1/
How does @bind now it should attach a listener to a custom input change event? my library emits these:
        const ev = new Event('input');
        ev.value = val;
        this.dispatchEvent(ev);

Note I deliberately diverged from the stock HTML elements for some design choices.

@bind will syncronize the value of your component with the self property inside LemonadeJS component. It pretty much does what you have done using oninput. @bind will do two-way binding.... if your self.value changes it apply that to your component, and if you component changes it will change self.value.

I have created many custom elements which implements element.val = function() {}
That is not the only way to do it and probably what you are doing would be fine. But val() helps you a lot if you want custom two way binding with LemonadeJS using the value property.

@Bind will syncronize the value of your component with the self property inside LemonadeJS component. It pretty much does what you have done using oninput. @Bind will do two-way binding.... if your self.value changes it apply that to your component, and if you component changes it will change self.value.

Makes sense, the custom component self-updates its value property on user input. I confirm @bind is equivalent to specifying the value and oninput properties in the example above.
However why the unpatched LemonadeJS is not working remains a mystery, as shown in the JSFiddle the knob correctly updates when setting its value property.
I will prepare a bare-bones custom HTML5 component example that reacts to value, to rule out any issues on my side.

Thanks for sharing your example, I will resolve your mistery... and yes it is a mistery indeed.

One problem in your componet.
const knob = document.createElement('g-knob');
knob.value = 0.33
document.body.appendChild(knob);

If you do that knob won't have any value.

Good catch! fixed in https://github.com/lucianoiam/guinda/commit/f79e395f55da70719646d240ff0f5903b1bab0ce, thanks a lot.
The component value was being overwritten with a default when attaching the component to DOM.
There is something else going on though, the value setter is never called by LemonadeJS. Is it possible that the library expects value to be a property and not a get/set pair? the relevant component code looks like this:

    get value() {
        return this._value;
    }

    set value(newValue) {
        console.log('Never called');

        this._value = newValue;
        this._valueUpdated();
        this._dispatchSetValueEvent(this.value);
    }

Trying to understand why set value() never gets called and at the same time no errors are printed to the console.
I inserted some debug messages here https://github.com/lemonadejs/lemonadejs/blob/496ad4a6c446aa7637dfdf30877d0818dad15c6e/dist/lemonade.js#L143
                const dummy = document.createElement('g-knob');
                console.log(dummy);
                console.log(typeof dummy);
                console.log(Object.keys(dummy));

                console.log(e);
                console.log(typeof e);
                console.log(Object.keys(e));

                e.value = v;

I fail to understand the output, I expected e to be an instance of the same type to the one returned by document.createElement(). First group of console.log() calls print:

And the second group:

I have spent a good chunk of my day to isolate the problem outside the LemonadeJS scope. So, it seems there is a problem on your component.
This will work.
    let div = document.createElement('template');
    div.innerHTML = `<g-knob
                    min="0"
                    max="1" value="0.2">
                </g-knob>`;
    let test = div.content.childNodes[0];
    root1.appendChild(test);
    test.value = 0.5

This won't work.
    let div = document.createElement('template');
    div.innerHTML = `<g-knob
                    min="0"
                    max="1" value="0.2">
                </g-knob>`;
    let test = div.content.childNodes[0];
    test.value = 0.1
    root1.appendChild(test);
    test.value = 0.5

Notice that the difference is only if I try to define a value before appending the ELEMENT to the DOM. If I define the value before the component goes to the DOM somehow setter and getter are destroyed.
Here is an example without LemonadeJS.
https://jsfiddle.net/wnbzkp9g/37/

As mentioned above, that bug was fixed (thanks again for pointing it out). Still, that bug should not have prevented things from working after the element is attached, only break the initial value.
The el.value call is failing and that is the culprit. Cannot explain why though, could you provide some testing tips?

somehow setter and getter are destroyed.
I do not understand this part, is it something my component does wrong?

This example does not use LEMONADEJS. If you make this example work, them lemonadeJS will work.
https://jsfiddle.net/wnbzkp9g/37/

hmm while I do not discard an issue on this side, it does not seem trivial. Only the template way of doing it as shown in the JSFiddle is failing, so until now we were looking at different results (I was testing with no. 3 below)
const html = `<g-knob
                min="0"
                max="1" value="0.2">
            </g-knob>`;

Fails ( same as previous JSFiddle )
    let template = document.createElement('template');
    template.innerHTML = html;
    let el_1 = template.content.childNodes[0];
    el_1.value = 0.1
    document.body.appendChild(el_1);
    el_1.value = 0.5

Works ( alternate way for template )
    let el_2 = document.createRange().createContextualFragment(html).firstChild;
    el_2.value = 0.1
    document.body.appendChild(el_2);
    el_2.value = 0.5

Works ( no template )
    let el_3 = document.createElement('g-knob');
    el_3.value = 0.1
    document.body.appendChild(el_3);
    el_3.value = 0.5

I can imagine, and those things are complicate. The problem LemonadeJS uses template, and the template is important since it will work with elements such as , . I am not sure why template is not working, this will require a long analysis of your script but unfortunately I won't be able to help from here.

No need for analyzing my script, nor I think it is an issue in LemonadeJS at this point. This barebones example displays the same behavior https://jsfiddle.net/h38md92L/ (note: it prints to the JSFiddle console).

Your code fails on templates which is the bases of LemonadeJS. If your code does not support template won't support LemonadeJS.
   let template = document.createElement('template');
    template.innerHTML = html;
    let el_1 = template.content.childNodes[0];
    el_1.value = 0.1
    document.body.appendChild(el_1);
    el_1.value = 0.5

Have you checked the JSFiddle?

It basically defines an empty HelloComponent custom component with a get/set property. Instantiating it using a template will cause the value setter to never be called. Just for fun tried to set the property name to something else and also does not work.
There is a potential risk of unrelated custom HTML5 components failing to work with LemonadeJS because of this behavior, for which I can only provide evidence but there is no explanation yet. I think it is safe to rule out issues in my library at this point too, unless there is also something substantially wrong in the hello example (also a possibility).
I am happy to perform further testing if needed

I have spent a lot of time on this issue. I tried so many different possibilities and there is no much alternatives for the value, and it seems there is a bug with the template which is not related to the use of LemonadeJS, but unfortunatelly won't be a easy task to change that from a template o another possibility and don't break thousands of applications around..... If you wish to use lemonadejs one alternative is:
class HelloElement extends HTMLElement {

    constructor(opt) {
        super();
    }

    connectedCallback() {
        var o = this;
        Object.defineProperty(this, 'value', {
            get: function () {
                return o._value;
            },
            set: function(v) {
                o._value = v;
            }
        });
    }
}

OK, it is enough to know that LemonadeJS is currently not suitable for use with arbitrary HTML5 Web Components, nor there is an issue in my own library.
I don't agree on imposing constraints onto 3rd party components as the solution though. Maybe PR #33 can serve as the starting point of a general solution, at least we now know why things are breaking.
Meanwhile I will continue working with a custom fork. Thanks for your time on this.

I found the solution. The problem is:
"From the MDN docs: It is not possible to simultaneously have a setter on a property that holds an actual value. That is why delete in the given answer is required"
This is an working example.
https://jsfiddle.net/gjxwnvdm/19/
You will need to use delete in case a property is existing, thats why if value applied before getter and setter is not working.
Here is more information:
https://stackoverflow.com/questions/67313182/webcomponents-property-setter-not-trigger-if-property-defined-before
So, if you wish to use LemonadeJS without customizations, you need to use delete this.value on the constructor.

In the case of the element created from a template, the first setter call never fires (ie, before attaching to the DOM). There is a missing 0 : set value = 0.2 line in the JSFiddle  output:
"Created 0"
"0 : set value = 0.5"
"Created 1"
"1 : set value = 0.2"
"1 : set value = 0.6"

It is not fired, but you can save the value on the constructor before you delete it as shown on the jsffidle.

This total makes sense. From now, you can decide the best course of action for you.

Good luck on your project.

Judging by the output of the JSFiddle with the big arrow, the initial value of the component will not be correctly set by LemonadeJS because the component is still not attached to the DOM when the first el.value = ... call takes place.
Just tried adding delete this.value to my widget, made sure LemonadeJS is unmodified 2.8.0 and as expected, the initial component value was not correctly set.
To make it clear, delete this.value is still NOT a solution.

The biggest problem is resolved by delete. I am not sure if face other problems.
So, integrate the webcomponent with LemonadeJS and value without any problem.
https://jsfiddle.net/10bdw3m6/29/

Removing the delete this.value from this new JSFiddle still allows the reactive view to work properly

Luciano,
If I remove this.value the value changes but the input range keeps still...

Fair enough, just realized there is a button so the test was incomplete. Now trying to replicate the fix in my own widget...

Cool, I hope this fixes your problem.

It did indeed, thanks a lot. I likely did something wrong earlier today, those widgets are implemented with a somehow complex class hierarchy. It is great to have isolated test code and evidence now. I honestly did not know about deleting properties before setting custom accessors, I got this in one of the notification emails from you:
delete a property to use getter and setter is mandatory in all research I have done.
Is that the case? probably explains why I try to avoid JavaScript unless working on web stuff, lol. As mentioned earlier this wasn't trivial.
Also unrelated but I was a bit suspicious about the discussion at first, starting projects that rely on smaller unknown dependencies is risky (same goes for anyone considering my own stuff). I guess one of the first steps is finding out how maintainers deal with feedback, then you know whether it is worth. Keep up with the great work.

Thanks great news! Quite happy you find the solution... yes, your case was a bit complicated so isolating the problem was crucial to find the solution. In the end everything makes sense and it was a good DOM exercise ;)
Thanks a lot. We have some other components... that might be usesul one day...
https://jspreadsheet.com/v9

Still trying to understand why delete.value is needed so other authors are not misguided. I am not particularly proficient in JavaScript so take this with a grain of salt...
So far it does not look as a bug in my library, but a requirement of LemonadeJS. As you mentioned earlier self.value is a very special property, and I think the fact that makes it special is that the library appends the value property to every created element. So, when a Web Component (WC) implementation also happens to implement a get/set pair for value, boom. As pointed out by MDN in these cases the property needs to be deleted...
This looks really more like your library making an assumption, unless it is standard practice every time an accessor is defined, its matching property is deleted for safety (I lack the experience here). The assumption can be turned into a requirement with a bit of proper documentation, which is great to know is on the way.
I give you credit for spotting the bug in guinda that overwrited the existing value with default values if the property was written before attaching the element to the DOM. Again an unfortunate coincidence that masked the root issue (colliding property and accessor). Adding insult to injury, I made some mistakes while testing your JSFiddles.
In conclusion one bug on my side was fixed, and the second update was merely for compatibility with LemonadeJS. I am not sure this is possible at all but ideally user elements should remain untouched and any unsurmountable exception clearly documented.

That is not actually related to LemonadeJS in particular, and you would probably bump on that one day or another since you are using getters and setters. But, this is not only related to the property value, could be related to any conflict between a property and getters/setters with the same name. One way to understand that is....
let obj = {
value: 123,
}
If you wish to change obj.value = 567 is fine, you are changing the property directly.
But, if you are using getters and setters, you cannot have a property value
let obj {
get value()
set value()
value: 123// this will cause issues
}
Thats why you have obj._value = 123
I share with you some documentation from Mozilla yestarday. I belive you can add something to the __construct of your classes so your users don't need to do that. You pretty much need to do the delete for all properties that has getters and setters with the same name.
Hope that is clear...

The documentation from Mozilla is helpful but has nothing to do with what I am stating here, as the widgets library does not define properties and accessors with the same name simultaneously. That explains why it has worked for some time in other environments.
I am thinking about a responsibility issue. Are developers expected to always delete properties when implementing accessors? that is what you seem to imply, but not what the MDN explicitly states. In other words, is it common practice to delete properties just for safety?
I fail to understand who is responsible of taking care of this situation:

Code which implements accessors (because the delete thing is documented, or common practice).
Code which sets properties to an instance potentially implementing accessors with the same name (in that case that must be documented).

I do not want to turn this into a philosophical debate as I lack the knowledge and experience, just pointing out I'm skeptical I have a bug on this front. And deleting every single accessor just in case, sounds horrible but could be the case, IMO JavaScript is not particularly beautiful after all 😅

You only need to delete if you have a getter or setter with the same name.

You only need to delete if you have a getter or setter with the same name.

Taking this literally, then my library was just fine. The issue arises only when LemonadeJS gets involved, it creates a new compatibility requirement that must be documented. We cannot just expect 3rd party existing Web Components libraries to already call delete this.value.
It is totally fine if LemonadeJS has some minor requirements to keep things simple, just have them clearly documented. It is a responsibility issue (in the software sense).

What is happening with LemonadeLS.

The object is create
LemonadeJS set the property based on the attributes defined in the tag
Them you getter and setters are created
Append the component to the DOM

Because LemonadeJS define property before the getter and setters are created, them you have a conflict.

I would say this one is key:

LemonadeJS set the property based on the attributes defined in the tag

Regarding <template>, again I am not very proficient but know there is DOMParser and createContextualFragment(). As shown earlier, the latter comes with its own quirks...

Yes, when you define a attribute in the tab , the value will be defined to the Test object. But, test object is receiving getters and setters delayd due the template engine.
We have tried a lot of different options for the template in the best, template is the most flexible. We will re-check other possibilities for version 3.


use vite alias lead to import Symbol value not equal

Describe the bug
use Vue3 + TS + Vite
1、set vite config alias
// vite.config.ts
  resolve: {
    alias: {
      "@global": "./src/global",
      "@util": "./src/util"
    },
  },

2、export symbol value
// src/global/event.ts
import { InjectionKey } from "vue";

export function addDrgeEvent(dom: Element, fn: (e: DragEvent) => void) {
  // ...
}

export const drgeKey: InjectionKey<typeof addDrgeEvent> = Symbol("addDrgeEvent")

3、write my plugin code（Vue instance uses）
// src/global/plugin.ts
import { drgeKey } from "./event"
// import { drgeKey } from "@global/event"

export const utilPlugin = {
  install(app: App) {
    app.provide(drgeKey, addDrgeEvent)
  },
};

4、use alias import, but inject to fail, is undefined
<script lang="ts" setup>
import { drgeKey } from "@global/event"
console.log(inject(drgeKey));    // undefined
</script>

When I import whitch don't use alias, or two file use alias import, it works
Reproduction
not
System Info
not

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

https://vitejs.dev/config/shared-options.html#resolve-alias

When aliasing to file system paths, always use absolute paths. Relative alias values will be used as-is and will not be resolved into file system paths.

For example like this:
import { defineConfig, normalizePath } from "vite";
import { fileURLToPath } from "node:url";

function fromRoot(relativePath: string) {
  return normalizePath(fileURLToPath(new URL(relativePath, import.meta.url)));
}

export default defineConfig({
  resolve: {
    alias: {
      "@global": fromRoot("./src/global"),
      "@util": fromRoot("./src/util"),
    },
  },
});

use relative path will use like this function, why not integrate with build-in code, I think a part of person will use relative path, and probably like me have same question

We are using @rollup/plugin-alias and that would be a big breaking change for the ecosystem, so it is better to stick to the way it currently works. Using a relative path is also valid if not as useful, so I don't think we could add a warning to flag all relative path usage.


Update standard token tests

Refs. PR #224

Seems like you forgot to rebase

My bad. You are right. Will redo it and open a new PR.


Graceful shutdown

When stopping the worker, I'd like to be able to tell the jobs that they should stop. And re-queue them on other workers.
In my use-case I've implemented the method to signal that the job needs to stop, however, there's no way to stop the job without either marking it as completed or as failed.
If I re-queue the job manually, I lose the MaxFails options, if I fail the job by returning an error, work still cannot honor the MaxFails value.
How would one go about doing this? I suggest if a job returns a work.ErrSkip error , MaxFails should not be increased.

How did you implement the method to handle job specific handling. Was it using middleware or something else?


Rest command is not working

This was fixed in #448.

Okay. Can I run force update to get the newest version or download and replace the old file?

No, unfortunately.  Update is not implemented.  You will need to download it from here.
https://developer.salesforce.com/tools/forcecli

Still same result. I downloaded and replaced the force.

The fix will be in the next release.  If you build from source, it's on the master branch.

I'll cut a new release now, was waiting for some CI stuff to finish.
On Wed, Oct 4, 2017 at 11:46 AM, Christian G. Warden <
<EMAIL_ADDRESS>wrote:

The fix will be in the next release. If you build from source, it's on the
master branch.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heroku/force/issues/450#issuecomment-334253045, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHGHp07Ip5DUnEQ42ltoetxssL2eIqJks5so9KWgaJpZM4PuBk5
.

Give it about 20 minutes and download again.  You will now the download is ready when you see the release pages has 8 downloadable resources.


spec/regression_spec.rb fails with ruby2.2

Hi,
SInce ruby2.2, nil is frozen.
https://bugs.ruby-lang.org/issues/8923
So the two tests in regression_spec.rb are failing with ruby2.2.
Cheers,
Cédric

@Empact this can be closed, #57 resolved it

Thanks!


[explore] fix query text modal while loading

Currently it's not possible to view queries while they are running, the
spinner appears endlessly. I decided to rearrange things a bit while
debugging so I could see clearly through it.

LGTM


Authenticated users as anon

Hello everyone !
I'm currently trying to use the WebSocketBundle in my project but I'm having some issues !
I've already done this in another project and everything worked just fine ! But I wanted to use the SonataAdminBundle so I created a new project and tried the same thing !! But when an authenticated user subscribe to a channel I get the following in the console :
[2016-04-09 14:39:04] websocket.DEBUG: INSERT CLIENT 1530 {"user":"s:36:\"anon-8812448825708f7e877ef8041502078\";"} [2016-04-09 14:39:04] websocket.INFO: anon-8812448825708f7e877ef8041502078 connected {"connection_id":1530,"session_id":"8812448825708f7e877ef8041502078","storage_id":1530}
instead of username connected......
Everything is working fine and the session are stored in the database, the web server and the websocket server are working in the same ip : (localhost) I tried deleting all the cookies from my web browser and trying again but nothing worked !!
this is my websocket config :
gos_web_socket:
    server:
        port: 8080        #The port the socket server will listen on
        host: localhost   #The host ip to bind to
        router:
            resources:
                - @AppBundle/Resources/config/pubsub/routing.yml
    client:
        firewall: admin
        session_handler: @session.handler.pdo
    pushers:
        zmq:
            default: true
            host: <IP_ADDRESS>
            port: 5555
            persistent: true
            protocol: tcp

Are you sure to be authenticated through admin firewall?

Yes !! I have two firewalls !! And I'm sure the user is authenticated thru this one !
I even tried the other firewall but no luck
    firewalls:
        # Disabling the security for the web debug toolbar, the profiler and Assetic.
        dev:
            pattern:  ^/(_(profiler|wdt)|css|images|js)/
            security: false

        # -> custom firewall for the admin area of the URL
        admin:
            pattern:            /admin(.*)
            context:            user
            form_login:
                provider:       fos_userbundle
                login_path:     /admin/login
                use_forward:    false
                check_path:     /admin/login_check
                failure_path:   null
            logout:
                path:           /admin/logout
                target:         /admin/login
            anonymous:          true

        # -> end custom configuration

        # default login area for standard users

        # This firewall is used to handle the public login area
        # This part is handled by the FOS User Bundle
        main:
            pattern:             .*
            context:             user
            form_login:
                provider:       fos_userbundle
                login_path:     /login
                use_forward:    false
                check_path:     /login_check
                failure_path:   null
            logout:             true
            anonymous:          true

having the same issue here. any solution available? thanks

Did you change the session name or use the default name (PHPSESSID) ?

No !! I'm just using the default one !

I also tried the following code just to make sure that the user is under the admin firewall !
$securityContext = $this->get('security.context');
$token = $securityContext->getToken();
$providerKey = $token->getProviderKey(); // admin

dump($providerKey);

I get the following result !

Hello,
I'm having the same issue. Symfony profiler shows user is authenticated, but console keeps showing anonymous users (websocket.INFO: anon-16709564465714e5063f16f267455790 connected).

I'm using memcached session handler which implements \SessionHandlerInterface :
framework:
    session:
        handler_id:  session.handler.memcached

gos_web_socket:
    client:
        firewall: main
        session_handler: session.handler.memcached

Okay, By dumping some variables I found out that the $authenticationProvider inside the ClientManipulator looks like this :

#authenticationProvider: Gos\Bundle\WebSocketBundle\Client\Auth\WebsocketAuthenticationProvider {#89
#tokenStorage: Symfony\Component\Security\Core\Authentication\Token\Storage\TokenStorage {#88
-token: Symfony\Component\Security\Core\Authentication\Token\AnonymousToken {#979 ÔÇª5}
}
#firewalls: array:2 [
0 => "admin"
1 => "main"
]
#logger: Symfony\Bridge\Monolog\Logger {#92}
#clientStorage: Gos\Bundle\WebSocketBundle\Client\ClientStorage {#93}
}

Not sure if that means Something !!

@ProPheT777 @matthieuy Any suggestions guys ! I'm stuck with this for a week now !! And I tried everything !!

Can you reproduce the bug on a fork of https://github.com/GeniusesOfSymfony/WebsocketAppDemo ? This is too much complex to debug you without a playground.
I'm so sorry that we can't help you much.

Of course it just work perfectly on a fork of WebsocketAppDemo !
I restarted my project on the WebsocketAppDemo base and now it works, but i can't find what is the difference...

Can I close it

I still can't fin a solution yet ! But anyway I'll start all over and try again ! And yes you can close it if you want to !
Thanks for the help

i'm having the same issue ! any solution ?

We are having the same problem aswell.

Hi, I have the same problem and I found how to fix it and it is simple:

The firewall name must be the firewall context name if exist. Else the firewall name.

I follow the setup guide and here
gos_web_socket:
    client:
        firewall: secured_area

secured_area must be the firewall context name if exist. Else the firewall name.
If you have a security configuration like this https://github.com/GeniusesOfSymfony/WebSocketBundle/issues/136#issuecomment-207827663
You must set the context instead of the firewall name:
gos_web_socket:
    client:
        firewall: user

Here is the problem: https://github.com/GeniusesOfSymfony/WebSocketBundle/blob/44e7cac0009c4f4cd7c56e758d24f8b7bb5d453e/Client/Auth/WebsocketAuthenticationProvider.php#L71
Also if you use SNC Redis I think that you should set snc-redis.session.locking false

I have the same problem. everything looks right, but still anon instead of username. The problem does not exist on local dev machine, but exists on prod server. The only distinction prod runs with SSL and stunnel. we have handshakes, console logs are empty, but in prod.log we see anon instead of user and chats aren't updated (push does not work)

Hi @v03adk, are you using the same domain name (or host name) to connect to web and sockets in prod? The PHPSESSID must be the same to "link" the session.

well, we use the same domain, but I am not sure about "www" part, let me show and explain
parameters.yml
websocket_host: example.com  websocket_port: 8443  websocket_origin: example.local  websocket_origin_www: www.example.local
config.yml
gos_web_socket:     client:         firewall: main         session_handler<EMAIL_ADDRESS>   pushers:         wamp:             host: "%websocket_host%"             port: "%websocket_port%"     server:         port: "%websocket_port%"        #The port the socket server will listen on         host: "%websocket_host%"  #The host ip to bind to         origin_check: true         router:             resources:                 -<EMAIL_ADDRESS>   origins:         - "%websocket_origin%"         - "%websocket_origin_www%"
this perfectly works locally. On prod server we have SSL, so we redirect all http connections to https://www.example.com

Ok, I think that the problem is related to the fact that www.example.com and example.com may not share the same cookie. If you can try to use the "same" hostname (with www part or without www  in both), I think that these simple update will solve the issue.

I will try that now. but what about WC.connect? it uses gos_websocket_host which will be with www, won't it be a problem?
I got error Could not bind to tcp://www.example.com:8080: Address already in use
We use stunnel as said in the docs, maybe stunnel uses both www and non-www versions.
And one more thing I forgot to mention. It worked before on prod, but then stopped. We deployed it almost 1.5 years ago and it worked. ten stopped. I think maybe it was after some update and we need to update configuration or something

I will try that now. but what about WC.connect? it uses gos_websocket_host which will be with www, won't it be a problem?

I think that it could not be a problem.

I got error Could not bind to tcp://www.example.com:8080: Address already in use
We use stunnel as said in the docs, maybe stunnel uses both www and non-www versions.

Other process are using the address, maybe you have the WS server running or a virtual host listening this address? You can use this command netstat -plnt | grep 8080 to check if there are other process using this address.


BigQuery AppendRows API could accept a write_stream

We cannot currently send routing metadata for streaming writes. Mainly because we must configure the grpc::ClientContext before we know what the first request will be.
In BigQuery, the semantics are to add extra routing information in the initial request, via the write_stream field. (Note that write_stream is also listed as a method signature)
Maybe we should add std::string const& write_stream as a parameter to the client call. Then we could set internal::GrpcSetupOption to [write_stream] (auto& context) { context.AddMetadata("x-goog-request-params", write_stream); } in order to achieve routing. I do not know whether we should try to modify the initial request to set this field.

We do not have time for this.


[bug] styled component behaves differently in deployed production app

There's a lot going on and I tried to reproduce in a forked repo, but the bug only manifests in my deployed app when changing routes twice. But given how I resolved it, I believe the bug originates from tamagui (or my understanding of how styled components work is incorrect).
Another relevant fact is that the bug only exists in the production build and only affects the web version. It affects all browsers that I tested (Safari, Chrome, Firefox).
Happy to give more details, but in its simplest form, I had a component that looks like:
const TOP_NAV_HEIGHT = 100;

const TopNav = styled(XStack, {
  position: 'absolute',
  top: 0,
  left: 0,
  right: 0,
  bc: 'black',
  height: TOP_NAV_HEIGHT,
  alignItems: 'flex-end',
  justifyContent: 'flex-end',
  display: 'flex',
  paddingBottom: 10,
  px: 20,
  animation: 'lazy',
  zIndex: 300_000,
});

Which I render it in the following context:
return (
    <YStack>
        <TopNav
            key={`top-nav`}
            opacity={isScrollingDown ? 1 : 0}
            y={isScrollingDown ? 0 : -TOP_NAV_HEIGHT}
        >

SomeText

        </TopNav>
        <ScrollView
            space={'$4'}
            scrollEventThrottle={100}
            paddingTop={TOP_NAV_HEIGHT}
            onScroll={(e) => {
                 //Determine if scrolling down to trigger display/hiding of top nav
            }}
        >
          //Arbitrary Content
        </ScrollView>
       <XGroup>
           //Links to various pages with the same layout that differ only in the content displayed inside the ScrollView
       </XGroup>
    </YStack>
);

The problem is that when I navigate to on one of the links inside the XGroup twice, the TopNav element loses most, but not all, of its properties (most importantly the absolute positioning). This causes a layout shift now that it occupies space on the page.
The reason I figure this is related to tamagui is because the fix is to replace TopNav with an XStack and inlining all of the properties that were passed into the styled version:
return (
    <YStack>
        <XStack
            key={`${pageTitle}-top-nav`}
            opacity={isScrollingDown ? 1 : 0}
            y={isScrollingDown ? 0 : -TOP_NAV_HEIGHT}
            position={'absolute'}
            top={0}
            left={0}
            right={0}
            bc={'black'}
            height={TOP_NAV_HEIGHT}
            alignItems={'flex-end'}
            justifyContent={'flex-end'}
            display={'flex'}
            paddingBottom={10}
            px={20}
            animation={'lazy'}
            zIndex={300_000}
        >

SomeText

        </XStack>
        <ScrollView
            space={'$4'}
            scrollEventThrottle={100}
            paddingTop={TOP_NAV_HEIGHT}
            onScroll={(e) => {
                 //Determine if scrolling down to trigger display/hiding of top nav
            }}
        >
          //Arbitrary Content
        </ScrollView>
       <XGroup>
           //Links to various pages with the same layout that differ only in the content displayed inside the ScrollView
       </XGroup>
    </YStack>
);

The above works fine in all environments and compilation targets, though from what I think I understand, it should be exactly the same as the styled TopNav component (just built in a less reusable way).

Can you add //! debug-verbose to the top of the files (both usage and definition) and paste the output? A repro would really help me look at this faster as well.

@natew Strangely enough, I can't reproduce anymore (even after checking out the exact commits in which I observed this behavior). I wonder if I had old dependencies that I just needed to yarn install? Anyway, apologies for the false report.

I had a very similar issue - styles not working randomly. Deleted .next, node_modules, package-lock.json after updating everything and it seems to be fixed?
For like 2-3 days my client-side styles did not work at all. Now they work fine again. This is the closest bug to what I experienced so my guess is there's some relationship, but it seems like a very rare thing to trigger


improve section divider rendering

Closes: #2076
Closes: #1860
Description

@andrewballantyne this solution uses custom CSS which is something we try to avoid in this project but it does make the solution simple to handle the various use cases.
There are many use cases to consider that make for a complex scenario:

section is hidden because component is not installed
section is hidden because section is controlled by a feature flag that is disabled
section contains no contents and is considered 'empty' => requires divider
section manages its own internal state and may request a divider
section contains data => no divider
the last section in the list => no divider
section contains an error => no divider, displays alert box

This solution uses CSS as it requires only 2 touch points:

Adds a class name to the stack component items (odh-project-details-components__item) which is used with sibling selectors to know when an item is not the last in the list
Conditionally adds the odh-details-section--separate class whenever a details section wants to signal that a separator is needed. This class is automatically added if the section is empty, or overridden by the parent component.

PipelinesSection overrides this with the showSeparator property because it manages it's own empty state internally.

No model mesh after:

Error state before:

Error state after:

How Has This Been Tested?

Create an empty project.
Create a project with some data. Eg a Notebook
Update DataScienceCluster to disable components.

Observe effect on project details view

Update odh-dashboard-config to disable some features. eg disableModelServing: true

Observe effect on project details view

Test Impact

Updated existing integration test.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@andrewballantyne fixed #1860 by removing EnsureAPIAvailability and performing the same API check one component level higher in PipelinesSection to display the loading state.

Looks good at a code level, didn't get to test it.
/approve
If anyone can test it, verify things, feel free to merge this without my final approval.

@christianvogt needs a rebase, i can add back my label when you do


Add support for objecttype PageCustomization

#2076

Strange characteres in the file?
Also, there are a few other things that needs fixing for 19 - will fix myself.
Thanks for this though.


Proposed 0.60.0-rc1

Codecov Report

Merging #2039 into develop will decrease coverage by -0.29%.
The diff coverage is 72.27%.

@@             Coverage Diff             @@
##           develop    #2039      +/-   ##
===========================================
- Coverage    67.93%   67.64%   -0.29%
===========================================
  Files          685      680       -5
  Lines        49591    49199     -392
===========================================
- Hits         33689    33281     -408
- Misses       15902    15918      +16

Impacted Files
Coverage Δ

src/ripple/ledger/impl/ApplyStateTable.cpp
86.18% <ø> (ø)
:white_check_mark:

src/ripple/protocol/Indexes.h
100% <ø> (ø)
:white_check_mark:

src/ripple/protocol/TxFormats.h
100% <ø> (ø)
:white_check_mark:

src/ripple/protocol/impl/BuildInfo.cpp
82.6% <ø> (ø)
:white_check_mark:

src/ripple/app/main/Amendments.cpp
100% <ø> (ø)
:white_check_mark:

src/ripple/protocol/LedgerFormats.h
100% <ø> (ø)
:white_check_mark:

src/ripple/protocol/impl/LedgerFormats.cpp
100% <100%> (ø)
:white_check_mark:

src/ripple/protocol/impl/TxFormats.cpp
100% <100%> (ø)
:white_check_mark:

src/ripple/conditions/Condition.h
100% <100%> (+3.44%)
:white_check_mark:

src/ripple/protocol/impl/Indexes.cpp
92.63% <100%> (ø)
:white_check_mark:

... and 19 more

Continue to review full report at Codecov.

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


[FEATURE] - query each stake snapshot independently [Draft]

What
A command to query each stake snaphost independently; for example
cardano-cli query stake-snapshot --mark-snapshot ...
cardano-cli query stake-snapshot --go-snapshot ...
the output should contain all 3 maps
[
"delegations",
"poolParams",
"stake"
]
Why
Currently, many tools rely on dumping the entire ledger-state to then extract the required snapshot values which is expensive and inefficient and there is no alternative good solution yet.
Personas

[ ] SPOs
[ ] dApp Devs
[ ] Exchanges
[x] Wallets
[x] 3rd party tools
[ ] ADA holders

Definition of Done (DoD)

[ ] Acceptance Criteria + User Stories & DoD created and singed-off (by PO, dev & test owners)
[ ] Builds successfully on CI
[ ] Code & Test review (as per Acceptance Criteria)
[ ] There is documentation and/or examples for the new functionality (usage/response)
[ ] Log/record changes on Vnext (or similar depending on what we adopt)
[ ] Ticket number(s) included in PR description
[ ] All Acceptance Criteria met and covered by dev/unit/property/integration tests
[ ] System/E2E automated tests + System Test Engineer Owner Sign-off

NOTE:  Ideally, we should merge only fully implemented and tested features into the master branch.
So all the above steps are required for the PR to be merged.
In order to avoid the PRs becoming stale and requiring to be rebased on master, these can be merged
after a reasonable time (current agreement is 3 days) if the System Test Engineer Owner's sign-off
was not provided (last step in the DoD).

IMPORTANT: Any deviation from the plan should be discussed and agreed as a comment in the Feature file.

Sign-off

[ ] Product Owner
[ ] Dev Owner
[ ] System Test Engineer Owner

Related PRs

PR # here

Acceptance Criteria
Acceptance Criteria & User Stories define here (or in a separate file (linked here) for a big feature)

the output should contain all 3 maps

might be good to split the maps  further by specifying arguments (unless it is going to be lumped at source and then filtered on client) to further reduce the output size to parse.

Looks perfect.

!

Any updates on this issue? Still relying on a full ledger state dump is very painful.

@newhoggy you asked how it was with 8.0.0; unfortunately not very good.
 time cardano-cli query stake-snapshot --mainnet --all-stake-pools > stakesnapshot.json

real	35m48.363s
user	0m0.041s
sys	0m0.006s

FYI  We need to see how this PR improves current performance before we proceed with queries for each snapshot.

pinging this issue again here. Ledger state is still very painful at 2.4gb.

A command to query each stake snaphost independently; for example
cardano-cli query stake-snapshot --mark-snapshot ...
cardano-cli query stake-snapshot --go-snapshot ...
the output should contain all 3 maps
[
"delegations",
"poolParams",
"stake"
]

@papacarp this is not on the high priorities at the moment. Integrating CIP1694 is on top, but I'll make sure its taken care off as soon as possible.

Even with binary cbor from the node, we're now at 2.26gb every epoch for the ledger state dump. Please continue to prioritize this. It can take upwards of 5 minutes to download and parse this cbor from the node. Most of this data, we don't use at all.

2.27gb

2.28gb

2.30gb

Just popping in to say hello and that this continues to be a huge issue.

+1


bundle: DRYer root.path entry

Instead of repeating the config.md conditions, just make the linkage more clear.  Now the chain is:

Bundles REQUIRE a config.json which is a bundle artifact.
If that config.json has a root.path entry (as specified in config.md), then add the referenced directory to the set of bundle artifacts.  The config.md requirements include “If defined, a directory MUST exist at the path declared by the field”.
Apply the “MUST all be present in a single directory” condition to all bundle artifacts.  I don't like that direct-child restriction, but I'm not touching it in this commit.

So these are the same requirements as before this commit, but with less redundancy and fewer words.

Rebased around #839 with 6cedef2 → 22836ee.

Please rebase

Please rebase

Rebased around #846 with 22836eec → b420c96c.
The Travis error looks like a network hiccup.  If you want that green you can probably just kick the build again.

LGTM

LGTM


String pattern not work

Hi， ljsonschma doesn't work expected when I try the regular expressions: regular expressions.
The error message is: property "OpenKey" validation failed: failed to match pattern "^(\([0-9]{3}\))?[0-9]{3}-[0-9]{4}$" with "555-1212"

I am wondering how match_pattern function behave like the documents.

As stated in the readme document, the pattern matching feature relies by default on string.find, which doesn't implement the ECMA-262 regular expressions required by JSON schema. In particular, string.find doesn't understand repetitions or optional groups that use used in your example.
As you noted, you can provide your own function by passing it as the match_pattern field in the option table when instantiating the schema. The function must behave like string.find:

It gets the string to match and then the pattern as arguments
It must return something that evaluates to true if there's a match, otherwise false (or nil)

I guess you can use one of the many PCRE bindings available for Lua for your use case.
See https://github.com/jdesgats/ljsonschema/blob/master/jsonschema/init.lua#L661


chore: yarn upgrade on all packages except react

Overview
I get security alerts for the repo, thought I'd make a PR to deal with them
I updated everything except the react package @friederbluemle  😅
This only changes yarn.lock and package.json dependencies, no code was changed, so should have no functional effect?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


is there any way to start steam client when steam mobile authenticator is on?

Recently, I turned on steam mobile authenticator. When I try to log in to steam by node-steam I got the steam error 85.
is there any way to start steam client when steam mobile authenticator is on?
my code looks like this:
// Initialize the Steam client and our trading library
var client = new steam.SteamClient();
var trade  = new steamtrade();
var sentryfile;
if(fs.existsSync('sentryfile.' + username + '.hash')) {
sentryfile = fs.readFileSync('sentryfile.' + username + '.hash');
}
//  Let's try logging in.
client.logOn({
accountName: username,
password: password,
shaSentryfile: sentryfile // If null, a new Steam Guard code will be requested
});

You're using an old and unsupported version of node-steam, and your question has been already asked many times here, please learn to search.


Add indirect and polymorphic to the ISO C++ Standard

Linked issue from ISO C++ Standards Committee: https://github.com/cplusplus/papers/issues/1680

Passed.

Some ambiguities in design and wording need our attention.


request may not have a session

see https://github.com/silverstripe/silverstripe-framework/pull/10512

Released as 4.11.9


Assign eligibility for privileged access group to group members

When doing an eligible assignment for a PAG I can select users and also security groups.
What happens when I select another security group to be eligible?

What I would like to achieve is to make individual members of a security group eligible for the PAG (to use GDAP roles assigned to the group).
Is nesting groups this way supported?
It seems not, as I cannot activate the eligible assignment for my user account who is a member of the group I have assigned.
The usecase is that a have a group of admins and I want each individual admin in that group to be eligible for the membership in the PAG. Is there a way to to that without having to manually add a user assignment for each user?

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

ID: f4da66b2-36f2-753f-4170-bcbf51824033
Version Independent ID: c9e72e4f-effc-37f0-f418-c92af00f0523
Content: Assign eligible owners and members for privileged access groups - Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/privileged-identity-management/groups-assign-member-owner.md
Service: active-directory
Sub-service: pim
GitHub Login: @curtand
Microsoft Alias: curtand

@joergrenn
Thanks for your feedback! We will investigate and update as appropriate.

@joergrenn
Since this issue isn't directly related to improving our docs, and to gain a better understanding of your issue, I'd recommend working closer with our support team via an Azure support request. Or you can leverage our Q&A forum by posting your issue there so our community, and MVPs can further assist you in troubleshooting this issue or finding potential workarounds.
Thank you for your time and patience throughout this issue!

Hello @JamesTran-MSFT
the docs are supposed to describe the feature, right?
I my opinion the description is missing if its possible to assign eligibility for membership of a PAG to a group and what happens if you do that.
If its not possible or doesn't work thats also a statement.

@joergrenn
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

#reassign:@amsliu

@joergrenn Thanks for providing feedback that helps improve our documentation. We are currently updating all the end-user content and we will address your issue as part of this process. We are now closing the issue. #please-close


build: fix windows build, build on multiple os using node 12 only

Fixes https://github.com/netlify/netlify-cms/issues/3444
Also, added build jobs for Mac OS and Windows and removed building on Node 10 (updated the contributing guide).
I think we can use Node LTS as a convention.
@erquhart Do you see any reason to build on non LTS versions?

@erezrokah I’m good with it, we can always adjust if non-LTS proves necessary.


CET Release Notes 5.31.0

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://656eb0a51c6f8a0d6b0d0a86--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://656f4138c2286e0b5714d1e2--harness-developer.netlify.app


Assistant with files

Silly question, but is there an example somewhere of creating an assistant, and providing it with a bunch of files to work with?  Maybe a full example that shows changing temperature, etc.?   Is there a way to create a vector store?

Hi there,
I updated the examples with more complex sample that hopefully answers your question:
See here: assistant example
Please re-open if you think this needs more.


FIX: whitenoise collectstatic source map

Fixes an issue with the whitenoise collectstatic which will crash because source map is not included.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@d5fa16e). Click here to learn what that means.

Additional details and impacted files
@@           Coverage Diff            @@
##             main       #25   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         5
  Lines           ?        37
  Branches        ?         0
========================================
  Hits            ?        37
  Misses          ?         0
  Partials        ?         0

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


cant generate 3d mesh file from delatin web

source png downloaded from https://mapbox.github.io/delatin (bay area, usa saved after height counted stop)

code
import imageio.v2 as imageio
import meshio
from pydelatin import Delatin
from pydelatin.util import decode_ele, rescale_positions

path = './bay_area_usa.png'
img= imageio.imread(path)
terrain = decode_ele(img, 'mapbox')
tin = Delatin(terrain, max_error = 30)
vertices, triangles = tin.vertices, tin.triangles
cells = [("triangle", triangles) ]
mesh = meshio.Mesh(vertices, cells)
mesh.write('bay_area_usa.stl')

result not expected

expected result
can see the terrain elevation in 3d format (*.stl)
n.b.

saved file size is 1280 x 1280 got same result
resized the source file into 512 x 512 got same result
tried every images provide from delatin web, got same result

best regards

source png downloaded from https://mapbox.github.io/delatin (bay area, usa saved after height counted stop)

That's the visual representation of the mesh from the output of delatin. It's not the input.
If you look at the network tab, you can copy the curl command to fetch it
curl 'https://a.tiles.mapbox.com/v4/mapbox.terrain-rgb/11/2014/1267@2x.png?access_token=pk.eyJ1IjoibW91cm5lciIsImEiOiJjbG83ZDF0ZGgwNTJ1MmtsajF1ZDN0c3ZvIn0.56k4reJ2cZAGNVklIGCXnQ' \
  -H 'sec-ch-ua: "Chromium";v="124", "Google Chrome";v="124", "Not-A.Brand";v="99"' \
  -H 'Referer: https://mapbox.github.io/' \
  -H 'Origin: https://mapbox.github.io' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36' \
  -H 'sec-ch-ua-platform: "macOS"' > terrain.png

This is the input data meant to be passed to the algorithm


Add browser tests

Add browser-based tests which will run using QUnit and PhantomJS.
These tests will be run along with existing tests in the grunt test task.

Marking this as invalid as browser tests will be used from the start for the browser package as part of the Europa :new_moon: rewrite.


Is there a way to detect when ctrl is pressed?

I want to globaly detect when ctrl is pressed (just the Control key. No other combinations.) And the example in the README, keycomb and #41 don't work.
Is this possible?

I figured it out. You can detect ctrl with IKeyboardEvents.KeyDown and IKeyboardEvents.KeyUp but not IKeyboardEvents.KeyPress.
This is in IKeyboardEvents.cs:

The KeyPress event is not raised by non-character keys; however, the non-character keys do raise the KeyDown and KeyUp events.

Is there any example code how to detect left -> ALT CTRL SHIFT?


Precomp.cpp and Nuget errors

Your Windows build number:  18890.1000

What you're doing and what's happening: Opening solution then building the following as Debug x64:

What's wrong / what should be happening instead:

When loading:
This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\..\..\packages\Microsoft.UI.Xaml.2.1.190405001-prerelease\build\native\Microsoft.UI.Xaml.targets.	CascadiaPackage	F:\Users\seacr\source\repos\Terminal\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj	120

When building: Repetitions of differenet versions of fatal error C1083: Cannot open source file: '..\precomp.cpp': No such file or directory (basically lots of errors referring to precomp.cpp missing).
When running .\tools\razzle.cmd:
PM> .\tools\razzle.cmd
Could not find MsBuild on your machine. It may be installed somewhere else.

That's pretty strange. If you right-click the solution inside Visual Studio and choose "Restore missing packages...", does it do anything?
We're tracking build issues like this in the build megathread at #489.

@DHowett-MSFT, in the end, I just used the included nugen.exe directly to restore packages, but that precomp.cpp spam is still there:

same NuGet error:
Severity	Code	Description	Project	File	Line	Suppression State
Error		This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\..\..\packages\Microsoft.UI.Xaml.2.1.190405001-prerelease\build\native\Microsoft.UI.Xaml.targets.	CascadiaPackage	C:\Users\xxxx\Desktop\New folder\Terminal-master\Terminal-master\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj	120

@DavidShield use included nugen.exe to restore and that'll go.

No resolution?
Severity	Code	Description	Project	File	Line	Suppression State
Error		This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ......\packages\Microsoft.UI.Xaml.2.1.190405001-prerelease\build\native\Microsoft.UI.Xaml.targets.	CascadiaPackage	D:\Downloads\Terminal-master\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj	123

@lazerl0rd, Hi, I tried to restore, but it didn't work
PS E:\Workspace\Visual Studio 2019\Visual Studio Projects\Terminal\dep\nuget> .\nuget.exe restore
The folder 'E:\Workspace\Visual Studio 2019\Visual Studio Projects\Terminal\dep\nuget' does not contain an msbuild solution or packages.config file to restore.

@lazerl0rd, Hi, I tried to restore, but it didn't work
PS E:\Workspace\Visual Studio 2019\Visual Studio Projects\Terminal\dep\nuget> .\nuget.exe restore
The folder 'E:\Workspace\Visual Studio 2019\Visual Studio Projects\Terminal\dep\nuget' does not contain an msbuild solution or packages.config file to restore.
Don't cd into the folder and run it. Start in E:\Workspace\Visual Studio 2019\Visual Studio Projects\Terminal then do .\dep\nuget\nuget.exe restore.

No resolution?
Severity Code Description Project File Line Suppression State
Error This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ......\packages\Microsoft.UI.Xaml.2.1.190405001-prerelease\build\native\Microsoft.UI.Xaml.targets. CascadiaPackage D:\Downloads\Terminal-master\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj 123
Follow the instructions I gave above.

I get that same error AFTER restoring packages from the command line:

The missing file is ......\packages\Microsoft.UI.Xaml.2.1.190405001-prerelease\build\native\Microsoft.UI.Xaml.targets.	CascadiaPackage (loading...)	C:\dev\Terminal\src\cascadia\CascadiaPackage\CascadiaPackage.wapproj	123

:(

Of course, RIGHT after I posted that, I saw that it was because it defaulted to targeting ARM64 by default.
Switch to"x64" and it should build

you need find and add MSBuild.exe  to system value
such as
MSBUILD
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe

Looks like this sorted itself out. Resolving.

@miniksa my build problem hadn’t been fully resolved. Only one section of it was. I still get the precmp failures.

you need find and add MSBuild.exe to system value
such as
MSBUILD
C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe
restart vs code

@songjiang951130 if you mean add to Env? It’s already there. And I’m using VS 2019 not VS Code.


Increase limit in suggestion list

Is there any way I can control the limit of items in suggestion list? It seems like it's currently limited to 5.
The problem is I have about 7 items like "First Item", "Second Item", "Third Item", "Fourth Item", "Fifth Item", "Sixth Item" and "Item". Let's say I want to choose an "Item". But when I enter "item" in search field I get only 5 first items. So apparently there's no way to choose an "Item" with that data source now.

@imajus try to specify data-limit attribute


Do not use daemon for nbconvert command

For #8483
For some reason the convert command fails on some Python versions with the following error:
Info 2019-11-25 00:42:43: Failed executing an rpc method. Error: Traceback (most recent call last):
  File "/home/vsts/work/1/s/pythonFiles/datascience/daemon/daemon_python.py", line 54, in _decorator
    return func(self, *args, **kwargs)
  File "/home/vsts/work/1/s/pythonFiles/datascience/jupyter_daemon.py", line 33, in m_exec_module
    return self._execute_and_capture_output(lambda : self._convert(args))
  File "/home/vsts/work/1/s/pythonFiles/datascience/daemon/daemon_python.py", line 104, in _execute_and_capture_output
    func()
  File "/home/vsts/work/1/s/pythonFiles/datascience/jupyter_daemon.py", line 33, in <lambda>
    return self._execute_and_capture_output(lambda : self._convert(args))
  File "/home/vsts/work/1/s/pythonFiles/datascience/jupyter_daemon.py", line 94, in _convert
    app.main()
  File "/home/vsts/py-3.7.5/lib/python3.7/site-packages/jupyter_core/application.py", line 268, in launch_instance
    return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
  File "/home/vsts/py-3.7.5/lib/python3.7/site-packages/traitlets/config/application.py", line 662, in launch_instance
    app = cls.instance(**kwargs)
  File "/home/vsts/py-3.7.5/lib/python3.7/site-packages/traitlets/config/configurable.py", line 423, in instance
    '%s are being created.' % cls.__name__
traitlets.config.configurable.MultipleInstanceError: Multiple incompatible subclass instances of NbConvertApp are being created.

Codecov Report

Merging #8777 into master will decrease coverage by 0.29%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master    #8777     +/-   ##
=========================================
- Coverage   58.39%   58.09%   -0.3%
=========================================
  Files         527      527
  Lines       27070    27070
  Branches     4045     4040      -5
=========================================
- Hits        15808    15727     -81
- Misses      10404    10485     +81
  Partials      858      858

Impacted Files
Coverage Δ

src/client/datascience/jupyter/jupyterCommand.ts
97.05% <100%> (ø)
:arrow_up:

src/client/testing/serviceRegistry.ts
49.09% <0%> (-47.28%)
:arrow_down:

src/client/testing/codeLenses/main.ts
40% <0%> (-30%)
:arrow_down:

src/client/datascience/jupyter/jupyterUtils.ts
64.7% <0%> (-29.42%)
:arrow_down:

...t/datascience/jupyter/jupyterDataRateLimitError.ts
50% <0%> (-25%)
:arrow_down:

src/client/formatters/serviceRegistry.ts
75% <0%> (-25%)
:arrow_down:

...ience/jupyter/jupyterDebuggerRemoteNotSupported.ts
60% <0%> (-20%)
:arrow_down:

...cience/jupyter/jupyterDebuggerNotInstalledError.ts
50% <0%> (-16.67%)
:arrow_down:

src/client/common/utils/icons.ts
83.33% <0%> (-16.67%)
:arrow_down:

src/client/api.ts
80% <0%> (-13.34%)
:arrow_down:

... and 5 more

Continue to review full report at Codecov.

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


Remove message about env value store

What does this PR do?
Add missing values in envStoreKey to avoid warnings
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Plot spectrogram show frequency data in Hz

Hello,
First of all thank you for the fabulous toolkit and tutorials. Second, I want to plot a spectrogram of EEG data, showing the power for each frequency band in a given measurement (along time of course).
Is this possible with your toolkit?
If so, I didn't understand how I can make the y-axis show a frequency scale in Hz, and I couldn't find a clear place to specify the frequency parameter of my data (it is necessary for the generation of a time-frequency plot).
Thanks a lot,
Elad

I think you just need to specify the parameter yaxis='frequency' in the call to scg.cws function.  Default magnitude output is amplitude.  If you want power you can specify the parameter spectrum='power'


hapi-fhir-spring-boot-sample-server-jpa does not support Bundle transactions

Issue
We are trying to use HAPI FHIR Spring Boot Sample (https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-spring-boot/hapi-fhir-spring-boot-samples/hapi-fhir-spring-boot-sample-server-jpa) as a base to work from, however we noticed that it does not seem to support Bundle transactions out of the box. After spinning up the server and trying to POST a Bundle with type set to 'transaction' the server responds with 400 - This is the base URL of FHIR server. Unable to handle this request, as it does not contain a resource type or operation name.
We have looked at some of the other sample JPA servers available and they all seem to support Bundle transactions, however they are using old style Servlets and web.xml rather than Spring Boot which we would like to avoid (most of our projects use Spring Boot and so a lot of our internal tooling depends on it).
Would be great to know if there is a simple fix for this.
Environment

HAPI FHIR Version: 3.7.0
OS: Mac
Browser: N/A

Additional context
We noticed when using the HAPI FHIR Spring Boot Sample that the /metadata endpoint does not include:
"interaction": [                 {                     "code": "history-system"                 },                 {                     "code": "transaction"                 }
which seems to be present for some of the other example servers.
Many Thanks!

@mouellet any thoughts?

Any update on this? I am migrating my HAPI JPA server to spring-boot and am blocked by this issue.

Have you tried modifying the other examples to use spring boot?
In my SpringBootServletInitializer
@Bean
public ServletRegistrationBean ServletRegistrationBean() {
    ServletRegistrationBean registration = new ServletRegistrationBean(new JpaRestfulServer(context), "/STU3/*");
    Map<String,String> params = new HashMap<>();
    params.put("FhirVersion","DSTU3");
    params.put("ImplementationDescription","LTHT FHIR CDR");
    registration.setInitParameters(params);
    registration.setName("FhirServlet");
    registration.setLoadOnStartup(1);
    return registration;
}

Modified the JpaRestful server
@WebServlet(urlPatterns = { "/STU3/*" }, displayName = "FHIR CDR Server")
public class JpaRestfulServer extends RestfulServer {
private static final long serialVersionUID = 1L;

private ApplicationContext appCtx;

private static final org.slf4j.Logger log = org.slf4j.LoggerFactory.getLogger(JpaRestfulServer.class);

JpaRestfulServer(ApplicationContext context) {

    // This is called from spring boot
    this.appCtx = context;

}

On 27 Mar 2019, at 16:45, Ben<EMAIL_ADDRESS>wrote:
Issue
We are trying to use HAPI FHIR Spring Boot Sample (https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-spring-boot/hapi-fhir-spring-boot-samples/hapi-fhir-spring-boot-sample-server-jpa https://github.com/jamesagnew/hapi-fhir/tree/master/hapi-fhir-spring-boot/hapi-fhir-spring-boot-samples/hapi-fhir-spring-boot-sample-server-jpa) as a base to work from, however we noticed that it does not seem to support Bundle transactions out of the box. After spinning up the server and trying to POST a Bundle with type set to 'transaction' the server responds with 400 - This is the base URL of FHIR server. Unable to handle this request, as it does not contain a resource type or operation name.
We have looked at some of the other sample JPA servers available and they all seem to support Bundle transactions, however they are using old style Servlets and web.xml rather than Spring Boot which we would like to avoid (most of our projects use Spring Boot and so a lot of our internal tooling depends on it).
Would be great to know if there is a simple fix for this.
Environment
HAPI FHIR Version: 3.7.0
OS: Mac
Browser: N/A
Additional context
We noticed when using the HAPI FHIR Spring Boot Sample that the /metadata endpoint does not include:
"interaction": [ { "code": "history-system" }, { "code": "transaction" }
which seems to be present for some of the other example servers.
Many Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/jamesagnew/hapi-fhir/issues/1256, or mute the thread https://github.com/notifications/unsubscribe-auth/AG3Y8kWnK0X3Ro3pz1e27capmtLb3UHqks5va6AxgaJpZM4cOR_-.

Unfortunately I'm not really sure what to do here.
The Spring Boot stuff was a community contribution, which is awesome, but it hasn't been maintained and I don't use Boot so I'm not in a position to do so.
I guess the right thing probably is to put out a call on the mailing list for a new owner and to deprecate if nobody steps up.

@jamesagnew we are also migrating from the JPA server to Spring Boot. So we will evaluate internally if we can take over the Spring project and we will let you know.

I was able to repro the issue on a working server by using the deprecated setPlainProviders() method. Therefore, I believe the issue is the use of that deprecated method in the FhirAutoConfiguration class (https://github.com/jamesagnew/hapi-fhir/blob/master/hapi-fhir-spring-boot/hapi-fhir-spring-boot-autoconfigure/src/main/java/ca/uhn/fhir/spring/boot/autoconfigure/FhirAutoConfiguration.java#L195). That should be registerProviders(systemProviders), right?

Hi guys,
@c-schuler, looks like your on the right track!
Sorry for not being more active, I've done that for client a while ago and I fear I don't have the time to support it now...
Anyway, the auto-configuration for this project only picks up the existing spring configurations from the underlying modules based on conditions. Just make sure any changes to those underlying spring configurations are be propagated.

Here's how I got it to work and a suggestion for a patch:
In your Spring configuration class, add the following bean:
    @Bean
    public JpaSystemProviderR4 jpaSystemProviderR4() {
        JpaSystemProviderR4 provider = new JpaSystemProviderR4();
        provider.setContext(fhirContext);
        return provider;
    }

And if you don't have a FhirRestfulServerCustomizer, then add one to your Spring configuration class too in order to register the provider above:
    @Bean
    public FhirRestfulServerCustomizer customize(
        List<IResourceProvider> resourceProviders,
        List<PlainProvider> plainProviders) {
        return (server) -> {

            server.setResourceProviders(resourceProviders);
            server.registerProvider(jpaSystemProviderR4());
            server.registerProviders(plainProviders);
        };
    }

Now, you need to modify JpaSystemProviderR4 in hapi-fhir-jpaserver-base and re-compile for your project (this is where patching the class will come in handy for future generations):
package ca.uhn.fhir.jpa.provider.r4;
...
public class JpaSystemProviderR4 extends BaseJpaSystemProviderDstu2Plus<Bundle, Meta> {

    @Autowired()
    @Qualifier("mySystemDaoR4")
    private IFhirSystemDao<Bundle, Meta> mySystemDao;

    @Autowired(required = false)
    private IFulltextSearchSvc mySearchDao;

    @PostConstruct
    public void initJpaSystemProviderR4() {
        setDao(mySystemDao);
    }
  ...
}

The code to add is the @PostConstruct method that configures the DAO.

Please let me know if you need further help as I may have missed something in my explanation.
--Matt


Lack of document/example for CommonJS project

It would have saved me a couple of hours if there is some instructions about how to require this module in a CommonJS project. I almost switched to other tools because I was not able to load the module.

How did you do it?

I have to require the library first, then invoke it with a d3 variable before using d3.tip(). Below is my coffeescript code:
d3tip_module = require 'd3-tip'
d3.tip is defined with the following call
d3tip_module(d3)
d3.tip().attr('class', 'd3-tip')...

Same problem, thanks for the solution

I was having the same problem and that worked. Thanks a lot for sharing.

I don't use commonjs, so if someone wants to submit a documentation update for this I'd be happy to accept it.


Updates to Node affinity weight section

Current:
https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity-weight
"If there are two possible nodes that match the requiredDuringSchedulingIgnoredDuringExecution rule, one with the label-1:key-1 label and another with the label-2:key-2 label, the scheduler considers the weight of each node and adds the weight to the other scores for that node, and schedules the Pod onto the node with the highest final score."
Change:
If there are two possible nodes that match the preferredDuringSchedulingIgnoredDuringExecution rule, one with the label-1:key-1 label and another with the label-2:key-2 label, the scheduler considers the weight of each node and adds the weight to the other scores for that node, and schedules the Pod onto the node with the highest final score.

/lgtm
Thanks


Autotyping Text Animation in the

Is your feature request related to a problem? Please describe.
Autotyping Text Animation will improve the website's overall dynamic nature.
Describe the solution you'd like
I would like to add some changes to the website repo via a PR that will make the text auto-type the text - " Welcome to Embellish".
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

We don't need this right now

ok


Create test.md

What problem does this PR solve?
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Code changes

Has exported function/method change
Has exported variable/fields change
Has interface methods change
Has persistent data change

Side effects

Possible performance regression
Increased code complexity
Breaking backward compatibility

Related changes

Need to cherry-pick to the release branch
Need to update the documentation
Need to update the tidb-ansible repository

Release note

Write release note for bug-fix or new feature.

/help

/test all

/test

/test

/test

/test


Adding a summary class with fieldname change requires reindex

When adding a summary class like:
    document-summary rename-summary {
        summary artist_name type string {
            source: artist
        }
    }

I get a re-index warning:
$ vespa deploy --wait 300
Uploading application package ... done

Success: Deployed .
WARNING In schema 'music', document summary 'rename-summary': Fields [artist_name] references non-attribute fields: Using this summary will cause disk accesses. Set 'from-disk' on this summary class to silence this warning.
WARNING Change(s) between active and new application that may require re-index:
reindexing: Consider re-indexing document type 'music' in cluster 'mycontentcluster' because:
    1) Document type 'music': Non-document field 'artist_name' added; this may be populated by reindexing

(disregard the first warning, that is expected)
Per https://docs.vespa.ai/en/reference/schema-reference.html#valid-changes-without-restart-or-re-feed I think there should be no need for reindexing.
Running the query without reindexing:
$ vespa query "select * from music where album contains 'head'" presentation.summary=rename-summary
{
    "root": {
        "id": "toplevel",
        "relevance": 1.0,
        "fields": {
            "totalCount": 1
        },
        "coverage": {
            "coverage": 100,
            "documents": 3,
            "full": true,
            "nodes": 1,
            "results": 1,
            "resultsFull": 1
        },
        "children": [
            {
                "id": "index:mycontentcluster/0/de97c3f0cf0d1122b3494a44",
                "relevance": 0.16343879032006284,
                "source": "mycontentcluster",
                "fields": {
                    "sddocname": "music"
                }
            }
        ]
    }
}

The field is not there. If I re-feed, it works, as the warning says:
$ vespa document ext/A-Head-Full-of-Dreams.json &&   vespa document ext/Love-Is-Here-To-Stay.json &&   vespa document ext/Hardwired...To-Self-Destruct.json
Success: put id:mynamespace:music::a-head-full-of-dreams
Success: put id:mynamespace:music::love-id-here-to-stay
Success: put id:mynamespace:music::hardwired-to-self-destruct

$ vespa query "select * from music where album contains 'head'" presentation.summary=rename-summary
{
    "root": {
        "id": "toplevel",
        "relevance": 1.0,
        "fields": {
            "totalCount": 1
        },
        "coverage": {
            "coverage": 100,
            "documents": 3,
            "full": true,
            "nodes": 1,
            "results": 1,
            "resultsFull": 1
        },
        "children": [
            {
                "id": "index:mycontentcluster/0/de97c3f0cf0d1122b3494a44",
                "relevance": 0.16343879032006284,
                "source": "mycontentcluster",
                "fields": {
                    "sddocname": "music",
                    "artist_name": "Coldplay"
                }
            }
        ]
    }
}

I find it quite odd that a re-feed is necessary in this case / the documentation needs an update if so
$ curl http://localhost:8080/state/v1/version
{
  "version" : "8.73.7"
}

        field artist type string {
            indexing: summary | index
        }

Clarified with @geirst : This is expected behavior for non-attribute fields. I will update documentation

Documented in https://github.com/vespa-engine/documentation/pull/2401


Fix regression

fix regressions introduced by PR #949

[x] add _cpu tag to lib correctly.
[x] restore some stuff, accidentally/unintensioally reverted by PR #949

Some of @rickardp's changes, whether intended or not, maybe better done in python-package.yml. However, it causes some serious problems, and it is important to quickly fix things that were fine before, I am submitting this PR.
P.S.: PR #1018 is not included.

At first glance, this basically reverts a lot of Rickard's work - could you explain why the changes are needed? There also seems to be a bunch of changes that aren't really "fix regression"..?

as I already mentioned, this is a quick and manual revert to fix the current regression state.

The missing _cpu tag might well be a regression, but this PR seems to be putting the Mamba/Conda stuff back in (why?), adding a setuptools and wheel in the shared-libs step, etc.
Wouldn't it be better to just fix things for the better instead of a "quick revert" that someone will need to fix again later? Since there's a lot of activity in this repo just now, and we're working in a state where we don't really have the luxury to actually properly test anything, I think we should accept the fact that main might be broken.

Could you maybe look into other options than mamba? I mean, this repo itself has install_cuda.py and install_cuda.sh scripts which apparently are meant to install the CUDA Toolkit – maybe we should use those?

Some comment from me, possibly #949 was merged too quick without aligning on the scope. Sorry for not realizing this! May I suggest discussing improvements in the RFCs, maybe in #1031?
I would argue the easiest way to manage CUDA dependencies is through Docker. What is currently lacking is dependabot-managed update for the CUDA versions. I was actually planning to fix this in a follow up PR, it involves creating Dockerfiles for the CUDA images as this is what Dependabot can work wiith. We need to continuously monitor for updates as NVIDIA deprecates CUDA versions fast, and Dependabot is the realistic way to handle this.  The problem here is Windows. While there seems to be some community-based Windows containers, AFAIK hosted runners won't run Windows containers. The community GitHub action does a decent job, but it's slow, owing to the fact that it runs the horribly slow CUDA installer. Some kind of image-based approach (just like Docker  for the Linux builds) would be the best solution

Hey @wkpark, @akx, @matthewdouglas, @rickardp,
Yes agreed, #949 was merged a bit hasty, due to an misunderstanding and too quick trigger finger on my side. Sorry for that! And thanks everyone for the collective cleanup / hotfix actions that ensued and got everything back to working order.
Based on your discussion above, I'm now not sure if this PR is still WIP or if you all agree that it's ready for review and merge? If not, what do we need to still implement or agree on in order to move forward?

Hey @wkpark, @akx, @matthewdouglas, @rickardp,
Yes agreed, #949 was merged a bit hasty, due to an misunderstanding and too quick trigger finger on my side. Sorry for that! And thanks everyone for the collective cleanup / hotfix actions that ensued and got everything back to working order.
Based on your discussion above, I'm now not sure if this PR is still WIP or if you all agree that it's ready for review and merge? If not, what do we need to still implement or agree on in order to move forward?

TBH I thought this PR was abandoned and most of the stuff had been broken out to other PRs.
I'll have another look as I am not completely sure what issues remain that this PR solves

use<EMAIL_ADDRESS>instead of microsoft/setup-msbuild
microsoft/setup-msbuild is used for msbuild<EMAIL_ADDRESS>
This is already on master I think

fix wheel names for aarch64

drop artifact retention-days: it could be configured Settings->Actions->General.

fail-fast: false restored.

I suggest we make these separate PRs. I think retention days we want to set separately per artifact type as some artifacts (wheels) are more useful than others (.so files). But agreed these need tuning

Hey @wkpark, @akx, @matthewdouglas, @rickardp,
Yes agreed, #949 was merged a bit hasty, due to an misunderstanding and too quick trigger finger on my side. Sorry for that! And thanks everyone for the collective cleanup / hotfix actions that ensued and got everything back to working order.
Based on your discussion above, I'm now not sure if this PR is still WIP or if you all agree that it's ready for review and merge? If not, what do we need to still implement or agree on in order to move forward?

several PRs have been already extracted and merged.
We can consider this PR as a reference or ideas, I do not intend to get it merged without further discussion or agree.


karibu-testing-v10:1.1.14 - MockVaadin.setup fails with Java 13

With karibu-testing-v10:1.1.14, Vaadin 14.0.7 and Java 13 we always get the following Exception when trying to setup a test:
java.lang.NoSuchFieldException: modifiers

	at java.base/java.lang.Class.getDeclaredField(Class.java:2412)
	at com.github.mvysny.kaributesting.v10.UtilsKt.makeNotFinal(Utils.kt:61)
	at com.github.mvysny.kaributesting.v10.MockNpmTemplateParser$Companion.install(MockNpmTemplateParser.kt:129)
	at com.github.mvysny.kaributesting.v10.MockVaadin.mockVaadin14(MockVaadin.kt:152)
	at com.github.mvysny.kaributesting.v10.MockVaadin.setup(MockVaadin.kt:126)
	at com.github.mvysny.kaributesting.v10.MockVaadin.setup(MockVaadin.kt:106)
	...

To me it looks like in Utils.kt#61 you try to change the "modifiers" of class "java.lang.reflect.Field" to being accessible and not final instead of the static "INSTANCE" field in class "com.vaadin.flow.component.polymertemplate.NpmTemplateParser"?!
We verified that (at least) all karibu-testing-v10 versions after 1.1.11 show this behaviour.

Unfortunately the NpmTemplateParser.INSTANCE field is final and cannot be modified without nasty reflection magic. There is more information at https://github.com/mvysny/karibu-testing/issues/26
I'm sad that the reflection magic doesn't work on Java 13; I'll add a more clear error message into Karibu-Testing. Meanwhile, please vote for https://github.com/vaadin/flow/issues/6537 to be fixed.
As a workaround:

Please use Java 11 - the "nasty reflection" solution works there.
Downgrade to Karibu-Testing 1.1.11. It works around NpmTemplateParser in a different way, but it may not work for you properly.

I'll add a test for Java 13 and show a more meaningful error message.

The fix has been merged into Vaadin, but will only be present in Vaadin 15+. The fix is not yet present in Vaadin 15.0.0.beta1.

Fixed - Karibu-Testing 1.2.x is now compatible with Java 13, but only works with Vaadin 15+.


Update for Qiskit 1.0

What
Updates code and examples to work with Qiskit 1.0.
Why
Qiskit 1.0 brings some stability guarantees and performance improvements. Most new users will use Qiskit 1.0 and will expect this project to be compatibile with it.
How
Mostly find/replace of import paths. Also replacing execute with backend.run.
# Old
execute(circuit, backend)

# New
transpile(circuit, backend)  # not always needed
backend.run(circuit)

See (Qiskit 1.0 feature changes)[https://docs.quantum.ibm.com/api/migration-guides/qiskit-1.0-features] for more information.
Remarks
I re-ran the example notebooks that used Qiskit, with the exception of examples/Full_loop_single_qubit.ipynb which I could not get working (see #244). Since it's not caused by the Qiskit upgrade, I think fixing it is out of scope of this PR. Please advise on how you'd like to handle it.
View de1cde6c84b44f2972065a862c0720cf1b89495d to see only the code changes to examples without the new cell outputs.
Checklist
Please include and complete the following checklist. Your Pull Request is (in most cases) not ready for review until the following have been completed. You can create a draft PR while you are still completing the checklist. Check the Contribution Guidelines for more details. You can mark an item as complete with the - [x] prefix

[x] Tests - Added unit tests for new code, regression tests for bugs and updated the integration tests if required
[x] Formatting & Linting - black and flake8 have been used to ensure styling guidelines are met
[ ] Type Annotations - All new code has been type annotated in the function signatures using type hints
[ ] Docstrings - Docstrings have been provided for functions in the numpydoc style
[ ] Documentation - The tutorial style documentation has been updated to explain changes & new features
[x] Notebooks - Example notebooks have been updated to incorporate changes and new features
[x] Changelog - A short note on this PR has been added to the Upcoming Release section

CI is failing but I can't reproduce locally; the tests passed and black claimed all .py files were formatted correctly.

CI is failing but I can't reproduce locally; the tests passed and black claimed all .py files were formatted correctly.

HI Frank, thanks for adding the qiskit 1.0 support and making the PR. I will look into the failing tests.


Translating - React without ES6

working on the page: "React without ES6"

🎉

Thank you Aladin for your contribution and for all what you're doing for the React community!
I have some suggestions if you don't mind 😄

sure, my pleasure! anything about sharing, learning, and building. I'm in!


Proposal: mechanism for handling multiple actions with the same reducer.

Hi all!
I'd like to propose a new feature to allow handling multiple actions with the same reducer in the case that someone has very general, over-arching properties of their state.
For example, when using redux on its own I've found it useful to have a loading property which gets reduced like this:
function loading(state = false, action) {
  switch(action.type) {
  case LOAD_SOMETHING_START:
  case LOAD_SOMETHING_ELSE_START:
    return true;

  case LOAD_SOMETHING_COMPLETE:
  case LOAD_SOMETHING_ELSE_COMPLETE:
    return false;

  default:
    return state;
  }
}

I find this preferable to invoking an action to update loading within a composite/async action using redux-thunk because I would prefer not to have my state's other properties know about the loading property and keep that logic central to the reducer for loading.
Initially I'd like to propose being able to define an action handler with a name that contains a delimiter like |. To illustrate with the previous example:
handleActions({
  'LOAD_SOMETHING_START | LOAD_SOMETHING_ELSE_START': () => true,
  'LOAD_SOMETHING_COMPLETE | LOAD_SOMETHING_ELSE_COMPLETE': () => false
}, false);

Alternatively, if it would be preferable not to expose the details about how to delimit action names, a function combineActions() might help:
const startActions = combineActions('LOAD_SOMETHING_START', 'LOAD_SOMETHING_ELSE_START');
const completeActions = combineActions('LOAD_SOMETHING_COMPLETE', 'LOAD_SOMETHING_ELSE_COMPLETE');

handleActions({
  [startActions]: () => true,
  [completeActions]: () => false
}, false);

What do you think? I'd be thrilled to submit a PR for this if we agree it would be worthwhile.

:+1: I like this a lot, and it's something that has kept me from fully adopting a createReducer/handleActions abstraction in my applications.
I know this issue is fairly dead, but there is interest :)

:+1: Here's some additional interest

:+1:

:+1:

thats very very useful 👍
@lukewestby is there any wip on this?
if not so, can I start working on it?

👍

I was thinking that a conventional delimiter like | could work, but there's no obvious way for library users to join action creators (which can be used as inputs to handleActions or handleAction) since the way an action creator stores its type (via toString) seems encapsulated from the library user.
So, I think the combineActions approach seems the most reasonable.

I've been using this feature at work via a fork of this project and it's turned out great for DRY'ing up our reducers (especially when using reducer composition). I'll see if I can contribute this feature back to the repository.
As mentioned above though, I don't see a cleaner path to doing this than the combineActions approach.


Mode Selection Documentation

I am unable to find any documentation on how "default mode" for CNI of transparent or bridged is selected, or how to verify what mode a cluster is using.  Can modes be switched? Are they switched automatically as part of https://github.com/Azure/AKS/releases/tag/2020-11-30 ?
I also haven't seen any mention of Calico in a while, and the documentation from "Transparent" looks awfully similar. If they are related, an explanation would be valuable.
I've upgraded az cli to
2.16.0, and see no mention of transparent mode in the inline help for az aks create or az aks update, so the web docs are my only source.

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

ID: d501ff67-9208-8bcb-e8df-f09e9b16a802
Version Independent ID: e3fc3851-ddc4-d26c-251d-6ae53d714081
Content: Frequently asked questions for Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/faq.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

+1
I came here to seek the same information. How do I set the mode? How can I tell what mode my existing clusters are using?

Thank you for the feedback.
We've added a task to our backlog and will prioritize accordingly.
#please-close

#please-open
#reassign:schaffererin

Hi, @rjewell-lower, thank you for the feedback. I apologize for the delay in responding. Since this issue was raised, the docs have been updated. Bridge mode is replaced by Transparent mode, and the doc goes into further detail about the different modes. Since no doc edits need to be made at this time, I will close this GitHub issue. Thank you again! #please-close


Website's navbar is not responsive for smartphone.

the website is not responsive, i want to improve the responsive design of the website.
please assign this task to me under the contribution of GSSoC' 24.

i will like to work on this issue .here is link of responsive navbar for mobile : https://drive.google.com/file/d/1iqDTn9z2nsVdKmp6tQ3FeGcLRPlJ7Ja6/view?usp=drive_link