cf dev fails to start during Waiting for services to start

I recently had to recreate my instance of pcfdev and it now consistently fails to start up again. It looks like a certificate issue
$ cf dev start -m 16384
Using existing image.
Allocating 16384 MB out of 128847 MB total system memory (104842 MB free).
Importing VM...
^[	Starting VM...
Provisioning VM...
Waiting for services to start...
7 out of 58 running
7 out of 58 running
7 out of 58 running
7 out of 58 running
7 out of 58 running
28 out of 58 running
37 out of 58 running
48 out of 58 running
55 out of 58 running
<snip>
55 out of 58 running
55 out of 58 running
Timed out after 3600 seconds.
FAILED
Error: failed to provision VM: Process exited with: 1. Reason was:  ().

$ sudo tail -f /var/vcap/monit/monit.log
[UTC Feb 13 09:51:36] info     : 'metron_agent' start: /var/vcap/jobs/metron_agent/bin/metron_agent_ctl
[UTC Feb 13 09:52:06] error    : 'metron_agent' failed to start
[UTC Feb 13 09:52:06] error    : 'loggregator_trafficcontroller' process is not running
[UTC Feb 13 09:52:06] info     : 'loggregator_trafficcontroller' trying to restart
[UTC Feb 13 09:52:06] info     : 'loggregator_trafficcontroller' start: /var/vcap/jobs/loggregator_trafficcontroller/bin/loggregator_trafficcontroller_ctl
[UTC Feb 13 09:52:36] error    : 'loggregator_trafficcontroller' failed to start
[UTC Feb 13 09:52:36] error    : 'doppler' process is not running
[UTC Feb 13 09:52:36] info     : 'doppler' trying to restart
[UTC Feb 13 09:52:36] info     : 'doppler' start: /var/vcap/jobs/doppler/bin/doppler_ctl
[UTC Feb 13 09:53:06] error    : 'doppler' failed to start
[UTC Feb 13 09:53:16] error    : 'metron_agent' process is not running
[UTC Feb 13 09:53:16] info     : 'metron_agent' trying to restart
[UTC Feb 13 09:53:16] info     : 'metron_agent' start: /var/vcap/jobs/metron_agent/bin/metron_agent_ctl
[UTC Feb 13 09:53:46] error    : 'metron_agent' failed to start
[UTC Feb 13 09:53:46] error    : 'loggregator_trafficcontroller' process is not running
[UTC Feb 13 09:53:46] info     : 'loggregator_trafficcontroller' trying to restart
[UTC Feb 13 09:53:46] info     : 'loggregator_trafficcontroller' start: /var/vcap/jobs/loggregator_trafficcontroller/bin/loggregator_trafficcontroller_ctl
[UTC Feb 13 09:54:16] error    : 'loggregator_trafficcontroller' failed to start
[UTC Feb 13 09:54:16] error    : 'doppler' process is not running
[UTC Feb 13 09:54:16] info     : 'doppler' trying to restart
[UTC Feb 13 09:54:16] info     : 'doppler' start: /var/vcap/jobs/doppler/bin/doppler_ctl

$ sudo cat /var/vcap/sys/log/doppler/doppler.log | grep certi
...lots of the following
2019/02/13 09:55:56 Could not use GRPC creds for server: x509: certificate has expired or is not yet valid

$ sudo cat /var/vcap/sys/log/metron_agent/metron.log | grep certi
...lots of the following
2019/02/13 09:56:36 Could not use GRPC creds for client: x509: certificate has expired or is not yet valid

$ sudo cat /var/vcap/sys/log/loggregator_trafficcontroller/trafficcontroller.log | grep cert
...lots of the following
2019/02/13 09:56:36 Could not use GRPC creds for client: x509: certificate has expired or is not yet valid

$ cf version
cf version 6.35.2+88a03e995.2018-03-15

$ cf dev version
PCF Dev version 0.30.0 (CLI: 850ae45, OVA: 0.549.0)

@richard-cox Please upgrade to the newest version on the CF Dev plugin. The one that you are currently using is outdated.
$ cf uninstall-plugin cfdev
$ cf install-plugin -r CF-Community "cfdev"
$ cf dev version
CLI: 0.0.13

@aemengo Is that based on https://github.com/cloudfoundry-incubator/cfdev? If so that's not an option for myself and team due to the lack of linux support

@aemengo I have the same issue as Richard - I'm on linux, so can't switch to CF Dev.

@richard-cox @nwmac
Unfortunately, you're correct. The certificates baked into the previous PCF Dev are right around their expiration dates. There aren't many good workarounds to employ from your end. Ideally, you could simply update to the latest version so we apologize for linux support not currently being available.

Linux support can be tracked here: https://github.com/cloudfoundry-incubator/cfdev/issues/18

@aemengo would it be possible to rebuild PCF Dev 0.30 with fresh certificates and provide linux devs with a solution while we wait for CF Dev under Linux? PCF Dev 0.30.1 ?

I just tried to install PCFDev locally and get similar errors as above. Seems it is no longer possible to install & use PCFDev on linux systems anymore.

If the recommended version 0.0.13 is indeed newer than the 0.30 version the version numbering is rather confusing. Any sane person will assume the 0.30 is the newer one.
Also since I am on Linux I can't use that version (yet). But let's ignore that for a second as I have another concern.
I beleave that one of my coleagues recently tried the 0.0.13 version and it seemed to have much more restricted set of commands (also further re-inforcing the impression that its an ancient version). For example I don't beleave it supports a command like cf dev ssh (though it is hard for me to confirm this seeing as I cannot actually use it on my machine).
I should note that for testing our use case we use cf dev ssh to connect to the VM and make some minor configuration changes to uaa to allow for testing some oauth flow's locally. So unless cf dev ssh command is supported by 0.0.13 version it isn't going to work for us.

@kdvolder Completely apologize for the confusion. There's a lot of misinformation floating around which is why we are trying to correct it all, to the best of our ability.
cf dev ssh was never intended to be a user facing feature. It was a command we added for the developers on the project to debug efficiently. The newest iteration of CF Dev much more closely mimics a cloud deployment of Cloud Foundry. If you'd like to make changes to uaa and are familiar with BOSH tooling, the appropriate way to do so is export the appropriate BOSH environment variables and then ssh into the appropriate instance. For example, on mac:
$ eval "$(cf dev bosh env)"
$ bosh -d cf ssh uaa

It was a command we added for the developers on the project to debug efficiently.

Sounds useful to anybody? You should probably put it back. Just IMHO.
Anyhow... I think we re straying a bit from the issue at hand here. When the time comes and I need help with that. I'll raise another ticket about possibly putting the ssh command back and/or documenting better ways to do things and avoid using it. Thanks for all the helpful info / comments :-)

@aemengo thanks.
I read other threads about this certificates (I'm also using 0.30, which is the one suggested by default ). I ssh'ed as suggested on other threads to change VM's system date on /etc/init.d to comply with certificates dates (apil in 2018) but it's still complaining with the same issue.
Anyways, after executing the command you provided above on a Windows machine "cf uninstall-plugin cfdev", I'm getting:
Plugin cfdev does not exist
I found next one: pcfdev-v0.13.0, rather than 0.0.13. Is it publicly accessible?
Thanks in advance.

@lennarth-anaya
There's a typo in the instructions from @aemengo the old plugin is called 'pcfdev' and the new one 'cfdev' and the version numbers between the two are unrelated. So you uninstall 'pcfdev' then install 'cfdev'.
$ cf uninstall-plugin pcfdev
$ cf install-plugin -r CF-Community "cfdev"
$ cf dev version
CLI: 0.0.13

getting below
Searching CF-Community for plugin cfdev...
Plugin requested has no binary available for your platform.

Any previous versions can be tried under Linux

My understanding is... the answer is "no". The 'old' version people were using, (including myself) was pcfdev version 0.30.0. But it recently broke because of some ssl certificates that expired. That's precisely what this github ticket is about. So I'm afraid we are out of luck :-(

Or even better, to edit the cf.yml deployment manifest and then re-deploy.

@aemengo I'd like to to the above. I found cf.yml here ~/.cfdev/services/cf.yml This file is re-created every time cf dev is stopped and the started (CF is deployed). Is that the file to edit? If yes, how shall I re-deploy the CF? Some BOSH command?

@BoykoAlex Yes, that file is recreated every time that you run cf dev start. To re-deploy, using BOSH, you could edit the file (after a successful start) and then:
$ eval "$(cf dev bosh env)"
$ bosh -d cf deploy ~/.cfdev/services/cf.yml

You can find out more here: https://bosh.io/docs/quick-start/

I guess Linux folks like me are all a bit stuck right now. pcfdev no longer works at all and cfdev doesn't have Linux support yet.
I read the comments in https://github.com/cloudfoundry-incubator/cfdev/issues/18
and from the looks of things this is described as a 'major feature request'. Combined with the fact that it had been sitting in the icebox until 5 days ago, I gather this support may not be arriving for a little while. Is that right @aemengo ?
If yes, how about trying to patch the VM for pcfdev to fix those expired ceritificates? Is that a option? Maybe someone who knows what to do there could either
a) post some instructions for users to do this via cf dev ssh.
or even better
b) patch the actual vm that cf dev start downloads on the first run.
I'm asking because at the moment I'm really stuck, and so I gather is any other Linux dev who dependended on pcfdev as part of there development/testing workflow.

@kdvolder @nwmac  @dion-ict @bipinm @lennarth-anaya @gitcreate31 @BoykoAlex  As much as we rather not have you using that old version, your argument is hard to argue with. 🙂 We went with b). Just released a patch here with the troublesome certificates bumped: v0.30.1 for PCF1.11.0: https://network.pivotal.io/products/pcfdev#/releases/312110.
The certificates will expire again in one year, but we should have Linux support for the new architecture much further along. Always appreciate the engagement!

Thank you @aemengo .But I tried installing pcfdev-v0.30.1+PCF1.11.0-linux , when i run cf dev start , i am getting
"FAILED
Error: Pivotal Network returned: 404 Not Found."

I got the 404 first. After I did
cf uninstall-plugin pcfdev
cf install-plugin -r CF-Community "cfdev"

It worked fine. v0.30.1 was pulled and PCF Dev works fine.

i am getting below error with cf install-plugin -r CF-Community "cfdev"
Searching CF-Community for plugin cfdev...
Plugin requested has no binary available for your platform.
FAILED

I tried installin 0.30.1 following these instructions: https://pivotal.io/platform/pcf-tutorials/getting-started-with-pivotal-cloud-foundry-dev/install-pcf-dev
I'm also getting the '404' error trying to start it.
$ cf dev start
FAILED
Error: Pivotal Network returned: 404 Not Found.

@pho-enix What you say didn't work for me. It still says the plugin is not available on Linux. I'm guessing that what you said here:

It worked fine. v0.30.1 was pulled and PCF Dev works fine.

... is probably not exactly what happened. Given the command you quoted I bet what you actually have 'pulled down' was 'cfdev version 0.0.13' not 'pcfdev version 0.30.1'.

@kdvolder @gitcreate31 Could you please give it another try? Are you still getting 404s?

@aemengo Donwloading vm ... 8% and rising :-) So looks like 404 issue is fixed.

Perfect.. All the services are up and running with v0.30.1  :)
The documentation @ https://docs.pivotal.io/pcf-dev/install-linux.html, states step 4 - "cf dev start", which starts a VM with 4 GB memory rather than the default 8 GB.  The 8 GB might not be sufficient as well, since the memory usage goes up to 17.9 GB in ubuntu after all services are started up (1.2 GB before VM startup)

So I've used pcfdev a bit yesterday and this morning. It now starts fine and seems to work fine for the most part.
Just one 'small' problem I have noticed is that log streaming from apps doesn't seem to work. I.e. pushing apps through various ways, including cf push, the STS boot dashboard and the app we are developing (our app uses cf java client to push other apps and stream their logs)... I get no errors but despite this there's never any log output being displayed for the app. The same also happens when I do cf logs <appname>.
@aemengo
Could this also be a certificate issue? I.e. maybe there's another expired certificate lurking somewhere?

@aemengo Thanks for updating! I've just successfully brought up v0.30.1 so will close this issue. However, as @kdvolder above, we also don't see any content in the log stream. Will investigate further next week.

@aemengo Thanks, this update got me back up and running as well.
I can confirm the issue @kdvolder @richard-cox are seeing, as well as 'cf app' always showing 0 disk and 0 memory usage (app running succesfully). The same behaviour when viewing app details on apps.local.pcfdev.io : 0 Bytes for Memory and Disk columns.

@richard-cox Fair enough to close this ticket. The issues about log streams (and app stats that @dion-ict noticed) are arguably different and less critiicial. I'll raise a separate ticket about the log streaming where this can be tracked independently.


run stylish-haskell script

This PR runs the scripts/haskell/stylish.sh script on the repository. It has become a bit stale.
This PR is unnecessary if we do #3078 , but we should merge one of them (along with a CI step to check stylish-haskell output).

The other PR sets columns: 80. Can we either make that change here too or remove it there?

One point on the newline style: If you're using your editor to search for the occurrence of an function in a file and you're looking for the import line, the search result might not now show where the function was imported from... Fairly minor point, but might make life a little more difficult for some.

I'm really dubious that it's worth the trouble of touching 314 files (or the 916 files of the other PR) and causing ongoing merge/rebase misery for all in-fly works.

I'm not 100% attached to this. An additional style check in CI would be useful, and we'd want to merge this along with it.
It'd be great if we could only run stylish-haskell on files that changed, to make this a more gradual transition.

@parsonsmatt says:

It'd be great if we could only run stylish-haskell on files that changed, to make this a more gradual transition

That can be done by making it part of a git pre-commit hook that only runs on files that are about to be commited.

I raised what I consdier major concerns about this in PR #3078.

@erikd Your concerns seem relevant to #3078 but I don't see how they apply here. Do you mean the "only indent four spaces past the module name" comment? That would likely require a patch to stylish-haskell to implement. I'm happy putting this on hold until that's done if that's the consensus on import-style.

@parsonsmatt Closing this because I'm pretty sure its been superseded.


New Feature: allow specifying of target host machine on every individual resource/data source

System Information
Linux distribution
 any
Terraform version
terraform -v

Terraform v1.5.7
on linux_amd64

Provider and libvirt versions
git describe --always --abbrev=40 --dirty

c8facd868b69360f4542f8907eb1cf4c7b2fffa8-dirty

Description of Issue/Question
The current recommendation for connecting to multiple hosts is to declare multiple providers and assign them aliases. Indeed, this is how hashicorp themselves recommend using multiple providers with AWS.
However, AWS is a service, where as libvirt is connecting directly to machines and therefore the use case is not exactly the same. Let's take for instance an enterprise which collocates multiple racks in multiple geographic locations (TOR,NYC,SFC). Each rack has an id (rackN), and in each rack there are 5 general purpose compute machines (generalN), 3 GPU enabled machines (gpuN), and 3 storage servers (storageN) with dedicated connectivity between. This gives each server a fqdn slug like tor-rack1-general2.evilcorp.com.
Now let's say an IaC engineer wants to create a module for an application that will allocate allocate a CPU frontend and a GPU backend, and allocate a storage device on the storage server.
The desired use-case for such a  module would  be something like so:
terraform {
  required_version = ">= 0.13"
  required_providers {
    libvirt = {
      source = "dmacvicar/libvirt"
      version = "1.0.0"
    }
    cloudflare = {
      source  = "cloudflare/cloudflare"
      version = "~> 4.0"
    }
    digitalocean = {
      source  = "digitalocean/digitalocean"
      version = "~> 2.0"
    }
  }
}

provider "digitalocean" {
  token = var.do_token
}

provider "cloudflare" {
  api_token = var.cf_token
}

provider "libvirt" {
  uri = "qemu+ssh://${var.target}/system?sshauth=privkey&no_verify=true"
}

module "dev" {
  source = "./foobar"

  region   = "TOR"
  hostname = "development"
  //...
}

module "uat" {
  source = "./foobar"

  region   = "TOR"
  hostname = "user-acceptance"
  //...
}

module "production" {
  source = "./foobar"

  region   = "TOR"
  hostname = "production"
  //...
}

Under the hood, the module foobar/main.tf would connect to an unknown number of host machines to accomplish this goal, something like:
resource "libvirt_volume" "local-data" {
  host = "${var.region}-rack1-storage.evilcorp.com"
  // ...
}

resource "libvirt_domain" "frontend" {
  host = "${var.region}-rack1-general2.evilcorp.com"
  // ...
}

resource "libvirt_domain" "compute" {
  host = "${var.region}-rack1-gpu2.evilcorp.com"
  // ...
}

Note how doing this with duplicated providers forces an abstraction leak: the IaC engineer working on the backend stuff now has to inform the application programmers that they need 3 providers to be able to call this module. Any changes to metal implementations cause application programmers to need to change their code, or IaC engineers to muck with code that isn't theirs.
I have implemented a full solution to this feature request here: https://github.com/memetb/terraform-provider-libvirt/compare/main...memetb:terraform-provider-libvirt:multi-connection?expand=1
Associated PR #1072
I have not submitted it as a PR because I used a currently outstanding PR as my branch base (I can rebase if there's interest for this to be pushed through).
Implementation Notes
A couple of improvements have been made which are of note:

there was an abstraction leak whereby definition modules would make use of locks and therefore need to call the configuration object. This abstraction has been corrected and a lock is obtained via an interface, this allows for...
per connection locking to allow for simultaneous deployment across any number of machines
for backwards compatibility, the host and uri arguments are both optional:

the provider uri argument, when specified, will act as a default URI to connect to
a host argument can be passed to any of the resources or data sources: if present, that host uri will be used, if absent the default URI will be used
if neither are present an error will be raised

Hi,
I strongly disagree with this provider handling multiple locations. Libvirt is just a service running on single machine and this provider is meant as a mean to connect to it. If there is need to communicate with multiple libvirt instances, there's a solution - multiple providers. If there's a need to orchestrate machines across different hosts, there are different solutions for that like oVirt, Proxmox, OpenStack, CloudStack or others.

I strongly disagree with this provider handling multiple locations. Libvirt is just a service running on single machine and this provider is meant as a mean to connect to it.

libvirt+ssh is a network service. Any machine which has a libvirt & ssh setup can be part of a cluster of servers which provide access to terraform this terraform provider.
terraform is an orchestration technology: the entire purpose of terraform is that it allows spinning up resources non-locally.
I'm not sure what your objection exactly is.

If there's a need to orchestrate machines across different hosts, there are different solutions for that like oVirt, Proxmox, OpenStack, CloudStack or others.

I'm not sure if you are suggesting the solution to having a terraform based problem is to use a non-terraform solution?

libvirt by itself work only on single machine level - I see no point in trying to somehow emulate it working on multiple hosts on provider level when perfectly working mechanisms already exists - multiple providers.
Having it on provider directly complicates internal structure and introduces another abstraction layer that does not have counterpart in pure libvirt - honestly it is huge effort with limited usecase and - as mentioned before - with existing mechanism to address it.

I'm not sure if you are suggesting the solution to having a terraform based problem is to use a non-terraform solution?

You are trying to achieve multi-host orchestration, which is not what libvirt is. It is not a libvirt problem domain so I suggested tools that solve multi-host problem.

You are trying to achieve multi-host orchestration, which is not what libvirt is. It is not a libvirt problem domain so I suggested tools that solve multi-host problem.

I'm not sure if you're saying "libvirt through terraform" , or just libvirt. The latter is a non-issue to begin with: I'm not trying to achieve anything in the libvirt library itself.
For the former, I have explained exactly the use case where this is useful:

The current recommendation for connecting to multiple hosts is to declare multiple providers and assign them aliases. Indeed, this is how hashicorp themselves recommend using multiple providers with AWS.

However, AWS is a service, where as libvirt is connecting directly to machines and therefore the use case is not exactly the same. Let's take for instance an enterprise which collocates multiple racks in multiple geographic locations (TOR,NYC,SFC).

The only difference between AWS and libvirt is that AWS API acts as an interposing stateless service allowing the declaration of a single provider and use slug values to "route" the destination resource.
This is not about orchestrating services on many hosts. It's about being able to declare (IaC) where your enterprise vault instances will live.


Add other CIFTI spaces

What would you like to see added in fMRIPrep?
I was reading Jeganathan et al. (preprint), and it seems like the onavg surface space would be preferable to fsaverage or fsLR in some (all?) situations, but the only surface spaces allowed for CIFTIs in fMRIPrep are fsLR-32k and fsLR-59k. I was wondering if it would be possible for fMRIPrep to add other CIFTI options.
Perhaps --cifti-output could be merged into --output-spaces, and the different CIFTI template combinations could be given unique identifiers there?
EDIT: Or maybe the output space string could be expanded to allow both a surface template+density and a volumetric template+resolution?
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
No response

That's an interesting question. We used to allow fsaverage5+MNI152NLin2009cAsym, but people did not love that the results were incompatible with HCP-pipelines CIFTI files.
Now we are using space-fsLR to clearly label these, so we could go back to permitting other spaces, but we would need to be clear on the processes here. Do we run msmsulc with onavg as a target, and what data files would be needed to achieve that? What's an appropriate volumetric space?
cc @feilong

@jaysonjeg Might be a good person to tag as well...

I'm thinking about generating sphere surfaces for onavg that are in align with fslr (current files are in align with fsavg). msmsulc generates the subject's sphere.reg that is in align with fslr, and we can use it to directly resample data to onavg. I need to perform some archeology to find these files.
Regarding the space, my personal preference is onavg + MNI152NLin2009cAsym. I agree with @tsalo's idea to allow combinations. For a few commonly used combinations we can support their short names for convenience.

I'm interested in switching to SUGAR which seems to have superior performance than msmsulc. At this moment, using msmsulc to align to fslr and resample using files in align with fslr is probably the best choice.

Perhaps one way of specifying combined spaces would to just use :: to delimit the surface space definition from the volumetric space definition? For example, dhcpAsym:cohort-42:den-32k::dhcpVol:cohort-42:res-2 would produce CIFTIs with the surface parts aligned to tpl-dhcpAsym_cohort-42_hemi-L_den-32k_sphere.surf.gii and the volumetric parts aligned to tpl-dhcpVol_cohort-42_res-2_T1w.nii.gz (which might be a good CIFTI space for Nibabies).

I'm thinking about generating sphere surfaces for onavg that are in align with fslr (current files are in align with fsavg). msmsulc generates the subject's sphere.reg that is in align with fslr, and we can use it to directly resample data to onavg. I need to perform some archeology to find these files.

@feilong does that mean any surface template could be used as long as its templateflow entry includes a sphere surface in alignment with fsLR?

Yes, theoretically we can use any surface template, and the naming convention makes sense to me.
I have some reservations simply naming the reference space fsLR. In practice, there are a few similar registration targets associated with fsLR. Initially there was conte69. The HCP data was aligned using hcp196, and the latest HCPPipelines include hcp449. I tend to treat them as different references, as the folding patterns associated with each of them are slightly different.

The registration references are available at HCPpipelines/global/templates/standard_mesh_atlases/{L,R}.refsulc.164k_fs_LR.shape.gii.
In the GIFTI head, the related files are named with Q1-Q6_Related449, and the IDs of the 449 participants can be found in the command.
In earlier commits of the repository (9f6189aabf7699c62d79987937d241717882a555), the files were different, and the tags in the GIFTI head were Q1-2-3_Related196.

I have some reservations simply naming the reference space fsLR.

That makes sense, though I think it's a separate issue for templateflow as long as the preps use the label consistently.
I'm trying to figure out the next steps. How does this sound?

Incorporate a naming convention for CIFTIs into niworkflows' Reference class (see https://github.com/nipreps/niworkflows/issues/881).

We need to ensure that the surface and the volume parts can be distinguished in the Reference object.

Limit surfaces in sMRIPrep/fMRIPrep to those that have a sphere file in alignment with fsLR.

I assume MSMsulc only works with a specific "version" of fsLR?

Add the requested surface space and the requested volume space to the list of output spaces within fMRIPrep.
Generalize the CIFTI-related workflows in fMRIPrep and sMRIPrep to use any surface and volume spaces with the necessary files, with fsLR as an intermediate step in the workflow.

I think Nibabies uses the dhcpAsym surface as an intermediate step between fsnative and fsLR, so maybe it already has some useful code for this? @mgxd is that correct?

Modify output filenames to include volspace and maybe volcohort.

The steps make sense to me.
Theoretically MSMSulc can be used with any space, but in practice it's often used with fsLR. For our purposes, it's also reasonable to use it with fsLR. Regarding the "flavor" of fsLR, I'm inclined to use hcp449, which is most up-to-date.

I'm thinking about generating sphere surfaces for onavg that are in align with fslr (current files are in align with fsavg). msmsulc generates the subject's sphere.reg that is in align with fslr, and we can use it to directly resample data to onavg. I need to perform some archeology to find these files.
Regarding the space, my personal preference is onavg + MNI152NLin2009cAsym. I agree with @tsalo's idea to allow combinations. For a few commonly used combinations we can support their short names for convenience.

Hi, @feilong,
First, align onavg to the fsLR, then align the individual space to fsLR, and finally resample the individual space data to onavg. The onavg results obtained this way will still be influenced by fsLR.
Additionally, this approach requires either a single resampling or double resampling, with two resamplings potentially affecting the FWHM.
If you directly align the individual space to onavg and then resample the individual space data to onavg, the resulting onavg will only be influenced by the onavg template.

Hi @NingAnMe,
This is related to the templateflow issue we've been talking about https://github.com/templateflow/templateflow/issues/171
The onavg template affords a resampling target, not a registration target.  In our paper we used FreeSurfer's registration algorithm and registration target, and we've been discussing replacing them with MSMSulc and one of the fsLR registration targets (e.g, hcp449).  This does not introduce an extra step.
We only resample the data once, from the individual's native space to onavg.  To do so, we need the individual's sphere and onavg's sphere to be aligned to the same registration target.  It does not matter which registration target it is.
The group statistics of the 1031 OpenNeuro participants can potentially be used as a registration target.  We haven't extensively explored this possibility yet.


ctr+s

Issue Type: Performance Issue
when saved the file is losing its style
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z)
OS version: Windows_NT x64 10.0.18363

Is this happening for all types of files? Are there any specific conditions this occurs under?

/needsMoreInfo
Please follow template for Bug not Perfomance Issue and provide all details required by template.
Also clear steps to reproduce this behavior.


Public Continuous Integration

Closes #6222  :green_heart: :green_heart: :green_heart:

[x] Setup Travis

[x] OS X setup. You can see a passing build here.
[x] script/cibuild didn't work out of the box on Travis; on my OS X machine it doesn't work either, showing the same failures. @kevinsawicki: any idea why we're getting those errors? run-specs task is not really reliable on my machine and I usually run tests through apm test: do you think we can keep it in Travis as well?
[x] Linux setup (to test builds only, as per current cibuild behavior).

[x] Ask Travis to enable multi-os setup, as it is disabled by default

Any idea or suggestion is most welcome, as usual. Thank you! :pray:
/cc: @atom/non-github-maintainers @atom/owners

any idea why we're getting those errors?

Those looks like integration spec errors, @maxbrunsfeld might know better

{"code":"ECONNREFUSED", "errno":"ECONNREFUSED", "syscall":"connect", "address":"<IP_ADDRESS>", "port":9515}

Yeah, it looks like chromedriver isn't running. Those tests try to run an executable at the path atom-shell/chromedriver/chromedriver. That executable is created by the download-atom-shell-chromedriver grunt task. Maybe we need to run that task as an additional install step.

Oh, nevermind, I just realized that the build you linked to was already running script/cibuild, which runs the aforementioned grunt task. Thinking...

@as-cii if you can reproduce these failures on your local machine, could you try focusing the integration tests, bumping this timeout to a larger number (a couple of seconds maybe) and re-running ATOM_INTEGRATION_TESTS_ENABLED=true apm test?
The tests currently have a very naive way of waiting for chromedriver to start up, just because it worked in our existing test and CI environments. If bumping the timeout fixes the problem on your machine, then I'll add a more complex polling-based strategy in place of this simple timeout, and hopefully that will fix the failures on Travis.

@maxbrunsfeld: thank you for your extensive investigation :metal:
The first thing I had to change on my machine was concurrency = 2 to concurrency = 1:  apparently this causes some race condition, which in turn arises issues such as ECONNREFUSED (may be related to this issue on selenium), or, even worse, it hangs the build (both on my machine and on Travis).
Bumping the timeout to 1000ms as you suggested seems to fix the issue: on my machine it always works now, whereas on Travis it randomly fails; using 5000ms allegedly works fine on Travis as well, thus confirming your hypothesis that our timeout is the culprit and that we may want to switch to a less flaky alternative. :sparkles:
@maxbrunsfeld: I think we can handle this as the selenium guys do https://github.com/SeleniumHQ/selenium/blob/master/dotnet/src/webdriver/DriverService.cs#L173-205. Namely, they constantly issue a GET request to the service, waiting for it to return 200. I don't know if you had something else in mind, but I feel like it could be a good starting point. What do you think?

@as-cii that looks perfect :guitar:.

Everything works nicely on Travis and, apparently, I managed to make AppVeyor work as well (I say "apparently" because the builds times out; read more below)
Installing packages and building Atom, however, takes a significant amount of time: on Travis this time is  ~18 minutes, whereas on AppVeyor it is more than 40 minutes, thus causing the build to timeout. We need to make that faster :zap:
Running specs takes a relatively short amount of time, therefore I wouldn't start optimizing from there (e.g. by splitting tests across many workers). By contrast, installing modules seems to be pretty slow and one idea could be to start caching dependencies; if we decide to go with that, I think there are a couple of problems with it:

AppVeyor: in order to cache dependencies we need to reach the end of the build. This can be easily worked around by running only one build with a modified appveyor.yml (e.g. spawn script/bootstrap only and cache everything). This feels somehow flaky as a workaround, though, and we may want to contact their support to ask for an extended build timeout (which we should reach anyway only when cache gets completely invalidated).
Travis CI: caching is enabled for private repositories and on the new "container infrastructure" only. I see two solutions to this issue:

Contact the support team and ask them if we could make use of their cache despite Atom being public;
Build our own cache layer;

@maxbrunsfeld @kevinsawicki: what's your take on this? Any feedback or suggestion is very welcome :+1:
Thank you! :pray:

@as-cii Re: Travis, after a quick look-over of the cibuild script I didn't see anything that would require sudo. It looks like we should be able to move to the container infrastructure without much hassle, unless I'm missing something. (The caching is also free now for public repositories with the container-based infrastructure.)

@mnquintana: thank you for your reply :bow: The requirement, however, is to run specs across several platforms: where possible I'd love to make use of the existing caching infrastructure, but, as far as I know, this is simply not possible on their OS X public boxes by default.
Moreover, when we'll settle on a caching option (assuming we should cache at all), my idea would be to have as little differences as possible among our CI scripts: namely, I'd prefer not to have two different caching strategies for two different platforms. I agree, however, that we shouldn't try to reinvent the wheel if we have other alternatives at hand :+1:

@maxbrunsfeld @kevinsawicki: seems like we have our first properly configured build! https://travis-ci.org/atom/atom/builds/57928777 :tada: :tada: :tada:
Unfortunately it's not green: I don't think the failures are related to the changes in this pull-request though, and it would be great if you could confirm you see those errors in your private cibuild as well every now and then.
Moreover, as stated in a previous comment, the build takes quite a while to complete and I have to say it's very slow compared to your private infrastructure (i.e. it takes more than 30 minutes on Travis). I feel like caching dependencies could be a quick win (e.g. it should get us under 10 minutes) but that would require a custom caching strategy, 'cause Travis does not provide it for public Mac projects.
The two issues illustrated above are my biggest concerns before :shipit: and I'd love to have your feedback on how to proceed, especially because we may need to setup a custom storage service (such as Amazon S3) to upload/download cached dependencies.
I am looking forward to collaborating with you on this :raised_hands: :bow:

@as-cii what do you think about only running the tests on Linux, and just using the OSX infrastructure to check that we can build the app? That way, we could use caching for the build that we rely on the most: the one that runs the tests.

@maxbrunsfeld: I think we're not ready yet to use Linux as our main infrastructure for testing, as a bunch of package specs fail on Ubuntu (even on my local VM) and https://github.com/travis-ci/travis-ci/issues/3643 hasn't been "fixed" yet. The path to make everything bullet-proof on that platform is likely complex and could take a fair amount of time.
On the other hand we have a quite solid OS X environment where, even if they take ~30min., specs run smoothly (especially after we'll complete #6385).
So, here's my proposal :green_heart:

Ditch AppVeyor for the time being, as it's a lot slower than Travis and running specs on Windows seems to be even more cumbersome than on Linux;
Keep triggering private CI builds when GitHub employees push a commit;
Use always Travis CI (along with the private CI when needed)

Run a full script/cibuild on :apple: ;
Only test builds on :penguin: ;

This way we can provide a CI for our contributors already and check if it works fine for them. In the meantime we could optimize stuff to achieve a better speed (e.g. use a caching layer, use the sudo: false infrastructure, etc.).
What do you think? :thought_balloon:

So, here's my proposal :green_heart:

I agree on all fronts. This change already adds a ton of value as it is.

In the meantime we could optimize stuff to achieve a better speed (e.g. use a caching layer, use the sudo: false infrastructure, etc.

I would say we could leave it as is for a while. I'd be reluctant to add the complexity of a custom caching layer. And as far as I know sudo: false only works with Linux, because it opts-in to the docker infrastructure. I could be wrong on both these fronts though; let me know what ideas you have.
Other than that, :ship:.

As you can see our latest build has successfully run our script/cibuild :tada: :tada: :tada:
I agree with all the changes you proposed and I already applied them: please, have a last look so that we can :shipit:
@kevinsawicki @maxbrunsfeld: what do you think if we run a build on Janky just to make sure we didn't break anything there and that it is able to co-exist with Travis gracefully :rainbow:?
Thanks to all of your for your extensive review and for the great support :sparkles:

what do you think if we run a build on Janky just to make sure we didn't break anything there and that it is able to co-exist gracefully with Travis :rainbow:?

Let's just ship it :ship:
Thanks so much for setting this up :green_heart:

This is great. :balloon:

This is great.

Agreed! Awesome job as usual @as-cii. King amongst men! :bow:

A huge thanks goes to Travis CI for making Multi-OS possible: you rock! :metal: (/cc: @rkh)
@kevinsawicki @maxbrunsfeld: I have spotted a bunch of errors during some of our OS X builds on Travis: I suspect this could be due to running package and core specs in parallel. I plan to give some :heart: to spec-task.coffee: this will include some refactoring :art: and a speedup :zap: for our build times (more on that this weekend, hopefully).
Thanks everyone! :bow:

:sweat_smile: :metal:


webOpener.js:2  Refused to create a TrustedTypePolicy named<EMAIL_ADDRESS>because it violates the following Content Security Policy

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:   VS Code (web) within Azure Machine Learning Studio
OS Version:

Steps to Reproduce:

Open a notebook in Azure ML.
Click "Edit in VSCode (web)

I don't have access to the ML Workspace to disable extensions.
Trying to open any notebook with VSCode (web) from within Machine Learning Studio and I'm getting the following error (appears in Developer Tools).
webOpener.js:2  Refused to create a TrustedTypePolicy named<EMAIL_ADDRESS>because it violates the following Content Security Policy directive: "trusted-types amdLoader cellRendererEditorText defaultWorkerFactory diffEditorWidget diffEditorWidget2 diffReview domLineBreaksComputer dompurify editorGhostText editorViewLayer notebookRenderer stickyScrollViewLayer tokenizeToString".

Without more evidence, this sounds like an issue with azure ml. Please start by filing an issue against them. They can follow up with us if there's something wrong on the vscode side


Liveocean

redo of #154

👋 @rsignell-usgs thanks for re-opening this. Re: pre-commit, yes this is long-running issue being tracked in https://github.com/pangeo-forge/staged-recipes/pull/88, and which I plan to resolve soon. You are correct it doesn't affect this recipe. (@andersy005, I've had some recent ideas of how we'll handle this pre-commit issue, will follow up with you separately within the next few days.)
Re: running liveocean, copying a few points I noted https://github.com/pangeo-forge/staged-recipes/pull/154#issuecomment-1233099517 here (didn't realize that PR was closed when I commented there 🤦 ):

... IIUC, this depends on https://github.com/pangeo-forge/pangeo-forge-recipes/pull/399, which has not been released yet. So a couple last blockers (all on my side) before we can run this here:

Release pangeo-forge-recipes. This is easy, can happen anytime.
Our current @pangeo-forge-bot backend is difficult to update with new pangeo-forge-recipes releases. I'm pushing to deploy a new version which will be easier to update this week.
Once the new backend is deployed, I'll need to update https://github.com/pangeo-data/pangeo-docker-images/tree/master/forge to get the latest pangeo-forge-recipes there.

Getting close here!

Okay @cisaacstern , thanks for the update!   🤞

Removing the blocked:recipes-release tag, because necessary changes were just released in https://github.com/pangeo-forge/pangeo-forge-recipes/releases/tag/0.9.1. Two of the three issues listed above as blockers here are now complete:

[x] Release pangeo-forge-recipes. This is easy, can happen anytime.
[x] Our current @pangeo-forge-bot backend is difficult to update with new pangeo-forge-recipes releases. I'm pushing to deploy a new version which will be easier to update this week.
[ ] Once the new backend is deployed, I'll need to update https://github.com/pangeo-data/pangeo-docker-images/tree/master/forge to get the latest pangeo-forge-recipes there.

@cisaacstern , any updates here?

Charles is currently on parental leave. 👶  In the meantime, maybe @andersy005 might be able to help move this forward?

Charles is currently on parental leave. 👶 In the meantime, maybe @andersy005 might be able to help move this forward?

i'm happy to look into this sometime this afternoon...

/run liveocean

@rsignell-usgs, something

tada The test run of liveocean at 1e8a4db succeeded!
import xarray as xr

store = "https://ncsa.osn.xsede.org/Pangeo/pangeo-forge/test/pangeo-forge/staged-recipes/recipe-run-1279/liveocean.zarr"
ds = xr.open_dataset(store, engine='zarr', chunks={})
ds

@rsignell-usgs, something seems to have gone wrong because the written store appears to be empty. i don't know why :(
....
File ~/mambaforge/envs/playground/lib/python3.10/site-packages/xarray/backends/zarr.py:401, in ZarrStore.open_group(cls, store, mode, synchronizer, group, consolidated, consolidate_on_close, chunk_store, storage_options, append_dim, write_region, safe_chunks, stacklevel)
    385     except KeyError:
    386         warnings.warn(
    387             "Failed to open Zarr store with consolidated metadata, "
    388             "falling back to try reading non-consolidated metadata. "
   (...)
    399             stacklevel=stacklevel,
    400         )
--> 401         zarr_group = zarr.open_group(store, **open_kwargs)
    402 elif consolidated:
    403     # TODO: an option to pass the metadata_key keyword
    404     zarr_group = zarr.open_consolidated(store, **open_kwargs)

File ~/mambaforge/envs/playground/lib/python3.10/site-packages/zarr/hierarchy.py:1347, in open_group(store, mode, cache_attrs, synchronizer, path, chunk_store, storage_options, zarr_version)
   1345         if contains_array(store, path=path):
   1346             raise ContainsArrayError(path)
-> 1347         raise GroupNotFoundError(path)
   1349 elif mode == 'w':
   1350     init_group(store, overwrite=True, path=path, chunk_store=chunk_store)

GroupNotFoundError: group not found at path ''

@andersy005 is there anything for me to do at this point, or just hang tight on my end?

oh, I see.  The recipe is working correctly.    It's just the code snipped that isn't working.
Full reproducible notebook: https://nbviewer.org/gist/09661e86832a34421c4fe03c72c0554d

So this should be merged, right?

@cisaacstern

Apologies for the delay, @rsignell-usgs! Thanks for the nudge. Yes, if test run passed then we can merge, which I'll do now.


How to install from source instead of NuGet

Hello community, I hope your week is going well. I have an inquiry and I was hoping to pick someone's brain.

If I was to add functionality to UdpSocketClient abstraction portable interface and class  and to the platform specific implementations would I need to repackage it in NuGet format?

Thank you kindly,

Hi @doubledunk
For testing/development purposes, it's easiest to reference the appropriate .dlls directly.
For example -

you clone sockets-for-pcl
you make some changes to IUdpSocketClient then implement the changes in Sockets.Implementation.Net and Sockets.Implementation.WinRT, you compile and everything is :ok:
you want to play with these changes so you create new project of Windows Desktop and iOS and UWP (or whatever), and a PCL that they all reference
In each project you reference Sockets.Plugin.Abstractions plus the correct dll for that platform:

for the PCL -> Sockets.Plugin\bin\Debug\..
for Windows -> Sockets.Plugin.WindowsDesktop\bin\Debug\..
for iOS -> Sockets.Plugin.iOSUnified\bin\Debug\..
for UWP -> Sockets.Plugin.WindowsStore\bin\Debug\..

Then you can write the code in your PCL and the platform projects will use their correct .dll. This is effectively what happens automatically for you when you install the nuget package. Hope that helps! :star2:


fuschia: add IP_TOS and IP_RECVTOS APIs

Needed to enable fuschia support on https://github.com/rust-lang/socket2/pull/224
See the fuschia header for reference

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Amanieu (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors r+

:pushpin: Commit 9458a0ef20c377d6c91acf36f79adf63d580cb1b has been approved by Amanieu

:hourglass: Testing commit 9458a0ef20c377d6c91acf36f79adf63d580cb1b with merge 5d2c3a43961f4e7b5f07d56f8fdf7793b60fcb6e...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 5d2c3a43961f4e7b5f07d56f8fdf7793b60fcb6e to master...


Publisher sample doesn't exit, why?

Run the publisher example. Messages are published, the publisher terminates, but the program doesn't exit.

cd samples/snippets/
mvn compile exec:java -Dexec.mainClass=pubsublite.PublisherExample

I tried setting -Dexec.cleanupDaemonThreads to False and True but neither seemed to help.

This is fixed in the most recent build- executors needed to be marked as daemon threads.


How much GPU memory is required at least?

Thank you for your excellent work.
Does anyone know how much GPU memory is required at least?
My Nvidia RTX  8GB，can't work......CUDA out of memory............sad

my GMEM is 6G, can run SadTalker, but out of memory here..........sad

12G can run well, by the way, RAM as important as GPU.

OK，GOT IT ,THKS AGAIN


log shows no error and web portal not working

I have same thing working on my local machine but when i uploaded the same on server no error i found on server and also nothing is working
server details...

What is this IP and port for? Is it supposed to be Traccar web interface? SSH access? Or something else?

this is remote desktop details to check why applicaiton is not working...

Looks like it's working. Can you provide more details on what is the issue.


Release Candidate Comments (Mentorship)

This issue was created to collect comments about the upcoming metrics release.
This thread is for comments about Mentorship
GitHub location: https://github.com/chaoss/wg-diversity-inclusion/blob/master/focus-areas/leadership/mentorship.md
See all release candidates of metrics are at:
https://chaoss.community/metrics-202001/

Do not italics the References


Add brukf2205's file

As a reminder, you have: created a branch, created a file and made a commit, and opened a pull request

_posts/0000-01-02-br_posts/0000-01-02-brukf2205.mdukf2205.md


bot chat connection status will not be updated if network disconnect,  it seems subscribe event not trigger, any ideas?

We are trying to add an UI interaction to indicate health status of directlineline connection. It seems DL does not provide a disconnected status for subscribing.  Is there any event that would fire when DL connection become disconnected?
  this.connectionStatusSubscription = this.botConnection.connectionStatus$.subscribe(
      connectionStatus => {
        var status = '';
        switch (connectionStatus) {
          case ConnectionStatus.Uninitialized:
            status = ChatConnectionStatus.Uninitialized.value;
            break;
          case ConnectionStatus.Connecting:
            status = ChatConnectionStatus.Connecting.value;
            break;
          case ConnectionStatus.Online:
            status = ChatConnectionStatus.Online.value;
            break;
          case ConnectionStatus.ExpiredToken:
            status = ChatConnectionStatus.ExpiredToken.value;
            break;
          case ConnectionStatus.FailedToConnect:
            status = ChatConnectionStatus.FailedToConnect.value;
            break;
          case ConnectionStatus.Ended:
            status = ChatConnectionStatus.Ended.value;
            break;
          default:
            status = ChatConnectionStatus.Unexpected.value;
            break;
        }
        // Dispatch to change directline indicator status shown.
      }
    );

Loading up for discussion/prioritization in an upcoming release


refactor: mark ownership functions as external

closed as we want to keep it more generic with public so far + to be discussed in the future.


Support hours in relative time range selection

Codecov Report

Merging #4950 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4950   +/-   ##
=======================================
  Coverage   77.07%   77.07%
=======================================
  Files          44       44
  Lines        8558     8558
=======================================
  Hits         6596     6596
  Misses       1962     1962

Continue to review full report at Codecov.

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


Update README.md

Line 40: correct spelling of Build (was Buid)
Summary: Please include a summary of the change
corrected spelling of "Build" in README.md
Description
corrected spelling of "Build" in README.md
Fixes #issue_no
None
Type of change
Spelling
Checklist:

[x ] I have made corresponding changes to the documentation

Thank you very much for your correction. It is very helpful to me because I'm a not native English speaker.


error when changing saved event from all day event to duration event

Describe the bug
Error in callback for watcher "date": "TypeError: Cannot read property 'date' of null"
To Reproduce
Steps to reproduce the behavior:

enter an all day event
Click on the event to edit it
Uncheck all day event checkbox and select event start date and time
See error in console

Desktop (please complete the following information):

OS: [windows]
Browser [chrome]

By adding 00:00 to the string in the input it doesn't throw the error when clicking on the icon to open datepicker, so to rectify the issue, I would say that string needs to be formatted to include hours and minutes

Thanks for the information. This is caused by a bug in the QScroller app extension, of which I am currently working on to convert to the component ui/app-ext combo provided by the ui kit. Once that is released and QCalendar demo updated, it should resolve itself.
I'll keep this issue open until then.

Ok thanks, great work on the extensions, they are fantastic
Is it a quick fix for you?, if not, any estimated timeframe

No. I have a lot of work to do for QScroller (needs conversion to the new UI kit). In the meantime, you can use QDateTimePicker by @TobyMosque

As for time frame, probably early next week

@lombo75 Sorry, I am still working on QScroller. I was in Emergency twice and had an MRI to deal with. Sciatica nerve pain, possible collapse disk in my back. The punishment for being a programmer for over 30 years hunched in a chair at a desk. :(

No worries, Jeff, I have the same issues with my back, and same amount of years programming, plus chuck in some very bad wrists, take your time, I am not in a hurry for the fix atm

I fixed the QScroller integration yesterday. But, have not looked into date/times when changing it from duration to all-day

I have had to make an additional fix in QScroller. This will be fixed in the demo in the next release. Very soon.

Closing, but let me know if there are any other issues.


Threads add to story linking is not working anymore after patching

After patched the instagram, the Threads's add to story and feed is not working anymore.

where do I find that?

No worries I got you.

It is in Threads app, this is when you click on the share button on on thread post

I found the deep linking not working also. Previously you can open instagram app directly from link. Now it direct me to web browser instead. I think the patch messed up the deep linking.

It is in Threads app, this is when you click on the share button on on thread post

so basically I found a solution for this, you have to patch it with LSPatch as a local "like instagram but don't apply any module on it"

I found the deep linking not working also. Previously you can open instagram app directly from link. Now it direct me to web browser instead. I think the patch messed up the deep linking.

please make sure to enable those:

Okay, I have try to remove the module in LSPatch and enable all the supported web address, but the only this address "www.instagram.com" cannot be enable, it disable after I enable it.

I found that, in unmodified apk, these option is enabled by default and cannot be toggle

Okay, I have try to remove the module in LSPatch and enable all the supported web address, but the only this address "www.instagram.com" cannot be enable, it disable after I enable it.

I see, it's strange tbh.
I will try somethings out.

did the threads app work?

did the threads app work?

No either

did the threads app work?

No either

it did work on my end, have you patched it with local mode?

yes it is in local mode. And I even uninstall and patch it in local mode and did not embed module

Does your web address "www.instagram.com" still enabled after navigate away and come back?

yes it is in local mode. And I even uninstall and patch it in local mode and did not embed module

strange that it does work on my end.
I will check on it once I get back home.

I am back.
so for the first issue, you have to make sure that you have did these steps:

install threads from google play store
go to LSPatch and add new patch
select patch mode as Local
start patch and uninstal and install the patched threads

I tried it and it works.
now for the second issue, as I can see when I tried to share a link from instagram it would be using "instagram.com" and not "www.instagram.com" in which not enabling it won't harm.
please try those, have a nice day.

wow I just tried, it work already. Thank you so much for your help
On Sat, Oct 28, 2023, 10:39 PM ReSo7200 @.***> wrote:

I am back.
so for the first issue, you have to make sure that you have did these
steps:

install threads from google play store
go to LSPatch and add new patch
select patch mode as Local
start patch and uninstal and install the patched threads

I tried it and it works.
now for the second issue, as I can see when I tried to share a link from
instagram it would be using "instagram.com" and not "www.instagram.com"
in which not enabling it won't harm.
please try those, have a nice day.
—
Reply to this email directly, view it on GitHub
https://github.com/xHookman/IGexperiments/issues/26#issuecomment-1783832973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUQDALIA66AQNIM6GPGEMDYBUKJPAVCNFSM6AAAAAA6T5ZRECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTHAZTEOJXGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

ok thanks for confirming!


Add NumPy style Docstrings to SimulAI packages

Add NumPy style Docstrings to SimulAI packages
Tasks

Review the current documentation for the Optimization package, Regression package, Regression.pytorch sub-package, Residuals package, Sampling package, Control utilities package, and ROM package in the SimulAI package.
Write clear, concise, and comprehensive docstrings for all functions, classes, and methods in the packages using the NumPy style of documentation.
Ensure that the docstrings provide enough information for users to understand how to use the package, what the function or class does and what inputs and outputs are
Add examples in the docstrings to make it easier for users to understand how to use the package
Test the packages after adding the docstrings to ensure that they are complete and accurate
Add docstrings to simulai/modules
Ensure that the docstrings are consistent in style and format throughout the package
Make all the packages easily accessible to users by providing links to the packages in the main documentation of SimulAI.

#60
@snitramodranoel  You can assign me for these tasks in this issuse.

📌 TODO
Controls

[ ] ROM Package
[ ] Utilities Package

Optimization Package

[ ] Write docstrings for all functions and classes
[ ] Add examples in the docstrings
[ ] Test the package to ensure that it is working correctly
[ ] Update the main documentation to include a link to the Optimization package
[ ] Review the package for any improvements that can be made

Regression Package

[ ] Write docstrings for all functions and classes
[ ] Add examples in the docstrings
[ ] Test the package to ensure that it is working correctly
[ ] Update the main documentation to include a link to the Optimization package
[ ] Review the package for any improvements that can be made

Regression.pytorch  Sub-Package

[ ] Write docstrings for all functions and classes
[ ] Add examples in the docstrings
[ ] Test the package to ensure that it is working correctly
[ ] Update the main documentation to include a link to the Optimization package
[ ] Review the package for any improvements that can be made

Residuals Package

[ ] Write docstrings for all functions and classes
[ ] Add examples in the docstrings
[ ] Test the package to ensure that it is working correctly
[ ] Update the main documentation to include a link to the Optimization package
[ ] Review the package for any improvements that can be made

Sampling Package

[ ] Write docstrings for all functions and classes
[ ] Add examples in the docstrings
[ ] Test the package to ensure that it is working correctly
[ ] Update the main documentation to include a link to the Optimization package
[ ] Review the package for any improvements that can be made

simulai/modules

[ ] Write docstrings for all functions and classes
[ ] Add examples in the docstrings
[ ] Test the package to ensure that it is working correctly
[ ] Update the main documentation to include a link to the Optimization package
[ ] Review the package for any improvements that can be made

I agree Numpy-style is a better choice for docstrings.

I'm considering to use pyment for automatically converting the docstrings from reST to numpydoc. Here is a patch file showing the modification made by pyment in the module simulai/rom/_rom.py.  What do you think ?
_rom.py.txt

Another example. Using the command line:
 pyment -w -p False simulai/regression/_elm.py -o numpydoc

It produces the output I sent as attachment. It is possible to pass the entire directory simulai as input and convert it in a single time.
_elm.py.txt

It can cover the reST->numpydoc conversion and we can focus on filling the missing docstrings.

We need to find a way to fix the copy tag warnings generated by Sphinx in our codebase.
For example, we get a warning like this.
/Users/koc/simulai/simulai/io.py:docstring of simulai.io.ScalerReshaper.prepare_input_data:4: WARNING: source/_modules/simulai.io:parameters: copy tag

We are looking for a solution to fix these errors and get the docstrings to our desired format without copy tag errors etc. There are more than 100 warnings because of this.
While the pyment library is great at converting document sequences from reST to numpydoc format, it doesn't fix Sphinx-generated copy tag warnings.
for example:
Before using pyment:

After using pyment:

I am looking for a solution that would help me to completely get rid of these warnings and have clean docstrings in the desired format. As seen above, only the docstring style is changing. But what I'm looking for is to get rid of these warnings completely.

I tried the pyment library for the io.py module and it broke many document threads. (These docstrings were already in the style of numpy-docstring.) I'll edit the io.py module again later, and I suggest you don't use the pyment library. (I fixed many bugs....) @Joao-L-S-Almeida

With this commit reverted it to Version V0.99.13 io.py module.
https://github.com/IBM/simulai/pull/74/commits/a2a06c38f3efd4263e9942b0f46aa3c768c04972


Finish FLV demuxer

Not sure what is missing at this point apart from: seeking and lots of minor details/features and cleanup at least. And https://github.com/sdroege/gst-plugin-rs/issues/15
Should be compared with the the C demuxer: https://cgit.freedesktop.org/gstreamer/gst-plugins-good/tree/gst/flv/gstflvdemux.c

This is now tracked in https://gitlab.freedesktop.org/gstreamer/gst-plugin-rs/issues/15


Proxy doesn't load TLS configuration files if they exist before proxy is started

Before and after #1119, the proxy doesn't load its TLS configuration, and so starts in a no-TLS configuration, when the configuration files already exist and are already valid. I have to touch one of the configuration files, which causes the fs_watch code to load the configuration.
/cc @hawkw

Ah, yeah, we should probably attempt to load the configuration files once before we start the watch, that should be fairly easy to fix. I'll see about adding a test for this as well.


Does medooze re-encode outgoing rtp stream internally when incoming stream attached?

As title, I wonder medooze re-encodes rtp stream or not.
If medooze re-encodes, How can I handle some options (e.g. keyframe interval, quantizer) for each tracks?
Best regards.

No, no transcoding is performed on server side.

Thanks for your replay :)
I see medooze does not transcode streams.
Without transcoding on server side, How does Refresher works?
We try to forward rtp tracks(video is h264 encoded, audio is opus encoded) to gstreamer.
Actually, we can receive rtp and paly it :)  However, sometimes video frame shows gray fogged screen..
We guess that not enough I-frame came frame medooze sfu server.

Refresher request periodically an Iframe to the origin via RTCP PLI/FIR, it is specially thought to be used with the recording as you will be likely would want to seek the file to a particular location.

Thanks!
I see how works the Refresher :)


Build out project registry/guides/integrating with the project registry page

This guide should walk through how to integrate with the project registery (generally) using Javascript. The audience for this page is someone building a front end to the registry.

Link to and summarize info on the Indexer page (getting data from the registry)
How to read data from the registry with examples in JS and Solidity (see the Tabs component in Nextra)

Let's merge #37 and #38 into this page as subsections
Create a Profile.pdf
Update a Profile.pdf

#37
This page should be a short guide to creating a new identity from the front end. It should walk through the function signature for createIdentity and explain each piece. It should include a snippet of sample code, in JavaScript, for how to create an identity

#38
This page should walk through how to update an identity from the front end. It will need to call out which updates will trigger a new anchor to be created. For each method to update an identity in the registry, it should walk through the signature, what each piece of data is or means, and then a snippet of JS showing how to interact with it

This page should be a lot like the Working with Pools page


server: not subscribe to topic with own service name

Signed-off-by: Vasiliy Tolstov<EMAIL_ADDRESS>

Subscribe only if if s.opts.Router != nil { so the proxy/network can still be a message exchange


added functions to manage bc online environment update windows

Added two scripts for managing bc online environment update windows.
Scripts:

Saas\Get-BcEnvironmentUpdateWindow.ps1: Function for getting Update Window on a Business Central online environment
Saas\Set-BcEnvironmentUpdateWindow.ps1: Function for setting Update Window on a Business Central online environment.

Hopefully, this time around, I didn't miss anything..

Normally you should add a few lines to releasenotes.txt as well.

PR looks good (haven't tested though) - please change from draft to ready for review when you are ready (and have resolved the conflict in releasenotes)

One thing I noticed - I had to copy "Create-SaasUrl" in "BcContainerHelper.psd1" to make the function get recognized. I didnt include this change in any commit, because the psd1's will be created automatically.
I believe the issue was a missing Export-ModuleMember in "SaaSHelperFunctions.ps1", which I have added.


Fix wordlist update ORANGE to yellow

Replace position word on position 2040.
'ORANGE' -->  'yellow'

Excellent catch in the code. This PR is not compatible with the new structure, but the error is definitely being corrected, thank you for catching this.


Add check for Whois lookup

Changes this pull request makes :
Added a check for simple whois lookup.
Also updated the requirements.txt file for new package i.e ipwhois
Checklist :

[ ] I have added the relevant documentation.
[x] My branch is up-to-date with the upstream master branch.
[x] I have fully tested the changes locally.

Development environment
OS: Manjaro
Python Version: 3.5

However the function simple may be, I guess it would be better to create a separate folder according to the current architecture and place it there.

@abhisharma404 I have made the requested changes

@mzfr Do update the README.md


Maven has SoLoader v0.5.1, But i can't find Git Tag v0.5.1

https://mvnrepository.com/artifact/com.facebook.soloader/soloader/0.5.1

My bad: https://github.com/facebook/SoLoader/releases/tag/v0.5.1

Thanks for your contribution


Fix support for mkdocs 1.1

MkDocs 1.1 dropped string_types
See https://github.com/timvink/mkdocs-git-revision-date-localized-plugin/issues/8

Thank you @timvink . I'm closing this PR because I already merged another PR which included this fix, and another one related to None in tags.

No problem. Thanks for the plugin !


add real sig for logic op // developing,not done.

What have you changed?
Please explain in detail what the changes are in this PR and why they are needed:

Summarize your change
How does this PR work? Include a brief introduction for any changed logic (optional)
Separately describe each logical change (optional)
Describe any limitations of the current code (optional)

Don't assume reviewers understand the original issue.
What is the type of the changes?
Pick one of the following and delete the others:

New feature (a change which adds functionality)
Improvement (a change which is an improvement to an existing feature)
Bugfix (a change which fixes an issue)
Engineering (engineering change which doesn't change any feature or fix any issue)
Misc (other changes)

How is the PR tested?
Please describe the tests that you ran to verify your changes. Have you added unit or integration tests, or run manual tests? What additional tests would give you greater confidence in this change?
Does this PR affect documentation (docs) or should it be mentioned in the release notes?

If there is a document change, please file a PR in (docs) and add the PR number here.
If this PR should be mentioned in the release note, please update the release notes.

Does this PR affect tidb-ansible?
If there is a configuration or metrics change, please file a PR in tidb-ansible, and add the PR number here.
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Any examples? (optional)

Hi, are there any reasons to implement logical op for the Real data type?

Hi, are there any reasons to implement logical op for the Real data type?

For select 0.1 and null. LogicalIntSig will translate real(0.1) to int(0),this will cause wrong result.
I will close this pr. Maybe there should be another better way to fix it.

@jingyugao Nice discovery. This is indeed a wrong result that we should not apply cast in this scenario. @xuhuaiyu Do you have suggestions?

@jingyugao Do you have any update？

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


/categories: "page" instead of "pages" when there's just one article tagged

Solved by https://github.com/StampyAI/stampy-ui/pull/834


[FEATURE] Barcodes Filter

Is your feature request related to a problem? Please describe.
No problem
Describe the solution you'd like
Similar to the already implemented sort feature, it would be great to add a filter, which would enable functionality such as only returning barcodes within a certain area (i.e. viewfinder).
It would be great to provide a base class (similar to BarcodeComparator.kt) which can provide the FrameMetadata, in order to enable more functionality.
Describe alternatives you've considered
This can be done manually within the implementation listener, but would be simpler if it was integrated into the library.
Additional context
None

In the android manifest the "uses-feature" forces the application that uses this library to use them.
An app could have the barcode scanning as optional feature, but by forcing these feature, the app cannot be installed because google play filters devices not matching.
A possible solution could be a change of:
<uses-feature android:name="android.hardware.camera" />
<uses-feature android:name="android.hardware.camera.autofocus" />
in:
<uses-feature android:name="android.hardware.camera" android:required="false"/>
<uses-feature android:name="android.hardware.camera.autofocus" android:required="false"/>

In the android manifest the "uses-feature" forces the application that uses this library to use them.
An app could have the barcode scanning as optional feature, but by forcing these feature, the app cannot be installed because google play filters devices not matching.
A possible solution could be a change of:
<uses-feature android:name="android.hardware.camera" />
<uses-feature android:name="android.hardware.camera.autofocus" />
in:
<uses-feature android:name="android.hardware.camera" android:required="false"/>
<uses-feature android:name="android.hardware.camera.autofocus" android:required="false"/>

I have raise this a new issue. Good spot. #2

This library is no longer maintained. Marking wontfix


add CD workflow for Massa-SC-toolkit and its dependencies

TODO:
for @massalabs/as, @massalabs/massa-as-sdk and @massalabs/massa-sc-toolkit

Setup projects CD
publish dev version on npm
remove imports from github  ( i.e https://gitpkg.now.sh/massalabs...)
write some internal doc to explain the new development workflow

We now have a CD workflow


Add a better error message when AWS creds resolver fails due to an invalid profile  Closes #1846

Integration test logs

Logs
N/A

Example query results

Results
> select * from aws_account

Error: connection config has an incorrect aws profile 'aws_nagrajaaa', update the configuration file (SQLSTATE HV000)

+-----------------+-----+-----------------+------------------+--------------------------+---------------------------------+-----------------------------------+--------------------------------+-------------------------------------+-------+------+-----------+--------+--->
| account_aliases | arn | organization_id | organization_arn | organization_feature_set | organization_master_account_arn | organization_master_account_email | organization_master_account_id | organization_available_policy_types | title | akas | partition | region | ac>
+-----------------+-----+-----------------+------------------+--------------------------+---------------------------------+-----------------------------------+--------------------------------+-------------------------------------+-------+------+-----------+--------+--->
+-----------------+-----+-----------------+------------------+--------------------------+---------------------------------+-----------------------------------+--------------------------------+-------------------------------------+-------+------+-----------+--------+--->

Verified that the changes also work for aggregator profiles -
 select * from aws_all.aws_account

Error: connection config has an invalid AWS profile 'default23', Please update the configuration file
	connection config has an invalid AWS profile 'testaab12', Please update the configuration file

@ParthaI :

Does this work if I pass a non-existent profile name in AWS_PROFILE env var?
Are we able to tell the user which connection is causing the issue?
What does invalid profile mean (per the error message)? Is it always if a non-existent profile name is given? Or could it be if a profile definition in the AWS credentials/config file has a missing or incorrect property, incorrect data, etc.?
We should remove the text Please update the configuration file. from the error message, it's unclear as to what update is required and in general we don't really use that in our error messages.
Is this the best place in the code flow to check?
Are the default config loading and credential retrieval function calls expensive?
When we check the results of _, err := cfg.Credentials.Retrieve(ctx), would that credentials retrieval be helpful for any other auth methods?

@cbruno10, Here are the few key points as per the above comments, please take a look, Thanks!
Q: Will this function work if I provide a non-existent profile name in the AWS_PROFILE environment variable?
A: No, it will not work if a non-existent profile name is provided in the AWS_PROFILE environment variable.
Q: Can we identify the specific connection that is causing the problem for the user?
A: Yes, we can append the connection name to the error message.
Q: What does "invalid profile" mean according to the error message? Is it only when a non-existent profile name is used? Or could it also refer to missing or incorrect properties, improper data, etc., within a profile definition in the AWS credentials/config file?
We should exclude the phrase "Please update the configuration file." from the error message. It's unclear what specific update is required, and this phrase isn't commonly used in our error messages.
A: "Invalid profile" refers specifically to a non-existent profile name being used. The code block cfg, err := config.LoadDefaultConfig(ctx, config.WithSharedConfigProfile(profile)) always generates an error when a non-existent profile name is provided. To catch this, we used _, err := cfg.Credentials.Retrieve(ctx).
Q: Is this the most appropriate point in the code to perform this check?
A: I believe it's the most suitable location to handle this check. Other authentication errors aren't detected by the cfg.Credentials.Retrieve() function.
Q: Do the calls to load default configuration and retrieve credentials impose a significant performance overhead?
A: No, these calls do not result in any additional costs.
Q: When we evaluate the results of _, err := cfg.Credentials.Retrieve(ctx), could this credentials retrieval be beneficial for other authentication methods?
A: The Retrieve() function provides a structure<EMAIL_ADDRESS>that includes Access Key, Secret key, Session Token, Source, CanExpire, and Expires. However, this information may not be useful for authentication methods such as AssumeRole Credentials (With MFA), AssumeRole Credentials (in ECS), AWS-Vault Credentials, and Credentials from an EC2 Instance Profile.


Request to add documentation for installing this plugin

I'm new to nvim, please help me configure this plugins, i'm also having an issue like the photo below, help meeee
I'm using nvim 0.10.0, ubuntu 22, ros humble, clangd

Hi,
There is not much configuration needed to get this plugin working. I would advise to use the lazy.nvim approach
{
	"ErickKramer/nvim-ros2",
	dependencies = {
		"nvim-lua/plenary.nvim",
		"nvim-telescope/telescope.nvim",
		"nvim-treesitter/nvim-treesitter",
	},
    opts = {
        -- Add any custom options here
			autocmds = true,
			telescope = true,
			treesitter = true,
    }
},

That's what I am using also in the neovim configuration targeted towards ROS 2 development https://github.com/ErickKramer/ros2-with-neovim/blob/0a0697ee8071beb956c8bff12faf51ff925252d3/.config/nvim/init.lua#L1267
Now, regarding your error, I am almost certain that the root cause is the missing compile_commands.json and/or using the wrong compiler while building your ROS package.
The very first compilation for a clean C++ package is somewhat cumbersome. But, you can do something like

Create a package using the ros2 pkg create --build-type ament_cmake <package_name>
Create some placeholder C++ and make sure you configure your CMakeLists.txt file

#include <chrono>
#include <functional>
#include <memory>
#include <string>

#include "rclcpp/rclcpp.hpp"
#include "std_msgs/msg/string.hpp"

using namespace std::chrono_literals;

/* This example creates a subclass of Node and uses std::bind() to register a
* member function as a callback from the timer. */

class MinimalPublisher : public rclcpp::Node
{
  public:
    MinimalPublisher()
    : Node("minimal_publisher"), count_(0)
    {
      publisher_ = this->create_publisher<std_msgs::msg::String>("topic", 10);
      timer_ = this->create_wall_timer(
      500ms, std::bind(&MinimalPublisher::timer_callback, this));
    }

  private:
    void timer_callback()
    {
      auto message = std_msgs::msg::String();
      message.data = "Hello, world! " + std::to_string(count_++);
      RCLCPP_INFO(this->get_logger(), "Publishing: '%s'", message.data.c_str());
      publisher_->publish(message);
    }
    rclcpp::TimerBase::SharedPtr timer_;
    rclcpp::Publisher<std_msgs::msg::String>::SharedPtr publisher_;
    size_t count_;
};

int main(int argc, char * argv[])
{
  rclcpp::init(argc, argv);
  rclcpp::spin(std::make_shared<MinimalPublisher>());
  rclcpp::shutdown();
  return 0;
}

find_package(rclcpp CONFIG REQUIRED)
add_executable(${PROJECT_NAME}_node src/<YOUR_FILE>.cpp)
install(
  TARGETS ${PROJECT_NAME}_node
  DESTINATION lib/${PROJECT_NAME}
)

Compile your workspace using the proper compiler and cmake flags
CC=clang CXX=clang++ colcon build --symlink-install --cmake-args -DCMAKE_EXPORT_COMPILE_COMMANDS=ON

Then, you should be able to get clang working normally.

Hopefully, this can help you to get your setup working

Thank you so much, you're the first most fast responded person on the issues that I've been published
Right now, I'm resolving it by adding env variable $CPATH, i'll give it a try with your solution


The full build log with the error is visible here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076927

Hi,
Sphinx 7.3 changed the output from "New in version..." to "Added to version...". I guess the test simply needs to be adapted.
Please see: https://github.com/sphinx-doc/sphinx/commit/db4939f00756d16e1ada3af22e183e4492836507
Kind Regards


Add Support for mySQL / mariaDB Database

Motivation
I wanted to use vercel to publish the app while still being able to keep the database stored on my server. However, since my host sadly doesn't support postgres, I decided to add mySQL support to spliit. As an added bonus, the app now runs a lot snappier! Somehow postgres database queries on my vercel-free-tier where unbearably slow (on average somewhere between 500 and 1000ms).
I can imagine that others would be interested in using mySQL, too. That's why I created this pull request.
Implementation
Since spliit is using prisma as ORM, it should be quite straightforward to apply the necessary changes.
My first idea was to add an environment variable to prisma/schema.prisma to configure the provider like this
datasource db {
  provider = env("PRISMA_PROVIDER")
  ...
}

However, this doesn't work (providers cannot be set via environment variables)!
Therefore I decided to generate prisma/schema.prisma from a template file prisma/schema.prisma.template with a script that is invoked with package.json's postinstall hook (scripts/generate-prisma-schema.sh). The provider to be used is determined from the database URL scheme provided in .env environment configuration. If the URL starts with postgresql://we are using postgres, if it starts with mysql://we are using mySQL, ...
Almost there ...
Migrations are platform specify, too. Therefore the migrations specified in prisma/migrations will fail for mySQL.
Therefore, I had to

move existing prisma/migrations to prisma/migrations_postgresql
add new migrations for mySQL in prisma/migrations_mysql
extend the script scripts/generate-prisma-schema.sh to symlink prisma/migrations to the correct migration folder

Drawbacks

needs post-install hook to work
migrations have to be specified for each database platform separately (maybe someone could point me to a more elegant solution)

Advantages

works for mySQL and mariaDB
easily extendable to other database platforms

Probably this is useful only to myself. If so please tell me and I will close this PR.

I think it is useful to give those who are self-hosting the choice of database engine.
As your two open PRs are quite big, it may be that @scastiel hasn't yet had time to look at them fully so keep it around for now and I'm sure you'll get some feedback.


Increase connection timeout via maven

I see that there is a Settings class with a connection timeout.
How can I change the default value by using my pom.xml?

Yes - see the dependency-check-maven configuration page and look for connectionTimeout.  This controls the connection timeout when downloading external resources over HTTP/S.

Thanks for pointing me there - i somehow missed that.


Research on Git VCS

Perform a research on Git VCS

Here are some references,
https://youtu.be/1ffBJ4sVUb4


Add ability to define stock on the fly

Sometimes you may need to use a specific sheet or roll size that is not in the Stocks library. Request to add an option to define a custom size for one-off use.

This sounds perfect for my work. Would there be anyway to report on or track it?

@p-storey What do you mean, exactly? My idea was to simply add some logic in the app to allow users to specify a stock from the library, or choose an option to create a one-time use stock. In that case, it would allow users to specify the height/width, or roll width.

Does this sound like what you're looking for? What do you mean report/track it? The stock info of course would be used in the project, so this would be output with the project report if one is used. If I'm missing something, let me know!

@tiliadavid on a weekly basis I have new sheet sizes, sometimes its material from a different supplier but more often its a sheet size ordered specifically to fit a job.
What you described sounds good and yes it might be useful to report or track it, just in case the stock needs adding properly into the database. Would it be straightforward to find it in the report if it was a new stock that had been added on the fly?

@p-storey @matthewkayy I've updated the branch to fully support adding custom sheets and rolls and giving the option to add them to the library. Let me know if you have a chance to test it out and if you have any feedback!
https://github.com/tilialabs/tilia-phoenix-connect/tree/AddCustomSheet


Issue with One Drive

Hi,
Thank you for this amazing app, it really helps to "clean up" things. However, I am constantly having the same issue. I don't know if I am doing something wrong or there is an issue.
I used the wrapper and I don't remember ever selecting to change the location of the default folders, however, after I run the script One Drive Backup feature no longer works properly.
Here is the script I used:
#region Privacy & Telemetry
DiagTrackService -Disable
DiagnosticDataLevel -Minimal
ErrorReporting -Disable
FeedbackFrequency -Never
ScheduledTasks -Disable
SigninInfo -Disable
LanguageListAccess -Disable
AdvertisingID -Disable
WindowsWelcomeExperience -Show
WindowsTips -Disable
SettingsSuggestedContent -Hide
AppsSilentInstalling -Disable
WhatsNewInWindows -Disable
TailoredExperiences -Disable
#endregion Privacy & Telemetry

#region UI & Personalization
ThisPC -Show
FileExtensions -Show
OpenFileExplorerTo -ThisPC
CortanaButton -Hide
FileTransferDialog -Detailed
FileExplorerRibbon -Expanded
RecycleBinDeleteConfirmation -Enable
3DObjects -Hide
PeopleTaskbar -Hide
WindowsInkWorkspace -Hide
MeetNow -Hide
NewsInterests -Disable
NewAppInstalledNotification -Hide
JPEGWallpapersQuality -Max
TaskManagerWindow -Expanded
RestartNotification -Show
ShortcutsSuffix -Disable
PrtScnSnippingTool -Enable
UnpinTaskbarShortcuts -Shortcuts Edge, Store, Mail
#endregion UI & Personalization

#region System
StorageSense -Enable
StorageSenseTempFiles -Enable
StorageSenseFrequency -Month
Hibernation -Disable
BSoDStopError -Enable
PowerPlan -High
LatestInstalled.NET -Enable
NetworkAdaptersSavePower -Disable
WinPrtScrFolder -Desktop
FoldersLaunchSeparateProcess -Enable
F1HelpPage -Disable
NumLock -Enable
Autoplay -Disable
ThumbnailCacheRemoval -Disable
SaveRestartableApps -Disable
#endregion System

#region Microsoft Defender & Security
NetworkProtection -Enable
PUAppsDetection -Enable
DefenderSandbox -Enable
WindowsSandbox -Enable
DismissMSAccount
#endregion Microsoft Defender & Security

I get the following error:

I always do this on clean installations and I have tried on same machines with and without running the script so there is something here.

Hm...

Just did a clean Win11 install and same happened.
First install:
Installed Win 11, made sure was fully up to date and nothing else. Opened OneDrive connected to Work account, backups worked.
Second install:
Installed Win 11, made all updates, ran the script. Logged into OneDrive and only folder documents was allowing me to back up saying the Desktop and Images was not allowed.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Dmitry Nefedov @.>
Sent: Wednesday, October 6, 2021 8:26:25 PM
To: farag2/Sophia-Script-for-Windows @.>
Cc: canyon1991 @.>; Author @.>
Subject: Re: [farag2/Sophia-Script-for-Windows] Issue with One Drive (#260)
I'll try with your preset tomorrow. Have never any issues neither for me (using a corporate OneDrive), nor for any others... That's scary me. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/farag2/Sophia-Script-for-Windows/issues/260#issuecomment-936962883, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANSSDRMC2JMERNSHK3LOWPLUFSPGDANCNFSM5FLC4GMA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Spent 2 hours.  There is no way to test whether OneDrive -Uninstall will be invoked due to session doesn't know it until it "meets" such string. PowerShell works string by string... So what do you think about such hack?
if ((Get-Content -Path $PSScriptRoot\Sophia.ps1 -Force | Select-String -SimpleMatch "OneDrive -Uninstall").Line.StartsWith("#"))
{
    $DesktopFolder = Get-ItemPropertyValue -Path "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" -Name Desktop
    New-ItemProperty -Path "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders" -Name "{B7BEDE81-DF94-4682-A7D8-57A52620B86F}" -Type ExpandString -Value $DesktopFolder -Force
}
else
{
    Write-Warning -Message  $Localization.OneDriveWarning
    Write-Error -Message $Localization.OneDriveWarning -ErrorAction SilentlyContinue
}

It will warn user in console and after the script will end running.

⏳


I think the image is wrongly label

Hi,
I was checking on branching topic. I think it is wrongly label. May cause confusion to others.
87ab2 should be the other way around.
it should be c2b9e
Love everyone who contribute to this work. Thanks everyone and may Allah reward you.

Huh, surprised this hasn't been fixed after so long, or that no one else caught it...
@peff this should be fixed. Interestingly enough, the .pdf (p88) does not have this problem even though the page does.

Hmm, this should have been fixed long ago by https://github.com/progit/progit2/issues/136. And as @jnavila re-imported the book images recently, I'd think we would be up to date. Weird...

Duplicate of #524, one of the two should get closed.

Since #472 is the original issue reporting this, I'll close this one in favour of #472.


[RPC] Fix listconsultations ""

This PR fixes the output of the rpc command listconsultations "" which was returning empty before but should return the full list of consultations.

A new build of 640dbb94382b53c21987a3fa2f36849fee844265 has completed succesfully!
Binaries available at https://build.nav.community/binaries/aguycalled-patch-6

Tested on Ubuntu 18.04


docs: add Debian & Ubuntu install example

What

Update README.MD to include an apt install cidr example.

Why

cidr is almost available on Debian, and is already available on Ubuntu Oracular.

References

Closes #88
https://launchpad.net/ubuntu/oracular/+source/cidr
https://tracker.debian.org/pkg/cidr

Thank you for your help @angelabad!


Add environment variables to workflow

__TEST__
__DEV__
__PROD__
__COVERAGE__

Also allow custom variables.

A little larger task than originally thought. Tests do not go through webpack and thus will not have the webpack DefinePlugin applying the values. This will probably break any tests for code which would uses these variables.

It appears to me that create-react-app gets around this by attaching environment variables to process.env which would be available to Jest when running unit test.


Update http4s-ember-server to 0.21.28

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s", artifactId = "http4s-ember-server" } ]

labels: library-update, semver-patch

Superseded by #48.


Numpy-fication vs. Sympy.ufuncify/autowrap

Starting from the excellent symbolic description of the Acoustic wave equation provided by @mloubout we now want to speed-up the basic python version of the equation. However, since we are performing a stencil computation the traditional Numpy-fication tricks of applying operations over arrays become very wasteful in terms of memory, because we effectively need to to replicate the matrix for each stencil point. This is illustrated in the bottom figure of this page.
Fortunately, the problem of applying complex Sympy expressions to numeric systems is known and documented here. In particular the ufuncify functionality, or the even lower level autowrap module that provide some control of the JIT process, should allow us to turn the expression stencil in the acoustic wave equation notebook into a compiled function that can be applied to the numpy arrays that represent our grid. This should speed up the notebook computation significantly and give us insights into the necessary steps to generate the core computation kernels, as well as a baseline performance target that opesci-fd will aim to beat.

@mloubout Please see PR #4 ,implemented using autowrap. A choice based on the simple fact that it seemed to be the easiest to implement of the available options. I'd like some feedback on whether the results are equivalent.


Huffman Coding

Python implementation of Huffman Coding using Greedy Approach.
Huffman Coding is a technique of compressing data to reduce its size without loss of data. It is generally useful to compress the data in which there are frequently occurring characters.
It follows a Greedy approach since it deals with generating minimum length prefix-free binary codes.
It uses variable-length encoding scheme for assigning binary codes to characters depending on how frequently they occur in the given text.
Priority Queue is used for building the Huffman tree such that the character that occurs most frequently is assigned the smallest code and the one that occurs least frequently gets the largest code.
It follows this procedure: -
Create a leaf node for each character and build a min heap using all the nodes (The frequency value is used to compare two nodes in min heap)
Repeat Steps 3 to 5 while heap has more than one node
Extract two nodes, say x and y, with minimum frequency from the heap
Create a new internal node z with x as its left child and y as its right child. Also frequency(z)= frequency(x)+frequency(y)
Add z to min heap
Last node in the heap is the root of Huffman tree

Python implementation of Huffman Coding using Greedy Approach

Hey @ASHMITA-DE, I am sorry but I am unable to find the reference. Please create an Issue first.
Also, I cannot see any file containing the codes for Huffman Coding using Greedy Approach.
For any queries/issues, feel free to reach out to us on our slack channel. Thankyou :)

Hey @ASHMITA-DE, I am sorry but I am unable to find the reference. Please create an Issue first.
Also, I cannot see any file containing the codes for Huffman Coding using Greedy Approach.
For any queries/issues, feel free to reach out to us on our slack channel. Thankyou :)

Done.

@geekquad , as per the new rules of Hacktoberfest 2020, could you please label this pull request as "hacktoberfest-accepted"? Thank you.


Entering images - caption saving

Image captions must be saved using "update" button, using only "save" button, it disappears
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

When I  '...'
Then I '....'
And I '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please identify where you experience this bug:
*** One of ***

Development (native|docker : shaw)
Sandbox - <UCD 2019-09-25 15:52:16 -0500>
Production
Browser [e.g. chrome, safari]

Thanks. In these kind of reports adding (annotated) screenshots will help us lock down what specifically is being referenced.  There is a lot that goes on in this task.

I think this one is duplicate: #1228


refactor: fix incorrect use of greater for index

The proper comparative for index is higher, not greater.
Closes #55

@rultor good to merge.

@rultor good to merge.

@rafamizes OK, I'll try to merge now. You can check the progress of the merge here

@rultor good to merge.

@rafamizes Done! FYI, the full log is here (took me 3min)

@rultor release, tag is 0.0.9.

@rultor release, tag is 0.0.9.

@rafamizes OK, I will release it now. Please check the progress here

@rultor release, tag is 0.0.9.

@rafamizes Done! FYI, the full log is here (took me 2min)

Merged and released by Rultor.

released by rultor.


Publish messages std_msgs/Float32 on topic "battery"

Publish a topic about Brick battery on ROS.

jabrena@roshost:~$ rostopic hz /battery
subscribed to [/battery]
average rate: 397.667
	min: 0.000s max: 0.013s std dev: 0.00196s window: 376
average rate: 403.519
	min: 0.000s max: 0.021s std dev: 0.00223s window: 786
average rate: 403.773
	min: 0.000s max: 0.026s std dev: 0.00229s window: 1191
average rate: 407.576
	min: 0.000s max: 0.026s std dev: 0.00225s window: 1608
average rate: 412.791
	min: 0.000s max: 0.079s std dev: 0.00315s window: 2026

jabrena@roshost:~$ rostopic echo /battery
data: 9.67784976959
---
data: 9.71329975128
---
data: 9.6423997879
---
data: 9.66012477875
---
data: 9.67784976959
---

Fixed


Update: README.md

Update: README.md

Codecov Report

Merging #91 (f0e7b1f) into main (75f8ef4) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #91   +/-   ##
=======================================
  Coverage   81.77%   81.77%
=======================================
  Files          17       17
  Lines         384      384
  Branches        3        3
=======================================
  Hits          314      314
  Misses         70       70


add Effect.scopedAsDisposable, for integrating Scope with the using keyword

maybe just Effect.disposable ?

Ah but it doesn't wait for cleanup to complete, it uses runFork so this won't work as it would leak resources

wondering if there is a way to let this "yield" from the dispose

wondering if there is a way to let this "yield" from the dispose

You can only have async finalizers if you use async / await unfortunately.