IntelliSense doesn't work in Insiders for basic ipynb and miniconda

Environment data

VS Code version:

Version: 1.57.0-insider
Commit: a62df5d6c53e844bfdc50694f943c3f34b6ff50e
Date: 2021-06-03T17:36:36.265Z (7 hrs ago)
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 20.5.0

Jupyter Extension version (available under the Extensions sidebar): v2021.6.902307158
Python Extension version (available under the Extensions sidebar): v2021.6.850516022-dev
Python and/or Anaconda version: Python 3.8.3 64-bit (base: conda)
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): n/a
Jupyter server running: Local

Expected behaviour
IntelliSense just works.
Actual behaviour
No IntelliSense in a basic ipynb.
Steps to reproduce:

Started from fresh VS Code install, Insiders and Release (with native notebooks enabled)
Installed extensions
Opened up a minimal Notebook
Set interpreter to miniconda installation
Tried to get arguments for pd.read_csv(…

Insiders: Broken
Release: Works
Logs
Using Pylance:
Error 2021-06-03 18:27:48: Live Notebook not available for file:///Users/digitarald/repos/data/feedback/anaylsis.ipynb

Using Jedi:
Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process Traceback (most recent call last):

Warn 2021-06-03 18:26:15: StdErr from Kernel Process Traceback (most recent call last):

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/kernelbase.py", line 268, in dispatch_shell

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/kernelbase.py", line 268, in dispatch_shell

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/kernelbase.py", line 268, in dispatch_shell

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     yield gen.maybe_future(handler(stream, idents, msg))

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     yield gen.maybe_future(handler(stream, idents, msg))

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     yield gen.maybe_future(handler(stream, idents, msg))

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/tornado/gen.py", line 762, in run

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/tornado/gen.py", line 762, in run

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/tornado/gen.py", line 762, in run

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     value = future.result()

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     value = future.result()

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     value = future.result()

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/tornado/gen.py", line 234, in wrapper

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/tornado/gen.py", line 234, in wrapper

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/tornado/gen.py", line 234, in wrapper

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     yielded = ctx_run(next, result)

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     yielded = ctx_run(next, result)

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     yielded = ctx_run(next, result)

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/kernelbase.py", line 583, in complete_request

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/kernelbase.py", line 583, in complete_request

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/kernelbase.py", line 583, in complete_request

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     matches = yield gen.maybe_future(self.do_complete(code, cursor_pos))

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     matches = yield gen.maybe_future(self.do_complete(code, cursor_pos))

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     matches = yield gen.maybe_future(self.do_complete(code, cursor_pos))

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/ipkernel.py", line 360, in do_complete

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/ipkernel.py", line 360, in do_complete

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/ipkernel.py", line 360, in do_complete

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     return self._experimental_do_complete(code, cursor_pos)

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     return self._experimental_do_complete(code, cursor_pos)

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     return self._experimental_do_complete(code, cursor_pos)

Info 2021-06-03 18:26:15: Widget Coordinator received IPyWidgets_msg_received
Info 2021-06-03 18:26:15: Widget Coordinator received IPyWidgets_iopub_msg_handled
Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/ipkernel.py", line 385, in _experimental_do_complete

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/ipkernel.py", line 385, in _experimental_do_complete

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/ipykernel/ipkernel.py", line 385, in _experimental_do_complete

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     completions = list(_rectify_completions(code, raw_completions))

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     completions = list(_rectify_completions(code, raw_completions))

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     completions = list(_rectify_completions(code, raw_completions))

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 484, in rectify_completions

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 484, in rectify_completions

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 484, in rectify_completions

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     completions = list(completions)

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     completions = list(completions)

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     completions = list(completions)

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1818, in completions

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1818, in completions

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1818, in completions

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     for c in self._completions(text, offset, _timeout=self.jedi_compute_type_timeout/1000):

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     for c in self._completions(text, offset, _timeout=self.jedi_compute_type_timeout/1000):

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     for c in self._completions(text, offset, _timeout=self.jedi_compute_type_timeout/1000):

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1861, in _completions

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1861, in _completions

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1861, in _completions

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     matched_text, matches, matches_origin, jedi_matches = self._complete(

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     matched_text, matches, matches_origin, jedi_matches = self._complete(

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     matched_text, matches, matches_origin, jedi_matches = self._complete(

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 2029, in _complete

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 2029, in _complete

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 2029, in _complete

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     completions = self._jedi_matches(

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     completions = self._jedi_matches(

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     completions = self._jedi_matches(

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1373, in _jedi_matches

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1373, in _jedi_matches

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/IPython/core/completer.py", line 1373, in _jedi_matches

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     interpreter = jedi.Interpreter(

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     interpreter = jedi.Interpreter(

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     interpreter = jedi.Interpreter(

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/jedi/api/__init__.py", line 725, in __init__

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/jedi/api/__init__.py", line 725, in __init__

Warn 2021-06-03 18:26:15: StdErr from Kernel Process   File "/Users/digitarald/miniconda3/lib/python3.8/site-packages/jedi/api/__init__.py", line 725, in __init__

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr:     super().__init__(code, environment=environment,

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process     super().__init__(code, environment=environment,

Warn 2021-06-03 18:26:15: StdErr from Kernel Process     super().__init__(code, environment=environment,

Info 2021-06-03 18:26:15: Python Daemon (pid: 27914): write to stderr: TypeError: __init__() got an unexpected keyword argument 'column'

Warn 2021-06-03 18:26:15: Kernel 27914 as possibly died, StdErr from Kernel Process TypeError: __init__() got an unexpected keyword argument 'column'

Warn 2021-06-03 18:26:15: StdErr from Kernel Process TypeError: __init__() got an unexpected keyword argument 'column'

By 'Release' do you mean VS Code stable 1.56.2?
We just fixed an issue with language server support for Python notebooks today: https://github.com/microsoft/vscode-python/pull/16385. That fix is in the Python extension. If you install this build of the Python extension, does IntelliSense work for you?  https://github.com/microsoft/vscode-python/suites/2904962837/artifacts/65133411
FWIW, installing that build of the Python extension, and the latest Insiders and Jupyter extension build off the Marketplace, works for me:

If that doesn't just work, could you please let me know if you have a Python interpreter selected (using the Python: Select Interpreter command from the command palette, or the interpreter selector in the bottom left, after switching focus away from a notebook)? That is required for IntelliSense to work (as the language server needs to know which Python environment to evaluate module imports against).

We just fixed an issue with language server support for Python notebooks today: microsoft/vscode-python#16385. That fix is in the Python extension. If you install this build of the Python extension, does IntelliSense work for you? https://github.com/microsoft/vscode-python/suites/2904962837/artifacts/65133411

Yes, that build works for me!

Perfect. I'll resolve this issue as a duplicate of https://github.com/microsoft/vscode-jupyter/issues/6108. Thanks for the confirmation and for filing a bug @digitarald 😊


[Beta 3] Soft crash with Minecolonies

#https://github.com/Minecolonies/minecolonies/issues/2143
More details at the linked issue, but essentially the instance will hang in errored server state if trying to update a world to the more recent versions of Minecolonies with TC6b3 installed, producing the following crashlog: https://pastebin.com/gXrRci3D
Minecolonies dev thinks it's on the TC end to fix, hence the cross-report.
Versions:
Minecolonies: 1.10.2 version 0.9.XXXX (any newer than 0.8.5086)
Forge <IP_ADDRESS>1
Thaumcraft 6.0 Beta3
(also, might want to update the issues link on curseforge to point to this tracker rather than the TC5 one)

This problems seems to be with FoamFix, not TC. It is attempting to assign invalid values to the crystal metadata.


after .10 upgrade app does not start any more

Hello,
I am receiving following error on starting my app:
[nuxt.js] Cannot load components TypeError: Cannot read property 'getters' of undefined
    at _callee$ (eval at <anonymous>

I use vuex and set some getters but I rechecked the getters existence and but I have no idea where this error comes from. Before the upgrade everything worked as expected. Any ideas?

My main concern is: I have no idea how to debug this error. I can't set any breakpoint to see which components is breaking because its inside of nuxt bundle:
[nuxt.js] Cannot load components TypeError: Cannot read property 'getters' of undefined
    at _callee$ (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:367:1), <anonymous>:15:34)
    at tryCatch (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:672:1), <anonymous>:64:40)
    at Generator.invoke [as _invoke] (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:672:1), <anonymous>:299:22)
    at Generator.prototype.(anonymous function) [as next] (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:672:1), <anonymous>:116:21)
    at step (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:367:1), <anonymous>:6:191)
    at eval (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:367:1), <anonymous>:6:437)
    at eval (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:367:1), <anonymous>:6:99)
    at eval (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:367:1), <anonymous>:32:21)
    at promisify (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:346:1), <anonymous>:95:15)
    at promiseSeries (eval at <anonymous> (http://localhost:3333/_nuxt/nuxt.bundle.b0190671b3eaf9cf79ab.js:346:1), <anonymous>:76:10)

It should be fixed with the 0.10.2 release. Sorry about this @dohomi

great all back! thanks for this quick fix and the highly improved released!


ivpn-service: 3.10.15 -> 3.13.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ivpn/desktop-app/releases.
meta.description for ivpn-service is: Official IVPN Desktop app
meta.homepage for ivpn-service is: https://www.ivpn.net/apps
meta.changelog for ivpn-service is: https://github.com/ivpn/desktop-app/releases/tag/v3.11.15
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.11.15 with grep in /nix/store/78zvlmjkpvwryx9xyn0ig7gb19nm05mj-ivpn-service-3.11.15
found 3.11.15 in filename of file in /nix/store/78zvlmjkpvwryx9xyn0ig7gb19nm05mj-ivpn-service-3.11.15

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
ivpn
ivpn-service

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/78zvlmjkpvwryx9xyn0ig7gb19nm05mj-ivpn-service-3.11.15 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/78zvlmjkpvwryx9xyn0ig7gb19nm05mj-ivpn-service-3.11.15
ls -la /nix/store/78zvlmjkpvwryx9xyn0ig7gb19nm05mj-ivpn-service-3.11.15/bin

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

1 package failed to build:

ivpn

1 package built:

ivpn-service

Maintainer pings
cc @urandom2 @AtaraxiaSjel for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ivpn/desktop-app/releases.
meta.description for ivpn-service is: Official IVPN Desktop app
meta.homepage for ivpn-service is: https://www.ivpn.net/apps
meta.changelog for ivpn-service is: https://github.com/ivpn/desktop-app/releases/tag/v3.13.4
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.13.4 with grep in /nix/store/y1c0abg1qhl4gxk5jgva2ys5i9xx43sh-ivpn-service-3.13.4
found 3.13.4 in filename of file in /nix/store/y1c0abg1qhl4gxk5jgva2ys5i9xx43sh-ivpn-service-3.13.4

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
ivpn
ivpn-service

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/y1c0abg1qhl4gxk5jgva2ys5i9xx43sh-ivpn-service-3.13.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/8a7527c45c1b9d0c582a58beac563d84e218eac6#ivpn-service

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/y1c0abg1qhl4gxk5jgva2ys5i9xx43sh-ivpn-service-3.13.4
ls -la /nix/store/y1c0abg1qhl4gxk5jgva2ys5i9xx43sh-ivpn-service-3.13.4/bin

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

1 package failed to build:

ivpn

1 package built:

ivpn-service

Maintainer pings
cc @urandom2 @AtaraxiaSjel for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ivpn/desktop-app/releases.
meta.description for ivpn-service is: Official IVPN Desktop app
meta.homepage for ivpn-service is: https://www.ivpn.net/apps
meta.changelog for ivpn-service is: https://github.com/ivpn/desktop-app/releases/tag/v3.14.2
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.14.2 with grep in /nix/store/gm8z99i6bc0kmiri565s6vy0a4snqa4w-ivpn-service-3.14.2
found 3.14.2 in filename of file in /nix/store/gm8z99i6bc0kmiri565s6vy0a4snqa4w-ivpn-service-3.14.2

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
ivpn
ivpn-service

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/gm8z99i6bc0kmiri565s6vy0a4snqa4w-ivpn-service-3.14.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/c7f120c108face5e83b9c4bedc75c5f4c54e4dd8#ivpn-service

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/gm8z99i6bc0kmiri565s6vy0a4snqa4w-ivpn-service-3.14.2
ls -la /nix/store/gm8z99i6bc0kmiri565s6vy0a4snqa4w-ivpn-service-3.14.2/bin

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

1 package failed to build:

ivpn

1 package built:

ivpn-service

Maintainer pings
cc @urandom2 @AtaraxiaSjel for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ivpn/desktop-app/releases.
meta.description for ivpn-service is: Official IVPN Desktop app
meta.homepage for ivpn-service is: https://www.ivpn.net/apps
meta.changelog for ivpn-service is: https://github.com/ivpn/desktop-app/releases/tag/v3.14.12
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.14.12 with grep in /nix/store/jwhinhy1hfi7i5mmfn14jdkn1zsrcrvj-ivpn-service-3.14.12
found 3.14.12 in filename of file in /nix/store/jwhinhy1hfi7i5mmfn14jdkn1zsrcrvj-ivpn-service-3.14.12

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
ivpn
ivpn-service

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/jwhinhy1hfi7i5mmfn14jdkn1zsrcrvj-ivpn-service-3.14.12 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/b03f5546d55a3770b848b3894447f3a5443d635e#ivpn-service

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/jwhinhy1hfi7i5mmfn14jdkn1zsrcrvj-ivpn-service-3.14.12
ls -la /nix/store/jwhinhy1hfi7i5mmfn14jdkn1zsrcrvj-ivpn-service-3.14.12/bin

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

1 package failed to build:

ivpn

1 package built:

ivpn-service

Maintainer pings
cc @urandom2 @AtaraxiaSjel for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/ivpn/desktop-app/releases.
meta.description for ivpn-service is: Official IVPN Desktop app
meta.homepage for ivpn-service is: https://www.ivpn.net/apps
meta.changelog for ivpn-service is: https://github.com/ivpn/desktop-app/releases/tag/v3.14.17
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.14.17 with grep in /nix/store/zz9dbn7pigmpkhfgkmlwvmpi92nf18r3-ivpn-service-3.14.17
found 3.14.17 in filename of file in /nix/store/zz9dbn7pigmpkhfgkmlwvmpi92nf18r3-ivpn-service-3.14.17

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

ivpn
ivpn-service

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zz9dbn7pigmpkhfgkmlwvmpi92nf18r3-ivpn-service-3.14.17 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/f3ca3caedcfe94d153dff8bfff859d88c2d5fe1f#ivpn-service

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zz9dbn7pigmpkhfgkmlwvmpi92nf18r3-ivpn-service-3.14.17
ls -la /nix/store/zz9dbn7pigmpkhfgkmlwvmpi92nf18r3-ivpn-service-3.14.17/bin

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

1 package failed to build:

ivpn

1 package built:

ivpn-service

Maintainer pings
cc @urandom2 @AtaraxiaSjel for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.


Unclear instructions

Item 2 in the Installation steps says, "Run the tika server:"
java -jar <path_to_nlm_ingestor>/jars/tika-server-standard-nlm-modified-2.9.2_v2.jar
What is path_to_nlm_ingestor?

Hello @Denis-Kazakov, You will have to checkout/clone this repo on your local machine. You can find the tika-server-standard-nlm-modified-2.9.2_v2.jar which is located in this repo here.


Issue 174: Fix wchar buffers pointing at the wrong memory locations

For WCHAR fields, buffer offsets were calculated incorrectly as the space for the null-terminator was added after multiplication of the ColumnSize with the row index, instead of being added to the ColumnSize before.
Instead of wrapping the equation in parens, I decided to use bufferSize, which includes space for the null-terminator and is stored as bytes instead of 2-byte SQLWCHAR units, and simply divide it by sizeof(SQLWCHAR). This makes it clearly what is actually happening (offsetting the memory location by the size of the buffer * the row you are trying to get from the buffer). It also matches the logic for SQLCHAR immediate below (except for the dividing by sizeof part).
Fixes #174
Signed-off-by: Mark Irish<EMAIL_ADDRESS>

Since its column-wise binding, I sort of when off here: https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqlbindcol-function?view=sql-server-ver15#column-wise-binding
Particularly part 3 where the value bound with SQLBindCol is:

BufferLength is the size of a single element in the data buffer array.

I don't think I need to use the full size of the actual buffer once I bind, so I calculate it, use it, then don't store it. Definitely a little weird... but it is what it is.

Yeah, I certainly didn't notice it when I reviewed it before and it would make perfect sense if it was only binding a single row.


summary.add_activation_summary not working?

In mnist-convnet example, if I want to use summary.add_activation_summary, I simply add
summary.add_activation_summary(logits)
at line96,
but it raised an error saying that the input placeholders are empty.
Seems like summary.add_activation_summary should be implemented inside the inference_runner but is not?

Often a summary tensor doesn't require input tensors to evaluate (e.g. summary of variables). But in this case the summary requires input tensors to evaluate. Then you'll face two options:

evaluate on a new input data taking from the dataflow
evaluate together with training (i.e. reuse a datapoint to evaluate the summary)
In most applications they don't make much difference, but in certain cases the difference is important.

To use 1., you can simply replace SimpleTrainer with QueueInputTrainer. Because of how tensorflow queue works, the queue will automatically produce the next data when it is needed.
To use 2., you can explicitly tell the trainer that the summary callback should be run together with training. This is done by overriding the default call back list:
        extra_callbacks=[
            MovingAverageSummary(),
            ProgressBar(),
            MergeAllSummaries(run_alone=True)
        ],

A bug was introduced lately. It always tries to evaluate the summary tensor in a separate sess.run call, which leads to error because the call may depend on feed_dict.


Exception: _debugLifecycleState was called on null

With lastest update to Flutter I've started getting exceptions thrown when switching between tabs with scroll views in them. I only get the exception when switching between two non-adjacent tabs. When switching between tabs next to each other everything is always fine.
If I'm doing something wrong, a more helpful error message would be great.
Steps to Reproduce
Please tell us what you were doing and what went wrong. If you are running flutter tools from the command line, please try adding the -v or --verbose option to gather more information.
If the problem is with your application's rendering, please attach a screenshot and any relevant source code.
If you are getting an exception in the logs, and your code is implicated in the first few frames, then please include the source code for the functions involved.
Logs
══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
The following NoSuchMethodError was thrown during performLayout():
The getter '_debugLifecycleState' was called on null.
Receiver: null
Tried calling: _debugLifecycleState
When the exception was thrown, this was the stack:
#0      Object._noSuchMethod (dart:core-patch/object_patch.dart:43)
#1      Object.noSuchMethod (dart:core-patch/object_patch.dart:47)
#2      _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1635:20)
#3      _SliverPersistentHeaderElement.visitChildren (package:flutter/src/widgets/sliver_persistent_header.dart:143:12)
#4      _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#5      ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#6      _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#7      ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#8      _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#9      MultiChildRenderObjectElement.visitChildren (package:flutter/src/widgets/framework.dart:4412:16)
#10     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#11     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#12     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#13     SingleChildRenderObjectElement.visitChildren (package:flutter/src/widgets/framework.dart:4312:14)
#14     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#15     SingleChildRenderObjectElement.visitChildren (package:flutter/src/widgets/framework.dart:4312:14)
#16     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#17     SingleChildRenderObjectElement.visitChildren (package:flutter/src/widgets/framework.dart:4312:14)
#18     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#19     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#20     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#21     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#22     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#23     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#24     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#25     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#26     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#27     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#28     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#29     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#30     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#31     ComponentElement.visitChildren (package:flutter/src/widgets/framework.dart:3418:14)
#32     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#33     SingleChildRenderObjectElement.visitChildren (package:flutter/src/widgets/framework.dart:4312:14)
#34     _InactiveElements._deactivateRecursively (package:flutter/src/widgets/framework.dart:1638:13)
#35     _InactiveElements.add (package:flutter/src/widgets/framework.dart:1647:7)
#36     Element.deactivateChild (package:flutter/src/widgets/framework.dart:2777:29)
#37     Element.updateChild (package:flutter/src/widgets/framework.dart:2521:9)
#38     SliverMultiBoxAdaptorElement.removeChild.<anonymous closure> (package:flutter/src/widgets/sliver.dart:620:32)
#39     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2113:19)
#40     SliverMultiBoxAdaptorElement.removeChild (package:flutter/src/widgets/sliver.dart:616:11)
#41     RenderSliverMultiBoxAdaptor.collectGarbage.<anonymous closure> (package:flutter/src/rendering/sliver_multi_box_adaptor.dart:302:23)
#42     RenderObject.invokeLayoutCallback.<anonymous closure> (package:flutter/src/rendering/object.dart:2022:58)
#43     PipelineOwner._enableMutationsToDirtySubtrees (package:flutter/src/rendering/object.dart:1120:15)
#44     RenderObject.invokeLayoutCallback (package:flutter/src/rendering/object.dart:2022:13)
#45     RenderSliverMultiBoxAdaptor.collectGarbage (package:flutter/src/rendering/sliver_multi_box_adaptor.dart:300:5)
#46     RenderSliverFixedExtentBoxAdaptor.performLayout (package:flutter/src/rendering/sliver_fixed_extent_list.dart:134:9)
#47     RenderObject.layout (package:flutter/src/rendering/object.dart:1926:7)
#48     RenderViewportBase.layoutChildSequence (package:flutter/src/rendering/viewport.dart:248:13)
#49     RenderViewport._attemptLayout (package:flutter/src/rendering/viewport.dart:882:12)
#50     RenderViewport.performLayout (package:flutter/src/rendering/viewport.dart:806:20)
#51     RenderObject._layoutWithoutResize (package:flutter/src/rendering/object.dart:1803:7)
#52     PipelineOwner.flushLayout (package:flutter/src/rendering/object.dart:1098:18)
#53     BindingBase&SchedulerBinding&GestureBinding&ServicesBinding&RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:251:19)
#54     BindingBase&SchedulerBinding&GestureBinding&ServicesBinding&RendererBinding&WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:504:22)
#55     BindingBase&SchedulerBinding&GestureBinding&ServicesBinding&RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:189:5)
#56     BindingBase&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:688:15)
#57     BindingBase&SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:636:9)
#58     _drawFrame (file:///b/build/slave/Mac_Engine/build/src/flutter/lib/ui/hooks.dart:88)
The following RenderObject was being processed when the exception was fired:
  RenderSliverFillViewport#73680391 relayoutBoundary=up1 NEEDS-LAYOUT
  creator: SliverFillViewport ← Viewport ← _ScrollableScope ← IgnorePointer-[GlobalKey#436933217] ←
  Listener ← _GestureSemantics ←
  RawGestureDetector-[LabeledGlobalKey<RawGestureDetectorState>#816117697] ← Scrollable ←
  NotificationListener<ScrollNotification> ← PageView ← NotificationListener<ScrollNotification> ←
  TabBarView ← ⋯
  parentData: paintOffset=Offset(0.0, 0.0) (can use size)
  constraints: SliverConstraints(AxisDirection.right, GrowthDirection.forward, ScrollDirection.idle,
  scrollOffset: 640.0, remainingPaintExtent: 320.0, crossAxisExtent: 444.0, viewportMainAxisExtent:
  320.0)
  geometry: SliverGeometry(scrollExtent: 1920.0, paintExtent: 320.0, maxPaintExtent: 1920.0,
  hasVisualOverflow: true, scrollOffsetCorrection: 0.0)
  currently live children: 2 to 2
This RenderObject had the following descendants (showing up to depth 5):
  RenderRepaintBoundary#1073716361
    RenderSemanticsGestureHandler#318907156
      RenderPointerListener#580511158
        RenderIgnorePointer#389621311
          RenderViewport#865338495
════════════════════════════════════════════════════════════════════════════════════════════════════

Flutter Doctor
[✓] Flutter (on Mac OS X 10.12.4 16E195, locale en-US, channel master)
    • Flutter at /Users/vik/Projects/flutter
    • Framework revision 1b56cb790c (7 hours ago), 2017-06-06 18:40:32 -0700
    • Engine revision 8686a45810
    • Tools Dart version 1.24.0-dev.3.0

[✓] Android toolchain - develop for Android devices (Android SDK 25.0.2)
    • Android SDK at /Users/vik/Library/Android/sdk
    • Platform android-25, build-tools 25.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.3.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 8.3.2, Build version 8E2002
    • ios-deploy 1.9.1
    • CocoaPods version 1.2.0

[✓] Android Studio (version 2.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Gradle version 3.2
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[-] IntelliJ IDEA Community Edition (version 2016.3.4)
    ✗ Flutter plugin version 12.1 - the recommended minimum version is 14.0.0
    • Dart plugin version 163.13137
    • For information about managing plugins, see
      https://www.jetbrains.com/help/idea/managing-plugins.html
    ✗ This install is older than the minimum recommended version of 2017.1.0.

[✓] Connected devices
    • iPhone SE • B19052F4-91FF-48C7-85B4-26C1D2D1A148 • ios • iOS 10.3 (simulator)

Is this fallout from @HansMuller's pagestate changes?

I was unable to reproduce the problem with https://gist.github.com/HansMuller/e43fecb89706a0245e5b300352482012
I tried creating scroll controllers keepScrollOffset true/false, providing PageStorageKeys per scrollable or not, etc.

Aha. I have been able to reproduce the problem by adding a SliverAppBar (which has a SliverPersistentHeader widget) to each CustomScrollView.  The failure occurs if the custom scroll view has a ValueKey. It doesn't appear to have anything to do with PageStorage; investigating...


Avi support

Even though avi is an ancient video file format that you think shouldn't be used anymore by people, avi was once the most popular video format. So many old videos are in avi. Please consider supporting avi format.

AVI support was added some months ago:

v0.98 Pre-release
AVI container support (work of dburckh, google/ExoPlayer#2092)
May not work with OpenDML files (dburckh/ExoPlayer#8)

AVI support was added some months ago:

Oh, great thanks.
But I get this error message opening avi video and looking online I found posts that says Just Player doesn't support that format.

Anyone can help me?

While the AVI container is somehow supported, it is mostly paired with older audio and video codecs which often may not be playable on current Android devices. To confirm this, state your device model and ideally share a video sample (or at least MediaInfo output).

On mp4 container some issue. Ac3 sound track

Latest version 0.128 includes Media3Avi, which is the most what can be done regarding support of Avi as of today.


Added .toCloudStorage function to batch.imagecollection

Dear @fitoprincipe, Dear all,
Thanks for your great work on this package! I really appreciate the work that you put in this project. It made my work on Google Earth Engine and exporting data much more enjoyable!
I recently needed to export some image collections directly to GCS instead of my Drive.
So, I added .toCloudStorage to the batch.imagecollection functions which is based on ee.batch.Export.image.toCloudStorage similar to .toDrive.
I tried to stay as close to the .toDrive function as possible.
I added a working example as a notebook here notebooks/batch/exportToGCS.ipynb. This notebook was modified from notebooks/batch/exportByFeat.ipynb. To reproduce the results, you would need a bucket with write access and a default GCS project.
Let me know what should be changed to make it compatible with the current codebase. I am happy to help, contribute, and make this feature accessible to others, too.

Hello @MarcCoru, thank you for this PR!! This really helps me a lot since I've been coding this by myself from the beginning =) As I have never used .toCloudStorage I didn't include it here, so this PR is great! I may leave some comments on code before I merge

Now looks great @MarcCoru, thanks!!!


Initial image pulls on Prow are extremely slow.

The initial unlucky test that happens to be pulling the images down takes an enormous amount of time.
https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio/12574/istio-integ-k8s-tests/5157/build-log.txt
It starts deployment & wait at 2019-03-19T16:25:56.902108Z
2019-03-19T16:25:46.909352Z	info	CI	Wrote out istio.yaml at: /tmp/citadel-test-411af006cd9541118d/istio-deployment-yaml-338472781/istio.yaml
2019-03-19T16:25:46.922481Z	info	CI	Created Helm-generated Yaml file(s): /tmp/citadel-test-411af006cd9541118d/istio-deployment-yaml-split-283703846/istio-install.yaml, /tmp/citadel-test-411af006cd9541118d/istio-deployment-yaml-split-283703846/istio-configure.yaml
2019-03-19T16:25:46.949613Z	info	CI	Applying YAML file: /tmp/citadel-test-411af006cd9541118d/env-kube-817069347/istio-kube-accessor-998212680/istio-install_namespaces_and_crds.yaml761451271
2019-03-19T16:25:50.968957Z	info	CI	Applying YAML file: /tmp/citadel-test-411af006cd9541118d/env-kube-817069347/istio-kube-accessor-998212680/istio-install_misc.yaml086281914
2019-03-19T16:25:56.902108Z	info	CI	Checking pods...
2019-03-19T16:25:57.066825Z	info	CI	  [ 0]                istio-citadel-6dd66c9cc4-jbhkx         Pending (Pending)
2019-03-19T16:25:57.066882Z	info	CI	  [ 1] istio-cleanup-secrets-79e2a6ef5ef33e84fa4e1b6d55ac1234-mpvk7         Pending (Pending)
2019-03-19T16:25:57.066889Z	info	CI	  [ 2]          istio-egressgateway-6565554886-fzbtb         Pending (Pending)
2019-03-19T16:25:57.066894Z	info	CI	  [ 3]                 istio-galley-76b6897586-8s22f         Pending (Pending)
2019-03-19T16:25:57.066898Z	info	CI	  [ 4]         istio-ingressgateway-57967d4b9c-bdqjm         Pending (Pending)
2019-03-19T16:25:57.066902Z	info	CI	  [ 5]                  istio-pilot-647c866664-gl6n7         Pending (Pending)
2019-03-19T16:25:57.066906Z	info	CI	  [ 6]                 istio-policy-768997bd9f-64gj7         Pending (Pending)
2019-03-19T16:25:57.066910Z	info	CI	  [ 7]                 istio-policy-768997bd9f-77ts8         Pending (Pending)
2019-03-19T16:25:57.066914Z	info	CI	  [ 8]       istio-sidecar-injector-5d7754c9c6-8879l         Pending (Pending)
2019-03-19T16:25:57.066920Z	info	CI	  [ 9]               istio-telemetry-ff564f5b7-mq9s2         Pending (Pending)
2019-03-19T16:25:57.066924Z	info	CI	  [10]                    prometheus-c8d8657bf-2526z         Pending (Pending)
2019-03-19T16:26:07.067204Z	info	CI	Checking pods...

First signs of life appear at 2019-03-19T16:31:38.581693Z, after ~6 minutes.
2019-03-19T16:31:38.581693Z	info	CI	Checking pods...
2019-03-19T16:31:38.617037Z	info	CI	  [ 0]                istio-citadel-6dd66c9cc4-jbhkx         Pending (Pending)
2019-03-19T16:31:38.617101Z	info	CI	  [ 1] istio-cleanup-secrets-79e2a6ef5ef33e84fa4e1b6d55ac1234-mpvk7         Pending (Pending)
2019-03-19T16:31:38.617108Z	info	CI	  [ 2]          istio-egressgateway-6565554886-fzbtb         Pending (Pending)
2019-03-19T16:31:38.617113Z	info	CI	  [ 3]                 istio-galley-76b6897586-8s22f         Pending (Pending)
2019-03-19T16:31:38.617118Z	info	CI	  [ 4]         istio-ingressgateway-57967d4b9c-bdqjm         Pending (Pending)
2019-03-19T16:31:38.617123Z	info	CI	  [ 5]                  istio-pilot-647c866664-gl6n7         Running (container not ready: 'discovery')
2019-03-19T16:31:38.617128Z	info	CI	  [ 6]                 istio-policy-768997bd9f-64gj7         Pending (Pending)
2019-03-19T16:31:38.617132Z	info	CI	  [ 7]                 istio-policy-768997bd9f-77ts8         Pending (Pending)
2019-03-19T16:31:38.617137Z	info	CI	  [ 8]       istio-sidecar-injector-5d7754c9c6-8879l         Pending (Pending)
2019-03-19T16:31:38.617141Z	info	CI	  [ 9]               istio-telemetry-ff564f5b7-mq9s2         Pending (Pending)
2019-03-19T16:31:38.617145Z	info	CI	  [10]                    prometheus-c8d8657bf-2526z         Pending (Pending)
2019-03-19T16:31:48.617374Z	info	CI	Checking pods...

And by 2019-03-19T16:41:01.385004Z things are still not settled due to slow image pulls. (~16 minutes)
2019-03-19T16:40:31.283613Z	info	CI	Checking pods...
2019-03-19T16:40:31.317807Z	info	CI	  [ 0]                istio-citadel-6dd66c9cc4-jbhkx         Running (Ready)
2019-03-19T16:40:31.317848Z	info	CI	  [ 1] istio-cleanup-secrets-79e2a6ef5ef33e84fa4e1b6d55ac1234-mpvk7       Succeeded (Ready)
2019-03-19T16:40:31.317852Z	info	CI	  [ 2]          istio-egressgateway-6565554886-fzbtb         Running (Ready)
2019-03-19T16:40:31.317856Z	info	CI	  [ 3]                 istio-galley-76b6897586-8s22f         Running (Ready)
2019-03-19T16:40:31.317860Z	info	CI	  [ 4]         istio-ingressgateway-57967d4b9c-bdqjm         Running (Ready)
2019-03-19T16:40:31.317864Z	info	CI	  [ 5]                  istio-pilot-647c866664-gl6n7         Running (Ready)
2019-03-19T16:40:31.317871Z	info	CI	  [ 6]                 istio-policy-768997bd9f-64gj7         Running (container not ready: 'mixer')
2019-03-19T16:40:31.317875Z	info	CI	  [ 7]                 istio-policy-768997bd9f-77ts8         Running (Ready)
2019-03-19T16:40:31.317878Z	info	CI	  [ 8]       istio-sidecar-injector-5d7754c9c6-8879l         Running (Ready)
2019-03-19T16:40:31.317883Z	info	CI	  [ 9]               istio-telemetry-ff564f5b7-mq9s2         Running (container not ready: 'mixer')
2019-03-19T16:40:31.317886Z	info	CI	  [10]                    prometheus-c8d8657bf-2526z         Running (Ready)
2019-03-19T16:40:41.318106Z	info	CI	Checking pods...
2019-03-19T16:40:41.350070Z	info	CI	  [ 0]                istio-citadel-6dd66c9cc4-jbhkx         Running (Ready)
2019-03-19T16:40:41.350125Z	info	CI	  [ 1] istio-cleanup-secrets-79e2a6ef5ef33e84fa4e1b6d55ac1234-mpvk7       Succeeded (Ready)
2019-03-19T16:40:41.350130Z	info	CI	  [ 2]          istio-egressgateway-6565554886-fzbtb         Running (Ready)
2019-03-19T16:40:41.350134Z	info	CI	  [ 3]                 istio-galley-76b6897586-8s22f         Running (Ready)
2019-03-19T16:40:41.350137Z	info	CI	  [ 4]         istio-ingressgateway-57967d4b9c-bdqjm         Running (Ready)
2019-03-19T16:40:41.350142Z	info	CI	  [ 5]                  istio-pilot-647c866664-gl6n7         Running (Ready)
2019-03-19T16:40:41.350149Z	info	CI	  [ 6]                 istio-policy-768997bd9f-64gj7         Running (container not ready: 'mixer')
2019-03-19T16:40:41.350154Z	info	CI	  [ 7]                 istio-policy-768997bd9f-77ts8         Running (Ready)
2019-03-19T16:40:41.350157Z	info	CI	  [ 8]       istio-sidecar-injector-5d7754c9c6-8879l         Running (Ready)
2019-03-19T16:40:41.350162Z	info	CI	  [ 9]               istio-telemetry-ff564f5b7-mq9s2         Running (container not ready: 'mixer')
2019-03-19T16:40:41.350166Z	info	CI	  [10]                    prometheus-c8d8657bf-2526z         Running (Ready)
2019-03-19T16:40:51.350474Z	info	CI	Checking pods...
2019-03-19T16:40:51.384586Z	info	CI	  [ 0]                istio-citadel-6dd66c9cc4-jbhkx         Running (Ready)
2019-03-19T16:40:51.384636Z	info	CI	  [ 1] istio-cleanup-secrets-79e2a6ef5ef33e84fa4e1b6d55ac1234-mpvk7       Succeeded (Ready)
2019-03-19T16:40:51.384641Z	info	CI	  [ 2]          istio-egressgateway-6565554886-fzbtb         Running (Ready)
2019-03-19T16:40:51.384644Z	info	CI	  [ 3]                 istio-galley-76b6897586-8s22f         Running (Ready)
2019-03-19T16:40:51.384648Z	info	CI	  [ 4]         istio-ingressgateway-57967d4b9c-bdqjm         Running (Ready)
2019-03-19T16:40:51.384652Z	info	CI	  [ 5]                  istio-pilot-647c866664-gl6n7         Running (Ready)
2019-03-19T16:40:51.384659Z	info	CI	  [ 6]                 istio-policy-768997bd9f-64gj7         Running (container not ready: 'mixer')
2019-03-19T16:40:51.384662Z	info	CI	  [ 7]                 istio-policy-768997bd9f-77ts8         Running (Ready)
2019-03-19T16:40:51.384665Z	info	CI	  [ 8]       istio-sidecar-injector-5d7754c9c6-8879l         Running (Ready)
2019-03-19T16:40:51.384672Z	info	CI	  [ 9]               istio-telemetry-ff564f5b7-mq9s2         Running (container not ready: 'mixer')
2019-03-19T16:40:51.384676Z	info	CI	  [10]                    prometheus-c8d8657bf-2526z         Running (Ready)
2019-03-19T16:41:01.385004Z	error	CI	Wait for Istio pods failed: timeout while waiting (last error: 2 errors occurred:

Compare it with a later deployment in another test:
Starts at 2019-03-19T16:42:28.939363Z
2019-03-19T16:42:28.939363Z	info	CI	Checking pods...
2019-03-19T16:42:29.114162Z	info	CI	  [ 0]                istio-citadel-6dd66c9cc4-wjrtj         Pending (Pending)
2019-03-19T16:42:29.114212Z	info	CI	  [ 1] istio-cleanup-secrets-79e2a6ef5ef33e84fa4e1b6d55ac1234-ccqb4         Pending (Pending)
2019-03-19T16:42:29.114219Z	info	CI	  [ 2]          istio-egressgateway-6565554886-zvgxh         Pending (Pending)
2019-03-19T16:42:29.114224Z	info	CI	  [ 3]                 istio-galley-76b6897586-xfj96         Pending (Pending)
2019-03-19T16:42:29.114230Z	info	CI	  [ 4]         istio-ingressgateway-57967d4b9c-hr4dt         Pending (Pending)
2019-03-19T16:42:29.114235Z	info	CI	  [ 5]                  istio-pilot-647c866664-nl6j5         Pending (Pending)
2019-03-19T16:42:29.114257Z	info	CI	  [ 6]                 istio-policy-768997bd9f-4xq5m         Pending (Pending)
2019-03-19T16:42:29.114261Z	info	CI	  [ 7]                 istio-policy-768997bd9f-hfgfj         Pending (Pending)
2019-03-19T16:42:29.114269Z	info	CI	  [ 8]       istio-sidecar-injector-5d7754c9c6-x887f         Pending (Pending)
2019-03-19T16:42:29.114274Z	info	CI	  [ 9]               istio-telemetry-ff564f5b7-s4v25         Pending (Pending)
2019-03-19T16:42:29.114279Z	info	CI	  [10]                    prometheus-c8d8657bf-5hzwk         Pending (Pending)

Completes at 2019-03-19T16:44:02.574453Z (~90 secs)
2019-03-19T16:43:59.590232Z	info	CI	Checking pods...
2019-03-19T16:43:59.625217Z	info	CI	  [ 0]                istio-citadel-6dd66c9cc4-wjrtj         Running (Ready)
2019-03-19T16:43:59.625265Z	info	CI	  [ 1] istio-cleanup-secrets-79e2a6ef5ef33e84fa4e1b6d55ac1234-ccqb4       Succeeded (Ready)
2019-03-19T16:43:59.625270Z	info	CI	  [ 2]          istio-egressgateway-6565554886-zvgxh         Running (Ready)
2019-03-19T16:43:59.625274Z	info	CI	  [ 3]                 istio-galley-76b6897586-xfj96         Running (Ready)
2019-03-19T16:43:59.625278Z	info	CI	  [ 4]         istio-ingressgateway-57967d4b9c-hr4dt         Running (Ready)
2019-03-19T16:43:59.625282Z	info	CI	  [ 5]                  istio-pilot-647c866664-nl6j5         Running (Ready)
2019-03-19T16:43:59.625286Z	info	CI	  [ 6]                 istio-policy-768997bd9f-4xq5m         Running (Ready)
2019-03-19T16:43:59.625290Z	info	CI	  [ 7]                 istio-policy-768997bd9f-hfgfj         Running (Ready)
2019-03-19T16:43:59.625295Z	info	CI	  [ 8]       istio-sidecar-injector-5d7754c9c6-x887f         Running (Ready)
2019-03-19T16:43:59.625298Z	info	CI	  [ 9]               istio-telemetry-ff564f5b7-s4v25         Running (Ready)
2019-03-19T16:43:59.625302Z	info	CI	  [10]                    prometheus-c8d8657bf-5hzwk         Running (Ready)
2019-03-19T16:43:59.631138Z	info	CI	Applying YAML file: /tmp/framework-test-e13e907a57394c52/TestBasic/istio-deployment-yaml-split566978485/istio-configure.yaml
2019-03-19T16:44:02.574453Z	info	CI	=== SUCCEEDED: Deploy Istio ===
--- PASS: TestBasic (145.06s)

istio-integ-k8s-tests and istio-presubmit are running at the same time, when in reality istio-integ-k8s-tests  should run only after  istio-presubmit is finished.
istio-integ-k8s-tests is pulling images which are not yet build by  istio-presubmit
https://github.com/istio/test-infra/blob/4d23ddb0a6b73730b0f3ea30cd83858d31ffff25/prow/cluster/jobs/istio/istio/istio.istio.master.yaml#L50

What is the right fix? Do we need to order them correctly in the file?

Yes, i am changing the order, PR is coming soon

Thanks!
On Tue, Mar 19, 2019 at 12:48 PM Maria Skidanova<EMAIL_ADDRESS>wrote:

Yes, i am changing the order, PR is coming soon
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/12606#issuecomment-474550823, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQR8I2PKLtLroZAIvYwnhVcZXyzZXpgsks5vYT8kgaJpZM4b80qA
.

This is fixed right? Going to close


nixos/dhcpcd: allow jemalloc and mimalloc memory allocators

The dhcpcd package version 10.0.0 and later now supports jemalloc and mimalloc memory allocators.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Rebased PR.
What is needed to get this PR merged?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/2019

Please stop touching dhcpcd until staging-next is merged, or submit your changes directly against staging-next. The manual merging every six hours is getting tedious.

Sorry, I created the PR before I knew about the dhcpcd changes in the staging branch.

Sorry, I also wasn't aware of that.

I've fallen foul of this before too.
:thinking: I wonder how practical it would be to have a CI check that alerted people to changes that created merge conflicts with staging..


The results res not good

Following the code, I retrain the model via 'python train_pcrnet.py'. The loss curve is not good with Chamfer distance. I can not find the reason. Could you help me?

Hey @zhangguanghui1,
Can you please check the visualizations of the 3D point clouds? Sometimes, the test loss might be unstable but the best_model has already learned to register 3D point clouds.
I would highly recommend visualizing the source, template, and registered point cloud.
Thank you.


Scheduled Actions for New Releases & Package Issues

This comes from https://github.com/luxtorpeda-dev/packages/issues/864#issuecomment-1499661363
RuneScape is one game where the link can become a 404 if the developers release a new version.
The idea here is to create a generic system for checking various engines for issues, and have a github action run scheduled daily (https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule).
Each engine can have in their env.sh file a list of scripts to run in scheduled mode. This could look like:
export ACTION_CHECK="./tests/version_download.sh"

These checks to make sure they're using the correct data should look at the json file and grab the download from there (could be something like jq to get the data in shell).
Then there'd be a script to run through and loop all the engines and check for any scripts, run them, and then move on to the next one. This should be done so that one failure would just let the rest keep running.
Success can be ignored, where no result file is stored. For an error, those should be stored in a JSON file. This could be done by the script itself if it encounters an error. All of these should be stored in a specific directory (parent script would give the name of it in a variable).
Then, a node action would be created and run to loop through the files in the folder, and create issues related to them. The name should be a good description (enginename - Issue encountered), coming from the JSON file. As well, any description, including error messages or what was happening. Tags should be created noting it's an engine bug or upgrade (for cases of new release).
Process should be created to ensure that only one issue is created, so that if the issue is not resolved, we don't keep creating issues. This could be done by checking to see if an issue with the same name has already been created, and if so, refrain from creating.
Common things that asking for if a new release is available should be in a common script, then for the ENV, instead of ACTION_CHECK with a script path (for custom jobs), another variable could be ACTION_RELEASE_CHECK="".

Also don't always assume that a failed download is because the download link changed. It might sometimes be due to unforeseen internet issues. Maybe Runescape servers were down for an hour for maintenance, maybe they're detecting our checks as some sort of bot traffic, maybe there's a routing issue between servers. It could be a false alarm.

This is now complete, with the latest changes. It'll create an issue like this if it's discovered - https://github.com/luxtorpeda-dev/packages/issues/1017


increase sidecar injector webhook test coverage

add test for annotation replace patching

add test for upgrading injected sidecar

benchmark http handler for webhook injection with default
parameterized template configuration.
$ go test -bench .
BenchmarkInjectServe-4           1000000              1469 ns/op

/lgtm

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
c710a69cbb7629b9fc7107c38b62fc30ade1433f
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
c710a69cbb7629b9fc7107c38b62fc30ade1433f
link
/test istio-pilot-e2e

prow/e2e-smoke.sh
25257a1e09ea7bbfa8bb9ad16c75c64935f5116d
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-smoke

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
25257a1e09ea7bbfa8bb9ad16c75c64935f5116d
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
25257a1e09ea7bbfa8bb9ad16c75c64935f5116d
link
/test e2e-smoke

prow/istio-unit-test.sh
f7c9278e5cdd73274130defd70811832943c29a4
link
/test istio-unit-test

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
25257a1e09ea7bbfa8bb9ad16c75c64935f5116d
link
/test e2e-smoke

prow/istio-unit-test.sh
f7c9278e5cdd73274130defd70811832943c29a4
link
/test istio-unit-test

prow/istio-presubmit.sh
f7c9278e5cdd73274130defd70811832943c29a4
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-test.sh
f7c9278e5cdd73274130defd70811832943c29a4
link
/test istio-unit-test

prow/istio-pilot-e2e.sh
f7c9278e5cdd73274130defd70811832943c29a4
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-test.sh
f7c9278e5cdd73274130defd70811832943c29a4
link
/test istio-unit-test

prow/istio-pilot-e2e.sh
f7c9278e5cdd73274130defd70811832943c29a4
link
/test istio-pilot-e2e

prow/e2e-smoke.sh
e934acef1be7c60d3a6f3f4c2e4e15bdd8d443c3
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-test.sh
f7c9278e5cdd73274130defd70811832943c29a4
link
/test istio-unit-test

prow/e2e-smoke.sh
e934acef1be7c60d3a6f3f4c2e4e15bdd8d443c3
link
/test e2e-smoke

prow/istio-pilot-e2e.sh
e934acef1be7c60d3a6f3f4c2e4e15bdd8d443c3
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

e2e-smoke fails because of #3320

pilot-e2e-fails for http reachability in auth enabled mode, could be due to the slow loading of certificates #3139 , but we are missing the logs we cannot be sure. In any case, the failure is unrelated to the changes in this PR.


Companion article for BWA OIDC w/Aspire sample app

https://github.com/dotnet/blazor-samples/tree/main/8.0/BlazorWebAppOidc
~Change the sample folder name first.~ Done! ... BlazorWebAppOidc

@travaille-dev ... Here's a revised LogInOrOut component that deals with the redirect problem. It's not particularly elegant relying upon reflection. However, it's a reasonable hack 🙈 until Stephen can get back and tell me how best to solve the problem. As for the IWeatherForecaster service not being on the server for server-side rendering, I'll work on that tomorrow.
@implements IDisposable
@using System.Reflection
@using System.Security.Claims
@using Microsoft.AspNetCore.Authorization
@inject IAuthorizationService AuthorizationService
@inject NavigationManager NavigationManager

    <AuthorizeView>
        <Authorized>
            <form action="authentication/logout" method="post">
                <AntiforgeryToken />
                <input type="hidden" name="ReturnUrl" value="@currentUrl" />
                <button type="submit" class="nav-link">
                     Logout @context.User.Identity?.Name
                </button>
            </form>
        </Authorized>
        <NotAuthorized>

                 Login

        </NotAuthorized>
    </AuthorizeView>

@code {
    private string? currentUrl;
    private ClaimsPrincipal? user;

    [CascadingParameter]
    private Task<AuthenticationState>? authenticationState { get; set; }

    protected override async Task OnInitializedAsync()
    {
        currentUrl = NavigationManager.ToBaseRelativePath(NavigationManager.Uri);
        NavigationManager.LocationChanged += OnLocationChanged;

        if (authenticationState is not null)
        {
            var authState = await authenticationState;
            user = authState?.User;
        }
    }

    private void OnLocationChanged(object? sender, LocationChangedEventArgs e)
    {
        var currentUrl = NavigationManager.ToBaseRelativePath(e.Location);

        if (user?.Identity is not null && user.Identity.IsAuthenticated)
        {
            var matchingAuthComponentCount =
            Assembly.GetExecutingAssembly()
                    .ExportedTypes
                    .Where(t => t.IsSubclassOf(typeof(ComponentBase)))
                    .Any(c => c.GetCustomAttributes(inherit: true)
                                    .OfType<AuthorizeAttribute>()
                                    .Any() &&
                                c.GetCustomAttributes(inherit: true)
                                    .OfType<RouteAttribute>()
                                    .Where(d => d.Template == $"/{currentUrl}")
                                    .Any());

            if (matchingAuthComponentCount)
            {
                currentUrl = string.Empty;
            }
        }

        StateHasChanged();
    }

    public void Dispose()
    {
        NavigationManager.LocationChanged -= OnLocationChanged;
    }
}

UPDATE (1/26) ...

I created a server implementation of the IWeatherForecaster service and moved the interface to a shared project, but I still ran into some auth problems. My current workaround is just to place <AuthorizeView>...</AuthorizeView> tags around the Weather entry in the NavMenu component, which stops a user from seeing it until they're logged in; therefore, prevents the prerendering error with IWeatherForecaster from ever happening by an unauthenticated user just selecting to navigate to the Weather component, signing in, and then getting a 💥 when they're redirected back to the app. That flow isn't a concern if they can't select the Weather component in the nav sidebar in the first place. I've set the sample apps up that way for now, and we'll see what Stephen wants to do when he gets back.
I found a number of good constants to use in the Program file; however, I might really want to make the samples all configuration based in the end. That's really the best way to manage all of this configuration, not via hard-coding anything into the Program file. I guess I can show both (e.g., place these hard-coded settings into a section at the end of the article for reference), but I think the main demonstration should use configuration. That's what real production apps do!


Cannot run karma tests

Steps to reproduce and a minimal demo of the problem

Clone the repository and change the component to use any observable.

Current behavior
18 08 2016 22:22:50.426:INFO [karma]: Karma v0.13.22 server started at http://localhost:9876/
18 08 2016 22:22:50.430:INFO [launcher]: Starting browser Chrome
18 08 2016 22:22:52.115:INFO [Chrome 52.0.2743 (Linux 0.0.0)]: Connected on socket /#iiI-4vTinwev68hfAAAA with id 59110883
18 08 2016 22:22:53.251:WARN [web-server]: 404: /base/node_modules/rxjs.js
Chrome 52.0.2743 (Linux 0.0.0) ERROR: Error{originalErr: Error{}}

Expected/desired behavior
There should be no such error
Other information
This one is probably introduced with rc5 build
The stack trace is
GET http://localhost:9876/base/node_modules/rxjs.js 404 (Not Found)
Error: Error: XHR error (404 Not Found) loading http://localhost:9876/base/node_modules/rxjs.js
	    at XMLHttpRequest.wrapFn [as _onreadystatechange] (http://localhost:9876/base/node_modules/zone.js/dist/zone.js:789:30)
	    at ZoneDelegate.invokeTask (http://localhost:9876/base/node_modules/zone.js/dist/zone.js:365:38)
	    at Zone.runTask (http://localhost:9876/base/node_modules/zone.js/dist/zone.js:265:48)
	    at XMLHttpRequest.ZoneTask.invoke (http://localhost:9876/base/node_modules/zone.js/dist/zone.js:432:34)
	Error loading http://localhost:9876/base/node_modules/rxjs.js as "rxjs" from http://localhost:9876/base/dist/dev/app/account/auth/auth.service.js

The auth.sevice.js file contains import { Observable } from 'rxjs';

I could reproduce the error.
Can you replace the import { Observable } from 'rxjs'; to import { Observable } from 'rxjs/Observable'; and try it again? It should fix the error

It fixes the error :+1: But it would be better if we could import from rxjs instead of others

Just hit this error on an unrelated project and this thread was literally the only one on Google which mentioned it. THANKS!


luci-app-openvpn: FileUpload fields not shown

In the OpenVPN LuCI interface, an instance created from a template has many FileUpload fields that are not shown despite being present in the uci config object (e.g. dh or ca).
They can be added explicitly so that they appear. But removal does not seem to be possible.

@jow- I could fix that with the "unsafeupload" property but it looks like some css magic is needed (at least in bootstrap theme):
OpenWrt theme:

Bootstrap theme:

Thanks!

Would that help? I think this fixes some things.
--- a/applications/luci-app-openvpn/luasrc/model/cbi/openvpn-advanced.lua
+++ b/applications/luci-app-openvpn/luasrc/model/cbi/openvpn-advanced.lua
@@ -247,6 +247,10 @@ for _, option in ipairs(params) do

 		o.optional = true

+		if option[1] == FileUpload then
+			o.datatype = "file"
+		end

@mwarning No, that will already checked by the used FileUpload function. Appropriate changes for your issue are in #2307

As a heads up, I applied the changes from #2307 to the current nightly build of OpenWrt and it did not seem to work yet.

@mwarning maybe you could elaborate what "did not seem to work" mean?
#2307 add the opportunity to remove existing entries ... it doesn't change the (desired) FileUpload behaviour that only valid file handles are shown.

That's a feature, not a bug. The FileUpload types are only visible if they reference a valid file (typically uploaded by the user in /etc/luci-uploads/....)

I tried to set secret and thought that would work. But OpenVPN did not start because the ca field etc. contains a dummy file path. But since I do not see that field, I do not know that I have to add (to make it visible) and then remove that field.

@dibdot looks good. I can see all fields that are set now. When I clear the dh filed and hit "Save & Apply", the field is removed. (But hitting the "Save" button doe not remove an empty field - is that intentional?)

Yes, that's the usual behaviour - only "apply" will finally update/commit the changes to the uci file itself.

Alright. And is it intentional that luci-app-openvpn does not depend on package openvpn?

yep - I will merge #2307 now. Thanks for your input & testing efforts.

ok, thanks for your efforts.


Updated references to lane change trigger boxes

In version 1.11 the lane change trigger box was changed to the "Vehicle Behavior Trigger Box". This needs updating in the RTD and at least something in the notes of the videos for the scenario generation.

resolved with 1.13 pr

resolved with 1.13 pr


How to get data if i'm using two mutate functions in a component?

I'm on a component where a api call exists on componentdidmount and one when use clicks on a button of that page so how can get the data of that particular api call?

I am not sure I understand your question completely. If I didn't please feel free to elaborate.
When you perform a mutation and you want the data returned from the api to update the data you currently have in your cache, then you can make use of the updateQuery option
https://github.com/tannerlinsley/react-query#query-updates-from-mutations

Yeah, we'll need more info here. From what you've given me, I would say first that React Query only works with React hooks and if you're using componentDidMount, then you are probably using class components, so React Query will not work in that situation.
Going to close this for triage, but please feel free to reopen a new issue with more information. Thanks!

I am using hooks only.
I'm using useEffect with empty array to act like componentDidMount.
`  const [mutate, { isLoading, data, error }] = useMutation(handleApi);
mutate({
method: "get",
endpoint: apiEndpoint,
data: {}
});

`
handleApi is a centralized api call function where i just need to pass request type, endpoint url and data, now...i've a component which makes an api call(1) using componentDIdMount(using useffect) which renders a certain number of list and that list contains a button which also makes an api call(2)...Now as i'm using mutate, i expect it to use data, isLoading, error like above. i've used mutate with both the api calls with different request type and endpoint url,  but as above mentioned (data, error, isloading) how to get the (data,error,isloading) for first api call and second one.

Your explanation is still too vague. I think the best way forward would be to create a codesandbox showing what you would like to achieve and we can help you fill in the gaps from there.
On Feb 21, 2020, 10:39 PM -0700, Himanshu Sain<EMAIL_ADDRESS>wrote:

I am using hooks only.
I'm using useEffect with empty array to act like componentDidMount.
const [mutate, { isLoading, data, error }] = useMutation(handleApi); mutate({ method: "get", endpoint: apiEndpoint, data: {} });
handleApi is a centralized api call function where i just need to pass request type, endpoint url and data, now...i've a component which makes an api call(1) using componentDIdMount(using useffect) which renders a certain number of list and that list contains a button which also makes an api call(2)...Now as i'm using mutate, i expect it to use data, isLoading, error like above. i've used mutate with both the api calls with different request type and endpoint url, but as above mentioned (data, error, isloading) how to get the (data,error,isloading) for first api call and second one.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.


[Android] Slow encryption/decryption

Currently key derivation by use of the scrypt() function is extremely slow on Android (only tested on emulator, as I don't have a real device). The same function takes ~3-4 seconds on the iOS emulator dev mode (with remote debugging disabled).
Things I've tried/checked:

Run in production mode vs dev mode (no difference)
Checked that enough memory is assigned to the emulator (1.5GB)
Disabled any console.log() (no difference)
Turned off redux-logger (no difference)
Running with Remote JS Debugging on, it's fast again. But that's because execution get's off loaded to the browser (read explanation here

We can't change the number of iterations (16384 to e.g. 1) because then keys created by other wallets will fail to verify. It's also less secure.

Yes, I am facing the same issue while running it on real device.It is taking around 10 minutes while doing the encrypt.

thank you for testing the android side!


Update deprecated web3 APIs

Fixes #109

If they serve no purpose other than helping debug failed tests, I'd say it's better to leave the parameters out. It's always possible to temporarily add -vvvvvvvs -Wd to travis config file if dev needs to check the output or logs.

@pcppcp @loredanacirstea I fixed all warnings, ready for review.


kw_only=True in class cannot be overridden by attributes

Mostly wondering if this is expected/desired:
import attr
@attr.s(kw_only=True)
class A:
    a = attr.ib(kw_only=False)

A(1)  # Error

That’s a good question. It’s inconsistent with other settings where attribute settings  always take precedence  over class settings. Kw_only is kind of special but probably not special enough to break that contract? 🤔

Let me know if this changes because I'll have to update the mypy plugin.  (Currently it's written with the current behavior)

I think I'll do some brain-storming on this.


Add Python samples

#30 should be reviewed first.

Merge conflicts are now resolved. @leahecole please take another pass over the code samples from a Python Samples Owner perspective?


[BUG]: Model Comparison via notebook

Describe the bug
Comparing two models using the notebook's preset option: Compare the three models and visualize and display them.
fails. with:  No module named 'gilda'
To Reproduce
Steps to reproduce the behavior:
https://app.staging.terarium.ai/projects/fee63545-9733-486e-901f-dfddc8fef193/workflow/666b0aa6-d020-4f69-a364-10ac3e287957

https://github.com/DARPA-ASKEM/askem-beaker/pull/138


16f OOP: Frames

Finally, we're down to the last dict ripe for conversion: the frame.
There's nothing wrong with a dict for a frame; what's going on is I'm tired of repeating helper functions for dealing with frames. These helper functions work primarily with frames and names, and it makes good sense to bundle them together so that we can use those functions wherever the frame goes.
Let's start with a Frame class:
https://github.com/nyjc-computing/pseudo/blob/c1ffed90f1bd74b3e3104c97d247b46cb5eca421/lang.py#L86-L133

Lets replace all the places where we treated frame as a dict, reworking them into method calls: [ac30c99cc37384a6eabfc3cab3d9f84ab8a1076a], [8d390402f5c314a2e316d9a30a01bb7e29757b83], [f17620215ca47198c0ca6543a9034ffcebdf7c7a]

Yep, we are trying to eliminate all uses of the helper functions for frames; we have replaced them with frame methods.
Since the frame methods don't do type-checking, we still have to keep the error methods, and use them where appropriate. Still, that means we've managed to replace two sets of helper functions (in the resolver and interpreter) with one set of methods (in Frame). Overall, it's still a win for maintainability.

And now we can remove the helpers: [69abe4003612e3ad43e2acda22564b8227943fce], [626a3433a851eb4f86ce72eb52622f171c1643a3]

A couple quick bugfixes: [03b2ba53d079b2891b407c0c8b7cd840dedd0ee9]


POST to /raw does not seem to work

Hey!
I was playing with the API using curl, but I encounter a problem. Any idea?
$ curl -X POST -F<EMAIL_ADDRESS>http://word-to-markdown.herokuapp.com/raw
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

  <TITLE>Internal Server Error</TITLE>

Internal Server Error

    closed stream

    <ADDRESS>
     WEBrick/1.3.1 (Ruby/2.1.0/2013-12-25) at
     word-to-markdown.herokuapp.com:80
    </ADDRESS>

This is now fixed. Not sure how it ever worked before. :smile:


310 v1.1 tracking issue

[x] Team formation is somewhat ugly

[x] #23 TAs need the dashboard

[x] Render single-student teams in admintab

[x] Add repositories list item for provisioned repos on student frontend.

[x] Don't show tables on student frontend that have no rows.

Add repositories list item for provisioned repos.

Team formation is still ugly. Just a little less so.


Rework ospkg

source tree structure
review struct ans interface types
what can be pulled out of stboot.go?
should trust be a sub package?

https://git.glasklar.is/system-transparency/core/stboot/-/tree/main/


Use direct download timeout configs for URL check during registerTemplate

Description
This PR allows the direct download timeout configurations to apply to the URL check during registerTemplate.
There is already support in the Downloader classes for these configurations for the actual download of templates, and the ConfigKeys already exist, so just needed to pass these in the CheckUrlCommand
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[x] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[x] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Tested locally, confirmed config items are passed along.
mgmt server:
2023-09-06 14:41:09,340 DEBUG [c.c.a.m.ClusteredAgentAttache] (qtp1911152052-21:ctx-09dfd07c ctx-600dfd34) (logid:1083f2be) (extid:) Seq 43-7668222790528401454: Forwarding Seq 43-7668222790528401454:  { Cmd , MgmtId:<PHONE_NUMBER>6821, via: 43(kvmlab2), Ver: v1, Flags: 100011, [{"org.apache.cloudstack.agent.directdownload.CheckUrlCommand":{"format":"QCOW2","url":"https://download.fedoraproject.org/pub/fedora/linux/releases/37/Cloud/x86_64/images/Fedora-Cloud-Base-37-1.7.x86_64.qcow2","connectTimeout":"7000","connectionRequestTimeout":"5000","socketTimeout":"8000","wait":"0","bypassHostMaintenance":"false"}}] } to<PHONE_NUMBER>
2023-09-06 14:41:11,405 DEBUG [c.c.a.t.Request] (AgentManager-Handler-8:null) (logid:) (extid:) Seq 43-7668222790528401454: Processing:  { Ans: , MgmtId:<PHONE_NUMBER>6821, via: 43, Ver: v1, Flags: 10, [{"org.apache.cloudstack.agent.directdownload.CheckUrlAnswer":{"templateSize":"(5.00 GB)<PHONE_NUMBER>","result":"true","wait":"0","bypassHostMaintenance":"false"}}] }

hypervisor:
2023-09-06 14:41:09,385 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:null) (logid:1083f2be) Request:Seq 43-7668222790528401454:  { Cmd , MgmtId:<PHONE_NUMBER>6821, via: 43, Ver: v1, Flags: 100011, [{"org.apache.cloudstack.agent.directdownload.CheckUrlCommand":{"format":"QCOW2","url":"https://download.fedoraproject.org/pub/fedora/linux/releases/37/Cloud/x86_64/images/Fedora-Cloud-Base-37-1.7.x86_64.qcow2","connectTimeout":"7000","connectionRequestTimeout":"5000","socketTimeout":"8000","wait":"0","bypassHostMaintenance":"false"}}] }
2023-09-06 14:41:09,386 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:null) (logid:1083f2be) Processing command: org.apache.cloudstack.agent.directdownload.CheckUrlCommand
2023-09-06 14:41:09,386 INFO  [resource.wrapper.LibvirtCheckUrlCommand] (agentRequest-Handler-4:null) (logid:1083f2be) Checking URL: https://download.fedoraproject.org/pub/fedora/linux/releases/37/Cloud/x86_64/images/Fedora-Cloud-Base-37-1.7.x86_64.qcow2, with connect timeout: 7000, connect request timeout: 5000, socket timeout: 8000
2023-09-06 14:41:11,404 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:null) (logid:1083f2be) Seq 43-7668222790528401454:  { Ans: , MgmtId:<PHONE_NUMBER>6821, via: 43, Ver: v1, Flags: 10, [{"org.apache.cloudstack.agent.directdownload.CheckUrlAnswer":{"templateSize":"(5.00 GB)<PHONE_NUMBER>","result":"true","wait":"0","bypassHostMaintenance":"false"}}] }

Updated unit tests to use the new constructor.

@blueorangutan package

@rohityadavcloud a [SF] Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: el9 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 6993

@blueorangutan test

@mlsorensen a [SF] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-7654)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 40486 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7948-t7654-kvm-centos7.zip
Smoke tests completed. 108 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File

@mlsorensen @nvazquez can you advice if this functionality is already covoured by the existing smoketests?


fix: Throw error if a required query param is nil

This PR updates our query provider logic to now throw an error if a required query parameter is nil.
Issue #

Description of changes

Scope

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Fixes https://github.com/awslabs/aws-sdk-swift/issues/686

I think there is room to improve our codegen here and move much of the logic to native swift. I refrained from doing this in this PR to limit the scope to simply fixing the bug and filed this issue to track the follow-up improvement work https://github.com/awslabs/smithy-swift/issues/471


Enable keyboard

Hello,
I use an app that uses your library, it displays SMS message at the bottom of the screen as well.
However, the app developer chose to disable keyboard.
The problem is i receive the OTP SMS on another phone
Can you help me to enable the keyboard?
Thanks.

Hello, I am not sure if I understood the question correctly. If the issue is related to reading an OTP from another device, this library doesn’t support that functionality. You might need to implement a method to communicate between the devices. On the other hand, if the issue is about disabling the keyboard after reading the OTP message, you could consider removing the function that hides the keyboard. Sharing code can also help.

Thanks for the quick reply.
My issue is the keyboard/paste from clipboard is disabled.
The app uses SMS Consent API that reads OTP then paste it sama as your mp4 video.
I receive the OTP on another phone so i want to enter it manually.
I don't have the app code, i downloaded it from Google Play Store then unpacked it using APKtool.
Unfortunately, i'm not a developer so i dunno which function i should remove.

I forgot to mention that i'm using Android on Raspberry PI 4 so no way to receive the OTP.
That's why i receive the OTP on another phone (non Android).

There are some ways to do this, but you can refer to here

I only found something like this in smali files
    sget-object v0, Landroidx/compose/ui/text/input/TextInputServiceAndroid$TextInputCommand;->HideKeyboard:Landroidx/compose/ui/text/input/TextInputServiceAndroid$TextInputCommand;
.method public static hideKeyboard(Landroid/view/View;Z)V
Anyway, i don't want to borther you with that anymore, i better buy a new Android phone.
Thank you.

No worry, If you have a chance to delete the line that calls hideKeyboard() function it may work. If you need any help you can contact me over discord.
username: _burkido

I don't seem to find your username on discord.
By the way, if you know how to send a verification code to the app in the below link then my problem will be solved as well.
https://www.headspin.io/blog/simulating-sms-messages-on-android


⚠ Fetchers has degraded performance

In b0a070b, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 341 ms

Resolved: Fetchers performance has improved in 19b6791.


Update z2ui5_cl_demo_app_123 new Element

Updated a sample for routes and legende

nice, looks great, thank you!


Display invalid email used by user in error message

Fixes https://github.com/aviaryan/timemandy/issues/1

Thanks @Monal5031


ci: retry  for curl

https://github.com/spidernet-io/spiderpool/issues/2479

CI FAIL : [It] About ifacer's e2e use cases


Handle multiple experiment data files

= Description =

Allow data files with multiple experiments to be imported and exported in the BioPreDyn software suite.

= Context =

Time series can contain more than one experiment per time point; importing and exporting such data sets should be possible. The biopredyn.result.Result class should handle that too.

= Success criteria =

Possibility to import / export data files with multiple experiments from / to NuML and CSV files.
Multiple experiment data can be converted to series of mean / variance tuples.

= Expected issues =

Will multiply the number of possible layouts in data files.

Imported from trac issue 53.  Created by bmoreau on 2014-09-11T14:42:44, last modified: 2014-10-01T11:37:58


Cannot connect to other external Rest API except servers.minetest.net

Hello,
My mod need to connect to another external rest API. It uses core.get_http_api(). It works fine with Minetest desktop, but failed with this minetest-wasm. Can you please point me how to fix this.
Thanks in advance.
P/S: In my test, with minetest-wasm, the core.get_http_api() can connect to servers.minetest.net, but not others.

This is a security feature. The proxy can only access servers.minetest.net and content.minetest.net

However, if you set up a server, the mod code runs on the server, and then your web client can just connect to that.


Operator standardization

Make a generic version of all graphblas operations
Use common populate methods for all operations and operators

Operations:

[x] Matrix Multiply
[x] Reduce to Vector
[x] Reduce to Scalar
[x] Union
[x] Intersect
[x] Update
[x] Apply
[x] Select

Some important things to note:

Operators are now listed by usage

unary1 are unary ops taking one argument (value)
unary3 are unary ops taking three arguments (value, row, column)
monoid2 are monoid ops taking two arguments (aVal, bVal)
binary2 are binary ops taking 2 arguments (leftVal, rightVal)
binary4 are binary ops taking 4 arguments (leftVal, rightVal, row, column)
binary5 are binary ops taking 5 arguments (leftVal, rightVal, row, column, overlap) -- these are only applicable for matrix multiplication in a semiring.

All usage of (row, column) above are called as (index, index) for vectors, meaning the code can use either row or column and the meaning will be the same for vectors. It's always just the index position. Passing it twice makes the API simpler.
Operators are also listed by operation. This lets each operation filter what operators make sense. For example, gt makes sense for intersection, but not union.
Thunks are handled by calling populateBinary, followed by code to grab the thunk argument from the block, replace all usages with the thunk, and then removing the argument from the block. This effectively turns it into a unary op, but keeps the definition consistent.
A new pattern has emerged for handling operation-specific custom operators (ex. select with probability). The custom operator must be handled in the non-generic lowering pass. Often, the custom operator affects deeply nested code. To avoid rewriting the outer loop, we write the outer loop(s) in a buildAlgorithm public function which accepts a function as an argument. The custom code is now injected by writing a function and passing it to buildAlgorithm. The generic operation uses the same buildAlgorithm to inject its code. See LowerSelectRewrite for an example of this pattern.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage remained the same at 82.978%

Files with Coverage Reduction
New Missed Lines
%

mlir_graphblas/engine.py
1
75.84%

mlir_graphblas/tests/test_profile.py
4
51.95%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3466

Relevant Lines:
4177

💛  - Coveralls

I'm happy with the code, so feel free to review it. I need to find and fix this segfault before merging.


Feature Request

Hello ,
I Like your Project Which Scans For SSL Vulnerabilties,
Hope you Won't Mind if i Ask for a Features Which Allow the Users to Give List of URL's to be Scanned !
Thanks!

Hello bro.
I think the same. I will make a plan.
thank you!

@arbazhussain149
update to a2sv v1.4.6 !
#> a2sv -f ./list.txt