Remove eksa controller build

Issue #, if available:
Description of changes:
We moved the cluster controller build to the CLI repo so this PR removes the unnecessary controller build code.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: taneyland
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [taneyland]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danbudris, taneyland
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [danbudris,taneyland]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

is it really Abhay? Or A-Bot-hay?


Add gettext annotations to most text

This commit greatly increases our gettext coverage to include:

all paragraphs on the index page
almost all short text, including auth
most page titles

Generally, what's left are our long document pages (about pages,
proofing helping pages) and some of our JavaScript.
Test plan: unit tests. I also created a dummy language and set all
text to ___ to visually confirm that most text had been captured.

Landing since it's been 24h


Is an item's url required or optional?

The spec says:

url (optional, string) is the URL of the resource described by the item. It’s the permalink. This may be the same as the id — but should be present regardless.

Given the phrase "should be present regardless," is the url actually required? Or am I misreading something?

The only reason url isn't technically required is because you might have offline feeds that don't necessarily point to a place on the web. For any normal feed for a blog or other web site, url should be there. The "regardless" just means that if id is a URL, it's not enough by itself; you also want url to have the same value. (In other words, clients shouldn't assume that id is a URL or be required to treat it as one.)

I see. Maybe rephrase to something like "This may be the same as the id, but even if it is, it should still be present"?

i am wondering: since JSON feed claims to be JSON-ified atom, what's the corresponding atom element here? it would be great to actually link the atom elements from the spec, as long as there is a strictly corresponding atom element.

I think the Atom comparison is mostly covered in the "mapping RSS and Atom" document: https://jsonfeed.org/mappingrssandatom


Inverse diffing direction in diffstat

This way, the additions from one version to next appear in green, as expected.

Thanks. Like I said elsewhere, I think this isn't a new thing with your recent PR, but I really find the new order here to be much more sensible. So I'm happy to make the change.

Thanks. Like I said elsewhere, I think this isn't a new thing with your recent PR, but I really find the new order here to be much more sensible. So I'm happy to make the change.


SQL results are not typecast to strings anymore

Checklist

[x] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[x] PR title is ready for changelog and subsystem label(s) applied

All result data was typecast to strings in mariasql. There were some places where the code assumed that was true, which was changed with the switch to mariadb.
This fixes #2724 and a similar bug in api subscriptions.

Closing issues
closes #2724

epic thanks @rocketeerbkw


Add highlight and typo-tolerance to the search

Hello,
Thanks for building react-parts, this is a really useful tool for me. I think the search results can still be improved, by adding highlight on the matching words and auto-fixing typos (among other things).
I took the liberty of forking the code and replace the json-based search with one using Algolia (which is a SaaS search engine, with the above features built-in). Full disclosure: I work at Algolia. Here is what it looks like:

You can test it live here (this is hosted on an heroku free plan, so first load might be slow).
Tell me if this is something you would be interested in. If so, I'll submit a PR. We're used to giving custom and free accounts to open-source projects as a way of contributing back, so this won't cost you anything. I did those changes a few weeks ago so I did not (yet) include the latest changes to the UI you did, but I'll happily merge them back.
Looking forward to hear from you, and see if we can build something together.

Hello @pixelastic,
First of all thank you for using react.parts and for taking the time to contribute. I would also like to thank Algolia for supporting open source projects :+1: Although I don't find myself needing the counters or the highlighting, the fuzzy matching is definitely a big improvement.
My only concern right now is that we only deploy whenever we add new features. The data files are simply uploaded via scp to the servers. Can you show us your fork to understand how you're doing the indexing? Thank you again for your contribution!

Sure thing.
The code responsible for pushing data to the index is here : https://github.com/algolia/react-parts/blob/feature/algolia-search/algolia.js
It basically reads the ./components/react-web.json and ./components/react-native-ios.json json files and push its content to the Algolia indices (pushing all ranking-relative settings with it). To keep your search index in sync, you'll have to re-run this script everytime you update the list of plugins (I guess this will replace the scp command).
(Don't pay attention to the multiple commits in the repo, I'll rebase/squash that properly later).

I personally like what i see in the PR. I hadn't tried Algolia in the past, but it seems pretty sweet, specially the part of not having to worry about maintaining an ElasticSearch / Solr instance, and the API is indeed friendly. :+1:

Hey again @pixelastic,
First of all, I'm sorry you had to do all those fixes to fetch.js. I did them too a long time ago but only consolidated and pushed them recently.
I like how the details related to the Algolia API are isolated in a single file. One thing I didn't understand in the new algolia.js script is that you push the components/react-*.json files instead of the data/react-*.json ones (that contain the metadata, such as stars).
Another thing I noticed (probably an easy fix) is with the pagination: Try to visit /web and go to "Next page". Now refresh the page. The results are not the same. One thing I usually do to make sure our server-side pagination works the same way as the client is to disable JavaScript in the browser.
To clarify why we have both the components and data files, I'm writing a readme with information about our current process (and also about our deployment strategy).
Thank you again! We really appreciate you taking the time to make React.parts better :+1:

I must confess I did not completely understood the difference between the components and data directories, so I might have copy-pasted the consolidated files (with metadata) inside the components directory and used that.
The fixes I did to the fetch.js file were mostly due to my account using two factor-authentication. In the end I disabled the 2FA before running the script and re-enabled it after :). If you did fix it on upstream I'll use your fixed version instead.
I'm glad you find this useful. I'll fix the issue you mentioned and squash/rebase all that soon. Thanks for making React.parts in the first place :)
If you want to see how it will look like from your Algolia dashboard, just create a free account and I'll give you ownership on the indices.

Thank you, we'll create an Algolia account later today :+1:
I hope the new readme will clarify why we keep the two separate folders. Your experience also reminded me that we should explain there how one can create a "Personal Access Token" in GitHub and use it as the username (with a blank password) to be granted limited read access.
We would love if you could send a simple PR with only the script and search functionality. The new release as a narrower footer, but we can add the Algolia logo to it with a link right after your PR, if you prefer. We can also add the highlighting, counters and visual changes afterwords. Let me know if that works for you!

That's perfect, I'll work on the fix/merge right now.

Until the readme is published, could help me with the order of the npm run commands?
Here is what I did:
npm run download:all
npm run parse
cp ./components/react-native.json ./data
cp ./components/react-web.json ./data
npm run fetch react-native
npm run fetch react-web

I tried the npm run fetch:all commands, but they did nothing, or complained that no json file were found in ./data. Am I on the right track here?

Generating the data/react-*.json files using the components/react-*.json files should be possible by running npm run fetch:all. But I just checked, and you are right, there is an issue if the files don't exist yet. Until the issue is fixed, you can:

Download react-web.json to data/react-web.json and react-native.json to data/react-native.json
Create empty json files with [] named data/react-web.json and data/react-native.json and then run npm run fetch:all

I'm sorry you are having this problem, and thanks for reporting it!

No problem, I figured this out. Thanks

Hello @pixelastic, our free Algolia account is associated to this address<EMAIL_ADDRESS>There's now a readme.md in the master branch and the bug you reported yesterday should also be fixed. Hope this helps!

@dmfrancisco Great, I've upgraded your account to a free one with unlimited operations. Thanks for the readme, it will make things clearer for other contributors.

This is awesome, and it comes at a good time because we really needeed a solution that scales for more than 2k components.
I'll update the publish script to run algolia and add the logo to the footer. I'm still not a fan of the highlighting. I find it too distracting and think it may be a little confusing when a record doesn't have any highlights (when what gets matched is a keyword). I also would prefer if the pagination started at 1 instead of 0. But I can make those minor changes myself.
So if you don't mind @pixelastic, I fetched and pushed your feature branch and will make those changes instead of merging the PR directly. We'll keep this PR open for now and will notify you as soon we deploy. Does that work for you?

Sure, feel free to tweak it as much as you'd like.
Regarding the highlight, maybe something acting directly on the text color instead of the background?

The highlight is interesting to give the user instant feedback on what he's searching, and letting him adjust his query while typing. Maybe it will become more useful when the dataset will grow. In the end, I'll let you test it and do what you think is best :)
If you could just add a link to our website on the Algolia logo that would be awesome. Keep me informed when this will be deployed :)

Everything seems to be working smoothly! I made some changes to the script, in order to have an index sorted by modified, to be used for the initial unfiltered list. Algolia's slave indices feature is really cool. I also added a dev index to allow us to experiment without affecting the production data.
You can check Algolia's logo here: https://new.react.parts
Again, thanks for making this possible :+1:
We'll make this available to the community within the next couple of days.

Happy to see that you started playing with it! Also, thanks for the logo, that's perfect.
Just a note though, be careful with your ranking formula. I saw that you moved the custom criterion in the second position. This criterion can only ever be the last of the list (meaning that all others -words, proximity, attribute and exact) will never be used. I think that is too aggressive and might not yield the most relevant results.

exact is used for the typotolerance, this will rank results with no typos higher than the one with typos
attribute will use the list of attributesToIndex you defined, giving more weight to the one on top. This lets you rank results with a match in name higher than the one with a match in author for example
words is used for multiple word queries: results that match several words will be ranked higher than those that only match one
proximity is used on multiple word queries as well. When searching for audio player, results that have audio player exactly will be ranked higher than the one that have audio foo bar bar foo player.

Disabling all those criteria will significantly impact the relevance of the search. I'd recommend reverting to the default (which is the good choice in 90% of cases). What was the use-case you were trying to solve? I'd be happy to help you with the configuration

Hey @pixelastic! Thank you for looking at the changes. I haven't made a lot of testing yet, but it seemed to me that the default ranking was not giving enough relevance to the stars. In theory it seems to me that:

Exact matches must be ranked higher than partial matches
We should give relevance to stars and downloads
The number of occurrences of a word or position (eg: in one record calendar appears 3 times in description and keywords but in another record only appears once) is less relevant (in my opinion, usually not relevant at all, and that's the main difference compared to searching text in other sites)

So after trying it out a little bit it seemed that:

Putting custom_ranking first was a bad idea (eg: Searching for "card" shows react-native-carousel at first because it has more stars). This meant the default typos as first is preferable
Putting custom_ranking second did better results, with matches with fewer typos on top sorted by stars and downloads

Here are some examples, left is default and right is with custom_ranking as second place:

Oh, I see. Thanks for the screenshots, this makes understanding the issue much easier.
We handle the exact criterion a bit differently when you have only one word in the query. In that case, if a record contains an attribute that is (or an array that contains) exactly what is typed, then this record is ranked higher. In your example, you have all the records that contains video in keywords ranked first (exact match, ordered by stars), then all the one that did not get an exact match (because video was found in the name or description`), also ordered by star.
To fix that, you can either remove the exact criterion from your ranking formula. I would not recommend it, this will negatively impact the relevance in other use-cases. Instead, we have an undocumented attribute that you can pass to your request to disable the exact criterion when there is only one word.
Just add to the searchConfig in get-search-results.js (don't forget to revert your ranking formula to the defaults if you do that):
var searchConfig = {
  [...]
  useQueryEqualsOneAttributeInRanking: 0
};

This should get you the same results as in your screenshots.

Thank you @pixelastic, that makes sense :+1: I just pushed this change.
One last thing: I've noticed that the search API fetches at most 1000 hits, which is more than enough for searches. However, when the user is not searching, she should have access to the entire catalog. I tried to use the browse method, but a cursor must be passed, which means if a user comes from an url (eg: /web?page=60) this wouldn't work. Since this is a fairly uncommon use-case, and the data doesn't weight that much, I ended up doing a browseAll and then slicing the data on the client (or node server) on those cases. But let me know if you have any suggestion.
And that's it, thank you again! We'll deploy this weekend :tada:

Sorry I was a bit late to answer that one. As you said, the search method is limited to 1000 records, because that's enough for a search response. Nobody will skim through 1000 records manually if they have a search available to narrow down their terms. On the other hand, the browse method is here to let you navigate in your index (maybe for backup, stats, etc).
I think the solution you came up with is the right one. Your index is not that big, and I don't see why someone would request the 60th page anyway, so you're pretty safe.

Thank you for your response!
Regarding the Algolia JS Client, I may have missed something, but it was not obvious when I read the docs that the page param would only work in the browse method (not browseAll) for the first 1000 records. The example also uses content.nbPages which seemed to always be undefined. The docs make it seem that the options and response are the same as the search method, but they don't seem to be (above the 1000 records). Let me know if I should open an issue!

Oh, thanks. I'll rewrite the documentation to make that more obvious then.

Hello again @pixelastic! We've been working a new project that has a more robust backend and that supersedes React.parts. It has been online for 2 weeks but only yesterday we open sourced the code.
Is Algolia still interested in sponsoring this new project? We would love to use your search engine! If you don't mind, we would reuse this account you gave us.

Sure thing. As long as it stays non-profit and you keep our logo somewhere, we're ok :)
Good luck with the new project, and don't hesitate if you need any help.

Sure :smiley: Thank you Tim!


document scale (width only) is different after read & write

Hi!
Faced with a very strange issue:
When I read the document and write it back as a new file without any changes width of columns became different.
Input:

output:

here is input file
tov.xlsx

it seems that height also changed.
Probably related to Dpi parsing.
@guyonroche could you please take a look at this issue? It's quite critical for me.
What currently I found:

In output document lost properties:pageSetup.fitToPage
useFirstPageNumber

in both (input output) parsed documents data set to default horizontalDpi:<PHONE_NUMBER>, verticalDpi:<PHONE_NUMBER>,

this is kind of "dirty hack", to prevent such issues
seems that wrong units used
workbook.eachSheet(function(worksheet, sheetId) {
                worksheet._columns.forEach((cl) => { cl.width = cl.width/2*1.3148148148148149; } );
              });

https://github.com/exceljs/exceljs/pull/854

This bug still existed, the column's width seems to be auto resized to the width of it's content.
However, this hack works good.

this is kind of "dirty hack", to prevent such issues seems that wrong units used
workbook.eachSheet(function(worksheet, sheetId) {
                worksheet._columns.forEach((cl) => { cl.width = cl.width/2*1.3148148148148149; } );
              });


New information about maintenance and support. Updated information about Unity support.

Description
Added information and links about maintenance and support for major versions.
Also updated the information about Unity support due to V3.5 changes and to fix a broken link to the Unity archive repo.
Motivation and Context

We needed to provide maintenance and support information.
The Unity information and links were out of date. See GitHub issue https://github.com/aws/aws-sdk-net/issues/1684.

Testing

All text was spellchecked and grammar checked.
All links were tested.

Screenshots (if appropriate)
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project
[x] My change requires a change to the documentation
[x] I have updated the documentation accordingly
[x] I have read the README document
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

License

[x] I confirm that this pull request can be released under the Apache 2 license

This PR has been merged into the latest release of the SDK


Send TLS alerts when intercepted connection is going to be closed

Now connection is silently closed, but we may send TLS record with TLS alert (fatal internal_error / warning close_notify)

#208 done instead

Reopening, because some TLS clients doesn't work well with TCP reset.

core/pull-requests/423


Log4j config

Description
Add the ability to configure log4j settings for each host.  Specifically, defaulted to rolling log file appender, with the ability to set the number of log files to keep, the size of each log file, and the name and path they should be written under.
Fixes # (issue)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Test Configuration:
Have tested on both RHEL 7.x and Ubuntu 18.04.  Full cluster deployment with logging settings adjusted.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules

@domenicbove updated with requested changes, please review.

@domenicbove good catch.  Corrected.


where are SpotifyApi.NetCore.Samples

The readme mentions sample code in "SpotifyApi.NetCore.Samples" but I'm unsure where to find those samples. Did i miss a samples folder, or is the intent now to learn solely from test case code?

Hi @badhras - Samples have been moved to a separate repo: https://github.com/Ringobot/SpotifyApi.NetCore.Samples
See also #22 which has more info


HOW TO: Import custom JavaScript file/library?

Could you please help me on how to and where to import custom JavaScript file and/or library or from a CDN?
Because usually I just inject it at the bottom part of the <body>, but it seems that this has a different method. Thank you so much.

Hello @veslorens
Node js has not a way to load url in require method.
You have three way to do this:

Check is there a package in npmjs first. If there is an npm package you can install it with npm install command. You can do yourself with fork repo and add package.json file.
Download required files (with all dependencies) from cdn and load from local.
Async load from url: http://stackoverflow.com/questions/7809397/how-to-require-from-url-in-node-js

Have a great day!

Hi @centrual
I'll try these methods you mentioned.
Thank you so much for your help.
Cheers!


Design tweaks

Some subtle changes that I think make the site look a little crisper. Replaces gray backgrounds in a couple places with white ones to add contrast, and introduces just a hint of color (a quiet green) to liven things up.

any chance you could host this somewhere real quick so i could check it out?

Yup! http://jsonapi.mymorguefile.com/

:+1: by me

Some random thoughts:
The splashes of green are nice.
The home page looks odd to me now that the banner isn't full width. Might be because there's no border on sides (see red arrows below) like there is on the top and bottom. As is, I think I prefer the current full width navbar and home page banner, but it's not a huge deal.

I like the use of green in the H1:

But I prefer the full caps font we're using now. It matches the font used on the home page banner.

@dgeb

The home page looks odd to me now that the banner isn't full width.

Yup. I had tried a full-width version, and was on the fence about it, but looking at it again I think you're right. PR updated!

But I prefer the full caps font we're using now

I think what you're reacting to here is how much heavier the new headings are, rather than the title case vs. all caps issue per se. I switched away from all caps for better readability, and to have the headings' style echo that of the selected item in the nav bar. But when I moved to title case, I had to make the heading bolder to keep the hierarchy intact, and I think I went a bit too far. So I've updated the PR to use a somewhat lighter font weight. Check it out and let me know if it feels better.

@ethanresnick thanks for making those changes.
My final nit is that the line under the top navbar should probably be full width on all pages, to match both the home page banner and the green line at the very top.
Other than that, I'm :+1:

My final nit is that the line under the top navbar should probably be full width on all pages, to match both the home page banner and the green line at the very top.

I mocked this up here, but I'm not sure it's an improvement.
To explain my thinking, let me back up a bit... It seems like there are two ways the layout can be made to "read" visually:

The navbar can appear as a distinct, full-width element with some centered, fixed-width content below it. This is how the current design on jsonapi.org reads:

The nav links can "read" as being part of the body content, with the whole page (including the nav links) "hanging" off the full-width line at the top. This is how the inner pages read in the design I'm proposing (and how the homepage did originally, with the fixed-width banner):

I'm ok with either structure, though I slightly prefer the first. Nevertheless, I switched to the second one in this PR (holding aside the homepage for a sec) because...
In both designs shown above, the nav links are aligned with the body content (not spread across the full width of the screen, for example), and this acts to naturally suggest the second "read". But, in the design currently up on jsonapi.org, the full-width background color behind the nav links and the (very dark) line below them serve to overcome the alignment and convincingly suggest a distinct, full-width navbar.
However, once I removed the gray background from behind the navbar (for contrast) and lightened the line below it, using just a full-width line below the nav links to suggest the first "read" felt insufficient and a little dissonant. Looking at that design, my brain still ultimately settles on the first interpretation, but there's a bit of tension. Meanwhile, narrowing the line to match the width of the main content removes this tension by cleanly suggesting the second interpretation instead.
So that's what I went with in this PR, and it's why I'd prefer this PR as-is to making the line below the nav links full-width. But there are also couple other options that I want to throw out there, that might address the concern's behind Dan's suggestion:

It's true that the homepage and the interior pages are inconsistent in this PR, because the homepage banner breaks the grid and goes full width. If this inconsistency is what's motivating Dan's suggestion, we could remove the inconsistency by going back to the fixed-width homepage banner, but with the side borders that Dan proposed earlier. Personally, this inconsistency, which I tried to avoid at first, doesn't bother me anymore, because I think the full-width banner's stronger impact justifies it. But I could go either way.

If Dan's suggestion is motivated less by the inconsistency and more by a preference for designs with a distinct, full-width navbar, which I can understand, we could add back a background color to the navbar and make it full-width, so that it would function just as it does on the current site. However, my suggestion here would be to make the background a quite green, rather than a gray (as my primary goal with this PR was to make the site less gray). This would mean substantially more color than this PR is proposing right now, though, which is why I was hesitant to suggest it at first. Still, I think it could be a viable option, so I mocked it up here. Live with it for a bit and let me know what you think.

Wow, @ethanresnick - thanks for doing the mockups. It's difficult to discuss these things without seeing them.
I personally favor option a - http://opt-a.mymorguefile.com/format/ - but would prefer some very slight background color to the navbar, at least on pages other than the home page (similar to what we're doing now).
I think the dark green in option d is overkill, and I find the truncated horizontal line under the navbar in b and c to be abrupt.
Of course, that's just my opinion :)

I personally favor option a - http://opt-a.mymorguefile.com/format/ - but would prefer some very slight background color to the navbar... I think the dark green in option d is overkill

@dgeb Cool! I'd also be happy with a full-width navbar, like in option a, once we put some background color behind it. So it sounds like the question is just picking that color. Would you be up to put together a version with a background color that you like? In the mean time, I'll also play with some versions that have subtler colors.
About the green used in option d, though: I do wonder if it feels like too much color just because we're so used to the current, gray design. As I've lived with option d for a bit (leaving it open, browsing around, and switching between it and other sites), the green bar has grown on me. So, if you haven't already, I'd encourage you to sit with it for a bit too and see if your feelings about it change.

So it sounds like the question is just picking that color.

I tend to favor leaving the navbar background color the same minimalist gray for now: #fafafa. This one minor color change could also be revisited separately.

About the green used in option d, though: I do wonder if it feels like too much color just because we're so used to the current, gray design.

I'm willing to be overruled here. @steveklabnik @tkellen @wycats what do you guys think about this green background to the navbar that Ethan favors?
http://opt-d.mymorguefile.com/format/

I'm not sure this comes across in my comments, but I do agree that the site could use a little more style / color.
One thought is to incorporate the logo on all pages in the nav bar, like we're doing over in http://discuss.jsonapi.org/

I like the green!
If ya'll want, I might be able to get some help from the Bocoup design team sometime in the coming months if we want a wholesale facelift.

I like the green!

Well, if both you guys are onboard, I'm fine with it too.

If ya'll want, I might be able to get some help from the Bocoup design team sometime in the coming months if we want a wholesale facelift.

Thanks - I think that would be awesome :100:

I'll open an issue on our trello board and see what kind of response I get. I'm not sure what all we have in the pipeline right now.

I feel neutral to vaguely positive about the green :+1:

I think I'd like the green better with a little less vertical padding (say 5px instead of 10px). That removes the weight imbalance that was my main objection.
P.S. how ironic is it to paint this particular bikeshed in public? :stuck_out_tongue_closed_eyes:

P.S. how ironic is it to paint this particular bikeshed in public?

Yeah, it's a delicious irony :D

I think I'd like the green better with a little less vertical padding (say 5px instead of 10px). That removes the weight imbalance that was my main objection.

I definitely see what you're talking about re the weight. I've shrunk the vertical padding somewhat (from 10px to 8px) and also desaturated the green a tiny bit so it's less heavy. I tried shrinking the vertical padding further, but it made the navigation feel a bit too narrow, and less inviting as a click target.
I've updated this PR to reflect the newest version, which is also visible at the old Option D URI.

If ya'll want, I might be able to get some help from the Bocoup design team sometime in the coming months if we want a wholesale facelift.

Sure! Thanks Tyler :)

@ethanresnick thanks - looks good to me! Was going to merge but there are conflicts - feel free to merge after resolving.

Awesome! Conflicts resolved & merged.
Thanks for the great feedback guys! The design we ended on is definitely better than the one I originally opened this PR with :)

Looking good! Thanks for seeing this through @ethanresnick :+1:


Stone paper scissors game

I would like to add javascript stone paper scissors game project as a participant of GSSOC,21 .
Kindly assign this issue to me.

@vinayak0127 @codDoc98 @sejalshri @Riya764 There is a rock paper scissor already present in the project.


Raydium decoder crate doesn't work

i'm really impressed with this project! i strongly believe that open-source initiatives like this will become fundamental building blocks of the solana ecosystem, similar to yellowstone-grpc.
while testing, I discovered that the raydium-amm-v4 decoder isn't functioning correctly. specifically, i was unable to decode account updates or instructions properly.
upon investigation, i found that the instruction discriminators are incorrect. given that this is a solana native program, the current instruction discriminators appear unusually long. additionally, there are some inaccuracies in the instruction arguments.
as for now successfully implemented fixes for:

swap instructions
initialize2 (pool creation) instructions

would you be open to a pull request with my changes?

Hello @passingBySol  @KellianDev. I want to get the exact amout out data when swapping to raydium


Building for specific blender versions

In my case, I have many versions of Blender on my system and I definitely don't want to install every time to each of them.
As you know, I am a fan of having a config file for which lets the developer decide which versions they want to install it (something akin to a requirements.txt if you will). Right now MCprep is using this build system and is being installed to even 2.7x versions still on my machine, which means a lot of complaining on startup. Not that this is a major problem for me, basically never using 2.7x again now, but there are other scenarios where it may be helpful.
Likewise, it could also be nice to have flags to install to a specific blender versions as well, something like: bpy-addon-build -b dev -v 3.6.
For the "versions to install to" config, it could be a text file containing just blender versions without their paths. Nice thing is, this could even serve as documentation (in a way) as to the canonically supported blender versions of a given addon. I think blender_installs.txt is a reasonable name to keep, but open to whatever.
I almost wonder if the tool should require specifying either a version (-v 3.6, a file (-v blender_installs.txt), or an all flag (-v all) and if not, enter a sort of interactive mode so it's clear what's about to happen.

Ok I will admit, I totally missed that the config info is actually in the yaml, so that part is great. I still think it could be nice to have a flag to install only a specific version though, and just make it so the default is -all which would basically seek those in the yaml file. But less pressing imo.

This has been added in 70395a0


Absolute urls and other fixes

Changing cross-repo links to absolute URLs plus:

removed en-us from existing links to make the URLs locale agnostic
changed azure docs links to new location in docs.microsoft.com
changed a couple of links from msdn to relative repo links (we have tons of these now that we migrated the content. I just fixed a few)
fixed a couple of broken links to visual-studio and office-dev

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/core/preview3/tools/dotnet-msbuild.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/layering.md
:white_check_mark:Succeeded
View
Details

docs/csharp/basic-types.md
:white_check_mark:Succeeded
View
Details

docs/csharp/classes.md
:white_check_mark:Succeeded
View
Details

docs/csharp/csharp.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/additional-resources.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/getting-started-with-csharp.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/introduction-to-the-csharp-language-and-the-net-framework.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/library-with-visual-studio-2017.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/testing-library-with-visual-studio.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/whats-new.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/cs0234.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/cs0246.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/cs1699.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/cs4014.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/index.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/app-deployment.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/checked-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/command-line-building-with-csc-exe.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/doc-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/errorreport-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/filealign-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/index.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/nowarn-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/nowin32manifest-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/subsystemversion-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/win32manifest-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/index.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/continue.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/do.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/for.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/goto.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/if-else.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/return.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/stackalloc.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/static.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/switch.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/try-catch-finally.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/try-catch.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/try-finally.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/while.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/preprocessor-directives/preprocessor-region.md
:white_check_mark:Succeeded
View
Details

docs/csharp/methods.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0035.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0584.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0585.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0586.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0587.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0588.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0589.md
:white_check_mark:Succeeded
View
Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/core/preview3/tools/dotnet-msbuild.md
:white_check_mark:Succeeded
View
Details

docs/core/preview3/tools/layering.md
:white_check_mark:Succeeded
View
Details

docs/csharp/basic-types.md
:white_check_mark:Succeeded
View
Details

docs/csharp/classes.md
:white_check_mark:Succeeded
View
Details

docs/csharp/csharp.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/additional-resources.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/getting-started-with-csharp.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/introduction-to-the-csharp-language-and-the-net-framework.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/library-with-visual-studio-2017.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/testing-library-with-visual-studio.md
:white_check_mark:Succeeded
View
Details

docs/csharp/getting-started/whats-new.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/cs0234.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/cs0246.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/cs1699.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/cs4014.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-messages/index.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/app-deployment.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/checked-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/command-line-building-with-csc-exe.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/doc-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/errorreport-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/filealign-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/index.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/nowarn-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/nowin32manifest-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/subsystemversion-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/compiler-options/win32manifest-compiler-option.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/index.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/continue.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/do.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/for.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/goto.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/if-else.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/return.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/stackalloc.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/static.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/switch.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/try-catch-finally.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/try-catch.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/try-finally.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/keywords/while.md
:white_check_mark:Succeeded
View
Details

docs/csharp/language-reference/preprocessor-directives/preprocessor-region.md
:white_check_mark:Succeeded
View
Details

docs/csharp/methods.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0035.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0584.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0585.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0586.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0587.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0588.md
:white_check_mark:Succeeded
View
Details

docs/csharp/misc/cs0589.md
:white_check_mark:Succeeded
View
Details

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

This is ready for review and I've already rebased to merge Steve's latest changes.
/cc @rpetrusha @stevehoag

Too many files to review all of the changes, but what I did review LGTM. :shipit:

ok thanks @stevehoag! just having an extra pair of eyes helps.


Cannot update self with other because they have different Parameters with the same name deep_dog_conv0_weight

mxnet-the-straight-dope/chapter08_computer-vision/fine-tuning.ipynb
cpu mode, when running the traning cell, got the following error:
AssertionError                            Traceback (most recent call last)
 in ()
62     #print(deep_dog_net)
63     #print(deep_dog_net.collect_params())
---> 64     deep_dog_net.collect_params().reset_ctx(contexts)
65     train(deep_dog_net, train_iter, val_iter, epochs, contexts)
/usr/local/lib/python2.7/dist-packages/mxnet/gluon/block.pyc in collect_params(self)
211         ret.update(self.params)
212         for cld in self._children:
--> 213             ret.update(cld.collect_params())
214         return ret
215
/usr/local/lib/python2.7/dist-packages/mxnet/gluon/parameter.pyc in update(self, other)
492                 assert self._params[k] is v,
493                     "Cannot update self with other because they have different "
--> 494                     "Parameters with the same name %s"%k
495             else:
496                 self._params[k] = v
AssertionError: Cannot update self with other because they have different Parameters with the same name deep_dog_conv0_weight

@szha can you please fix this - I think this is related to a change in the naming convention of conv layers in the prelease that also affected our distributed tutorials.

Taking a look

@wzhang1 could you upgrade your mxnet to the latest version?
pip install mxnet -U --pre --user

@szha it seems that in the ubuntu 16.04 I'm using, I got the following result for os.path.exists
Python 2.7.12 (default, Nov 19 2016, 06:48:10)
[GCC 5.4.0 20160609] on linux2

os.path.exists("/home/w/.mxnet/models/squeezenet1.1-33ba0f93.params")
True
os.path.exists("~/.mxnet/models/squeezenet1.1-33ba0f93.params")
False

os.path.expanduser is used for expanding ~. I'm not sure how this is relevant.

@szha I remove a optional variable in line 132 and the model is loaded for me
net.load_params(get_model_file('squeezenet%s'%version), ctx=ctx)
https://github.com/apache/incubator-mxnet/blob/master/python/mxnet/gluon/model_zoo/vision/squeezenet.py

@szha or add net.load_params   in get_squeezenet, which way do you prefer?

@szha I went to to look the changes and found similar issue for other networks, should be a small fix
https://github.com/apache/incubator-mxnet/pull/7892/commits/dfd1bb960b8346ee9032480160cfcb85764d1407

closing, default location issue moved to /mxnet/gluon/model_zoo/vision

Thank you everyone!


Docs: link fixes

This PR fixes a few broken links on ./docs/1-introduction.md and ./docs/2-migrate.mdx that impact the SDK's generated docs on arbitrum-docs.

@douglance , is there anything missing in this PR for a review/merge?


[Feature] Temporarily Show Dynamic Token border

Just want to preface this with, i'm unsure if it's possible/in scope but it would be a neat little QoL
But, my thought is some sort of option that allows you to have a special mask layer, this mask layer acts as a normal mask (IE the mask for Dynamic Token border is already, but with one extra feature. In the Image preview show the border (like without the coloration etc.) but make it so it isn't included in the final image
If this were possible it makes designing a token more straight forward as it's very clear what the result is

Hi, yes, I have been thinking about this, it's just a bit harder than it might seem.

yeah, I assumed as much. If not, no pressure relatively easy to work around


migrate data from extension

its possible to migrate data from extensions?

Hi @albertobraschi ,
Our migration tool helps to port core Magento 2 data only, as indicated here.
Migrating extensions' data is a separated task which is beyond scope of our migration tool. It would be best to check with your extension providers to see if they're ready for Magento 2 though.
Meanwhile, as you might know, we no longer maintain the outdate script at Github, and replace it with a newer UB Data Migration Pro here.
If you're interested, you can check out a few case studies below to learn more about our new migration tool version:

We did use the Pro version ourself to help Winetasting.com – Migrate 382,047 customer entities to Magento 2
And this case study as well - Freelaunch.nl used UB Data Migration Pro to migrate 230,000 products to Magento 2
Case Study: Successful Magento 2 Data Migration for Kwaaijongens.nl

Hope that helps.
Regards,
Ubertheme team


Cotx x3 teardown - RasPi 4

More internal shots here https://fccid.io/document.php?id=5394081
Seems to use sx1302 with sx1257 front ends


Why not use redis for caching?

I saw the code is using a lot of sqlite for caching, might if I asked why not redis?

It is using sqlite as a database - to store data.
The other use is a cache class. sqlite is used there only for someting named 'dev server', for production server we are using memcached for caching.
Which case you are reffering to?

I'm referring to the first use case that you mentioned. I'm quite confused why switching caching tools from SQLite to memcache instead of sticking to one tool. And more over, seems like redis could provide more memory for caching, why not use redis for this scenario.
I'm just out of curious and thanks very much for the answer ;)

Looks like you are mixing two thing because you are still using term cache.
It's not a cache, but a relational database used to store all tweets. Redis is not a database engine. So for a database we are using sqlite, and possibly MySQL in a future.
Second case is a cache. Why whould we force to install Memcached on dev server? There's no need to do that because sqlite is more than sufficient for that task and it's built in python. For a production server - we can't use sqlite here (but we could use MySQL for example), Memcached is our tool of choice for that task.
seems like redis could provide more memory for caching
That is not true, you can set Memcached to use all the RAM you have.

Thanks a lot for the explanation, I will close the issue here.


Changing console error attachment name as per requirement

@pagangil,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@nigurr @puagarwa : Please review this PR for changing console file name as per PM ask.


Dropdown menu does not work on smaller resolution

Hello,
I browsed a bit on web and this was kinda issue back in 2013 maybe even earlier so I supposed this would be already fixed but unfortunately not.
When you have scrolling navbar you are unable to have dropdown menu on smaller resolution.
After clicking on the particular dropdown parent it immediately closes and didnt shows the children.
Is there some fix?
Thanks

My bad. Again, I figured it out few moments after I post it here.
Easing was automatically closing Navbar after click on "a" element. So I replaced the dropdown element with "div" and same .css options. Looks the same, and .js is not closing navbar after click. YEY.
So sorry for that.


Handle unpremultiply the same way in image out buffer and callback.

For the image out callback case we did not unpremultiply alpha, and
there was a test to check that, but for the image buffer case we
always unpremultiplied alpha.
I added an API function similar to keep/undo orientation where the
user can specify the desired behavior.

Added changelog entry


How to gracefully refresh accesstoken instead of using static passwords?

How to work with password which expire after some time or that are not present initially?
Microsoft released an example  of how to set it up using ioredis, but the problem is that I cannot get it to work as I want.
Global Redis Client
Having only one global redis client and once the access token expires you would need to ensure that it swaps the old instance with a new instance.

Will the swap cause the old redis client to drop pending commands?
You would need to ensure that the old client is diconnected gracefully.
[Issue] The initial client will have incorrect password until it runs out of reconnection attempts and uses the latest changes in the options object. The only way to get around this seem to be to update the redis.options.username/password after a successful auth command.
How would this work when running in dev?

Local Redis Client
You create an async factory for providing redis clients with the latest password and ensure that the client is freed after it has been used within a small scope. No need to worry about updating the redis options to match the latest password after the access token expires. However, the issue I ran into with this solution is that it eventually ran out of connections. 'ERR max number of clients reached'
Question
Is there any guidance on implementing access token based redis clients. Or how can I override the default way redis handles connections to use a username/password that is resolved asyncronously after the client has been created? It would be good if these overrides could be added to the constructor so that developers can work with access tokens without having to hack around it like I'm trying to do.
Thanks.

Would a solution that looks like this be a valid way to override the normal behaviour?
export function getRedisClient(): Redis {
  const c = createRedisInstance();
  (c as any)._connect = c.connect;
  const connect = async (callback?: Callback<void>) => {
    const accessToken = await getRedisPassword();
    c.options.username = "default";
    c.options.password = accessToken;
    return (c as any)._connect(callback);
  };
  c.connect = connect;
  return c;
}

See also #1738


Add Support for TailwindCSS to ReactPlay

We have decided to add support for TailwindCSS and SASS.
Discussed in https://github.com/atapas/react-play/discussions/73

Originally posted by joshi-kaushal April 20, 2022
Hello,
As we go ahead and get contributions from people around the globe, I think we should have a standard set for styling.
Tailwind CSS seems like a great option for me since it is widely accepted, has a minimal learning curve, and most importantly the styling is standardized.
I can take the whole responsibility of integrating our existing app with Tailwind.

I see this play merge will add the SASS Support. So this issue needs to take care of Tailwind alone.
https://github.com/atapas/react-play/pull/163/files

Can I add tailwind support to my react play, so that it can be merged. As I have already did that 😄

Can I add tailwind support to my react play, so that it can be merged. As I have already did that 😄

I would say go ahead and convert your play to support Tailwind. If someone picks this issue in isolation and just adds support, that will be even faster as the scope of the changes will be limited.

Hello @atapas Sir, I would like to work on this issue

Hello @atapas Sir, I would like to work on this issue

All yours.

Hello @vasantisuthar Could you please review the PR once?
https://github.com/atapas/react-play/pull/183


Update manual.html

Hello. When I create my first codemirror script, I found it can't load the file lib/codemirror.css because the filepath is incorrect. the file 'codemirror.css' and 'codemirror.js' is in the same directory, the the html should be . Thank you for your watching.

Thank you! Merged as 1ded3f6


Bluetooth: Restoring connection to peripheral issue

Application flow

Central discovers and connects to 2 peripherals
When one of the connections is dropped, central attempt to restore that connection again

Describe the bug
When the connection with with the firstly connected peripheral is dropped and by trying to reconnect again, the connected callback is called with error code 0x02
To Reproduce
Steps to reproduce the behavior:

Checkout this commit 319ec5e7c0966e9aef03fc4376370a89096b4209
Run ~/zephyrproject/zephyr/tests/bluetooth/bsim_bt/bsim_test_conn_stress/tests_scripts/conn_stress.sh

Logs and console output
d_01: @00:00:00.000000  *** Booting Zephyr OS build zephyr-v3.2.0-2919-ga5ad275de209 ***
d_02: @00:00:00.000000  *** Booting Zephyr OS build zephyr-v3.2.0-2919-ga5ad275de209 ***
d_00: @00:00:00.000000  *** Booting Zephyr OS build zephyr-v3.2.0-2919-ga5ad275de209 ***
d_01: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
d_01: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF52x (0x0002)
d_01: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 3.2 Build 99
d_01: @00:00:00.000000  [00:00:00.000,000] <wrn> bt_id: bt_read_static_addr: No static addresses stored in controller
d_00: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
d_02: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
d_00: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF52x (0x0002)
d_02: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF52x (0x0002)
d_00: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 3.2 Build 99
d_02: @00:00:00.000000  [00:00:00.000,000] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 3.2 Build 99
d_01: @00:00:00.000000  [Peripheral] : Initializing Test
d_02: @00:00:00.000000  [00:00:00.000,000] <wrn> bt_id: bt_read_static_addr: No static addresses stored in controller
d_00: @00:00:00.000000  [00:00:00.000,000] <wrn> bt_id: bt_read_static_addr: No static addresses stored in controller
d_02: @00:00:00.000000  [Peripheral] : Initializing Test
d_00: @00:00:00.000000  [Central] : Initializing Test
d_01: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: Identity: CB:04:A6:15:1F:50 (random)
d_01: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x0000, manufacturer 0x05f1
d_01: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0xffff
d_01: @00:00:00.004568  [Peripheral] : Bluetooth initialized
d_01: @00:00:00.004938  [Peripheral] : Advertising successfully started
d_00: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: Identity: DE:CD:A2:21:EE:22 (random)
d_00: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x0000, manufacturer 0x05f1
d_00: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0xffff
d_00: @00:00:00.004568  [Central] : Bluetooth initialized
d_00: @00:00:00.004938  [Central] : Scanning successfully started
d_02: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: Identity: DD:D1:7D:F0:5F:33 (random)
d_02: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x0000, manufacturer 0x05f1
d_02: @00:00:00.004568  [00:00:00.004,547] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0xffff
d_02: @00:00:00.004568  [Peripheral] : Bluetooth initialized
d_02: @00:00:00.004938  [Peripheral] : Advertising successfully started
d_00: @00:00:00.007160  [Central] : ------------------------------------------------------
d_00: @00:00:00.007160  [Central] : [DEVICE]: 7A:7C:28:1F:71:40 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:00:00.007160  [Central] : ------------------------------------------------------
d_00: @00:00:00.007916  [Central] : ------------------------------------------------------
d_00: @00:00:00.007916  [Central] : [DEVICE]: 7A:7C:28:1F:71:40 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:00:00.007916  [Central] : ------------------------------------------------------
d_00: @00:00:00.007916  [Central] : Device name : Zephyr Peripheral
d_00: @00:00:00.007917  [Central] : Scanning successfully stopped
d_00: @00:00:00.007917  [Central] : Connecting to 7A:7C:28:1F:71:40 (random)
d_01: @00:00:00.114719  [Peripheral] : Updated MTU: TX: 23 RX: 23 bytes
d_01: @00:00:00.114719  [Peripheral] : Connection 0x80d3060 established : 60:5D:FC:C7:1A:F4 (random)
d_00: @00:00:00.114716  [Central] : Updated MTU: TX: 23 RX: 23 bytes
d_00: @00:00:00.114716  [Central] : Connection 0x80d3160 established : 7A:7C:28:1F:71:40 (random)
d_00: @00:00:00.114716  [Central] : Active connections count : 1
d_00: @00:00:00.114716  [Central] : Connection reference store index 0
d_00: @00:00:00.115924  [Central] : Security level for connection 0x80d3160 with peer 7A:7C:28:1F:71:40 (random) is set to : 2
d_00: @00:00:00.329316  [Central] : Scanning successfully started
d_01: @00:00:00.716046  [Peripheral] : Security for 0x80d3060 changed: 60:5D:FC:C7:1A:F4 (random) level 2
d_01: @00:00:00.718506  [Peripheral] : Discovering peer 60:5D:FC:C7:1A:F4 (random) primary service
d_00: @00:00:00.743762  [Central] : ------------------------------------------------------
d_00: @00:00:00.743762  [Central] : [DEVICE]: 68:11:15:89:AB:56 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:00:00.743762  [Central] : ------------------------------------------------------
d_00: @00:00:00.744518  [Central] : ------------------------------------------------------
d_00: @00:00:00.744518  [Central] : [DEVICE]: 68:11:15:89:AB:56 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:00:00.744518  [Central] : ------------------------------------------------------
d_00: @00:00:00.744518  [Central] : Device name : Zephyr Peripheral
d_00: @00:00:00.744519  [Central] : Scanning successfully stopped
d_00: @00:00:00.744519  [Central] : Connecting to 68:11:15:89:AB:56 (random)
d_00: @00:00:00.816240  [Central] : Security for conn (0) @ 0x80d3160 changed: 7A:7C:28:1F:71:40 (random) level 2
d_00: @00:00:00.828278  [Central] : Updating MTU for CB:04:A6:15:1F:50 (random)...
d_02: @00:00:00.846958  [Peripheral] : Updated MTU: TX: 23 RX: 23 bytes
d_02: @00:00:00.846958  [Peripheral] : Connection 0x80d3060 established : 60:5D:FC:C7:1A:F4 (random)
d_00: @00:00:00.846965  [Central] : Updated MTU: TX: 23 RX: 23 bytes
d_00: @00:00:00.846965  [Central] : Connection 0x80d3218 established : 68:11:15:89:AB:56 (random)
d_00: @00:00:00.846965  [Central] : Active connections count : 2
d_00: @00:00:00.846965  [Central] : Connection reference store index 1
d_00: @00:00:00.848173  [Central] : Security level for connection 0x80d3218 with peer 68:11:15:89:AB:56 (random) is set to : 2
d_01: @00:00:00.966069  [Peripheral] : Updated MTU: TX: 247 RX: 247 bytes
d_01: @00:00:00.966069  [Peripheral] : Updating MTU succeeded DE:CD:A2:21:EE:22 (random)
d_01: @00:00:01.016078  [Peripheral] : Primary Service Found
d_00: @00:00:01.016316  [Central] : Updated MTU: TX: 247 RX: 247 bytes
d_00: @00:00:01.016316  [Central] : MTU exchange addr CB:04:A6:15:1F:50 (random) conn 0 successful
d_00: @00:00:01.027863  [Central] : Discovering peer CB:04:A6:15:1F:50 (random) primary service
d_01: @00:00:01.116149  [Peripheral] : Service Characteristic Found
d_00: @00:00:01.116395  [Central] : Primary Service Found
d_01: @00:00:01.216081  [Peripheral] : [SUBSCRIBED] addr DE:CD:A2:21:EE:22 (random)
d_00: @00:00:01.216399  [Central] : Service Characteristic Found
d_00: @00:00:01.316311  [Central] : [SUBSCRIBED] addr CB:04:A6:15:1F:50 (random) conn 0
d_02: @00:00:01.367206  [Peripheral] : Security for 0x80d3060 changed: 60:5D:FC:C7:1A:F4 (random) level 2
d_02: @00:00:01.377137  [Peripheral] : Discovering peer 60:5D:FC:C7:1A:F4 (random) primary service
d_00: @00:00:01.417400  [Central] : Security for conn (1) @ 0x80d3218 changed: 68:11:15:89:AB:56 (random) level 2
d_00: @00:00:01.427033  [Central] : Updating MTU for DD:D1:7D:F0:5F:33 (random)...
d_02: @00:00:01.517229  [Peripheral] : Updated MTU: TX: 247 RX: 247 bytes
d_02: @00:00:01.517229  [Peripheral] : Updating MTU succeeded DE:CD:A2:21:EE:22 (random)
d_02: @00:00:01.567237  [Peripheral] : Primary Service Found
d_00: @00:00:01.567476  [Central] : Updated MTU: TX: 247 RX: 247 bytes
d_00: @00:00:01.567476  [Central] : MTU exchange addr DD:D1:7D:F0:5F:33 (random) conn 1 successful
d_00: @00:00:01.586701  [Central] : Discovering peer DD:D1:7D:F0:5F:33 (random) primary service
d_02: @00:00:01.667309  [Peripheral] : Service Characteristic Found
d_00: @00:00:01.667556  [Central] : Primary Service Found
d_02: @00:00:01.767241  [Peripheral] : [SUBSCRIBED] addr DE:CD:A2:21:EE:22 (random)
d_00: @00:00:01.767560  [Central] : Service Characteristic Found
d_00: @00:00:01.867473  [Central] : [SUBSCRIBED] addr DD:D1:7D:F0:5F:33 (random) conn 1
d_00: @00:00:02.968305  [Central] : [NOTIFICATION] addr DD:D1:7D:F0:5F:33 (random) conn 1 data cnt:0 DD:D1 length 220 cnt 0
d_00: @00:00:05.867493  [Central] : LE conn param req: DD:D1:7D:F0:5F:33 (random) int (0x0018 (~30 ms), 0x0028 (~50 ms)) lat 0 to 42
d_00: @00:00:05.867493  [Central] : Updating DD:D1:7D:F0:5F:33 (random)... connection parameters
d_00: @00:00:05.867493  [Central] : Updating connection parameters succeeded DD:D1:7D:F0:5F:33 (random)
d_02: @00:00:05.917214  [Peripheral] : LE conn param updated: DE:CD:A2:21:EE:22 (random) int 0x0028 (~50 ms) lat 0 to 400
d_02: @00:00:05.917714  [Peripheral] : LE conn param req: DE:CD:A2:21:EE:22 (random) int (0x000a (~12 ms), 0x001e (~37 ms)) lat 0 to 400
d_00: @00:00:06.315339  [Central] : LE conn param updated: DD:D1:7D:F0:5F:33 (random) int 0x001e (~37 ms) lat 0 to 400
d_02: @00:00:06.315278  [Peripheral] : LE conn param updated: DE:CD:A2:21:EE:22 (random) int 0x001e (~37 ms) lat 0 to 400
d_00: @00:00:06.367267  [Central] : [NOTIFICATION] addr CB:04:A6:15:1F:50 (random) conn 0 data cnt:0 CB:04 length 220 cnt 0
d_00: @00:00:06.370763  [Central] : LE conn param req: CB:04:A6:15:1F:50 (random) int (0x0018 (~30 ms), 0x0028 (~50 ms)) lat 0 to 42
d_00: @00:00:06.370763  [Central] : Updating CB:04:A6:15:1F:50 (random)... connection parameters
d_00: @00:00:06.370763  [Central] : Updating connection parameters succeeded CB:04:A6:15:1F:50 (random)
d_01: @00:00:06.372453  [Peripheral] : [NOTIFICATION] addr DE:CD:A2:21:EE:22 (random) conn 0x80d3060 data cnt:0 length 220 cnt 0
d_02: @00:00:06.396384  [Peripheral] : [NOTIFICATION] addr DE:CD:A2:21:EE:22 (random) conn 0x80d3060 data cnt:0 length 220 cnt 0
d_01: @00:00:06.420598  [Peripheral] : LE conn param updated: DE:CD:A2:21:EE:22 (random) int 0x0028 (~50 ms) lat 0 to 400
d_01: @00:00:06.421098  [Peripheral] : LE conn param req: DE:CD:A2:21:EE:22 (random) int (0x000a (~12 ms), 0x001e (~37 ms)) lat 0 to 400
d_01: @00:00:06.814118  [Peripheral] : LE conn param updated: DE:CD:A2:21:EE:22 (random) int 0x001e (~37 ms) lat 0 to 400
d_00: @00:00:06.814179  [Central] : LE conn param updated: CB:04:A6:15:1F:50 (random) int 0x001e (~37 ms) lat 0 to 400
d_00: @00:00:28.893348  [Central] : [NOTIFICATION] addr DD:D1:7D:F0:5F:33 (random) conn 1 data cnt:100 DD:D1 length 220 cnt 100
d_00: @00:00:31.567310  [Central] : [NOTIFICATION] addr CB:04:A6:15:1F:50 (random) conn 0 data cnt:100 CB:04 length 220 cnt 100
d_01: @00:00:31.571148  [Peripheral] : [NOTIFICATION] addr DE:CD:A2:21:EE:22 (random) conn 0x80d3060 data cnt:100 length 220 cnt 100
d_02: @00:00:32.346384  [Peripheral] : [NOTIFICATION] addr DE:CD:A2:21:EE:22 (random) conn 0x80d3060 data cnt:100 length 220 cnt 100
d_00: @00:00:54.843348  [Central] : [NOTIFICATION] addr DD:D1:7D:F0:5F:33 (random) conn 1 data cnt:200 DD:D1 length 220 cnt 200
d_00: @00:00:57.517310  [Central] : [NOTIFICATION] addr CB:04:A6:15:1F:50 (random) conn 0 data cnt:200 CB:04 length 220 cnt 200
d_01: @00:00:57.521148  [Peripheral] : [NOTIFICATION] addr DE:CD:A2:21:EE:22 (random) conn 0x80d3060 data cnt:200 length 220 cnt 200
d_02: @00:00:58.296384  [Peripheral] : [NOTIFICATION] addr DE:CD:A2:21:EE:22 (random) conn 0x80d3060 data cnt:200 length 220 cnt 200
d_01: @00:01:09.974488  [Peripheral] : [UNSUBSCRIBED] addr DE:CD:A2:21:EE:22 (random)
d_01: @00:01:10.041104  [Peripheral] : [UNSUBSCRIBED]
d_00: @00:01:10.078764  [Central] disconnected:474 : Connection (0) @ 0x80d3160 with Peer CB:04:A6:15:1F:50 (random) terminated (reason 0x15)
d_01: @00:01:10.078765  [Peripheral] disconnected:88 : Connection @ 0x80d3060 with Peer DE:CD:A2:21:EE:22 (random) terminated (reason 0x16)
d_00: @00:01:10.303823  [Central] : Scanning successfully started
d_00: @00:01:10.391499  [Central] : ------------------------------------------------------
d_00: @00:01:10.391499  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:01:10.391499  [Central] : ------------------------------------------------------
d_00: @00:01:10.392255  [Central] : ------------------------------------------------------
d_00: @00:01:10.392255  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:01:10.392255  [Central] : ------------------------------------------------------
d_00: @00:01:10.392255  [Central] : Device name : Zephyr Peripheral
d_00: @00:01:10.392256  [Central] : Scanning successfully stopped
d_00: @00:01:10.392256  [Central] : Connecting to CB:04:A6:15:1F:50 (random)
d_02: @00:01:10.712952  [Peripheral] : [UNSUBSCRIBED] addr DE:CD:A2:21:EE:22 (random)
d_02: @00:01:10.817265  [Peripheral] : [UNSUBSCRIBED]
d_00: @00:01:10.854923  [Central] disconnected:474 : Connection (1) @ 0x80d3218 with Peer DD:D1:7D:F0:5F:33 (random) terminated (reason 0x15)
d_02: @00:01:10.854925  [Peripheral] disconnected:88 : Connection @ 0x80d3060 with Peer DE:CD:A2:21:EE:22 (random) terminated (reason 0x16)
d_00: @00:01:13.387392  [Central] connected:417 : Failed to connect to CB:04:A6:15:1F:50 (random) (2)
d_00: @00:01:13.606934  [Central] : Scanning successfully started
d_00: @00:01:13.809163  [Central] : ------------------------------------------------------
d_00: @00:01:13.809163  [Central] : [DEVICE]: DD:D1:7D:F0:5F:33 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:01:13.809163  [Central] : ------------------------------------------------------
d_00: @00:01:13.809919  [Central] : ------------------------------------------------------
d_00: @00:01:13.809919  [Central] : [DEVICE]: DD:D1:7D:F0:5F:33 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:01:13.809919  [Central] : ------------------------------------------------------
d_00: @00:01:13.809919  [Central] : Device name : Zephyr Peripheral
d_00: @00:01:13.809920  [Central] : Scanning successfully stopped
d_00: @00:01:13.809920  [Central] : Connecting to DD:D1:7D:F0:5F:33 (random)
d_02: @00:01:13.913486  [Peripheral] : Updated MTU: TX: 23 RX: 23 bytes
d_02: @00:01:13.914694  [Peripheral] : Connection 0x80d3060 established : DE:CD:A2:21:EE:22 (random)
d_00: @00:01:13.913483  [Central] : Updated MTU: TX: 23 RX: 23 bytes
d_00: @00:01:13.913483  [Central] : Connection 0x80d3160 established : DD:D1:7D:F0:5F:33 (random)
d_00: @00:01:13.913483  [Central] : Active connections count : 1
d_00: @00:01:13.913483  [Central] : Connection reference store index 1
d_00: @00:01:13.971586  [Central] : [UNSUBSCRIBED] addr DD:D1:7D:F0:5F:33 (random)
d_02: @00:01:14.071252  [Peripheral] : Security for 0x80d3060 changed: DE:CD:A2:21:EE:22 (random) level 2
d_02: @00:01:14.085938  [Peripheral] : Discovering peer DE:CD:A2:21:EE:22 (random) primary service
d_00: @00:01:14.121483  [Central] : Security for conn (1) @ 0x80d3160 changed: DD:D1:7D:F0:5F:33 (random) level 2
d_00: @00:01:14.135834  [Central] : Scanning successfully started
d_00: @00:01:14.135834  [Central] : Updating MTU for DD:D1:7D:F0:5F:33 (random)...
d_00: @00:01:14.188466  [Central] : ------------------------------------------------------
d_00: @00:01:14.188466  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:01:14.188466  [Central] : ------------------------------------------------------
d_00: @00:01:14.189222  [Central] : ------------------------------------------------------
d_00: @00:01:14.189222  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:01:14.189222  [Central] : ------------------------------------------------------
d_00: @00:01:14.189222  [Central] : Device name : Zephyr Peripheral
d_00: @00:01:14.189223  [Central] : Scanning successfully stopped
d_00: @00:01:14.189223  [Central] : Connecting to CB:04:A6:15:1F:50 (random)
d_02: @00:01:14.271300  [Peripheral] : Updated MTU: TX: 247 RX: 247 bytes
d_02: @00:01:14.271300  [Peripheral] : Updating MTU succeeded DE:CD:A2:21:EE:22 (random)
d_02: @00:01:14.421316  [Peripheral] : Primary Service Found
d_00: @00:01:14.421634  [Central] : Updated MTU: TX: 247 RX: 247 bytes
d_00: @00:01:14.421634  [Central] : MTU exchange addr DD:D1:7D:F0:5F:33 (random) conn 1 successful
d_00: @00:01:14.435212  [Central] : Discovering peer DD:D1:7D:F0:5F:33 (random) primary service
d_02: @00:01:14.621295  [Peripheral] : Service Characteristic Found
d_00: @00:01:14.771418  [Central] : Primary Service Found
d_02: @00:01:14.871675  [Peripheral] : [SUBSCRIBED] addr DE:CD:A2:21:EE:22 (random)
d_00: @00:01:14.871993  [Central] : Service Characteristic Found
d_00: @00:01:15.121458  [Central] : [SUBSCRIBED] addr DD:D1:7D:F0:5F:33 (random) conn 1
d_00: @00:01:15.122770  [Central] : [NOTIFICATION] addr DD:D1:7D:F0:5F:33 (random) conn 1 data cnt:0 DD:D1 length 220 cnt 0
d_02: @00:01:16.075327  [Peripheral] : [NOTIFICATION] addr DE:CD:A2:21:EE:22 (random) conn 0x80d3060 data cnt:0 length 220 cnt 0
d_00: @00:01:17.189485  [Central] connected:417 : Failed to connect to CB:04:A6:15:1F:50 (random) (2)
d_00: @00:01:17.419007  [Central] : Scanning successfully started
d_00: @00:01:17.547687  [Central] : ------------------------------------------------------
d_00: @00:01:17.547687  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:01:17.547687  [Central] : ------------------------------------------------------
d_00: @00:01:17.548443  [Central] : ------------------------------------------------------
d_00: @00:01:17.548443  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:01:17.548443  [Central] : ------------------------------------------------------
d_00: @00:01:17.548443  [Central] : Device name : Zephyr Peripheral
d_00: @00:01:17.548444  [Central] : Scanning successfully stopped
d_00: @00:01:17.548444  [Central] : Connecting to CB:04:A6:15:1F:50 (random)
d_00: @00:01:18.971478  [Central] : LE conn param req: DD:D1:7D:F0:5F:33 (random) int (0x0018 (~30 ms), 0x0028 (~50 ms)) lat 0 to 42
d_00: @00:01:18.971478  [Central] : Updating DD:D1:7D:F0:5F:33 (random)... connection parameters
d_00: @00:01:18.971478  [Central] : Updating connection parameters succeeded DD:D1:7D:F0:5F:33 (random)
d_02: @00:01:19.071200  [Peripheral] : LE conn param updated: DE:CD:A2:21:EE:22 (random) int 0x0028 (~50 ms) lat 0 to 400
d_02: @00:01:19.072624  [Peripheral] : LE conn param req: DE:CD:A2:21:EE:22 (random) int (0x000a (~12 ms), 0x001e (~37 ms)) lat 0 to 400
d_02: @00:01:19.569275  [Peripheral] : LE conn param updated: DE:CD:A2:21:EE:22 (random) int 0x001e (~37 ms) lat 0 to 400
d_00: @00:01:19.569306  [Central] : LE conn param updated: DD:D1:7D:F0:5F:33 (random) int 0x001e (~37 ms) lat 0 to 400
d_00: @00:01:20.542512  [Central] connected:417 : Failed to connect to CB:04:A6:15:1F:50 (random) (2)
d_00: @00:01:20.762055  [Central] : Scanning successfully started
d_00: @00:01:21.025411  [Central] : ------------------------------------------------------
d_00: @00:01:21.025411  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:01:21.025411  [Central] : ------------------------------------------------------
d_00: @00:01:21.026167  [Central] : ------------------------------------------------------
d_00: @00:01:21.026167  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:01:21.026167  [Central] : ------------------------------------------------------
d_00: @00:01:21.026167  [Central] : Device name : Zephyr Peripheral
d_00: @00:01:21.026168  [Central] : Scanning successfully stopped
d_00: @00:01:21.026168  [Central] : Connecting to CB:04:A6:15:1F:50 (random)
d_00: @00:01:24.025270  [Central] connected:417 : Failed to connect to CB:04:A6:15:1F:50 (random) (2)
d_00: @00:01:24.244813  [Central] : Scanning successfully started
d_00: @00:01:24.403552  [Central] : ------------------------------------------------------
d_00: @00:01:24.403552  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:01:24.403552  [Central] : ------------------------------------------------------
d_00: @00:01:24.404308  [Central] : ------------------------------------------------------
d_00: @00:01:24.404308  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:01:24.404308  [Central] : ------------------------------------------------------
d_00: @00:01:24.404308  [Central] : Device name : Zephyr Peripheral
d_00: @00:01:24.404309  [Central] : Scanning successfully stopped
d_00: @00:01:24.404309  [Central] : Connecting to CB:04:A6:15:1F:50 (random)
d_00: @00:01:27.398256  [Central] connected:417 : Failed to connect to CB:04:A6:15:1F:50 (random) (2)
d_00: @00:01:27.627778  [Central] : Scanning successfully started
d_00: @00:01:27.651112  [Central] : ------------------------------------------------------
d_00: @00:01:27.651112  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:01:27.651112  [Central] : ------------------------------------------------------
d_00: @00:01:27.651868  [Central] : ------------------------------------------------------
d_00: @00:01:27.651868  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:01:27.651868  [Central] : ------------------------------------------------------
d_00: @00:01:27.651868  [Central] : Device name : Zephyr Peripheral
d_00: @00:01:27.651869  [Central] : Scanning successfully stopped
d_00: @00:01:27.651869  [Central] : Connecting to CB:04:A6:15:1F:50 (random)
d_00: @00:01:30.651491  [Central] connected:417 : Failed to connect to CB:04:A6:15:1F:50 (random) (2)
d_00: @00:01:30.871033  [Central] : Scanning successfully started
d_00: @00:01:30.920552  [Central] : ------------------------------------------------------
d_00: @00:01:30.920552  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 0, AD data len 3, RSSI -35
d_00: @00:01:30.920552  [Central] : ------------------------------------------------------
d_00: @00:01:30.921308  [Central] : ------------------------------------------------------
d_00: @00:01:30.921308  [Central] : [DEVICE]: CB:04:A6:15:1F:50 (random), AD evt type 4, AD data len 19, RSSI -35
d_00: @00:01:30.921308  [Central] : ------------------------------------------------------
d_00: @00:01:30.921308  [Central] : Device name : Zephyr Peripheral
d_00: @00:01:30.921309  [Central] : Scanning successfully stopped
d_00: @00:01:30.921309  [Central] : Connecting to CB:04:A6:15:1F:50 (random)
d_00: @00:01:33.924684  [Central] connected:417 : Failed to connect to CB:04:A6:15:1F:50 (random) (2)

doesn't happen anymore after rebasing on today's main.


[Feature Request] Passphrase-QR scan text formatted QR generated by separate SW

If you use passphrases as part of your security model it would be nice to be able to scan text QR codes to quickly import a longer string of text.

Thank you for the suggestion. It's something that's been asked about multiple times and these are my thoughts on it: writing a passphrase down, or transcribing it to a QR code, transforms the passphrase from something you know, into something that you have. A seed phrase + passphrase has the same functional authentication threshhold as a 2-of-2 multisig wallet. If you're looking for a wallet that's protected by two things that you "have" I would consider just using a 2-of-2.


make element.reflexController a dictionary

Type of PR (feature, enhancement, bug fix, etc.)
bug fix
Description
Following up on #377, this PR makes element.reflexController a dictionary to prevent multiple reflexes on the same element from overwriting eachothers' data
Fixes # (issue)
Why should this be added
prevents race conditions when running multiple reflexes on the same element
Checklist

[X] My code follows the style guidelines of this project
[X] Checks (StandardRB & Prettier-Standard) are passing
[X] This is not a documentation update

Please note that the best way to suggest changes or updates to the documentation is to join Discord and leave a note in the #docs channel. Any documentation updates posted as PRs cannot be accepted at this time. :heart:

Hey Rafe, another good catch.
My understanding of things is that an element can only have one instance of a controller on it. That means we could solve this "simply" by removing line 56 of lifecycle.js, right?
I'm trying to wrap my head around a scenario where there would be multiple different Reflex controllers on an element with different names. We might have to ask @hopsoft for clarity here.

Good call- I suspect removing delete element.reflexController would do the trick.  I'll test that next chance I get.

I'll have to think on this a bit harder, but the reason we call delete element.reflexController  is to clean up references that might cause memory leaks, so we'd still want to remove any references to controllers embedded in the new dictionary datatype.

I usually shy away from shotgun solutions, but I have an idea:
if (reflexes.length == 1) delete element.reflexController

The premise here is that if there's only one active Reflex in the dictionary, it's the current one, so you're safe to clear out the controller reference.

Makes sense, but I expect that this should be sufficient. delete element.reflexController[reflexId]


aliasPrimaryConnectionString doesn't exist anymore

We have some ARM templates that try to get the aliasPrimaryConnectionString key from an EventHub that have DR enabled.  The templates have been working fine for the past few months but around yesterday they all stopped working with the following error msg:
##[error]InvalidTemplate: Unable to process template language expressions for resource '/subscriptions/[SubscriptionId]/resourceGroups/[RG Name]/providers/Microsoft.Resources/deployments/[DeploymentName]' at line '1' and column '11619'. 'The language expression property 'aliasPrimaryConnectionString' doesn't exist, available properties are 'primaryConnectionString, secondaryConnectionString, primaryKey, secondaryKey, keyName'.'
Here's the problematic line:
"EventHubServiceSettings:EventHubConnectionString": {
    "value": "[listKeys(resourceId(parameters('eventHubResourceGroupName'),'Microsoft.EventHub/namespaces/eventhubs/authorizationRules', parameters('eventHubNamespace'), parameters('eventHubName'),  variables('eventHubAccessPolicies')),'2017-04-01').aliasPrimaryConnectionString]"
},

Anything have changed recently?

Hi @Madsteph We checked the release for both this action and azure cli but none of them released any new version in the timeframe discussed above. Are you still facing this issue?

Closing this issue due to inactivity. Please reopen if you are still facing this issue.


Added optional backendconfig resource for mercure

GCP load balancers by default terminate connections after 30 seconds. This can be changed by
adding a backendConfig resource and tweaking the timeoutSec property.
More info at: https://github.com/dunglas/mercure/issues/106 and
https://cloud.google.com/kubernetes-engine/docs/how-to/configure-backend-service

/assign @dunglas

/lgtm

thank you @Merlak


Metal: Multiview support

This PR adds multi-view support for the Metal rendering device driver.
Testing
GodotStereoDemo
A screenshot of XR enabled and rendering multiple views, thanks to @BastiaanOlij

Clearing attachments
It is not easy to test clearing a subset of an attachment when multi-view is enabled in Godot outside of XR, so I validated it by creating a multi-view frame buffer and clearing it and then validating the output in the Metal Debugger.
The following screenshot has the following properties:

A 1024x1024 frame buffer with a view count of 2.
Clear rect of { x=10, y=10, w=50, h=50 }
Clear colour of Color.AQUAMARINE
Clear depth of 0.5

In this screenshot, we can see the following:

Two views of a multi-view frame buffer, ❶ and ❷
The colour texture, ❸ and ❹, is cleared to aquamarine at the rectangle 10, 10, 60, 60
The depth texture, ❺ and ❻, is cleared to 0.5 at the rectangle 10, 10, 60, 60

The GDScript to set up the multi-view frame buffer:
var framebuffer2: RID
var clearColors2 := PackedColorArray([Color.AQUAMARINE])
var framebuf_texture
var d_framebuf_texture

func create_multiview():

	rd = RenderingServer.get_rendering_device()

	#  <<  --  FRAMEBUFFER  --  >>

	var attachments = []

	#  <<  -- COLOR  -- >>

	var tex_format := RDTextureFormat.new()
	tex_format.texture_type = RenderingDevice.TEXTURE_TYPE_2D_ARRAY
	tex_format.height = 1024
	tex_format.width = 1024
	tex_format.array_layers = 2
	tex_format.format = RenderingDevice.DATA_FORMAT_R8G8B8A8_UNORM
	tex_format.usage_bits = RenderingDevice.TEXTURE_USAGE_COLOR_ATTACHMENT_BIT | RenderingDevice.TEXTURE_USAGE_CAN_COPY_FROM_BIT

	var tex_view := RDTextureView.new()
	framebuf_texture = rd.texture_create(tex_format, tex_view)
	print("framebuffe texture : ", rd.texture_is_valid(framebuf_texture))

	var af := RDAttachmentFormat.new()
	af.set_format(tex_format.format)
	af.set_samples(RenderingDevice.TEXTURE_SAMPLES_1)
	af.usage_flags = tex_format.usage_bits
	attachments.push_back(af)

	#  WORKS, but is actually slower than with texture_get_data()

	#t2drd = Texture2DRD.new()
	#t2drd.texture_rd_rid = RID()
	#t2drd.texture_rd_rid = framebuf_texture

	#  <<  --  DEPTH  --  >>

	var dtex_format := RDTextureFormat.new()
	var dtex_view := RDTextureView.new()
	dtex_format.texture_type = RenderingDevice.TEXTURE_TYPE_2D_ARRAY
	dtex_format.height = 1024
	dtex_format.width = 1024
	dtex_format.array_layers = 2
	dtex_format.format = RenderingDevice.DATA_FORMAT_D16_UNORM
	dtex_format.usage_bits = RenderingDevice.TEXTURE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT
	d_framebuf_texture = rd.texture_create(dtex_format, dtex_view)
	print("depth buffer texture : ", rd.texture_is_valid(d_framebuf_texture))

	var daf := RDAttachmentFormat.new()
	daf.set_format(dtex_format.format)
	daf.set_samples(RenderingDevice.TEXTURE_SAMPLES_1)
	daf.usage_flags = dtex_format.usage_bits
	attachments.push_back(daf)

	# ---

	var framebuf_format := rd.framebuffer_format_create(attachments, 2)
	framebuffer2 = rd.framebuffer_create([framebuf_texture, d_framebuf_texture], framebuf_format, 2)
	print("framebuffer : ", rd.framebuffer_is_valid(framebuffer2))

and some code to clear it:
func draw_test():
	var dlist := rd.draw_list_begin(framebuffer2,
		RenderingDevice.INITIAL_ACTION_CLEAR, RenderingDevice.FINAL_ACTION_READ,
		RenderingDevice.INITIAL_ACTION_CLEAR, RenderingDevice.FINAL_ACTION_READ,
		clearColors2, 0.5, 3, Rect2(10, 10, 50, 50))
	rd.draw_list_end()

@BastiaanOlij and @RevoluPowered might be interested in this PR

Amazing stuart! I'm going to see how far I get with implementing XR_KHR_metal_enable ontop of this, that should be a great test for it.

Thanks!
I can't review the actual rendering code (it's beyond me) but I tested this with a simple XR project that I threw together using MobileVRInterface and it worked great in my testing on an M2 Mac mini!
However, with verbose output turned on, I'm getting is debug message spammed:

And in the console, it's spamming blank lines (probably one per frame?)
So, there's something wrong with that vformat(), but we probably shouldn't be printing something every frame anyway.

Thanks @dsnopek it's now removed!

Thanks @AThousandShips – resolved all your feedback

Thanks!


temp-jenkinsx-quickstart2 to 0.0.1

Promote temp-jenkinsx-quickstart2 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Merge v2 of spl

prating changes were made
Outcomes now check date ranges to either exclude or include rates
Example:
/pay-leave-for-parents/y/yes/2014-2-1/employee/employee/yes/yes/444-week/yes/yes/yes/444-week/yes
should have
Remaining weeks (between 6 April 2013 and 5 April 2014)	£136.78 per week or 90% of her average weekly earnings (before tax), whichever is lower
Remaining weeks (between 6 April 2014 and 5 April 2015)	£138.18 per week or 90% of her average weekly earnings (before tax), whichever is lower
for maternity pay

LGTM :+1:


extend/ENV: make 'passphrase' sensitive

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Keys containing passphrase are sensitive, this PR modifies extend/ENV.rb to ensure this.

Review period skipped due to critical label.

Thanks @nandahkrishna!


refactor(deps): awsim_sensor_kit_launch repo path update

Description
This PR updates awsim_sensor_kit_launch repo path after transfer to TIER IV's organization. Before it was in Robotec.AI's organization scope.
awsim_sensor_kit_launch pulling using vcs still works even without this PR due to GitHub transfer mechanics details (it automatically redirects from an old URL to a new one), but to keep order this PR updates the URL in the autoware.repos file.
Tests performed
I manually tested whether the new path was correctly pulled from the new location.
Effects on system behavior
Not applicable.
Interface changes
None changed.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

The change was already merged here https://github.com/autowarefoundation/autoware/pull/5403.


Missing cookie Same-Site attribute

Using this extension yields the following future deprecation warning:

Some cookies are misusing the recommended sameSite attribute
Cookie "flash" will be soon rejected because it has the Same-Site attribute set to "none" or an invalid value, without the "secure" attribute. To know more about the "Same-Site" attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

Would it be advisable to specify Same-Site: Strict on the cookie?

Sounds like a good idea. Can you think of some scenario when it can be problematic to have that as default?
I'll add it as an option anyway, so in the worst case, it can be modified.

I am unfamiliar with the behavior of this policy across subdomains.
There could be a scenario where a user expects a certain behavior with an app behind a reverse proxy.
E.g. account.example.com -> localhost:4000/account and store.example.com -> localhost:4000/store might not share flash messages, but are served by the same backend at different routes.

It seems like it should work with subdomains, according to this: https://andrewlock.net/understanding-samesite-cookies/
I don't get the warning when testing on the SvelteKit dev server, in what circumstances do you get it?


Update tryton 4 8

Motivation for this change
Minor bugfix release.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

@GrahamcOfBorg build tryton trytond

Success on x86_64-linux (full log)
Attempted: tryton, trytond
Partial log (click to expand)
warning: no files found matching '*/gtk-2.0/*'
warning: no files found matching '*.po' under directory 'doc'
warning: no files found matching '*.pot' under directory 'doc'
writing manifest file 'tryton.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK

Failure on x86_64-darwin (full log)
Attempted: tryton, trytond
Partial log (click to expand)
make[2]: *** [Makefile:1018: test-inline-pixbufs.h] Error 1
make[2]: Leaving directory '/private/tmp/nix-build-gtk+-2.24.32.drv-0/gtk+-2.24.32/demos'
make[1]: *** [Makefile:733: all-recursive] Error 1
make[1]: Leaving directory '/private/tmp/nix-build-gtk+-2.24.32.drv-0/gtk+-2.24.32'
make: *** [Makefile:625: all] Error 2
builder for '/nix/store/q3r1yrh0463vzjiamkkh7yqkf6iynm6l-gtk+-2.24.32.drv' failed with exit code 2
cannot build derivation '/nix/store/rx7kj50sf1jd8382knxaj2r1g0z4g9qj-python2.7-pygtk-2.24.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/qcn01pmx7mb3s9dd1jbnywyah2c12pws-python2.7-GooCalendar-0.3.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/r7k24dqxnahxvj9za21zx0rjfx2fiixx-tryton-4.8.2.drv': 3 dependencies couldn't be built
error: build of '/nix/store/r7k24dqxnahxvj9za21zx0rjfx2fiixx-tryton-4.8.2.drv' failed

Failure on aarch64-linux (full log)
Attempted: tryton, trytond
Partial log (click to expand)
   Compiling alloc v0.0.0 (file:///build/rustc-1.25.0-src/src/liballoc)
   Compiling panic_unwind v0.0.0 (file:///build/rustc-1.25.0-src/src/libpanic_unwind)
   Compiling alloc_system v0.0.0 (file:///build/rustc-1.25.0-src/src/liballoc_system)
building of '/nix/store/7yx1x18p9b8yng991pknrf46mz84qf44-rustc-1.25.0.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/d2wdy21mav0ws9irk2pflzjzjw4r4y8y-cargo-0.26.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/d7yxili5h426r90dk1lgsi4iakg39vlm-librsvg-2.42.4.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/xfwnpr79430fzf9whq9mzdmb2cfrm97y-icon-naming-utils-0.8.90.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/02bhmamd6srkvcvg05w9s4jm70nkq9rx-adwaita-icon-theme-3.28.0.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/4m89iybjbn36gxp7c334z02ka0r3yhny-tryton-4.8.2.drv': 2 dependencies couldn't be built
error: build of '/nix/store/4m89iybjbn36gxp7c334z02ka0r3yhny-tryton-4.8.2.drv' failed

Darwin and aarch64 failures look unrelated.


Detected as trojan

ChitChat getting tagged for Trojan:Win32/Bearfoos.A!ml on Windows 11 by Windows Defender

Not a huge surprise since I haven't started signing the binaries. I probably should do that at some point, in the mean time you can clone the project and run 'yarn tauri build' from the root of the repo.

Ya i built from yarn tauri dev to get it running from source :) I'd imagine eventually signing might help avoid the hit from defender.