Unable to write to BLE server(external device) from ESP32(BLE client) using example "gattc_gatts_coex" (IDFGH-3169)

IDF version- v4.1-dev-1086-g93a8603c5
OS- windows
I am using gattc_gatts_coex example to communicate with a "blood pressure monitor device" which is a ble server.
How does this BP monitor work - It works as both manually and by giving values over BLE. For example to start the BP monitor BLE client shou;d send byte array of {00,02,03,64,69} also in hex {0x00,0x02,0x03,0x40,0x45} and after receiving the value the device start NOTIFY the sensed value of Blood Pressure to the client. I tried with nrF BLE scanner app and it work perfectly fine.
Now, I want to implement it wth ESP32 by using gattc_gatts_coex example, The connection is successful but when I tried to write the above mentioned byte array it doesn,t turned on to record the value. I tried to turn it on manually, which can be done by press button and  I am able to receive data in ESP_GATTC_NOTIFY_EVT. I tried different alteration to write to the BLE server (BP monitor device) through ESP32 but none of them are working.
I think there is some UUID issue because the write write_uuid is different from service_uuid or I am doing some mistake in writing the byte array. I am attaching my code, BLE scanner screenshot and debug logs here. Kindly review.
Code is here:-
code.zip
Ble Screenshot of Server:-

Debug Logs:-

@ROYMURLI Thanks for your contribution. @GYC-Espressif

Hi, Any progress in this issue.

Hi, Any suggestions. @Alvin1Zhang  @GYC-Espressif

Hi, @ROYMURLI
Use the esp_ble_gattc_write_char_descr API to set the value of Client Characteristic Configuration to notify. Use as follows:
                    if (count > 0 && descr_elem_result[0].uuid.len == ESP_UUID_LEN_16 && descr_elem_result[0].uuid.uuid.uuid16 == ESP_GATT_UUID_CHAR_CLIENT_CONFIG) {
                        ret_status = esp_ble_gattc_write_char_descr( gattc_if,
                                                                     gattc_profile_tab[GATTC_PROFILE_C_APP_ID].conn_id,
                                                                     descr_elem_result[0].handle,
                                                                     sizeof(notify_en),
                                                                     (uint8_t *)&notify_en,
                                                                     ESP_GATT_WRITE_TYPE_RSP,
                                                                     ESP_GATT_AUTH_REQ_NONE);

                    }

@ROYMURLI Would you please help share if any updates for this issue? Thanks.

I am not working on this issue. I will start again and will check if it is working or not. Till then I am closing this issue. Thanks for your help.


What about HTTP 1.1 support?

Yeah going to look into that and see if I can make some progress on that soon. It works fine in most cases but there are some edge cases where forcing it to 1.0 causes issues.

Please tell me where I am wrong, `cause it does not work for me - I can not get response body with HTTP 1.1:
$request = $client->request('GET', 'http://facebook.com', [], '1.1');
$request->on('response', function ($res) {
$res->on('data', function ($data, $res) {
var_dump($data);
});
});
it does not work for http://vk.com, http://facebook.com
why?

@deathmood answered your question here: https://github.com/reactphp/http-client/pull/49#issuecomment-149054443


Add support for anchor tags

Links that point to non existent anchors https://github.com/lenisha/linkchecker-test/blob/main/about.html#L92 are not detected

This is a bit of a tricky one. Anchors are really the properties of the document contents, not really being integral parts of the URLs.
What I really mean by that is this:

You can't tell if an anchor is valid by merely making a request (you can only check the URL path without the anchor)
To verify anchors, you'd have to parse the HTML and check they're there (but we already do it using html5ever, a browser grade parser)

So this might not be very straightforward, but should be perfectly doable. I'd welcome such a feature :smiley:

To verify anchors, you'd have to parse the retrieved HTML and check they're there (but we already do it for link extraction using html5ever, a browser grade parser)

HTMLs are parsed for link extraction on the input HTML documents, but not for the target HTML documents. So it would required to first check whether the target is actually an HTML document, then download it fully (currently it is only partially downloaded or not all all when using -X head) and then parse the target HTML for a matching id attribute.
When support for internal links via file existence check is added (#21), then it could be at least cheaply added for those:

If the link/URL is an internal one, check only if the target file exists, relative to the input HTML file location or relative to the base path, when given and it is an absolute internal link.
Then, if the target is an HTML file, or a directory that contains an index.htm/index.html, check for a contained matching id attribute.

In other cases, I think it's difficult if one does not want to imply much overhead for checking the URLs document type and downloading it completely.

For reference the hint by @polarathene: https://github.com/lycheeverse/lychee/issues/21#issuecomment-859969005
Another case where the difficulties with target downloads etc do not apply, and probably this is what you had in mind anyway, is to check for scroll links within the input HTMLs. so if there is an , to check whether there is an id="heading" as well. If such is wanted, it's good to create a generic method/function for it, so that URL fragments can be generally detected and HTMLs generally scanned for matching IDs, but at first implemented for such same-page scroll links, then depending on #21 for locally stored target HTML files, and gradually for online HTML documents, when this is found to be important enough to fully download the target, based on content-type: text/html or so. But I'm not sure if the content type header is reliable enough of if there is a risk that a large archive or video file is unintentionally downloaded 😄.

But I'm not sure if the content type header is reliable enough of if there is a risk that a large archive or video file is unintentionally downloaded

Response headers should provide info about content size, completing a request in full (eg downloading a large resource) shouldn't be necessary and could be terminated early AFAIK?

completing a request in full (eg downloading a large resource) shouldn't be necessary and could be terminated early AFAIK?

If you want to check whether the an URL fragment is valid or not, you need to download the whole document of course, which is the whole issue I see here, as long as it's not about same-page links or local files. Currently the download is terminated early, reasonably, so currently it is impossible to apply this feature for remote HTML documents without changing the download behaviour based on such things like HTTP headers, which is why I think one needs to evaluate carefully if the effort is worth it or not 😉.

you need to download the whole document of course, which is the whole issue I see here

Downloading a complete HTML document to operate on isn't much of a concern vs larger files which I thought was being raised as the concern but could be avoided.
You make a good point though, especially with some HTML documents that are dependent on JS to populate the real content, such as React pages without any pre-rendering process involved. That'd require actually loading and running the JS..
I haven't used lychee myself yet, so I'm not sure if it supports that well (anchor tag feature aside).

If other attributes of 'a' tag is provided, you can use that to help you determine whether to download that webpage, or whether it links to webpage, etc. But it gets complicated.
https://html.spec.whatwg.org/multipage/links.html#links

Anchor tags are supported by https://github.com/killercup/link-checker and the implementation is done with a HashSet of anchor links per page. https://github.com/killercup/link-checker/blob/master/src/links.rs. Something to look into if we get around to adding it to lychee.

Sometimes anchors aren’t even in the HTML itself, like for static websites! Another approach could be to make the request with and without the anchor and compare the scroll location if that’s possible, it means making two requests though

make the request with and without the anchor and compare the scroll location if that’s possible

that requires emulation of webpage rendering and is outside the scope of this project.

Also dynamic websites send an HTML document with element IDs, or do you mean scrolling via JavaScript? Usually JavaScript is just used to better control smooth scrolling, in addition to the still present functional element IDs for clients with no JavaScript support.
If there is really no matching ID, then I agree that the required full browser features, including JavaScript engine etc are out of scope. Also I can't imagine that anyone wants to wait 5-10 seconds two times for every checked link, required to load all assets, render the page, execute JavaScript, finish all events etc. Furthermore, since many websites have no definit "all done", but load/show additional dynamic content (ads, cookie banners, notification banners, ...), random seconds after the relevant content has been rendered already, including content shift and changing scroll position, it is practically impossible to do such comparison reliably without a lot of false negatives and without giving a very long grace period (30 seconds?) to minimise the risk of still expanding content.

it might be worth splitting up the scope here. For my use case (a technical specification), I have a bunch of local .md files. I'd like to see that the links within those files are valid: they go to a valid file (already checked), and to a valid target anchor among the spec files.  Also, I'd like to see that the http/s urls at least go to a valid place. As noted it could be challenging to ensure an anchor is valid on a dynamic site. I'm less interested in whether the external HTML files have the right anchor— those are likely to move around and not everyone tries to keep stable links.
Perhaps a way forward would be to have some way to determine which filetypes and schemes are subject to anchor checking.
In my case:  filetype *.md and scheme file: only.
Other users, such as the original author, may make it more broad such as including http: and https:

yes seems solving this as a whole isnt so simple but this solves a part of it
how does it determine if a link follows the md format?

how does it determine if a link follows the md format? checking the pr it seems to check if the link ends with .md

Yep, it just looks at the extension.

Thanks for the summary.
From my perspective, the answers to your open questions would be as follows:

Which of the 5 link types we should support fragment checks for?

I agree that we should tackle 1-3. The other two cases seem to be outliers, which we could tackle later if needed.

Whether they should be opt-in or opt-out?

If it turns out that fragment checking is robust enough, I would not mind enabling it by default. By "robust enough" I mean that the number of false-positives is below a threshold of, say, 1% of all runs reporting a broken fragment, which in fact is working. I would not mind false-negatives too much. So I'd say, let's stay conservative and not report an error if we're uncertain. As for the flags, I'd vote for --include-fragments or --exclude-fragements, as this is the naming scheme for other inclusions/exclusions right now and follows the principle of least surprise. Whether we want to differentiate between e.g. --include-md-fragments and --include-html-fragments can be answered later. Ideally, I'd prefer a single option, but if one check is much more robust than the other, it might merit a separate flag.

Which method(s) of generating fragments from markdown should we implement? Should we support multiple? If so, how do we expose these options to the user?

I'd keep it simple for now. We can always add another option later to specify the detection algorithm, e.g. --fragment-generation kebap-case.

If we want to provide a simple interface with only one generation approach, I think we should either use heading attributes and fall back to unique kebab case when not present, or use both unique kebab case and heading attributes (when present).

Yes, fully agree. A combination of heading attributes and unique kebab case would work. We can use the examples from the Gitlab docs for our tests.

i think checking html files should be higher priority because majority of the time it'll be case 4, though im not sure how we'd do this, we'd probably need to parse the html and check for <hn> tags
i agree this should be opt-in because many websites dont support anchors, or they use anchors differently
another, possibly less efficient approach, would be to compare the response with and without the anchor to see if they're the same, this'd definitely be opt-in
this though isn't enough for websites/browsers that use anchors to scroll, which many of them do so i think that'd require users to provide a browser api, then we'd check if it scrolled with the anchor or not

i think checking html files should be higher priority because majority of the time it'll be case 4

Yes, websites without a file extension are indeed a common use-case.

though im not sure how we'd do this, we'd probably need to parse the html and check for <hn> tags

We already parse HTML, and we have access to all tags, thanks to html5ever and html5gum, so fetching the <hn> won't be an issue.

i agree this should be opt-in because many websites dont support anchors, or they use anchors differently

AFAIK, anchors are mainly a browser feature. They are not even sent to the website and are only handled client-side. You can confirm that by sending a request with an anchor tag to any website; it will be stripped out before the request.
Compare the URL in the address bar with the URL in the network tab:

JavaScript might also handle anchors, as they have access to the address bar. This is mainly used for dynamic websites I guess.
No browser API is needed, as it's enough to know that the anchor exists on the website that the browser tries to render. We don't have to emulate the actual rendering. Just the anchor id generation.
There's a chance I misunderstood your point.

i meant that for mainly spas or ssr, some websites use anchors kind of like paths or queries, for example example.com#anchor is like example.com/anchor i think this is dome to keep state of what "page" the user is in, so they can show that on reload or going back etc
these sites are a minority tho so we could skip over this if its too much work (probably is)

Ah, you got it. Thanks for the explanation. Yes, SPAs will be tricky for now. We might not be able to check these. Let's start with the simple use-case of static / server side rendered pages, which will already be a great step forward.

I was wrong about GitLab and GitHub using the same fragment generation. I've created some test cases to compare common forges:

Heading
Forgejo
GitHub
GitLab

# Repeated Heading
repeated-heading
repeated-heading
repeated-heading

## This header has a :thumbsup: in it
this-header-has-a-thumbsup-in-it
this-header-has-a-thumbsup-in-it
this-header-has-a-thumbsup-in-it

# header with 한글 characters (using unicode)
header-with-한글-characters-using-unicode
header-with-한글-characters-using-unicode
header-with-한글-characters-using-unicode

### Repeated Heading
repeated-heading-1
repeated-heading-1
repeated-heading-1

## Repeated Heading
repeated-heading-2
repeated-heading-2
repeated-heading-2

## Underscores foo_bar_, dots . and numbers 1.7e-3
underscores-foo_bar_-dots-and-numbers-1-7e-3
underscores-foo_bar_-dots--and-numbers-17e-3
underscores-foo_bar_-dots-and-numbers-17e-3

## Many          spaces
many-spaces
many----------spaces
many-spaces

NB: GitLab doesn't appear to follow it's own GitLab flavoured markdown documentation.  Specifically, it doesn't actually collapse shortcodes and 1.7 doesn't become 1-7 but 17.
The major difference appears to be that GitLab and Forgejo both collapse all non alphanumeric characters into a single dash whereas GitHub converts whitespace characters to dashes and ignores all others. However, GitLab appears to ignore the . in 1.7e-3 like GitHub whereas Forgejo doesn't.
mdBook seems to follow GitHub's fragment generation. I suggest we do the same as it is the most popular forge. The option remains to additional generators in the config in the future.

Perfect. Great analysis!
Maybe you want to start a new crate (anchorfy?) which allows you to create the fragment from different flavors?
assert_eq!(anchorfy::Github("## Many          spaces"), "many----------spaces".to_string());
assert_eq!(anchorfy::Gitlab("## Many          spaces"), "many-spaces".to_string());

For now, GitHub/mdbook would be enough.

how would we handle these outside of the popular sites? should we provide a way for the user to configure this (probably the same way we pre-configure these websites)?

I'd assume >90% of all Markdown files we check are on GitHub. If we make it configurable, we should keep it simple. Maybe we just introduce a --fragment-format option at some point, which accepts github, gitlab, etc. as an argument. For the initial version, let's go with GitHub and wait for feature requests. Otherwise, the PR becomes too big. What do you think?

thats fair enough but another major use case would be linking to documentation, for example swagger
i think we should design the header format used in an independent way so that in the future we can let others set it easier

Sorry, I don't quite get it. If we find a fragment link in a document, we have to check if that fragment exists. Say we find "#helloworld" and there is a headline named "Hello World", for which a fragment was generated automatically by the hoster (GitHub, GitLab, Swagger (?)). Now the question is if that headline gets converted into "#helloworld" or "#hello-world" or something else. How can we design the header format in such a case? Don't we have to generate the same fragment link as the hoster?
It's likely I might be missing something here.

Don't we have to generate the same fragment link as the hoster

yes thats what i mean, the exact implementation would need a balance between verbosity and conciseness but for example something like
[ { " ": "-" } ]

this would replace   in the content with - in the header, transforming hello world to hello-world, we'd likely need more configuration like escaping, casing, handling duplicates and so on

Ah, I understand now. Not sure how to find the right balance between simplicity and flexibility here. Open for suggestions for the configuration format.

we could use toml, i believe it supports arbitrary keys as string ("abc" = "xyz") which could be used for replacing characters
we could take an "enum" (not sure toml supports them) for casing, options i can think of are camel case, snake case, kebab case, pascal case and macro case

should we provide a way for the user to configure this (probably the same way we pre-configure these websites)?

I'm personally not keen on this idea.
In an ideal world, fragment generation would be specified in the common mark spec, but it isn't and there are a few different common methods. I don't want to encourage xkcd № 927, especially if it involves adding significant complexity to the tool and configuration.
I think hard coding the common generation methods in lychee (or in a separate crate) would help clearly document existing generation methods and hopefully help reduce, stop or even reverse their proliferation.

https://github.com/lycheeverse/lychee/pull/1198 has been merged, so of the link types laid out in https://github.com/lycheeverse/lychee/issues/185#issuecomment-1613580697 Lychee now supports types 1 and 2.

Awesome progress! 🚀
Here's our current architecture after the changes:

Supporting fragments in URLs (e.g. https://foo/bar.html#frag as in option 3 in the link types) won't be a small change, I guess.
We'd probably have to make few changes to the architecture, because right now there's no way for the check step to "ask" for all links of a given input or even just ask if a link occurs in a given input (e.g. "is https://foo/bar.html#frag valid?").
One way to go about it might be to fully decouple input handling from link checking (where inputs can be files or websites).
The fragment cache is a basic version of that, but it's limited to fragments. I think we need a bigger cache for all inputs we encounter and a central entity, which manages this cache. We can think of it as an abstraction on top of the network and the file system, purpose-built for our use-case.
It could lazy-load resources on demand and store the parsed information from inputs, which would be used by the rest of the system; so our parsed representation would be the ground-truth for the rest of the link checking. For each input, it would contain a big map of the URI of the input (i.e. the path or URL) and its parsed links/fragments.
It should be fully async, and we will need read/write access throughout the program's runtime.
Maybe this is even a graph problem, but I don't feel comfortable going down that route.
In any case, we will need a lot of discussions to come up with a solid design.
However we model it, a check to see if an input contains a link or fragment should be trivial from other parts of the program. We should not deal with ad-hoc resource-fetching within the checking code.
@HU90m, any thoughts on this? Maybe I'm overcomplicating things.

That sounds like a splendid plan.
A simplified view of the current flow could be illustrated as:

I think an elegant implementation of this idea would be to remove the collector and move the extractors into the Client. The inputs are converted directly to Requests, with the only transformation being the de-globbing of globs. These initial requests will be given a depth of 0, depth being a new member of Request:
pub struct Request {
    /// A valid Uniform Resource Identifier of a given endpoint, which can be
    /// checked with lychee
    pub uri: Uri,

    /// The resource which contained the given URI
    pub source: InputSource,

    // ...

    /// Depth of the link,
    /// where a depth of 0 is a link provided in the user input.
    pub depth: u32,
}

When the client handles a request it will fetch the file (form the file system or network). If successfully fetched, It will then parse the file extracting links and optionally fragments, if the file isn't in it's cache. After which, the file will be added to a cache in the client along with it's links and fragments. The extracted links will be converted to Requests with a depth of their origin file plus one, and be put back into the request channel to be handled later.
There will be max_depth option that defaults to 1. If a request's depth is greater or equal to max_depth, it's extracted links won't be put back into the request channel.
This gives us recursive checks for free, when max_depth >= 1! Another advantage is the possibility of combining the fragment and link extractors so that files are only parsed once.
A simplistic illustration of the above:

As it is possible for Client to produce more requests than it consumes, we should probably use mpsc::unbounded_channel.

Also I enjoyed the lychee talk, props!

Also I enjoyed the lychee talk, props!

Thanks for watching and glad you liked it.
Should we move the architecture discussion into a separate issue?

Should we move the architecture discussion into a separate issue?

Let's!

Done. ✌

Anchor support has landed now.
Future improvements can be discussed in new issues and the architecture discussion at https://github.com/lycheeverse/lychee/issues/1252.


Icon Change: StyleLint

Change Icon of StyleLint
StyleLint currently has a pure black icon which isn't visible on the default UI color scheme.

I recommend swapping it to a white version.
Attached here is a white png at 32x32, but white on white is invisible:
-->  <--
<svg width="40" height="39" viewBox="0 0 40 39">
  <g fill="#fff">
    <path d="M20.272 38.16c4.375-15.642 4.248-15.713 7.41-26.866l.76.44c.414.237.752.042.752-.434V5.98c.84-2.938 1.496-5.21 1.69-5.89h3.425L40 5.36l-3.738 3.23 2.827 3.057L20.46 38.16c-.09.15-.217.116-.188 0z"/>
    <path d="M22.307 4.444c.17 0 .306.093.306.21V7.38c0 .113-.137.206-.306.206h-4.6c-.17 0-.307-.093-.307-.208V4.652c0-.115.137-.21.306-.21h4.6zm5.68-3.018l-5.062 2.922c.<IP_ADDRESS>.094.305V7.38c0 .14-.058.268-.148.37l5.113 2.952c.348.202.634.037.634-.365V1.792c0-.403-.285-.567-.634-.366zM16.993 7.38V4.652c0-.112.036-.215.094-.304l-5.062-2.924c-.348-.2-.634-.036-.634.366v8.545c0 .402.288.567.637.365l5.112-2.952c-.09-.103-.145-.23-.145-.37z"/>
    <path d="M19.54 38.16h.188c-4.374-15.642-4.248-15.713-7.41-26.866l-.76.44c-.413.237-.752.042-.752-.434V5.98C9.966 3.043 9.31.77 9.116.09H5.692L0 5.36l3.737 3.23L.91 11.648 19.54 38.16z"/>
    <ellipse cx="19.861" cy="11.897" rx="1.382" ry="1.382"/>
    <ellipse cx="19.861" cy="20.112" rx="1.382" ry="1.382"/>
    <ellipse cx="19.861" cy="28.329" rx="1.382" ry="1.382"/>
  </g>
</svg>

svg is great!

@robertohuertasm Is there something good to know when dealing with svgs? Can I put them in the icons folder as usual?

Yes, you can put them there. The problem is that the build process is still not ready. I'll have to modify it in order to mark svg somehow.
There's still a huge refactoring pending in the project because there are some things that are not really used anymore but are still there for people who use VSCode < 1.6.0.
I was willing to introduce these modifications with the next VSCode release but maybe we can move forward.

Let's use the png for this release. We have 3 icons to support along this one. I will start the svg feature next.


Tasks 261-300: update categories, domains and addressing feedbacks

Signing off on addressing human feedback.

The remaining changes are done. You can merge if you are happy with the tasks.


Group px width gets converted to percentages

Noticed when I use a mj-group component and specify a pixel width, the output class is a calculated percentage instead of the provided pixel width.

Hi @adambullmer
I remember why we've done this. Mobile width could be anywhere from 300 to 480px, so set column in px could behave not as intended depending on the device. That's why we're using percentage width in column only to make it fluid
Does it make sense to you ?

Yes and no. I saw where the group would be more responsive as a percentage. Maybe there's a better option than overriding the default. I unfortunately need a fixed width grouping container, and would love to write it all in mjml rather than opening a raw tag and doing it with tables manually. Maybe there could be an override like a fixed-width option for users who are aware of the implications.

On a side note, to me it feels like specifying pixels is not intended to be a responsive pattern in the first place, and feels like buggy or unexpected behavior. Might want to mention that caveat in the docs.
It's mostly the discussion we had  when implementing mj-group. To be fair you can still use new css-class attribute and inline the width with mj-style.  So it doesn't introduce some unclear behaviour to mj-group and anyone can still use a pixel width for group.

Does it seems an ok approach for you ?

Yeah, that seems fair. What version will that css-class attribute be available? I see it on the website, but the latest non-master mjml renderer engine says it's not a valid property. (also tried pairing the mj-class property with the attribute and didn't have any luck with that either)
But, if I understood correctly I should get the desired result like this?
<mjml>
<mj-head>
  <mj-attributes>
    <mj-class name="fixed-width" width="400px" />
  </mj-attributes>
</mj-head>
<mj-body>
  <mj-container>
    <mj-section>
      <mj-group width="400px" css-class="fixed-width">
        <mj-column>
          <mj-text>Column 1</mj-text>
        </mj-column>
        <mj-column>
          <mj-text>Column 2</mj-text>
        </mj-column>
      </mj-group>
    </mj-section>
  </mj-container>
</mj-body>
</mjml>

MJML.io doc is updated to 3.3.3 but it's not released yet. You can try this solution on beta 3.3.3-beta3
Not mj-class doesn't work like that : it only apply attributes on defined mj-element.

so then a mj-style with a free form class, and then the css-class attribute on the element?

I'm closing this issue, feel free to use css-class to bypass the behaviour but we won't let px width in mj-group.

@iRyusa could you guys please update documentation here then?
https://mjml.io/documentation/#mjml-group

Column inside a group must have a width in percentage, not in pixel

This is noticed in the doc already

I think it does say px in the table below that
On 30 Jun 2017 21:55, "Maxime Brazeilles"<EMAIL_ADDRESS>wrote:

Column inside a group must have a width in percentage, not in pixel
This is noticed in the doc already
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mjmlio/mjml/issues/641#issuecomment-312359399, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AKxLOPJf7ab_TMYAPL6LdyNCG_OYmq23ks5sJVK9gaJpZM4M9WFp
.

Well px are supported but converted as percent to ensure mobile view isn't broken might add a notice then nice catch @dalefish @FoxWhite


Issues with Models with complex arguments

Trying to create a simple MZI circuit with where I can give complex parameters to each coupler. For example:
def coupler(S31=1/jnp.sqrt(2), S41=1j/jnp.sqrt(2)) -> sax.SDict:
    coupler_dict = sax.reciprocal(
        {
            ("in0", "out0"): S31,
            ("in0", "out1"): S41,
            ("in1", "out0"): S41,
            ("in1", "out1"): S31,
        }
    )
    return coupler_dict
def MZI_arms(phase_top = 0., phase_bottom = 0) -> sax.SDict:
    _sdict = sax.reciprocal(
        {
            ("in0", "out0"): jnp.exp(1j*phase_top),
            ("in1", "out1"): jnp.exp(1j*phase_bottom),
        }
    )
    return _sdict
mzi, info = sax.circuit(
    netlist={
        "instances": {
            "BS1": "coupler",
            "PS1": "phase_shifter",
            "BS2": "coupler",
            "PS2": "phase_shifter",
        },
        "connections": {
            "BS1,out0": "PS1,in0",
            "BS1,out1": "PS1,in1",
            "PS1,out0": "BS2,in0",
            "PS1,out1": "BS2,in1",
            "BS2,out0": "PS2,in0",
            "BS2,out1": "PS2,in1",
        },
        "ports": {
            "in0": "BS1,in0",
            "in1": "BS1,in1",
            "out0": "PS2,out0",
            "out1": "PS2,out1",
        },
    },
    models={
        "coupler": coupler,
        "phase_shifter": MZI_arms,
    }
)

This returns a warning for me as follows:
[.../lib/python3.11/site-packages/jax/_src/numpy/lax_numpy.py:2089]: ComplexWarning: Casting complex values to real discards the imaginary part
  out_array: Array = lax_internal._convert_element_type(

Is that an issue? I am not sure I should trust the final result...

Hi @thomaslima, thanks for the bug report. This issue will be fixed in sax>=0.10.4.

Awesome. Wasn’t sure if it was a bug. Thanks!
On Wed, Nov 29, 2023 at 11:59 Floris Laporte @.***>
wrote:

Hi @thomaslima https://github.com/thomaslima, thanks for the bug
report. This issue will be fixed in sax>=0.10.4.
—
Reply to this email directly, view it on GitHub
https://github.com/flaport/sax/issues/28#issuecomment-1832338737, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIJZE5ZUQ5HLNOMALNBZTDYG5SYLAVCNFSM6AAAAAA76L2QGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZSGMZTQNZTG4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Fix TeachingTip title and sub title not being initially collapsed.

Set Title and Subtitle TextBlocks visibility to collapsed in OnApplyTemplate if they are empty. Add a test.

/azp run

What about #3397? They both address the same underlying issues.

ugh, I didn't realize you had already solved this issue... This is a great example of why our current PR state is so bad

I like your PR better, specifically using VSM to set the visibility.

ugh, I didn't realize you had already solved this issue... This is a great example of why our current PR state is so bad

Once all open PRs have been merged, I think this won't be an issue anymore.


lib/tsserver.js and typescript/lib/typingsInstaller.js lurk around

I have recently enabled logging of processes in our CI and I have a log for after our integration tests:
https://gist.github.com/bpasero/3de5e01bd32f57c845253af07e19d27a
From https://dev.azure.com/monacotools/Monaco/_build/results?buildId=165478&view=logs&j=963754b8-394e-5caf-de5d-2790b068caec&t=79e950e2-ae58-5fea-a241-0229f56d23a3
Notice these:
/__w/1/vscode-reh-web-linux-x64/node --max-old-space-size=3072 /__w/1/vscode-reh-web-linux-x64/extensions/node_modules/typescript/lib/tsserver.js --useInferredProjectPerProjectRoot --disableAutomaticTypingAcquisition --enableTelemetry --cancellationPipeName /tmp/vscode-typescript1000/8ef3a9a595f292584b78/tscancellation-3d884c073fbecb888c67.tmp* --locale en-US --noGetErrOnBackgroundUpdate --validateDefaultNpmLocation --useNodeIpc

and
/__w/1/vscode-reh-web-linux-x64/node /__w/1/s/extensions/node_modules/typescript/lib/typingsInstaller.js --globalTypingsCacheLocation /home/builduser/.cache/typescript/4.6 --enableTelemetry --typesMapLocation /__w/1/s/extensions/node_modules/typescript/lib/typesMap.json --validateDefaultNpmLocation

It seems the automated typings acquisition is getting orphaned and still runs.
As a bandaid I had tried to disable automated typings aquisition via setting, e.g.:
https://github.com/microsoft/vscode/blob/8e8b3026fcdbdd4855dcfa3c96e24d1058779aea/extensions/vscode-api-tests/testWorkspace/.vscode/settings.json#L10
And this seems to be passed to TS (via disableAutomaticTypingAcquisition) but does not seem to help.
Not sure this is an extension problem in TS or in the extension host. My feeling is:

we kill the main process
the extension host has no more parent
extension host self terminates
TS extension does not check for parent process to go away

I've pushed a change to deactivate extensions after tests are run, so it should now be possible to for extensions to better clean up.

Looks like that was the root problem and that the processes are gone in https://dev.azure.com/monacotools/Monaco/_build/results?buildId=165758&view=logs&jobId=963754b8-394e-5caf-de5d-2790b068caec&j=963754b8-394e-5caf-de5d-2790b068caec&t=79e950e2-ae58-5fea-a241-0229f56d23a3

@alexdima thank you 💯


Can't upload test results if they have more than 65,535 characters

I got this error from the dotnet-tests-report action as run here:
Invoke-WebRequest: D:\a\_actions\zyborg\dotnet-tests-report\v1.3.0\action.ps1:144
Line |
 144 |      Invoke-WebRequest -Headers $hdr $url -Method Post -Body ($bdy | C …
     |      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | {"message":"Invalid request.\n\nOnly 65535 characters are allowed; 93137 were
     | supplied.","documentation_url":"https://docs.github.com/rest/reference/checks#create-a-check-run"}

There's got to be some other way to present the test results...

Yep, you can see the details in #9.

Yep, you can see the details in #9.


Pokemons

All the Pokemons from Japanese Manga Series!

Looks good, Please do one thing create a demo folder inside "Pokemons" and add a gif of your project named demo.gif

Ok i will do it! Thanks Irshad
On Sun, Oct 2, 2022, 7:26 PM Md Irshad @.***> wrote:

Looks good, Please do one thing create a demo folder inside "Pokemons" and
add a gif of your project named demo.gif
—
Reply to this email directly, view it on GitHub
https://github.com/irshadmd/Awesome-CSS-Projects/pull/17#issuecomment-1264656612,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY45DHRNFFCXXPKIUEXUX63WBGLRNANCNFSM6AAAAAAQ244XLM
.
You are receiving this because you authored the thread.Message ID:
@.***>

@GeekkyCoder please add demo.gif

sure i almost forget it! sorry for that
On Wed, Oct 5, 2022, 4:13 PM Md Irshad @.***> wrote:

@GeekkyCoder https://github.com/GeekkyCoder please add demo.gif
—
Reply to this email directly, view it on GitHub
https://github.com/irshadmd/Awesome-CSS-Projects/pull/17#issuecomment-1268292577,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY45DHWVTIB6EDCPH55W7MLWBVPHLANCNFSM6AAAAAAQ244XLM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Request for Benchmark Datasets used in MotionDirector

Hi,
Thank you for your insightful work and this repository.
I was wondering if you plan to release the benchmarks proposed in the paper?
Thanks!

Hi. The inference videos used in the paper include two resources. For the customization on multiple videos, we use the UCF Sports Action data set. For the customization on a single video, we use the benchmark released by the LOVEU-TGVE competition at CVPR 2023.

Hi. The inference videos used in the paper come from two resources. For the customization on multiple videos, we use the UCF Sports Action data set. For the customization on a single video, we use the benchmark released by the LOVEU-TGVE competition at CVPR 2023.

Could you please give me the prompt of ucf and the 3 additional prompts you used in loveu2023?


Is this still maintained?

Hello,
Sorry for the ping and my scepticism, but is this project still maintained?
Most recent commit is almost one year ago and documentation seems to be at barebones, half cooked.
I'm using it at work and I'm very pleased, but I'm worried about long term support.
Regards

Sure I am, this has the potential to save me hours of work and tooling. Just let me know how

Cool - getting a work plan organized this end will give you a shout back early next week!


Waybar doesn't detect active workspace

I have Waybar version 0.9.24 and hyprland 0.40.0 for Asahi Linux Fedora Remix.
Everything worked fine, but after I updated packages via dnf update workspace detection has broken
Also this is what waybar outputs when launching from Terminal
(waybar:7644): Gtk-WARNING **: 15:51:28.856: Theme parsing error: gtk.css:6616:68: Invalid name of pseudo-class
[2024-05-07 15:51:28.878] [info] Using configuration file /home/andrey/.config/waybar/config
[2024-05-07 15:51:28.878] [info] Including resource file: ~/.config/waybar/modules
[2024-05-07 15:51:28.882] [info] Discovered appearance 'dark'
[2024-05-07 15:51:28.882] [info] Using CSS file /home/andrey/.config/waybar/style.css
[2024-05-07 15:51:28.888] [warning] Failed to open bar ipc connection: Socket path is empty
[2024-05-07 15:51:28.888] [warning] Mapping is not an object
[2024-05-07 15:51:28.888] [info] Hyprland IPC starting
[2024-05-07 15:51:28.888] [error] Hyprland IPC: Couldn't connect to /tmp/hypr/cba1ade848feac44b2eda677503900639581c3f4_1715085219_541070725/.socket.sock. (3)
[2024-05-07 15:51:28.888] [error] Hyprland IPC: Couldn't connect to /tmp/hypr/cba1ade848feac44b2eda677503900639581c3f4_1715085219_541070725/.socket.sock. (3)
[2024-05-07 15:51:28.888] [error] Monitor 'eDP-1' does not have an ID? Using 0
[2024-05-07 15:51:28.888] [error] Hyprland IPC: Unable to connect?
[2024-05-07 15:51:28.888] [error] Hyprland IPC: Couldn't connect to /tmp/hypr/cba1ade848feac44b2eda677503900639581c3f4_1715085219_541070725/.socket.sock. (3)
[2024-05-07 15:51:28.888] [error] Hyprland IPC: Couldn't connect to /tmp/hypr/cba1ade848feac44b2eda677503900639581c3f4_1715085219_541070725/.socket.sock. (3)
[2024-05-07 15:51:28.888] [error] Hyprland IPC: Couldn't connect to /tmp/hypr/cba1ade848feac44b2eda677503900639581c3f4_1715085219_541070725/.socket.sock. (3)
[2024-05-07 15:51:28.902] [error] Hyprland IPC: Couldn't connect to /tmp/hypr/cba1ade848feac44b2eda677503900639581c3f4_1715085219_541070725/.socket.sock. (3)
P.S. Sorry for my bad English

Also need to mention is that my disto is just Fedora 39 for MacBook's

ln -s $XDG_RUNTIME_DIR/hypr /tmp/hypr
This command helped me

Why did you close the issue? Creating a symlink is a workaround, the problem still exists and needs to be fixed, exactly because Hyprland has moved the location of its socket.

Why did you close the issue? Creating a symlink is a workaround, the problem still exists and needs to be fixed, exactly because Hyprland has moved the location of its socket.

Because the issue did get fixed, there was a release with the change 3 days ago, in 0.10.3

Why did you close the issue? Creating a symlink is a workaround, the problem still exists and needs to be fixed, exactly because Hyprland has moved the location of its socket.

I've installed waybar-git instead of waybar and everything began to work again

Installing waybar-git hasn't solved this for me.
Workspaces below
workspace = 2, persistent:true,monitor:eDP-1
workspace = 3, persistent:true,monitor:eDP-1
workspace = 4, persistent:true,monitor:eDP-1
workspace = 5, persistent:true,monitor:eDP-1```


Fix: Install udev rules

Udev Rules usually installed with setup-usb.sh of tar.gz
Without, camera will not be recognized in Ubuntu stock install

Thank you for providing this PR. LGTM, will be merged soon.


Why select text then type, append to value but not remplace ?

1 - I write : "Paris, Fra"
2 - I select all the text "Paris, Fra"
3 - I write : "London"
4 - It gives me : "Paris, FraLondon"

Excepted
1 - I write : "Paris, Fra"
2 - I select all the text "Paris, Fra"
3 - I write : "London"
4 - Removes "Paris, Fra"
5 - It gives me : "London"
Thanks!

Closed with 1be2036f45961b82bf55cd874209748bd6217296 👍


[v2.9] Add ability to specify a service account for a node pool in a GKE cluster

The gke-operator (in v2.9) now supports the ability to specify a service account for a node pool. This is an optional field that may be set to an email address of a service account that has limited permissions, for example<EMAIL_ADDRESS>To set this field, one needs to set the value for field .spec.nodePools[*].config.serviceAccount. If not set, the default service account will be used.
There is currently no API method that lists the service accounts for a project, that the UI could invoke to help the user pick a service account. Adding such an API is possible but it would require additional permissions for the GKE service account that Rancher uses, i.e. to include the roles/iam.serviceAccountViewer IAM role.
Relates to https://github.com/rancher/gke-operator/issues/262

Will transfer this to dashboard repo for better UI tracking since I don't see direct backend work here.


Grid: "Current Column | Sort | Custom..." should open the "Order or Hide Columns" dialog

Fixed in v0.149


Deprecated selector in gcc-make-run\node_modules\atom-space-pen-views\stylesheets\select-list.less

In gcc-make-run\node_modules\atom-space-pen-views\stylesheets\select-list.less:
Starting from Atom v1.13.0, the contents of atom-text-editor elements are no longer encapsulated within a shadow DOM boundary. This means you should stop using :host and ::shadow pseudo-selectors, and prepend all your syntax selectors with syntax--. To prevent breakage with existing style sheets, Atom will automatically upgrade the following selectors:

.cursor, atom-text-editor::shadow .cursor, atom-text-editor .gutter .line-number, atom-text-editor .line => .cursor, atom-text-editor.editor .cursor, atom-text-editor .gutter .line-number, atom-text-editor .line

Automatic translation of selectors will be removed in a few release cycles to minimize startup time. Please, make sure to upgrade the above selectors as soon as possible.
I'm getting this warning.

Atom is gone.


Add sample_rate to transactions and tracestate

What does this pull request do?
Adds the sample_rate to transactions, and propagates the sample_rate through tracestate
Related issues
Closes #888

:broken_heart: Tests Failed

Expand to view the summary

Build stats

Build Cause: [Pull request #891 opened]

Start Time: 2020-07-21T16:41:01.081+0000

Duration: 23 min 55 sec

Test stats :test_tube:

Test
Results

Failed
5

Passed
10659

Skipped
7698

Total
18362

Test errors
Expand to view the tests failures

Name: Initializing / Test / Python-python-3.7-4 / test_transaction_with_eventlet – tests.contrib.test_eventlet

Age: 1
Duration: 10.033
Error Details: assert 0 == 1   -0   +1

Name: Initializing / Test / Python-python-3.9-rc-4 / test_transaction_with_eventlet – tests.contrib.test_eventlet

Age: 1
Duration: 10.034
Error Details: assert 0 == 1   -0   +1

Name: Initializing / Test / Python-python-3.8-0 / test_transaction_with_eventlet – tests.contrib.test_eventlet

Age: 1
Duration: 10.028
Error Details: assert 0 == 1   -0   +1

Name: Initializing / Test / Python-python-3.6-2 / test_transaction_with_eventlet – tests.contrib.test_eventlet

Age: 1
Duration: 10.03
Error Details: assert 0 == 1   -0   +1

Name: Initializing / Test / Python-pypy-3-1 / test_transaction_with_eventlet – tests.contrib.test_eventlet

Age: 1
Duration: 10.521
Error Details: assert 0 == 1   -0   +1

Steps errors
Expand to view the steps failures

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.6 eventlet-newest

Duration: 0 min 27 sec

Start Time: 2020-07-21T16:55:14.775+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.6 eventlet-newest

Duration: 0 min 26 sec

Start Time: 2020-07-21T16:56:20.812+0000

log

Name: Error signal

Description: Python-python-3.6-eventlet-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-07-21T16:56:47.018+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.7 eventlet-newest

Duration: 0 min 28 sec

Start Time: 2020-07-21T16:52:55.396+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.7 eventlet-newest

Duration: 0 min 27 sec

Start Time: 2020-07-21T16:53:42.611+0000

log

Name: Error signal

Description: Python-python-3.7-eventlet-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-07-21T16:54:10.221+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.8 eventlet-newest

Duration: 0 min 27 sec

Start Time: 2020-07-21T16:54:33.444+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.8 eventlet-newest

Duration: 0 min 27 sec

Start Time: 2020-07-21T16:55:18.295+0000

log

Name: Error signal

Description: Python-python-3.8-eventlet-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-07-21T16:55:45.827+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.9-rc eventlet-newest

Duration: 0 min 28 sec

Start Time: 2020-07-21T16:54:25.334+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh python-3.9-rc eventlet-newest

Duration: 0 min 28 sec

Start Time: 2020-07-21T16:55:15.322+0000

log

Name: Error signal

Description: Python-python-3.9-rc-eventlet-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-07-21T16:55:43.201+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 eventlet-newest

Duration: 1 min 16 sec

Start Time: 2020-07-21T16:59:30.210+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 eventlet-newest

Duration: 1 min 13 sec

Start Time: 2020-07-21T17:01:03.174+0000

log

Name: Error signal

Description: Python-pypy-3-eventlet-newest tests failed : hudson.AbortException: script returned exit code 2

Duration: 0 min 0 sec

Start Time: 2020-07-21T17:02:16.198+0000

log

Name: Shell Script

Description: ./tests/scripts/docker/run_tests.sh pypy-3 django-2.2

Duration: 4 min 14 sec

Start Time: 2020-07-21T16:48:23.170+0000

log

Name: Restore files previously stashed

Description: coverage-python-3.6-pymemcache-newest

Duration: 0 min 0 sec

Start Time: 2020-07-21T17:03:52.945+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-07-21T17:03:40.825Z] tests/instrumentation/redis_tests.py                         81     79      4      0     2%
[2020-07-21T17:03:40.825Z] tests/instrumentation/requests_tests.py                      92     90      0      0     2%
[2020-07-21T17:03:40.825Z] tests/instrumentation/sqlite_tests.py                        83     77      4      0     7%
[2020-07-21T17:03:40.825Z] tests/instrumentation/transactions_store_tests.py           251    211     22      0    15%
[2020-07-21T17:03:40.825Z] tests/instrumentation/urllib3_tests.py                      107     94      8      0    11%
[2020-07-21T17:03:40.825Z] tests/instrumentation/urllib_tests.py                       129    109      8      0    15%
[2020-07-21T17:03:40.825Z] tests/metrics/__init__.py                                     0      0      0      0   100%
[2020-07-21T17:03:40.825Z] tests/metrics/base_tests.py                                 107     90     16      0    14%
[2020-07-21T17:03:40.825Z] tests/metrics/breakdown_tests.py                            180    168     58      0     5%
[2020-07-21T17:03:40.825Z] tests/metrics/cpu_linux_tests.py                             56     43     10      0    20%
[2020-07-21T17:03:40.825Z] tests/metrics/cpu_psutil_tests.py                            27     22      4      0    16%
[2020-07-21T17:03:40.825Z] tests/middleware/__init__.py                                  0      0      0      0   100%
[2020-07-21T17:03:40.825Z] tests/middleware/tests.py                                    32     25      2      0    21%
[2020-07-21T17:03:40.825Z] tests/processors/__init__.py                                  0      0      0      0   100%
[2020-07-21T17:03:40.825Z] tests/processors/tests.py                                   145    111     12      0    22%
[2020-07-21T17:03:40.825Z] tests/transports/__init__.py                                  0      0      0      0   100%
[2020-07-21T17:03:40.825Z] tests/transports/test_base.py                               161    128     14      0    19%
[2020-07-21T17:03:40.825Z] tests/transports/test_urllib3.py                            201    164      8      0    18%
[2020-07-21T17:03:40.825Z] tests/utils/__init__.py                                       2      1      2      0    25%
[2020-07-21T17:03:40.825Z] tests/utils/cgroup_tests.py                                   7      3      0      0    57%
[2020-07-21T17:03:40.825Z] tests/utils/cloud_tests.py                                   30     21      0      0    30%
[2020-07-21T17:03:40.825Z] tests/utils/compat.py                                         4      3      2      0    17%
[2020-07-21T17:03:40.825Z] tests/utils/compat_tests.py                                  36     19      2      0    45%
[2020-07-21T17:03:40.825Z] tests/utils/encoding/__init__.py                              0      0      0      0   100%
[2020-07-21T17:03:40.825Z] tests/utils/encoding/tests.py                               124     99      8      0    19%
[2020-07-21T17:03:40.825Z] tests/utils/json_utils/__init__.py                            0      0      0      0   100%
[2020-07-21T17:03:40.825Z] tests/utils/json_utils/tests.py                              26     14      2      0    43%
[2020-07-21T17:03:40.825Z] tests/utils/stacks/__init__.py                               10      7      4      0    21%
[2020-07-21T17:03:40.825Z] tests/utils/stacks/tests.py                                 127    100     10      3    22%
[2020-07-21T17:03:40.825Z] tests/utils/test_disttracing_header.py                       55     42      0      0    24%
[2020-07-21T17:03:40.825Z] tests/utils/tests.py                                         69     45      2      0    34%
[2020-07-21T17:03:40.825Z] tests/utils/threading_tests.py                               37     31      2      0    15%
[2020-07-21T17:03:40.825Z] tests/utils/wsgi/__init__.py                                  0      0      0      0   100%
[2020-07-21T17:03:40.825Z] tests/utils/wsgi/tests.py                                    47     32      0      0    32%
[2020-07-21T17:03:40.825Z] -------------------------------------------------------------------------------------------
[2020-07-21T17:03:40.825Z] TOTAL                                                     10862   8095   1767    135    24%
[2020-07-21T17:03:40.825Z]
[2020-07-21T17:03:40.825Z] ============ 2 passed, 27 skipped, 463 deselected in 43.31 seconds =============
[2020-07-21T17:03:40.825Z] + cleanup
[2020-07-21T17:03:40.825Z] + '[' -n 1 ']'
[2020-07-21T17:03:40.825Z] + ./scripts/docker/docker-summary.sh
[2020-07-21T17:03:40.825Z] *******************************************************
[2020-07-21T17:03:40.825Z] ***************Docker Containers Summary***************
[2020-07-21T17:03:40.825Z] *******************************************************
[2020-07-21T17:03:40.825Z] CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
[2020-07-21T17:03:40.825Z] + PYTHON_VERSION=
[2020-07-21T17:03:40.825Z] + docker-compose down -v
[2020-07-21T17:03:40.825Z] Removing network tests_default
[2020-07-21T17:03:41.087Z] Removing volume tests_pypgdata
[2020-07-21T17:03:41.087Z] Removing volume tests_pymongodata30
[2020-07-21T17:03:41.087Z] Removing volume tests_pymongodata32
[2020-07-21T17:03:41.087Z] Removing volume tests_pymongodata34
[2020-07-21T17:03:41.087Z] Removing volume tests_pymongodata36
[2020-07-21T17:03:41.087Z] Removing volume tests_pyesdata7
[2020-07-21T17:03:41.087Z] Removing volume tests_pyesdata6
[2020-07-21T17:03:41.087Z] Removing volume tests_pyesdata5
[2020-07-21T17:03:41.087Z] Removing volume tests_pyesdata2
[2020-07-21T17:03:41.087Z] Removing volume tests_pycassandradata3
[2020-07-21T17:03:41.087Z] Removing volume tests_pymssqldata
[2020-07-21T17:03:41.087Z] Removing volume tests_mysqldata
[2020-07-21T17:03:41.087Z] + [[ -n '' ]]
[2020-07-21T17:03:41.234Z] Running in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-891/src/github.com/elastic/apm-agent-python
[2020-07-21T17:03:41.656Z] + chmod 755 docker-logs.sh
[2020-07-21T17:03:41.969Z] + ./docker-logs.sh Python-pypy-3-graphene-2 docker-compose.yml
[2020-07-21T17:03:42.004Z] Archiving artifacts
[2020-07-21T17:03:42.046Z] Recording test results
[2020-07-21T17:03:43.139Z] Stashed 1 file(s)
[2020-07-21T17:03:45.335Z] Post stage
[2020-07-21T17:03:45.647Z] + pip3 install --user coverage
[2020-07-21T17:03:47.039Z] Collecting coverage
[2020-07-21T17:03:47.609Z]   Downloading https://files.pythonhosted.org/packages/db/19/ad8f558e885a11a68111300ee23a632cc46a5ef6aaed875ba56460076fa7/coverage-5.2-cp36-cp36m-manylinux1_x86_64.whl (229kB)
[2020-07-21T17:03:47.609Z] Installing collected packages: coverage
[2020-07-21T17:03:47.609Z] Successfully installed coverage-5.2
[2020-07-21T17:03:47.898Z] Running in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-891/src/github.com/elastic/apm-agent-python
[2020-07-21T17:03:53.029Z] Error when executing always post condition:
[2020-07-21T17:03:53.030Z] hudson.AbortException: No such saved stash ‘coverage-python-3.6-pymemcache-newest’
[2020-07-21T17:03:53.030Z] 	at org.jenkinsci.plugins.workflow.flow.StashManager.unstash(StashManager.java:159)
[2020-07-21T17:03:53.030Z] 	at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:76)
[2020-07-21T17:03:53.030Z] 	at org.jenkinsci.plugins.workflow.support.steps.stash.UnstashStep$Execution.run(UnstashStep.java:63)
[2020-07-21T17:03:53.030Z] 	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
[2020-07-21T17:03:53.030Z] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[2020-07-21T17:03:53.030Z] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[2020-07-21T17:03:53.030Z] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[2020-07-21T17:03:53.030Z] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[2020-07-21T17:03:53.030Z] 	at java.lang.Thread.run(Thread.java:748)
[2020-07-21T17:03:53.030Z]
[2020-07-21T17:03:53.178Z] Stage "Building packages" skipped due to earlier failure(s)
[2020-07-21T17:03:53.276Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-07-21T17:03:53.376Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2020-07-21T17:03:53.600Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-07-21T17:03:53.642Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-07-21T17:03:53.742Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-07-21T17:03:53.841Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-07-21T17:03:55.103Z] Running on worker-1225339 in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-891
[2020-07-21T17:03:55.236Z] [INFO] getVaultSecret: Getting secrets
[2020-07-21T17:03:55.326Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-07-21T17:03:57.912Z] + chmod 755 generate-build-data.sh
[2020-07-21T17:03:57.912Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-891/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-891/runs/1 FAILURE 1374938
[2020-07-21T17:03:57.912Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-891/runs/1/steps/?limit=10000 -o steps-info.json
[2020-07-21T17:04:02.078Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-891/runs/1/tests/?status=FAILED -o tests-errors.json

This is code complete. Just need to add a few more tests (this is mostly a note to self since I'll be PTO for awhile):

Weight empty if incoming traceparent doesn't define it
Weight 0 for unsampled transaction
Weight present in transaction payload
Weight present in span payload

This will have to be rewritten for the new spec in https://github.com/elastic/apm/pull/307 once it is finalized.

This has been rewritten for the updated (finalized) spec and tests have been written as well. It's ready for review.

A change to the spec is in review and this should wait to be merged until it's finalized. (Though I've already implemented the minimum value requirement, which is really the only change to my implementation so far.)
https://github.com/elastic/apm/pull/335


Add events that interrupt service page

Based on work from: https://www.pivotaltracker.com/story/show/154128739

Thanks @mfine30!


dosc: use proper name in docstring

Codecov Report

Merging #32 (932f29a) into master (682c377) will increase coverage by 100.00%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           master       #32        +/-   ##
=============================================
+ Coverage        0   100.00%   +100.00%
=============================================
  Files           0         9         +9
  Lines           0       367       +367
  Branches        0        68        +68
=============================================
+ Hits            0       367       +367

Impacted Files
Coverage Δ

solutions/adv_2022_08.py
100.00% <0.00%> (ø)

solutions/adv_2022_04.py
100.00% <0.00%> (ø)

solutions/adv_2022_06.py
100.00% <0.00%> (ø)

solutions/adv_2022_03.py
100.00% <0.00%> (ø)

solutions/adv_2022_01.py
100.00% <0.00%> (ø)

solutions/adv_2022_00.py
100.00% <0.00%> (ø)

solutions/adv_2022_05.py
100.00% <0.00%> (ø)

solutions/adv_2022_07.py
100.00% <0.00%> (ø)

solutions/adv_2022_02.py
100.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Change State Name "quantity" to allow specific name for that state

Because the name of quantity states defaults to "quantity" instead of allowing a specific name, it is not possible to have two quantity states listed under a single character. The second entry is rejected because the State "quantity" already exists for that Character. This will become a problem for at least two of the upcoming schemas that include characters such as stomatal dimensions which will include quantities length, width, area, perimeter, etc. Is this a difficult fix that has to be shifted to V2 or is this not such a difficult fix?

It is not a difficult fix and does not need to wait to V2, but has to wait until pbot dev work resumes in winter.

I think @NoisyFlowers had a cogent workaround for this but that wasn't recorded in the issue. I'll try to find it later.

The proper way to handle the scenario described is to have a stateless super-character "stomatal dimensions" with separate sub-characters for "stomatal length", "stomatal width", etc.


Update Prime.py

I think that since we have to check prime numbers in a big range so optimizing the code should be priority else it would take hours to check for some very big value of "number"

Hello, this repository was created for Hacktoberfest 2020 and is no longer active.


Load only required chunks

Hi,
I have multiple entries in webpack. so i would like to download only required chunks.
chunkExtractor.getScriptTags();

will always return all of the chunks even these i dont need and are useless for current page.
i am not sure if i am doing something wrong or is it limitation of this library?
implementation looks like this:
entry part of webpack
{
    entry: {
        main: "./src/index.tsx",
        home: "./src/components/home/HomeContainer",
        productDetail: "./src/components/products/ProductDetailContainer",
        productList: "./src/components/products/ProductListContainer",
   }
}

server side
const chunkExtractor = new ChunkExtractor({
  stats,
  entryPoint: ['main', 'home', 'productDetail', 'productList'],
});

const app = chunkExtractor.collectChunks(RenderApp(req.url, store));
const scriptsHtml = chunkExtractor.getScriptTags({ async: true });
const appHtml = await renderToStringAsync(app);

componenet with these entries
const LazyHome = lazy(() => import('src/components/home/HomeContainer'), { chunkName: 'home' });
const LazyProductDetail = lazy(() => import('src/components/products/ProductDetailContainer'), { chunkName: 'productDetail' });
const LazyProductList = lazy(() => import('src/components/products/ProductListContainer'), { chunkName: 'productList' });

export const RouteApp = withRouter((props) => {
  return (
    <Route
      path={Routes.HOMEPAGE}
      render={(props) => (
        <React.Suspense fallback={null}>
        <App {...props}>
          <Switch>
              <Route
                exact
                path={Routes.HOMEPAGE}
                component={LazyHome}
              />
              <Route
                exact
                path={Routes.PRODUCT_DETAIL_WITH_PARAMS}
                component={LazyProductDetail}
              />
              <Route
                path={Routes.PRODUCT_LIST_WITH_PARAMS}
                component={LazyProductList}
              />

            {/* <Route path="*" component={LoadableConnectedNotFoundContainer} /> */}
          </Switch>
        </App>
        </React.Suspense>
      )}
    />
  );
});

Hi.
entryPoint option for new ChunkExtractor() should should just be 'main'. Or omit it entirely, as that's the default anyway.
Then the chunkExtractor will only get the chunks actually required for the page. Adding other items to the entryPoint is telling it you want all those chunks included. So that's why you got them!
Also, you shouldn't need to include home, productDetail or productList in Webpack config entry - Webpack will see you are using import() to load these and understand it needs to make them each into individual chunks automatically.
Hope that helps...


Cldc 1102 admin organisations page

ACs:
When I log in as a customer support person:

[x] Instead of "Your organisation" I see "Organisations" in the navigation bar

[x] When I click "Organisations" I see a list of all organisation names/links in the system using the design from the prototype https://core-beta-prototype.herokuapp.com/organisations

[x] The page should have the same pagination functionality as the logs page

[x] When I click the name/link to an organisation I see the logs page for that organisation (filtered), and have "About this organisation" as a sub navigation bar item. When I click "About this organisation" I see the organisation edit page and can edit details

When I log in as a different user type and try to visit the Organisation list page:

[x] I get a page not found response

This will need rebasing on main

Is there a ticket to add a "Create Organisation" button for support users?

@baarkerlounger not that I know of. Was not in the Acs for this one either tho


MAINT: fix mypy errors after adding py.typed marker

Reference issue
None
What does this implement/fix?
Adding the py.typed marker caused mypy to realize that all of our
extension modules exist, which changed the errors we were getting from
"missing import" to "x attribute in the module does not exist"
(because it has no stubs). Shuffle the ignores in the ratchet to
account for that.
Also update runtests.py to support the --no-build flag, since you
can now run mypy against an installed SciPy.
Additional information
None

@tylerjereddy this fixed things for me; LMK if it clears things up for you too.

Grr, actually now it works for me using
python setup.py install
./runtests.py --mypy --no-build

but fails doing it the other way... I will keep working on it tomorrow, sorry all.

We reverted the marker (and I never could get this to work under all circumstances), so closing this. Can revisit later if needed.


extremely long delays even after patched mainHack.ns

Im still seeing day-long delay times on grow(), even after the merged patch. I had a single playthrough where things seemed to delay properly, but its never happened again and I am at a loss to explain why it would work once and never again. I've gone over the code but I guess I still don't understand why this var
const growDelay = Math.max(0, weakenTime - growTime - 15 * 1000)
subtracts the grow time from the weaken time? Shouldn't this simply be the weakenTime plus a few ms? Similarly, what is the point of subtracting hacktime from the hackDelay var?
Making these changes in my own mainHack.ns completely fixed the timing issues for me. I admit I only took a cursory scan of the code, so if someone has a deeper understanding of the game mechanics please do correct me.

It aims to make the Grow/Hack calls end just before weaken (by sleeping the difference between the timings before any grow operation starts)
EX:
Weaken = 2 minutes
Grow = 1 minute
(weakentime-grow= 45 seconds)
so when it runs cycles, it runs weaken, then the grow starts 45 seconds later (so it ends 15 seconds before weaken does)
One thing to check: the initHacking.ns script will re-download and overwrite mainHack.ns if you run it.


GestureDetector's onScaleUpdate does not differentiate between horizontal and vertical scaling on Windows

Steps to Reproduce

Execute flutter run on the code sample (on a Windows Laptop)
Start a zooming gesture. Make sure you zoom horizontally more then vertically.
Have a look at the logs.

Expected results: horizontalScale should be different then verticalScale
Actual results: horizontalScale and verticalScale are the same
This seems to be only a problem on Windows devices (touchscreen and trackpad). On my android phone it works as expected.

Code sample

(Copied from https://github.com/flutter/flutter/issues/59247#issuecomment-748072672)
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      theme: ThemeData.dark(),
      home: const Home(),
    );
  }
}

class Home extends StatelessWidget {
  const Home({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('Material App Bar'),
      ),
      body: Center(
        child: GestureDetector(
          onScaleUpdate: (val) {
            print(val);
          },
          child: Image.network('https://i.imgur.com/QCNbOAo.png'),
        ),
      ),
      floatingActionButton: FloatingActionButton(
        child: const Icon(Icons.add),
        onPressed: () {},
      ),
    );
  }
}

Logs

flutter: ScaleUpdateDetails(focalPoint: Offset(-205.5, -103.5), localFocalPoint: Offset(-525.5, -169.2), scale: 2.409745216369629, horizontalScale: 2.409745216369629, verticalScale: 2.409745216369629, rotation: 0.0, pointerCount: 1, focalPointDelta: Offset(-4.3, -2.2))
flutter: ScaleUpdateDetails(focalPoint: Offset(-208.5, -104.9), localFocalPoint: Offset(-528.5, -170.7), scale: 2.4155378341674805, horizontalScale: 2.4155378341674805, verticalScale: 2.4155378341674805, rotation: 0.0, pointerCount: 1, focalPointDelta: Offset(-3.0, -1.5))
flutter: ScaleUpdateDetails(focalPoint: Offset(-212.8, -107.1), localFocalPoint: Offset(-532.8, -172.9), scale: 2.424056053161621, horizontalScale: 2.424056053161621, verticalScale: 2.424056053161621, rotation: 0.0, pointerCount: 1, focalPointDelta: Offset(-4.3, -2.2))
flutter: ScaleUpdateDetails(focalPoint: Offset(-218.6, -110.0), localFocalPoint: Offset(-538.6, -175.7), scale: 2.4353017807006836, horizontalScale: 2.4353017807006836, verticalScale: 2.4353017807006836, rotation: 0.0, pointerCount: 1, focalPointDelta: Offset(-5.7, -2.9))
flutter: ScaleUpdateDetails(focalPoint: Offset(-222.9, -112.1), localFocalPoint: Offset(-542.9, -177.9), scale: 2.4438209533691406, horizontalScale: 2.4438209533691406, verticalScale: 2.4438209533691406, rotation: 0.0, pointerCount: 1, focalPointDelta: Offset(-4.3, -2.2))
flutter: ScaleUpdateDetails(focalPoint: Offset(-223.0, -112.0), localFocalPoint: Offset(-543.0, -177.8), scale: 2.4438209533691406, horizontalScale: 2.4438209533691406, verticalScale: 2.4438209533691406, rotation: 0.0, pointerCount: 1, focalPointDelta: Offset(-0.1, 0.1))

Analyzing example...

   info - Avoid `print` calls in production code - lib\main.dart:97:13 -
          avoid_print

1 issue found. (ran in 2.9s)

[√] Flutter (Channel stable, 3.3.10, on Microsoft Windows [Version
    10.0.22621.1105], locale de-DE)
    • Flutter version 3.3.10 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (5 weeks ago), 2022-12-15 07:36:55
      -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[√] Android toolchain - develop for Android devices (Android SDK version
    33.0.1)
    • Android SDK at C:\Users\Maximilian\AppData\Local\Android\sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build
      11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Build Tools 2022
    17.4.3)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual
      Studio\2022\BuildTools
    • Visual Studio Build Tools 2022 version 17.4.33205.214
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2021.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      11.0.13+0-b1751.21-8125866)

[√] VS Code (version 1.74.3)
    • VS Code at C:\Users\Maximilian\AppData\Local\Programs\Microsoft VS
      Code
    • Flutter extension version 3.56.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows
      [Version 10.0.22621.1105]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome
      109.0.5414.75
    • Edge (web)        • edge    • web-javascript • Microsoft Edge
      108.0.1462.54

[√] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Windows APIs do not return horizontal and vertical zoom separately (at least for trackpad). Not sure why you are also seeing this on the touchscreen though.

Windows APIs do not return horizontal and vertical zoom separately

Oh, I thought this would be calculated by flutter. Do you know if there is any way, I could get the vertical/horizontal scale manually.
I think it would be good, if this behavior would be documented as semi intentional in the dart docs.

Not sure why you are also seeing this on the touchscreen though.

My bad, it works for the touchscreen. It seems like I didn't look close enough.

It depends on your device, it might be possible to write some Windows code to get the exact touch points on the trackpad. But there is no generic way to do that for all Windows laptops. Windows trackpad support in Flutter is done using the Direct Manipulation API, which gives its data as a 3x2 matrix. That can only represent translation, scaling, and rotating, but not any sort of stretching. So Windows tells us already what the zoom is on the trackpad, Flutter has no way at any level to know the exact touch locations in order to generate more information.
It's a good idea to add a caveat on horizontalScale and verticalScale that they won't be differentiated on trackpads.

Based on above comment, I am going ahead and labeling this as a documentation issue.

I ended up using the ctrl key to switch between vertical and horizontal zooming in my application.

This also happens with macOS trackpad (see recently open and closed, #132846).

Blocked by this on MacOS as well, does anyone know a workaround in order to identify a "vertical trackpad scale" / "horizontal trackpad scale" ?
Thanks

macOS does not have an easy way to get these values. I someone could write some custom code in the flutter engine to compute them based on finger positions in the trackpad.
What's the use case?

@moffatman I am evaluating two_dimensional_scrollables and have a large table
I want to be able to "scale it vertically" a.k.a only the height of the rows increases proportionally to vertical scale
I also want to be able to "scale it horizontally" a.k.a only the width of the columns increases proportionally to horizontal scale

Ok it's interesting, not sure I ever saw an app with that style. Well you'll have to learn or find someone who can modify flutter engine to support this.


Implement opentelementry integration with SigNoz

This PR is a POC for integrating with the SigNoz observability system https://signoz.io, which is an open-source alternative to Datadog.
The express app in the PR sends performance trace data about:

Express routes
Express middleware
Any function in the source code that ends with _trace. This excludes node_modules

The app also tries to recover using express-async-errors, and sends exception data to SigNoz when one occurs. Source maps are used to retain the original lines in the source code in the exception stack trace.
Open in Gitpod

Would be great to have the relevant git commit in both the traces and errors reported

Would be good to get client-side tracing error reporting going
Working on trpc integration. Will also want to do this for json rpc
Also need to provide details in the trace attributes about the application's current deployment environment. dev, prod, server1, server2 etc.
And add logging with winston
And set up alert to go off for "new error found" https://chatgpt.com/c/eee8908c-0538-4918-aa33-8c7a930b0661

Make it so tailscale only exposes a particular port for sending data for the server sending data. I can read it from my machines though. Make it so remote deployment server can only access send port https://www.reddit.com/r/Tailscale/s/pHiZ3esART


Cannot input PIN on setup: async_pin_needed

When I try  the first setup and the TV is turned on. The integration requires a PIN code from the TV. The TV shows the PIN, however the integration doesn't provide a way to input the pin. would it need to be put into a config file?
Logs
022-05-01 18:08:53 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user INFO None
2022-05-01 18:10:43 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user NOT task_mqtt
2022-05-01 18:10:43 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _async_pin_needed

Which HA version do you use? Can you provide screenshots of the config flow?
You should be able to enter the PIN during the config flow. It's only needed one time, so it's not stored in any config afterwards.

Versions:
Host Operating System | Home Assistant OS 7.6
Supervisor Version | supervisor-2022.05.0
Home Assistant Core: 2022.5.2
Mosquitto broker mosquitto.conf:
onnection hisense
address <IP_ADDRESS>:36669
username hisenseservice
password  multimqttservice
clientid HomeAssistant
bridge_tls_version tlsv1.2
bridge_cafile /share/mosquitto/hisense_ca.pem
bridge_certfile /share/mosquitto/hisense_client.pem
bridge_keyfile /share/mosquitto/hisense_client.key
bridge_insecure true
start_type automatic
try_private true
topic /remoteapp/# both 0 hisense ""

sounds like https://github.com/sehaas/ha_hisense_tv/issues/24#issuecomment-1094059067

I have the same problem as @de68guard. I have also tried different browser but can't the pin field on HA.

My guess is, that it's a timing issue. I published a new version with more debug logging.
You can change the log level for just one component like:
logger:
  default: info
  logs:
    custom_components.hisense_tv: debug

Okay thanks.
I've added this to my Config.yaml, how to get this config_flow Logs?

Hi
Thanks for pointing to https://github.com/sehaas/ha_hisense_tv/issues/24#issuecomment-1094059067, I did notice that issue before and tested in firefox and Chromium (both in linux), but as suggested I have also tested the same in Chrome and Edge (now in Windows 10) with the same results.
I must be missing something basic
logger already as suggested
logger:
default: info
logs:
custom_components.hisense_tv: debug
Logs the following messages:
2022-05-11 14:23:22 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user INFO None
2022-05-11 14:23:47 INFO (Thread-3) [homeassistant.components.mqtt] Connected to MQTT server core-mosquitto:1883 (0)
2022-05-11 14:24:13 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user NOT task_mqtt
2022-05-11 14:24:14 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _async_pin_needed
I have success with https://github.com/newAM/hisensetv:
python3.8 -m pip install hisensetv
hisensetv <IP_ADDRESS> --authorize
Please enter the 4-digit code: 7815
Also I have good responses with MQTT-explorer directly to TV with the same certs and over the Bridge in Hass.
My next test would be try use HACS that I have not used before.
Thanks

Please use version 22.05.09, your log output is from an older version.
Your MQTT setup should be OK, as your TV does display the PIN. I suspect the problem during the HA config flow and async calls.

Thanks
forgot to deploy the new downloaded version:
Logs
2022-05-11 18:02:46 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user - user_input is None
2022-05-11 18:03:45 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user - set task_mqtt
2022-05-11 18:03:45 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _check_authentication - publish gettvstate
2022-05-11 18:03:45 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _check_authentication - publish sourcelist
2022-05-11 18:03:45 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _async_pin_needed
2022-05-11 18:03:45 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] _unsubscribe
2022-05-11 18:03:45 DEBUG (MainThread) [custom_components.hisense_tv.config_flow] async_step_user - task_auth is False

Thanks for the logs. Right after your last entry, the config flow would call the next step return self.async_show_progress_done(next_step_id="auth"). But it looks like async_step_auth is never called.
Unfortunately it always works for me, so I can't reproduce/debug your behaviour.
These API calls are provided by HA and I don't know where to start looking for the problem.

Thanks for the logs. Right after your last entry, the config flow would call the next step return self.async_show_progress_done(next_step_id="auth"). But it looks like async_step_auth is never called. Unfortunately it always works for me, so I can't reproduce/debug your behaviour. These API calls are provided by HA and I don't know where to start looking for the problem.

Thanks for the help so far, I have been trying a couple of debug attempts including trace the Mosquitto bridge, I cann see the issue is in the HA API that try to follow after self.async_show_progress_done but no luck
I would try install a mosquitto bridge in a VM and use it instead of the addon docker,
if the same issue maybe can I authorise with the python from https://github.com/newAM/hisensetv?
Last I would try reinstall everything in a dedicated HASS instance.

@sehaas Much appreciated, finally it works.
I had to use a newer device (laptop) running Chrome (my lab devices are all a bit old).
I try to many things and was focusing in the HASS  instance using the clue of timing issues from https://community.home-assistant.io/t/hisense-tv-control/97638/253, but at the end it was my devices were to old (timing maybe).

The newer devices that worked both are Windows, one W10 and the other W11, and both are Windows11 capable, maybe that is the clue, I haven't played further.


ELBV2 - Fix elbv2 modify_rule expects Conditions (#4677)

Fixes #4677

Codecov Report

Merging #4681 (a88bb9d) into master (3d10536) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4681   +/-   ##
=======================================
  Coverage   95.26%   95.26%
=======================================
  Files         550      550
  Lines       60752    60754    +2
=======================================
+ Hits        57877    57879    +2
  Misses       2875     2875

Flag
Coverage Δ

servertests
47.81% <0.00%> (+<0.01%)
:arrow_up:

test_responses
32.46% <0.00%> (-0.01%)
:arrow_down:

unittests
95.18% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

moto/elbv2/responses.py
94.02% <100.00%> (ø)

moto/sns/models.py
96.65% <0.00%> (+0.01%)
:arrow_up:

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 3d10536...a88bb9d. Read the comment docs.


"Chunky" feel (fps drop) when inspector first enabled on Windows

@cpr2323 sent me a video displaying fps drops on Windows with https://github.com/cpr2323/A8Manager as the target app. The frame rate drops only after the initial open, not after toggle off/on
See also: #62

It looks like the difference is:

on initial open, the root component is selected and keyboard focused
on toggle off then on, the root component is no longer selected

so it's some issue with the root selection, probably component snapshotting


Doesn't revalidate a cart revalidate it for all customers?

Looking through the code and have a question around revalidateTag(TAGS.cart). Since the same tag is used for all carts, won't that revalidate all carts? Shouldn't the tag also include cart id or something to narrow it down to that specific customers cart to avoid more fetches than needed?

Exactly my thoughts.

The cart operation is sent with the header, cache: 'no-store', so unless I'm missing something, nothing in the cart is cached, so there is nothing to revalidate and you would never do revalidation on a cart. You just call the functions again to get a new cart etc. The cookie with the cartId is sent in the request.
As an aside, I wouldn't do Cart operations on the server, like this repo does, but that's another discussion.

The fetch to retrieve the latest cart items always grabs the most up-to-date data, using no-store. However, when doing a mutation (like adding to cart), you still want to call revalidateTag to clear the entire Next.js router cache, so you'll see the updated cart values when navigating between pages. If you were to reload the page, you would go back to the fresh fetch with no-store to get the latest cart data. But you're right, we could make the cache tag even more specific if we wanted to!

hi @leerob , thanks for the answer! In your example, you opted not to cache the cart data by using ‘no-store’ with the fetch function, but you still applied the tag to enable route cache revalidation. I’m curious if there’s a way to achieve similar functionality using unstable_cache. Specifically, is it possible to mark or tag the function call without actually caching the data?
Additionally, when utilizing a custom cache handler, such as the one provided here, my understanding is that even if the data is not cached, calling revalidateTag from a server action will still trigger the revalidateTag function of this custom cache handler. Is that correct?

According to this doc:

In a Server Action:
Revalidating data on-demand by path with (revalidatePath) or by cache tag with (revalidateTag)
Using cookies.set or cookies.delete invalidates the Router Cache to prevent routes that use cookies from becoming stale (e.g. authentication).

Here is the workaround I am using:
// serverHelper.ts
import "server-only";

export const revalidateRouteCache = () => {
  cookies().delete("random");
};

// action.ts
"use server"
export async function addItem(...) {
  ...
  // revalidateTag(TAGS.cart);
  revalidateRouteCache();
}


Select on iPad not functional

Current Behavior
When loading a page with a  on iPad browser, the first press, the select shows up, but selecting an item is not functional. Subsequent presses do not open the select.
Expected Behavior
No response
Tamagui Version
Latest

Reproduction
https://tamagui.dev/docs/components/select/1.0.0

Fails on both a physical iPad and the latest iPad simulator. Fails on both demo and other sites.

System Info
No response

https://user-images.githubusercontent.com/39423472/232855585-1efd69bb-701e-489d-8f1c-ac4f206f19fc.mp4

issue can also be reproduced in chrome by showing the device toolbar and setting dimensions to ipad.

Use  to a sheet for all "touch" platforms instead of just adapting by size as a workaround.


CURL not timing out, wrapper stuck 'indefinitely'

Currently having an issue where there is a connection made to the API, but the API is very slow (Been loading for a few minutes). This in turn block the whole website.
I suggest adding the following to the curl function
curl_setopt($ch, CURLOPT_CONNECTTIMEOUT ,0);
curl_setopt($ch, CURLOPT_TIMEOUT, 10);
So that if after 10 second in total CURL will stop. 10 seconds should be long enough for this API.

Created a fork and made it 8 second. Will see how it goes once the API is fully operating again.

Hello! We did have some minor API availability issues the last couple of days, but we believe that to be resolved now. Are you still experiencing this issue consistently?

Addressed in #78


First batch of Django 1.8 compatibility

Fix #517

Coverage increased (+0.14%) to 68.83% when pulling 171e69245dee3657e9e43da7ef63190ec5e4d659 on nephila:feature/django18 into 7b0bf6a6be4dd8a3267ee7624f55e1ce6d22493e on stefanfoulis:develop.

Coverage increased (+0.14%) to 68.83% when pulling 171e69245dee3657e9e43da7ef63190ec5e4d659 on nephila:feature/django18 into 7b0bf6a6be4dd8a3267ee7624f55e1ce6d22493e on stefanfoulis:develop.

Coverage increased (+0.14%) to 68.83% when pulling 171e69245dee3657e9e43da7ef63190ec5e4d659 on nephila:feature/django18 into 7b0bf6a6be4dd8a3267ee7624f55e1ce6d22493e on stefanfoulis:develop.

Coverage increased (+0.14%) to 68.83% when pulling 171e69245dee3657e9e43da7ef63190ec5e4d659 on nephila:feature/django18 into 7b0bf6a6be4dd8a3267ee7624f55e1ce6d22493e on stefanfoulis:develop.

Coverage increased (+0.14%) to 68.83% when pulling 2d2068ff99f1992c3aae1ee6e8aa7746a12d02c2 on nephila:feature/django18 into 7b0bf6a6be4dd8a3267ee7624f55e1ce6d22493e on stefanfoulis:develop.

Coverage increased (+0.14%) to 68.83% when pulling 2d2068ff99f1992c3aae1ee6e8aa7746a12d02c2 on nephila:feature/django18 into 7b0bf6a6be4dd8a3267ee7624f55e1ce6d22493e on stefanfoulis:develop.


feat: dim sun icon

Preview

I also kind-of don't look like sun either 😅

What is the use case for this icon? The most common reason for the sun to be "dim" is when there are clouds in front of it, and there is already an icon for that.

yeah well I get the use case but would it be really useful?

Every icon can have it's uses, someway or other 🤷

How about something like this?

How about something like this?

OMG! That's a good one.
//cc @ericfennis

@karsa-mistmere @mittalyashu I think this looks even better!

I think there's maybe even space for multiple dim levels (I've just checked and iOS uses the same concept for its brightness level indicator icon).

I don't have access to the PR code, so here's a Figma file: https://www.figma.com/file/iRBudsI3NG79KtEODp1V5Z/lucide%2Fbrightness-dim-(%23545)?node-id=0%3A1

brightness-full breaks guidelines, but everything else is great :0

brightness-full breaks guidelines, but everything else is great :0

Yeah, at that point due to some other icons I'd been under the impression that this particular guideline could be broken on a case by case basis. Let's scratch full and stick with medium and low (and potentially night light).

yeah all the icons that break this rule are basically from the feather icon set and need to be refactored

yeah all the icons that break this rule are basically from the feather icon set and need to be refactored

Yeah, I've been on it this last week. 😁

@ericfennis just added now 🙂