New artwork: Deno Cooky, by DaimonGh0st

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

Do I need to do something else?

Thanks for the PR. We don't use this repository anymore, as the website went closed-source, so we wont accept any new artworks submissions.


Segmentation fault when running inside a container

Describe the bug
I recently encountered a segmentation fault error when running tarpaulin (version 0.18.0) with multi-threaded tests inside an LXC container. This looked very similar to issue #190, as it appeared randomly. I realized that tarpaulin shows the following warning every time when starting a test:
WARN cargo_tarpaulin::process_handling::linux: Failed to set processor affinity EINVAL: Invalid argument

I tried to prevent any actual parallel execution by setting the processor affinity manually with taskset -ac 0 cargo tarpaulin, which also failed with the message Invalid argument.
Looking at the affinity mask of existing processes, it showed that all processes in this container were running with the mask 0xefb5420050 (containing 16 bits set to one for 16 cores). This might be caused by the fact that only some cores are forwarded inside the container.
Setting the mask to one or two of those cores made the segfault disappear (e.g. with taskset -ac 4,6 cargo tarpaulin). Setting it to three or more cores though made the problem reappear.
Looking at the tarpaulin code at https://github.com/xd009642/tarpaulin/blob/develop/src/process_handling/linux.rs#L85 the warning and the issues might be fixable by checking an existing affinity mask and setting it to only one of those existing cores. I'll try this out today or tomorrow to see if it consistently solves the segfault issues.
Although I was wondering why this affinity setting is needed in the first place. It seems to me that tarpaulin only works correctly if no code is actually executed in parallel, enforced by the processor affinity. Is this an intended limitation or just a workaround for deeper issues?
To Reproduce
I used the following example to produce the segfaults. They happen at around 25% of the time. lib.rs

So I'm not 100% if it is needed, I either saw some code or documentation from something like strace or gdb that lead me to think it could fix an intermittent segfault other people were reporting that I couldn't reproduce. But tarpaulin has moved on a lot since then so I think it might just be safer to remove it... Either the checking existing affinity or just removing it would be solutions in my book, just need to do some more thorough tests to make sure it doesn't break anything


Search Bar Collapse

Description
Search bar is getting collapsed from end when typed something
Screenshots
https://user-images.githubusercontent.com/104709529/199681355-09b5d452-e98c-4d1e-9516-f7baee8a9c57.mp4
Additional information
No response

@Debajyoti14


[Feature Request]: Introduce metrics for number of backed and included candidates

Component
Other
Feature Description
We need a metrics that would reflect:

The total number of backed candidates inherents in our blocks
The total number of included candidates inherents in our blocks
The total number of blocks we procuded

References and additional Information
No response

I suggest to add three more metrics:

blocks without included candidates
blocks without backed candidates
blocks without both included and backed candidates at the same time


FeatureRequest: download wiki

Would it be possible to also download the wiki files. We are using the wiki to (obviously) store project documentation, would be super nice to interface with that also via CLI

We'd have to look into how to access the current state of the wiki pages. I assume they look similar to other files that are part of a project.
One way I could imagine this to look like is that we treat it as another storage provider. So you end up with a new sub-directory called wiki/ which contains text files corresponding to each page.

Wikis behave just like files in the api, but they are currently read only. I think your idea having a wiki provider is a good one.


More idiomatic scala code

PR improves readability of code base by introducing scala pattern matching idioms and couple code formatting issues.

@iamrohit @vrajat what do you think about PR?

@iamrohit @vrajat any chance to look at the PR? It has been open for two weeks now...

@venkata91 thanks for the feedback!


Add quotation marks for generated code

This fixes an issue where the generated code for Javascript XHR and Fetch are missing quotation marks preventing the user from easily coping and pasting the code.

Hey @johnhenry,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: ee3a5860-e728-11e9-8e12-4bc655cb216a


update grid to cropped items after clicking patches button

What changes are proposed in this pull request?

Currently, patches views don't crop to the bounding box:

with this change:

How is this patch tested? If it is not, please explain why.
(Details)
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[ ] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

@kaixi-wang I tested this locally and it runs fine, but I also do not see the error you're fixing without this change locally either? So question is: does it make sense to you that this change is required for Teams but not OSS?


Question

What library gd.py use to get requests from the gd server?
Is it requests, aiohttp, or something else?

aiohttp https://github.com/nekitdev/gd.py/blob/main/gd/http.py

Thanks for replying, @sSolsta. Closing this issue as completed.

did u forget to close it

Looks like I did, haha :)


Bump identity-apps console version to 2.10.6

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/7123706096

Closing as already there's a PR: https://github.com/wso2/product-is/pull/18474


Fix masking of ragged indices that was causing an out of bounds error.

Some meshes (e.g. QU240km) don't do masking of ragged indices with 0. Instead they use number of indices+1 as the invalid value, which can produce out of bounds errors. This PR adds a check if that the case and if so set the out of bounds indices to -1.
Also moved the zero indexing to the minimal dataset construction function to ensure it's done and done uniformly across arrays.

This probably should be a patch release, bumping up the version to 0.1.1. Should I do that as part of this PR?

That's up to you.  I tend to prefer making a separate PR to update the version unless there are no other PRs since the last release.

Gotcha. I'll open a new PR for updating the version to 0.1.1. I think I'll opt for just a tag after that, and wait for a new release to include the datasets module, as part of 0.2.0.


Transparent taskbar only when no maximized window

It would be nice if the taskbar with transparent styling enabled would loose it's transparency, if there's a window maximized on the current monitor. (In that case the taskbar doesn't blend in the background anyway, it would also fix #49 in that case.)

I second this.
It would be nice if the same options would be available as from TranslucentTB.
Now I'm using both programs to get my preferred look.


[Manual] Add manual test plan for vm-import with EFI mode and secure boot

What this PR does / why we need it:
This PR is used to add manual test plan according to the latest vm-import-controller enhancement issue
https://github.com/harvester/harvester/issues/5846
Test Scenarios

For OpenStack:

BIOS based VM Migration
EFI Based VM Migration
EFI Based VM with secure boot migration:
Using a custom storage class

For VMware:

BIOS based VM Migration
EFI Based VM Migration
EFI Based VM with secure boot migration:
Using a custom storage class

Special notes for your reviewer:
Tested on the local hugo server, image can be loaded well.
Additional documentation or context
Related task ticket:
https://github.com/harvester/tests/issues/1509

Thanks for this addition @TachunLin ! :+1:


Reactions backend: make endpoints more REST-ful

Adding a reaction is now a PUT request to
/messages/<message_id>/emoji_reactions/<emoji_name>
Similarly, removing a reaction is now a DELETE request to
/messages/<message_id>/emoji_reactions/<emoji_name>
This PR changes the url, updates the views and tests, and also adds a test for invalid emoji when removing reaction

Automated message from Dropbox CLA bot
@arpith, it looks like you've already signed the Dropbox CLA. Thanks!

@timabbott @kracekumar could you take a look?

@arpith  Looks good to me.

This looks great!  Merged, thanks @arpith!

Thanks @timabbott :)


pull request for e2e test at 12/18/2016 06:15:21

:white_check_mark: Validation status: passed
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.


authorization levels

@chrisjsewell writes

Some possible levels of access:

Data retrieval (could have this allowed by default)
Sensitive data retrieval ??
Element (node, group, computer, etc) additions
Element deletions
Submitting processes

I personally think we can start just with keeping the routes that are open in the aiida-core REST API open, and protecting any functionality that modifies the DB.

As discussed during the meeting with @NinadBhat and @chrisjsewell , we will start with a binary authorization approach (some routes behind authentication; authentication provides access to all routes).
Happy to modify if strong use cases for a more fine-grained authorization appear.


bug: mesh.updateIndices() behaves differently according to the passed typed array

https://playground.babylonjs.com/#A4V5U3
The user can't know how the indices array is converted in the underlying index buffer but he's allowed to pass the type he wants to updateIndices()
If the passed type differs from the generated one under the hood, it leads to weird shapes

Not a bug for me. There is an expected format and you have to stick with it.
Not sure to know how we can help on that.
This is an advanced function expecting 16 bits indices unless you create a mesh with more than 65536 vertices

ok, I reacted to fast by putting a bug here
Let's inform the user in the API doc that he needs to pass the same type in the parameter than the one of existing indices array
ok for this ?
(and let's close this ;-) )

sure thing


How do you capture the selected file or folder in a parent controller $scope variable?

I am trying to use angular-filemanager to browse for files and then to select a file or folder, populate it in my application textbox. Any ideas on how to do this? I am trying to use pickCallback but haven't been quite able to figure it out yet.
PS: I am relatively new to angular, so apologies if the answer is obvious.
Thanks!
Vishal.

Never mind, I figured it out. Thanks!


Weave Net logo update

Please can the logo used for Weave Net be updated to this one?

I can provide an Illustrator .ai file instead or as well, if that is preferable.

Is it possible to get a Weavenet logo that is different from Weaveworks? That will be a showstopper if (as I hope) Weavenet becomes a CNCF project.
Cc @monadic

The logo that was used in the landscape is old & was only used for a short period, so we'd prefer it changed to the corporate one if that's the only Weaveworks thing in the landscape.
Completely understand (& agree) that the corporate one can't be used if it becomes a CNCF project - we'd be happy to contribute a neutral logo if/when that happens.

OK.
--
Dan Kohn<EMAIL_ADDRESS>Executive Director, Cloud Native Computing Foundation https://cncf.io/
tel:+1-415-233-1000
On Fri, Aug 18, 2017 at 9:46 AM, Pid<EMAIL_ADDRESS>wrote:

The logo that was used in the landscape is old & was only used for a short
period, so we'd prefer it changed to the corporate one if that's the only
Weaveworks thing in the landscape.
Completely understand (& agree) that the corporate one can't be used if it
becomes a CNCF project - we'd be happy to contribute a neutral logo if/when
that happens.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cncf/landscape/issues/145#issuecomment-323358089, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AC8MBngRhhkAb3UnwuPw-mxyz-WJE1TEks5sZZW7gaJpZM4O7jHf
.

Hi @pidster, we currently have that corporate one used in the Monitoring (for Weave Scope). We also currently have Weave Flux in Service Management, and you found Weave Net. Please let me know your preference within the next two days and we can update for the upcoming version.
We'd also be happy to contribute a possible logo (either through our LF designers or by kicking off a 99designs campaign) for the prospective project, working with your team and direction throughout the process. Let me know if you'd like to take us up on that offer.
cc: @monadic

Please update Net logo to this (for now, until the other submission happens).
weave-sq-logos-net.ai.zip

@pidster we try to avoid having many products/projects from the same company to begin with, having the same logo only difference being "net" vs "cloud" (#146) underneath makes it very glaring.

@shawnpreissner I read the guidelines as meaning one-per-box was OK. (Net will change again soon, but we haven't been able to address that yet).
We thought, as Netflix also has multiple projects under one brand, we'd copy how their logos are presented.
Our normal logos place the product word to the right of the 'weave' prefix, but this makes it too small to read. Getting sign off for these square variants was quite a task, I don't know how else I can solve this & keep everyone happy.

Thanks @pidster, closing as this update was included in the most recent version https://github.com/cncf/landscape#current-version


Hi, it seems I can't access the optical flow frames

Hi Rong,
It seems I can't access the optical flow frames in the driver. Could you give me the access right?
best,
John

Hi,
thanks for your interest. Pls try it again. It should work now.
Best,

Appreciate your timely reply! It works now.

Hi Rong,
It seems I can't access the optical flow frames in the driver. Could you please check it again?
Best,

Hi Rong,
It seems I can't access the optical flow frames in the driver. Could you please check it again?
Best,

Hi Oliveyo,
please try again, it should work now. Thx!
Best,

Thanks, I can open it now.

Hi, the link to the optical flow images seems to be inaccessible, please could you check

Hi, the link to the optical flow images seems to be inaccessible, please could you check

Dear ae208gpu,
please try again. It should be accessible now.
Best,


Dealing with carb_ratio time slots in autotune Phase 3

In https://github.com/openaps/docs/blob/master/docs/docs/Customize-Iterate/autotune.md at Phase 3 / Step 3 / carb_ratio, documentation on how to deal with a carb ratio that depends on time slots is missing.

Hi Luuc - the documentation states that Autotune does not support multiple
carb ratios at this time. Please PR to make that more clear if you felt you
missed it/got to that step without knowing it.
On Sun, Aug 20, 2017 at 6:17 AM Luuc<EMAIL_ADDRESS>wrote:

In docs/docs/docs/Customize-Iterate/autotune.md at Phase 3 / Step 3 /
carb_ratio, documentation on how to deal with a carb ratio that depends
on time slots is missing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openaps/docs/issues/1009, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHH0hb8UBJU0XI6yeHj9d9pH3vxcaPv6ks5saDHTgaJpZM4O8nI3
.

--
Dana Lewis | http://OpenAPS.org | http://DIYPS.org http://diyps.org |
@DanaMLewis http://www.twitter.com/danamlewis |
http://www.linkedin.com/in/danalewis
"Doing something for someone else is more important than anything you would
do for yourself."

I see, okay will do soon!


Loadout v2.3.0 Pull Request

Merging all changes through Loadout v2.3.0.

Going to pull this in preparation for deployment to the main site (hopefully in a few days). Thanks for your work so far. 👍


ODS > Component > Lists

Lists
Requirement
As a developer
I want to insert a List
So That I will get this ready to use component compatible with Orange design specifications and a11y requirements
DSM reference
General description
the page will propose to the user describe the component and allow to see the implementation in action
UI specifications
Anatomy
Component
For the component description please refer to the DSM updates
App Page

title: "List"
image: DSM_[Android-Components]_[Lists].jpg
Text: intro text in the DSM
Core field:

the page will propose in the same page the selected variants

Variants
Image + Title+ Subtitle
Variant displayed with an action icon at the right
This list should display the sliding control mechanism
Image + Title
Variant displayed with an action icon at the right
Title + Subtitle
Variant displayed with an action icon at the right
Title
Variant displayed with an action icon at the right
Title with Label and action icon
Title list variant displayed with both the action icon and the label at the right
Title with Label
Title list variant displayed without the action icon at the right but with the label instead
Title with 2 icons
Title list variant displayed with 2 action icons at the right
States
Component

Selected
Unselected

Internationalization
---an example should be provided if possible--- (this will not be added in the first iteration of the creation of this component)
UX specifications
Interaction

All:

on an unselected item the content is switched to the selected item's content page

Touch:

Nothing Specific

Keyboard:

Nothing specific

Animations

NA

Accessibility
Visual Accessibility

taken into account within the design

Usage Accessibility

(?) Focus order - the items of the list one by one. In each item's the user should switch from the title >subtitle > action icons or label
(?) Focus loss expected behavior - NA
(?) Screen Reader - read only the Label alt description and not the icon
(?) Switch Control

Technical specifications
Implementation tasks
Related tasks

@B3nz01d The link to the DSM reference is not good, can you give me the right one, please ?

Problem with Voice Over

Problem with Voice Over

We need to create an issue for voice over on this component because nothing was done.

We need to create an issue for voice over on this component because nothing was done. -> #212

Ok thank you Ludovic
I assign you the ticket, then assign it to me once ok

https://github.com/Orange-OpenSource/ods-ios/issues/298


Add visual regression testing to storybook

Visual regression testing can be a huge benefit ensuring that different layouts work for different device sizes and ensuring that stylings in your application are not breaking. It provides a great way to ensure that a component appears the way it should rather than asserting specific CSS rules, selectors, and HTML markup.
Visual Testing Reference
GOAL
The goal here is to make use of storybook addons and integrate visual testing for our components.

Depends on https://github.com/wayfair/awesome-learning/issues/158


Consolidate allocs and conversions

This PR draft is a reply to
@asn-d6 "That said, I would be curious to see how a PR for this one would look like." from the discussion in #234.
Note that this PR-draft is based on #235 just to avoid conflicts, it completely removes the variable from the code anyway.
It may be helpful for review to look at the 2 commits 3ba09df and 9e5de9a separately.
Personally, I find the code actually cleaner that way (less duplication, clearer semantics), but I have no strong feelings about this PR draft.

Note that this does not actually touch the public API.

Did an initial review here. Thanks for the code!
I'm pretty sure that the code is correct, but I'm debating whether the changes are worth incorporating or not.
I think while we are evaluating this PR, we can ignore the performance benefits of this approach as memory allocation is generally fast, and the speed difference between five allocs of total size N, versus one alloc of total size N is probably on the order of nanoseconds, whereas we are dealing with millisecond ops here.
Focusing on the simplifications of this PR, I can definitely see how make_claim_from_blob_kzg_proof() allows us to avoid code duplication in the two functions where it's used. However that comes at the cost of introducing a new custom struct (not in the spec) and a new non-trivial function (not in the spec).
All in all, I think I don't have a strong opinion about these changes. I would opt to not merge this PR due to being close to the freeze but I can certainly be persuaded towards the other direction.

After thinking about it some more, I'm not really a fan of this idea. I made an alternative version, but I don't like it either. My main problem is that it differs from the spec too much. Unless there's a big performance improvement, I think I'd rather keep what we already have.

And I don't see any noticeable performance improvements. The differences are within the margin of error.
Current
Benchmark/VerifyKZGProof-20              	    1174	   1020153 ns/op
Benchmark/VerifyBlobKZGProof-20          	     740	   1612213 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=1)-20         	     714	   1677503 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=2)-20         	     452	   2652104 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=4)-20         	     261	   4589978 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=8)-20         	     141	   8442185 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=16)-20        	      72	  16187426 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=32)-20        	      37	  31674580 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=64)-20        	      18	  62640058 ns/op

Consolidated Allocations
Benchmark/VerifyKZGProof-20              	    1167	   1023479 ns/op
Benchmark/VerifyBlobKZGProof-20          	     741	   1607667 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=1)-20         	     714	   1677561 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=2)-20         	     452	   2647706 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=4)-20         	     261	   4584247 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=8)-20         	     141	   8461970 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=16)-20        	      73	  16197958 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=32)-20        	      37	  31807864 ns/op
Benchmark/VerifyBlobKZGProofBatch(count=64)-20        	      18	  62744236 ns/op


Replace leveldb not found errors in package localstore

I am working on a version of bee that uses BadgerDB instead of LevelDB for localstore to reduce the disk io requirements (https://github.com/mrsimicsak/bee/tree/badgerfrompr75). While working on changing over I discovered that localstore checks for returned leveldb.ErrNotFound errors, making it dependent on LevelDB where it otherwise wouldn't be.
Creating a shed.ErrNotFound and using it in place of the LevelDB.ErrNotFound would make it easier to swap database backends and eliminate localstore's dependency on LevelDB.

Thanks. Dust settled a bit after the launch now. We'll look into this.

@mrsimicsak I'm closing this since the PR went stale and this is not time well spent considering we are looking into doing significant changes in our storage abstractions.


Post-merge review of #1419 "Universal tensor transform feature"

All review comments must be resolved (the most important ones are marked with :red_circle:).

https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1419#pullrequestreview-920308419

/cc @aska-0096 @shaojiewang @DrizztDoUrden
@junliume Currently this is of high_urgency

@aska-0096 could you follow up with Artem's comments in #1419 asap?

@atamazov @junliume I send the PR #1481 to cover these review suggestions, hope it works.

Is there any specific reason for not basing this on TransposingSolver?https://github.com/ROCmSoftwarePlatform/MIOpen/blob/0c6bdeb3ff46505d65f69a8c6e72ec0eef29835a/src/include/miopen/utility/transposing_solver.hpp#L411
That removes a whole lot of duplications and doesn't require any modification to the transposed solver.
Example of usage: https://github.com/ROCmSoftwarePlatform/MIOpen/blob/0c6bdeb3ff46505d65f69a8c6e72ec0eef29835a/src/include/miopen/pooling/solvers.hpp#L140
If your kernel is universal, just replace this pseudo-solver: https://github.com/ROCmSoftwarePlatform/MIOpen/blob/0c6bdeb3ff46505d65f69a8c6e72ec0eef29835a/src/include/miopen/utility/transposing_solver.hpp#L164

@aska-0096 could you take a look and respond to @DrizztDoUrden 's inquiries above? Thanks!

@DrizztDoUrden Sorry for late reply. I'd like to give three main advantage in tensor reorder solver.
Performance:

In tensor reorder method, we re-utilize the exist batched-transpose kernel for higher performance. You can refer to performance data in PR# 1419.
All Tensor reorder kernel is compiled in compile-time, and chosen via specific reorder sequence(i.e. Reorder NCHW to NHWC is (0,2,3,1)). This kind of design will decrease the run-time workload.

Completeness:
1.We support various of datatype, int8, fp16, fp32 and fp64.

Can we close this one since #1481 is merged?

@junliume This can be closed after resolving all comments in

https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1419#pullrequestreview-920308419

7 comments from https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1419#pullrequestreview-920308419 are not resolved yet; couple of them are red.

Description updated with https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1481#pullrequestreview-936525781.

Updated in #1515. @atamazov

Description updated. @junliume Currently this is of normal_urgency


netlify needs critters

Fixes #23.

@all-contributors please add @icy-meteor for bug

@all-contributors please add @icy-meteor for bug


[Feature request] Stack for simple sensor

I think many newbies would welcome a possibility to implement their own end node (sensor) for testing purposes. Would it be possible to provide an example implementation of z-stack firmware with minimal end node code, serving e.g. as a simple demo sensor (e.g. on/off switch)... I'm not familiar with z-stack API and it is kind of hard to grasp for beginner and such example end node would be a great showcase which could be further extended and developed into many different custom zigbee nodes.. Is there any similar project already available?

Yes search for/have a look at pvto.switch and DiYruz or something closely to this (it is mentioned in the 1.6.0 release logs AFAIK).


Implement more CoAP Options

Observe
Max-Age
Uri-Query

I used these in my application, might be useful for others too.

Also, I've noticed that you must call option append functions in order by their CoAP code.
This works:
otCoapHeaderAppendObserveOption(&reqHeader, 0); otCoapHeaderAppendUriPathOptions(&reqHeader, "path"); otCoapHeaderAppendMaxAgeOption(&reqHeader, 1234); otCoapHeaderAppendUriQueryOption(&reqHeader, "key=value");
This doesn't:
otCoapHeaderAppendUriPathOptions(&reqHeader, "path"); otCoapHeaderAppendUriQueryOption(&reqHeader, "key=value"); otCoapHeaderAppendObserveOption(&reqHeader, 0); otCoapHeaderAppendMaxAgeOption(&reqHeader, 1234);
Observe and Max-Age are not added because kCoapOptionObserve, kCoapOptionMaxAge < kCoapOptionUriQuery.
Should I create a [known-]issue for this?

Codecov Report

Merging #1362 into master will increase coverage by 0.31%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1362      +/-   ##
=========================================
+ Coverage   68.68%     69%   +0.31%
=========================================
  Files         171     171
  Lines       26854   26892      +38
  Branches     3375    3377       +2
=========================================
+ Hits        18446   18557     +111
+ Misses       6985    6924      -61
+ Partials     1423    1411      -12

Impacted Files
Coverage Δ

include/openthread-coap.h
100% <ø> (ø)
:white_check_mark:

src/core/coap/coap_header.hpp
100% <ø> (ø)
:white_check_mark:

src/core/openthread.cpp
46.12% <ø> (+11.12%)
:white_check_mark:

src/core/coap/coap_header.cpp
55.71% <ø> (-12.31%)
:x:

src/ncp/ncp_base.cpp
38.27% <ø> (-0.47%)
:x:

src/core/thread/mesh_forwarder.cpp
75.99% <ø> (ø)
:white_check_mark:

src/core/thread/mle_router.cpp
79.68% <ø> (ø)
:white_check_mark:

src/core/thread/mle.cpp
80.68% <ø> (+0.21%)
:white_check_mark:

src/core/net/ip6.cpp
56.82% <ø> (+0.24%)
:white_check_mark:

third_party/mbedtls/repo/library/bignum.c
51.09% <ø> (+0.41%)
:white_check_mark:

... and 9 more

Continue to review full report at Codecov.

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

Sorry I didn't have time to do the changes yesterday, as I said I would. I'm pushing them now. Fixed comment alignment and changed code to be more concise. Unit tested it locally on my machine, seemed to work. Currently don't have access to real setup to sniff if everything is good over-the-air, but I'm pretty sure it will be. Please check if I haven't missed anything.

@jwhui P.S. this solution saved 38 bytes for Cortex M0+ processor :)

@GiedriusM, thanks for the update!
BTWk looks like clang static analyzer is failing on you latest update:
coap/coap_header.cpp:186:44: warning: The left operand of '-' is a garbage value
    uint16_t optionDelta = aOption.mNumber - mOptionLast;

Also, make sure to run astyle before pushing your changes.

Left an embarrassing mistake. Rushing, while switching between different repos and environments does not help :) Hopefully, it's all good now. Tested in over the air setup.


Feat: Improve isLoading to prevent loading for undefined

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/51333
PROPOSAL: N/A
Tests

Open any workspace
Enable Company Cards
Navigate to Company Cards and see that no loading spinner is there

[x] Verify that no errors appear in the JS console

Offline tests

Same as tests
QA Steps

None

[X] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[x] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

https://github.com/user-attachments/assets/d52d9dc5-0d73-4c91-abf2-305734463d96

There is loading indicator when opening the page on a fresh sign in, is this expected?

On the Expensify Card page you mean?

@waterim could we easily clean that up here too?

@joekaufmanexpensify Sorry, missed this comment, sure, will update today

All good. And sounds great. TY!

@joekaufmanexpensify Issue is a bit weird as this loading is an issue with some onyx update, On an initial loading all useOnyx hooks are returning an undefined for a moment and a correct data after meanwhile in companyCards everything works correctly and data is coming from onyx as it should be

Got it. Is it easy to fix that?

@joekaufmanexpensify Cant understand why its happening, we dont have any resets, but it still shows undefined for some reason, still researching

@joekaufmanexpensify
Okay, finally I was able to understand why its happening, sorry for taking more time, I was thinking totally in a different way
This loading is happening on the Expensify because useOnyx is not delaying rendering of the component, same as in company cards, but for companyCards we are getting cardFeeds  in "WorkspaceInitialPage" initializing data for this key which we are using in companyCards for updating brickRoadIndicator
But  for expensifyCards both cardSettings and cardList are not initialized in other places and thats why for the initial render it shows loading inidicator for a moment while it getting data from onyx store as useOnyx has 'isLoading' inidicator during that time.
Im not sure do we need to fix it to be honest, as its an expected behaviour from useOnyx, but 2 solutions exists:

replace useOnyx with withOnyx, as withOnyx waits for data to be loaded, but its deprecated
to use cardSettings and cardList in WorkspaceInitialPage for brickRoadIndicator, but we didnt have it earlier and I don't know do we need it or not

Let me know your thoughts on this please

Is one of those solutions viable? The loading indicator does look kind of odd. If we can fix this without much effort, that would be solid IMO.

@joekaufmanexpensify it will be hacky or with using a deprecated withOnyx, only these 2 solutions I can see here
But I can add a brickRoadIndicator as we don't have and for this will use both those onyx keys, if its fine I will go with this one

@joekaufmanexpensify @getusha Updated

But I can add a brickRoadIndicator as we don't have and for this will use both those onyx keys, if its fine I will go with this one

Mind clarifying a bit more about what this solution means? I'm not sure I understand

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Bump solium version to 1.1.7

Bumps the solium version.

I have the big "flatten the deps" PR coming in that does this, so going to close this one.


Some converter tests are flakey

About one in 20 times, test will complain about misshapen weights, but when rerun, the test passes

https://github.com/NVIDIA/TRTorch/pull/15 addresses the flakiness in the linear test


Gmdx support 💡[FEATURE] ...

https://www.moddb.com/mods/gmdx

Or https://www.moddb.com/mods/deus-ex-revision

Hi,
This is beyond the feature scope of the renderer.
Technically, it should already work, if it's not the case it's likely due to modifications these mods made to the game engine.
You may want to contact the modding teams and ask if they can look into it.
If there is a bug with the renderer that prevents it from working with these mods, I will happily accept a merge request.


ha-camera-stream is only rendering preview image

This was a red herring, the camera in question did not have go2rtc setup correct in my frigate.yml.


Found out Pretrained Weight in README.md is crashed

I've got errors for importing weights from ./pretrained/resnet_38d.params and ./pretrained/od_cam.pth.
I think the pretrained weights given in README.md is crashed, because I solved the problems for importing the weights from original resnet38 pretrained one.

Yes, I have also encountered this problem. How can I fix it?

Yes, I'm having this problem too, how can I fix it?


Searching for multiple citation keys on quick search box

Hello,
Following on issue #502, would it be possible to add a way to retrieve multiple items from multiple citation keys?
For instance: a search string containing "gupta_review_2013,holt_aircraft_2016,sampigethaya_future_2011" would return all the three items associated with them.
You'll need to look for the comma ',' to know when one citation ends and the next one starts.
I believe you could add an additional menu item to the search dropdown menu ("Title, Authors", "All Fields and Tags", "Everything").

Can you try this?
There's no (sensible) way to add new items to the search dropdown. To get citekey search into the existing search box required quite invasive runtime-patching of Zotero; the search infrastructure of Zotero really doesn't expect to be extended.

closing for inactivity

Ouch, this is one of the things I hate in zotero.  I.e. something similar to
'search title, abstract and keywords' of any bibliographic database.
On 8 August 2017 at 17:56, retorquere<EMAIL_ADDRESS>wrote:

Closed #649
https://github.com/retorquere/zotero-better-bibtex/issues/649.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/retorquere/zotero-better-bibtex/issues/649#event-1197613698,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQUNuZy3EXybWDYzHjEePb3m6ADKbtwoks5sWJMhgaJpZM4MFNmU
.

multi-key search is implemented in #759


OneOf Select Items

if you could paste your schema here, I could have a look

sry my question was non sense :) can you please close it?

no problem :)


style: fixed Accordion icon position

Jira ticket
https://jira.zopa/browse/ZUI-13

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Making phone directory

Describe the project you want to add with tech stack
Making phone directory using c++

@TusharKesarwani @MohitGupta121 @pranjay-poddar assign please


feat(keymaps): Allow setting custom keymaps.

This PR adds options to the setup function that allows the user to create custom keymaps. Relevant parameters are type hinted. The changes should be non-breaking.

Hi! Thanks for doing this. I only have two problems regarding this PR:

I didn't want to add any configuration options, but that being said keymaps are the most reasonable ones to add. I'll have to think a little bit about this.
Your solution broke the vim/window resize handling.

I see. Thanks for pointing out the resize issue. I didn't notice this and I'll have a look at it. Regarding the configuration options, I believe having the keymaps as options is (subjectively) easier to write compared to APIs to be used with vim.keymap.

Thanks for this!


Delete old tesla from account

Is your feature request related to a problem? Please describe.
I have a new tesla and am unable to delete the old one which is not connected to my account anymore.
I can delete the app and add it again but would be nice to have a delete option for the old car.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Delete option
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Delete the integration and reinstall it.
Additional context
Add any other context or screenshots about the feature request here.
None.

Unfortunately, this is a HA issue. If you no longer have a car, the integration no longer provides any data for it. The fact HA keeps the entity means you have to manage it in HA. You should be able to delete the device there.
Reinstalling the component basically wipes everything and then you just see what is current. But again, that's a HA design decision.


RayJob: don't delete submitter job when ShutdownAfterJobFinishes=true

Why are these changes needed?
When a RayJob is configured with ShutdownAfterJobFinishes=true, Kuberay will immediately delete the associated RayCluster and submitter job once the job completes. Users can tune how long the cluster and submitter job stays around with TTLSecondsAfterFinished. Note that the RayJob resource itself is never deleted automatically, this always needs external action to be removed.
Even without setting TTLSecondsAfterFinished, there is very little reason to delete the submitter job. The submitter job usually contains the most useful logs for the job and is not using any cluster resources once completed. In addition, the submitter job will always be cleaned up when the RayJob is eventually deleted due it's owner reference back to the RayJob. This PR proposes to never delete the submitter job once a job completes when ShutdownAfterJobFinishes=true. The only exception is for suspended RayJob where the submitter job needs to be stopped.
Related issue number
Closes https://github.com/ray-project/kuberay/issues/1832
Checks

[X] I've made sure the tests are passing.
Testing Strategy

[X] Unit tests
[X] Manual tests
[ ] This PR is not tested :(

@kevin85421 thoughts? This is an alternative approach to https://github.com/ray-project/kuberay/issues/1832 which I think is much cleaner and more practical for most users.

I prefer to continue deleting the submitter's Job to free up computing resources. For RayJob, I expect users to submit and then not have to worry about it further. The TTLSecondsAfterFinished is utilized to ensure that logging tools have sufficient time to persist the logs. I don't expect users to need to read the logs in the Kubernetes Job.

A scenario where users need to access the Kubernetes Job arises when the Ray job fails, and they need to troubleshoot. However, in most cases, the driver log isn't very useful for troubleshooting once the RayCluster is no longer present.
If users wish to use RayJob for iterative Ray script development (submit, debug, fix, submit again), they should set ShutdownAfterJobFinishes to false. In addition, we don't encourage users to use RayJob for iterative development.

I agree that there will definitely be many cases where you need the entire cluster to stay around.

I don't expect users to need to read the logs in the Kubernetes Job.

This part I'm not sure about, it depends on the Ray job right?
My main point is that a Kubernetes Job that is "Completed" does not actually use any compute resources. The node frees up requested resources for the submitter job once the job completes anyways. If the submitter job is not using any resources when completed, why delete it if it could contain useful logs?

Here's an example using a local Kind cluster with one node:
$ kubectl get no
NAME                 STATUS   ROLES           AGE   VERSION
kind-control-plane   Ready    control-plane   17m   v1.24.0

While the job runs, you can see the requested resources on the node:
  Namespace                   Name                                                       CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                                       ------------  ----------  ---------------  -------------  ---
  default                     kuberay-operator-5987588ffc-tz46f                          100m (0%)     100m (0%)   512Mi (0%)       512Mi (0%)     16m
  default                     rayjob-sample-5tzjl                                        500m (0%)     1 (0%)      200Mi (0%)       1Gi (0%)       8s
  default                     rayjob-sample-raycluster-5dl9l-head-bj84k                  20 (15%)      0 (0%)      0 (0%)           0 (0%)         43s
  default                     rayjob-sample-raycluster-5dl9l-worker-small-group-76brh    200m (0%)     1 (0%)      256Mi (0%)       256Mi (0%)     43s
  kube-system                 coredns-6d4b75cb6d-g4bgd                                   100m (0%)     0 (0%)      70Mi (0%)        170Mi (0%)     16m
  kube-system                 coredns-6d4b75cb6d-xgkg8                                   100m (0%)     0 (0%)      70Mi (0%)        170Mi (0%)     16m
  kube-system                 etcd-kind-control-plane                                    100m (0%)     0 (0%)      100Mi (0%)       0 (0%)         16m
  kube-system                 kindnet-sb2vz                                              100m (0%)     100m (0%)   50Mi (0%)        50Mi (0%)      16m
  kube-system                 kube-apiserver-kind-control-plane                          250m (0%)     0 (0%)      0 (0%)           0 (0%)         16m
  kube-system                 kube-controller-manager-kind-control-plane                 200m (0%)     0 (0%)      0 (0%)           0 (0%)         16m
  kube-system                 kube-proxy-r8w7n                                           0 (0%)        0 (0%)      0 (0%)           0 (0%)         16m
  kube-system                 kube-scheduler-kind-control-plane                          100m (0%)     0 (0%)      0 (0%)           0 (0%)         16m
  local-path-storage          local-path-provisioner-9cd9bd544-d772w                     0 (0%)        0 (0%)      0 (0%)           0 (0%)         16m

With ShutdownAfterJobFinishes=true, the submitter job is left in "Completed" state and the RayCluster is deleted:
$ kubectl get po
NAME                                READY   STATUS      RESTARTS   AGE
kuberay-operator-5987588ffc-tz46f   1/1     Running     0          18m
rayjob-sample-5tzjl                 0/1     Completed   0          85s

And checking the node again, the submitter job is not taking any resources:
  Namespace                   Name                                          CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                          ------------  ----------  ---------------  -------------  ---
  default                     kuberay-operator-5987588ffc-tz46f             100m (0%)     100m (0%)   512Mi (0%)       512Mi (0%)     18m
  kube-system                 coredns-6d4b75cb6d-g4bgd                      100m (0%)     0 (0%)      70Mi (0%)        170Mi (0%)     18m
  kube-system                 coredns-6d4b75cb6d-xgkg8                      100m (0%)     0 (0%)      70Mi (0%)        170Mi (0%)     18m
  kube-system                 etcd-kind-control-plane                       100m (0%)     0 (0%)      100Mi (0%)       0 (0%)         18m
  kube-system                 kindnet-sb2vz                                 100m (0%)     100m (0%)   50Mi (0%)        50Mi (0%)      18m
  kube-system                 kube-apiserver-kind-control-plane             250m (0%)     0 (0%)      0 (0%)           0 (0%)         18m
  kube-system                 kube-controller-manager-kind-control-plane    200m (0%)     0 (0%)      0 (0%)           0 (0%)         18m
  kube-system                 kube-proxy-r8w7n                              0 (0%)        0 (0%)      0 (0%)           0 (0%)         18m
  kube-system                 kube-scheduler-kind-control-plane             100m (0%)     0 (0%)      0 (0%)           0 (0%)         18m
  local-path-storage          local-path-provisioner-9cd9bd544-d772w        0 (0%)        0 (0%)      0 (0%)           0 (0%)         18m

My main point is that a Kubernetes Job that is "Completed" does not actually use any compute resources. The node frees up requested resources for the submitter job once the job completes anyways. If the submitter job is not using any resources when completed, why delete it if it could contain useful logs?

Good point. I didn't realize that when a job enters 'Completed,' it doesn't use any compute resources. In that case, this PR makes sense to me.


Is this project dead?

Last release was in 2018 and there are many open issues.

Yeah, same question.  what is the status of this project?

I'm interested in this question too

I have some assistance now and some time of my own to contribute. I made a release and I am updating the CI to use github actions


Update opentelemetry-sdk-testing to 1.4.0

Updates io.opentelemetry:opentelemetry-sdk-testing from 1.3.0 to 1.4.0.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.opentelemetry", artifactId = "opentelemetry-sdk-testing" } ]

labels: test-library-update, semver-minor

Superseded by #390.


cargo install --git hardcodes master, doesn't use the default remote branch (HEAD)

Problem
cargo install --git uses the master branch by default. A better default would be to use the default remote branch (aka HEAD), which is typically master but more people have been setting to other names recently.
Steps
cargo install --git https://github.com/sunshowers/non-master-branch

The output is:
    Updating git repository `https://github.com/sunshowers/non-master-branch`error: failed to find branch `master`

Caused by:
  cannot locate local branch 'master'; class=Reference (4); code=NotFound (-3)

Possible Solution(s)

Use the default remote branch (a minor BC breakage, but I'd be surprised if it broke anyone).
If the BC breakage is too severe, at least warn about this.

Notes
Output of cargo version:
cargo 1.44.0 (05d080faa 2020-05-06)

CC #8364

CC #8364

Thanks! Looks like this is addressed by that PR.

Duplicate of #3517

Closing as duplicate of #3517


Discuss workflow for code generation

Update:
I am closing this issue for the following reasons:

Masterbots Search branch is no longer part of the current path.


[e2e]: generic schedule main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3209045003
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Sat Oct  8 04:03:55 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3209045003
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Sat Oct  8 17:30:59 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3212849423
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.schedule.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.schedule.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Sun Oct  9 04:32:08 UTC 2022
Tests are passing now. Closing this issue.


App cards show "Connect" links for services that are already connected

http://bit.ly/zUhwzq

this is done on uimerge. I'll close when I merge to master.

done.


[Request] QR code integration

When sending a file, a QR code should appear . The package qr_flutter: ^4.0.0 can create this code easily.
When receiving a file, (on mobile platforms at least) the app should open the camera and search for qr codes. If a qr code is scanned, then it should use that as the code. I'm unsure how to implement this, it's possible the above package has that feature too.
This would make it much easier to send files to phones from anywhere.

There is a URI scheme specified for the classic file-transfer protocol, which should be followed also for QR codes: https://github.com/magic-wormhole/magic-wormhole-protocols/blob/main/uri-scheme.md
(This would also allow Destiny to associate to the wormhole-transfer: scheme in case the QR code is scanned by e.g. a built-in scanner)

There is proposed support from the CLI client as well: https://github.com/magic-wormhole/magic-wormhole/pull/555#issuecomment-2477056406


Move server to its own module and clean up dependencies

Reopening #1114

Codecov Report

Merging #1116 into master will increase coverage by 0.91%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #1116      +/-   ##
============================================
+ Coverage     87.13%   88.04%   +0.91%
+ Complexity      262       85     -177
============================================
  Files           107       69      -38
  Lines          1384     1046     -338
  Branches         92       71      -21
============================================
- Hits           1206      921     -285
+ Misses          131       88      -43
+ Partials         47       37      -10

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 09b63f7...1544cb5. Read the comment docs.

@tkrop sorry for the late turnaround, finally got a chance to make the changes - ready for another review. Thanks!

Thanks for the contribution. Have just seen it and will have a look soon.

:+1:

:+1:


Fix: Healthcheck neo4j don't keep output file of wget

Description
Motivation and Context
Docker healthcheck creates a new file in the neo4j docker every 10 seconds. To avoid filling the /var/lib/neo4j folder with thousands of files, the commit redirects the output of wget to /dev/null.
How Has This Been Tested?
The docker containers was removed to trigger docker compose up and check if the docker is in the healthy status
Types of changes

[ ] Chore (a change that does not modify the application functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] Documentation updates are needed, and have been made accordingly.
[ ] I have added and/or updated tests to cover my changes.
[ ] All new and existing tests passed.
[ ] My changes include a database migration.

recheck

One of our engineers pointed out that -o /dev/null might be better served as -q. Thoughts @nodauf?

Yes, totally agree! I did the commit on PR.

Thanks for the update! Pulling this in as soon as checks pass.

@all-contributors please add @nodauf for

@all-contributors please add @nodauf for code


The packages toggle disappeared mysteriously from Coder

Fixed, but it's a button for now, as toggle looks seem to have issues, e.g. the combination of the material background look and glamorous button look do not show anything in a toolbar.


MouseMoveExt  did not work while active a window whose process run as Administrator during hooking.

As title

A condition：Hook run in a no-administrator process


Send email on error

As it might happen that you need to take action it would be good to get an email notification on errors.

Feature is now in testing

This is released with 0.14.0:
Logging to Email (Errors only):
  --logging-mail-from LOGGINGMAILFROM
                        Mail address to send mails from
  --logging-mail-to LOGGINGMAILTO
                        Mail address to send mails to (can be used multiple
                        times)
  --logging-mail-host LOGGINGMAILHOST
                        Mail server host
  --logging-mail-credentials LOGGINGMAILCREDENTIALS LOGGINGMAILCREDENTIALS
                        Mail server credentials
  --logging-mail-subject LOGGINGMAILSUBJECT
                        Mail subject
  --logging-mail-notls  Mail do not use TLS
  --logging-mail-testmail
                        Try to send Testmail at startup


feat(requireAliases): new function "requireish" accepts aliases for require

Third try :D
I hope that I haven't forgot something again this time.
The new function accepts either a string or an array of strings as require aliases.
It is tested and documented.
The CI build will obviously fail because aliasify depends on browserify-transform-tools version 1.5.4+ which is not published yet. This will optimally happen if my PR in the other repo gets accepted too.

Yeah it would really be nice... But I have no idea on how to accomplish this.
PS: I saw you merged the new function and published it as version 1.6.0
If this feature from aliasify should be merged the package.json has to be adjusted to point to the right transform tools version.

Used https://github.com/benbria/aliasify/pull/41 instead.


search with gpt4

Notebook with postgres and gpt4

/assign @bjoydeep

@SherinV this looks good. Can you just add in the readme what do you if we do not want to run Argilla.

@SherinV this looks good. Can you just add in the readme what do you if we do not want to run Argilla.

Done. Added the lines to be commented out.


Add language attribute to generated html pages

From the SonarLint rules...
The  element should provide the lang and/or xml:lang attribute in order to identify the default language of a document.
It enables assistive technologies, such as screen readers, to provide a comfortable reading experience by adapting the pronunciation and accent to the language. It also helps braille translation software, telling it to switch the control codes for accented characters for instance.
Other benefits of marking the language include:

assisting user agents in providing dictionary definitions or helping users benefit from translation tools.
improving search engine ranking.

fixed


Experimental support for color temperature

Adds experimental support for controlling color temperature via the set_ct_abx operation on supported devices. Previously only devices supporting color would be able to set the color temperature.

Should resolve #17 and #22.

Hi,
CT message works. But temperaure selector in home app is missing cold color temperature screenshot 1,2. And some issue with switching color in screenshot 3. When I press the color so the color of the bulb changes but no in home app.

Hi, when would you like to merge those changes?

Is there an easy option I can install this for my homebridge so I can test it also? Sorry if those are dumb questions but I'm not familiar with JS and new to homebridge stuff.


API: The results are not sorted in chronological order

I saw these before:

The order of the hours is incorrect.
But this is a new example:
https://explorer.ooni.org/search?since=2022-03-27&until=2022-04-24&domain=raw.githubusercontent.com&probe_cc=IR&test_name=web_connectivity&failure=false

More correctly here:
https://api.ooni.io/api/v1/measurements?limit=50&failure=false&probe_cc=IR&domain=raw.githubusercontent.com&test_name=web_connectivity&since=2022-03-27&until=2022-04-24&offset=50
If you search for 07:18 here ^ :

Thanks for reporting this. I think this is pretty important to fix, because it's most likely going to also mess up with how pagination is done.
I see that the reason why this being done seems to be caused by the fact that we are sorting based on test_start_time when certain filters are applied (see: https://github.com/ooni/api/blob/clickhouse/newapi/ooniapi/measurements.py#L1329), yet these lead to an inconsistent view, because we are displaying the measurement_start_time.

Until fixing it, if someone wants to use API without problem, can add &order_by=measurement_start_time.
e.g., for above API URL:
https://api.ooni.io/api/v1/measurements?limit=50&failure=false&probe_cc=IR&domain=raw.githubusercontent.com&test_name=web_connectivity&since=2022-03-27&until=2022-04-24&offset=50&order_by=measurement_start_time

Sorting by test_start_time as default has been done for a long time when using PostgreSQL due to performance limitations. Now it's not an issue anymore. Fixed and deployed.
Thanks for the bug report!


Adds command 'onenote notebook add'. Closes #3100

Adds 'onenote notebook add' command. Closes #3100

Thanks for your PR @Abderahman88! We'll review it ASAP.

@plamber No problem, I'll work on it 👍

Hi @Abderahman88,
Are you still working on this issue?
Thank you for your feedback,
Patrick

@plamber Sorry, I forgot this one. I'll resume this issue. Thanks for the reminder.

Hi @Abderahman88,
Happy new year. I just wanted to follow up on this topic. Do you need some help for these activities?
When touching the PR could you please also ensure that the conflicting files have been resolved?
Thank you,
Patrick

Hi @Abderahman88,
this is just a gentle reminder about this issue. Are you currently working on it?
Thank you for your feedback

Hi @plamber
I'll work on it 👍

hi @Abderahman88,
this is just a gentle reminder. Do you need some help for this command?
Cheers

@plamber Sorry forget this one. I'll resume the work on this one. Thank you for the reminder.

I've used my own custom Azure AD identity and added all OneNote permissions, but I still get this error?
Error: The OAuth token provided does not have the necessary scopes to complete the request. Please make sure you are including one or more of the following scopes: Notes.ReadWrite.All,Notes.Read.All,Notes.Create,Notes.ReadWrite,Notes.ReadWrite.CreatedByApp,Notes.Create,Notes.ReadWrite,Notes.ReadWrite.CreatedByApp,Notes.ReadWrite.All

@Abderahman88: have you tried to get the access token and verify using https://jwt.io/ if the scopes are included?
To me it feels that you are using the PnP multi tenant application, which does not have Notes.ReadWrite.All
@waldekmastykarz: could we consider adding Notes.ReadWrite.All to our multi-tenant application. It is missing right now

@waldekmastykarz: could we consider adding Notes.ReadWrite.All to our multi-tenant application. It is missing right now

We typically update permissions only after merging PRs to ensure that we're not requesting permissions for things we don't support. Do we have any commands that require this permission already?

Not yet. This command is almost ready to be merged

Not yet. This command is almost ready to be merged

Is this actually the case? Looking at the previous comments, it seems like we've got issues with the missing scope. Is that indeed the case, or was it an issue with @Abderahman88 testing and you verified the PR with a custom AAD app and it's working properly and ready to be merged?

The command as it is, is fine. We are just lacking the sample output in the documentation and the permission in production.
Im am sure @Abderahman88 just did a wrong test with his app. Lets wait for the final confirmation.

One thing I noticed with this PR is that there are several occurrences of promise/then usage. Ideally, this would be written with async/await.

@plamber I've found my mistake. I've added OneNote permissions in my custom AD app and not the Graph OneNote permissions.

@plamber I've found my mistake. I've added OneNote permissions in my custom AD app and not the Graph OneNote permissions.

Thanks for the update and sorry for the hold up. We will review it ASAP

@Abderahman88 did you have a chance to check my comments? We are on the right track. Just a bit of work is needed to make it happen 👍
let me know if I may help 👍 You rock 🤩

@Abderahman88 I'll work on it this week.

@Adam-it  I'll work on it this week.

Awesome 🤩👍

@Adam-it I'll work on it this week.

@Abderahman88 did you maybe have a chance to check out this PR 🙂?

@Abderahman88 I was wondering if you maybe need my help in proceeding with this PR? Is there something blocking you maybe you would like to recheck together or share work on this PR with me?
Let me know how it's going and if I may be of any help to you 👍 Please do not hesitate to reach out in any way 🙂

@Adam-it Sorry, had a busy week. I'll resume this PR. If I need help, I'll let you know 👍

@Adam-it Sorry, had a busy week. I'll resume this PR. If I need help, I'll let you know 👍

conference week, I know 😉. Let me know if I can help to keep this moving forward 👍

@Abderahman88 It has been like 8 months since this PR is opened and since then a lot has changed on our side (like we changed our docs to docusource and now we use .mdx instead of .md). This PR became out of date and it would be wise to start a new branch from our current main and restart the work on this command knowing what we learned already from this PR 👍.
Let's close this one and when you are ready to contribute again you may always open a new PR aligned with latest main 👍.
I would like to thank you for all your fantastic work done till now 🤩 you did an amazing job 👍. We all do open source when we have time for it so it's totally ok to take a step back and retry when the time is right 💪.
If you will need any more guidance or help with adding this command please do not hesitate to reach me out. The best way would be to start an open chat on our Discord server so you will get a fast response from one of the maintainers or contributors 😍.


Don't check for null for structs

Fix to https://github.com/microsoft/typespec/pull/4919

API change check
API changes are not detected in this pull request.


Fix for_each_pixel do not compile with lambdas

Fix #186 by replacing the inner for_each loop on lines with a simple range-based loop.
Environment
Boost 1.68, tested with MSVC 2017.
References
Fix #186

#139 as a similar fix and is already merged.


catch for all event handlers that return promises?

I wondered whether it might be handy to include a mechanism for giving plastiq a catch block for unhandled rejection of promises returned by event handlers. There's an argument that we already have a global way of doing this (window.addEventListener('unhandledrejection', ...) but it doesn't work very well, or in a non-window environment. Or do you think this is userland responsibility?

I'm thinking this belongs in userland... Node is pretty aware of unhandled rejections now, and so are most browsers. Closing


[Card in card] md new design & spec

Currently, the Card in card component at md breakpoint looks huge, the text card drops below image, and can be as wide as 1055px.
Current design for md:

Proposed design for md:

Files are in their Box folder.


iamy: enable tests

iamy: enable tests
@nix { "action": "setPhase", "phase": "checkPhase" }
running tests
=== RUN   TestIsSkippableManagedResource
=== RUN   TestIsSkippableManagedResource/myalias-123/iam/role/aws-service-role/spot.amazonaws.com/AWSServiceRoleForEC2Spot.yaml
=== RUN   TestIsSkippableManagedResource/AWSServiceRoleTest
=== RUN   TestIsSkippableManagedResource/my-example-role-ABCDEFGH1234567
=== RUN   TestIsSkippableManagedResource/myalias-123/iam/user/foo/billy.blogs.yaml
=== RUN   TestIsSkippableManagedResource/myalias-123/s3/my-bucket.yaml
=== RUN   TestIsSkippableManagedResource/myalias-123/iam/instance-profile/example.yaml
--- PASS: TestIsSkippableManagedResource (0.00s)
    --- PASS: TestIsSkippableManagedResource/myalias-123/iam/role/aws-service-role/spot.amazonaws.com/AWSServiceRoleForEC2Spot.yaml (0.00s)
    --- PASS: TestIsSkippableManagedResource/AWSServiceRoleTest (0.00s)
    --- PASS: TestIsSkippableManagedResource/my-example-role-ABCDEFGH1234567 (0.00s)
    --- PASS: TestIsSkippableManagedResource/myalias-123/iam/user/foo/billy.blogs.yaml (0.00s)
    --- PASS: TestIsSkippableManagedResource/myalias-123/s3/my-bucket.yaml (0.00s)
    --- PASS: TestIsSkippableManagedResource/myalias-123/iam/instance-profile/example.yaml (0.00s)
=== RUN   TestPolicyIsDetachedFromRoleBeforeUpdate
2022/04/06 08:41:12 Loading YAML IAM data from /build/source/iamy/testdata/awsdiff/testcase1-local
2022/04/06 08:41:12 Loading myalias-123/iam/role/testrole.yaml
2022/04/06 08:41:12 Loading YAML IAM data from /build/source/iamy/testdata/awsdiff/testcase1-remote
2022/04/06 08:41:12 Loading myalias-123/iam/policy/test.yaml
2022/04/06 08:41:12 Loading myalias-123/iam/role/testrole.yaml
--- PASS: TestPolicyIsDetachedFromRoleBeforeUpdate (0.00s)
=== RUN   TestCfnMangedResources
=== RUN   TestCfnMangedResources/With_fetched_CFN_resource_lists
=== RUN   TestCfnMangedResources/With_heuristic_matching
--- PASS: TestCfnMangedResources (0.00s)
    --- PASS: TestCfnMangedResources/With_fetched_CFN_resource_lists (0.00s)
    --- PASS: TestCfnMangedResources/With_heuristic_matching (0.00s)
=== RUN   TestNewAccountFromString
--- PASS: TestNewAccountFromString (0.00s)
=== RUN   TestNewAccountFromStringWithNoAlias
--- PASS: TestNewAccountFromStringWithNoAlias (0.00s)
=== RUN   TestRecursivelyNormaliseAwsPolicy
--- PASS: TestRecursivelyNormaliseAwsPolicy (0.00s)
=== RUN   TestNewPolicyDocumentFromJson
--- PASS: TestNewPolicyDocumentFromJson (0.00s)
=== RUN   TestRoundTrip
2022/04/06 08:41:12 Loading YAML IAM data from /build/source/iamy/testdata
2022/04/06 08:41:12 Skipping awsdiff/testcase1-local/myalias-123/iam/role/testrole.yaml
2022/04/06 08:41:12 Skipping awsdiff/testcase1-remote/myalias-123/iam/policy/test.yaml
2022/04/06 08:41:12 Skipping awsdiff/testcase1-remote/myalias-123/iam/role/testrole.yaml
2022/04/06 08:41:12 Loading myalias-123/iam/group/DevOps.yaml
2022/04/06 08:41:12 Loading myalias-123/iam/policy/TestPolicyAccess.yaml
2022/04/06 08:41:12 Loading myalias-123/iam/role/ecsInstanceRole.yaml
2022/04/06 08:41:12 Loading myalias-123/iam/user/foo/billy.blogs.yaml
2022/04/06 08:41:12 Loading myalias-123/s3/my-bucket.yaml
Creating tmp dir /build/loaddumpertest1037231014
2022/04/06 08:41:12 Dumping YAML IAM data to /build/loaddumpertest1037231014
--- PASS: TestRoundTrip (0.00s)
PASS
ok  	github.com/99designs/iamy/iamy	0.005s

Result of nixpkgs-review pr 167501 run on x86_64-darwin 1

1 package built:

iamy


DSEGOG-348 view favourite filters

Description
A user should be able to view a favourite filters.
add edit and delete buttons
Testing instructions
Add a set up instructions describing how the reviewer should test the code

[ ] Review code
[ ] Check Actions build
[ ] Review changes to test coverage
[ ] {more steps here}

Agile board tracking
closes DSEOG-347

@joshuadkitenge Could you merge develop into the add-favourite-filters branch and then merge/rebase this branch? It looks like at some point this branch has had dev merged in and so in the PR review it's hard to tell which changes are actually from this PR and what are "changes" from dev since the base add-favourite-filters branch doesn't have those.


Display sensor in extra data template

I am struggling to display a sensor in an extra_data_template.
This works:
homeassistant:
    customize:
        sensor.home_battery_load_watts:
            friendly_name: test
            extra_data_template: "test"

These do not:
            extra_data_template: '{{ states.sensor.whizbangjr_amps.state }}'

            extra_data_template: {{ states.sensor.whizbangjr_amps.state }}

Note: the bellow non working exemple works as a value_template elsewhere ....
            extra_data_template: '{{ states.sensor.whizbangjr_amp.state|int }}'

            extra_data_template: '{{ entities.sensor.whizbangjr_amp }}'

Note: The bellow exemple test won't execute as javascript but show the script literally in the UI "return 'test';"
            extra_data_template: >
                return 'test';

This won't work either:
            extra_data_template: >
                {{states.sensor.whizbangjr_amp}}A

Indeed test were made using latest version:
$ ./update.sh
Getting state-card-custom-ui.html
Getting state-card-custom-ui.html.gz
Updated to Custom UI '20170802'
Getting ha-panel-custom-ui.html
Getting ha-panel-custom-ui.html.gz
Updated Panel to '20170802'
Getting __init__.py
File up to date.
Getting services.yaml
File up to date.

Another fail (the badge shows properly, not the extra_data)
sensor.home_battery_load_watts:
            friendly_name: test
            extra_data_template: >
                ${attributes.amps + 'A'}
            extra_badge:
                entity_id: sensor.whizbangjr_amps  # Will take precedence over attribute and unit below.
                attribute: amps
                unit: A
                blacklist_states: 0

Those are JavaScript templates evaluated in your browser, not Jinja2 templates which are evaluated server-side and use a different syntax.
I added a clarification to the docs about this.
${attributes.amps + 'A'} should work however.
I just tested the following and it worked:
    light.study_lights:
      friendly_name: Light stretch-slider break-slider-toggle
      state_card_mode: break-slider-toggle
      stretch_slider: true
      amps: 11
      extra_data_template: >
        ${attributes.amps + 'A'}

extra_data_template: >
                return 'test';

worked fine too.
To make sure last version is loaded properly - open your browser's dev panel (Ctrl+shift+I or F12 on Chrome) - the CustomUI version should be printed in the console.

I'd rather display the sensor ( states.sensor.whizbangjr_amps.state ) data directly without having to use an extra badge or a static attribute. Is that possible ?
I tried to "console.log" the entities object but it doesn't seem to do anything.
extra_data_template: >
                console.log(entities); return 'test';

I found my way:
extra_data_template: >
                return entities["sensor.whizbangjr_amps"].state + "A";


Add collation for Dev Guide

Coverage remained the same at 45.501% when pulling 1fbf0b20735624e77e5a47c97f3e271764636327 on V0.2_dash into ab254a42520b2d4905211ee3f4167ce4308f76d5 on V0.2.

I'm merging this, so that i can check through for everyone's collation tag all at one go


Update default value for forwarder_retry_queue_payloads_max_size.

What does this PR do?
Update default value for forwarder_retry_queue_payloads_max_size to 15Mb
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
Describe your test plan
For QA, check The actual memory used is greater than the payloads size as there are extra fields like HTTP headers, but no more than 2.5 times the payload size.

Wrong rebase. Closed in favor of https://github.com/DataDog/datadog-agent/pull/6654


Sharing fixes

This references issue https://github.com/Microsoft/HoloToolkit-Unity/issues/292
The major fixes here are subscribing to NetworkConnection events so that we know when we're connected to the server instead of using Invoke with a certain time (which failed when init took more than one second) and using Singleton<T> for SharingStage, as the previous implementation was broken and an unnecessary duplication of efforts.
My previous testing showed the Sharing sample scene to work now, which wasn't the case before; I would appreciate if some other people tested and verified this to be true.

Hi @Holo-Krzysztof, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@Holo-Krzysztof, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

I've moved the singleton access calls into start, WorldAnchorStore is fine in Awake, I guess.

Also, enum ImportExportState could be private, as well as ImportExportState currentState


Other kind of panorama is ok to GibsonEnv?

Hi, I'm trying to import my own environment into the GibsonEnv. I mentioned that the panos in GibsonEnv are equirectangular ones. I was wondering if I can use other types of panoramas to replace the equirectangular ones?

@aDobeZ do you currently use pano with equirectangular one? I tried to uncomment the related code, but not able to run the demo.
It seems some OpenGL code is there, but it was commented out. Why is pano not supported right now? I'd like to follow this feature. @fxia22


Why is the MainController declared as function and not as a class?

I guess because of the annotations right?
But isn't there a better solution?

I'm not able to find a MainController in use in any of the branches. I think that this has been resolved.


TypeError: Cannot read property 'sizes' of undefined

Mac 10.12.6
Node 8.2.1
Webpack 2.6.1

/Users/jesse/Code/web/frontend/node_modules/webpack-dashboard/plugin/index.js:57
inspectpack[action]({
^
TypeError: Cannot read property 'sizes' of undefined
at Promise.all.bundles.map.bundle (/Users/jesse/Code/web/frontend/node_modules/webpack-dashboard/plugin/index.js:57:18)
at Array.map (native)
at INSPECTPACK_INDEPENDENT_ACTIONS.forEach.action (/Users/jesse/Code/web/frontend/node_modules/webpack-dashboard/plugin/index.js:56:25)
at Array.forEach (native)
at getBundleMetrics (/Users/jesse/Code/web/frontend/node_modules/webpack-dashboard/plugin/index.js:55:35)
at Compiler.compiler.plugin.stats (/Users/jesse/Code/web/frontend/node_modules/webpack-dashboard/plugin/index.js:220:7)
at Compiler.applyPlugins (/Users/jesse/Code/web/frontend/node_modules/tapable/lib/Tapable.js:61:14)
at /Users/jesse/Code/web/frontend/node_modules/webpack/lib/Compiler.js:271:13
at Compiler.emitRecords (/Users/jesse/Code/web/frontend/node_modules/webpack/lib/Compiler.js:367:37)
at /Users/jesse/Code/web/frontend/node_modules/webpack/lib/Compiler.js:265:12
at /Users/jesse/Code/web/frontend/node_modules/webpack/lib/Compiler.js:360:11
at next (/Users/jesse/Code/web/frontend/node_modules/tapable/lib/Tapable.js:154:11)
at Compiler.compiler.plugin (/Users/jesse/Code/web/frontend/node_modules/webpack/lib/performance/SizeLimitsPlugin.js:99:4)
at Compiler.applyPluginsAsyncSeries1 (/Users/jesse/Code/web/frontend/node_modules/tapable/lib/Tapable.js:158:13)
at Compiler.afterEmit (/Users/jesse/Code/web/frontend/node_modules/webpack/lib/Compiler.js:357:8)
at Compiler. (/Users/jesse/Code/web/frontend/node_modules/webpack/lib/Compiler.js:352:14)
at /Users/jesse/Code/web/frontend/node_modules/async/dist/async.js:421:16
at iteratorCallback (/Users/jesse/Code/web/frontend/node_modules/async/dist/async.js:998:13)
at /Users/jesse/Code/web/frontend/node_modules/async/dist/async.js:906:16
at /Users/jesse/Code/web/frontend/node_modules/graceful-fs/graceful-fs.js:43:10
at FSReqWrap.oncomplete (fs.js:135:15)

I just tried running with webpack-dev-server instead of just webpack and this didn't occur.

hmm. was there any error on build?

I had the same error on Windows using Express.
webpack: Compiled successfully.
Error from inspectpack: TypeError: Cannot read property 'sizes' of undefined
    at Promise.all.bundles.map.bundle (F:\sbp\ui\node_modules\webpack-dashboard\plugin\index.js:55:18)
    at Array.map (native)
    at getSizes (F:\sbp\ui\node_modules\webpack-dashboard\plugin\index.js:54:13)
    at MapSink.event (F:\sbp\ui\node_modules\most\lib\fusion\Map.js:71:22)
    at PropagateTask.runJust [as _run] (F:\sbp\ui\node_modules\most\lib\source\core.js:46:8)
    at PropagateTask.run (F:\sbp\ui\node_modules\most\lib\scheduler\PropagateTask.js:43:8)
    at ScheduledTask.run (F:\sbp\ui\node_modules\most\lib\scheduler\ScheduledTask.js:20:20)
    at runTask (F:\sbp\ui\node_modules\most\lib\task.js:18:17)
    at runTasks (F:\sbp\ui\node_modules\most\lib\scheduler\Timeline.js:80:7)
    at Timeline.runTasks (F:\sbp\ui\node_modules\most\lib\scheduler\Timeline.js:69:20)
    at Scheduler._runReadyTasks (F:\sbp\ui\node_modules\most\lib\scheduler\Scheduler.js:107:17)
    at Asap.Scheduler._runReadyTasksBound [as f] (F:\sbp\ui\node_modules\most\lib\scheduler\Scheduler.js:29:10)
    at Asap.run (F:\sbp\ui\node_modules\most\lib\scheduler\ClockTimer.js:32:30)
    at runTask (F:\sbp\ui\node_modules\most\lib\task.js:18:17)
    at process._tickCallback (internal/process/next_tick.js:109:7)
F:\sbp\ui\node_modules\most\lib\fatalError.js:13
    throw e;
    ^

TypeError: Cannot read property 'terminate' of undefined
    at DashboardPlugin.cleanup (F:\sbp\ui\node_modules\webpack-dashboard\plugin\index.js:134:23)
    at Object.error (F:\sbp\ui\node_modules\webpack-dashboard\plugin\index.js:270:18)
    at throwError (F:\sbp\ui\node_modules\most\lib\observable\subscribe.js:86:18)
    at F:\sbp\ui\node_modules\most\lib\observable\subscribe.js:71:5
    at process._tickCallback (internal/process/next_tick.js:109:7)
error Command failed with exit code 1.

@jessehattabaugh this should be resolved using the latest builds of webpack-dashboard and the app.

@maccuaa what platform is this happening on. Sounds like the daemon is failing to initialize. Are you on latest?

Reinstalling everything seems to have fixed the issue.   Now however I am having a similar issue as #20.  Only one process is spawned (I presume the webpack-dashboard process) but it rapidly starts eating up memory until it runs out of memory and dies.
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

That being said it isn't an issue for this project, if you like I can raise it on webpack-dashboard.

Yeah please ticket it there


obs-cmd: 0.17.4 -> 0.17.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/grigio/obs-cmd/releases.
meta.description for obs-cmd is: Minimal CLI to control OBS Studio via obs-websocket
meta.homepage for obs-cmd is: https://github.com/grigio/obs-cmd
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.17.5 with grep in /nix/store/0cwn1s776v20v2a5zp1bqsd29wf2d5lh-obs-cmd-0.17.5
found 0.17.5 in filename of file in /nix/store/0cwn1s776v20v2a5zp1bqsd29wf2d5lh-obs-cmd-0.17.5

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
obs-cmd

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0cwn1s776v20v2a5zp1bqsd29wf2d5lh-obs-cmd-0.17.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A obs-cmd https://github.com/r-ryantm/nixpkgs/archive/f319e891ed08d94fc1df6db66ebf749f3664efa2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/f319e891ed08d94fc1df6db66ebf749f3664efa2#obs-cmd

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0cwn1s776v20v2a5zp1bqsd29wf2d5lh-obs-cmd-0.17.5
ls -la /nix/store/0cwn1s776v20v2a5zp1bqsd29wf2d5lh-obs-cmd-0.17.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

obs-cmd

Maintainer pings
cc @ianmjones for testing.

Result of nixpkgs-review pr 299209 run on x86_64-linux 1

1 package built:

obs-cmd


kubectl set image doesn't work nor apply

I am trying to update existing deployment using this command:
kubectl set image deployment flaskapp flaskapp=scientronic92/flaskapp:5 --record

after it was flaskapp:4.

The new docker image is tested outside and it works perfectly.
I also tried using:
kubectl edit and kubectl apply still get the same result.

The problem was in tagging and uploading docker image!


Build Error: iOS: firebase_core

Time Tracking: MA-78
Local iOS simulator and device builds failing on experimental
https://github.com/firebase/flutterfire/issues/9806
This is done when:

[ ] iOS build issues on experimental resolved

Notes:
It appears a patch was applied to existing versions of firebase_core, causing debug iOS builds to fail.

Previously resolved in dev


Allow extraction of messages with no line number

Some linters output file-level errors that don't correspond to a
specific line number. Previously, this was only workable by either
manually building the Overcommit::Hook::Message instance or
splicing a dummy line number into the output.

Merged in 908d0db960417d641b5a07f91b11ffa2f883de63.


transient_for errors in child component

I have the following hierarchy: App > Component and Component::init crates OpenDialog.
The issue is that in this case transient_for(&root) results in this:
2023-12-09T12:40:47.898031Z ERROR relm4::component::sync::builder: Couldn't find root of transient widget

The reason is that Component wasn't yet added to window, we're still building it. I didn't find clearer solution than to pass Window down as Component::Init, but it feels like that error shouldn't happen and OpenDialog should be able to attach to window once window is available even if is not available during construction.

The way Relm4 handles this is the following:

Store code for transient_for as closures
Wait for all the main component to finish initialization (which usually initializes most child components)
Call all stored closures

Yet if you call transient_for later on, the code won't be delayed. This means that the widget has no root yet when transient_for is called. One solution for that would be to add the widget of the child components before calling transient_for on the component builder.
This is - like many things in Relm4 - a problem of ordering certain operations. However, we could try to solve this by executing the transient_for code as an asynchronous task. This way, it should only run once the function in which transient_for was called from has returned, which should mean that the widget should have been added to window already...
Would you mind testing a branch with a potential fix for your issue?

I can test a potential fix, sure


feat(general): fixed Makefile paths

The Makefile paths were not updated yet. @serge1peshcoff I am not sure if I changed the backup_core correctly.
I also changed localhost into <IP_ADDRESS> in Vagrantfile, since that caused an error for me (both Windows and Linux)

Btw, couldn't push directly to this repo, so I used a fork. Not sure if tests will run this way

@serge1peshcoff  what do you think this check anomaly is? I mean, going to the tab "checks" shows empty, I expect something to be there for consistency with this page (even though we have configured tests to not run for forks - and even there, can you see options for running most commands except the ones with passwords?)

okay, this is most likely due to CircleCI not running PR checks for forked PRs:

I've made myself an admin of AEGEE/MyAEGEE and disabled some administrators restrictions in order to be able to merge this, will disable it after merging.
@WikiRik I've also given you the write access, so it's better to push to this repo directly.

but this is silly, CircleCI does not tell github to not wait?

CircleCI doesn't send the checks statuses because they are not executed,
and they are required, so is impossible to merge stuff this way.
On Sun, 5 Jul 2020, 12:37 linuxbandit<EMAIL_ADDRESS>wrote:

but this is silly, CircleCI does not tell github to not wait?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/AEGEE/MyAEGEE/pull/150#issuecomment-653865255, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIC3IOH7WMMOLCUS2TPRPDR2BCWFANCNFSM4OO6DHGQ
.

I've made myself an admin of AEGEE/MyAEGEE and disabled some administrators restrictions in order to be able to merge this, will disable it after merging.
@WikiRik I've also given you the write access, so it's better to push to this repo directly.

Awesome, thanks!