[BDG-FORMATS-54] Generalizing the Fragment type

I think storing reads after a "groupby" operation has occurred is an excellent idea, as the reads will likely always be analyzed as a group.  Having multiple reads from a single fragment of DNA is one such use case, but there are others.  Droplet-seq is one that I am interested in.  Incorporating random
barcodes is another.
Here is a summary of my proposal, based in part on @ilveroluca's work:

Support a fastq-like object Sequence, though I don't think this is strictly necessary.
Rename to Bucket, as it sounds more general to my ears.
Move run-specific or instrument-specific metadata into separate objects, as they don't necessarily make sense as top-level objects.
Remove fragmentSize, as it's specific to one use case and it's rather easily computable.
Support for multiple types of grouped objects.  What's the best way to deal with this?  union somehow?  I envision that we may add more types in the future that we'll want to persist as grouped objects.  At the moment, there is just a set of arrays for the type of objects that could be grouped.  This could be extended as we desire the ability to group other object types.
Sequence and quality information from alignments should be retrieved from AlignmentRecords.
I don't think platform-specific information should be propagated through the entire chain of data types.  Why don't we include it in Genotype, then?  In my mind, any platform-specific analysis happens very early on, generally even before the fastq stage.  Therefore, I've moved platform-specific metadata into the Sequence object.

Fixes #54.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/bdg-formats-prb/62/
Test PASSed.

I think the Bucket and the Fragment record types represent two different concepts.
The Bucket represents a generic group of reads, akin to the recordGroup concept that is present in SAM/BAM and has already been transferred to the AlignmentRecord.
The Fragment on the other hand is a single piece of DNA which has been read in parts.  The parts are ordered and they may overlap.
As you said, the "Fragment" could be seen as a special case of the Bucket, as long as the Bucket is ordered (which in the case of your patch, it is).  However, if a program starts processing a data set and finds a Bucket, how should it know whether to treat the sequences within the group as belonging to a single DNA fragment (e.g., important for alignment) or as a group of single-end reads?  You'd have to tell it, somehow, and complicate processing to address the different possible behaviours in the code.  Or you'd have to restrict the software to only work with "Fragment buckets", taking away the user's ability to use Buckets for logical read groups -- which wouldn't be nice.
I suppose that when dealing with single-end reads, or perhaps in downstream analyses, knowing whether two reads come from the same fragment might not be very useful.  But in upstream analysis it is something that happens often enough (every flowcell!) to warrant it's own record type.
My two cents.

I think the Bucket and the Fragment record types represent two different concepts.

Agreed, but I'd say that Fragment is a subclass of Bucket.

The Bucket represents a generic group of reads, akin to the recordGroup concept that is present in SAM/BAM and has already been transferred to the AlignmentRecord.

Except the BAM format is pre-groupBy.  The key useful feature here is that the Bucket stores all the reads in a group together physically, while the readGroup annotation in BAM simply stores the group key with the read, but the reads can be scattered in the file.

if a program starts processing a data set and finds a Bucket, how should it know whether to treat the sequences within the group as belonging to a single DNA fragment (e.g., important for alignment) or as a group of single-end reads? You'd have to tell it, somehow, and complicate processing to address the different possible behaviours in the code. Or you'd have to restrict the software to only work with "Fragment buckets", taking away the user's ability to use Buckets for logical read groups -- which wouldn't be nice.

I'm not sure I understand the concern here.  Say there are two use cases for Bucket, one called Fragment and another called Droplet.  Say Fragment is always composed of exactly two reads in a particular orientation, and say that Droplet is composed of a variable/unknown number of reads where the order doesn't matter.  You write a program that reads Buckets and assumes they're only composed of two reads, and I write a program that reads Bucketss and assumes that each Bucket may have a different number of reads.  No problem.
Actually, you could model your Fragment object as a Scala class or as a separate Avro object that's internal to your program.  So when you load the RDD[Bucket], you immediately convert it to an RDD[Fragment].

I don't want to hold up bigdatagenomics/adam#815, but after that merges, I'd like to resolve this before we add more functionality based on the Fragment type.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/bdg-formats-prb/68/
Test PASSed.

@ryan-williams Looking again at my comments, I think there may be a use for keeping both an array of Sequence and an array of AlignmentRecord.  In my comment, I specified that exactly one of these should be non-null.  I guess this is from the perspective where you might be working with reads that don't need to be mapped in the same way.  Still, I'd be fine making it only AlignmentRecord as long as it's easy to work with non-mapped AlignmentRecords.

I think that we have some ability and precedent for letting ARs be mapped or unmapped.
Let me know if there's some case for having both that I've missed; so far the two I've heard (on adam#815) are:

normalize the sequence for efficiency in the case of chimeric reads

store hard-clipped bases that aren't currently stored in ARs.

is not persuasive to me, and 2. would be better solved by putting that info into ARs if we actually care about it.

Separately from all of this, I'd be inclined to agree that if we had both arrays we should try to enforce exactly one of them being non-null at all times, but that's still a kind of gross solution and I'd much rather avoid it if we don't have a compelling need for it.
Finally, if there was a concrete case where we want to bucket things besides ARs, that would also warrant consideration here, but it doesn't sound like we have one. Moreover, in the event that we had one, that might be best served by a new Bucket-like record-class that is specific to that thing; there's no use making Bucket so general that anyone that uses it has to layer assumptions all over it at runtime… just make a new record type at that point!
I think Bucket as basically an object that wraps an array of ARs is a nice bite-size abstraction to add.

sgtm with all your points.  I'll push another commit to remove the Sequence array.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/bdg-formats-prb/69/
Test PASSed.

Coming back to this one after having proposed Alphabet, Sequence, Slice, and Read in #83.
Might the proposal here be updated to create two new record types:
record Read[s, Bucket, Group, Fragment, Set, List, ...] {
  union { null, string } name = null;
  array<Read> reads = [];
}
record AlignmentRecord[s, Bucket, Group, Fragment, Set, List, ...] {
  union { null, string } name = null;
  array<AlignmentRecord> alignments = [];
}

I prefer Group over Bucket, even though that is slightly overloaded by BAM's recordGroup.

Closing as WontFix


*: http and https on the same port

./etcd --experimental-v3demo --cert-file cert --key-file key \
--listen-client-urls=http://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379 \
--advertise-client-urls=http://<IP_ADDRESS>:2379,https://<IP_ADDRESS>:2379

works now.
fix https://github.com/coreos/etcd/issues/4737
/cc @heyitsanthony @gyuho @philips

Test failed from govet. I have quick fix here https://github.com/coreos/etcd/pull/4833.
Could you merge that first, and rerun this test?
Thanks.

I still need to fix a few tests.

@heyitsanthony @gyuho Now test passed. PTAL.

code looks fine (although startEtcd really needs to be split up), but can this include a small e2e test?

@heyitsanthony Will add a e2e test.

@heyitsanthony Added an e2e test.

lgtm aside from the isClientBoth stuff

@heyitsanthony Fixed. Merging...


add entry for "scbs", a tool for sc methylation data

Hi there,
a few months ago we released "scbs", a command line tool for the analysis of single-cell methylation data. We also published a corresponding preprint on bioRxiv. I think it would be a nice addition to the list!
Best regards,
Lukas

Thanks, @LKremer. And welcome to the contributor club!


Title:  An AI Assistant using openai api and voice recognition system

Is your proposal related to a problem? Please describe.
Yes, For beginners who love the AI and want to make an assistant it can be a interesting project.
Please assign me this issue under GSSOC24.
Add any other context or screenshots about the proposal request here.
No response

Also documenntation will be there

@Avishek8136 You already created one issue before please focus on that.

Previous work is completed


check_extra734 Failing when bucket policy is empty

Next line doesn't consider that when the bucket policy is empty aws cli returns "An error occurred (NoSuchBucketPolicy) when called the GetBucketPolicy operation: The bucket policy does not exist"
$AWSCLI s3api get-bucket-policy $PROFILE_OPT --bucket $bucket --region $BUCKET_LOCATION --output text --query Policy > $TEMP_SSE_POLICY_FILE 2>&1
The if statements are not considering the "Could not connect to the endpoint" to the url of the policy is an answer for an unexistent bucket policy
Replicate:
Run the check with a bucket whit  no bucket policy

Hello @theOriginalClauBotas ,
has this been fixed?
Isn't that if statement the one on this line?
https://github.com/toniblyx/prowler/blob/master/checks/check_extra734#L68
Cheers!

Yes, that particular behaviour was fixed here https://github.com/toniblyx/prowler/pull/407 (probably wasn't using that version). Please feel free to reopen this issue if you identify the error again.


External Link Detection is Iffy

Observed/problematic behavior
https://user-images.githubusercontent.com/117921904/227072833-2b5d10c0-a48b-4614-9912-a62a85ac3640.mp4
Expected behavior
Links to regular pages are not false flagged
Steps to reproduce
visit https://hangar.papermc.io/terms and then click the link to the privacy policy page
Other
No response

Duplicate of #1121


Fix code scanning alert - Flask app is run in debug mode

Tracking issue for:

[x] https://github.com/githubofkrishnadhas/quote-of-the-moment/security/code-scanning/1

This fix is implemented as suggested.


support timegridCurrentTime template

Current Behavior

I can not change the current time format.

Expected Behavior

The timegrid supports templates that allow the user to change the format of the current time.

Fantastic work @jungeun-cho !
Do you plan on releasing it somewhere this week or should I built it from source if I really need it?

@Pentiado
v1.11.0 released today.  🎉
This feature is now supported!
Enjoy tui.calendar!

Great! Thanks @jungeun-cho !


add libjpeg-dev to install instructions

I was missing libjpeg-dev on a fresh install of ubuntu 14.04

Hey Adrian,
Thanks for contribution. Do you need it for building jpeg-recompress?
Could you please place it so it is ordered alphabetically as other package names?

@toy
I really don't remember which one asked me libjpeg-dev to build.. I've already placed it alphabetically ordered.

@acrogenesis After running the original apt-get command on a fresh ubuntu 14.04 leaves me with pngout and svgo not installed, but both they don't need libjpeg-dev. Even jpeg-recompress doesn't depend on it.

I started a new droplet on DigitalOcean after running sudo apt-get install -y advancecomp gifsicle jhead jpegoptim libjpeg-progs optipng pngcrush pngquant and trying to install jpegoptim it say's:
Cannot find libjpeg or you have too old version (v6 or later required).
Installing libjpeg-dev solves it.

But you are compiling jpegoptim, the apt-get command is for installing prebuilt binaries. So libjpeg-progs provides jpegtran, but libjpeg-dev is only needed to compile binaries.
Also I've noticed that lots of binaries provided through apt-get are outdated, so I suggest to use image_optim_pack as you are on linux.

Just doing a little housekeeping... I think we can close this PR? It's quite old and libjpeg-dev doesn't appear to be required.
Just for reference the Discourse install guide  which uses image_optim and installs many apt based packages does not need the libjpeg-dev package when installing jpegoptim.

Thanks for this great project 👍


I would like to create an example for java file I/O operations

This is to explain the file FileInputStream and FileOutputStream operations in java.io package

You can create a PR for that.


[just ideas] - Option for dealing with deep component prop passing within Connected components

Apologies for polluting the issue list since it's not really an issue but I believe there is some interest in coming up with a workable solution that
a) Keeps the Smart/Dumb component divide clean & generally near the top of the component tree for a given part of the app domain AND
b) Avoid the hassle of passing @connect results down deep chains of children
I liked the Provide/connect pattern a lot so I generalized it in react-tunnel and starting playing with a patter like so
// in some Top level Component
<Provider store={mystore} /> //react-redux Provider
  {() => <App />}
</Provider>

// in a route handler
@connect(
  myStateMapper,
  (dispatch) => ({
    someActions: bindActionCreators(subsetOfMyActions, dispatch)
  })
)
export class ConnectedComponent...

// within ConnectedComponent's render()
<Provider someActions={this.props.someActions}> //react-tunnel Provider
  {() => <PageController />}
</Provider>

// deep within PageController's render tree
@inject(
  (provided) => ({
    specificActionIwant: someActions.specificActionIwant
  })
)
export class DeepComponent...

//within DeepComponent's lifecycle methods
...
this.props.specificActionIWant();
...

The Provider in react-tunnel puts props into context under the provided namespace and inject pulls them off with the mapProvidedToProps function.
It's not react-redux specific nor really related to redux in any way (and there are probably plenty of other DI type libraries that will get the same job done) but i thought it fit nicely with the react-redux paradigm but would give you the option to use similar semantics deeper in the component tree without bringing along anything specific to redux.
As a final note, you could actually do away wiht the react-redux Provider and just use the react-tunnel provider and inject by doing
// near top of app
<Provider store={mystore}>  //react-tunnel Provider
  {() => <App />}
</Provider>

//when you are going to connect...
@connect(
  stateFn,
  actionFn
)
@inject( provided => ({store: provided.store}) )
export class InjectedThenConnectedComponent...

//the above would have store made available to connect via props and not context but that is now supported in react-redux

anyhow, just some food for thought... would love feedback even if it's why this is a horrible idea.
Thanks,
Josh

Closing, no real traction here.

It'll be easier to experiment with this stuff when 0.14 ships, but yeah, not really related to Redux.
I'm not convinced a middle solution is needed here. Having several context split points makes it harder to move components around the app, as dependencies become implicit.

Agreed on the context splits concern but I do think that by pushing the connect to route handler style tier of a component tree ( which is nice for exactly the reasons you suggest it re: redux aware/unaware splits) we leave on the table the perennial problem of contexualizing the output of connect for use by the whole child tree. In shallow trees this isn't much of a concern but for complex and deep ones it is.
I can imagine that some will start to connect their leaf components using the mapDispatchToProps argument only which gets the job done, but only for that use case (providing action creators deeply) and ties their implementation to the react redux dependency unnecessarily.
One doesn't really need tunnel in that you can manage this all via the context feature (presumably it will be documented in 0.14) but then that is also the case for react-redux's provider too now that store can be loaded from props in connect.
Are you in particular an advocate for vanilla prop passing everything? Or vanilla context use?
To be clear I suspect that react-tunnel can and will be abused overused and cause problems of its own. Not sure what to do about that other than discouraging bad practices.

Are you in particular an advocate for vanilla prop passing everything? Or vanilla context use?

I try to connect() route handlers and use props all the way down unless some component gets too complicated and then it gets its own connect(), but also gets a “dumb” props-only version in case I want to reuse it later.

Makes sense, I guess i would just replace the deep connect() with inject() since it isn't strictly bound to the semantics of redux. The thing about either option is that they map what is contextual information into props so that you the 'dumb' version doesn't care how it get's its props and this means you can easily partially or fully unwind this style of props providing without having to refactor said component.


Not possible to deploy RKE2 clusters to Harvester

Rancher Server Setup

Rancher version: v2.6.6
Installation option (Docker install/Helm Chart): Docker install
Proxy/Cert Details: standard self signed, switched for testing to letsencrypt

Information about the Cluster

Kubernetes version: 1.23.7
Cluster Type (Local/Downstream):  RKE / RKE2 on Harvester v1.0.2

User Information

What is the role of the user logged in? Admin

Describe the bug

Cannot deploy RKE2 clusters to Harvester cluster but deploying RKE1 works like a charm.

To Reproduce

Install Rancher
Install Harvester
Add Harvester Cluster to Rancher
Create new RKE2 cluster on Harvester

Result

Cluster management pane shows:

Waiting for viable init node

Message inside nodes:

  failureMessage: |-
    Failure detected from referenced resource rke-machine.cattle.io/v1, Kind=HarvesterMachine with name "*-pool-442adf80-vvnnf": Downloading driver from https://rancher.*/assets/docker-machine-driver-harvester
    Doing /etc/rancher/ssl
    ls: cannot access 'docker-machine-driver-*': No such file or directory
    downloaded file  failed sha256 checksum
    download of driver from https://rancher.*/assets/docker-machine-driver-harvester failed

Docker logs from rancher

2022/06/30 14:44:41 [ERROR] error syncing 'fleet-default/cluster-pool-442adf80-g96x7': handler machine-provision: no machine owner ref, requeuing
[...]
2022/06/30 15:30:25 [ERROR] error syncing 'fleet-default/cluster-bootstrap-template-gv9pr': handler rke-machine: failed to delete fleet-default/cluster-bootstrap-template-gv9pr-machine-bootstrap /v1, Kind=Secret for rke-machine fleet-default/cluster-bootstrap-template-gv9pr: secrets "cluster-bootstrap-template-gv9pr-machine-bootstrap" not found, failed to delete fleet-default/cluster-bootstrap-template-gv9pr-machine-plan /v1, Kind=Secret for rke-machine fleet-default/cluster-bootstrap-template-gv9pr: secrets "cluster-bootstrap-template-gv9pr-machine-plan" not found, failed to delete fleet-default/cluster-bootstrap-template-gv9pr-machine-plan /v1, Kind=ServiceAccount for rke-machine fleet-default/cluster-bootstrap-template-gv9pr: serviceaccounts "cluster-bootstrap-template-gv9pr-machine-plan" not found, requeuing

Expected Result
If RKE1 deployment is successful, RKE2 should work too?
Screenshots

Additional context
Switched because of this error to a real certificate powered by lets encrypt, same behavior. Machine and DNS is available inside network. Machines are not getting created on Harvester.
admin@rancher:~$ wget https://rancher.*/assets/docker-machine-driver-harvester
--2022-06-30 15:26:55--  https://rancher.*/assets/docker-machine-driver-harvester
Resolving rancher.* (rancher.*)... 10.X.X.X
Connecting to rancher.* (rancher.*)|10.X.X.X|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 38760448 (37M) [application/octet-stream]
Saving to: ‘docker-machine-driver-harvester’

docker-machine-driver-harvester                                                               100%[================================================================================================================================================================================================================================================>]  36.96M  --.-KB/s    in 0.04s

2022-06-30 15:26:55 (878 MB/s) - ‘docker-machine-driver-harvester’ saved [38760448/38760448]

admin@rancher:~$

Hi @parsifallo are u using the master-head version? the v2.6.5 works fine for me and we only see this issue with the master-head version because the backend API has made some changes to the cloud-provider part, and it will be resolved with the upcoming UI changes.

Hi @guangbochen ! I am using Docker image "rancher/rancher:latest", but I see there's a new version. Will give it try now

The issue still exists in the latest version but ur first issue description has mentioned it was Rancher version: v2.6.5, just want to make sure it wasn't Rancher v2.6.5, thanks.

Strange, I copied the version number from the lower left of the web GUI. So I tested explicitly Docker image rancher/rancher:v2.6.6. I can add the Harvester cluster (shown as active) but if I try to create a cluster rancher shows this error message during creation: clusters.management.cattle.io "c-m-mpm4rd4l" not found, same behavior with v2.6.5. Now I started a fresh rancher installation with v2.6.5, added Harvester but I get the same errors:
2022/07/01 07:23:57 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:23:57 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:23:57 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:23:57 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:23:57 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:23:57 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:23:59 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:24:05 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:20 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:20 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:20 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:20 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [MachineProvision] Failed to create infrastructure fleet-default/cluster-pool1-303e2776-9dcqh for machine cluster-pool1-6568745bcb-w2txf, deleting and recreating...
2022/07/01 07:26:21 [INFO] [MachineProvision] Failed to create infrastructure fleet-default/cluster-pool1-303e2776-b6s6v for machine cluster-pool1-6568745bcb-4ph9s, deleting and recreating...
2022/07/01 07:26:21 [INFO] [MachineProvision] Failed to create infrastructure fleet-default/cluster-pool1-303e2776-vmxsq for machine cluster-pool1-6568745bcb-8wlb7, deleting and recreating...
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:21 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:21 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:22 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:22 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:23 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:26 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:31 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing
2022/07/01 07:26:35 [INFO] [planner] rkecluster fleet-default/cluster: waiting: waiting for viable init node
2022/07/01 07:26:41 [ERROR] error syncing '_all_': handler user-controllers-controller: failed to start user controllers for cluster c-m-sqwqwv7m: ClusterUnavailable 503: cluster not found, requeuing

Gonna try some other versions

Downgraded to 2.6.4, same error but this time it is shown in rancher gui:
provisioning bootstrap node(s) cluster1234-pool1-76b5d455d9-n8gtj: failed creating server (HarvesterMachine) in infrastructure provider: CreateError: Downloading driver from https://rancher.*/assets/docker-machine-driver-harvester
Doing /etc/rancher/ssl
ls: cannot access 'docker-machine-driver-*': No such file or directory
downloaded file failed sha256 checksum
download of driver from https://rancher.*/assets/docker-machine-driver-harvester failed, waiting for agent to check in and apply initial plan

Deploying RKE1 still works

I guess I found (part of) the issue. I started rancher with --network host instead of defining ports. But it still not works with the current version. Needed to downgrade to 2.6.5 for getting it to work

I seem to have the same issue but using openstack driver and not harvesterm perhaps it's something more global

Hello! I encountered the same problem on Rancher v2.8.5. As a driver - Harvester. Did you manage to solve it?

I'm also experiencing this when trying to create a RKE2 cluster using my custom node driver when running rancher locally on Docker Desktop. It seems to be an issue where download_driver.sh is failing because of the SSL cert (https://github.com/rancher/machine/blob/9183b3ff738e16ece4391a2e6bcc8ef88889e8ae/package/download_driver.sh#L15). I'm going to try running the rancher docker container with -e CURL_INSECURE=true to see if that works around the issue when running it locally.

That didn't seem to help

@PAzter1101 I'm actually not using harvester, just using my own custom node driver but I can't seem to figure out how to make download_driver.sh happy with the default self signed SSL cert for running rancher locally on Docker desktop.


No hint path defined for [adminlte]

I've installed adminlte-laravel on an existing (not new) laravel project but every time I try to go to the /home page, I get the error "No hint path defined for [adminlte]".
I'm also unable to use the artisan make:view command because the console is saying that it doesn't exist.
What can I do to make sure that adminlte is installed properly into the already existing laravel project?
Below is the install log when I ran the install command.
Install log
adminlte-laravel install
/root/.composer/vendor/bin/llum package AdminLTE
Running composer require acacha/admin-lte-template-laravel
Running composer as root/super user is highly discouraged as packages, plugins and scripts cannot always be trusted
Using version ^4.1 for acacha/admin-lte-template-laravel
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Nothing to install or update
Generating autoload files
> Illuminate\Foundation\ComposerScripts::postUpdate
> php artisan optimize
Generating optimized class loader
The compiled services file has been removed.
File /appdata/var/www/html/tracking/config/app.php already supports llum.
Llum is already installed. Skipping...
Adding Acacha\AdminLTETemplateLaravel\Providers\AdminLTETemplateServiceProvider::class to Laravel config app.php file
Adding Acacha\AdminLTETemplateLaravel\Facades\AdminLTE::class to Laravel config app.php file
Publishing complete.

Update! Something that should be included in the install instructions. Be sure to run this command after installation:

php artisan config:cache

That command refreshed the configuration cache and I can now use the create views command. However, now, there is a different error (the multiple references appear to be a result of my trying to install multiple times):

The Mix manifest does not exist. (View: /appdata/var/www/html/tracking/vendor/acacha/admin-lte-template-laravel/resources/views/layouts/partials/scripts.blade.php) (View: /appdata/var/www/html/tracking/vendor/acacha/admin-lte-template-laravel/resources/views/layouts/partials/scripts.blade.php) (View: /appdata/var/www/html/tracking/vendor/acacha/admin-lte-template-laravel/resources/views/layouts/partials/scripts.blade.php) (View: /appdata/var/www/html/tracking/vendor/acacha/admin-lte-template-laravel/resources/views/layouts/partials/scripts.blade.php)

The installer is not intended for installation in existing packages (or at least is not always guaranted to work). You will have to manually adapt you app.
This package (as a lot of Laravel packages) modifies/add to your app:

More source PHP code via composer: this works always with no problem when updating or installing Laravel packages in no fresh projects.
Remember to add/check AdminLTE service provider (https://github.com/acacha/adminlte-laravel/blob/master/src/Providers/AdminLTETemplateServiceProvider.php) to you app (this package use acacha/llum to automate this but suppose config/app.ph has been altered and in some conditions will not always work ). Waiting for Package autodiscover in Laravel (https://medium.com/@taylorotwell/package-auto-discovery-in-laravel-5-5-ea9e3ab20518) in Laravel 5.5!! So check you config/app.php file
Publish files from vendor yo your app with php artisan publish command: this is the tricky part! You can republish package files but be carefull about overwriting you code (use git to check changes).  So you have to manually mix your public/resources/src folder and compare with files in package

See also https://github.com/acacha/adminlte-laravel/issues/270

adding "JeroenNoten\LaravelAdminLte\AdminLteServiceProvider::class, solved the probleme" to config/app.php solved it for me


Steam/Epic/Others Ability to list all games in library and show installed/not installed games

Check for existing issue
Due dilligence done to check for any duplicate request types or issues.
Describe the solution you'd like
Would like to list all purchased games to the steam/epic user in their library and list them as either installed or not installed.
Simple first step would be to just have the ability to launch the other game engine to install the game if there is no easy way to request an install
Screenshots
Games for Epic/Steam are only listing installed games. can we list all available?

This is already supported. Go to plugin settings and enable import of uninstalled games.


Fix WithDockerfileTests container start failures.

This PR fixes #4792.
The issue was that the team that owns that image on MCR significantly changed the way it works (it just runs an executable rather than a web server that can service static content by the looks of it). To address this I changed to using the Mariner-based Nginx image also hosted on mcr.microsoft.com (because supply chain issues).
This resulted in a few necessary changes to the Dockerfile setups. Should all be unblocked now.
Microsoft Reviewers: Open in CodeFlow

This PR fixes #4792.

I think you meant https://github.com/dotnet/aspire/issues/4828 .


bpf: nodeport: constrain CT lookups to relevant entry types

The nodeport code typically only cares about specific types of CT entries
(those that have the .nodeport and/or .dsr flags set). It carries all sorts
of cruft to deal with aliased / stale entries.
As we can't bake the .nodeport / .dsr flags into the actual CT map key
(it's not flexible enough, and would break compatibility), do the next
best thing and teach the low-level CT lookup code about such constraints.
If the caller specifies a set of CT_ENTRY_* types, then the lookup code
will validate the matched entry accordingly.
If the matched entry doesn't match any of the types, it's treated as
CT_NEW. This for instance avoids any unwanted update to the entry's
statistics.
Note that ideally the "generic" CT lookups (bpf_lxc, HostFW, SNAT) would have the opposite behaviour, and exclude the nodeport-specific entry types from their lookup. Future work.

/test

/test

@gentoo-root :wave: I vaguely remember discussing this a while ago. Here is your chance to say that you hate it :grin: .

/test


Multi-image mode with imaginghelper

Hi,
I'm currently working with the latest released version of openseadragon to date (2.0.0) and the imaginghelper plugin. I currently have some problems with it like : the zoomlevel is incorrect and the result of physicalToDataPoint is not right. My guess is that the imaginghelper doesn't support the new true multi-image mode of openseadragon. I just want to know if anyone had this issue before and if there is a solution right now. If not I'll keep on debugging
Thanks !

You're correct, I need to update that plugin!!
Trying to squeeze some time...

You're welcome to patch it if you'd like ;)

Perfect, I'll look into that this monday, I'll try to do a patch. It's my first time on github :P

Closing in favor of https://github.com/msalsbery/OpenSeadragonImagingHelper/issues/8


Docs: update copyright in LICENSE.md (fixes #9)

This updates the license copyright as suggested by @kborchers in #9.

Thanks for your help!


UserAgent for android webview.

We need the WebView on Android devices to have a customizable User Agent string.
@Shchvova  FYI

According to the conversation with Vlad, he could implement setNativeProperty in Lua. Usage as follows:
webView:setNativeProperty("UserAgent", "Custom User Agent")

Thanks, we'll be happy to test it across devices when that's done.

@Shchvova do docs need an update for that? (I could have done this myself but I don't know if it needs changing :) )
https://docs.coronalabs.com/api/type/NativeDisplayObject/setNativeProperty.html

@sekodev Thanks! I just tested it and updated documentation.

Thanks @Shchvova. Build 3646 is working well for us!


ECDC-1594: Add total number of update messages to StatisticReporter

Add channel wise total number of updates to StatisticReporter

Thinking out loud: do we care what kind of messages are sent to Kafka (i.e. does it matter if they PVA or CA)?
If not, then we could just ask the producer to count how many messages it sends?
@matthew-d-jones what do you think?

should channel specific total number of updates be there? or just total number of updates can be enough.

This is quite a complex solution, which also involves quite a lot of work every time a PV update is handled. Although some optimisations could be made, for example not constructing the f string on every update in the handler, I think we should consider a different approach.
My suggestion would be to use a (threadsafe) counter that is very cheap to increment, for example:
import itertools
import threading

class Counter:
    """
    Threadsafe counter, optimised for write performance
    """
    def __init__(self):
        self._number_of_read = 0
        self._counter = itertools.count()
        self._read_lock = threading.Lock()

    def increment(self):
        next(self._counter)

    def value(self):
        with self._read_lock:
            # We can only get the value of counter by calling next()
            # so we work around this by accounting for the times we
            # increment it whilst reading the value
            value = next(self._counter) - self._number_of_read
            self._number_of_read += 1
        return value

I agree with Matt that incrementing such a counter in the produce() method to track the total number of messages could be sufficient.

Yes this looks interesting. I will implement this and get back to you guys in case have some questions. Thank you


Letters Shared Between Two Words

Before jumping into Pr first comment for assign.
Problem statement : Create a function that returns the number of characters shared between two words.
Probelm Link : https://edabit.com/challenge/qeCS48GXtK9NJLc9C
Choose one Cateorgy - Hard
Question category : Arrays,Strings
Before submitting a PR please Check some details.

[ ] fileName formet should be in camelcase
example- returnTheNextNumber.py

[ ] Choose label for Problem , example- "good first issue", "easy"

[ ] In file there should be problem statement and link to problem

/* Problem-Task : This program will add two numbers

Problem Link : https://edabit.com/challenge/qeCS48GXtK9NJLc9C
*/
int main() {
int bla;
return 0;
}
This repository is vaild for HacktoberFest2020

Read before making PR - How to contribute on Github
Good Luck.

Please assign this to me


[UI] - Fixed YAML text overlapping

Description
This PR fixes #5811
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Output:

Restarting the failed workflows.

All greens ✅

@Chadha93 any command for this code formatting or I need to do it manually?

@Chadha93 any command for this code formatting or I need to do it manually?

Ok, try manually once.

@Chadha93 any command for this code formatting or I need to do it manually?

Ok, try manually once.

ok

@subhradwip01 Could you please address the above changes?

Ya.. I will

Tested OK, merging this one, please do have a look at this issue https://github.com/meshery/meshery/issues/5862

Yayyy @subhradwip01  🎉


Periodically post a message

TBD

What's the idea here @woutermeuwis ?

Well, to periodically post a message 😅
I don't remember why, but at some point someone requested this 😂

a random message? that could be fun.
how about we make it random quotes instead and they come from a quote repository based on nerland discord users' quotes.

If i remember correctly the intention was for this to be configurable.
For example asking the bot to post something every hour.
This could either be a simple message, or actually be a command.
I could for example ask the bot to say ?membercount each hour, triggering it to actually log the membercount.
But once again, it's just vaguely in my memory :p

Is this issue still relevant? If yes, you can re-open.


Generate TPC-DS data on S3 is very slow

There is a long time hanging at the end of each table generations. We found that S3a rename is very very slow.

PR #139, #140 to upgrade Spark and Hadoop version

PR #145, #146  to enable magic committer for s3a

Done


[Feature Request] - Add Liquid BTC support

With the high fee environment and Sparrow being the wallet of choice I think it is only fitting to add support for the liquid network.

I do not see fees as some kind of negative externality, but simply Bitcoin working as designed. The Liquid network still has very low usage, and offers a different security model. Sparrow will continue to focus on the Bitcoin network.


TLS handshake timeout on pull

I'm running an S3 backed private registry secured by a self-signed certificate, and I'm getting a TLS handshake timeout when trying to pull an image.
I've followed the instructions for deploying a repo with a self-signed certificate, and docker login and docker push work perfectly.
My ca.crt files are located in /etc/docker/certs.d/<MY_DOMAIN>.com:5555/ca.crt
I've appended the ca.crt file I'm using for authentication to my certificate chain to mitigate this issue
I'm attempting this interaction between my server and my local docker-machine instance installed via docker toolbox, and in either direction push succeeds but pull fails.
Here's the 'docker version' output on my remote ubuntu VPS:
Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   76d6bc9
 Built:        Tue Nov  3 17:43:42 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   76d6bc9
 Built:        Tue Nov  3 17:43:42 UTC 2015
 OS/Arch:      linux/amd64

And the same for my docker-machine instance:
Client:
 Version:      1.8.3
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   f4bf5c7
 Built:        Mon Oct 12 18:01:15 UTC 2015
 OS/Arch:      darwin/amd64

Server:
 Version:      1.8.3
 API version:  1.20
 Go version:   go1.4.2
 Git commit:   f4bf5c7
 Built:        Mon Oct 12 18:01:15 UTC 2015
 OS/Arch:      linux/amd64

Here's the output I get on the pulling instance:
$ docker pull <MY_DOMAIN>.com:5555/wordpress
Using default tag: latest
latest: Pulling from wordpress
07d9e8952b29: Pulling fs layer
...
2650eb09e142: Pulling fs layer
a719479f5894: Already exists
91bac885982d: Already exists
unable to ping registry endpoint https://<MY_DOMAIN>.com:5555/v0/
v2 ping attempt failed with error: Get https://<MY_DOMAIN>.com:5555/v2/: net/http: TLS handshake timeout
v1 ping attempt failed with error: Get https://<MY_DOMAIN>.com:5555/v1/_ping: net/http: TLS handshake timeout

And here's the log output I see from the registry:
registry_1 | time="2015-11-20T12:52:13Z" level=warning msg="error authorizing context: basic authentication challenge: htpasswd.challenge{realm:\"Registry Realm\", err:(*errors.errorString)(0xc20802ac80)}" go.version=go1.4.3 http.request.host="<MY_DOMAIN>.com:5555" http.request.id=4b60afd3-9689-4c4c-9ce6-e99698858614 http.request.method=GET http.request.remoteaddr="<IP_ADDRESS>:62234" http.request.uri="/v2/" http.request.useragent="docker/1.8.3 go/go1.4.2 git-commit/f4bf5c7 kernel/4.1.10-boot2docker os/linux arch/amd64" instance.id=faae7048-4d08-45c1-9571-96e89e93252a version=v2.2.0
registry_1 | <IP_ADDRESS> - - [20/Nov/2015:12:52:12 +0000] "GET /v2/ HTTP/1.1" 401 87 "" "docker/1.8.3 go/go1.4.2 git-commit/f4bf5c7 kernel/4.1.10-boot2docker os/linux arch/amd64"
registry_1 | time="2015-11-20T12:52:27Z" level=info msg="response completed" go.version=go1.4.3 http.request.host="<MY_DOMAIN>.com:5555" http.request.id=932a4974-4d06-454a-b797-641492796fa3 http.request.method=GET http.request.remoteaddr="<IP_ADDRESS>:62285" http.request.uri="/v2/wordpress/manifests/latest" http.request.useragent="docker/1.8.3 go/go1.4.2 git-commit/f4bf5c7 kernel/4.1.10-boot2docker os/linux arch/amd64" http.response.contenttype="application/json; charset=utf-8" http.response.duration=9.702194028s http.response.status=200 http.response.written=64063 instance.id=faae7048-4d08-45c1-9571-96e89e93252a version=v2.2.0
registry_1 | <IP_ADDRESS> - - [20/Nov/2015:12:52:18 +0000] "GET /v2/wordpress/manifests/latest      HTTP/1.1" 200 64063 "" "docker/1.8.3 go/go1.4.2 git-commit/f4bf5c7 kernel/4.1.10-boot2docker os/linux arch/amd64"
registry_1 | 2015/11/20 12:53:15 http: TLS handshake error from <IP_ADDRESS>:62466: EOF
registry_1 | 2015/11/20 12:53:24 http: TLS handshake error from <IP_ADDRESS>:62465: EOF
...
registry_1 | 2015/11/20 12:54:09 http: TLS handshake error from <IP_ADDRESS>:62457: EOF

@spencerkohan  Can you rerun the daemon with debug mode enabled and inspect the logs?
Also, can you curl or use a browser to hit that endpoint using your certificate?  This should work:
curl -i -X GET https://<MY_DOMAIN>.com:5555/v2/wordpress/manifests/latest

Ok I'm trying this now.  Is there an easy way to run in debug mode when starting with docker-compose?  I'm looking at the docs and there's no mention of it.

compose starts the registry, it's the daemon you want to start in debug mode.  There is no other option except to restart it with the -d flag :cry:

In the process of trying to run the daemon in debug mode I ran into a problem with my ip tables.  I ended up rebooting the VPS hosting the registry, and now everything's working perfectly.  No idea what was the problem or what's changed, but unless I can reproduce I guess it must have been related to the host system and not docker or the registry.


CAMEL-20710 Implemented Objects.equals() for comparison of strings

CAMEL-20710 Implemented Objects.equals() for comparison of strings

/component-test camel-netty


Not resetting metrics when running in Gaggle mode

While continuing efforts to de-duplicate the code used in tests, I found that Goose is not resetting the metrics when running a load test in Gaggle mode. It behaves as if --no-reset-metrics is always set. Resetting the metrics is supposed to be a default behavior.

Intermittent test issues caused the feature to be reverted, reopening.


[WIP] PSR-6 Cache implementation of state storage

tests fail, also @neeckeloo could you first file an issue for each pull request and explain reasoning and the kind of issues you've been having so that we can discuss and choose the best solution

You can see #25 to understand why this PR build failed.
Do not you think you've closed the pull request a little prematurely? IMO, a pull request can aim to start a discussion like an issue.
I proposed to implement a state storage based on PSR-6 Cache interfaces to improve flexibility. Currently, the package allow only to use APC to store metrics.

No interest in this proposal? If not, I will have to create a small repository with this state storage implementation.

@neeckeloo could you first file an issue for each pull request and explain reasoning and the kind of issues you've been having so that we can discuss and choose the best solution.


Newman is incompatable with newest versions of

Newman does not support the newest versions of node.js and npm. The newest version of node.js that seems to work is v0.10.29 with npm v1.4.14. When attempting to call newman with the newest versions, the following error is returned.
[root@myuser]# newman -h
/usr/local/lib/node_modules/newman/node_modules/jsdom-nogyp/lib/jsdom/level1/core.js:554
      Array.prototype.splice.call(this._childNodes, refChildIndex, 0, newChild
                             ^
TypeError: Cannot set property length of [object Object] which has only a getter
    at Object.core.Node.insertBefore (/usr/local/lib/node_modules/newman/node_modules/jsdom-nogyp/lib/jsdom/level1/core.js:554:30)
    at Object.<anonymous> (/usr/local/lib/node_modules/newman/node_modules/jsdom-nogyp/lib/jsdom/level2/events.js:314:20)
    at Object.proto.(anonymous function) [as insertBefore] (/usr/local/lib/node_modules/newman/node_modules/jsdom-nogyp/lib/jsdom/utils.js:23:26)
    at Object.core.Node.appendChild (/usr/local/lib/node_modules/newman/node_modules/jsdom-nogyp/lib/jsdom/level1/core.js:672:17)
    at /usr/local/lib/node_modules/newman/node_modules/jquery/dist/jquery.js:4006:18
    at /usr/local/lib/node_modules/newman/node_modules/jquery/dist/jquery.js:4026:3
    at module.exports (/usr/local/lib/node_modules/newman/node_modules/jquery/dist/jquery.js:31:12)
    at Object.<anonymous> (/usr/local/lib/node_modules/newman/src/utilities/PreRequestScriptProcessor.js:6:48)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)

I am using node v0.11.14 and npm 2.0.0
Me too facing the same error.  Anyone having the same problem ?

I'm using the latest versions of node (0.10.36) and npm (2.4.1), and Newman is working fine for me.
http://puu.sh/fqGix.png

Thanks @abhijitkane  its working fine with (0.10.36 - Officially updated node version ). Most of our build tools using the more advanced version of node. That's why i faced the issue.


Update circle ci

PR contains two changes:

Update CircleCI version from 1.0 to 2.0. (1.0 will not longer be supported in August.) Tests are traditional unit tests.
A prototype for ecosystem plugin tests. Any branch named n.n.n-build will execute a second series of tests where a manager is installed along with several blueprints.


Feature/wiki permission change

This improves the cases in which wikis' sharejs uuids will be migrated, barring users who no longer should have access from accessing these pages. This includes a permission change to read-only, as well as migrations on wiki pages that have not yet been saved.

Pass finished. :nut_and_bolt:

:ship: :it:


Research alternative algorithms for detecting CRISPR repeats and spacers

CRISPRfinder has been giving us issues, so it would be good to investigate if there are alternatives that might work better.
These are all the CRISPR-detecting programs that I know of:

CRISPRfinder
MetaCRT
PilerCR
crispi CRISPR interactive database
CRISPRAlign

I think, of this list, CRISPRfinder is still the best for our purposes, but if there are others out there we should find out.
The Koonin paper we've heavily referenced says they use CRISPRfinder via the procedure outlined in CRISPRmap: an automated classification of repeat conservation in prokaryotic adaptive immune systems and CRISPRstrand: predicting repeat orientations to determine the crRNA-encoding strand at CRISPR loci, which are definitely worth checking out.

A new version of CRISPRfinder has been released, so we plan on continuing to use that!


handle empty docker auths cleanly

fixes https://github.com/openshift/source-to-image/issues/640
@jim-minter ptal

[test]

(longer term we should probably be removing this custom parser logic and using the docker engine library assuming it has something appropriate.  we're using fsouza/go-dockerclient to handle this in origin)

[test]

[test]

[test]

@oatmealraisin ptal

@coreydaley ptal

@bparees lgtm

[merge]

@bparees fyi I never got an e-mail notification for your 'ptal' message and github didn't cc me on the issue, hence the radio silence!

(longer term we should probably be removing this custom parser logic and using the docker engine library assuming it has something appropriate. we're using fsouza/go-dockerclient to handle this in origin)

Maybe; actually I had a look at this a while back.  There are two principal problems:

upstream, docker has rather moved from .dockercfg files to preferring config.json files, and origin especially has a fair amount of logic centred around .dockercfg files which may be troublesome to adjust.  That bridge may need to be crossed at some point, but for now I thought it added churn for little value.
the docker client library code doesn't expose methods for reading in arbitrary .dockercfg files (it looks for $DOCKER_CONFIG/config.json first, then $HOME/.docker/.dockercfg as a fallback). Reading an arbitrary .dockercfg is currently allowed as a s2i command line switch and is also used by Origin through our API, and all of that would need to be deprecated / reworked as well.

belatedly, fwiw, perhaps this is worth a test case.

fyi I never got an e-mail notification for your 'ptal' message and github didn't cc me on the issue, hence the radio silence!

weird.  github must be censoring me.
Thanks for the background on utility logic for parsing the various dockerconfig formats.  I guess we'll leave it as is for now.
Agreed that it's worthy of a TC.


[Bug] Error tauri.conf.json error on tauri > bundle > targets: ["all"] is not valid under any of the given schemas

Search before asking

[X] 我在 issues 列表中搜索，没有找到类似的内容。
I searched in the issues and found nothing similar.

Pake version
1.3.0
System version
Manjaro Linux x86_64 KDE
Node.js version
18.14.2
Minimal reproduce step
pake {url} --name desktop-client --transparent
What did you expect to see?
build deb success
What did you see instead?
Error logs
npm verb reify failed optional dependency /home/shun/node/lib/node_modules/pake-cli/node_modules/fsevents
npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 33526ms

up to date, audited 237 packages in 34s

78 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm verb exit 0
npm info ok

><EMAIL_ADDRESS>build
> npm run tauri build --release

><EMAIL_ADDRESS>tauri
> tauri build

       Error `tauri.conf.json` error on `tauri > bundle > targets`: ["all"] is not valid under any of the given schemas
file:///home/shun/node/lib/node_modules/pake-cli/dist/cli.js:1828
                reject(new Error(`${code}`));
                       ^

Error: 1
    at file:///home/shun/node/lib/node_modules/pake-cli/dist/cli.js:1828:24
    at /home/shun/node/lib/node_modules/pake-cli/node_modules/shelljs/src/exec.js:145:9
    at ChildProcess.exithandler (node:child_process:427:5)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5)

Node.js v18.14.2

Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

#360 https://github.com/tw93/Pake/issues/113


Editor's Bracket styling for C/C++ and C#  seems to be only following javaScript style bracket-styling

Spotted by @binnysenpai
Apparently, the Editor only follow JavaScript-style bracket-styling for the autobracket formatting for C#/C++ files.
video link
Usually in Visual Studio, this would be autoomaticaly formatted by automatically newline the opening bracket and put the statement after the line.
And also it seems not to format automatically  this type of statements
video link
Which should look like this

What yu refer to is the 'format on type' feature. That would have to be provided by the language extension. Please file a request directly to https://github.com/OmniSharp/omnisharp-vscode for c# or https://github.com/Microsoft/vscode-cpptools/issues for cpp.

Thank you, will be reposting this issue in Omnisharp repo


fix: No files generated by Buf.build inside NPM package [DEV-3499]

Task linked: DEV-3499 Fix no files generated in ts-proto package by Buf.build


Not being unmounted properly

I bumped into a bizarre bug with svelte-calendar and pagejs (?) and to keep momentum I had to move onto a different calendar component. Although I'd enthusiastically re-test this for you a I think you're currently the top svelte calendar component out there.
I can't seem to produce a minimal repro and really can't spend any more time on it, but here's an executive summary:
Under some condition (not sure which condition), the svelte-calendar component was preventing its parent components from being removed from the DOM. I'm assuming there's an unmount that's not being returned to clean something up, or that the unmount is asynchronous and doesn't actually resolve.
In any case, I can't safely blame svelte-calendar apart from noting that removing the calendar and replacing with a native input worked fine.
The calendar was being used like this:
<Calendar bind:selected={from}>
  <button class="calendar-button">
    {formatButton(from)}
  </button>
</Calendar>

Interesting, I'll see if I can reproduce with the pagejs router I have for svelte.  Thanks for letting me know!

No problem. I definitely don't expect it to be fixed. It's working for you, which is great. I can absolutely test for you, though. Let me know

Also worth noting. It wasn't the slot usage that broke it. (Got the same bug with <Calendar bind:selected={from} />)

@Crisfole Do you get a stack trace when this happens?  I'm seeing something similar to what you've described when I npm link svelte-calendar into a project but can't seem to reproduce with it installed normally.

No...it just sort of sticks around... Can you push a repro? I'll test?
On Wed, Aug 7, 2019, 6:27 PM Jonathan Greenemeier<EMAIL_ADDRESS>wrote:

@Crisfole https://github.com/Crisfole Do you get a stack trace when
this happens? I'm seeing something similar to what you've described when I npm
link svelte-calendar into a project but can't seem to reproduce with it
installed normally.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/6eDesign/svelte-calendar/issues/32?email_source=notifications&email_token=AADE4NILJU7ZNFPJV5J2YETQDND43A5CNFSM4IJXDTQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3Z4EWY#issuecomment-519291483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADE4NM7WPZKZUUD5TFPXVTQDND43ANCNFSM4IJXDTQQ
.

I think this is a duplicate of https://github.com/6eDesign/svelte-calendar/issues/65 which is better described, and it's actually a bug in Svelte.

Also relates to this issue https://github.com/sveltejs/sapper/issues/814


Implement StableAddress and CloneStableAddress for OwningRef where appropriate

This enables nesting of OwningRef.
I'm a bit confused as to why crates.io has version 0.2.1 but the master branch here is 0.2.0. I've bumped the version to 0.2.2 to be safe.

Thanks!


Challenge completion indicator should not have side margin

Description
A2 English blocks have challenges whose title is displayed next to a completion indicator. The indicator is having a right margin, which creates a gap between the indicator and the text.

This issue is because the indicator has a badge class:
https://github.com/freeCodeCamp/freeCodeCamp/blob/29326e64242782dbfeef744bf978a70be8a66091/client/src/templates/Introduction/components/challenges.tsx#L35
This badge class was harmless as it didn't have any CSS rules associated, until we added badges to the user profile page, which caused a class name collision:

https://github.com/freeCodeCamp/freeCodeCamp/blob/29326e64242782dbfeef744bf978a70be8a66091/client/src/components/profile/components/camper.tsx#L67
https://github.com/freeCodeCamp/freeCodeCamp/blob/29326e64242782dbfeef744bf978a70be8a66091/client/src/components/profile/components/camper.css#L89-L91

Affected page
https://www.freecodecamp.org/learn/a2-english-for-developers/
Changes needed

Remove the badge class from:

https://github.com/freeCodeCamp/freeCodeCamp/blob/29326e64242782dbfeef744bf978a70be8a66091/client/src/templates/Introduction/components/challenges.tsx#L35
https://github.com/freeCodeCamp/freeCodeCamp/blob/29326e64242782dbfeef744bf978a70be8a66091/client/src/templates/Introduction/components/challenges.tsx#L45

Rename the badge class in camper.tsx to camper-badge to avoid future collision

I can take this one, but I don't seem to have the permissions to assign myself to this issue. 🤷

Awesome, thanks for clarifying!


Implement auth by service account

We're currently only using authentication via OAuth which requires an admin in the flow to periodically consent.
This issue is to implement authentication via Service Account for MTA purposes.

It looks like I have this working. Don't have a PR yet, but wanted to capture the changes:

In auth.py add support for loading credentials for a service account. That looks something like

creds = SvcCredentials.from_service_account_file(cred_path).with_scopes(SCOPES).with_subject(user_email)

This requires adding a new parameter for user_email which is the email address of a user that has necessary access to the APIs.

Add a new paramater for customer_id. It should replace instances of my_customer in API calls (but can default to that value).

The service account will need domain-wide delegation with the API scopes to be able to run. (doesn't need to be assigned an admin role like we thought.)

The service account will need domain-wide delegation with the API scopes to be able to run. (doesn't need to be assigned an admin role like we thought.)

Any reason domain-wide delegation needs to be enabled for the service account in our use case? Haven't dug into it myself but the documentation emphasizes to use domain-wide delegation only as a last resort.

So in testing I get an error Access denied. You are not authorized to read activity records. when I don't have domain-wide delegation, but do have the service account added with an appropriate role. I haven't found documentation from Google yet, but SO answers point to needing domain-wide delegation to access activity records. answer 1 | [answer 2](https://stackoverflow.com/a/52057067]


Google Play Games and the emulator

Is Google Play Games login supposed to work in the emulator?
I can log in on hardware devices.
But on the Android Emulator - NEXUS 5 - API 25, I get:
07-01 22:03:22.652 5858-5858/com.steenriver.buggy V/GamesNativeSDK: Play Games callback indicates connection failure.
07-01 22:03:22.652 5858-6124/com.steenriver.buggy I/GamesNativeSDK: UI interaction required to connect to Google Play.

It does not work in the emulator because the Play Games App is not part of the emulator image.
You'll need to use an emulator configuration that includes the Play Store - then you'll be able to install the required apps.

Thanks, but my emulator has Google Play Games app running on it.
https://lh3.googleusercontent.com/-1BRH9SrE-G0/WV2thfgOaBI/AAAAAAAAElA/S3icTARj4n4CXbX-lRbKRTtet5YZbygXgCL0BGAs/w519-d-h923-p/emu.png

Be careful with the emulator.  I am getting some strange crashes to do with Static variables being handled differently.  Physical devices is the best way to test.


[KCC] Add the testcase for simple-project solution

Updated the original solution to make project-id a required setter.
Added the feature to append a random ID when the value needs to be globally unique.

The updated test-cli will be uploaded after the PR is merged.


Extend section about global variables with info about automatic imports

... and add subtitle for ProvidePlugin within section "Provided Plugins"

Thank you, was just thinking about doing this myself!


When I try the example, i get the following error: Precondition Failed

Describe the bug
Today i bought 2 tile sticker. I was able the activate them in the app. Then i try to get the information with this python module. But I get an error message: Precondition Failed.
To Reproduce
Steps to reproduce the behavior:
I go to the pypi page of pytile. And use the example (Create a client, initialize it, and get to work)
Then i fill in the correct login credentials. When i run python3 test.py I get that message.
Expected behavior
I should work.
Screenshots
[pytile]$ python3 test.py
Traceback (most recent call last):
  File "test.py", line 18, in <module>
    asyncio.get_event_loop().run_until_complete(main())
  File "/usr/local/Cellar/python/3.7.4_1/Frameworks/Python.framework/Versions/3.7/lib/python3.7/asyncio/base_events.py", line 579, in run_until_complete
    return future.result()
  File "test.py", line 15, in main
    await client.tiles.all()
  File "/usr/local/lib/python3.7/site-packages/pytile/tile.py", line 31, in all
    "get", "tiles", params=[("tile_uuids", uuid) for uuid in tile_uuid_list]
  File "/usr/local/lib/python3.7/site-packages/pytile/client.py", line 105, in request
    ) from None
pytile.errors.RequestError: Error requesting data from tiles: 412, message='Precondition Failed', url=URL('https://production.tile-api.com/api/v1/tiles?tile_uuids=********&tile_uuids=p!*******&tile_uuids=p!******')

What are the contents of test.py? That's not a file in this repo.

This is my content:
import asyncio
from aiohttp import ClientSession
from pytile import Client
async def main() -> None:
"""Create the aiohttp session and run the example."""
async with ClientSession() as websession:
client =<EMAIL_ADDRESS>"********", websession)
await client.async_init()
    # Get all Tiles associated with an account:
    await client.tiles.all()

asyncio.get_event_loop().run_until_complete(main())

That looks good.
When I run the exact same code with my credentials, my Tile data comes back as expected (no 412 error).
I'm curious about the first line of your description:

Today i bought 2 tile sticker.

Are you referring to these? If so, that's a possible difference (since I don't have that kind of tracker). Let me know and we can debug from there.

Yes, indeed. What I can do is reset my password and send my account to you so that you can test it.

That would be amazing; I'll treat it confidentially and let you know as soon as I'm done. You can reach me at<EMAIL_ADDRESS>

I have send you an email.

Got it! I can reproduce the error; will follow up when I have more info.

Good to hear!

@rolfberkenbosch Can you pull the latest dev and see if your script works?

@bachya there is an error in your new example:
`
import asyncio
from aiohttp import ClientSession
from pytile import login
async def main() -> None:
"""Create the aiohttp session and run the example."""
async with ClientSession() as websession:
client = await<EMAIL_ADDRESS>"*******", websession)
    # Get all Tiles associated with an account:
    await client.tiles.all()

asyncio.get_event_loop().run_until_complete(main())
`
Traceback (most recent call last):   File "test.py", line 5, in <module>     from pytile import login ImportError: cannot import name 'login' from 'pytile' (/Users/rolfberkenbosch/Projects/Git/pytile/pytile/__init__.py)

Instead of login, we should use async_login

With pypi package 3.0.0 i'm not getting any errors. So you have fixed it ? Because your example let not see any output of locations of the trackers.

@bachya I can confirm it is working. I have modified the files in home-assistant, and it is also working with the pypi 3.0.0 version.  Should I send  the fix to home-assistant ?

@bachya there is an error in your new example:

Good catch; I'll get that fixed.

@bachya I can confirm it is working. I have modified the files in home-assistant, and it is also working with the pypi 3.0.0 version. Should I send the fix to home-assistant ?

Wonderful! If you have the time and inclination to submit a HASS PR, please do.


Zigbee2MQTT not updating HA Entities

When adding devices to zigbee2mqtt the devices appear after pairing and can be controlled, however zigbee2mqtt is not updating Home Assistant with the new entities, thus they are not visible in the developer list, nor in Node Red.
If I rename the device and mark it to update Home Assistant this also does not work.
version: 1.18.1-1
CONFIGURATION

data_path: /config/zigbee2mqtt
external_converters: []
devices: devices.yaml
groups: groups.yaml
homeassistant: true
permit_join: false
mqtt:
  base_topic: zigbee2mqtt
serial:
  port: >-
    /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B001CCC7177-if00
advanced:
  log_level: warn
  pan_id: 6754
  channel: 11
  network_key:
    - 1
    - 3
    - 5
    - 7
    - 9
    - 11
    - 13
    - 15
    - 0
    - 2
    - 4
    - 6
    - 8
    - 10
    - 12
    - 13
  availability_blocklist: []
  availability_passlist: []
device_options: {}
blocklist: []
passlist: []
queue: {}
frontend:
  port: 8099
experimental: {}
socat:
  enabled: false
  master: 'pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777'
  slave: 'tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5'
  options: '-d -d'
  log: false

// replace this line with your pasted configuration

**Running platform (details from Suypervisor > System)**

Core: core-2021.3.4
Supervisor: supervisor-2021.03.9
Operating System: Home Assistant OS 5.12

**Your logs from Home Assistant Supervisor**

1-04-07 09:28:01 INFO (MainThread) [supervisor.host.network] Updating local network information
21-04-07 09:28:02 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-04-07 09:28:02 INFO (MainThread) [supervisor.host] Host information reload completed
21-04-07 09:28:02 INFO (MainThread) [supervisor.host.apparmor] Loading AppArmor Profiles: {'hassio-supervisor'}
21-04-07 09:28:02 INFO (MainThread) [supervisor.host.services] Reloading local service hassos-apparmor.service
21-04-07 09:28:02 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-dns with version 2021.01.0
21-04-07 09:28:02 INFO (MainThread) [supervisor.plugins.dns] Starting CoreDNS plugin
21-04-07 09:28:03 INFO (SyncWorker_1) [supervisor.docker.dns] Starting DNS homeassistant/aarch64-hassio-dns with version 2021.01.0 - <IP_ADDRESS>
21-04-07 09:28:03 INFO (MainThread) [supervisor.plugins.dns] Updated /etc/resolv.conf
21-04-07 09:28:03 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-audio with version 2021.02.1
21-04-07 09:28:03 INFO (MainThread) [supervisor.plugins.audio] Starting Audio plugin
21-04-07 09:28:04 INFO (SyncWorker_0) [supervisor.docker.audio] Starting Audio homeassistant/aarch64-hassio-audio with version 2021.02.1 - <IP_ADDRESS>
21-04-07 09:28:04 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-cli with version 2021.03.1
21-04-07 09:28:04 INFO (MainThread) [supervisor.plugins.cli] Starting CLI plugin
21-04-07 09:28:05 INFO (SyncWorker_0) [supervisor.docker.cli] Starting CLI homeassistant/aarch64-hassio-cli with version 2021.03.1 - <IP_ADDRESS>
21-04-07 09:28:05 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-observer with version 2020.10.1
21-04-07 09:28:05 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/aarch64-hassio-multicast with version 2021.04.0
21-04-07 09:28:05 INFO (MainThread) [supervisor.plugins.multicast] Starting Multicast plugin
21-04-07 09:28:05 INFO (SyncWorker_1) [supervisor.docker.multicast] Starting Multicast homeassistant/aarch64-hassio-multicast with version 2021.04.0 - Host
21-04-07 09:28:05 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-04-07 09:28:08 INFO (MainThread) [supervisor.homeassistant.secrets] Loaded 1 Home Assistant secrets
21-04-07 09:28:08 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to homeassistant/raspberrypi4-64-homeassistant with version 2021.3.4
21-04-07 09:28:08 INFO (MainThread) [supervisor.hassos] Detect Home Assistant Operating System 5.12 / BootSlot A
21-04-07 09:28:08 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/15d21743 repository
21-04-07 09:28:08 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/a0d7b954 repository
21-04-07 09:28:08 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/core repository
21-04-07 09:28:08 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/cebe7a76 repository
21-04-07 09:28:08 INFO (MainThread) [supervisor.store.git] Loading add-on /data/addons/git/7ad98f9c repository
21-04-07 09:28:09 INFO (MainThread) [supervisor.store] Loading add-ons from store: 69 all - 69 new - 0 remove
21-04-07 09:28:09 INFO (MainThread) [supervisor.addons] Found 12 installed add-ons
21-04-07 09:28:09 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/unifi/aarch64 with version 0.21.0
21-04-07 09:28:09 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-mosquitto with version 5.1.1
21-04-07 09:28:09 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to thomasmauerer/samba-backup-aarch64 with version 4.4
21-04-07 09:28:09 INFO (SyncWorker_5) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/adguard/aarch64 with version 4.0.0
21-04-07 09:28:09 INFO (SyncWorker_3) [supervisor.docker.interface] Attaching to zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.18.1-1
21-04-07 09:28:09 INFO (SyncWorker_4) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/bitwarden/aarch64 with version 0.9.0
21-04-07 09:28:09 INFO (SyncWorker_6) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/vscode/aarch64 with version 3.1.0
21-04-07 09:28:09 INFO (SyncWorker_7) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-letsencrypt with version 4.11.0
21-04-07 09:28:09 INFO (SyncWorker_1) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/node-red/aarch64 with version 8.2.1
21-04-07 09:28:09 INFO (SyncWorker_0) [supervisor.docker.interface] Attaching to homeassistant/aarch64-addon-duckdns with version 1.12.5
21-04-07 09:28:09 INFO (SyncWorker_5) [supervisor.docker.interface] Attaching to esphome/esphome-hassio-aarch64 with version 1.16.2
21-04-07 09:28:09 INFO (SyncWorker_2) [supervisor.docker.interface] Attaching to ghcr.io/hassio-addons/ssh/aarch64 with version 8.0.3
21-04-07 09:28:09 INFO (MainThread) [supervisor.snapshots] Found 7 snapshot files
21-04-07 09:28:09 INFO (MainThread) [supervisor.discovery] Loaded 2 messages
21-04-07 09:28:09 INFO (MainThread) [supervisor.ingress] Loaded 63 ingress sessions
21-04-07 09:28:09 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.SETUP
21-04-07 09:28:09 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-04-07 09:28:09 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.SETUP
21-04-07 09:28:09 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-04-07 09:28:09 INFO (MainThread) [main] Running Supervisor
21-04-07 09:28:10 INFO (MainThread) [supervisor.hassos] Rauc: A - marked slot kernel.0 as good
21-04-07 09:28:10 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.INITIALIZE' starting 0 add-ons
21-04-07 09:28:10 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SYSTEM' starting 1 add-ons
21-04-07 09:28:11 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-mosquitto with version 5.1.1
21-04-07 09:28:13 INFO (MainThread) [supervisor.services.modules.mqtt] Set core_mosquitto as service provider for mqtt
21-04-07 09:28:16 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.SERVICES' starting 6 add-ons
21-04-07 09:28:16 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/vscode/aarch64 with version 3.1.0
21-04-07 09:28:18 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/unifi/aarch64 with version 0.21.0
21-04-07 09:28:18 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/ssh/aarch64 with version 8.0.3
21-04-07 09:28:19 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/bitwarden/aarch64 with version 0.9.0
21-04-07 09:28:21 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on homeassistant/aarch64-addon-duckdns with version 1.12.5
21-04-07 09:28:21 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/adguard/aarch64 with version 4.0.0
21-04-07 09:28:27 INFO (MainThread) [supervisor.core] Start Home Assistant Core
21-04-07 09:28:27 INFO (SyncWorker_6) [supervisor.docker.interface] Starting homeassistant
21-04-07 09:28:27 INFO (MainThread) [supervisor.homeassistant.core] Wait until Home Assistant is ready
21-04-07 09:28:30 INFO (MainThread) [supervisor.api.security] /network/interface/default/info access from a0d7b954_adguard
21-04-07 09:28:49 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.STARTUP
21-04-07 09:28:49 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
21-04-07 09:28:55 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-04-07 09:29:06 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
21-04-07 09:29:06 INFO (MainThread) [supervisor.addons] Phase 'AddonStartup.APPLICATION' starting 4 add-ons
21-04-07 09:29:07 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/node-red/aarch64 with version 8.2.1
21-04-07 09:29:07 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on esphome/esphome-hassio-aarch64 with version 1.16.2
21-04-07 09:29:09 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on thomasmauerer/samba-backup-aarch64 with version 4.4
21-04-07 09:29:10 INFO (MainThread) [supervisor.api.security] /host/info access from a0d7b954_esphome
21-04-07 09:29:11 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.18.1-1
21-04-07 09:29:16 INFO (MainThread) [supervisor.misc.tasks] All core tasks are scheduled
21-04-07 09:29:16 INFO (MainThread) [supervisor.core] Supervisor is up and running
21-04-07 09:29:16 INFO (MainThread) [supervisor.host.info] Updating local host information
21-04-07 09:29:16 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
21-04-07 09:29:16 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
21-04-07 09:29:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
21-04-07 09:29:16 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
21-04-07 09:29:17 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
21-04-07 09:29:17 INFO (MainThread) [supervisor.resolution.check] System checks complete
21-04-07 09:29:17 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
21-04-07 09:29:17 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
21-04-07 09:29:17 INFO (MainThread) [supervisor.host.services] Updating service information
21-04-07 09:29:17 INFO (MainThread) [supervisor.host.network] Updating local network information
21-04-07 09:29:27 WARNING (MainThread) [supervisor.dbus.network] Can't process /org/freedesktop/NetworkManager/Devices/30: Error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.freedesktop.DBus.Properties” on object at path /org/freedesktop/NetworkManager/Devices/30
21-04-07 09:29:27 INFO (MainThread) [supervisor.host.sound] Updating PulseAudio information
21-04-07 09:29:28 INFO (MainThread) [supervisor.host] Host information reload completed
21-04-07 09:29:56 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'mqtt'
21-04-07 09:29:57 INFO (MainThread) [supervisor.auth] Successful login for 'mqtt'
21-04-07 09:29:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
21-04-07 09:29:59 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
21-04-07 09:29:59 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running

Same issue here. Brand new install of HA and Zigbee2MQTT (after upgrading from a Pi3 to a Pi4). I can pair Zigbee devices, they do show up in the Zigbee2Mqtt web ui, but I can't find them in Home Assistant.

Small update here, I think I managed to get it back to work. I had to enable auto discovery for the MQTT integration. Now the Zigbee devices are added again.

Same issue !

If your devices are properly showing in the zigbee2mqtt UI but not in home assistant even after restart, the problem is with your MQTT integration. Either wrong authentication or some connectivity errors.
I recommend you use the built in authentication discovery with the built in mosquitto add-on.
Can you post the add-on logs as well?


arangod crash with [SchedWorker] caught unexpected signal 11 (SIGSEGV)

My Environment

ArangoDB Version:        3.7.10
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   systemd
Infrastructure:               own
Operating System:        Ubuntu 18.04
Total RAM in your machine:        256 GB
Disks in use:        HDD
Used Package:              Ubuntu .deb

Component, Query & Data
Affected feature:
arangod
AQL query (if applicable):
No specific query identified. We're not using graph features.
Dataset:
half a billion docs among multiple collections.
Size of your Dataset on disk:
~1TB
Note : a continuous replication to another machine is running
Steps to reproduce

Nothing special, usual ArangoJS clients running, server load relatively low
Sudden crash
kill -9 then start again (systemctl stop hanged for too long)

Problem:
With nothing special happening, at least no special circumstance identified, arangod suddenly crashes with the following error :
2021-05-27T13:09:09Z [47088] FATAL [a7902] {crash} ArangoDB 3.7.10 [linux], thread 1157457 [SchedWorker] caught unexpected signal 11 (SIGSEGV) accessing address 0x00007f67ffe4b6e0: signal handler invoked - image base address: 0x00007f6b627c5000 - CPU context: rip: 0x00007f67ffe4b6e0, rsp: 0x00007e5010cfd098, efl: 0x0000000000010202, rbp: 0x00007f6691dea2a0, rsi: 0x00007e5010d00ef8, rdi: 0x00007f67ffe4b840, rax: 0x00007f67ffe4b500, rbx: 0x00007f66ad89a5e0, rcx: 0x0000000000000011, rdx: 0xffffffffffffe3a8, r8: 0x00007f6b624008c0, r9: 0x0000000000000020, r10: 0x0000000000000088, r11: 0x00007e5010d02b20, r12: 0x00007f68009a8a40, r13: 0x0000000000000000, r14: 0x00007e5010cfd150, r15: 0x00007f66ad89a588
2021-05-27T13:09:09Z [47088] INFO [308c3] {crash} frame  1 [+0x00000000007e31c0] *no symbol name available for this frame
2021-05-27T13:09:09Z [47088] INFO [308c3] {crash} frame  2 [+0x00000000038000f2] *no symbol name available for this frame
2021-05-27T13:09:09Z [47088] INFO [ded81] {crash} available physical memory:<PHONE_NUMBER>32, rss usage:<PHONE_NUMBER>24, vsz usage:<PHONE_NUMBER>344, threads: 90

(previous log entry is a slow query, nothing special)
This is the first time it happens. Arangod had been running  with version 3.7.10 for around 2 months without any problem, and for 2 years and half with previous versions without any crash.
Memory was not exhausted, server load relatively low, CPU barely used.
Is it possible that this is due to a hardware issue, for ex. faulty RAM unit ?
Thanks for any advice.
Greetings,
Mathias

Unfortunately from the limited information available it is impossible to tell what caused this. However, what I can say is that the seg fault did not occur inside the arangod executable.
The address of the instruction that caused the seg fault ist 0x00007f67ffe4b6e0 (rip). The image base address of the arangod executable is 0x00007f6b627c5000 which is larger than rip, so the seg fault occured in some other lib in the process. Unfortunately that is all I can tell from the available information. The reported frames only point to the signal handling functions in arango that generate the provided log messages.

If this happens again, could you provide a coredump so we can take a look? If you need more information about how to create coredumps you can take a look at our README_maintainers.md.

Thank you for your analysis. We'll look for the coredump feature if it happens again.

Hi. It looks like it doesn't happen anymore with v3.8.*

marking as solved then.


Add support for specifying pin/touch policy on generated keys.

E.g. slot, err := yk.GenerateRSAWithPolicies(ykpiv.Authentication, 2048, ykpiv.PinPolicyAlways, ykpiv.TouchPolicyAlways)

Thanks for the patch, @JackOfMostTrades! Tons of stuff I never got around to (EC, policy), so thanks so much for this!


Image size compressor tool

Please make sure you do the following before filing your PR:

[x] Provide a video or screenshots of any visual changes made
[x] Run pnpm run check and make sure everything passes

I am a regular user of the image compressor tool, so i thought it would be useful to implement it here too but without any added packages.

This is awesome.


CMD+R should post a refresh notification.

For the sake of consistency, cmd+r should just post a refresh notification. This way other tools can also observe and react to the refresh without ugly hacks.

This is my first PR into the actual code, my previous one was just a doc change. I'm not quite sure how to figure out what failed.

Seems fine to me. Travis failure is probably unrelated.
@facebook-github-bot shipit

Thanks Nick, if you ever get a chance to make it onto the reactiflux Slack channel, I want to talk over the ListView section header touch problems with ya. :)


Terraform command 'plan' failed with exit code 'null'

Describe the bug
In one of my pipelines I get an error during terraform plan saying:
##[error]Terraform command 'plan' failed with exit code 'null'.
##[error]TypeError: Cannot read property 'toString' of null
To Reproduce
Can't understand what is actual does this, so I can't reproduce in another repo.
Expected behavior
Terraform plan goes through without any errors.
Pipeline Logs
Logs with debug mode:
##[debug]Exit code null received from tool '/azp/_work/_tool/terraform/1.7.3/x64/terraform'
##[debug]STDIO streams have closed for tool '/azp/_work/_tool/terraform/1.7.3/x64/terraform'
##[debug]allowTelemetryCollection=false
##[error]Terraform command 'plan' failed with exit code 'null'.
##[debug]Processed: ##vso[task.issue type=error;]Terraform command 'plan' failed with exit code 'null'.
##[debug]set TERRAFORM_PLAN_HAS_CHANGES=false
##[debug]Processed: ##vso[task.setvariable variable=TERRAFORM_PLAN_HAS_CHANGES;isOutput=false;issecret=false;]false
##[debug]allowTelemetryCollection=false
##[debug]command=plan
##[debug]command=plan
##[debug]secureVarsFile=undefined
##[debug]command=plan
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local
##[debug]command=plan
##[debug]environmentServiceName=***
##[debug]command=plan
##[debug]providerAzureRmSubscriptionId=undefined
##[debug]command=plan
##[debug]environmentServiceName=***
##[debug]runAzLogin=false
##[debug]command=plan
##[debug]publishPlanResults=undefined
##[debug]command=plan
##[debug]command=plan
##[debug]command=plan
##[debug]command=plan
##[debug]command=plan
##[debug]command=plan
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local
##[debug]backendType=local

Agent Configuration

OS: Ubuntu
Self Hosted
Terraform version used: Tried several. Including latest version (1.7.3)

Additional context
The Azure pipeline task is looking like this.
          - task: TerraformCLI@1
            displayName: "Run > terraform plan"
            inputs:
              command: "plan"
              environmentServiceName: "$(service_connection_name)"
              #publishPlanResults: "PlanResults"
              commandOptions: "-out=$(Build.ArtifactStagingDirectory)/$(Build.Buildnumber).tfplan -var azuredevops_personal_access_token=$(azuredevops_personal_access_token)"
              workingDirectory: $(working_directory)
              allowTelemetryCollection: false

I tried to comment out the publishPlanResults option, and the pipeline went through as expected. At next run I get the same error again.

When upgrading to azurerm 3.90 from 3.50 it looks like it actual gives me an error I can read, and not just throw exit code null. See issue mentioned above.

I experienced the same error in another pipeline which had an older Terraform version.
To get the error message The plugin.(*GRPCProvider).ConfigureProvider request was cancelled I also had to update Terraform version from 1.5 to 1.7.

I figured out what the problem actual was:
In my code I configure the azurerm provider several times to go against several Azure subscriptions. If I configured the azurerm provider six times against six different Azure subscriptions I got the error.
When configuring the provider so many times it looks like it uses more memory than on a normal run with one configured azurerm provider. My self-hosted Azure DevOps agent had 1 GB of memory. When increasing the memory to 2 GB everything works as expected.
So, the problem was actually that the Azure DevOps Agent ran out of memory.

I’m glad you solved it. Thanks for letting us know.


[Help for writing rule with Filter]

Hi all!
I have a query search like this ' NOT GeoIPfrom.country_name: Vietnam and Message_VPN: "GlobalProtect portal user authentication succeeded" '
I have written like this:
filter:

term:
Message_VPN: "GlobalProtect portal user authentication succeeded"
and:

not:
term:
GeoIPfrom.country_name: "Vietnam"
But it does not work exactly
Can anyone help me to write this rule please:
Thanks and Best Regards

You can check https://elastalert.readthedocs.io/en/latest/recipes/writing_filters.html#negation-and-or


Handle null offsets in MATH table

This lets math subtables be None instead of attempting to read at an offset of 0. As discussed in #110. It also moves the read_at_offset32 to a private stream extension for the ankr table as discussed. While this doesn't fully resolve the offset problem, it at least fixes the specific bug in the math table.

Ok, good for now. Do you need a version bump?
I might look for a better solution on the weekends.

Version bump would be nice, but I can also wait for after the weekend. :)

Done.

Thanks!


Epic reducer project

I think this is ready for merge!

@berekuk it's still failing the build; see the tests.

@berekuk it's still failing the build; see the tests.

  We've found a bug for you!
  /home/runner/work/squiggle/squiggle/packages/squiggle-lang/src/rescript/ReducerProject/ReducerProject.res:259:67-73

  257 │     let ofUser = Continuation.minus(those, these)
  258 │
  259 │     (getResultOption(project, "main")->Belt.Option.getWithDefault(IEvV
      │ oid->Ok), ofUser)
  260 │   }
  261 │ }

  The variant constructor IEvVoid can't be found.

I don't understand.
ReducerProject.evaluate refers to the naked IEvVoid without InternalExpressionValue, which shouldn't work, but sometimes it builds anyway. And sometimes it doesn't. (I managed to reproduce this once locally and then switched to other branch and back again, and now it builds).
@umuro

Codecov Report

Merging #1009 (044ed0b) into develop (462f1c9) will increase coverage by 0.76%.
The diff coverage is 77.70%.

:exclamation: Current head 044ed0b differs from pull request most recent head 247e101. Consider uploading reports for the commit 247e101 to get more accurate results

@@             Coverage Diff             @@
##           develop    #1009      +/-   ##
===========================================
+ Coverage    58.22%   58.98%   +0.76%
===========================================
  Files           74       82       +8
  Lines         4191     4396     +205
===========================================
+ Hits          2440     2593     +153
- Misses        1751     1803      +52

Impacted Files
Coverage Δ

...quiggle-lang/__tests__/Reducer/Reducer_Helpers.res
60.00% <ø> (-40.00%)
:arrow_down:

...ang/__tests__/Reducer/Reducer_TestMacroHelpers.res
77.77% <ø> (ø)

...g/src/rescript/Distributions/DistributionTypes.res
12.90% <ø> (ø)

...le-lang/src/rescript/Distributions/GenericDist.res
62.56% <ø> (ø)

...cript/Distributions/PointSetDist/PointSetTypes.res
11.76% <ø> (ø)

.../rescript/FunctionRegistry/Library/FR_Pointset.res
86.84% <ø> (ø)

...c/rescript/FunctionRegistry/Library/FR_Scoring.res
70.00% <ø> (ø)

...e-lang/src/rescript/Reducer/Reducer_ErrorValue.res
64.00% <0.00%> (-5.57%)
:arrow_down:

...ducer_Expression/Reducer_ExpressionWithContext.res
100.00% <ø> (ø)

...Expression/Reducer_Expression_BindingsReplacer.res
100.00% <ø> (ø)

... and 40 more

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


Can't get it to work on Breakout

I tried using DQfD for Atari Breakout but it didn't work (after 4 millions training steps, the average reward reached 40 and doesn't increase pass that. The normal DQN can go over 100). I tried different exploration epsilon (0.1 and 0.01). Different batch size (32 and 64). Different replay buffer size (5e5 and 1e6). However, they couldn't go pass 40.
Do you know what I should do or do you have a set of hyper parameters that works for Breakout.

Thank you for the experiment and I've observed the same problem.
I'm sorry I don't know the exact cause.
Perhaps, This is because There are some bugs or the DQN implementation is not so efficient.
(I tested Original DQN Implementation(OpenAI baselines) this code is based on and it couldn't go over 100 after 4M steps.)
I'll continue to investigate the cause.

Thank you

any progress？


Publish to grafana plugin repo

Please publish to grafana plugin repo

@nrukavkov Thank you for your interesting in the Environment Data Source. Unfortunately, it was rejected because of the security concerns exposing environment variables, which is the whole purpose of it.
The latest version signed as Private plugin for http://localhost, which works in the most cases if you are using NGINX in front of Grafana.
You can build and sign it for the specific domain if required.
Let us know if there is anything else.


copy paste replaced with a function

Summary: Copy paste replaced with a function
Type: Feature
Test Plan: UT
Jira: RIALTO-222

https://jenkins.code.rdkcentral.com/job/build-component/71362/ started.

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/github-triggered/2122/ started

https://jenkinsrdkm.cmf.code.rdkcentral.com/job/build-component-platform/4452/ started.

Sanity tests for ['RPI3 Hybrid/MC'] added.
https://jenkinsrdkm.cmf.code.rdkcentral.com/job/test-components-flow/10456/


Fixes to make this class work again.

Just helping out those looking for this...
@iStorry

@fijiwebdesign Thanks 👍


fix: add headerClassName and cellClassName

allow users to customize cell styles easily

Because one is flexbox and the other isn't, and also because you'll sometimes want styles to apply to one and not the other, I think it makes sense to namespace them.

Coverage remained the same at 89.783% when pulling b3abc28dc68bd7717a767d10b467730c60a37519 on lbirch/column-alignment into 72603243f8bda0b51799bf41ce7fcedd3b0d5e2f on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: