Unable to start container with sysbox runtime after kernel update.

Running Ubuntu 22.04, and just received kernel update from 5.15.0-47 to 5.15.0-48, matching this security advisory, and It seems that containers can no-longer be started with the runtime:-
https://ubuntu.com/security/notices/USN-5624-1
# docker run --runtime sysbox-runc -it nestybox/ubuntu-focal-docker:latest /bin/bash
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: container_linux.go:425: starting container process caused: process_linux.go:607: container init caused: process_linux.go:578: handleReqOp caused: rootfs_init_linux.go:366: failed to mkdirall /var/lib/sysbox/shiftfs/002a816d-d852-4e38-ac0d-d6b37bbdd8ea/var/lib/rancher/rke2: mkdir /var/lib/sysbox/shiftfs/002a816d-d852-4e38-ac0d-d6b37bbdd8ea/var/lib/rancher: value too large for defined data type caused: mkdir /var/lib/sysbox/shiftfs/002a816d-d852-4e38-ac0d-d6b37bbdd8ea/var/lib/rancher: value too large for defined data type: unknown.

Rolled back to 5.15.0-47 and it seems to be working again.
Installed from "sysbox-ce_0.5.2-0.linux_amd64.deb" - Any thoughts would be appreciated.

Hi @netlore , thanks for using Sysbox.
The error is for sure caused by incompatibility between shiftfs and the kernel (nothing in sysbox per-se).
Just yesterday someone else reported this issue too: https://github.com/nestybox/sysbox/issues/595
There must be something in the 5.15.0-48 kernel that is causing the incompatibility with the shiftfs module. Speculating a bit, maybe the kernel is missing a Ubuntu patch required for overlayfs to work with shiftfs, or maybe the shiftfs module needs updating to work with this kernel.
We would need to dig deep into the commits of 5.15.0-48 to see what's going on.
If rolling back to the prior kernel is not an option for you, as a workaround you can try using a newer kernel (maybe 5.18?) or configuring Sysbox to not use shiftfs (it will instead use an alternative mechanism called ID-mapped-mounts in the kernel). To do the latter, modify the sysbox systemd service for the sysbox-mgr and pass the --disable-shiftfs flag to it.
Disabling shiftfs is not ideal, but things should still work without it.

Oh wow, I've been looking into the situation with shiftfs, and it seems there could be some serious confusion going on... it seems that the upstream kernel is going for ID-Mapped mounts, but it's not yet supported for ZFS or CephFS... and shiftfs has never been officially upstreamed, but Canonical are carrying patches to include it in their kernels through 22.04... I'll need to review the diffs tomorrow, but I believe there were changes to shiftfs between -47 and -48....  perhaps because of the 11 CVE's that -48 addressed.
Can you clarify why you favour shiftfs, as you said that disabling shiftfs (using ID-Mapped mounts) is not ideal... I'd like to understand what's not ideal about it (other than the current lack of support for ZFS/CephFS).
I can of course update you with whatever details I find regarding changes to shiftfs in -48 (if you're interested)... in the morning.

I noticed in the changelog for Canonical's kernel that 5.15.0-48 includes a resync with upstream, I wonder if they lost their patch that allows shiftfs to work with overlayfs, i feel like that would break things in the above kind of way.... here's the patch for that
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846272
Will check to see if it's actually the case that this is missing, and/or if it was accidental or.....

This seems to show a related check in overlayfs, being reverted to mainline, could this be the smoking gun?
diff -ur linux-5.15.0-47/fs/overlayfs/super.c linux-5.15.0-48/fs/overlayfs/super.c
--- linux-5.15.0-47/fs/overlayfs/super.c	2022-09-22 15:52:28.806462177 +0100
+++ linux-5.15.0-48/fs/overlayfs/super.c	2022-09-22 15:53:35.962351879 +0100
@@ -873,7 +873,7 @@
 		pr_err("filesystem on '%s' not supported\n", name);
 		goto out_put;
 	}
-	if (mnt_user_ns(path->mnt) != &init_user_ns) {
+	if (is_idmapped_mnt(path->mnt)) {
 		pr_err("idmapped layers are currently not supported\n");
 		goto out_put;
 	}

This seems to show a related check in overlayfs, being reverted to mainline, could this be the smoking gun?
diff -ur linux-5.15.0-47/fs/overlayfs/super.c linux-5.15.0-48/fs/overlayfs/super.c
--- linux-5.15.0-47/fs/overlayfs/super.c	2022-09-22 15:52:28.806462177 +0100
+++ linux-5.15.0-48/fs/overlayfs/super.c	2022-09-22 15:53:35.962351879 +0100
@@ -873,7 +873,7 @@
 		pr_err("filesystem on '%s' not supported\n", name);
 		goto out_put;
 	}
-	if (mnt_user_ns(path->mnt) != &init_user_ns) {
+	if (is_idmapped_mnt(path->mnt)) {
 		pr_err("idmapped layers are currently not supported\n");
 		goto out_put;
 	}

Hi @netlore, apologies for the late reply. I don't think that's the culprit because it's related to ID-mapped-mounts rather than shiftfs itself.
Below is the list of patches to overlayfs that are required to make it work with shiftfs. I didn't check if the 5.15.0-48 kernel is missing any of these.
07648d68cea786d2ff599b51139013044ec59a8a   (05/16/22 - UBUNTU: SAUCE: overlayfs: prevent dereferencing struct file in ovl_vm_prfile_set())
b07bc17b8363190be1328fe162768f7fdcb8fcaa   (04/14/22 - UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files)
730264093da28294476d5c41b055a271facdd998   (10/02/19 - UBUNTU: SAUCE: overlayfs: allow with shiftfs as underlay)
3fb38c98e060b327cb58373775dcc95ed52d1f22   (01/19/16 - UBUNTU: SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs)
796fe8290349ef4cd8719a68966893c1c1b5a677   (01/12/22 - UBUNTU: SAUCE: vfs: test that one given mount param is not larger than PAGE_SIZE)

FYI: kernel 5.19 seems to work: https://github.com/nestybox/sysbox/issues/595#issuecomment-1255906485

Downgrading to 5.15.0-47 fixed the issue for me as well

What are the consequences in temporarily disabling shiftfs?
Do we need to recreate volumes, mounted directories?
Will it affect file ownerships ?
Thanks for the help

Hi @drakes00,

What are the consequences in temporarily disabling shiftfs?

There should be minor negative consequences (see below), but there is no need to recreate volumes, mounted dirs, etc., and it won't affect file ownership on the host machine either.
The only thing is that without shiftfs your kernel must support ID-mapped-mounts, which works in a lot of cases but not all (it's improving fast though).
One area were ID-mapped-mounts did not work until recently is compatibility with overlayfs (which is important since Docker sets up the container's rootfs with overlayfs). Due to this incompatibility we added a work-around in sysbox where if shiftfs is not present, it chowns the container's rootfs when the container starts; that's not ideal but it works.
I believe kernel 5.19 added ID-mapped-mount support for overlayfs (need to double-check). If true, then we will adjust sysbox to use ID-mapped-mounts for the container's rootfs too, and at that point ID-mapped-mounts would essentially replace shiftfs for all practical purposes.
Hope that helps.
A bit more info on this in the sysbox user guide doc.

Hey there - any update on this issue?  Running into the same on a recently updated 22.04.1 LTS ubuntu system
selina@cirl-mrt-1:~$ uname -a
Linux cirl-mrt-1 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
sudo docker run -d -p 1880:1880 --runtime=sysbox-runc  -v /home/selina/node_red_data:/data  --name mynodered localnodered
712be8c1aa6567b56b529bd48c1bd5a0cef2e3d1866d0c6c67b9ed885101c3ac
docker: Error response from daemon: OCI runtime create failed: container_linux.go:425: starting container process caused: process_linux.go:607: container init caused: process_linux.go:578: handleReqOp caused: rootfs_init_linux.go:366: failed to mkdirall /var/lib/sysbox/shiftfs/b31752a4-1f50-49b6-8fd0-eb0c983a2a78/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs: mkdir /var/lib/sysbox/shiftfs/b31752a4-1f50-49b6-8fd0-eb0c983a2a78/var/lib/containerd: value too large for defined data type caused: mkdir /var/lib/sysbox/shiftfs/b31752a4-1f50-49b6-8fd0-eb0c983a2a78/var/lib/containerd: value too large for defined data type: unknown.

Hey there - any update on this issue? Running into the same on a recently updated 22.04.1 LTS ubuntu system
selina@cirl-mrt-1:~$ uname -a Linux cirl-mrt-1 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux docker run -d -p 1880:1880 --runtime=sysbox-runc -v /home/selina/node_red_data:/data --name mynodered localnodered 712be8c1aa6567b56b529bd48c1bd5a0cef2e3d1866d0c6c67b9ed885101c3ac docker: Error response from daemon: OCI runtime create failed: container_linux.go:425: starting container process caused: process_linux.go:607: container init caused: process_linux.go:578: handleReqOp caused: rootfs_init_linux.go:366: failed to mkdirall /var/lib/sysbox/shiftfs/b31752a4-1f50-49b6-8fd0-eb0c983a2a78/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs: mkdir /var/lib/sysbox/shiftfs/b31752a4-1f50-49b6-8fd0-eb0c983a2a78/var/lib/containerd: value too large for defined data type caused: mkdir /var/lib/sysbox/shiftfs/b31752a4-1f50-49b6-8fd0-eb0c983a2a78/var/lib/containerd: value too large for defined data type: unknown.

Hi, kernel 6.0.0 solved the issue on my end.
Cheers
Linux Ma1X-Os-X-n3zu 6.0.0-060000-generic #202210022231 SMP PREEMPT_DYNAMIC Sun Oct 2 22:35:09 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
% sysbox-runc -v
sysbox-runc
        edition:        Community Edition (CE)
        version:        0.5.2
        commit:         d91c42c2125fd7aaf46f66307eb5c2a025f30289
        built at:       Wed May 18 19:49:04 UTC 2022
        built by:       Rodny Molina
        oci-specs:      1.0.2-dev

This does help; thanks!

I wonder if it's worthwhile to add a check in the sysbox-mgr to automatically disable using shiftfs in known broken kernels.

Here's a one-liner to disable shiftfs:
printf '%s\n' '[Service]' 'ExecStart=' 'ExecStart=/usr/bin/sysbox-mgr --disable-shiftfs' | sudo tee /etc/systemd/system/sysbox-mgr.service.d/override.conf && sudo systemctl daemon-reload && sudo systemctl restart sysbox

I believe kernel 5.19 added ID-mapped-mount support for overlayfs (need to double-check). If true, then we will adjust sysbox to use ID-mapped-mounts for the container's rootfs too, and at that point ID-mapped-mounts would essentially replace shiftfs for all practical purposes.

Is there somewhere I can track changes in regards to sysbox/idmapped/kernel 5.19

Hi @philipzgithub, assuming that in fact overlayfs supports ID-mapped-mounts, this will be included in the ~v0.7 release of Sysbox. Not sure on the timeline yet, likely ~Feb 2022.
In any case, overlayfs support for ID-mapped-mounts is a "nice-to-have", but not a "must-have" as mentioned in my comment above.

Thank you @ctalledo , you have save me a lot of time and effort.

the regression has been filed as a bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849

the regression has been filed as a bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849

That's great, thanks for digging that up @philipzgithub.

Oh yeah, I edited it. Thanks!

@felipecrs

I wonder if it's worthwhile to add a check in the sysbox-mgr to automatically disable using shiftfs in known broken kernels.

This is a good idea, especially with so many kernel changes going on these days in this area. During sysbox-mgr's initialization we could attempt to mount a shiftfs resource and decide to enable/disable shiftfs based on this.

I wonder if it's worthwhile to add a check in the sysbox-mgr to automatically disable using shiftfs in known broken kernels.

It's not trivial to implement though, because testing whether shiftfs-on-overlayfs works requires mounting shiftfs, and that in turn requires the process enter a new user-namespace, and that requires UID mappings, and so on ...

My initial thought was to simply check if the kernel is Ubuntu >=5.15.0-58...

It's broken since 5.15-0-48 I believe, and I believe in 5.17 and possibly 5.19 too; we don't know when the fix is coming so it's hard to tie it to a kernel version.

Updating to 5.19.0-28 fixed the problem for me :)

FYI: commit with the fix for shiftfs in Ubuntu: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar/commit/fs/shiftfs.c?h=master-next&id=cfe3544e11cc53e0038410a2199ee6afeea3687f
Should be present in the upcoming Ubuntu 23.04 release (Lunar Lobster), due April 2023.
NOTE: the upcoming release of Sysbox (v0.6.0) will automatically check if shiftfs works on the host or not, and adjust accordingly. In platforms where it works, it will use it as needed. In platforms where it does not work, it will use alternative mechanism. The new Sysbox release will also automatically check if the kernel supports ID-mapped mounts (kernel 5.12+) and overlayfs on ID-mapped mounted lower dirs (kernel 5.19+), and use both of these features. The latter one really makes shiftfs unnecessary going forward.


feat(typegen): Go Type Gen

What kind of change does this PR introduce?
Feature
What is the current behaviour?
No Go types
What is the new behaviour?
This PR adds type generation for Go based on the proposal in this discussion.
There's also some cleanup in server.ts for local development, which a) crosses off a TODO comment and b) makes it simpler to extend with new type generators later.
It's worth noting that Go structs don't have optional fields, so there's no benefit to creating multiple types per table (e.g. the TypeScript Row, Insert and Update variants of each table), so this has been left out.
Additional context
This PR requires #685 to be merged first and currently contains the changes from that PR. If you're interested in the changes made by this one, I recommend looking at commits b24e63d onwards, which mostly touch these files:

*/go.ts
server.ts
routes.ts
package.json

Still TODO:

[x] Handle composite types
[x] Handle range types
[x] Tests

Let me know your feedback or if you'd like any changes :)

Going to mark this as draft for now - I've decided it might be better to separate out the Select, Insert and Update models (as in JS) and make use of the sql.Null* types in the standard library

I've now done the above, so this should be ready to go


LightBox fade-in animation not working

I see there is intention in the code to animate the alpha for the lightbox so that it fades in. However on calling the lightbox, if I have e.g.
      style: {
        backgroundBlur: "none",
        backgroundColor: "#888888DD"
      }

then the background instantly turns grey with transparency, and on dismiss it fades back nicely.
It would be great to have the background fade in also.

This issue will be addressed in react-native-navigation #246.


Initial work on electra mobile

Initial work for storing the encrypted device id after verifying from the back end - This is just for a demo and more work will start after API availability.
in the Demo we have.

Splash loading screen which navigates the user to Login or Registration Screen after validating the device id from back end which is spring boot which I am using for testing purpose.

Thank you @durrab and welcome here 🙂 !
I will check and test that today.

So first global notes:

I don't know why it's not there but there should be an .editorconfig file making sure we keep some consistency among the text editors / IDEs. I see you are using Eclipse, there is a plugin to take it into account. We use the same rules among all projects: https://github.com/Electra-project/electra-desktop/blob/master/.editorconfig
Be careful not to push your .settings & your .env. Add these paths to the gitignore. As for the .env, provide instead a .env.sample which is an empirical convention, so that you can add private data in you .env while sharing with contributors what env vars they need to set in order to contribute.


Python 2.6 support

This PR adds Python 2.6 support. Most of the work was in fixing the tests to use unittest2 instead of unittest for python < 2.7. The fixes to the code itself involved adding positional arguments to all of the .format() calls.
All but 1 tests passed (the CREATE DATABASE IF NOT EXIST test fails because that feature wasn't added until influxdb 0.9.4 from what I can tell, and this was testing against 0.9.3). I did not test this on anything other than py26
Should resolve #288

You may also enable python2.6 tests in travis via .travis.yml

Updated .travis.yml. The newly added py26 check passes. Does everything else look ok?

Looks good. I'll fix flake8 and py32 myself.

Thank you for your work!


Investigate ways to improve how critical notebook failures can be surfaced more easily

Scenario:

Clone the Elyra examples repository https://github.com/elyra-ai/examples
Open JL and navigate to pipelines/dax_noaa_weather_data
Open  analyze_NOAA_weather_data.pipeline
Open the properties for the load_data.ipynb node
Remove the pre-defined environment variable DATASET_URL
Save and run the pipeline using the local configuration
Pipeline execution will fail because the notebook cannot perform it's task without the variable being present (code cell 2)

The following information is displayed in

Traceback (most recent call last):
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor_local.py", line 151, in process
    subprocess.run(argv, cwd=file_dir, env=envs, check=True)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/subprocess.py", line 512, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['papermill', '/Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb', '/Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb', '--cwd', '/Users/patti/elyra_ga/workspace_italo/hello_world']' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor_local.py", line 70, in process
    operation_processor.process(operation)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor_local.py", line 154, in process
    raise RuntimeError(f'Internal error executing {filepath}') from ex
RuntimeError: Internal error executing /Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/tornado/web.py", line 1703, in _execute
    result = await result
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/handlers.py", line 89, in post
    response = await PipelineProcessorManager.instance().process(pipeline)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor.py", line 69, in process
    res = await asyncio.get_event_loop().run_in_executor(None, processor.process, pipeline)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor_local.py", line 72, in process
    raise RuntimeError(f'Error processing operation {operation.name}.') from ex
RuntimeError: Error processing operation load_data.

The following information is included in the log file, when running the pipeline locally. Note the output in Exception encountered at "In [2]":, which surfaces the root cause of the expected failure.
Processing Pipeline : sss
Input Notebook:  /Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb
Output Notebook: /Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb
Working directory: /Users/patti/elyra_ga/workspace_italo/hello_world
Executing:   0%|                                                               | 0/11 [00:00<?, ?cell/s]Executing notebook with kernel: python3
Executing:  36%|████████████████████                                   | 4/11 [00:01<00:02,  2.70cell/s]
Traceback (most recent call last):
  File "/Users/patti/anaconda3/envs/elyra_ga/bin/papermill", line 8, in <module>
    sys.exit(papermill())
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/papermill/cli.py", line 256, in papermill
    execution_timeout=execution_timeout,
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/papermill/execute.py", line 110, in execute_notebook
    raise_for_execution_errors(nb, output_path)
  File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/papermill/execute.py", line 222, in raise_for_execution_errors
    raise error
papermill.exceptions.PapermillExecutionError:
---------------------------------------------------------------------------
Exception encountered at "In [2]":
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-2-55cb24574a79> in <module>
      1 if os.environ.get('DATASET_URL') is None:
----> 2     raise RuntimeError('Cannot run notebook. Required parameter is missing.')
      3
      4 data_file = os.environ['DATASET_URL']

RuntimeError: Cannot run notebook. Required parameter is missing.

[E 12:27:42.003 LabApp] Internal error executing /Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb
[E 12:27:42.004 LabApp] Uncaught exception POST /elyra/pipeline/schedule?1601666859941 (::1)
    HTTPServerRequest(protocol='http', host='localhost:8888', method='POST', uri='/elyra/pipeline/schedule?1601666859941', version='HTTP/1.1', remote_ip='::1')
    Traceback (most recent call last):
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor_local.py", line 151, in process
        subprocess.run(argv, cwd=file_dir, env=envs, check=True)
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/subprocess.py", line 512, in run
        output=stdout, stderr=stderr)
    subprocess.CalledProcessError: Command '['papermill', '/Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb', '/Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb', '--cwd', '/Users/patti/elyra_ga/workspace_italo/hello_world']' returned non-zero exit status 1.

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor_local.py", line 70, in process
        operation_processor.process(operation)
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor_local.py", line 154, in process
        raise RuntimeError(f'Internal error executing {filepath}') from ex
    RuntimeError: Internal error executing /Users/patti/elyra_ga/workspace_italo/hello_world/load_data.ipynb

    The above exception was the direct cause of the following exception:

    Traceback (most recent call last):
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/tornado/web.py", line 1703, in _execute
        result = await result
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/handlers.py", line 89, in post
        response = await PipelineProcessorManager.instance().process(pipeline)
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor.py", line 69, in process
        res = await asyncio.get_event_loop().run_in_executor(None, processor.process, pipeline)
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/concurrent/futures/thread.py", line 57, in run
        result = self.fn(*self.args, **self.kwargs)
      File "/Users/patti/anaconda3/envs/elyra_ga/lib/python3.7/site-packages/elyra/pipeline/processor_local.py", line 72, in process
        raise RuntimeError(f'Error processing operation {operation.name}.') from ex
    RuntimeError: Error processing operation load_data.
[E 12:27:42.014 LabApp] {
      "Host": "localhost:8888",
      "Connection": "keep-alive",
      "Content-Length": "1575",
      "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.121 Safari/537.36",
      "X-Xsrftoken": "2|a9adb8bb|0fd98202a8b5a025f542eed9abdc80eb|1600702626",
      "Authorization": "token 248bd113da8cb22fbcada8e1d6738672858b8171b9c9ee7a",
      "Content-Type": "text/plain;charset=UTF-8",
      "Accept": "*/*",
      "Origin": "http://localhost:8888",
      "Sec-Fetch-Site": "same-origin",
      "Sec-Fetch-Mode": "cors",
      "Sec-Fetch-Dest": "empty",
      "Referer": "http://localhost:8888/lab/workspaces/auto-V",
      "Accept-Encoding": "gzip, deflate, br",
      "Accept-Language": "en-US,en;q=0.9,de;q=0.8",
      "Cookie": "username-localhost-8889=\"2|1:0|10:1600383050|23:username-localhost-8889|44:MDU2OTMwN2ZkYjgyNDVkZTk4ZjAzOTA0NDM3YjgwMDE=|d3c5c9c627c74545b1fe3f7819e9b6bd1fa6ad2e3b140963bb1e07bfd1d47f79\"; _xsrf=2|a9adb8bb|0fd98202a8b5a025f542eed9abdc80eb|1600702626; username-localhost-8888=\"2|1:0|10:1601666854|23:username-localhost-8888|44:M2I1YWFiZDAwMmJlNGFjNDg1OWFiYWNjZGM3NmFhN2I=|472a3b969ca642d90dfaa058cdd00b960ef40b0b041a7b0cc2971ccba3d05478\""
    }
[E 12:27:42.014 LabApp] 500 POST /elyra/pipeline/schedule?1601666859941 (::1) 2070.48ms referer=http://localhost:8888/lab/workspaces/auto-V

The key idea the notebook is trying to implement is that under certain circumstances notebook processing must be aborted, either because a user error (like in this case a missing input), or because the code itself was bad.

Ideally a user won't have to dig through lengthy log outputs to determine where the failure occurred. Do note that the completed notebook (for local execution!) contains the error

For KFP execution one would have to download the artifacts from COS to obtain the same information.

Hmm - I'm not convinced we can do much better here.  We might be able to "move" the location of the notebook error closer to the end of the traceback, but given its logged in the first place, that seems sufficient.
In addition, you certainly cannot beat the fact that the error is preserved in the output notebook!  Sure, for non-local runs that output notebook is not local, but that's all working as designed.
I'm inclined to close this issue but we should probably see what dumping CalledProcessError.stderr can do for us.  If it merely leads to the same information getting logged twice, then that is even worse.

I spent some time with this and there might be some things we can do to prevent the user from having to dig through the server log - although nothing is really easier than just pulling up the notebook and seeing the errors.

I think we should be calling papermill, both locally and from kfp-notebook, with the --no-progress-bar option.  This eliminates the useless progress bar output in the log.  Here's an example of what gets removed:
Executing:   0%|          | 0/2 [00:00<?, ?cell/s]Executing notebook with kernel: python3\n\rExecuting:  50%|\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88     | 1/2 [00:01<00:01,  1.28s/cell]\rExecuting: 100%|\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88\xe2\x96\x88| 2/2 [00:01<00:00,  1.19cell/s]

By adding capture_output=True to the subprocess.run() command, the resulting CalledProcessError instance (raised when a non-zero exit status occurs) will populate its stderr property with what is typically in the log file relative to the notebook.  However, this has newlines escaped and the entire stack trace - for the notebook error is on a single line.
Here's an example:
b'Input Notebook:  /Users/kbates/notebooks/elyra/pipeline1/node1.ipynb\nOutput Notebook: /Users/kbates/notebooks/elyra/pipeline1/node1.ipynb\nWorking directory: /Users/kbates/notebooks/elyra/pipeline1\nExecuting notebook with kernel: python3\nTraceback (most recent call last):\n  File "/opt/anaconda3/envs/elyra-dev/bin/papermill", line 10, in <module>\n    sys.exit(papermill())\n  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/click/core.py", line 829, in __call__\n    return self.main(*args, **kwargs)\n  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/click/core.py", line 782, in main\n    rv = self.invoke(ctx)\n  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/click/core.py", line 1066, in invoke\n    return ctx.invoke(self.callback, **ctx.params)\n  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/click/core.py", line 610, in invoke\n    return callback(*args, **kwargs)\n  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/papermill/cli.py", line 238, in papermill\n    execution_timeout=execution_timeout,\n  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/papermill/execute.py", line 110, in execute_notebook\n    raise_for_execution_errors(nb, output_path)\n  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/papermill/execute.py", line 222, in raise_for_execution_errors\n    raise error\npapermill.exceptions.PapermillExecutionError: \n---------------------------------------------------------------------------\nException encountered at "In [1]":\n---------------------------------------------------------------------------\nFileExistsError                           Traceback (most recent call last)\n<ipython-input-1-e517ff5eec72> in <module>\n      7 os.getenv("OUTPUT_FILENAMES")\n      8 # Execute the node\n----> 9 NotebookNode().run()\n\n~/notebooks/elyra/pipeline1/node_util/node_util.py in run(self)\n     71         self.process_inputs("INPUT_FILENAMES")\n     72         self.perform_experiment()\n---> 73         self.process_outputs("OUTPUT_FILENAMES")\n     74 \n     75     def perform_experiment(self) -> None:\n\n~/notebooks/elyra/pipeline1/node_util/node_util.py in process_outputs(self, env_var)\n    104         for filename in filenames:\n    105             if filename:\n--> 106                 outputs.append(OutputNodeFile(filename))\n    107 \n    108 \n\n~/notebooks/elyra/pipeline1/node_util/node_util.py in __init__(self, filename)\n     36 \n     37         if os.path.exists(self.filename):\n---> 38             raise FileExistsError("File \'{}\' already exists!".format(self.filename))\n     39 \n     40     def write(self, data) -> None:\n\nFileExistsError: File \'node1a.out\' already exists!\n\n'

By making these changes, we can get the contextual error back to the user, but, it's nasty.  If we add this, we should perhaps look into expanding the escaped newlines so that least this section of the error details reads more nicely - like what the logs show.
By the way when capture_output=True the log file would only contain what we log and not the non-escaped output that is there today.  So, while we gain the information getting to the user, we lose the pretty-printing from the papermill logging.  That said, I think if we can pretty the CalledProcessError.stderr output (perhaps in the server so that the logged exception looks good as well) then this is probably a win for the user.
Thoughts?
cc: @lresende

Turns out that by simply decoding the stderr property as follows: ex.stderr.decode('unicode_escape') we can produce the following error details entry (which also gets logged into the server log the same way):
Traceback (most recent call last):
  File "/Users/kbates/repos/oss/elyra-ai/elyra/elyra/pipeline/processor_local.py", line 151, in process
    completed = run(argv, cwd=file_dir, env=envs, capture_output=True, check=True)
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/subprocess.py", line 487, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['papermill', '/Users/kbates/notebooks/elyra/pipeline1/node1.ipynb', '/Users/kbates/notebooks/elyra/pipeline1/node1.ipynb', '--cwd', '/Users/kbates/notebooks/elyra/pipeline1', '--no-progress-bar']' returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/kbates/repos/oss/elyra-ai/elyra/elyra/pipeline/processor_local.py", line 70, in process
    operation_processor.process(operation)
  File "/Users/kbates/repos/oss/elyra-ai/elyra/elyra/pipeline/processor_local.py", line 153, in process
    raise RuntimeError(f'Internal error executing {filepath}: {ex.stderr.decode("unicode_escape")}') from ex
RuntimeError: Internal error executing /Users/kbates/notebooks/elyra/pipeline1/node1.ipynb: Input Notebook:  /Users/kbates/notebooks/elyra/pipeline1/node1.ipynb
Output Notebook: /Users/kbates/notebooks/elyra/pipeline1/node1.ipynb
Working directory: /Users/kbates/notebooks/elyra/pipeline1
Executing notebook with kernel: python3
Traceback (most recent call last):
  File "/opt/anaconda3/envs/elyra-dev/bin/papermill", line 10, in <module>
    sys.exit(papermill())
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/papermill/cli.py", line 238, in papermill
    execution_timeout=execution_timeout,
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/papermill/execute.py", line 110, in execute_notebook
    raise_for_execution_errors(nb, output_path)
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/papermill/execute.py", line 222, in raise_for_execution_errors
    raise error
papermill.exceptions.PapermillExecutionError:
---------------------------------------------------------------------------
Exception encountered at "In [1]":
---------------------------------------------------------------------------
FileExistsError                           Traceback (most recent call last)
<ipython-input-1-e517ff5eec72> in <module>
      7 os.getenv("OUTPUT_FILENAMES")
      8 # Execute the node
----> 9 NotebookNode().run()

~/notebooks/elyra/pipeline1/node_util/node_util.py in run(self)
     71         self.process_inputs("INPUT_FILENAMES")
     72         self.perform_experiment()
---> 73         self.process_outputs("OUTPUT_FILENAMES")
     74
     75     def perform_experiment(self) -> None:

~/notebooks/elyra/pipeline1/node_util/node_util.py in process_outputs(self, env_var)
    104         for filename in filenames:
    105             if filename:
--> 106                 outputs.append(OutputNodeFile(filename))
    107
    108

~/notebooks/elyra/pipeline1/node_util/node_util.py in __init__(self, filename)
     36
     37         if os.path.exists(self.filename):
---> 38             raise FileExistsError("File '{}' already exists!".format(self.filename))
     39
     40     def write(self, data) -> None:

FileExistsError: File 'node1a.out' already exists!

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/site-packages/tornado/web.py", line 1703, in _execute
    result = await result
  File "/Users/kbates/repos/oss/elyra-ai/elyra/elyra/pipeline/handlers.py", line 89, in post
    response = await PipelineProcessorManager.instance().process(pipeline)
  File "/Users/kbates/repos/oss/elyra-ai/elyra/elyra/pipeline/processor.py", line 69, in process
    res = await asyncio.get_event_loop().run_in_executor(None, processor.process, pipeline)
  File "/opt/anaconda3/envs/elyra-dev/lib/python3.7/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/Users/kbates/repos/oss/elyra-ai/elyra/elyra/pipeline/processor_local.py", line 72, in process
    raise RuntimeError(f'Error processing operation {operation.name}.') from ex
RuntimeError: Error processing operation node1.

I think this is an improvement and am happy to submit a PR if others agree.

I went ahead and created the PR since its probably easier to discuss this stuff in the PR.

Much better, although I admit if the output in the "Error making request" dialog window could be reduced to just stating something like "An error occurred processing cell X in notebook Y. Please check the notebook output for details." that be (user friendly)^2 😃


Psbt file save issue

Unable to save PSBT to microSD

Check the log file (Help menu) for the error message. This error is from the operating system - not much Sparrow can do.


Ability to configure roles for gcloud_iam provider

Summary
At the moment, for every provider one can configure a set of roles with permission sets. It enables one to control the access roles to which a user can raise appeals for.
Bigquery example - https://odpf.github.io/guardian/docs/providers/bigquery#yaml-representation which has roles and permission set for each resource type.
This is not true for gcloud_iam provider. Only this provider does not have a way to take in the configured roles/permissions from the provider config file. Due to which if the gcloud_iam is exposed as a provider to users, the GetRoles method will fetch every iam role  available in GCP. If one wants to restrict users to only a certain roles through guardian like other providers, they cannot currently., and the user would be able to raise an appeal for any role in gcp.
Proposed solution
Modify the gcp provider to

get roles from the provider config if roles are provided, and use them as the only roles available for appeals.
continue as it is in the current form if the roles are not provided in the provider config.

@bsushmith @rahmatrhd is this duplicate of #218?

@ravisuhag not initially, but now the discussion for this also happens in #218

Covered in #218


Add data type conversion support in injectorFlowProxyController.js

Currently, the code maps the injector attributes to flow input variables and sets the data type as String but the code needs to be doing better inference on the injector attribute data type to identify boolean, number, date, etc.
https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/components_config_for_flow_tips_map.htm

@afawcett @ImJohnMDaniel I've started work on this feature in branch https://github.com/afawcett/force-di/tree/flow-proxy-attributes

@afawcett @ImJohnMDaniel I believe we are at an architectural decision making point before moving forward on this issue.
To map the injector attribute values to flow input variables, then we need to know the intended data type the injector attributes represent in the flow.
Relying on javascript's typeof or instanceof keywords is not sufficient because, for example, Date and DateTime values returned from apex methods and stored in <aura:attribute type="Date"> and <aura:attribute type="DateTime"> tags are still passed around among the components as JSON, which is just text.
What I'm seeing is that regardless what type I specify for <aura:attribute type="Date"> or <aura:attribute type="DateTime">, the data type of those attributes are passed to <c:injectorAttribute> and obtained by the injector's js controller as JSON. So when I do typeof injectAttr.get('v.value') then I'm getting string. So it is very ambiguous whether the developer wanted to pass a literal text value as "2018-07-28" or the date value.
Options
Option 1
My preferred approach would be that we leverage the Flow's metadata and infer the data type based on matching injector attribute names to flow input variable names.
However, to complicate things, since we're in Lightning, I can't easily retrieve the expected Flow input variables from either the REST API (only works if it's autolaunched/headless by the way) or the Metadata API (for any flow type) without using a Named Credential. This limitation Andy and I have discussed at length on other projects.
Option 2
Since option 1 requires undue burden of Named Credential, I believe we need the <c:injectorAttribute> tags to include a third property to indicate their intended data type.
<aura:component>
    <aura:attribute name="name" type="String"/>
    <aura:attribute name="value" type="Object"/>
    <aura:attribute name="type" type="String"/>
</aura:component>

<c:injector bindingName="flow_AccountRecord">
    <c:injectorAttribute name="recordId" value="{!v.recordId}" type="String"/>
    <c:injectorAttribute name="myDate" value="{!v.myDate}" type="Date"/>
    <c:injectorAttribute name="myDateTime" value="{!v.myDateTime}" type="DateTime"/>
</c:injector>

For reference, here is example code using MetadataService.cls to retrieve Flow input variable information.
This does fail when called from Apex class in Lightning component context due to invalid session id, as expected. Hence a need for Named Credential, so I'm leaning towards implementing this with adding dataType property to <c:injectorAttribute> component until/if such a time where Named Credentials aren't necessary to make API callouts from Apex in Lightning.
However, even though going through Metadata API route means we can infer the data types, the Metadata API requires the flow version as part of the API name when retrieving the information. This would mean that in the CMDT, the developer would need to somehow indicate the flow version. We wouldn't want it to be part of the flow name itself, I don't think, because in visualforce and apex contexts we can invoke a flow without specifying the version.
    private static void testGetFlowMetadata() {

        MetadataService.MetadataPort service = new MetadataService.MetadataPort();
        service.SessionHeader = new MetadataService.SessionHeader_element();
        service.SessionHeader.sessionId = UserInfo.getSessionId();

        MetadataService.ReadFlowResult result = (MetadataService.ReadFlowResult) service.readMetadata('Flow', new String[] { 'AccountRecordFlowVF-4' });
        for ( MetadataService.Flow f : result.records ) {
            System.debug(f);
            for ( MetadataService.FlowVariable var : f.variables ) {
                System.debug('\t' + 'name=' + var.name + ', dataType=' + var.dataType + ', isInput=' + var.isInput + ', isOutput=' + var.isOutput + ', isCollection=' + var.isCollection + ', objectType=' + var.objectType);
            }
            System.debug('---');
        }

    }

Just to bring this thread up to speed.  @douglascayers, based on side discussions, it appears that better option is option 2 -- "<c:injectorAttribute> tags to include a third property to indicate their intended data type".  Is that accurate?

Correct @ImJohnMDaniel


feat(pixels): add my new pixel (34, 34)

Checklist

[ ] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Thank you god!


UI not translated: QueueModeNext / QueueModeInstant

These texts seem to be not properly translated. Whatever I changed language, they remained the same.

Tested on the demo world: https://vrchat.com/home/world/wrld_7239d09c-7b25-43a5-8ccd-502d986b016a

Hello! It seems the problem is the player unable to find the newly added texts, as these texts are added in 1.0.10, did you changed or copied the language text to elsewhere before updating to latest version?

No, I did not modify the string; it occurred on your world.
Installing the latest VPM package into a new project did not produce the issue.
I tried to reproduce the issue on my world, but I couldn't.

Oh I see! I thought you are talking about problem occurred when you try importing it to your world.
It's fine, just a minor issue that I will fix it later.
But it does not related the asset provided on this repository, so I'll close this issue.
Thanks for informing me about this anyway.


Custom AppInsights for Analytics page

Background
We'd like to know how often users are utilizing and interacting with the new Analytics page. To that end, we'd like to include some custom AppInsights metrics to gauge user engagement.
Proposed Solution
Normally we would just use backend calls as a proxy for these engagement metrics, but in this case the metrics will be loaded on every admin login so they won't tell us much about how often the users are actually taking time to utilize or play with the metrics. Instead, we'd like frontend metrics to track the following:

how often users engage with the facility selection
how often they engage with date selection (and what date range they most often choose, if possible)
clicks into the admin dashboard from top nav, vs just loading and landing on that page

Thanks for capturing our conversation here, Emma. Appreciate this...and will be eager to see what we discover!

Icing this in favor of looking into GA.

Closing as it will become obsolete when we have real analytics in place.


Only let reindexing puts through locked bucket if their TaS token matches that of the lock

@geirst please review
@jonmv FYI
Avoids race condition edge case where reindexing puts from an outdated
visitor may pass through a bucket lock intended for a newly created
visitor operation
Tokens are 128-bit values derived from a CSPRNG, so uniqueness is for
all intents and purposes guaranteed.

🥳


[Question] How to update translation

I guess this might be done through some website like crowdin or something but where i can find the link?

Thanks for asking!
Information on translation is available here:
https://github.com/coreinfrastructure/best-practices-badge/blob/main/doc/translators.md
We would love your help! What languages other than English do you know well?


Fix shellcheck errors

Signed-off-by: Shatakshi<EMAIL_ADDRESS>Related to Bugbash. Fixed errors reported by sonatype lift.

Update
This PR was from a subtask in issue #3081.
Due to the test case tests.test_rwx.test_rwx_statefulset_scale_down_up always fail.


[v2] Refactoring based on rk-entry/v2

Codecov Report

Merging #59 (0218635) into master (0b6ef15) will decrease coverage by 1.95%.
The diff coverage is 91.74%.

@@            Coverage Diff             @@
##           master      #59      +/-   ##
==========================================
- Coverage   90.36%   88.41%   -1.96%
==========================================
  Files          19       19
  Lines        1661     1467     -194
==========================================
- Hits         1501     1297     -204
- Misses        131      141      +10
  Partials       29       29

Impacted Files
Coverage Δ

boot/error/grpc_error_wrap.go
100.00% <ø> (ø)

middleware/common.go
96.51% <ø> (ø)

middleware/context/wrappers.go
66.66% <ø> (ø)

middleware/cors/interceptor.go
100.00% <ø> (ø)

middleware/csrf/interceptor.go
100.00% <ø> (ø)

middleware/secure/interceptor.go
100.00% <ø> (ø)

boot/proxy_entry.go
62.44% <77.27%> (-0.35%)
:arrow_down:

boot/grpc_entry.go
87.19% <88.43%> (-5.12%)
:arrow_down:

boot/gw_server_options.go
90.16% <100.00%> (-0.24%)
:arrow_down:

middleware/auth/server_interceptor.go
94.73% <100.00%> (ø)

... and 10 more

Continue to review full report at Codecov.

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


Protect Network Call during Client Creation with Retries

The client creation code used in the DedupManifestArtifactClientFactory contains a hidden network call to retrieve all the API locations.  This will occasionally fail with an opaque error.   Instead of failing, use our standard retry helper to backoff and retry in case the issue is transient.

@mjroghelia - can you please merge this PR. Thanks

@mjroghelia - can you please merge this PR. Thanks


API Management - Create or Update API on Azure Functions - Make fields editable with variables

When I want to use this task in a Task group then I'll have to work with variables. One field is not editable, namely:

Functions Resource Group

Simular issue as #16

Hello,
Done and published!
Best Regards

You are fast 🥇 👍


Add proto and sidecar code for volumegroup

This PR adds the following codes/logic:

Updated the csi-addons spec api
Added volume group proto files
Added volume group sidecar and client setup

Created a separate PR for proto and sidecar code so that we can merge this and later on take the controller code once ceph code is merged.

@nixpanic @Madhu-1 @Rakshith-R can you please take a look.

Looks good to me. @Madhu-1 do you want to have a final look?

@mergifyio refresh

@mergifyio rebase


Commands unavailable in command palette

Sublime Text version number: 3.0, build 3170
Git version number: 2.4.2
OS type and version: Mac OSX High Sierra, 10.13.3

Noticed that the usual commands for GitSavvy (status, push, etc) are unavailable in the command palette. Uninstalling and reinstalling the package has no effect, but the reinstall did yield the attached console output.
Console error output:

reloading plugin GitSavvy.init
Traceback (most recent call last):
File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 116, in reload_plugin
m = importlib.import_module(modulename)
File "./python3.3/importlib/init.py", line 90, in import_module
File "", line 1584, in _gcd_import
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
zipimport.ZipImportError: bad local file header in /Users/brandong/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package
reloading plugin GitSavvy.git_savvy
Traceback (most recent call last):
File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 116, in reload_plugin
m = importlib.import_module(modulename)
File "./python3.3/importlib/init.py", line 90, in import_module
File "", line 1584, in _gcd_import
File "", line 1565, in _find_and_load
File "", line 1532, in _find_and_load_unlocked
File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 1183, in load_module
exec(compile(source, source_path, 'exec'), mod.dict)
File "/Users/brandong/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package/git_savvy.py", line 41, in
File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 1183, in load_module
exec(compile(source, source_path, 'exec'), mod.dict)
File "/Users/brandong/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package/gitlab/commands/init.py", line 1, in
File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 1183, in load_module
exec(compile(source, source_path, 'exec'), mod.dict)
File "/Users/brandong/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package/gitlab/commands/open_on_remote.py", line 5, in
File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 1183, in load_module
exec(compile(source, source_path, 'exec'), mod.dict)
File "/Users/brandong/Library/Application Support/Sublime Text 3/Installed Packages/GitSavvy.sublime-package/gitlab/gitlab.py", line 14, in
ImportError: cannot import name FailedGitLabRequest

Let me know how else I can help troubleshoot.

I see you have updated Sublime to lates release.
Have you tried to restart sublime. Maybe also the mac?
Never seen this error before.

Yess!!!!! I am pro at fixing these issue.  :D  Glad we solved it


Question: Regarding BotAPIv3.0

Hi, Thanks for all the work that is getting done to maintain this repository active. Was planning to use some of the features of BotAPI v3.0. Could you please let me know the current release plan for BotAPIv3.0.
Thanks again!.

See #332. There's no released version that supports Bot API v3.0 yet though, so you'll have to clone the git version manually for now:
rm -rf node_modules/node-telegram-bot-api
git clone https://github.com/yagop/node-telegram-bot-api.git node_modules/node-telegram-bot-api

Hi, Thanks for the info.

Thanks @sheshvs for using this library. Thanks @nyuszika7h for the help.
ANS: https://github.com/yagop/node-telegram-bot-api/issues/349#issuecomment-307565380


fif.gz is allowed even though not mentioned in the spec

We should either remove it or adjust the spec.

+1 for adjusting the spec and continue to allow for .fif.gz. Compression is a good feature.

why not, but the corresponding datasets are also going to be updated I presume?

I don't think we should encourage people to compress their MEG recordings (no matter which file format is used). Maybe it's a bit radical, but I'd be more in favor of not supporting .fif.gz extensions.
The .fif files have low compression ratios, between 10% and 15%. It saves some storage space, but to the expense of the usability of the datasets. To process the MEG recordings, they need to be fully unzipped first, which takes a lot of time and doubles the storage space needed. The gain in storage is negligible compared to the complexity of handling these compressed files.
The question is not the same for .nii files: these are small files with high compression ratios (up to 75%) that can be uncompressed in memory on the fly.
If compression has to be added to MEG recordings, it should be done within the file formats (it would be possible to add some compression to the .fif files), not simply by gzipping them.

Thanks @ftadel, I was going to reply very similar.
I think this topic was raised a while ago, and we finally decided not to allow compressed *.gz files for MEG, for the reasons given above by @ftadel . So we finally didn't include this format in the specs for MEG.
I don't think it makes sense to reopen the discussion again, unless someone has a very strong opinion. For what I remember there was quite big consensus.
However, it's true this is not contemplated in the validator, so this needs to be fixed.
I will also make it more explicit in the specs.
((We are only speaking for MEG data))
Cheers!

thanks @ftadel for the more nuanced view, I wasn't aware of previous discussions. :-)

I agree with @ftadel but someone has to update the corresponding dataset. Currently, the files in ds000117 are in fif.gz format :-)

Rik is working on it. He will also add the missing Freesurfer folders and some fields in the json files.

I agree with @ftadel you won't get much with fif.gz for raw files and it significantly slows down the IO or requires to duplicate files on disk.

Erratum:
I've just unzipped all the .fif.gz files in ds000117 and realized that my initial tests were bad examples. These files have compression ratios of around 70% (it saves 30% of the disk space).
Even at this ratio, I would not recommend gzipping these files because of the added complexity to handle and process them. If we have to unzip all the files before processing them, we lose a lot of the interest of the compression. But it is more open to discussion than what I thought.

And empty room recordings are almost at 50% compression ratio...

That's quite interesting indeed !


KAFKA-2603: Add timeout arg to ConsoleConsumer

Added --timeout-ms argument to ConsoleConsumer that works with both old and new consumer. Also modified ducktape ConsoleConsumer service to use this arg instead of consumer.timeout.ms config that works only with the old consumer.

Just realize now console_consumer.properties would become a dummy file again :)
My take is that the value of having a template file is to specify some universal config values that will be used across all test runs with probably different combinations of other config values; or universally use some pre-defined values from the framework setup. For example
tests/kafkatest/services/templates/console_consumer.properties
If we do not have any value definitions in the template file (i.e. a file is empty / dummy), then appending different values to this file and use it for various test runs is no difference with creating a new file each run with different values on-the-fly. Hence I feel the empty file itself brings us no extra benefit for customizing test runs, and better be removed and creating new files for different runs instead. For now since we do not have customizable test runs using console consumer yet we can simply do the same as #271.

@guozhangwang Have removed the empty console_consumer.properties file in the latest commit.

console_consumer.properties is now used by quota tests and is no longer empty. So I have reverted the change to remove the file and rebased.

LGTM, thanks @rajinisivaram for being so patient in the review process.

@guozhangwang Thank you for reviewing and committing this.


Support JSX compilation

TypeScript can compile TSX (.tsx files, maybe jsx files too?).

TypeScript ships with three JSX modes: preserve, react, and react-native

I imagine the only one that would work is react as preserve would require a second step.

https://www.typescriptlang.org/docs/handbook/jsx.html seems there are a few more config values for { jsx: ...} that might be possible.

https://github.com/google/playground-elements/pull/319


When a single / is in list of files, AzCopy deletes all blobs under the src directory

Which version of the AzCopy was used?
10.10.0
Which platform are you using? (ex: Windows, Mac, Linux)
All
What command did you run?
Delete blob
What problem was encountered?
If a line ends with consecutive /s in the list of files file, e.g. /, AzCopy will delete all blobs under the src directory. The expected result is that only blobs with a prefix / under the src directory are deleted.
How can we reproduce the problem in the simplest way?
Have a blob container with these two blobs
blob.txt
/blob.txt
azcopy delete https://acct.blob.core.windows.net/container/
list of files content:
/
Check the result, blob.txt is deleted. Only blob.txt is deleted.
Have you found a mitigation/solution?
Manually filter the lines before passing AzCopy the list of files. I think a quick mitigation would be simply to ignore lines that are / so people won't accidentally delete their blobs.

The expectation is incorrect. The blob storage is a different product and does not behave traditional filesystems behave, and clients (like azcopy) adhere to convention that the path separators in blob name are used as virtual directories. Please follow the convention  recommended here. Azcopy will consider any path ending with '/' as a directory.


Feature/page compare legend & fix for popovers (fixes #1513)

Adding a legend to the PageCompare tool which allows to show or hide rows based on attributes (ONLY_LEFT, ONLY_RIGHT, EQUAL & NOT_EQUAL) + fixing the popover issue described in the issue #1513

Coverage increased (+0.005%) to 40.888% when pulling 722171e5813ace210d075ac006088448a2e3ed16 on frederikmann:feature/page-compare-legend into 71e98ec2e5d8eb660e9f33f8b4ae2ab18c040e12 on Adobe-Consulting-Services:master.


Please invite me to the GitHub Community Organization

Name
Shruti Arora
Discord Username (if applicable)
shrutii#1672
Additional Context
I met Eddie on Twitter and was flattered by his skills and community work and how amazing a mentor he is . Eddie's reputation is certainly a factor. I would love to be a part of this growth and want to enter in the Open Source World .

Welcome to the community!


No default kong.conf on MacOS

So, I followed the installation steps for a Mac at this URL: https://getkong.org/install/osx/, and contrary to what the docs say about a default config file at /etc/kong/kong.conf.default, there exists none in my installation. In fact, there is no /etc/kong directory at all.
Steps To Reproduce

brew tap mashape/kong
brew install kong. Successfully installed.
ls /etc/kong. Result: No such file or directory

Additional Details & Logs

Kong version: 0.11.0
Kong debug-level startup logs : Irrelevant
Kong configuration (registered APIs/Plugins & configuration file): Doesn't exist.
Operating System: MacOS Seirra - 10.12.6

files installed with brew are going to be under /usr/local/Cellar/ on the filesystem. actually, in your case what you're looking for might be /usr/local/Cellar/kong/0.11.0/nginx-kong.conf

@Pinguwien's answer is correct, so I will close this issue. @sanjay-varanasi , if you have more support questions, please use any of these channels:

The main place for questions is gitter
Alternatively, there's also a mailing list, in case you prefer that format.

Thanks!


Dog food the action

Add a CI config where we use our own action :)

wouldn;t something like this work if you create a .github/workflows/release.yaml
...
      - name: Update changelog
        id: update_changelog
        uses: ./
        with:
          tag: ${{ github.ref_name }}
...

wouldn;t something like this work if you create a .github/workflows/release.yaml
...
      - name: Update changelog
        id: update_changelog
        uses: ./
        with:
          tag: ${{ github.ref_name }}
...

Probably, I just haven't gotten around to it! We need to also make a commit and stuff so it needs a slightly bigger workflow.


Are You Sure doesn't show alert when submitting a dirty form

Are You Sure gives the following error when submitting:
$dirtyforms is not defined.
Because of this there's no alert when submitting a dirty form

Issue is within are.you.sure plugin.
I've made a pull request on Are You Sure template, see: https://github.com/codedance/jquery.AreYouSure/pull/116

@mmarcos why did you reop


add include and exclude option in pint lint

we are using pint to scan a folder ,but this folder may contains  README.md ,which will lead to
values/blackbox-exporter/README.md:3 Fatal: found character that cannot start any token (yaml/parse)

a exclude or include parameter in pint lint command or parser config will help do the work.

You can pass a regex/glob to the lint command.
e.g. pint lint **/*.yaml

I believe this PR solves this issue

@LeoQuote is the above what you were thinking?

yes exactly


Rancher v2.0.7 upgrade re-adds cluster nodes by hostname

It would seem that after the v2.0.7 upgrade my cluster was reconfigured and the nodes were readded by hostname instead of IP like they were previously.
Rancher versions:
rancher/rancher v2.0.7
Docker version: (docker version,docker info preferred)
17.03-ce
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
uname -r
4.4.0-116-generic
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
vSphere VM
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Rancher-ha deployed with RKE
Steps to Reproduce:
Deploy v2.0.5/6 cluster and define the nodes in the cluster.yml with just the IP addresses, the cluster will then be created with all nodes having the name being their IP addresses. After the upgrade to v2.0.7 my cluster now shows 6 nodes instead of 3, with 3 of them Unavailable with a Kubelet stopped posting node status. message all of these are the nodes that were deployed originally and added to the cluster with their IP addresses as the name. The other 3 nodes are the same nodes however they were added to the cluster with their hostnames instead of IP addressses.
Results:
3 Unavailable nodes that are the same as the available nodes added to the cluster. The extra nodes that were added only show that they have a role of Worker and the other Unavialble nodes show they have a role of All
Here is the kubectl output:
> kubectl get nodes --kubeconfig kube_config_cluster.yml
NAME            STATUS     ROLES                      AGE       VERSION
<IP_ADDRESS>   NotReady   controlplane,etcd,worker   23d       v1.10.5
<IP_ADDRESS>   NotReady   controlplane,etcd,worker   23d       v1.10.5
<IP_ADDRESS>   NotReady   controlplane,etcd,worker   9d        v1.10.5
rancher-ha1     Ready      <none>                     19h       v1.10.5
rancher-ha2     Ready      <none>                     19h       v1.10.5
rancher-ha4     Ready      <none>                     19h       v1.10.5

Also it seems that now the cluster is being reported as an imported cluster in the Rancher GUI

@frenchtoasters i wasn't able to reproduce the problem, i can see the node still registered with the IP even after the upgrade to v2.0.7, i think what might happened is that you configured the hostname_override in the cluster.yml and upgraded, this will cause the kubelet to restart and re-register with the hostname instead, can you show us the cluster.yml before and after upgrade?

The only difference from before and after was that i added a cloud provider after the upgrade and before i noticed the issue above.
Before
nodes:
  - address: <IP_ADDRESS> # hostname or IP to access nodes
    user: ubuntu # root user (usually 'root')
    role: [controlplane,etcd,worker] # K8s roles for node
    ssh_key_path: ~/.ssh/rancher # path to PEM file
  - address: <IP_ADDRESS>
    user: ubuntu
    role: [controlplane,etcd,worker]
    ssh_key_path: ~/.ssh/rancher
  - address: <IP_ADDRESS>
    user: ubuntu
    role: [controlplane,etcd,worker]
    ssh_key_path: ~/.ssh/rancher

addons: |-
  ---
  kind: Namespace
  apiVersion: v1
  metadata:
    name: cattle-system
  ---
  kind: ServiceAccount
  apiVersion: v1
  metadata:
    name: cattle-admin
    namespace: cattle-system
  ---
  kind: ClusterRoleBinding
  apiVersion: rbac.authorization.k8s.io/v1
  metadata:
    name: cattle-crb
    namespace: cattle-system
  subjects:
  - kind: ServiceAccount
    name: cattle-admin
    namespace: cattle-system
  roleRef:
    kind: ClusterRole
    name: cluster-admin
    apiGroup: rbac.authorization.k8s.io
  ---
  apiVersion: v1
  kind: Secret
  metadata:
    name: cattle-keys-ingress
    namespace: cattle-system
  type: Opaque
  data:
    tls.crt:
    tls.key:
  ---
  apiVersion: v1
  kind: Secret
  metadata:
    name: cattle-keys-server
    namespace: cattle-system
  type: Opaque
  data:
    cacerts.pem:
  ---
  apiVersion: v1
  kind: Service
  metadata:
    namespace: cattle-system
    name: cattle-service
    labels:
      app: cattle
  spec:
    ports:
    - port: 80
      targetPort: 80
      protocol: TCP
      name: http
    - port: 443
      targetPort: 443
      protocol: TCP
      name: https
    selector:
      app: cattle
  ---
  apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    namespace: cattle-system
    name: cattle-ingress-http
    annotations:
      nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
  spec:
    rules:
    - host: rancher-ha.lab  # FQDN to access cattle server
      http:
        paths:
        - backend:
            serviceName: cattle-service
            servicePort: 80
    tls:
    - secretName: cattle-keys-ingress
      hosts:
      - rancher-ha.lab     # FQDN to access cattle server
  ---
  kind: Deployment
  apiVersion: extensions/v1beta1
  metadata:
    namespace: cattle-system
    name: cattle
  spec:
    replicas: 1
    template:
      metadata:
        labels:
          app: cattle
      spec:
        serviceAccountName: cattle-admin
        containers:
        - image: rancher/rancher:latest
          imagePullPolicy: Always
          name: cattle-server
          ports:
          - containerPort: 80
            protocol: TCP
          - containerPort: 443
            protocol: TCP
          volumeMounts:
          - mountPath: /etc/rancher/ssl
            name: cattle-keys-volume
            readOnly: true
        volumes:
        - name: cattle-keys-volume
          secret:
            defaultMode: 420
            secretName: cattle-keys-server

services:
  etcd:
    snapshot: true # enables recurring etcd snapshots
    creation: 6h0s # time increment between snapshots
    retention: 24h # time increment before snapshot purge

After:
nodes:
  - address: <IP_ADDRESS> # hostname or IP to access nodes
    user: ubuntu # root user (usually 'root')
    role: [controlplane,etcd,worker] # K8s roles for node
    ssh_key_path: ~/.ssh/rancher # path to PEM file
  - address: <IP_ADDRESS>
    user: ubuntu
    role: [controlplane,etcd,worker]
    ssh_key_path: ~/.ssh/rancher
  - address: <IP_ADDRESS>
    user: ubuntu
    role: [controlplane,etcd,worker]
    ssh_key_path: ~/.ssh/rancher

addons: |-
  ---
  kind: Namespace
  apiVersion: v1
  metadata:
    name: cattle-system
  ---
  kind: ServiceAccount
  apiVersion: v1
  metadata:
    name: cattle-admin
    namespace: cattle-system
  ---
  kind: ClusterRoleBinding
  apiVersion: rbac.authorization.k8s.io/v1
  metadata:
    name: cattle-crb
    namespace: cattle-system
  subjects:
  - kind: ServiceAccount
    name: cattle-admin
    namespace: cattle-system
  roleRef:
    kind: ClusterRole
    name: cluster-admin
    apiGroup: rbac.authorization.k8s.io
  ---
  apiVersion: v1
  kind: Secret
  metadata:
    name: cattle-keys-ingress
    namespace: cattle-system
  type: Opaque
  data:
    tls.crt:
    tls.key:
  ---
  apiVersion: v1
  kind: Secret
  metadata:
    name: cattle-keys-server
    namespace: cattle-system
  type: Opaque
  data:
    cacerts.pem:
  ---
  apiVersion: v1
  kind: Service
  metadata:
    namespace: cattle-system
    name: cattle-service
    labels:
      app: cattle
  spec:
    ports:
    - port: 80
      targetPort: 80
      protocol: TCP
      name: http
    - port: 443
      targetPort: 443
      protocol: TCP
      name: https
    selector:
      app: cattle
  ---
  apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    namespace: cattle-system
    name: cattle-ingress-http
    annotations:
      nginx.ingress.kubernetes.io/proxy-connect-timeout: "30"
      nginx.ingress.kubernetes.io/proxy-read-timeout: "1800"   # Max time in seconds for ws to remain shell window open
      nginx.ingress.kubernetes.io/proxy-send-timeout: "1800"   # Max time in seconds for ws to remain shell window open
  spec:
    rules:
    - host: rancher-ha.tom.future.lab  # FQDN to access cattle server
      http:
        paths:
        - backend:
            serviceName: cattle-service
            servicePort: 80
    tls:
    - secretName: cattle-keys-ingress
      hosts:
      - rancher-ha.tom.future.lab     # FQDN to access cattle server
  ---
  kind: Deployment
  apiVersion: extensions/v1beta1
  metadata:
    namespace: cattle-system
    name: cattle
  spec:
    replicas: 1
    template:
      metadata:
        labels:
          app: cattle
      spec:
        serviceAccountName: cattle-admin
        containers:
        - image: rancher/rancher:latest
          imagePullPolicy: Always
          name: cattle-server
          ports:
          - containerPort: 80
            protocol: TCP
          - containerPort: 443
            protocol: TCP
          volumeMounts:
          - mountPath: /etc/rancher/ssl
            name: cattle-keys-volume
            readOnly: true
        volumes:
        - name: cattle-keys-volume
          secret:
            defaultMode: 420
            secretName: cattle-keys-server

services:
  etcd:
    snapshot: true # enables recurring etcd snapshots
    creation: 6h0s # time increment between snapshots
    retention: 24h # time increment before snapshot purge

cloud_provider:
  name: vsphere
  vsphereCloudProvider:
    global:
      insecure-flag: true
      user<EMAIL_ADDRESS>      password:
      datacenter: MGMT
      working-dir: kubernetes
      server: <IP_ADDRESS>
  virtual_center:
    <IP_ADDRESS>: {}
  worksapce:
    server: <IP_ADDRESS>
    datacenter: MGMT
    folder: kubernetes
    default-datastore: mgmt-vms/mgmt-vms1

Let us know if this is still reproducible


Mozc removes consonants before generating the kana output.

https://bugs.chromium.org/p/chromium/issues/detail?id=681389
The above issue has animated GIFs to show the problem. Someone was able to recreate in the issue above.
The reason I am posting this issue upstream is that the issue has also started appearing in the LINE windows app running through Wine 2.0... Maybe LINE recently switched to use reactJS-native?... but either way it seems like it must be a problem with mozc.
I am using fcitx-mozc 2.17.2116.102+gitfd0f5b34+dfsg-1ubuntu1.1 which seems to be lagging behind this branch... If someone using the most recent version could check if this is still an issue or not, I would appreciate it. fcitx/mozc github has disabled issue creation, so I can not bring it up with them unless I make a fake pull request and just explain the issue there.

Steps to reproduce the problem:

Install Linux Mint 18.1 Cinnamon
in terminal, install Japanese IME with following command:
$ sudo apt install fcitx-mozc --install-recommends
Then activate by using:
$ im-config -n fcitx
Log out, then log in your Linux user.
You will notice keyboard icon on system tray.
Ctrl + Space to enable Japanese input (Orange icon with japanese symbol in it)
Visit Facebook, and place cursor in any text box, enable Japanese input and type in saigoni
Notice 最後い is shown instead of the actual proper 最後に (the kana is showing "i" instead of "ni")

retry 7 and 8 using firefox on the same system and notice it will show 最後に properly.
What is the expected behavior?
Do not auto-remove consonants after pressing space bar to select a kanji combination.
What went wrong?
it looks like the normal HTML input tags are OK, but the special reactJS generated text input for writing something on your feed or writing a comment on someone else's post is broken with Japanese input on Chrome only.

Chrome

Firefox

Also, I explain how to use with a US keyboard in the explanation but I am using an iBuffalo Japanese keyboard, if that makes a difference, (I doubt it)

Also hit by this problem, it's extremely annoying.

Hi, thank you for reporting.
Because this happens on a specific application, we think this is an issue of that application and/or an issue between IMF (i.e. fcitx) and the application. In this case, it could also be an issue of the web application.
Unfortunately, this kind of issue is not controllable from our implementation layer.


Keypair does not exist.

.yml
===============
driver:
name: ec2
aws_ssh_key_id: kitchen # key pair name
region: us-west-2 # region code of aws
availability_zone: us-west-2b # availability_zone of us-west
subnet_id: subnet-69716922 # subnet-id noted from above steps
instance_type: t2.micro # as it is free instance type
image_id: ami-0d1cd67c26f5fca19 # image id of ubuntu
security_group_ids: ["sg-8e4a56d1"]
The forwarded_port port feature lets you connect to ports on the VM guest via
localhost on the host.
see also: https://www.vagrantup.com/docs/networking/forwarded_ports.html
network:
- ["forwarded_port", {guest: 80, host: 8080}]
provisioner:
name: chef_zero
You may wish to disable always updating cookbooks in CI or other testing environments.
For example:
always_update_cookbooks: <%= !ENV['CI'] %>
always_update_cookbooks: true
product_name and product_version specifies a specific Chef product and version to install.
see the Chef documentation for more details: https://docs.chef.io/config_yml_kitchen.html
product_name: chef
product_version: 15
verifier:
name: inspec
transport:
ssh_key: "~/.ssh/kitchen.pem"
connection_timeout: 10
connection_retries: 3
username: ubuntu
platforms:

name: ubuntu-18.04
#- name: centos-7

suites:

name: default
run_list:

recipe[testkitchen::default]
verifier:
inspec_tests:

test/integration/default
attributes:
================

Hi,
Use ssh key as below and tray once
ssh_key: ./kitchen.pem

Hi,
Issue with your kitchen.yml file, send your kitchen.yml file to check.

check the pemfile path in kitchen.yml.

Kitchen.yml file: I tired both, it didn't work for me..
Just to mention:  vpc id showing the aws portal and what i get using the command "aws ec2 describe-vpcs" is different.
I took the book what it shows in cmd line, "subnet, vpc & Security group".

driver:
name: ec2
aws_ssh_key_id: kitchen # key pair name
region: us-west-2 # region code of aws
availability_zone: us-west-2b # availability_zone of us-west
subnet_id: subnet-69716922 # subnet-id noted from above steps
instance_type: t2.micro # as it is free instance type
image_id: ami-0d1cd67c26f5fca19 # image id of ubuntu
security_group_ids: ["sg-8e4a56d1"]
The forwarded_port port feature lets you connect to ports on the VM guest via
localhost on the host.
see also: https://www.vagrantup.com/docs/networking/forwarded_ports.html
network:
- ["forwarded_port", {guest: 80, host: 8080}]
provisioner:
name: chef_zero
You may wish to disable always updating cookbooks in CI or other testing environments.
For example:
always_update_cookbooks: <%= !ENV['CI'] %>
always_update_cookbooks: true
product_name and product_version specifies a specific Chef product and version to install.
see the Chef documentation for more details: https://docs.chef.io/config_yml_kitchen.html
product_name: chef
product_version: 15
verifier:
name: inspec
transport:
ssh_key: "/kitchen.pem"
connection_timeout: 10
connection_retries: 3
username: ubuntu
platforms:

name: ubuntu-18.04
#- name: centos-7

suites:

name: default
run_list:

recipe[testkitchen::default]
verifier:
inspec_tests:

test/integration/default
attributes:
====================

Please change the driver to ec2

Please relook at https://directdevops.blog/2019/04/02/test-kitchen-setup-with-aws/

Hello Team,
Thank you for the replies, the above mentioned issue got resolved, I'm looking at "east-us" region in AWS portal. later changed to "west us 2", now vpc, subnet $ SG are matched and successfully executed for ubuntu.. installed tomcat also but only for ubuntu..
When  i tried to do for centos. got the below error, look like image problem "ami for centos".

Can anyone help me with this.. Thank you..

try to launch manually for centos ami once and copy that ami and use in your kitchen.yml

Hi Manikanta,
Thank you for the update,
I tired to do the same, but didn't work out both have same  "ami-0bc06212a56393ee1"

@srmanikanta Try to take remote connection and look into issue

HI surendramannem,
Try the below command to get AMI Image of centos for your current region and try to use that ami to install.
aws ec2 describe-images --owners 'aws-marketplace' --filters 'Name=product-code,Values=aw0evgkw8e5c1q413zgy5pjce' --query 'sort_by(Images, &CreationDate)[-1].[ImageId]' --output 'text'

Sure , will try that. Thank you for the help.
Regards,
Surendra Mannem.
On Wed, 22 Apr 2020 at 12:46 PM, rpkoya<EMAIL_ADDRESS>wrote:

HI surendramannem,
Try the below command to get AMI Image of centos for your current region
and try to use that ami to install.
aws ec2 describe-images --owners 'aws-marketplace' --filters
'Name=product-code,Values=aw0evgkw8e5c1q413zgy5pjce' --query
'sort_by(Images, &CreationDate)[-1].[ImageId]' --output 'text'
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/QT-DevOps/DevOpsIssues/issues/813#issuecomment-617597419,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AM6J3CJEMNTHY7CECOHK5ATRN2KVFANCNFSM4MK7S77A
.


[ios]Further investigate iOS 18.2 WebView behavior

This is a follow-up for the original issue here
On iOS 18.2 the web view's gesture recognizer likely cached the old state of our FlutterDelayingGestureRecognizer (see PR description here).
The current workaround doesn't address a problem where a platform view receives the gesture even when it shouldn't have. (See discussion here)
Also this is potentially a bug on iOS, so we may wanna create a reproducible project in UIKit and file the radar with Apple.

So there's still an opportunity for asking Apple to fix this issue, and we go straight to upgrade iOS instead of upgrading Flutter sdk, right? Because upgrading Flutter SDK for some huge projects is a tough job. Perhaps solving this problem through Apple is the best solution for everyone.


New onEnterFrame animation sample

Simple onEnterFrame animation handling sample.
Concepts introduced:

onEnterFrame animation
multiple objects
external class
random number
movement constraints
pool of objects

Closing this to get it better with cross-platform + next compatibility


Partner application communication ports for office 365

When setting up partner application and enabling OAuth for Office365, what ports needs to be open from Front End server to Echange online and Sharepoint online and microsoft sts? is port 443 as destination port enough?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c5164207-7822-cf54-717e-6216e0627ebd
Version Independent ID: 786f5413-3660-06eb-484f-8d5758d3ec59
Content: Port and protocol requirements for servers
Content Source: Skype/SfbServer/plan-your-deployment/network-requirements/ports-and-protocols.md
Product: skype-for-business-itpro
GitHub Login: @jambirk
Microsoft Alias: jambirk

@hansarh Thank you for this feedback
I want to make sure we get you the answers that you need. I am going to get this over to the Teams/Skype for Business team.
The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Andrea,
The article is specifically about on-premise implementations only. The office 365/ skype for business online implementation is a whole other ball of wax (which we already link to), and the hybrid implementation is described in the hybrid topics. For DNS, they need to whitelist appropriately for both on-prem and online.
I don’t agree that much if anything needs to be done here. Exchange OL integration is covered in its own topic, this is not the place to be doing it.

James Birkinshaw     |    Skype for Business ITPro Content
From: AndreaBarr<EMAIL_ADDRESS>Sent: Tuesday, October 16, 2018 1:21 PM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness<EMAIL_ADDRESS>Cc: James Birkinshaw<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Partner application communication ports for office 365 (#869)
@hansarhhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhansarh&data=02|01|jambirk%40microsoft.com|44d8cc269db34d19133d08d633a4f579|72f988bf86f141af91ab2d7cd011db47|1|0|636753180921677096&sdata=Xi2cd3mbmou3TbZMeC63gdgvclWX5HAIauyTy3qPSNg%3D&reserved=0 Thank you for this feedback
I want to make sure we get you the answers that you need. I am going to get this over to the Teams/Skype for Business team.
The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fissues%2F869%23issuecomment-430386314&data=02|01|jambirk%40microsoft.com|44d8cc269db34d19133d08d633a4f579|72f988bf86f141af91ab2d7cd011db47|1|0|636753180921687108&sdata=LbIvaYKq8%2BGgaH%2BkyCyU4QpnwtScIYsZ%2BXUwbf4%2Blq4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAf-jxeek-5dw8LMGAdKEJ8Mi-3ByGMb8ks5ulj_JgaJpZM4XXEVS&data=02|01|jambirk%40microsoft.com|44d8cc269db34d19133d08d633a4f579|72f988bf86f141af91ab2d7cd011db47|1|0|636753180921697121&sdata=SQWLSNj0WpJFWw%2BSrlZ%2Bl6%2FOaCwWxjK35ThoiOXNJPk%3D&reserved=0.

I've added a link to the hybrid port and protocol discussion, alongside the existing link to online O365 implementations.

@hansarh It looks like James has addressed your inquiry. I am going to close this issue. If the issue is not resolved please re-open this issue.


Bump web-ui version to 1.9.0-SNAPSHOT

Why are the changes needed?

Previous version bumping missed web-ui, see details #5273
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Was this patch authored or co-authored using generative AI tooling?

No.

Thanks, merged to master


Timeseries plot style

An update to the comparer plotter such that it takes a style and a color input. I wanted to also allow for color input, since this is actually the main reason why I started the issue #463: I want to use my own colors to match my other plots. The style input is just a bonus from my point of view :)
Design decisions:

The user can only pass one of the two; either color OR style
If none are passed, the default colors are used.
Inputs can be passed as list of strings or as a single string. If a single string is passed but more than one model result is in the comparer, an error is raised. If len(list) < num_models an error is also raised.
If len(color) > num_models: the first color is used for the observations. I am unsure whether this is the best way to do it, since there might be cases, where I just have a large list of colors that I pass to all of my plots regardless of the number of models... On the other hand, allowing the user to choose the observation colors is also useful in case of duplicate colors (default obs color is black, and maybe I want one of the lines to be black too?)

Example 1: giving a color input
# Given a comparer:
cmp = create_comparer()
# Pass a color input to the plot.timeseries() method
ax = cmp.plot.timeseries(color=["red", "blue"])
plt.show()

This code yields the following plot:

Example 2: also specifying the color of the observation points
Above, the default color of the observations is black. If we want them to be e.g. green instead, we pass it as the first color.
# Pass a color input to the plot.timeseries() method
ax = cmp.plot.timeseries(color=["green","red", "blue"])
plt.show()

This yields the following plot:

Example 3: giving a style input
We can also pass a style input instead
# Pass a color input to the plot.timeseries() method
ax = cmp.plot.timeseries(style=["r-.", "b--"])
plt.show()

@FrejaTerpPetersen for the benefit of the interested reader... could you please include some sample code and screenshots of the new functionality in this description above. Visuals are easy to grasp, when browsing around.

Sure thing - I updated the description

closes #463


Deletion of Linked List

Deleting elements of singly linked list at starting ending or middle position c++ code

i can do it in c python java too

@Kumar-laxmi


add mcause shifts and values

also add the values for the exception and interrupt causes, given in table 8.6.1
Deadline: 6th April 2022

https://github.com/mmoizhussain/riscv-sbi-basic/pull/22

https://github.com/mmoizhussain/riscv-sbi-basic/pull/32


useless

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 1606e33f-a0b8-08ca-a071-d219842e8994
Version Independent ID: 0064c141-bae1-b963-a00d-05cc51fdaa69
Content: PySpark interactive environment with Azure HDInsight Tools
Content Source: articles/hdinsight/set-up-pyspark-interactive-environment.md
Service: hdinsight
GitHub Login: @yeturis
Microsoft Alias: sairamyeturi

I try this way but useless, still note me PySpark installation error. Please see moreDetails

@Killerkk
Thanks for your feedback! We will investigate and update as appropriate.

@Killerkk
Thank you for bringing this to our attention.
Here are some general troubleshooting steps you can try

Ensure you have the right Python version (3.5 or later) for PySpark.
Confirm you have Java 8 or later installed.
Check your PySpark version with pyspark --version.
Verify your environment variables with echo $SPARK_HOME.
If issues persist, consider reinstalling PySpark.
For an issue like this, I'd recommend you create a support ticket since the support team will be able to respond much more quickly and have a conversation with you to figure out what could be going on.


pub black mod - perf error

Tracking issue to fix black mod as pub for testing n next algos.
https://github.com/rust-lang/rust/issues/128730

https://github.com/rust-lang/rust/issues/128730
tracking


Remove Module

Is there a way  one  can remove the prebuilt modules?

You can turn them off by disabling them in the config, however that doesn't remove the migrations.


'RecordARDelegate' is unavailable: cannot find Swift declaration for this protocol

I followed the first setup instructions and when I did so it ran fine on my physical device, however, its not able to complile on the simulators. How can I work around this problem as I still need to test other aspects of my app on the simulator. Thanks

@Cez95 can you clarify what error you're receiving when you run your application on a simulator?

Yea, the error I get is 'RecordARDelegate' is unavailable: cannot find Swift declaration for this protocol. Its a runtime error and when I run the app on my physical device it disapears. Only shows when I have a simulator as the deployent target

Unfortunately, none of these solutions work. The problem continues to persist for simulators. Will there be a cocoa pod for this project available in the future?

@Cez95, yes I'm currently working on it under the pkg-manager branch.
However, in the mean time I'd recommend installing the framework by dragging the ARVideoKit.xcodeproj into your project.

@Cez95, you can now install ARVideoKit using Cocoapods by doing the following:

add this line to your Podfile:

pod 'ARVideoKit', :git => 'https://github.com/AFathi/ARVideoKit.git'

then install

$ pod install

This is perfect! I was still having issues with inserting the framework but this changes the game! Thank you!
Sent from my iPhone

On Jul 8, 2018, at 6:42 PM, Ahmed Bekhit<EMAIL_ADDRESS>wrote:
@Cez95, you can now install ARVideoKit using Cocoapods by doing the following:
add this line to your Podfile:
pod 'ARVideoKit', :git => 'https://github.com/AFathi/ARVideoKit.git'
then install
$ pod install
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Release version 0.0.4

What's Changed

Use readFile instead of openTextDocument for regex test case discovery by @mnoah1 in https://github.com/uber/vscode-bazel-bsp/pull/13
Add getting started docs by @mnoah1 in https://github.com/uber/vscode-bazel-bsp/pull/12
Adjust notifications during sync by @mnoah1 in https://github.com/uber/vscode-bazel-bsp/pull/14
Show setup message when no targets returned from sync by @mnoah1 in https://github.com/uber/vscode-bazel-bsp/pull/15
Adjustments to Python test discovery by @mnoah1 in https://github.com/uber/vscode-bazel-bsp/pull/17
Add results from parameterized tests to parent by @mnoah1 in https://github.com/uber/vscode-bazel-bsp/pull/16


Cannot reopen panel once closed in angr management.

Description
after closing the control panel via the x button or Toggle Panel menu option, neither the Start binsync or toggle panel menu options will not reopen the panel.
Steps to reproduce the bug
In angr management enable binsync, then open the panel via toggle panel or start binsync, close via toggle panel or close button, then attempt to reopen with the menu options, and it will not reopen.
Environment
python 3.10, binsync 4.2.1, angr management 9.2.106
Additional context
No response

Hmmm I see. I think someone else reported this issue in the past and dropped investigation.
@frqmod any chance I can get you to emerge from the woodwork and debug this, since you own this code 😁?


Error clicking links on nixos installed with flatpak

Clicking any links returns this:
thread 'main' panicked at 'Error to open this url: GString(Native(Some("https://example.com")))', src/views/webview.rs:48:31

Since the error is being ignored, we don't really know what's happening: https://github.com/gigitux/youpforwhatsapp/blob/54b225709119303a64d792ccb201c9d8243bbdfe/src/views/webview.rs#L49


KeyID support for RFC7517

Hi!
I've created PR in Centrifigo which uses your package as a dependency. What I'm trying to add is support for JWKS where encryption keys are rotating and to fetch appropriate public key kid header is used. See RFC
There is a problem with current Header which doesn't contain KeyID property. Previously it was presented in https://github.com/centrifugal/centrifugo/pull/410/.
I can create PR for that.

Hi @danikarik thank you for the PR. I'm aware of this issue in Centrifugo, so big thank you for fixing it.
There is one little problem....I've merged things to the master on a way to v4. Today I'll try to cleanup a bit and I might ask you to rebase your change (probably without any conflict). Hopefully you'll understand my point :)

Hi @danikarik thank you for the PR. I'm aware of this issue in Centrifugo, so big thank you for fixing it.
There is one little problem....I've merged things to the master on a way to v4. Today I'll try to cleanup a bit and I might ask you to rebase your change (probably without any conflict). Hopefully you'll understand my point :)


Add interpolation documentation

This adds a section to the existing topic on searching for addresses, which we wrote for the libpostal integration. I think this is really the only location where we need to discuss interpolation, as I didn't really see a specific place for it in search or search/structured.

Adds section on interpolation
Adds API responses on accuracy/match_type to add interpolation
Adds a random example

I wasn't exactly clear on whether we use straight line interpolation at all, or if it's always the "accentuate the curves" way because it considers the street geometry (which is how I wrote it).
Take a look @dianashk @missinglink @orangejulius! Thanks!

Thanks for the great reviews, @dianashk!
I believe I've gotten all of them but the discussion of straight-line interpolation. If we don't use that in any form, perhaps we remove that paragraph entirely so it doesn't cause confusion.

Thanks for making the updates. I think it's good to explain what straight line interpolation means because it's the basis of what we do as well. I've you've explained the shortcoming it would be good to follow up with explaining how we improve upon that. We effectively break a curved street into smaller straight line parts and employ the straight line technique in those. That should be enough detail to be useful and not too technical.


GeneView - Two seperate columns for gene accessions and gene names

Modify the GeneView table to show Gene Accessions and Gene Names in separate columns

Gene Name now displayed, if differs from ACCESSION, to avoid duplication of large entries in GeneView table, especially for Wheat. Help text explaining this also added to column header tooltip (mouseover)

FYI, commit: https://github.com/Rothamsted/knetminer/pull/218/commits/80ac92d063185919d2de1db9d92b667f0750664a