Failed git push: Permission denied

This could be a duplicate of #28, but since the symptoms were different, I thought I'd file it.
tl;dr: I can't push from an in-cluster Ubuntu pod to the builder. The git client gets a permissions error.
I'm running an Ubuntu pod inside of k8s, and connecting to builder from there. The full  record of my install is here: https://gist.github.com/technosophos/9d5ebda491141eaf3475
The relevant details, though, are this:
  root@ubuntu:/example-ruby-sinatra# git remote add deis ssh://git@<IP_ADDRESS>:2223/keener-hacienda.git

Following instructions, we should now be able to push:
root@ubuntu:/example-ruby-sinatra# git push deis master
The authenticity of host '[<IP_ADDRESS>]:2223 ([<IP_ADDRESS>]:2223)' can't be established.
ECDSA key fingerprint is SHA256:Vs7LSYv1qopIQeDdgMLOHt5GhbE8tFT73XtfSQxneLo.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[<IP_ADDRESS>]:2223' (ECDSA) to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Checking the logs:
⇒  k --namespace=deis logs deis-builder-1dtun
2015/12/14 19:52:05 Listening... on 3000
[debug] Name: HOST, Val: <IP_ADDRESS>
[debug] Name: DEIS_ETCD_1_SERVICE_HOST, Val: <IP_ADDRESS>
[debug] Name: DEIS_ETCD_1_SERVICE_PORT_CLIENT, Val: 4100
[debug] Name: ETCD_PATH, Val: /deis/builder
[debug] Name: ETCD_TTL, Val: 20
[debug] Name: ETCD, Val: <IP_ADDRESS>:4100
[info] Sleeping
[info] Woke up.
[info] Could not get SSH host key from etcd. Generating new ones.
[info] Parsed host key /etc/ssh/ssh_host_rsa_key.
[info] Parsed host key /etc/ssh/ssh_host_dsa_key.
[info] Parsed host key /etc/ssh/ssh_host_ecdsa_key.
[info] Building confd templates. This may take a moment.
[debug] Recoverable error: exit status 1
[debug] Output: "2015-12-14T19:52:29Z deis-builder-1dtun confd[21]: ERROR 100: Key not found (/deis/controller) [13]\n2015-12-14T19:52:29Z deis-builder-1dtun confd[21]: ERROR 100: Key not found (/deis/controller) [13]\n"
[info] Re-trying template build. (Elapsed time: 3)
[debug] Recoverable error: exit status 1
[debug] Output: "2015-12-14T19:52:32Z deis-builder-1dtun confd[26]: ERROR 100: Key not found (/deis/controller) [13]\n2015-12-14T19:52:32Z deis-builder-1dtun confd[26]: ERROR 100: Key not found (/deis/controller) [13]\n"
[info] Re-trying template build. (Elapsed time: 6)
[debug] Recoverable error: exit status 1
[debug] Output: "2015-12-14T19:52:35Z deis-builder-1dtun confd[31]: ERROR 100: Key not found (/deis/controller) [13]\n2015-12-14T19:52:35Z deis-builder-1dtun confd[31]: ERROR 100: Key not found (/deis/controller) [13]\n"
[info] Re-trying template build. (Elapsed time: 9)
[info] Templates generated for <IP_ADDRESS>:4100 on run 3
[info] Watching confd.
[debug] Name: EXTERNAL_PORT, Val: 2223
[info] Added hostkey.
[info] Added hostkey.
[info] Added hostkey.
[info] Builder is running.
[info] Listening on <IP_ADDRESS>:2223
[info] Accepting new connections.
[info] Checking closer.
[info] Checking closer.
[info] Accepted connection.
[error] Failed handshake: EOF (&{{0xc820170000}})

I can verify that I can now get to this step (which I think means the present issue is closed):
root@ubuntu:/example-ruby-sinatra# git push deis master
Counting objects: 119, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (62/62), done.
Writing objects: 100% (119/119), 25.58 KiB | 0 bytes/s, done.
Total 119 (delta 49), reused 119 (delta 49)
/home/git/builder: line 129: /bin/mc: No such file or directory
To ssh://git@<IP_ADDRESS>:2223/keener-hacienda.git
 * [new branch]      master -> master

@technosophos yes I believe that means this issue is closed. Going to close now but if this issue recurs after I fix #30, I'll reopen

I am running into this still.
I used a trick of attempting to ssh to the builder as user git with -vvv to see what's going wrong.
From outside the cluster (accessing via router):
[kent@mbp ~]$ ssh -i ~/.ssh/kent -vvv -p 2222<EMAIL_ADDRESS>Warning: Identity file /Users/kent/.ssh/kent not accessible: No such file or directory.
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/kent/.ssh/config
debug1: /Users/kent/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to deis.krancour.deis.ninja [<IP_ADDRESS>] port 2222.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/Users/kent/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /Users/kent/.ssh/id_rsa type 1
debug1: identity file /Users/kent/.ssh/id_rsa-cert type -1
debug1: identity file /Users/kent/.ssh/id_dsa type -1
debug1: identity file /Users/kent/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
ssh_exchange_identification: Connection closed by remote host

To rule out router problems, here's the same troubleshooting technique applied from within the cluster.  The IP you see is the builder's service IP:
ubuntu@ip-172-20-0-101:~$ ssh -vvv -i id_rsa -p 2222<EMAIL_ADDRESS>OpenSSH_6.7p1 Ubuntu-5ubuntu1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to <IP_ADDRESS> [<IP_ADDRESS>] port 2222.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file id_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Ubuntu-5ubuntu1
ssh_exchange_identification: read: Connection reset by peer

Note that I've tried all the obvious things.  I have looked at /home/git/.ssh/authorized_keys on the builder.  It looks good.  I have tried different keys.  I have verified the key I'm using works on v1.x clusters.

Did you do a deis keys:add? I forgot to do that yesterday when I first filed this bug, but by the time I remembered, @arschles had already fixed the existing auth error.

I must be misunderstanding what @krancour did... why use a key that does not exist?

@technosophos the key did exist.  The only thing unusual about what I did was that as a diagnostic procedure, I used ssh directly so I could get a trace that might indicate why the git push was failing.  That said, the traces do seem to be indicating that the key is bad or doesn't exist, however, the same key works just fine with 1.x clusters.

@krancour this is what I am not understanding:
[kent@mbp ~]$ ssh -i ~/.ssh/kent -vvv -p 2222<EMAIL_ADDRESS>Warning: Identity file /Users/kent/.ssh/kent not accessible: No such file or directory.
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/kent/.ssh/config

Ah... whoops... let me try that again.  There is a problem, but you're right... I botched that line, so the trace isn't useful.

Here we go:
[kent@mbp ~]$ ssh -i ~/.ssh/id_rsa -vvv -p 2222<EMAIL_ADDRESS>OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/kent/.ssh/config
debug1: /Users/kent/.ssh/config line 1: Applying options for *
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to deis.krancour.deis.ninja [<IP_ADDRESS>] port 2222.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/Users/kent/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /Users/kent/.ssh/id_rsa type 1
debug1: identity file /Users/kent/.ssh/id_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
ssh_exchange_identification: Connection closed by remote host

What's still weird to me is that you are getting a response from an OpenSSH server. What server is that? Builder does not run OpenSSH. It runs a custom SSH server that uses the Go library.

n/m... that's teh client output, isn't it

I couldn't reproduce this on my local k8s cluster. Below I've listed everything I did from start to finish.
1. Install Deis on the Cluster
helm up
helm fetch deis/deis
helm install deis

That resulted in the following services (kd is an alias for kubectl get --namespace=deis):
ENG000656:builder aaronschlesinger$ kd get svc
NAME                  CLUSTER_IP   EXTERNAL_IP   PORT(S)             SELECTOR                   AGE
deis-builder          <IP_ADDRESS>   <none>        2222/TCP            name=deis-builder          14s
deis-database         <IP_ADDRESS>    <none>        5432/TCP            name=deis-database         14s
deis-etcd-1           <IP_ADDRESS>   <none>        2380/TCP,4100/TCP   name=deis-etcd-1           14s
deis-etcd-discovery   <IP_ADDRESS>   <none>        2381/TCP            name=deis-etcd-discovery   14s
deis-minio            <IP_ADDRESS>    <none>        9000/TCP            app=deis-minio             14s
deis-registry         <IP_ADDRESS>   <none>        5000/TCP            name=deis-registry         14s
deis-workflow         <IP_ADDRESS>   <none>        80/TCP              name=deis-workflow         14s

Then, I waited until all relevant pods were up:
ENG000656:builder aaronschlesinger$ kd get pod
NAME                        READY     STATUS    RESTARTS   AGE
deis-builder-b2t2u          1/1       Running   1          3m
deis-database-vnku3         1/1       Running   0          3m
deis-etcd-1-gxt12           1/1       Running   1          3m
deis-etcd-1-o6uu3           1/1       Running   0          3m
deis-etcd-1-pg2rj           1/1       Running   0          3m
deis-etcd-discovery-cf7tz   1/1       Running   0          3m
deis-minio-lgski            1/1       Running   0          3m
deis-registry-gzxua         1/1       Running   0          3m
deis-router-s4cti           0/1       Pending   0          3m
deis-workflow-yh1xd         1/1       Running   0          3m

2. Set up the Account
Then, I logged into the minion (I'm running a cluster created by micro-kube) and set up an account:
core@micro-kube ~/example-go $ ./deis register <IP_ADDRESS>
username: arschles
password:
password (confirm):
email<EMAIL_ADDRESS>Registered arschles
Logged in as arschles

3. Generate and add Keys
Then, generated and added my keys to the agent and Deis:
core@micro-kube ~/example-go $ ssh-keygen -t rsa -b 4096 -C<EMAIL_ADDRESS>Generating public/private rsa key pair.
Enter file in which to save the key (/home/core/.ssh/id_rsa):
/home/core/.ssh/id_rsa already exists.
Overwrite (y/n)? y
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/core/.ssh/id_rsa.
Your public key has been saved in /home/core/.ssh/id_rsa.pub.
The key fingerprint is:
b1:1d:0f:70:57:de:64:93:ce:fb:84:2c:18:56:a4:f2<EMAIL_ADDRESS>The key's randomart image is:
+---[RSA 4096]----+
|        . ..o...+|
|         o o.. =.|
|        o +.  + .|
|         *o+   o |
|        S.Eo.. ..|
|          . . o..|
|             . ..|
|                .|
|                 |
+-----------------+
core@micro-kube ~/example-go $ eval $(ssh-agent) && ssh-add ~/.ssh/id_rsa
Agent pid 29720
Identity added: /home/core/.ssh/id_rsa (rsa w/o comment)
core@micro-kube ~/example-go $ ./deis keys:add ~/.ssh/id_rsa.pub
Uploading id_rsa.pub to deis... done

4. Create new Project
Then I created a new project:
core@micro-kube ~/example-go $ ./deis create --no-remote
Creating Application... done, created luxury-gemstone
remote available at ssh://git@<IP_ADDRESS>:2222/luxury-gemstone.git

5. Set up new git remote
Then, pointed my git remote at builder:
core@micro-kube ~/example-go $ git remote add deis ssh://git@<IP_ADDRESS>:2222/luxury-gemstone.git

6. Push to the deis remote
Then pushed:
core@micro-kube ~/example-go $ git push deis master
The authenticity of host '[<IP_ADDRESS>]:2222 ([<IP_ADDRESS>]:2222)' can't be established.
RSA key fingerprint is 85:94:7f:63:f6:53:0c:15:86:f3:50:1d:60:f0:32:27.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[<IP_ADDRESS>]:2222' (RSA) to the list of known hosts.
Counting objects: 165, done.
Compressing objects: 100% (151/151), done.
Writing objects: 100% (165/165), 3.02 MiB | 11.00 KiB/s, done.
Total 165 (delta 81), reused 0 (delta 0)
mc: Configuration written to [/var/minio-conf/config.json]. Please update your access credentials.
mc: Successfully created ‘/var/minio-conf/share’.
mc: Initialized share uploads ‘/var/minio-conf/share/uploads.json’ file.
mc: Initialized share downloads ‘/var/minio-conf/share/downloads.json’ file.
Added host ‘http://<IP_ADDRESS>:9000’ successfully.
Bucket created successfully ‘http://<IP_ADDRESS>:9000/git’.
‘luxury-gemstone.tar.gz’ -> ‘http://<IP_ADDRESS>:9000/git/home/luxury-gemstone:git-2783d643/tar’
Total: 2.97 MB, Transferred: 2.97 MB, Speed: 22.75 MB/s
stored tarfile in http://<IP_ADDRESS>:9000/git/home/luxury-gemstone:git-2783d643/tar
pod "deis-slugbuilder" created
no file
no file
no file

Unfortunately, the no file message continues, because builder starts up the deis-slugbuilder pod in the default namespace but the cluster is running in the deis namespace. I've created #39 to track that.

I built a new cluster and am now unable to repro this.

@krancour I'm not sure why you'd have to build a new cluster, so this still concerns me.
@technosophos @slack do you mind trying to repro this again?

Doing it now.

@arschles I think my cluster was in a bad state.  I told @technosophos earlier, but I was running on t1.micros and I know I was starting to have resource issues.  Many pods, including the builder started flapping.  I can't help but imagine that contributed.

@krancour ok, I think I'm just paranoid. Thanks for letting me know.

I was running into this as well and it was related to helmc generating a builder-key that began with a space, causing api access between builder and controller to fail, which is why destroying and rebuilding the cluster worked, if the affected people also regenerated their secrets.
I opened deis/charts#303 to track the issue.

The fix for me was to run "ssh-add" in the terminal ;)


Dev #611 - further amendments

Additional copy changes for start page
Screenshot

Thanks Cristina just one very small change - where it says
'There are 23 collections within NPD, for example the, termly school census', the second comma's in the wrong place.
Could you change to
'There are 23 collections within NPD, for example, the termly school census'.
No need to run past me again, just copy to staging after that. Thanks.

@dgamblin3008 fixed now, new screenshot:


Edits on several documentation pages.

Mostly on How-to-Setup.
Maybe think about renaming to "installation-instructions"?

Mostly on How-to-Setup.
Maybe think about renaming to "installation-instructions"?

I think that Setup and Install have the same meaning, but since Setup can contain Install.
I think that How2Setup is good for the title, and installation-instructions is good for Markdown Heading.

Mostly on How-to-Setup.
Maybe think about renaming to "installation-instructions"?

I consider that Setup and Install have the same meaning, but since Setup can contain Install.
so I think that How2Setup is good for the title, and installation-instructions is good for Markdown Heading.

I agree with this too.

Ok. I will update How-to-Setup.md to make sure the headers match and I'll move the reference to wsldl/main.c into the wsldl-pg/docs repository.


Fix incorrect documentation of AUTO_HOST_ENDPOINTS

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 1e87807f14b0f799360900236a2812e703aa9fc7
https://deploy-preview-3550--calico.netlify.app


Improve Scaling Jobs docs and jobs scaling logic

Current documentation about jobs scaling is incomplete and the jobs scaler does not behave as one would intuitively expect.
The algorithm for spawning of new jobs is not described in detail in the docs. I would expect that:

When a job pulls a new task from the queue, it should dequeue it from the queue on the start.
The value of metric exposed by scaler should be the length of the queue (number of tasks that have not been pulled by any job yet).
After each pollingInterval KEDA spawns new jobs and their number is equal to value of the metric (length of the queue) - number of jobs that don't have running or completed status.
At the same time the number of new jobs is capped by inequality number of new jobs to spawn + number of jobs without running or completed status <= maxReplicaCount.

The 3. point was proposed also in https://github.com/kedacore/keda/issues/525#issuecomment-583379349 to work like this but it still has not been resolved. If there are already jobs in pending status, KEDA does not take them into account and spawns all jobs in the queue again during next polling which can result in huge number of jobs if e.g. the pending jobs cannot be scheduled or are waiting for new nodes to be provisioned.
Further it is not clear, in the context of jobs scaling, what is the meaning of cooldownPeriod, minReplicaCount and threshold in Prometheus trigger (and similar parameters in other triggers).

We are working on setting better expectations around Jobs in v2.0 and think this is good input for our docs.
As far as I know this works how we are aiming for it, right @zroubalik?
@hmoravec Are you up for contributing improved docs on this front?


Replicate existing Salt website design + functionality in Next.js/Mosaic

Following discussion today...
Our long term architectural approach for the site will be Next.js based. We will migrate away from Docusaurus.
Prior to additional site work in terms of content pages, templates, we will replicate the existing Salt site in Next.js, and use that as the foundation for further iteration.
@james-nash @JoanaMMoreira @JohannaJoergensen @shey-v fyi
### Tasks
- [x] Check-in with Mark Tate to discuss Mosaic migration
- [x] Steve King to grant Jo access to repo
- [ ] #1121
- [ ] Determine the approach towards migration - i.e. one page or lump work
- [ ] Determine page layout and theming
- [ ] Migrating the content and styles
- [ ] Migrating docusaurus components (navbar, vertical navigation, TOC, hamburger menu, footer, etc.)
- [ ] Migrating custom made components (card, link, etc)
- [ ] Code and design reviews

[ ] Check-in with Mark Tate to discuss Mosaic migration
[ ] Steve King to grant Jo access to repo
[ ] Install next.js/mosaic
[ ] Determine the approach towards migration - i.e. one page or lump work
[ ] Determine page layout and theming
[ ] Migrating the content and styles
[ ] Migrating custom made/docusaurus components
[ ] Code and design reviews

8 Feb - Jo reached out to Mark - mtg to be scheduled

hi all, has this meeting been scheduled with Marc? @james-nash
Can we get some preliminary estimated delivery dates around the below tasks?

Determine the approach towards migration - i.e. one page or lump work
Determine page layout and theming
Migrating the content and styles
Migrating docusaurus components (navbar, vertical navigation, TOC, hamburger menu, footer, etc.)
Migrating custom made components (card, link, etc)
Code and design reviews

Thank you.

April 6 - migrating docs


Have the physics enforce the scroll position.

This contains the following:

A new ScrollPhysics class that prevents content size changes from causing the scroll position to go out of bounds.
A new mechanism in ScrollPosition to enable that new physics behavior.
A fix to SliverFixedExtentList, there was an off-by-one error that led to incorrect maxScrollExtents calculation when reaching the end of the list.
Some cleanup in the scroll activity file.

cc @gaaclarke @goderbauer

FIxes #55610.

Curious about opinions on whether the test changes here should be written up in a migration guide.

I went ahead and added the dragging test for you.  I think this is what you want for the ballistic test but it wasn't passing for me.  Looks like I wasn't able to drag beyond the extents:
  testWidgets('shrink listview while ballistic', (WidgetTester tester) async {
    // widget tests run at<EMAIL_ADDRESS>    await tester.pumpWidget(MaterialApp(
      home: ListView.builder(
        itemBuilder: (BuildContext context, int index) => index == 0
              ? const ExpandingBox(collapsedSize: 400, expandedsize: 1200)
              : Container(height: 300, color: Colors.red),
        itemCount: 2,
      ),
    ));

    final ScrollPosition position =
        tester.state<ScrollableState>(find.byType(Scrollable)).position;
    expect(position.activity.runtimeType, IdleScrollActivity);
    expect(position.minScrollExtent, 0.0);
    expect(position.maxScrollExtent, 100.0);
    expect(position.pixels, 0.0);
    await tester.tap(find.byType(FlatButton));
    await tester.pumpAndSettle();

    final TestGesture drag1 = await tester.startGesture(const Offset(10.0, 500.0));
    await tester.pumpAndSettle();
    await drag1.moveTo(const Offset(10.0, 0.0));
    await tester.pumpAndSettle();
    await drag1.up();
    await tester.pumpAndSettle();
    expect(position.pixels, closeTo(500.00, 0.01));
    expect(position.minScrollExtent, 0.0);
    expect(position.maxScrollExtent, 900.0);

    final TestGesture drag2 = await tester.startGesture(const Offset(10.0, 500.0));
    await tester.pumpAndSettle();
    await drag2.moveTo(const Offset(10.0, 0.0));
    await tester.pumpAndSettle();
    expect(position.maxScrollExtent, 900.0);
    expect(position.pixels, closeTo(1000.00, 0.01));
    expect(position.activity.runtimeType, DragScrollActivity);
    await drag2.up();
    await tester.pump();
    expect(position.activity.runtimeType, BallisticScrollActivity);

    final _ExpandingBoxState expandingBoxState =
        tester.state<_ExpandingBoxState>(find.byType(ExpandingBox));
    expandingBoxState.toggleSize();
    await tester.pumpAndSettle();
    expect(position.minScrollExtent, 0.0);
    expect(position.maxScrollExtent, 100.0);
    expect(position.pixels, 100.0);
  });

I think this will work with dragging since you aren't predicating on isScrolling?

Yup.

Can you add my test to assert the shrinking while dragging?

Yeah I meant to do that but forgot, realized that while lying in bed last night. :-) I've got it locally, will upload momentarily.

Also a test that shrinks the size while the ScrollView is ballistic would be nice.

I'll see what I can do. I'm not sure I really want to test that case since it's still not "right" in any sane sense (the new code doesn't kick in since velocity != 0). I've no idea what to really do in that case to make it work "right".

It's not apparent to me on reading through how this gets around:

Tests that jump out of bounds and rely on that with intialPosition

I didn't run into any of these. Maybe the code I have to handle the out of bounds scrolls (maintaining the delta to the edge rather than clamping in that case) is handling those?

Pull to refresh mechanisms in iOS

I didn't run into this either, but presumably that's handled by the out-of-bounds case too.

ScrollView who switch between a state of knowing and having infinite extents

I saw one test where that was happening, but it turns out the test was failing because of the off-by-one error mentioned in the PR, it had nothing to do with not knowing the extents per se.

I'll see what I can do. I'm not sure I really want to test that case since it's still not "right" in any sane sense (the new code doesn't kick in since velocity != 0). I've no idea what to really do in that case to make it work "right".

I added one that you just bumped with the force push.  The concern I had was the the offset of the correction would compound with the ballistic animation such that the after the animation you ended up not at the max extents but some arbitrary point further in depending on when the correction happened in the animation.  If the animations are working off deltas instead of absolute values that can happen.
I think we can disregard what it looks like, but it's obviously wrong if the end result isn't what I mentioned.

The ballistics and the corrections are all working in absolute values, that's why I avoid doing anything if the velocity is non-zero (don't want them fighting).
Sorry about blowing away your change, I didn't even know it was possible to add to other people's PRs. My workflow is just amend && push while iterating on fixes. :-)


Traffic steps cleanup

changes done here are contained by this PR: https://github.com/Cognifide/bobcat/pull/42/files#diff-48ce6fb73055a7ecc035c68e0e313d56


Translate Documentation for Integrations

Hi, everyone.
I found that all documentation about Integrations is not included in this repository (either official or unofficial), but they are included in astro's docs site.
Now, I would like to ask, what should I do if I want to submit translations for @astro/mdx?

Because some Integrations are quite important, such as @astrojs/mdx,@astrojs/tailwindcss, @astrojs/image, and so on.


Fix default values of multiple options with optional values

Fixes default values for multiple options with optional values. The sentinel object (click.core._flag_needs_value) is now properly replaced by the value of flag_value.

fixes #2001

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

Things get a bit weird with ParameterSource and multiple options: you might get some of the option values from defaults or the prompt, others specified explicitly on the command line.
Also, default values populated from flag_value have ParameterSource.COMMANDLINE rather than ParameterSource.DEFAULT, which doesn't seem right.

Things get a bit weird with ParameterSource and multiple options: you might get some of the option values from defaults or the prompt, others specified explicitly on the command line.

That needs to be addressed, the value may only come from one source.

Things get a bit weird with ParameterSource and multiple options: you might get some of the option values from defaults or the prompt, others specified explicitly on the command line.

That needs to be addressed, the value may only come from one source.

@davidism OK, I'll need some more input from you then, there are two potential cases that I'm seeing:
Without a prompt
@click.option('--foo', multiple=True, is_flag=False, flag_value='default')

So if you do ./script.py --foo --foo test you'd get ('default', 'test') as a value for foo option and the source is ParameterSource.COMMANDLINE, which is accurate for both items in the list because of how flag_value source is determined:
https://github.com/pallets/click/blob/ce152bd7215038f762ee918e6e181a5309ad57c9/src/click/core.py#L2867-L2869
So everything seems fine in this case as is, assuming that ParameterSource.COMMANDLINE is correct and shouldn't be ParameterSource.DEFAULT instead for one of the items.
With a prompt
@click.option('--foo', multiple=True, is_flag=False, flag_value='default', prompt="Foo")`

How do you even specify multiple values with a prompt? I'm getting an Error: Value must be an iterable. for whatever input I provide. Is prompting even supposed to work for options with multiple=True?

If I do ./script.py --foo --foo test, am I expected to provide values via the prompt for both of them, or just the first one that's missing a value?

Provided that it is possible to use prompts with multiple=True and specify just one of the values, if I do ./script.py --foo --foo test and specify one of the values after being prompted what's the ParameterSource then? One part of the value is coming from ParameterSource.PROMPT and the other one is coming from ParameterSource.COMMANDLINE.

Seeing how it doesn't seem possible to set an iterable value via the prompt, there's no problem with ParameterSource as is here either :sweat_smile:

@davidism OK, I've reverted the changes related to prompting, as it's not really related to the issue at hand. So things should be pretty straightforward now and source is set to ParameterSource.COMMANDLINE whenever option's default value is being used.


Upgrade git-commit-id-maven-plugin 8.0.0 -> 8.0.1

This PR contains the following updates:

Package
Type
Update
Change

git-commit-id-maven-plugin
build
patch
8.0.0 -> 8.0.1

Release Notes

git-commit-id/git-commit-id-maven-plugin (git-commit-id-maven-plugin)
v8.0.1: Version 8.0.1
Compare Source
Version 8.0.1 is finally there and includes various bug-fixes and improvements :-)
New Features / Bug-Fixes:
The main key-aspects that have been improved or being worked on are the following:

make use of git-commit-id-plugin-core:6.0.0-rc.8

downgrade jgit.version from <IP_ADDRESS>311291450-r to <IP_ADDRESS>309050840-r (https://github.com/git-commit-id/git-commit-id-maven-plugin/issues/712)

Getting the latest release
The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:
<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>8.0.1</version>
</dependency>

Getting the latest snapshot (build automatically)
If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:
<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.
Known Issues / Limitations:

This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022
Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/287 or https://github.com/git-commit-id/maven-git-commit-id-plugin/issues/413#issuecomment-487952607 for details and potential workarounds

Reporting Problems
If you find any problem with this plugin, feel free to report it here

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade git-commit-id-maven-plugin 8.0.0 -> 8.0.1

See:
- https://github.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v8.0.1
- https://github.com/git-commit-id/git-commit-id-maven-plugin/compare/v8.0.0...v8.0.1


Ignore pandas futurewarning in dissolve

Codecov Report
Base: 85.68% // Head: 85.58% // Decreases project coverage by -0.10% :warning:

Coverage data is based on head (d6e0a03) compared to base (c2f73b2).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #184      +/-   ##
==========================================
- Coverage   85.68%   85.58%   -0.11%
==========================================
  Files          18       18
  Lines        3263     3267       +4
==========================================
  Hits         2796     2796
- Misses        467      471       +4

Impacted Files
Coverage Δ

geofileops/util/_geoops_gpd.py
87.14% <100.00%> (-0.62%)
:arrow_down:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


fix(versions): update Activiti/activiti-cloud-full-chart-security versions into master

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.61

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.61


Remove June 2023 GDK Update 2 as part of migrating to unified GDK ID

Remove June 2023 GDK Update 2 as part of migrating to unified GDK ID per #186890
Microsoft Reviewers: Open in CodeFlow

@microsoft/xbox-developer-experience-toolbox for review


gdal : openexr is EOL. Use openexr_3 instead

Issue description
gdal is currently using openexr which uses version 2.5.10 and is no longer being updated
openexr_3 is the most up to date version and should, if possible, be used instead.

@Geospatial

@sjdwhiting , thanks for letting us know.


Remove dependency on OpenSSL

It is only used by the ws and websocket crates, and can be quite annoying especially on Windows.
Depends on https://github.com/libp2p/rust-libp2p/issues/849

Triage: libp2p no longer depends on OpenSSL, but jsonrpc does.

We're using rusttls almost everywhere now?

Closing as fixed.
I don't know what has fixed it, but we only depend on openssl-probe now.


Is the local broker abandoned?

as the title says...

its been over a year since the last update, so my guess is yes.

Hi!
The project is still maintained, but my time is really limited at the moment. I've just released a new version of the addon that should be compatible with the latest MerossIot library.


Fix/validation fail

Coverage decreased (-0.6%) to 71.038% when pulling bf31836a0a5c1136d584d42db58a54b376b158e3 on fix/validation_fail into b7bbb70b5f9f2738c93c0357d5ef0f7e378f3396 on develop.

Coverage decreased (-0.006%) to 71.585% when pulling 0440ecafb83708e38fb0f41ce5863b0503dfdc9f on fix/validation_fail into b7bbb70b5f9f2738c93c0357d5ef0f7e378f3396 on develop.


UI should not show Swarm sidebar when no agents on managers

Is your feature request related to a problem? Please describe.
We are experimenting with using Portainer's new agent service to have one Portainer instance manage multiple endpoints. Some of the endpoints that we're wanting to manage intentionally do not include any Swarm manager nodes. When accessing these endpoints, all UI elements that expect Swarm are still visible and enabled but display errors when selected.
Examples of the broken UI elements include the Swarm-specific sidebar items (Services, Stacks, Secrets, etc.), widgets on the Dashboard view, and oddly enough the Volumes view although that isn't Swarm specific.
Describe the solution you'd like
Ideally it would be great if these UI elements were hidden when the agents for that endpoint don't include a manager, and instead showed an interface similar to what you would see in a non-Swarm configuration.
Describe alternatives you've considered
A potential alternate solution would include a per-endpoint property to select the UI so that each endpoint could have a different UI when connected to.
Additional context
Your tool is awesome and the agents just make it better!

@taiidani at the moment the agent is purely design to be used with Swarm clusters only. It's not recommended to deploy it on standalone hosts.
We recommend you to connect Portainer to a standard TLS secured way when you want to manage a Standalone Docker environment.
Agent support for Standalone hosts will come later.


Set database connection for exists validation. Fix for #183

This pull request will fix issue #183.

@KasparRosin could this get merged by any change?


Update kodi-extra.sh

Updated to use the official Kodi repo. From my fork of this project

since its a inporvment to the one already in there. im going to ok it
i will change the one word


Add Config and Migration plus review changes

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
✔

Hi @vjik and @xepozz us requested except...

@xepozz Did not put "yiisoft/db-migration" to "suggested" section in composer.json as breaks build, please can we deal with this in another pull request.
@vjik not remove the empty di as this also cause problems (can not exactly remember what they were), please can we deal with this in another pull request.

just add commits one by one, do not care about the rest.

Yes. We take care about squashing commits when merging, but we need to see how it progressed while doing review. Also, force-pushing is quite confusing for GitHub UI.

just add commits one by one, do not care about the rest.

Yes. We take care about squashing commits when merging, but we need to see how it progressed while doing review. Also, force-pushing is quite confusing for GitHub UI.

Oh dear, please send me a link to the process I should following if I would like to ammend a pull request in github :-|

Hi @xepozz @samdark @vjik , hopefully we can merge with the following outstanding...

// TWK TODO timeout should not be hard coded
// TWK TODO what is useMaster in Yii3
@xepozz, have removed yiisoft/db-migration from composer.json, but yiisoft/mutex still in required section cause used in Adopter (see constructor)

Apologies in advance if I have done any squeezed and forced commits, still googling to see exactly what you mean by that...

@aphraoh latest commits are fine.

Sent from my iPhoneOn 3 Apr 2024, at 17:33, Alexander Makarov @.***> wrote:
Let's merge it and address comments separately. Good job, @aphraoh.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>


Navigation property [PropName] not found on Action call with Expand

Hi, I found a issue when i have 2 or more actions with the same name for different collections and i try to expand a navigation property. For example, i have have the following endpoints:
domain.com/odata/categories/sync
domain.com/odata/products/sync
On GetFunction method of Simple.OData.Client.V3.Adapter.Metadata class, it returns the first one ocurrence of action with name "sync", without take in consideration the collection name like "categories" or "products".

Thank you for the issue report. I received a similar bug report about V4 adapter. Looking into it.


Keeping currently selected option visible during dropdown?

Is there a way to not clear the value of .multiselect__input when multiselect is activated? I'd prefer to have the currently selected value stay showing instead of the the placeholder "Select option" (in the default case).

This already works as described if searchable is false. Otherwise we need that space for the search input. You can see the currently selected value highlighted in the dropdown.


Can you release a new version to rubygems

the version currently there is over 2 years old (0.1.1). The readme on github doesn't work with that version.

Hi @davich, sorry I hadn’t gotten to it before - I just pushed v0.2.0!


Forecast service not respecting dates and observables

The forecast service seems to ignore any observables and to/from date parameters, and return a fixed set of observable data over a fixed date range. The only parameters that seem to affect the results is the selection type (with lat/lon's) and the HRRRX flag.
For example, the following two URI's return the same data:

https://firemap.sdsc.edu:5443/forecast?hrrrx=true&selection=withinRadius&lat=33.100492&lon=-116.3013267&radius=2&observable=wind_speed&from=2016-10-24T07:20:14.369271-07:00&to=2016-10-25T10:20:14.369271-07:00
https://firemap.sdsc.edu:5443/forecast?hrrrx=true&selection=withinRadius&lat=33.100492&lon=-116.3013267&radius=2&observable=temperature

The issue that Pylaski silently ignores unexpected parameters when it should return an error. reqparse cannot do validation and is no longer supported, so need to find a replacement.


Add a hybrid connection object to an existing web app

Library name and version
Azure.ResourceManager.AppService v1.0.2
Query/Question
Hello,
I would like to ask if there is a possibility to add hybrid connection object created for an Azure Relay to existing Web App using Azure.ResourceManager.AppService package? I cannot find that functionality - am I missing something? Maybe I should use another package?
Thank you in advance for your answer!
Environment
No response

Hi @JagodaMika , Thank you for using Azure SDK for .NET.
For your question, after you create the site resource, you could create a HybridConnection under it.
Please refer to:
            var siteCollection = (await CreateResourceGroupAsync()).GetWebSites();
            var input = ResourceDataHelper.GetBasicSiteData(DefaultLocation);
            var siteResource = (await siteCollection.CreateOrUpdateAsync(WaitUntil.Completed, siteName, input)).Value;
            var connectionCollection = siteResource.GetWebSiteHybridConnections();
            var connectionData = new RelayServiceConnectionEntityData()
            {
                EntityName = entityName,
                EntityConnectionString = entityConnectionString,
                ResourceConnectionString = resourceConnectionString,
                Hostname = hostname,
                Port = port,
                BiztalkUri = biztalkUri,
                Kind = kind
            };
            var connectionResource = (await connectionCollection.CreateOrUpdateAsync(WaitUntil.Completed, entityName, connectionData)).value;

/unresolve
Hi! Thanks a lot for pointing the right place! But it looks like it doesn't work as expected. When I'm trying to use the code which you posted, everytime I receive an error:
{"Code":"BadRequest","Message":"Required parameter EntityName, EntityConnectionString, ResoureType, ResourceConnectionString, Hostname, or BiztalkUri is missing.","Target":null,"Details":[{"Message":"Required parameter EntityName, EntityConnectionString, ResoureType, ResourceConnectionString, Hostname, or BiztalkUri is missing."},{"Code":"BadRequest"},{"ErrorEntity":{"ExtendedCode":"01010","MessageTemplate":"Required parameter {0} is missing.","Parameters":["EntityName, EntityConnectionString, ResoureType, ResourceConnectionString, Hostname, or BiztalkUri"],"Code":"BadRequest","Message":"Required parameter EntityName, EntityConnectionString, ResoureType, ResourceConnectionString, Hostname, or BiztalkUri is missing."}}],"Innererror":null}
All properties which I can set are set - only ResourceType cannot be set, because it is readonly.
Also I tried to get existing hybrid connection from list of hybrid connections under web site:
var singleSite = await _azureResourceGroup.GetWebSiteAsync("webSiteName");
var siteHybridConnections = singleSite.Value.GetWebSiteHybridConnections();
var existingHybridConnection = await siteHybridConnections.GetAsync("entityName");

but it also doesn't work and returns an error:
Specified argument was out of the range of valid values. (Parameter 'resourceType')
Stacktrace:
at Azure.Core.ResourceType..ctor(String resourceType)
at Azure.ResourceManager.AppService.RelayServiceConnectionEntityData.DeserializeRelayServiceConnectionEntityData(JsonElement element)
at Azure.ResourceManager.AppService.WebAppsRestOperations.d__297.MoveNext()
at Azure.ResourceManager.AppService.WebSiteHybridConnectionCollection.d__7.MoveNext()
So I believe that both errors are caused by some bug related to 'ResourceType' property in RelayServiceConnectionEntityData class.

/unresolve

Yes, the responce value type mapping got some issue here.
Opened a issue for Hybrid Connection in AppService. #37585


Localize field names

Hi,
I'm trying to localize field names with Umbraco Dictionary Items, but I'm not able to do it. Is this possible?
Regards.

Hi @ragivi ,
You should be able to localize your field names by using the built-in localization in Form Editor.
Check these docs: https://github.com/kjac/FormEditor/blob/master/Docs/extend_field_simple.md#step-2-register-the-field
Basically you need to add your field name to the appropriate localization JS file under /App_Plugins/FormEditor/js/langs/, using composition.field.[field alias] as key. Check the list of Danish field name translations in the Danish localization file - e.g. https://github.com/kjac/FormEditor/blob/master/Source/Umbraco/Plugin/js/langs/da-dk.js#L4

Hi @kjac ,
These docs show the case when you want to localize field type names or other configurations, but I want that the labels of the fields were localized, sorry if I hadn't explained well.
For example: I have a form with a field of textbox type with a label "Name". Then, I want that in the public web, the label "Name" appears localized in English ("Name") and in Spanish ("Nombre").
Thanks!

Hey again, and sorry for the late reply.
I don't believe localization of field labels is a core feature. The officially recommended way of doing country specific sites in Umbraco is to have separate content trees, and thus you'd have separate forms (unless you're doing form reuse).
On top of that there's the matter of non-value fields (headings, text paragraphs etc). They don't have a field name that could be used for localization through the dictionary.
However you're in control of the rendering, and you can do pretty much what you want with it. For example, you could fetch the text box label (this line) from the dictionary with a fallback to the defined label by replacing @Model.Label with something like this:
@Umbraco.Coalesce(Umbraco.GetDictionaryValue("form." + Model.Name.ToLowerInvariant()), Model.Label).
Disclaimer... that code is written in free hand and not tested 😄

Hi kjac!
Your solution is great! The code works perfectly. I know that the officially recommended way is have two separate nodes, but in one site it was a requirement to have only one node (I solved it with Vorto package).
Thanks a lot.


Make the checkout directory configurable

This changes the plugin to use BUILDKITE_BUILD_CHECKOUT_PATH by
default with the ability to specify another path. When only one repo is
checked out, it is checked out directly at the checkout path, as in the
Buildkite default checkout behavior. When multiple repos are checked
out, they are each in their own subdirectory under
BUILDKITE_BUILD_CHECKOUT_PATH with names determined by their URL.
I made use of this in my own project with
https://github.com/google/iree/pull/8619
Fixes https://github.com/hasura/smooth-checkout-buildkite-plugin/issues/13
Fixes https://github.com/hasura/smooth-checkout-buildkite-plugin/issues/21
Fixes https://github.com/hasura/smooth-checkout-buildkite-plugin/issues/22
Fixes https://github.com/hasura/smooth-checkout-buildkite-plugin/issues/23

@scriptnull PTAL
@imperfect-fourth does this address your use case for #23 also?

the working directory for single repo checkout is different

Ah my bad, it seems the behaviour is same

I think that the first one can be avoided by keeping both the env vars for now and maybe marking WORKSPACE as deprecated. What do you think?

Sure, that makes sense to me

Sorry I was out on vacation for a while. I've updated to still set the WORKSPACE variable. Note that this still isn't backward compatible because it defaults to buildkite's default checkout path instead of the custom path that was hardcoded before. I don't see a clean way to preserve backward compatibility here.

Ping on this?

@GMNGeoffrey sorry for the delay. A new release have been made(v4.0.0) with your changes. Thank you for the contribution!


IC - 20200226

Describe the contribution
Fix #377, #408, #274, #509, and #315
Requirement and Documentation scrubs
#512, #513, #516, #518, #522, #525, and #506
Testing performed
Steps taken to test the contribution:
Current CI passes
Test 4 in Enhanced CI in https://github.com/nasa/cFS/pull/40

Expected behavior changes
PR #497, PR #510, PR #514 PR #515, PR #517 PR #521, PR #524, PR #526  - Requirement scrubs.
PR #507 - Updated API documentation
PR #477 - Removed references to device drivers in both code and documentation.
PR #461 - Fixes incorrect debug messages in fsw/cfe-core/src/es/cfe_es_perf.c
PR #485 - NumOfChildTasks will now be decremented when a child task is deleted.
System(s) tested on
CI: Ubuntu 18.04
Additional context
N/A
Third party code
N/A
Contributor Info - All information REQUIRED for consideration of pull request
Gerardo E. Cruz-Ortiz - NASA/GSFC

CCB 20200226 - Approved


Add params,responses for /search endpoints, placeholder Tags models

Needs to be rebased on top of master after #17 is merged to be valid spec (/search/collections needs to references Collections stuff)


[analyzer] doesn't show import for ../../models/bar.dart

Dart analyzer doesn't appear to be able to walk down to a parent directory and then into a child directory.
eg
lib/screens/foo/foo.dart
lib/models/bar.dart

if you try to import Bar() from inside foo.dart, the only option given by the analyzer (via VSCode auto complete) is to import the package
import 'package:myapp/models/bar.dart';
This import then gets mixed in with all the other package imports instead of being next to the other relative imports
Ideally it would be able to do the following
import '../../models/bar.dart'

This issue has already been resolved. Tested on latest stable. Are you still seeing this?


Trace/breakpoint trap hokus-cms_linux_amd64.deb 0.6.2 first run

calling hokus-cms
installed on Debian
also tried 0.6.1 (signed 0.6.0 in the .deb file)
same
what am I missing?

have you tried using the App.image version?

Run sudo sysctl kernel.unprivileged_userns_clone=1
See https://medium.com/@authmane512/solve-the-suid-sandbox-helper-binary-was-found-but-is-not-configured-correctly-3-solutions-4f1425a9a76c


sfdx force:project:create error, what is going wrong?

Summary
When I attempt to create a new Project in the CLI, using VisualStudio Code as my IDE, I get the following error message:
PS C:\Users\dthto\sfdxprojects\testProject> sfdx force:project:create --projectname testProject1
{ AssertionError [ERR_ASSERTION]: Trying to copy from a source that does not exist: C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\lib\templates\project\standard\ScratchDef.json
at EditionInterface.exports.copy (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\node_modules\mem-fs-editor\lib\actions\copy.js:49:3)
at EditionInterface.module.exports [as copyTpl] (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\node_modules\mem-fs-editor\lib\actions\copy-tpl.js:29:8)
at ProjectGenerator.writing (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\lib\generators\projectGenerator.js:53:17)
at Object. (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\node_modules\yeoman-generator\lib\index.js:395:23)
at C:\Program Files (x86)\Salesforce CLI\client\node_modules\run-async\index.js:25:25
at new Promise ()
at C:\Program Files (x86)\Salesforce CLI\client\node_modules\run-async\index.js:24:19
at self.env.runLoop.add.completed (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\node_modules\yeoman-generator\lib\index.js:396:9)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
generatedMessage: false,
name: 'AssertionError [ERR_ASSERTION]',
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '==' }
{ AssertionError [ERR_ASSERTION]: Trying to copy from a source that does not exist: C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\lib\templates\project\standard\ScratchDef.json
at EditionInterface.exports.copy (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\node_modules\mem-fs-editor\lib\actions\copy.js:49:3)
at EditionInterface.module.exports [as copyTpl] (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\node_modules\mem-fs-editor\lib\actions\copy-tpl.js:29:8)
at ProjectGenerator.writing (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\lib\generators\projectGenerator.js:53:17)
at Object. (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\node_modules\yeoman-generator\lib\index.js:395:23)
at C:\Program Files (x86)\Salesforce CLI\client\node_modules\run-async\index.js:25:25
at new Promise ()
at C:\Program Files (x86)\Salesforce CLI\client\node_modules\run-async\index.js:24:19
at self.env.runLoop.add.completed (C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\node_modules\yeoman-generator\lib\index.js:396:9)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
generatedMessage: false,
name: 'AssertionError [ERR_ASSERTION]',
code: 'ERR_ASSERTION',
actual: false,
expected: true,
operator: '==' }
Steps To Reproduce:

Type "sfdx force:project:create --projectname PROJECTNAME " and press enter

Expected result
A project skeleton structure and definition file will be created
Actual result
Error message as shown above
Additional information
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version): Current
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core) Current
OS and version: Windows 10 Pro version 10.0.18362 Build 18362

@ntotten would you take a look at this issue?

Hi @dannyodd thanks for opening this issue. The stack trace you've added indicates that a template file that the cli ships with and is used by the project:create command, is not available. I'm currently testing on a Windows machine with the same OS version you are on and can't replicate the issue on the latest version of the CLI (v7.33.2). Could you confirm you are in this version and still experiencing the issue ?
If you are still getting this issue in that version then could you go into your file system and verify that this file is not present( C:\Program Files (x86)\Salesforce CLI\client\node_modules\salesforcedx-templates\lib\templates\project\standard\ScratchDef.json ) ? If that's the case then something might've gone wrong during installation/update of your CLI.

sfdx update helped in my case
I have x86 version


account for characters before literal start pos for doclinks

I'm guessing this patch is correct, at least it seams to work.
For the first line of string literals, the starting character position for doclinks must take into account the starting character position of the string literal.
With 1.3.0, introducing a doclink errors on the 1st & 2nd lines of the string literal results in compile-js and compile-dart output:
./source/ceylon/buffer/ByteBuffer.ceylon:16: warning: declaration is missing: 'ByteBufferX'
    "Creates a [[ByteBufferX]] x [[ByteBufferX]]initally backed by the given [[initialArray]].
             ^
./source/ceylon/buffer/ByteBuffer.ceylon:16: warning: declaration is missing: 'ByteBufferX'
    "Creates a [[ByteBufferX]] x [[ByteBufferX]]initally backed by the given [[initialArray]].
                               ^
./source/ceylon/buffer/ByteBuffer.ceylon:17: warning: declaration is missing: 'ByteBufferX'
     The capacity [[ByteBufferX]] of the new buffer will be the size of the array. The returned
                    ^

with this patch:
./source/ceylon/buffer/ByteBuffer.ceylon:16: warning: declaration is missing: 'ByteBufferX'
    "Creates a [[ByteBufferX]] x [[ByteBufferX]]initally backed by the given [[initialArray]].
                 ^
./source/ceylon/buffer/ByteBuffer.ceylon:16: warning: declaration is missing: 'ByteBufferX'
    "Creates a [[ByteBufferX]] x [[ByteBufferX]]initally backed by the given [[initialArray]].
                                   ^
./source/ceylon/buffer/ByteBuffer.ceylon:17: warning: declaration is missing: 'ByteBufferX'
     The capacity [[ByteBufferX]] of the new buffer will be the size of the array. The returned
                    ^

Can one of the admins verify this patch? (see README)

OK, I trust you ;)

OK, I trust you ;)

It must have been the "it seams to work" with an "a" that inspired the confidence.


Make FASET form checkboxes less ugly

https://v4-alpha.getbootstrap.com/components/forms/#checkboxes

This was fixed in #38


Work on development containers, bringing back scanning functionality

Hello @politeauthority! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/pignus_api/collects/image_builds.py:

Line 59:80: E501 line too long (96 > 79 characters)

In the file src/pignus_client/__init__.py:

Line 77:80: E501 line too long (84 > 79 characters)
Line 82:80: E501 line too long (82 > 79 characters)

In the file src/pignus_client/models/base.py:

Line 67:80: E501 line too long (90 > 79 characters)
Line 86:32: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 98:80: E501 line too long (90 > 79 characters)
Line 117:80: E501 line too long (81 > 79 characters)

In the file src/pignus_sentry/pignus_sentry.py:

Line 2:80: E501 line too long (80 > 79 characters)
Line 19:80: E501 line too long (90 > 79 characters)
Line 30:80: E501 line too long (80 > 79 characters)

In the file src/pignus_shared/utils/misc.py:

Line 294:80: E501 line too long (88 > 79 characters)
Line 302:80: E501 line too long (90 > 79 characters)

In the file tests/unit/pignus_client/models/test_client_model_base.py:

Line 1:43: W291 trailing whitespace
Line 10:1: W191 indentation contains tabs
Line 11:1: W191 indentation contains tabs
Line 12:1: W191 indentation contains tabs
Line 13:1: W191 indentation contains tabs
Line 14:1: W191 indentation contains tabs
Line 15:1: W191 indentation contains tabs
Line 17:1: W191 indentation contains tabs
Line 18:1: W191 indentation contains tabs
Line 19:1: W191 indentation contains tabs
Line 20:1: W191 indentation contains tabs
Line 21:1: W191 indentation contains tabs
Line 22:1: W191 indentation contains tabs
Line 24:1: W191 indentation contains tabs
Line 25:1: W191 indentation contains tabs
Line 26:1: W191 indentation contains tabs
Line 27:1: W191 indentation contains tabs
Line 28:1: W191 indentation contains tabs
Line 29:1: W191 indentation contains tabs
Line 30:1: E101 indentation contains mixed spaces and tabs
Line 30:13: E122 continuation line missing indentation or outdented
Line 34:1: E101 indentation contains mixed spaces and tabs
Line 34:1: W191 indentation contains tabs
Line 35:1: W191 indentation contains tabs
Line 36:1: W191 indentation contains tabs


Update to rules_apple 3.5.1 minimum supported version

3.5.1 includes a fix we need to get in for codesigntool to work correctly. This increases min version of rules_apple to 3.5.1 for version 4.3.1 of rules_ios (to be released)

4.4.0 of rules_ios (to be released)

Why not a patch release?

4.4.0 of rules_ios (to be released)

Why not a patch release?

honestly not sure what would be more typical here, its not a bug fix in this repo but does increase the version. Thoughts @mattrobmattrob?

🤷 Patch is probably the correct version bump based on semver but I don't feel strongly.

Updated


Add patch versions of helm charts to release notes.

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
I previously grabbed the versions from the helm charts themselves which do not include the patch versions, this PR adds the patch versions of the helm charts in the latest release bundle.
What testing has been done?
Documentation change, no testing required.

@Christian-Nunnally Do you still want to submit this?


Only one client shown

openvpn status says 5 clients actually logged in but only one is shown in web interface.
OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jan  9 2019
Any idea?

What authentication do you use?

Client certificates

Hm. My setup uses the same method and works just fine. Can you provide the log of the application?


New message indicator disappears when hovered over and report action menu does not hide

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:

New line indicator is always displayed, even after hovering over
Report action menu should hide after hovering to another message

Actual Result:

New line indicator disappears when hovered over
Report action menu doesn't hide when hovering over another message and 2 menus can be seen

Action Performed:

Go to a chat with unread messages
Hover over the new message line indicator (expected result 1)
Hover over the Copy function in the report action menu
Slowly move the cursor to another message (expected result 2)

Workaround:
No need, visual issue.
Platform:
Where is this issue occurring?
Web ✔
iOS
Android
Desktop App ✔
Mobile Web
Version Number: 1.0.28-0
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/44479856/115787369-19e52d80-a390-11eb-9f05-71e857f33e09.mp4

Expensify/Expensify Issue URL:
View all open jobs on Upwork

From @roryabraham https://expensify.slack.com/archives/C01GTK53T8Q/p1619042344491700

ISSUE: When hovering a chat with the NEW chat indicator, the chat indicator disappears. Furthermore, the hover state of the report action is sometimes persisted when it should not be (note in the second screenshot that there are two hovered report actions. To reproduce the first part, hover over a new chat, and the new chat indicator will disappear. To reproduce the second part, slowly move the cursor from a new chat to the one above. Fiddle with it and it's pretty easy to reproduce the incorrect hover state.

Triggered auto assignment to @jboniface (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Triggered auto assignment to @ctkochan22 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Just to clarify on the expected result for (1), this is how it looks in Slack:

And I think we want the same ... the line should be visible but the ReportActionContextMenu that appears on hover should cover the NEW text.

Triggered auto assignment to @stephanieelliott (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Triggered auto assignment to @deetergp (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

This job has been posted to Upwork: https://www.upwork.com/jobs/~016c9e344435c0905d

Proposal

We will remove the hovered from the condition check here.
https://github.com/Expensify/Expensify.cash/blob/f213be0a1be5a04599d2f17d8848b0a7824eb8be/src/pages/home/report/ReportActionItem.js#L122-L123
Now we have to adjust the z-index for the context menu
https://github.com/Expensify/Expensify.cash/blob/f213be0a1be5a04599d2f17d8848b0a7824eb8be/src/styles/getReportActionItemStyles.js#L30-L36.
zIndex: 1 works well.

This fixes the above issue & after these changes context menu does not persist hovered state.

Okay, thanks @parasharrajat, feel free to submit a PR

@stephanieelliott Waiting for this job to be assigned to me. Lol fix is already merged.

Oop, gotcha @parasharrajat! Thanks, will flag this for payment after the 7 day hold period.


Use std::env::home_dir instead of std::env::var_os("HOME")

std::env::home_dir has a sensible fallback in case $HOME is not set.

USERPROFILE is Windows-only. What is the purpose of this change?

The fallback exists, it just isn't documented. See https://github.com/rust-lang/rust/pull/29690.

OK. But what is the value of the change? If HOME is not set, the environment is not even nearly XDG compliant, I believe...

The value is that the library doesn't panic in this case, making it more useful for programs trying to be robust.
I wanted to use this library to make cargo XDG-compliant, but they probably won't like it if it generated an error in more cases due to such a change.

Hm, it's true that something like cargo shouldn't really care if the environment is perfectly XDG compliant or not.

Thanks!


Spyder won't properly close on Mac OSX Darwin

Problem Description
Spyder won't properly close on Mac OSX Darwin.
I bought a new macbook pro, first time using OSX in a long time.  When I close out of spyder, the window closes, but spyder keeps running.  It still ties up the terminal that I launch it from and remains on the dock.
What steps will reproduce the problem?

Open spyder in a terminal.
Close spyder.

What is the expected output? What do you see instead?
Spyder should just open and then close.  Instead, it it remains on the dock and the process continues running.
Package Versions

Spyder: 3.2.7
Python: 3.6.3
Qt: 5.6.2
PyQt: 5.6
Operating System: OSX Darwin

Dependencies

IPython >=4.0    :  6.2.1 (OK)
cython >=0.21    :  None (NOK)
jedi >=0.9.0     :  0.11.1 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
numpy >=1.7      :  1.14.1 (OK)
pandas >=0.13.1  :  None (NOK)
psutil >=0.3     :  5.4.3 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pyflakes >=0.6.0 :  1.6.0 (OK)
pygments >=2.0   :  2.2.0 (OK)
pylint >=0.25    :  1.8.2 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
rope >=0.9.4     :  0.10.7 (OK)
sphinx >=0.6.6   :  1.7.1 (OK)
sympy >=0.7.3    :  None (NOK)

It does't close properly on any platform. For now, please run
conda install tornado=4.5.3

to avoid this problem. It'll be fixed after Anaconda uploads the latest version of jupyter_client.


Get the 64bit test working on MacOSX

MacOS X doesn't have /proc/meminfo so use sysctl -a

 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.


Enabled dashboard in ceph-anisble deployment

Signed-off-by: sunilkumarn417<EMAIL_ADDRESS>
Code changes for enabling dashboard on ceph-ansible module.
Enabled dashboard  on ceph-ansible smoke test suites.

Successful test link:
http://pulpito.ceph.redhat.com/sunnagar-2020-10-20_03:26:16-smoke:ceph-ansible-master-distro-basic-clara/

can you also enable dashbaord in system-tests suite.


Provisioning.Cloud.Async sample readme requres updates

This sample is missing pretty much all documentation. Should also reference following blog post, which actually explains the model in detail - http://blogs.msdn.com/b/vesku/archive/2014/08/29/asynchronous-site-collection-provisioning-for-office-365.aspx.

Closing since documentation is in place


Improve RTT support

I've successfully setup Seggers RTT for my Zephyr project using an MCULink debug probe on an LPC55S16 (I know - the irony :D)
I really do love that the support is available, but along the way I've run into a few issues regarding usability, namely:
1. the default settings of pyocd rtt were not able to find the control block, because it searched in the wrong RAM
The memory is ordered as follows:
 Region     Type   Start       End         Size        Access  Sector      Page
 nsflash    Flash  0x00000000  0x0003d7ff  0x0003d800  rx      0x00000200  0x00000200
 nsrom      Rom    0x03000000  0x0301ffff  0x00020000  rx      -           -
 nscoderam  Ram    0x04000000  0x04003fff  0x00004000  rwx     -           -
 sflash     Flash  0x10000000  0x1003d7ff  0x0003d800  rx      0x00000200  0x00000200
 srom       Rom    0x13000000  0x1301ffff  0x00020000  srx     -           -
 scoderam   Ram    0x14000000  0x14003fff  0x00004000  srwx    -           -
 nsram      Ram    0x20000000  0x2000ffff  0x00010000  rwx     -           -
 sram       Ram    0x30000000  0x3000ffff  0x00010000  srwx    -           -

Because pyocd only searches in the first RAM section by default (here nscoderam) it couldn't find the block which is hidden in nsram. Additionally the search range is by default far to short (4096B, but block is at 0x20002300).
Afterwards the pyocd rtt command runs smoothly.
In comparison Seggers J-Link directly finds the block without issues.
2. enabling RTT over the gdbserver could be greatly improved
This has taken me the longest. The help messages if one inputs the wrong command / wrong length are basically useless. And there is no explanation for what the arguments even are (besides rtt {setup|start|stop|server}).
Additionally there are no default presets and the choice of what can be adjusted is rather interesting. Especially being able to configure the control block identity code is ...
3. gdbserver's rtt start should have more information
If rtt start completed successfully, one only receives a notification of "Control block found". I think it would really be helpful here to have some more information so that one can verify if that is plausible (e.g. number of channels, ...)

I'm btw happy to help here out. Especially 2 and 3 are easy to fix. For the first one I'm unsure. Is there maybe a way to find out where the control block could be located, or is it stored per device, ...?

Hi @tyalie, there's definitely a lot that can be improved about pyocd's RTT support. I'll have to reply fully this weekend, but I wanted to let you know I agree and am on board.
Quick answer for your question: we can probably find the control block without searching if we have the ELF by looking for the appropriate symbol. There's already an --elf argument for pyocd gdb, so it makes sense to add one for the rtt subcommand too.

we can probably find the control block without searching if we have the ELF by looking for the appropriate symbol.

I'm not fully sure if that is possible, because the SEGGER SDK builds the control block during initialization and reorders it from what exists in code. That is probably quite clever as otherwise the control block would be found in the code section, but it makes it harder for us to find it just through the elf.

It should be fine. The location of the _SEGGER_RTT symbol is what we need. And whether the acID member contains the "SEGGER RTT" string tells us whether it's initialised.
I'm not sure if that will solve the issues you describe with initialisation, though. There is also the possibility of a stale RTT CB being left in RAM. Something similar can happen for RTOS structures. The gdbserver thread reporting docs describe how this is handled for the RTOS case.
For the gdbserver we don't even need the ELF file since we can ask gdb for the value of symbols (during a specific phase when gdb connects to the gdbserver).
For the other changes, let's break them down in order of priority.

Fixes/improvements to finding the CB.

Fixing #1553 is top priority.
While this is fixed, widening the default search range to all RAM regions seems reasonable.
Adding ELF support for finding the CB.

gdbserver CB initialization sync/race condition
Config file and session options (#1417)
gdbserver rtt command improvements
Docs would be nice!!

Beyond the first item, the priorities don't really matter to me. It's just an attempt to put them in some order. 😄
Btw, honestly, I haven't really used the RTT support much. It was all written by other folks, so I'm not even all that familiar with the code. But I'd definitely like to improve it.

It should be fine. The location of the _SEGGER_RTT symbol is what we need. And whether the acID member contains the "SEGGER RTT" string tells us whether it's initialised.
I'm not sure if that will solve the issues you describe with initialisation, though. There is also the possibility of a stale RTT CB being left in RAM. Something similar can happen for RTOS structures. The gdbserver thread reporting docs describe how this is handled for the RTOS case.
For the gdbserver we don't even need the ELF file since we can ask gdb for the value of symbols (during a specific phase when gdb connects to the gdbserver).
For the other changes, let's break them down in order of priority.

Fixes/improvements to finding the CB.

Fixing Control block not found when using rtt with pyocd 0.35.0 #1553 is top priority.
Raised a PR to fix this issue, https://github.com/pyocd/pyOCD/pull/1583
While this is fixed, widening the default search range to all RAM regions seems reasonable.
Adding ELF support for finding the CB.

gdbserver CB initialization sync/race condition

Config file and session options (RTT settings not available as session options #1417)

gdbserver rtt command improvements

Docs would be nice!!

Beyond the first item, the priorities don't really matter to me. It's just an attempt to put them in some order. 😄
Btw, honestly, I haven't really used the RTT support much. It was all written by other folks, so I'm not even all that familiar with the code. But I'd definitely like to improve it.

working.。。。。。

Hi all, I am trying to pass rtt start to gdbserver and I can't seem to get it working. Does anyone have an example on how to enable rtt through gdbserver like mentioned on bullet point 3?


feature: default settings should not assume a nerd font

Did you check the docs?

[X] I have read all the lazy.nvim docs

Is your feature request related to a problem? Please describe.
I'm sure that it's more sane not to force users without a nerd font to dig documentation about icons and copy-paste chunks of code. Actually I'm don't know how many people use a nerd font, but i don't thing the percent of those people so big. The defaults should be adjusted considering the most common use cases
Describe the solution you'd like
I would suggest to use ordinary utf-8 symbols for icons by default.
Describe alternatives you've considered

Install a nerd fond (what terrify me).
Copy-past the example about icons from readme (it adds a little mess to my init.lua).

Additional context
No response

Most people use nerd fonts and if you dont want that, it's easy enough to change the icons.

There's even an example config in the docs without nerd fonts...

Most people use nerd fonts and if you dont want that, it's easy enough to change the icons.

I wouldn't be so certain about most people. There is no statistics about it, but ok. I'm not going to argue about that.
But how about another point? The defaults without fancy icons would be acceptable for everyone

The defaults without fancy icons would be acceptable for everyone

And ugly, so no thank you

ui.nerdfont = false would be good enough for people who don't use such font


End-device has difficulty joining network.

Observation: The Helium Console shows that the LNS receives the JoinRequest and sends a JoinAccept via one of the Gateways that heard the end-device.  Device never receives the JoinAccept.  The response in the console appears to be immediate, and while this does not necessarily mean that the packet will be scheduled immediately at the Gateway transmitter, it does highlight a problem.
Diagnosis: The JoinAccept packet is transmitted outside the JOIN_ACCEPT_DELAY1 and JOIN_ACCEPT_DELAY2 windows.  Could the Gateway be using the RECEIVE_DELAY1 timer instead of JOIN_ACCEPT_DELAY1 timer?
LoRaWAN Compliance Requirement: After transmitting JoinRequest, the end-device waits for the expiry of JOIN_ACCEPT_DELAY1 before turning on its receiver.
End-Device Hack:
Enable Continuous Rx to find Rx timing.
Reduce the JOIN_ACCEPT_DELAY1 timer to value less than timing.
Preferred Solution: Network should adhere to JOIN_ACCEPT_DELAY1 and JOIN_ACCEPT_DELAY2 values per the LoRaWAN Regional Parameters specification.

I'm seeing this too.
I have 2 identical third party devices that I can't modify or access the source code or any LoRaWAN config besides eui's and period.
1 joined a week ago and has been uplinking for several days.
I tried to join the other, but so far it has failed after many attempts.
Then I tried to rejoin the first, and it hasn't succeeded either.
I literally can't use Helium if it won't join - this issue should be treated as an emergency by the team, and I think the router needs more attention and developer resources.

https://github.com/helium/router/issues/478
https://github.com/helium/router/issues/465

duplicate of #465


How to launch a Gazebo Garden simulation with PX4?

Hello, I am trying to figure out how to to launch a PX4 simulation with the new versions of gazebo but I can not understand it.
I have also try to use project_mavlink but since PX4 runs in a docker container I can not see the drones fly even if the mission end well.
Plus I wish to use the DDS to get drones topic like it was in project_px4_vision example.
Can you please give me some help to do this?

check that you are working with the web_gui_4uavs branch of the project.
Also run the command $ xhost + before launching the launch_sitl.bash in order to provide access to the DISPLAY to the gazebo container.


feature(1)remove old mtmv code

Proposed changes
Issue Number: close #xxx
remove old mtmv code,we will implement mtmv in a new way
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run p0

run buildall

run feut

run buildall


Support additional credential types

clarify list of required credentials and priority:

[ ] additional legal framework credentials / versions
[ ] Certificate types (Discussion: Data model for certificates + API reference implementation / CXAR-1100)
[ ] Roles?

Documentation: steps for introducing a new credential type

VCs will be created by the issuer component and signed by the wallet; no activity on MIW side regarding new credentials required, see: #245


Add FileHash entity to TI map file hash detections

Required items, please complete
Change(s):

Adds FileHash entity mapping to Threat Intelligence detections relating to file hash indicators
Adds projection of FileHashValue and FileHashType to "TI map File Hash to CommonSecurityLog Event" and "TI map File Hash to Security Event"

Reason for Change(s):

Incidents created with these detection rule templates would not indicate the identified file hash in the entity list, requiring analyst to spend extra time reviewing event information

Version Updated:

Yes

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

@AaronHoffmannRL Would you please sign the CLA when you have a moment. Thanks.

Thanks for the reminder @aprakash13 , all set now


Failed to get ready for the component for morphling

After execute ”kubectl create namespace morphling-system”
kubectl apply -k manifests/configmap
kubectl apply -k manifests/controllers
kubectl apply -k manifests/pv
kubectl apply -k manifests/mysql-db
kubectl apply -k manifests/db-manager
kubectl apply -k manifests/ui
kubectl apply -k manifests/algorithm
root@xxx# kubectl get deployment -n morphling-system
NAME                         READY   UP-TO-DATE   AVAILABLE   AGE
morphling-algorithm-server   0/1     1            0           26m
morphling-controller         0/1     1            0           28m
morphling-db-manager         0/1     1            0           28m
morphling-mysql              0/1     1            0           28m
morphling-ui                 0/1     1            0           28m
I have installed all docker images for the components but fail to start and can access to the website of morphling

After execute ”kubectl create namespace morphling-system”
kubectl apply -k manifests/configmap kubectl apply -k manifests/controllers kubectl apply -k manifests/pv kubectl apply -k manifests/mysql-db kubectl apply -k manifests/db-manager kubectl apply -k manifests/ui kubectl apply -k manifests/algorithm
root@xxx# kubectl get deployment -n morphling-system NAME READY UP-TO-DATE AVAILABLE AGE morphling-algorithm-server 0/1 1 0 26m morphling-controller 0/1 1 0 28m morphling-db-manager 0/1 1 0 28m morphling-mysql 0/1 1 0 28m morphling-ui 0/1 1 0 28m
I have installed all docker images for the components but fail to start and can access to the website of morphling

Thank you for reaching out.
It seems that your deployments are not ready yet: AVAILABLE is 0/1.
Can you check the event of pods, providing more detailed info, so that we can inspect this problm

will close this issue


CNI_PATH not set on rootless setup

Description
Networking does not work after a standard rootless setup, because the bridge executable is not found.
Workaround (assuming that nerdctl-full has been unpacked under .local/bin):
export CNI_PATH=$HOME/.local/bin/libexec/cni

Steps to reproduce the issue

cd $HOME/.local/bin
curl -L https://github.com/containerd/nerdctl/releases/download/v1.7.2/nerdctl-full-1.7.2-linux-amd64.tar.gz | tar xz
containerd-rootless-setuptool.sh install
nerdctl run -it --rm alpine

Describe the results you received and expected
nerdctl run -it --rm alpine
FATA[0000] failed to verify networking settings: failed to create default network: needs CNI plugin "bridge" to be installed in CNI_PATH ("/opt/cni/bin"), see https://github.com/containernetworking/plugins/releases: exec: "/opt/cni/bin/bridge": stat /opt/cni/bin/bridge: no such file or directory

What version of nerdctl are you using?
1.7.2
Are you using a variant of nerdctl? (e.g., Rancher Desktop)
None
Host information
Client:
 Namespace:	default
 Debug Mode:	false

Server:
 Server Version: 1.6.26
 Storage Driver: overlayfs
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Log: fluentd journald json-file syslog
  Storage: native overlayfs
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
  rootless
 Kernel Version: 5.15.0-91-generic
 Operating System: Ubuntu 22.04.3 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 62.79GiB
 Name: linuxbox
 ID: 1575fb66-3b37-4cee-874c-1a7ce862ed01

WARNING: AppArmor profile "nerdctl-default" is not loaded.
         Use 'sudo nerdctl apparmor load' if you prefer to use AppArmor with rootless mode.
         This warning is negligible if you do not intend to use AppArmor.
WARNING: No cpu cfs period support
WARNING: No cpu cfs quota support
WARNING: No cpu shares support
WARNING: No cpuset support
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

export CNI_PATH=$HOME/.local/bin/libexec/cni

This path looks weird.
The bridge binary should be located in $HOME/local/libexec/cni.
https://github.com/containerd/nerdctl/blob/bcb5163685432904137046c7a973b8b52cb41999/docs/faq.md?plain=1#L214-L222


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v2.6.27 to before v5.10.51",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5e3ca0ec76fce92daa4eed0d02de9c79b1fe3920",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f9fb4986f4d81182f938d16beb4f983fe71212aa"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "5e3ca0ec76fce92daa4eed0d02de9c79b1fe3920",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "f9fb4986f4d81182f938d16beb4f983fe71212aa",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "seq_buf: Fix overflow in seq_buf_putmem_hex()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.51 by commit f9fb4986f4d81182f938d16beb4f983fe71212aa, it was introduced in version v2.6.27 by commit 5e3ca0ec76fce92daa4eed0d02de9c79b1fe3920. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001292


Prow job for kops build testing

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/lgtm

Is the lint job required yet?

Is the lint job required yet?

Is the lint job required yet?

No. The job is yet to be checked in.

Is the lint job required yet?

No. The job is yet to be checked in.

/hold

/hold

/retest

/retest

/unhold

/unhold


Rquest to evaluate the new Claude 3.5 Sonnet and Haiku

Request in title. Super good work!!

Thank you for your attention!
You can find the results for Claude 3.5 Sonnet on our leaderboard.
Unfortunately, we are currently unable to access Claude 3.5 Haiku.


Fix building issue on Xcode 12.5

Hi,
Error 'exported: true' has no effect in '_specialize' attribute @_specialize(exported: true, where T == UInt8) fix.
Xcode 12.5 specific error.

thank you @v-belyaev for providing this


Reliability fixes for fork-source-link-same-view

Fixes https://github.com/refined-github/refined-github/issues/5479
Follows #5351

Test

Visit https://github.com/humphd/browser-extension-template/tree/update-deps/.github
Link must point to https://github.com/fregante/browser-extension-template/tree/main/.github
Click "Code" tab
Link must be reset to https://github.com/fregante/browser-extension-template
Click "Pull requests" tab
Link must include URL parameters https://github.com/humphd/browser-extension-template/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc
Go back in history to verify everything is still correct

@fregante I'll have some time tomorrow

Going in for v22.3.17


Bazel 7 - scala_proto_aspect rule must declare '@@bazel_tools//tools/jdk:toolchain_type' toolchain in order to use java_common

Hi! I'm trying to upgrade a project to use Bazel 7 and I'm hitting this error for usages of scala_proto_library:
ERROR: /Users/amyzhao/bazel7_rulesscala_repro/BUILD:8:14: in @@io_bazel_rules_scala//scala_proto/private:scala_proto.bzl%scala_proto_aspect aspect on proto_library rule //:compression_proto:
Traceback (most recent call last):
	File "/private/var/tmp/_bazel_amyzhao/c82b0e05e300610aef22bff1e91debae/external/io_bazel_rules_scala/scala_proto/private/scala_proto_aspect.bzl", line 188, column 29, in _scala_proto_aspect_impl
		return run_aspect_phases(
	File "/private/var/tmp/_bazel_amyzhao/c82b0e05e300610aef22bff1e91debae/external/io_bazel_rules_scala/scala/private/phases/api.bzl", line 48, column 23, in run_aspect_phases
		return _run_phases(ctx, builtin_customizable_phases, target)
	File "/private/var/tmp/_bazel_amyzhao/c82b0e05e300610aef22bff1e91debae/external/io_bazel_rules_scala/scala/private/phases/api.bzl", line 77, column 32, in _run_phases
		new_provider = function(ctx, current_provider)
	File "/private/var/tmp/_bazel_amyzhao/c82b0e05e300610aef22bff1e91debae/external/io_bazel_rules_scala/scala_proto/private/scala_proto_aspect.bzl", line 155, column 37, in _phase_generate_and_compile
		java_info = _compile_sources(ctx, toolchain, proto, src_jars, deps, scalacopts, stamp_label)
	File "/private/var/tmp/_bazel_amyzhao/c82b0e05e300610aef22bff1e91debae/external/io_bazel_rules_scala/scala_proto/private/scala_proto_aspect.bzl", line 129, column 35, in _compile_sources
		source_jar = _pack_sources(ctx, src_jars),
	File "/private/var/tmp/_bazel_amyzhao/c82b0e05e300610aef22bff1e91debae/external/io_bazel_rules_scala/scala_proto/private/scala_proto_aspect.bzl", line 50, column 36, in _pack_sources
		return java_common.pack_sources(
	File "/virtual_builtins_bzl/common/java/java_common.bzl", line 156, column 68, in _pack_sources
Error in _check_java_toolchain_is_declared_on_rule: Rule 'proto_library' in '/Users/amyzhao/bazel7_rulesscala_repro/BUILD:8:14' must declare '@@bazel_tools//tools/jdk:toolchain_type' toolchain in order to use java_common. See https://github.com/bazelbuild/bazel/issues/18970.

you should be able to repro by cloning https://github.com/amybzhao/bazel7_rulesscala_repro and running bazel build //:protobuf (with bazel 7)
I've also included a patch that seems to fix the issue (using it is currently commented out in the WORKSPACE file)

Fixed with #1534


Feedback: Shorter days

For all days most students were done around ~13.30. Even with longer breaks throughout the day. I would recommend shorter days (potentially two hours pr. day over 5 days). Potentially have it spill out in the second week. Or assign some of the hours as dedicated to student cafés.

From issue #13

Kenneth was helpful and was able to help individually if needed
Suggestion for spreading the class is relevant, 3x7h does not match the cognitive science knowledge about the length of our attention span and ultradian brain cycles


Correct repository prop in package.json

Broken link on npmjs page is no fun 😢.
Fixed! 🎉

Thank you!


[gitsync] Failure to push release/policy change means waiting for next sync

If someone has pushed a commit to the config repo from outside flux, it can take a while for that to be noticed (up to five minutes, which is the period of the automatic sync). In the meantime, everything that would require a change to the repo will fail; and, there is no way to overcome this other than waiting.
Possibly the simplest way to improve this would be to notice when an operation has failed specifically because of a push conflict, and in that case schedule a sync, and tell the user to try again. The sync will most likely run before the user can resubmit the job, so the latter is likely to succeed.
An alternative would be to give the user a means to trigger a sync; there's no way to do this synchronously at present (i.e., to trigger it then wait for it to complete); but it still has the same property as above, that the sync will likely happen before the operation is retried.

#623 implemented the first option: if a job fails to push its commit, it will pull from the upstream repo before returning. That means the next thing that runs will at least have an up-to-date repo.


improved markup and language of README.md

first section lacks links; perhaps section header should change?

@sandroacoelho - Please merge...


Problem with lock acquire non-blocking optimization

(PS: I earlier tried creating an issue on the Python issue tracker but I wasn't quite sure of the exact problem, and I am still coming up to speed on asyncio. So my original report was dismissed twice, but not entirely on merits, but just because of communication gaps.)
Here is an attempt to explain it correctly:
Motivating Example
import asyncio

lock = asyncio.Lock()

def a ():  # logic is identical to b()
 yield from lock.acquire()
 for i in range(10):
  print('a: ' + str(i))
  if i % 2 == 0:
   lock.release()
   yield from lock.acquire()
 lock.release()

def b ():  # logic is identical to a()
 yield from lock.acquire()
 for i in range(10):
  print('b: ' + str(i))
  if i % 2 == 0:
   lock.release()
   yield from lock.acquire()
 lock.release()

asyncio.get_event_loop().run_until_complete(asyncio.gather(a(), b()))

print('done')

The expectation is that a() and b() will run concurrently. However, the way lock is implemented, one will run to completion before the other even starts.
May be this example is contrived, but there are other situations where you want to run cooperatively while using a lock around segments which may or may not block for safety of shared data.
Explanation
The reason one runs to completion before the other even starts is because of the following 3 lines of code in asyncio.lock.acquire:
if not self._locked and all(w.cancelled() for w in self._waiters):
    self._locked = True
    return True

I. e. when no other coroutine is waiting on the lock then yield from lock.acquire() will not yield control back to scheduler.
The problem is that the other coroutine does not even have a chance to register as a waiter because of this optimization.
Inefficiency of Workarounds
One could add a yield from asyncio.sleep(0) before the acquire or after the release. However in the common case when some coroutine has had a chance to register as a waiter, this will cause two yields instead of one. I. e. one extra, unnecessary return to the scheduler.
No Way to Predict Fast Path or Not
If asyncio.lock had a method that would let the caller know whether the lock would be acquired in the fast path or not then the caller could use this for an efficient workaround.
But, there isn't any such method or way to know this in advance.
Inconsistency with Documentation
Not entirely inconsistent, but the docstring of lock.acquire is at best ambiguous: "This method blocks until the lock is unlocked, then sets it to locked and returns True." It gives the impression that the method blocks although a precise reading indicates that it does not tell what happens if the lock is already unlocked.
This point is to suggest fixing the fundamental problem in the spirit of the documentation rather than tweak the documentation to document the current behavior.
Minimal Suggested Fix
At least allow the caller to know, after the fact, whether acquire() yielded to the scheduler or not. This could be done by setting a flag which could be interrogated in a new, separate call. Or, have acquire() return a tuple that includes an additional boolean that tells whether control was yielded or not.
Alternate Suggested Fixes

Allow a caller to interrogate in advance whether or not acquire() will yield control or not. This amounts to an additional method that tells you how many non-cancelled waiters exist. This is not ideal because it requires counting waiters twice: once in advance and once when acquire() is called.

Always yield control and do not optimize - a reasonable choice because locks in co-operative multi-tasking will typically have other coroutines waiting (otherwise you can get away without a lock itself).

Ideal Fix
My ideal fix is 2. above -- just do not optimize this and always yield control to the scheduler. Cooperative multitasking locks are qualitatively different from multi-threading locks and as far as I can see multitasking locks will typically have contention and therefore no need to optimize the fast path.
Thanks!

Hi,
Thanks for the detailed explanation! I understand the issue, but can't see why it needs to be fixed: if you use a lock in a coroutine, it's probably because you need to synchronize IO operations. They will be invoked with await/yield from and most likely yield to the scheduler.
In other words: in which "real-world" case do you think that an asyncio.Lock will be used without yielding?
Rather than yield from asyncio.sleep(0), you can use loop.call_soon(lock.release) to ensure that the lock will be released during the next loop iteration, which effectively makes yield from lock.acquire() to yield to the scheduler.

Thanks for taking the time to fully understand the issue. Typically application software fixes give significant weight to real-life use cases, whereas systems software such as libraries consider even remote cases. That's because there is a HUGE diversity of python users and if there is an issue, somebody or the other will encounter it. In other words, libraries such has this have to be a bit aspirational and strive to perfection.
That said, I dug deeper into this issue and found 2 things that make it moot.

Numerous other asyncio coroutines do not block in the fast path, including those used for mutual exclusions. Two random examples: Event.wait() and Queue.get().
Thus, firstly, fixing just Lock is of little consequence -- users must still be cautious about many other coroutines.
Secondly, I am not sure whether it is wise for all co-routines or even just mutual exclusion ones to be "fixed" so that they always yield to the scheduler, even in the fast path. In fact, I lean towards preserving the current fast paths.
Thirdly, I am inclined to believe that there should always be a way to tell whether the coroutine will yield to scheduler or not.

There is indeed a method Lock.locked() that can predict whether Lock.acquire() will yield to scheduler or not, and Lock.locked() itself does not yield to the scheduler.
This method can be used by minority users who may care about this condition. Hopefully other similar coroutines with a fast path also have similar predictor methods.

This distantly relates to an earlier debate in #284 (not involving me) regarding the behavior of asyncio.sleep(0). The call to sleep(t) was actually de-optimized (in the context of this issue) to yield to scheduler even though it could just return without yielding when t == 0. This was done to avoid adding a new method to the library.
Given the above discussion, it seems like a bad idea to have done so. I hope in light of the discussion in this issue, somebody decides to go with the original thought to add async.nop rather than overload sleep in an unusual way.

Finally, I just noticed that the atypical behavior of asyncio.sleep is not even documented in the docstring. Hopefully the library maintainers at least fix this oversight.

Accordingly, I withdraw this issue. I do want to bring @1st1 's attention to this, especially regarding asyncio.nop(). Please close this issue at your convenience.

Closing this. It was an interesting discussion! I'll add, as I close it, that I made similar decisions implementing async.Queue. At first I wanted any statement in a coroutine like yield from q.get() or yield from q.put(data) to definitely yield to the scheduler and unblock any other waiting coroutine. Guido and Nikolay convinced me that it was better for q.get() and q.put() to take a fast path if possible and not unblock all waiting coroutines. In real life, coroutines do I/O and yield to the scheduler while they wait for the I/O to complete, and that naturally causes the sort of interleaved execution you expected in your code example.

Thanks for adding your explanation @ajdavis
I agree that all is fine given the presence of fast path functions such as Lock.locked() that can predict whether another coroutine will yield or take the fast path.
The anomaly of asyncio.sleep(0) does remain and I hope some day a asyncio.nop() is added or at least the behavior of sleep(0) is documented.
Thanks!


[ BDHK-362 ] CLI Generate x-chain signature

Synchronized implementation of single-signature generation to generate identical values with Solidity.
Upgraded sign functions to produce cross-chain signatures.
Refactored sign and verification functions to support uni- and multi-userOps signature.

Summary by CodeRabbit

New Features

Enhanced signing and verification process for user operations, allowing for batch processing.
Introduced cross-chain signing functionality for user operations.

Bug Fixes

Improved error handling in signing tests, replacing panic calls with assertions.

Tests

Expanded test coverage for user operation signing, including conventional and Intent user operations.
Added new tests for cross-chain ECDSA signature generation and verification.

expectedAddress

yes, correct my bad, i meant bytes.Equal()