Phase 2

[x] Update FAQ content
[x] New homepage styles & content
[x] Figure out what's happening with the workshop page
[x] Enter schedule details
[x] Check styling of schedule page
[x] Schedule should at least default to local time (maybe don't include the timezone switcher at all?)
[ ] Ensure service worker is up to date
[ ] Make sharp lines uneven (including top header)

@harleenkbatra08 @argyleink I couldn't find a design for the workshop page. Also, do we have enough content to justify one?
Now I'm waiting on the schedule so I can create the schedule page.

Here's the new homepage https://deploy-preview-354--cds2019.netlify.app/devsummit/

We'll have info like "Days, time, name of the speaker with title and
abstract of their workshops" so it merits a dedicated space for sure. Will
leave it up to you guys on whether y'all want it to be a dedicated page or
if you want to add info on the schedule page (note that the workshops are
happening BEFORE the event - Dec 7 & 8th)
On Mon, Nov 2, 2020 at 3:50 PM Jake Archibald<EMAIL_ADDRESS>wrote:

Here's the new homepage
https://deploy-preview-354--cds2019.netlify.app/devsummit/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/devsummit/pull/354#issuecomment-720555164,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHVD57OM27CEYHMST7W22TSN3ILLANCNFSM4THUAM3A
.

--

•  *Harleen Batra
•  *Developer PMM - Chrome
•  +44<PHONE_NUMBER>

Jake - looks like the copy for the "Hours" didn't get updated (still has
"workshops" mentioned etc). See here:
https://docs.google.com/document/d/1OiMKDpxpOYRZVueJNL9NsiZ5FkM7FPQv5wAdOnBF3rw/edit
On Mon, Nov 2, 2020 at 4:04 PM Harleen Batra<EMAIL_ADDRESS>wrote:

We'll have info like "Days, time, name of the speaker with title and
abstract of their workshops" so it merits a dedicated space for sure. Will
leave it up to you guys on whether y'all want it to be a dedicated page or
if you want to add info on the schedule page (note that the workshops are
happening BEFORE the event - Dec 7 & 8th)
On Mon, Nov 2, 2020 at 3:50 PM Jake Archibald<EMAIL_ADDRESS>wrote:

Here's the new homepage
https://deploy-preview-354--cds2019.netlify.app/devsummit/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/devsummit/pull/354#issuecomment-720555164,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHVD57OM27CEYHMST7W22TSN3ILLANCNFSM4THUAM3A
.

--

•  *Harleen Batra
•  *Developer PMM - Chrome
•  +44<PHONE_NUMBER> <+44%2020%203321%202414>

--

•  *Harleen Batra
•  *Developer PMM - Chrome
•  +44<PHONE_NUMBER>

@harleenkbatra08 ah, sorry. Done!

overall LGTM 👍
found only the following tiny nits and requests:

1. Let's get rid of the footer link area since it's only got 1 item in it

2. Squiggle effect missing from YouTube "ask a question" module

3. align chrome://about media to center

(nice to have) squiggle effect on the bottom of the main navbar

Adam - wdyt about the Workshops section? Should we add it to the Schedule
page or have a standalone page?
On Mon, Nov 2, 2020 at 6:02 PM Adam Argyle<EMAIL_ADDRESS>wrote:

overall LGTM 👍
found only the following tiny nits and requests:

Let's get rid of the footer link area since it's only got 1 item in it

[image: image]
https://user-images.githubusercontent.com/1134620/97900450-7f186a00-1cef-11eb-80be-0bb82abb3490.png
2. Squiggle effect missing from YouTube "ask a question" module
[image: image]
https://user-images.githubusercontent.com/1134620/97900808-12519f80-1cf0-11eb-8bec-9ce038babdc0.png
3. align chrome://about media to center [image: Screen Shot 2020-11-02 at
9 48 45 AM]
https://user-images.githubusercontent.com/1134620/97901207-b5a2b480-1cf0-11eb-8eef-f39679d1ce02.png

(nice to have) squiggle effect on the bottom of the main navbar

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/devsummit/pull/354#issuecomment-720633453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHVD5YXU2X3ZJI2HY5I3H3SN3X25ANCNFSM4THUAM3A
.

--

•  *Harleen Batra
•  *Developer PMM - Chrome
•  +44<PHONE_NUMBER>

I think it should go into the schedule overflow section

Ok. But we should probably just call that section "Chrome://workshops" to
avoid confusion. Thanks!
On Mon, 2 Nov 2020, 19:06 Adam Argyle<EMAIL_ADDRESS>wrote:

I think it should go into the schedule overflow section
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/devsummit/pull/354#issuecomment-720666726,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHVD52NMW4WQTJ44FWRLETSN37KZANCNFSM4THUAM3A
.

but it'll be sharing that section with "office hours" too and maybe live streams? it's def still an "event overflow" schedule area for times of stuff, unless i'm missing something about workshops and what they are in terms of CDS?

I sent an email with a link to the speaker/session information. Thanks.

@argyleink

Let's get rid of the footer link area since it's only got 1 item in it

It could have a schedule link in it for this phase btw. Happy to remove it though.

Squiggle effect missing from YouTube "ask a question" module

There isn't one in the design. What colour would you like it?

(nice to have) squiggle effect on the bottom of the main navbar

I'm not sure which navbar you're referring to? The links in the header?

but it'll be sharing that section with "office hours" too and maybe live streams? it's def still an "event overflow" schedule area for times of stuff, unless i'm missing something about workshops and what they are in terms of CDS?

Hmm.. fair point about having office hours in there as well, but there's nothing more than what we had on the homepage to add on this landing page. Also thinking about the flow:
On the home page we have chrome://hours and chrome://workshops, but when you land on their respective landing pages they'll be nested under a chrome://overflow?
Will the subsections within still be called chrome://workshops and chrome://hours? or just Workshops and Office Hours? Also, the landing page is the first time someone sees chrome://overflow? What is that? why wasn't it introduced on the home page. It's a slightly confusing message in my head.
But happy to let you design it first and we can take a look at how it flows.

@googlebot I consent. I submit.
On Tue, Nov 3, 2020 at 3:18 PM Surma<EMAIL_ADDRESS>wrote:

@googlebot https://github.com/googlebot I consent.
(now shut up)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/devsummit/pull/354#issuecomment-721192527,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHVD56X5UOHMW3CNDWT4ULSOANLPANCNFSM4THUAM3A
.

--

•  *Harleen Batra
•  *Developer PMM - Chrome
•  +44<PHONE_NUMBER>

Do it!

Let's get rid of the footer link area since it's only got 1 item in it

Schedule link makes it 2.. still a bit lonely. Hm, well, let's leave it in and add "schedule", we can grow into it as the event date get's closer.

Squiggle effect missing from YouTube "ask a question" module

That squiggle effect should be applied to every module's top and bottom. Goal is to show few hard lines or rounded corners, instead match the hand drawn style.

(nice to have) squiggle effect on the bottom of the main navbar

The hard line there on the bottom side of the main nav. Similar to how the modules have squiggly tops and bottoms, the navbar could/should have a squiggly bottom. low fg's tho at this point, but if you're already adding a few more squiggly edges, a navbar one would be nice.

On the home page we have chrome://hours and chrome://workshops, but when you land on their respective landing pages they'll be nested under a chrome://overflow

Overflow is a classic web term for anything where content can't fit the area. It's fun for a web summit because we do offer tons of additional content that doesnt fit into the schedule, hence it's overflowing! 🙂   I don't think it's confusing for a homepage to provide details under a specific header to itself (hi, i'm chrome://office-hours info), then be organized under a new header (overflow) alongside other related time sensitive content on another page.
The sub sections in overflow do retain their own headers, office hours and workshops will be clearly labeled and have a nice place to list their event details. Get an intro about the topic on the home page, get the actual hard details at the schedule page. I think it's best when homepages tease their subpages, like not give everything away. Keep me posted though, and def keep sharing sentiments! Helps keep me in check and thinking healthy about information architecture.

Gotcha Adam - do you think it makes sense to design that section real quick
or will Jake it on? The content for the workshops details is here:
https://docs.google.com/document/d/1OiMKDpxpOYRZVueJNL9NsiZ5FkM7FPQv5wAdOnBF3rw/edit?disco=AAAAHMHZBhw
And there's no more info for Office Hours beyond what we have on the
homepage
On Tue, Nov 3, 2020 at 4:17 PM Adam Argyle<EMAIL_ADDRESS>wrote:

Let's get rid of the footer link area since it's only got 1 item in it
Schedule link makes it 2.. still a bit lonely. Hm, well, let's leave it in
and add "schedule", we can grow into it as the event date get's closer.
Squiggle effect missing from YouTube "ask a question" module
That squiggle effect should be applied to every module's top and bottom.
Goal is to show few hard lines or rounded corners, instead match the hand
drawn style.
(nice to have) squiggle effect on the bottom of the main navbar
https://user-images.githubusercontent.com/1134620/98008437-5fde1300-1da9-11eb-93bd-6cc94a0ef268.png
The hard line there on the bottom side of the main nav. Similar to how the
modules have squiggly tops and bottoms, the navbar could/should have a
squiggly bottom. low fg's tho at this point, but if you're already adding a
few more squiggly edges, a navbar one would be nice.
On the home page we have chrome://hours and chrome://workshops, but when
you land on their respective landing pages they'll be nested under a
chrome://overflow
Overflow is a classic web term for anything where content can't fit the
area. It's fun for a web summit because we do offer tons of additional
content that doesnt fit into the schedule, hence it's overflowing! 🙂 I
don't think it's confusing for a homepage to provide details under a
specific header to itself (hi, i'm chrome://office-hours info), then be
organized under a new header (overflow) alongside other related time
sensitive content on another page.
The sub sections in overflow do retain their own headers, office hours and
workshops will be clearly labeled and have a nice place to list their event
details. Get an intro about the topic on the home page, get the actual hard
details at the schedule page. I think it's best when homepages tease their
subpages, like not give everything away. Keep me posted though, and def
keep sharing sentiments! Helps keep me in check and thinking healthy about
information architecture.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/devsummit/pull/354#issuecomment-721229040,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHVD52PI43K6PIAVFXQ2VLSOAUJLANCNFSM4THUAM3A
.

--

•  *Harleen Batra
•  *Developer PMM - Chrome
•  +44<PHONE_NUMBER>

@argyleink

The hard line there on the bottom side of the main nav. Similar to how the modules have squiggly tops and bottoms, the navbar could/should have a squiggly bottom.

Aha! Now I'm on the same page. I thought you meant the full colour banner squiggles, but now I realise you just want the sharp line to be uneven. Gotcha.

@harleenkbatra08 @argyleink happy with the schedule and workshops? https://deploy-preview-354--cds2019.netlify.app/devsummit/schedule/
I still need to fix those squiggles, but I'll do that now.

We also have workshop descriptions so would be nice to have those called
out. I assume Adam will look at that today?
On Wed, Nov 4, 2020 at 4:55 PM Jake Archibald<EMAIL_ADDRESS>wrote:

@harleenkbatra08 https://github.com/harleenkbatra08 @argyleink
https://github.com/argyleink happy with the schedule and workshops?
https://deploy-preview-354--cds2019.netlify.app/devsummit/schedule/
I still need to fix those squiggles, but I'll do that now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/devsummit/pull/354#issuecomment-721850363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALHVD56TUBLQHJIDS67TK33SOGBQBANCNFSM4THUAM3A
.

--

•  *Harleen Batra
•  *Developer PMM - Chrome
•  +44<PHONE_NUMBER>

Ok, all the design things are done my end. If there are significant changes it's going to take me some time to get to. I really need to get back to my other CDS deadlines.

rad work @jakearchibald, things look great, the squiggles everywhere is very charming.
to save you time, i can go in and add some of the changes harleen and I made in the design for workshops?

[ ] add description paragraph to workshop card
[ ] speaker names should be links to their social
[ ] add speaker avatar (i'm actually not sure about this one, i didnt find the assets in the spreadsheet and they add a little bit of noise just as much as they add a personal touch) maybe i'll try a small avatar instead of the bigger one i put in the designs..

PR is very close 🙂
Want me to hack a bit on it?

Feel free.to hack on it!
Note to self: I need to update the keynote description.

On mobile, it looks great.
On desktop though, "Description" seems tied to speakers. Can we move it a nit to the right?
Mobile

Desktop

@argyleink over to you for the above 😄

@beaufortfrancois i changed the header from "Description" to "Session Information" so it's not as specific about what it's headlining, then at mobile or desktop it can be appropriate for the layout. Thoughts?

@beaufortfrancois i changed the header from "Description" to "Session Information" so it's not as specific about what it's headlining, then at mobile or desktop it can be appropriate for the layout. Thoughts?

Works for me ;) Thank you!

Ohh good catch @beaufortfrancois!

@jakearchibald - the reminder card on each of the sessions, has a CTA that sends people to the 2019 registration form. We should update that to our 2020 registration form.

@jakearchibald could you please change Parisa's title on the Opening keynote session page to Chrome Browser, Google instead of Chrome Eng, Google? Thanks
https://developer.chrome.com/devsummit/sessions/chrome-and-the-web-in-2020/


Feature/openxr support

Re: https://github.com/icosa-foundation/open-brush/pull/799, I'm going to make the same PR here. Didn't remember that we also do a cleanup job here


update dependency versions

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Closed in favor of #7. Organization forks do not support rerendering.


Training Failed

The phenomenon is a purple box, and I don't quite understand it.
This is a new model. For example, I named it "CXK" in "Process RVC Dataset", then why would I be prompted that this model does not exist? This is obviously a new model that I want to train.
2024-09-09 05:00:50,933 - root - ERROR - Traceback (most recent call last):
File "E:\ComfyUI-aki-v1.3\execution.py", line 323, in execute
output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
File "E:\ComfyUI-aki-v1.3\execution.py", line 198, in get_output_data
return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
File "E:\ComfyUI-aki-v1.3\execution.py", line 169, in _map_node_over_list
process_inputs(input_dict, i)
File "E:\ComfyUI-aki-v1.3\execution.py", line 158, in process_inputs
results.append(getattr(obj, func)(**inputs))
File "E:\ComfyUI-aki-v1.3\custom_nodes\Comfy-RVC\custom_nodes\rvc_nodes.py", line 482, in train_model
assert os.path.isfile(model_path), f"Failed to train model {model_path}..."
AssertionError: Failed to train model E:\ComfyUI-aki-v1.3\models\RVC\cxk_48k.pth...
2024-09-09 05:00:50,934 - root - INFO - Prompt executed in 12.04 seconds
## Attached Workflow
Please make sure that workflow does not contain any sensitive information such as API keys or passwords.

{"last_node_id":18,"last_link_id":31,"nodes":[{"id":6,"type":"RVCNode","pos":{"0":945.4000854492188,"1":-349.9999694824219},"size":{"0":418.1999816894531,"1":166},"flags":{},"order":7,"mode":0,"inputs":[{"name":"audio","type":"AUDIO,VHS_AUDIO","link":12,"label":"audio"},{"name":"model","type":"RVC_MODEL","link":23,"label":"model"},{"name":"hubert_model","type":"HUBERT_MODEL","link":24,"label":"hubert_model"},{"name":"pitch_extraction_params","type":"PITCH_EXTRACTION","link":25,"label":"pitch_extraction_params"}],"outputs":[{"name":"VHS_AUDIO","type":"VHS_AUDIO","links":[13],"slot_index":0,"shape":3,"label":"VHS_AUDIO"}],"properties":{"Node name for S&R":"RVCNode"},"widgets_values":[0,"flac",true]},{"id":10,"type":"UVR5Node","pos":{"0":573.4000854492188,"1":-355.9999694824219},"size":{"0":315,"1":150},"flags":{},"order":4,"mode":0,"inputs":[{"name":"audio","type":"AUDIO,VHS_AUDIO","link":11,"label":"audio"}],"outputs":[{"name":"primary_stem","type":"VHS_AUDIO","links":[12],"slot_index":0,"shape":3,"label":"primary_stem"},{"name":"secondary_stem","type":"VHS_AUDIO","links":[14],"slot_index":1,"shape":3,"label":"secondary_stem"}],"properties":{"Node name for S&R":"UVR5Node"},"widgets_values":["UVR/HP5-vocals+instrumentals.pth",true,10,"flac"]},{"id":11,"type":"MergeAudioNode","pos":{"0":1431.4000244140625,"1":-346.9999694824219},"size":{"0":315,"1":166},"flags":{},"order":8,"mode":0,"inputs":[{"name":"audio1","type":"AUDIO,VHS_AUDIO","link":13,"label":"audio1"},{"name":"audio2","type":"AUDIO,VHS_AUDIO","link":14,"label":"audio2"},{"name":"audio3_opt","type":"AUDIO,VHS_AUDIO","link":null,"label":"audio3_opt"},{"name":"audio4_opt","type":"AUDIO,VHS_AUDIO","link":null,"label":"audio4_opt"}],"outputs":[{"name":"vhs_audio","type":"VHS_AUDIO","links":null,"slot_index":0,"shape":3,"label":"vhs_audio"},{"name":"audio","type":"AUDIO","links":[],"slot_index":1,"shape":3,"label":"audio"}],"properties":{"Node name for S&R":"MergeAudioNode"},"widgets_values":["None","median",true]},{"id":9,"type":"RVC-Studio.LoadAudio","pos":{"0":315.40008544921875,"1":-363.9999694824219},"size":{"0":210,"1":146},"flags":{},"order":0,"mode":0,"inputs":[],"outputs":[{"name":"audio_name","type":"STRING","links":null,"shape":3,"label":"audio_name"},{"name":"vhs_audio","type":"VHS_AUDIO","links":[11],"slot_index":1,"shape":3,"label":"vhs_audio"},{"name":"audio","type":"AUDIO","links":null,"shape":3,"label":"audio"}],"properties":{"Node name for S&R":"RVC-Studio.LoadAudio"},"widgets_values":["Tank - 千年泪.flac",44100,"image"]},{"id":5,"type":"LoadHubertModel","pos":{"0":-403,"1":402},"size":{"0":315,"1":58},"flags":{},"order":1,"mode":0,"inputs":[],"outputs":[{"name":"hubert_model","type":"HUBERT_MODEL","links":[28],"slot_index":0,"shape":3,"label":"hubert_model"}],"properties":{"Node name for S&R":"LoadHubertModel"},"widgets_values":["content-vec-best.safetensors"]},{"id":17,"type":"RVCProcessDatasetNode","pos":{"0":-8,"1":176},"size":{"0":337.6000061035156,"1":290},"flags":{},"order":5,"mode":0,"inputs":[{"name":"hubert_model","type":"HUBERT_MODEL","link":28,"label":"hubert_model"},{"name":"pitch_extraction_params","type":"PITCH_EXTRACTION","link":29,"label":"pitch_extraction_params"},{"name":"audio_processor","type":"AUDIO_PROCESSOR","link":null,"label":"audio_processor"}],"outputs":[{"name":"rvc_dataset_pipe","type":"RVC_DATASET_PIPE","links":[30],"slot_index":0,"shape":3,"label":"rvc_dataset_pipe"}],"properties":{"Node name for S&R":"RVCProcessDatasetNode"},"widgets_values":["cxk","蔡徐坤.zip","48k",12,3,0.5,0.9500000000000001,0.01,"image"]},{"id":3,"type":"LoadPitchExtractionParams","pos":{"0":-387,"1":130},"size":{"0":315,"1":202},"flags":{},"order":2,"mode":0,"inputs":[],"outputs":[{"name":"pitch_extraction_params","type":"PITCH_EXTRACTION","links":[29],"slot_index":0,"shape":3,"label":"pitch_extraction_params"}],"properties":{"Node name for S&R":"LoadPitchExtractionParams"},"widgets_values":["rmvpe+",true,0.75,48000,0.25,0.25,160]},{"id":18,"type":"RVCTrainParamsNode","pos":{"0":-45,"1":-152},"size":{"0":315,"1":250},"flags":{},"order":3,"mode":0,"inputs":[],"outputs":[{"name":"rvc_training_params","type":"RVC_TRAINING_PARAMS","links":[31],"shape":3,"label":"rvc_training_params","slot_index":0}],"properties":{"Node name for S&R":"RVCTrainParamsNode"},"widgets_values":[3,45,1,2,0,0,0,0,0]},{"id":15,"type":"RVCTrainModelNode","pos":{"0":380,"1":87},"size":{"0":506.4000244140625,"1":430},"flags":{},"order":6,"mode":0,"inputs":[{"name":"rvc_dataset_pipe","type":"RVC_DATASET_PIPE","link":30,"label":"rvc_dataset_pipe"},{"name":"rvc_training_params","type":"RVC_TRAINING_PARAMS","link":31,"label":"rvc_training_params"}],"outputs":[{"name":"model","type":"RVC_MODEL","links":[23],"slot_index":0,"shape":3,"label":"model"},{"name":"model_name","type":"STRING","links":null,"shape":3,"label":"model_name"},{"name":"hubert_model","type":"HUBERT_MODEL","links":[24],"slot_index":2,"shape":3,"label":"hubert_model"},{"name":"pitch_extraction_params","type":"PITCH_EXTRACTION","links":[25],"slot_index":3,"shape":3,"label":"pitch_extraction_params"}],"properties":{"Node name for S&R":"RVCTrainModelNode"},"widgets_values":["0",200,100,"pretrained_v2/f0G40k.pth","pretrained_v2/f0D40k.pth","pretrained_v2/D_DMR-V1-32k-f0.pth",false,false,false,true,true,50,1,1]}],"links":[[11,9,1,10,0,"AUDIO,VHS_AUDIO"],[12,10,0,6,0,"AUDIO,VHS_AUDIO"],[13,6,0,11,0,"AUDIO,VHS_AUDIO"],[14,10,1,11,1,"AUDIO,VHS_AUDIO"],[23,15,0,6,1,"RVC_MODEL"],[24,15,2,6,2,"HUBERT_MODEL"],[25,15,3,6,3,"PITCH_EXTRACTION"],[28,5,0,17,0,"HUBERT_MODEL"],[29,3,0,17,1,"PITCH_EXTRACTION"],[30,17,0,15,0,"RVC_DATASET_PIPE"],[31,18,0,15,1,"RVC_TRAINING_PARAMS"]],"groups":[{"title":"Model Trainer","bounding":[-413,45,1303,466],"color":"#b06634","font_size":24,"flags":{}},{"title":"Basic Voice Changer","bounding":[305,-438,1451,267],"color":"#3f789e","font_size":24,"flags":{}}],"config":{},"extra":{"ds":{"scale":1.1,"offset":[285.8904644461148,186.55384639246716]}},"version":0.4}

You are using a 40k pretrain to train a 48k model. Try changing to a 48k pretrain or lower your sr to 40k.


Better Showcase of Examples

Several months ago I read that MDL v2 is in development. I don't think it's been released yet - and I think you're working on it.
But I wanted to comment that MDL v1 is pretty amazing in itself. I also wanted to add that the elm-mdl project has done an amazing job showcasing in-depth examples of the work that you all have done on this project.
So, regardless of whether v2 of MDL does ship, please review the polished showcase of examples of elm-mdl. I often go to look over there for examples of what I can do with MDL.

MDL V2 isn't happening, MDL is being replaced by Material Components for Web

MDL is being ~replaced by~ Material Components for Web

MDL has evolved into Material Components for Web. The V2 base is now the foundation for MCW.
MDL is no longer actively maintained beyond a few lagging things to be done as there is no more time allocated to it internally since MCW is taking over the goals of MDL. We won't be making any major modifications to the examples, showcase, or microsite.
Thank you.


Generic Backends

As of v0.7.0, bevy_save simply saves files directly to the disk after serialization.
We should allow users to change how bevy_save saves and loads - perhaps they want to use a database or have other requirements like  on WASM.

Closed as completed via #b7f7fb


Support ECDSA SSH keys in Lagoon

The YubiKey 5 Series supports the following algorithms on the PIV smart card application.
RSA 1024
RSA 2048
ECC P-256
ECC P-384

https://support.yubico.com/support/solutions/articles/15000014219-yubikey-5-series-technical-manual
I'd like to use my Yubikey to interact with Lagoon via SSH, but only RSA and Ed25519 keys are supported by Lagoon. For various reasons RSA 2048-bit keys aren't great so it would be nice to add support for at least ecdsa-sha2-nistp256, and possibly ecdsa-sha2-nistp384.

Lagoon should also support the FIDO/U2F key types ecdsa-sk and ed25519-sk.
https://www.openssh.com/txt/release-8.2

As long as the key type is parsable by sshpk - it should be easyish to add in.
I'm not sure that the *-sk are supported by sshpk, so we may need to look to validate somehow else?

Looks like it isn't supported https://github.com/joyent/node-sshpk/issues/72

Even the non sk versions will make it easier to use Yubikeys.

ECDSA key support is now in Lagoon


Most recent RSSI in child/neighbour tables

This adds an entry to the child and neighbour tables for the most recent RSSI observed.
There is an accompanying  wpantund PR.

Codecov Report

Merging #1519 into master will increase coverage by 0.39%.
The diff coverage is 64%.

@@            Coverage Diff             @@
##           master    #1519      +/-   ##
==========================================
+ Coverage   69.28%   69.67%   +0.39%
==========================================
  Files         150      150
  Lines       20009    19512     -497
  Branches     2446     2390      -56
==========================================
- Hits        13863    13595     -268
+ Misses       5230     5033     -197
+ Partials      916      884      -32

Impacted Files
Coverage Δ

src/ncp/ncp_base.cpp
23.06% <ø> (-10.76%)
:arrow_down:

include/openthread/types.h
100% <ø> (ø)
:arrow_up:

src/core/thread/link_quality.cpp
88.76% <100%> (+0.52%)
:arrow_up:

src/core/thread/mle_router.cpp
80.21% <52.63%> (+0.18%)
:arrow_up:

src/core/thread/mesh_forwarder.cpp
74.04% <0%> (-0.33%)
:arrow_down:

src/core/thread/network_data_leader_ftd.cpp
68.22% <0%> (+0.23%)
:arrow_up:

src/core/thread/lowpan.cpp
93.01% <0%> (+0.71%)
:arrow_up:

src/core/thread/lowpan.hpp
97.36% <0%> (+10.52%)
:arrow_up:

Continue to review full report at Codecov.

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


Docs: CohereRanker

@AnushreeBannadabhavi will kindly create a draft.

@AnushreeBannadabhavi in case you want to help with this, check your Discord account for a message from me.
(I can share a draft with you).

Hi @anakin87!
I updated the draft. Let me know if any more changes are needed.

@dfokina FYI.

Hello @AnushreeBannadabhavi , @anakin87  - the docs are live: https://docs.haystack.deepset.ai/docs/cohereranker


Accept the merge request

@sharmistharanit  Can you please accept the merge request of mine. And please check it once. I have written python code for our file, run the unit test, documented it and submitted the executed time. I have done it only for practicing. I have not used einstein method, will do it later.

I am not sure how to merge. I will do it after class. @poojashresthacode

@sharmistharanit got any idea for merging?

yes, I have merged it already. please check it. @poojashresthacode


Under-sample check

Check for equality in count of majority class and second-most populous class in under_sample_balance, since we might get a "negative-length" mask otherwise, and break things...

Fixed in  63b30f3


PG - Hidden actions when browsing a database?

PG - In "No autocommit mode", when connecting to a machine, after double clicking on a table, the "Transaction indicator" says i have 1 uncommitted action. And i just connected and did onthing else than double-click on table name.
What could that be?

seems to be duplicate of #8136 .
closed as duplicate


--handle-extended-json-format support needs to be added to az [group] deployment validate commands

Just like we support this flag for the two create commands, we also need the same support for the two versions of validate
az group deployment validate --handle-extended-json-format
az deployment validate --handle-extended-json-format

Got it! We will do it soon.


source-bundle: don't include or build the "base image"

See original issue on GitLab
In GitLab by [Gitlab user @hashpling] on Aug 21, 2017, 17:51
Typically a BuildStream project will contain a low level dependency that is a base image containing a shell and low-level utilities required to build the project.
A source-bundle creates a tarball that can be used to build the project in a pre-existing environment. As it stands, attempting to build the "base image" in a source bundle will attempt to install the utilities over the top of the pre-existing environment.
I think it would be desirable to have an option that enabled excluding a .bst and everything below it the the dependency hierarchy from a source bundle. This would create source bundles that could be significantly smaller and didn't attempt to re-install base image artifacts.

In GitLab by [Gitlab user @hashpling] on Aug 21, 2017, 18:01
closed

In GitLab by [Gitlab user @hashpling] on Aug 21, 2017, 18:01
Looks like I need --except


Docker support

@kelonye Thanks for PR, I believe this very specific to a user chatterbot app. I felt this PR should goes chatterbot-tricks.
Any comments @gunthercox

I agree with @vkosuri. I like the idea of having these instructions available to point people to if they have questions. However I'm not sure how useful a Docker container is for the typical Python developer who wants to use or contribute to this project.

Just thought docker is preferred over virtualenv nowadays. Nice project btw ..

@kelonye if you are interested make use of please PR, please submit a PR chatterbot-tricks.


BUG - Collider on bubbles not becoming larger with bubble size increase

This is actually a problem on all of the bubbles. The collider seems to be smaller.

@wadek2 You need to remove collider on your Bubble prefab.


Sensors quickly become unavailable after HA restart

Hi - i am loving the integration.
I would love help with getting the sensors to be responsive.
I am able to connect to the Altitude, and send it commands etc. However, the sensors are unavailable/not being updated on the dashboard - and I'd love to be able to know what read what the current source is etc. I can change the source using the remote.send command... but tht source sensor doesn't update (even though the source changes). Same with volume etc.
Any help would be hugely appreciated.

Hey @BarneyHam , would love for you to help if you're willing. What firmware version are you running on your Altitude? I'm running 4.4.0, which is currently the latest. The sensors are working with my machine (see below). I followed the protocol specification here.
Keep in mind that sensors are pushed to the client up connection and as they change thereafter. So if there is anything preventing your Altitude from communicating with Home Assistant it will not receive the sensor updates. I am willing to bet that's what's happening.

Thank you.
Yes - firmware is 4.4.0.
So... I have discovered that I am getting responses on all the sensors except the source - which reads as "Unknown" (see below). The rest are changing as I make adjustments... but if I change the source, it stays as unknown? [But I can change the source.. both directly, and using the remote command through HA].

Got it. Then it seems like we aren't loading the sources properly upon connection. See this line. During my testing I noticed, at times, that all of the sources would not be sent. There are a couple of things we could do:

Provide 2 sensors -- source and source_index. The latter would always be set, and it would be an integer. The former would depend on loading all of the sources properly.
If the source index does not exist, we could attempt to reload the sources and try again.

The source_index should be very reliable though since it does not depend on mapping.

Yes - I'd be happy to just rely on an integer source_index, if that helps - I know separately what integer would map to which source.

Hi @binarylogic !
Would it be possible to give a timeframe for when you might be able to look at implementing the 2 sensor solution? I realise you will be really busy, and everything you are doing on this great integration is for the benefit of others... so that's not a chase. Just asking so I can pllaning for the HA installation I am doing. THANK YOU!

Hi @BarneyHam, I'll try to find time in the next week or so. I have a few other things that I want to improve. If you want it now, it should be relatively easy to add. You can basically copy what's going on with the other sensors.

Thank @binarylogic. I did try myself to figure it out from the raw code, but I'm afraid I got a bit lost! I'll wait for your update. Thank you.

Hi @binarylogic - so sorry to sound like I’m chasing, but do you know when you might be able to create the source index sensor? It will be hugely valuable for the HA installation I’m putting in right now.  Realise you are doing this entirely to help others - like me! Thank you!!

Hi @binarylogic - would hugely appreciate an update on whether you think you'll be able to get to this update to include a more stable source_index sensor. It's not something I can see how to add to the code myself :( And just need to know if I need to try to find a different solution to the installation needs. Thank you so much. Barney

Hi @BarneyHam, apologies, this has been an extremely busy week. I will take care of this tomorrow morning.

Thank you, @binarylogic, I do appreciate you helping here so much.

Hi @binarylogic  - I am guessing that setting up a source_index sensor isn't as straightforward as hoped.
My only other thought, given that presets seem to be reading correctly, is to create presets to match each source (duplicating standard set up),  and then use the preset sensor as an indicator of the source.  If there are any other solutions you can suggest please let me know.


🐞 C++ "<<" attempts to autocomplete even after disabling completing quotations

Description
When writing C++ code, the operator "<<" is commonly used. However, when typing in "<<", it attempts to autocomplete it into "<>", probably due to HTML support.
To Reproduce

Open a new C++ file
Type "<<"
Problem shown

Expected Behavior
There should be a setting that disables this, or a "per file" setting. Instead of keeping it throughout the text editor, only use that autocomplete if the file is an HTML, JSX, svelte, etc. file.
Version Information
CodeEdit: 0.0.3-alpha 37
macOS: 14.4 Dev Beta (23E5191e)
Xcode: 15.3 beta 3 (15E5194e)
Additional Context
No response
Screenshots
No response

The <> autocomplete has been removed in a recent pr on CodeEditSourceEditor here. It will be pushed up to the main app on the next release.


Add Vale to lint the docs

The docs team has discussed using the Vale  linter to point out style, grammar, and spelling errors. For consistency and ease of use, we should include Vale in the repo in some way.
Option 1:
Add the Vale files contributors need (.vale.ini, a styles directory, the Microsoft and suse-vale-styleguide packages), plus instructions in the README on installing and using Vale to detect possible errors.
Option 2:
Investigate adding a Github Action so that all contributions get passed through Vale: https://github.com/errata-ai/vale-action
Before we try either, we should also make some adjustments to the existing base of the Microsoft style guide (which Rancher docs primarily follow, with the SUSE guide as a supplement) to match the Rancher docs' implementation -- for example, the Rancher docs use title case instead of sentence case in headings.

2 things to note:

The existing https://github.com/errata-ai/vale-action action is pretty simple to set up on a repo, but it doesn't scale well to a repo of our size. When I was testing the action on my fork, the check would take 30-40 minutes for a single page.

This is what the results look like from running https://github.com/errata-ai/vale-action on a PR:


In the spec draft missed (Async)DisposableStack.prototype.constructor

That's at least strange since it's defined on all built-in constructors. It's already an issue, Chromium 133:

We had to unship anyhow for some last-minute crashers, so should be fine to change.


Parse markdown outputs in notebooks along with the rest of the markdown on a page in order to programmatically generate MyST content

Jupyter notebook cells can produce text output that is specific to markdown (text/markdown). It'd be useful if MyST could parse this output along with the rest of the markdown in the notebook. This would allow for programmatic generation of notebook content, and along with the {embed} directive could allow you to nicely stitch together MyST content via any Jupyter Kernel.
For example:

As an example, the MyST-nb Sphinx extension documents this functionality here.
An example from our docs where this would be useful
In the admonitions docs here:
https://github.com/executablebooks/mystmd/blob/c0f51ee51890158081736722cb01bcf510699786/docs/admonitions.md?plain=1#L34-L98
We have a big list of all the different types of admonitions for demonstration.  If we parsed Markdown outputs as MyST, we could replace it with something like:
inner = []
for admonition in ["note", "tip", "warning"]:
	s = """
	````{tab-item}
    ```{%s}
    This is an %s admonition.
    ```
    ````
    """ % admonition
	inner.append(s)
template = """
`````{tab-set}
%s
````` % "\n".join(inner)
"""

continuing #1559 here:
An example for this would be the following:

Right now I have a nice notebook which analyzes exactly one physical structure.
The analysis results in several graphs / tables / images / ..., each generated by a code cell

My problem now is, that I have 2-20 different structures. For each I get graphs based on the same code.
Right now the only solution is to put them all below each other, leading to a quite long doc.
Better would be to have

tabs in which I can select which structure I want to see

and/or

a table which has only the main results (maybe broken down in a number or two), but on click on a row, I see a detailed analysis for that structure.

A simplified example might be statistics about bank accounts (not scientific, but less abstract).

It's simple to write a notebook which produces graphs / tables, ... based on an account number
Now I have 5 accounts and want this one notebook to do the same analysis with all of them. An overview would be the balance of each one in a table. But I'd like to be able to switch tabs/expand rows of the different account to see the detailed graphs.

For different use-cases different approaches might be best. I'm wondering what might be possible:

have on the complete notebook level tabs, i.e. execute the notebook like github actions matrix with different parameters
have tabs within each output (which might be syncronized when switching (?))
Having outputs combined with hidden content, e.g. a table in which i can expand individual rows to see more details.

Workaround: Write to temporary text files and then use {include}
I discovered this workaround today, it's a bit cludgy but isn't too hacky. It takes advantage of the fact that code cells are executed before a page is parsed by MyST. This means that you can do something like the following:
## Generate content with Jupyter

```{code-cell} python
from pathlib import Path
p = Path("../_build/txt/tmp.txt")
p.parent.mkdir(parents=True, exist_ok=True)
_ = p.write_text("- **Testing**\n- Testing two\n- Testing three")
```

And then include it in the page with MyST markdown like so:

```{include} ../_build/txt/tmp.txt
```

This will:

Generate some MyST Markdown in Jupyter
Write it to a .txt file
And later in the page, in MyST MD, we reference that .txt file with an {include} statement

So the file is first executed, the txt file is created, and MyST then includes it

@choldgraf we should also make it possible to include files with .myst.json extensions, to support pulling in AST.

Yeah I was thinking that too. It also made me wonder if the notebook cell MyST support could be more like the plugin structure, rather than making it language specific.
For example, a cell tag like output-myst or output-myst-ast that would tell MyST to parse stdout as MyST (similar to what executable plugins do).
Does that make sense? If so I can update the issue body to reflect that suggestion.

@choldgraf the natural way to do this would be to define a MIME type for MyST AST, and recognise it in our transforms!

That sounds like a good idea. Though if it were the only way,  then each kernel would need to have a package that outputs MyST right? The benefit of tags and stdout is that anybody in any language could use it without developing anything specific.

Although we don't need a package for this (certainly with ipython, you can just use display), I'm curious to understand your thought process - are you picturing a user printing stringified json to the stdout? Or myst markup, I.e text/markdown?

My idea was inspired by the way that you handled "black box" outputs for the executable plugins infrastructure. So below I'll share a Python and an R cell that would generate either MyST MD or MyST AST. At build time, if the tag was identified on a cell, then any text/plain output (or however stdout gets logged) would be parsed differently. Without those tags, the output would just be parsed like any other stdout.
Python - MyST MD
```{code-cell} python
:tags: output-myst-md
print("- **Bolded** list item")
```

Python - MyST AST
```{code-cell} python
:tags: output-myst-ast
ast = {
      "type": "list",
      "ordered": false,
      "spread": false,
      "children": [
        {
          "type": "listItem",
          "spread": True,
          "children": [
            {
              "type": "strong",
              "children": [
                {
                  "type": "text",
                  "value": "Bolded"
                }
              ]
            },
            {
              "type": "text",
              "value": " list item"
            }
          ]
        }
      ]
    }
print(ast)
```

I love the idea of parsing plain/MysT mardkown proper, as it's very easy to generate from many tools. In my code I very often have something like
from IPython.display import display, Markdown
md = lambda s: display(Markdown(s))

and I use md(x) everywhere as a "print markdown" shorthand to generate legible, pretty reporting with zero fuss.
Having the ability to properly handle that (along perhaps with a new MyST object in IPython.display) would be very useful, I think.

I decided to create a separate issue to track generating MyST AST directly from cell outputs, since that might be an easier short-term solution and get us part of the way there:

https://github.com/jupyter-book/mystmd/issues/1633

@rowanc1 @stevejpurves @fwkoch @choldgraf
I can't seem to paste these in Discord right now. Here are some quick discussion videos (~2min each) about the work I've been doing on Markdown output parsing:
https://github.com/user-attachments/assets/e0d61b90-2148-42e5-b433-1fddbad6f301
https://github.com/user-attachments/assets/a2d69933-1d2b-4c2a-8c83-3aba3b8f7c03
The PR I'm most excited about is currently https://github.com/jupyter-book/mystmd/pull/1671.
Need to dash, no rush here, but it would be good to book in a video meeting at some point.

I'm very far from an expert in the nuances of the AST-consuming tools that may already exist, but FWIW I found your argument compelling, @agoose77 (and thanks for those explanatory videos!).
A mechanism to tag "escape hatches" that transparently allow for third parties to opt-in with their own implementation and otherwise pass through silently is pragmatic and useful (I seem to recall the C++ standards group having a similar mechanism for compiler extensions, though my memory could be off).
It gives room for experimenting with tradeoffs and side effects before settling into a solution that gets baked into the AST proper, which seems like a very important benefit. Thanks!


Where to put notify view function?

In the documentation it states that a function called show_me_the_money(sender, **kwargs) should be added to the project in order to handle the POST request sent by PayPal on completion of payment. However, the documentation fails to describe where that function should be placed. Should it be placed in the views.py file of the current project, or should there be another python file created just for that function?

The documentation doesn't mention it because you may put it wherever you like that makes sense for your project. Please see the Django docs in signals - https://docs.djangoproject.com/en/dev/topics/signals/ . There is a section "Where should this code live?"
Hope that helps.


Validation error messages for stream fields not shown

When trying to save a page with an invalid stream field (e.g. required blocks missing or less / more blocks than allowed inside the stream field), the error message/s is/are not shown

This might arise from this: in 'classic' wagtail, the error messages (block_errors) are contained in the 'sequence-container' (admin\templates\wagtailadmin\block_forms\sequence.html) which does not appear with wagtail-react-streamfield installed.

Fixed by bf57687e1bd9e10bb788a6ab7c2c9be1cc4c472e.


Add missing "author" field to Information Sources

... then later on switch to Relaton proper.
from discussion with @maccraymer

There are other missing attributes for information sources (citations) in addition to the author. See the current ISOGR and data entry spreadsheet for all the attributes that are presently used.
-Mike


Ignore .jfm files in Visual Studio

Reasons for making this change:
.jfm files have started blocking checking for .sqlproj projects in Visual Studio. .jfm files are a new file-type created by the Microsoft ESENT database engine - this is a recent improvement only in Windows 10 Anniversary update. As the SSDT .sqlproj type in Visual Studio uses this engine for .dbmdl metadata files, and this file is locked by the user, this currently blocks users from checking into Git repositories.
This fix helps mitigate this by avoiding checkin of this file type.
Links to documentation supporting these rule changes:
An example of this issue is this StackOverflow post
 which shows the issues cause by this, and an explanation of the cause. At present, the file type is not documented by the ESENT team, so there is no official doc covering this.
Disclosure: I work for Microsoft on the SSDT team shipping .sqlproj support into Visual Studio.

@kevcunnane thanks for the extra information!

that's nice
I've had a PR waiting to be merged for the past couple of months (since beta of win10 anniversary) to add this extension to the ignore list
at least it's in now...

Hi,
I am facing the same issue.
I have added the *.jfm extension in gitignore file under User-specific files and Other ClientBin/ tag
as mentioned below.
User-specific files
*.jfm
Others
ClientBin/
*.jfm
but it doesn't work.
Could anyone please let me know what I am missing.
Any help is highly appreciated.

it should work @aabhishek1
could you find a way to verify your gitignore?

Thank You TheBeardedLlama for you reply, could you please let me know I could I verify my gitignore.

if you're using VS, then there's a plugin that @madskristensen has developed called .ignore
https://github.com/madskristensen/IgnoreFiles
it will show you what's matching and what's not

In case someone is looking for this and their .jfm file was not removed after it was added to gitignore run this: git rm --cached *.jfm and it will fix the problem (right-click in the directory and select Git Bash Here and run it).


Irish translation back to 100%

messages.po: 1239 translated messages.

If it helps expedite the merge, three experienced Irish translators have already reviewed these changes.


Support message type transition phase 2

Command line flag is --emit-old-didcomm-prefix, default to new, always accept either

Codecov Report

Merging #705 into master will decrease coverage by 0.00%.
The diff coverage is 98.93%.

@@            Coverage Diff             @@
##           master     #705      +/-   ##
==========================================
- Coverage   99.02%   99.01%   -0.01%
==========================================
  Files         253      254       +1
  Lines       13686    13680       -6
==========================================
- Hits        13552    13545       -7
- Misses        134      135       +1

Addresses https://github.com/hyperledger/aries-cloudagent-python/issues/694


rkt: Specifying/Overriding Environment Variables and Ports at Runtime

It would be more secure if rkt only took explicit environment variables via args for run/enter. As a file or multiple tags:
rkt enter f4c3 /cmd/to/run --env PORT=8080 --env LOG=/tmp/log (available for just this app)
or
rkt run f4c3 --env-file ./environment.txt (this environment is global in the container)
environment.txt (should be simple, explicit with no expansion):
PORT=8080
LOG=/tmp/log
Ports
As a side note, how do ports tie into this? The main use case we are solving for is hosting many web/tcp containers for micro services on a single box.  The port to bind on can't be reserved in advance.  They all would be living behind a load balancer/router (nginx).  A manifest takes named ports and from a security perspective only those named ports should be able to be opened from the container. At the same time we should be able to pass in overrides. Passing in a port as an environment variable shouldn't work because from a security perspective the manifest dictates the port namespace. So to override we could do this (keeping with the example above:
rkt enter f4c3 /cmd/to/run --port www=8080 --env LOG=/tmp/log
"www" is the named port in the manifest.  rkt should fail if www is not a valid port in the manifest.
Handling Port Collisions
After merging passed in port assignments with those in the manifest, rkt should check at startup if all ports specified are open.  It should fail if the ports are not available.  An --ignore-port-assign flag could be used to avoid failure.  It would then be the responsibility of the app to handle that case.  This is useful in cases where a hot standby is running.  It would periodically try to bind on the service port.
Conclusion
I think with clean environment and port overrides Rocket is solid.  If we keep with ideas around 12 Factor applications and micro services we don't need anything more.  No fancy networking model as well.  The host will be running a router to direct traffic to particular ports that "it assigns".

The environment variable support has landed in https://github.com/coreos/rocket/pull/597, and ports will be addressed in #624, moving to there.

Sweet!


Twitter announced recently new API paid version, can you tell us how we migrate from here

Hi,
I am in this space. Currently from code base i see that we are using this library and thinking whether we might be impacted with Twitter recent API changes.
We are happy to take paid version if required for our application internally talking to procurement team, but can guide me how do I migrate it using same library .
I think current library is using 1.1 version which is deprecated?

gp


Structs to define inference/generative methods

This draft PR is about defining a structure for defining the inference/generative method.
The approach I've taken involves defining an EpiAwareMethod struct (as well as creating an abstract type hierarchy in EpiAwareBase).
The EpiAwareMethod defines a sequence of optimization methods (defined as either MAP or VI) followed by a single sampling method. The concept here is that the optimizations methods pass results to the next one sequentially before supplying initialization information to a sampler (e.g. NUTS).
I have added a ManyPathfinderMethod struct into EpiInference to give an example; however, I'm saying the scope of this PR is structure rather than the implementation.

I think this is a good structure to scaffold implementation methods onto.
Thoughts @seabbs ?

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

Project coverage is 98.26%. Comparing base (43c448a) to head (020b4f1).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #155      +/-   ##
==========================================
+ Coverage   98.24%   98.26%   +0.02%
==========================================
  Files          25       26       +1
  Lines         228      231       +3
==========================================
+ Hits          224      227       +3
  Misses          4        4

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