binder and pybind11 packages

Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@copumpkin if I'm correct you're the llvm/clang expert here, so maybe you have a solution.
I'm packaging binder, and the following are the installation instructions:
# Create build dir
mkdir $HOME/prefix && cd $HOME/prefix

# Clone  LLVM
git clone http://llvm.org/git/llvm.git llvm && cd llvm
git reset --hard origin/release_38

# Clone Clang
cd $HOME/prefix/llvm/tools
git clone http://llvm.org/git/clang.git clang
cd clang && git reset --hard origin/release_38

# Clone Clang extra tools
cd $HOME/prefix/llvm/tools/clang/tools
git clone http://llvm.org/git/clang-tools-extra.git extra

# Create symlink pointing to binder/src dir
ln -s $HOME/binder/binder $HOME/prefix/llvm/tools/clang/tools/extra/binder

# Create ``llvm/tools/clang/tools/extra/CMakeLists.txt`` file with content: ``add_subdirectory(binder)``
echo 'add_subdirectory(binder)' > $HOME/prefix/llvm/tools/clang/tools/extra/CMakeLists.txt

# Build Binder
mkdir $HOME/prefix/build && cd $HOME/prefix/build
cmake -G Ninja -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_EH=1 -DLLVM_ENABLE_RTTI=ON .. && ninja

# At this point, if all above steps is succeseful, binder should be at
# $HOME/prefix/build/bin/binder

Nixpkgs provides clang and llvm, and clang is also built with the extra tools if I am correct.
Here, though, they use the extra tools repo to build binder. Could you suggest a better way to build binder than to build clang again?
If I just run cmake like I have in the current expression I get the following error:
$ nix-build -A python.pkgs.binder
these derivations will be built:
  /nix/store/417h1a5zkmjg26bxjnkvlkilj4rkh7g5-python2.7-binder-2017-03-27.drv
building path(s) ‘/nix/store/2xa90i07yvzf3jrzakgh9iw20r95bgwj-python2.7-binder-2017-03-27’
unpacking sources
unpacking source archive /nix/store/n2zfx0pg979sjqfg6nwv8nyim36mfsdc-binder
source root is binder/binder
setting SOURCE_DATE_EPOCH to timestamp 315619200 of file binder/binder/util.hpp
patching sources
configuring
fixing cmake files...
cmake flags: -DCMAKE_BUILD_TYPE=Release -DCMAKE_SKIP_BUILD_RPATH=ON -DCMAKE_INSTALL_INCLUDEDIR=/nix/store/2xa90i07yvzf3jrzakgh9iw20r95bgwj-python2.7-binder-2017-03-27/include -DCMAKE_INSTALL_LIBDIR=/nix/store/2xa90i07yvzf3jrzakgh9iw20r95bgwj-python2.7-binder-2017-03-27/lib -DCMAKE_INSTALL_NAME_DIR=/nix/store/2xa90i07yvzf3jrzakgh9iw20r95bgwj-python2.7-binder-2017-03-27/lib -DCMAKE_INSTALL_PREFIX=/nix/store/2xa90i07yvzf3jrzakgh9iw20r95bgwj-python2.7-binder-2017-03-27
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /nix/store/dqfikdyxdrykwcbg1wp6nd725y0c7va4-gcc-wrapper-5.4.0/bin/gcc
-- Check for working C compiler: /nix/store/dqfikdyxdrykwcbg1wp6nd725y0c7va4-gcc-wrapper-5.4.0/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /nix/store/dqfikdyxdrykwcbg1wp6nd725y0c7va4-gcc-wrapper-5.4.0/bin/g++
-- Check for working CXX compiler: /nix/store/dqfikdyxdrykwcbg1wp6nd725y0c7va4-gcc-wrapper-5.4.0/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:8 (add_clang_executable):
  Unknown CMake command "add_clang_executable".

CMake Warning (dev) in CMakeLists.txt:
  No cmake_minimum_required command is present.  A line of code such as

    cmake_minimum_required(VERSION 3.7)

  should be added at the top of the file.  The version specified may be lower
  if you wish to support older CMake versions for this project.  For more
  information run "cmake --help-policy CMP0000".
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Configuring incomplete, errors occurred!
See also "/tmp/nix-build-python2.7-binder-2017-03-27.drv-0/binder/binder/build/CMakeFiles/CMakeOutput.log".
builder for ‘/nix/store/417h1a5zkmjg26bxjnkvlkilj4rkh7g5-python2.7-binder-2017-03-27.drv’ failed with exit code 1
error: build of ‘/nix/store/417h1a5zkmjg26bxjnkvlkilj4rkh7g5-python2.7-binder-2017-03-27.drv’ failed

I wouldn't call myself an expert, but I've dealt with it a fair amount. Judging from their instructions, they might actually want the source to clang as opposed to a precompiled library/binary? It seems odd, but you could probably just make sure to drop the source files (i.e., just refer to .src) in the places the binder build expects to find them. I don't know if they then just use their build system to tell clang to build from scratch (which would suck) or if they just need to pull out a file or two, but I'd probably start that way, see what it expects to do, and then perhaps try patching up the build to use a prebuilt clang if we can.

Apparently building tooling for Clang is done like this according to the docs
https://clang.llvm.org/docs/LibASTMatchersTutorial.html
We need a Nix ninja it seems :)
I think the easiest solution here for me is to override clang-tools-extra_src to use the binder source with the additional cmake rule. If more programs start doing this we might want to keep the build directory and use that as input.

I got binder to build, and it seems to be working. The next issue I have is having it find headers. One can pass -I for includes and such.
Ideally, I would like it to support NIX_CFLAGS_COMPILE, making it more useful in a Nix expression. Therefore, I used wrapCC. Unfortunately, that seems to unset -fexceptions again.

Closing because I'm not working on this anymore.


[v3] Configure online editor

This issue is part of the migration to v3. You can read full details about the various changes here.
In Exercism v3, students can now choose to work on exercises directly from their browser, instead of having to download exercises to their local machine. The track-specific settings for the in-browser editor are defined in the top-level "online_editor" field in the track's config.json file. This field is defined as an object with two fields:

"indent_style": the indent style, either "space" or "tab".
"indent_size": the indent size, which is an integer (e.g. 4).

You can find a full description of these fields in the spec.
Goal
The "online_editor" field should be updated to correspond to the track's best practices regarding indentation.
Example
"online_editor": {
  "indent_style": "space",
  "indent_size": 4
}

Tracking
https://github.com/exercism/v3-launch/issues/2

I threw a few files through dfmt, and the config that is present in config.json seems to be dfmt's default.

@0x647262 Thanks a lot for checking!


[Bug]: Toggling the native property on a dropdown results in null errors

Describe the bug
Toggling the native property on a dropdown results in null errors
Uncaught TypeError: _rootEL is undefined

Provide Code
<GoADropdown name="colors" value="red" onChange={()=>{}} native={true}>
  <GoADropdownItem value="red" label="Red" />
  <GoADropdownItem value="green" label="Green" />
  <GoADropdownItem value="blue" label="Blue" />
</GoADropdown>

To Reproduce

Use the existing deployment of the code sandbox
Go to the Dropdown  Component page
Toggle native on and off, you should see the error come up in console

What browsers are you seeing the problem on?
Chrome
Firefox

Complete

:tada: This issue has been resolved in version 4.12.1 :tada:
The release is available on:

npm package (@BUGFIX dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.12.1 :tada:
The release is available on:

npm package (@BUGFIX dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.0.0-alpha.174 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.0.0-alpha.211 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.4.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.13.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.5.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.13.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 2.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 4.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.5.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BUG] docker-composer: It's not possible to reutilize image built by another service

Let's say I have the following docker-compose file:
service1:
build:
context: .
dockerfile: ./Dockerfile
image: service1:latest
service2:
build:
context: ./service2/
dockerfile: ./Dockerfile
depends_on: ["service1"]
In this docker-compose, I'm building the service1 image and tagging it as "service1:latest". So logically I should be able to use it in the Dockerfile of service2, like this:
service2 dockerfile:
FROM service1:latest
I have tested locally and it works as expected, however, it does not work on Infrabox.
Why??
First: the image of "service1" is tagged with a weird prefix other than the tag I defined. Example:
ha-eu-de-1.infrabox.datahub.only.sap/project-id/my-job/service1
Second: When building the image of service2, I get the following error:
failed to build: pull access denied for service1, repository does not exist or may require 'docker login'

Check this link which reproduces the bug: https://infrabox.datahub.only.sap/dashboard/#/project/datahub-flowagent/build/6149/1/job/integration-tests


Weird behavior

Hi,
I'm having a weird result when comparing those two string.
It always return a rating of 0 despite them having 2 letters in common.
stringSimilarity.compareTwoStrings('NOS', 'NPS')
//0
stringSimilarity.findBestMatch('NOS', ['NPS'])
//{ ratings: [ { target: 'NPS', rating: 0 } ], bestMatch: { target: 'NPS', rating: 0 } }
https://runkit.com/588655d7fb7a220014a01b47/5886577d0629220014e341d7
Thanks.

That's how the algorithm works -
NOS is split into two bigrams NO and OS
NPS is split similarly into NP and PS
There are no common bigrams, hence similarity is 0
Further reading: https://en.wikipedia.org/wiki/Sørensen–Dice_coefficient#Formula

Ah I guess I should have read more on the algoritm.
I ended up using this instead and it did what I wanted.
https://www.npmjs.com/package/leven
Thanks for the answer.


Leukemia patient

Opening a PR to be able to code review

I'd suggest your configure your git author / git email, btw :)

Not ready to merge until fixed I think please consider contributing to non-main and rollback the merge https://github.com/imallona/rock_roi_paper/pull/10 @gimoro

attempt to reopen


Small typo in Makefile

Hello,
I noticed this small typo in your Makefile, do you mean shell find ...?
https://github.com/sjl/necro/blob/d72e8e894ceaeb14ce2e1199b5ba7d74f7812b47/Makefile#L10

Nope, ffind is my own file finder: https://github.com/sjl/friendly-find


Fix minor typo in documentation

Just a minor fix to documentation.
Thanks!

Thank you! :green_heart:


Failed to connect to Jupyter notebook Kernel Python 3 is not usable.

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

Create a new .ipynb file

Actual behavior

Starting Jupyter server: Starting Jupyter Notebook

Failed to connect to Jupyter notebook. http://localhost:8888/

Error: Kernel Python 3 is not usable. Check the Jupyter output tab for more information.

Source: Python (Extension)

Expected behavior

Local server would start and allow execution of Jupyter Notebook cells

Your Jupyter and/or Python environment
Please provide as much info as you readily know

Jupyter server running: Local | Remote | N/A

Local

Extension version: 20YY.MM.#####-xxx

VS Code version: #.##

Setting python.jediEnabled: true | false

WHERE? HOW?

Setting python.languageServer: Jedi | Microsoft | None

WHERE? HOW?

Python and/or Anaconda version: #.#.#

user5@system5:~/Documents$ python --version
Python 2.7.18rc1
user5@system5:~/Documents$ python3 --version
Python 3.8.5

OS: Windows | Mac | Linux (distro):

user5@system5:~/Documents$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal

Virtual environment: conda | venv | virtualenv | N/A | ...
N/A

Python Output

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

Hi @SeaDude, thanks for reporting a bug and apologies for the trouble. Would you mind providing the contents of the Jupyter output tab, as that should contain more specific information about what went wrong? You can locate the output tab as follows:

Sure thing!
Starting Jupyter from /usr/bin/python with command line --no-browser --notebook-dir="/home/user5/Documents" --config=/tmp/f96a2665-b386-4d2d-82c6-fd45c077aff8/jupyter_notebook_config.py --NotebookApp.iopub_data_rate_limit=10000000000.0
[I 13:34:53.433 NotebookApp] Serving notebooks from local directory: /home/user5/Documents
[I 13:34:53.434 NotebookApp] The Jupyter Notebook is running at:
[I 13:34:53.434 NotebookApp] http://localhost:8888/?token=4b6097d7557db2c380834baeb78ec28df3d2b4c28627c902
[I 13:34:53.434 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 13:34:53.438 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///home/user5/.local/share/jupyter/runtime/nbserver-6170-open.html
    Or copy and paste one of these URLs:
        http://localhost:8888/?token=4b6097d7557db2c380834baeb78ec28df3d2b4c28627c902
[I 13:34:53.753 NotebookApp] Creating new notebook in /
[I 13:34:53.806 NotebookApp] Kernel started: 6a615421-5b13-4129-92ad-dd5b11dae8aa
[W 13:34:53.815 NotebookApp] delete /t-ad8f2d10-69f1-4d52-9549-514f77e107c2.ipynb
/usr/bin/python3: No module named ipykernel_launcher
[I 13:34:56.804 NotebookApp] KernelRestarter: restarting kernel (1/5), new random ports
/usr/bin/python3: No module named ipykernel_launcher
[I 13:34:59.809 NotebookApp] KernelRestarter: restarting kernel (2/5), new random ports
/usr/bin/python3: No module named ipykernel_launcher
[I 13:35:02.821 NotebookApp] KernelRestarter: restarting kernel (3/5), new random ports
/usr/bin/python3: No module named ipykernel_launcher
[I 13:35:05.832 NotebookApp] KernelRestarter: restarting kernel (4/5), new random ports
/usr/bin/python3: No module named ipykernel_launcher
[W 13:35:08.841 NotebookApp] KernelRestarter: restart failed
[W 13:35:08.842 NotebookApp] Kernel 6a615421-5b13-4129-92ad-dd5b11dae8aa died, removing from map.
[C 13:35:13.799 NotebookApp] received signal 15, stopping
[I 13:35:13.800 NotebookApp] Shutting down 0 kernels

Just a heads up, Jupyter notebooks in VS Code worked great until recently. Things that recently changed: Upgraded Ubuntu and updated VS Code to latest versions.

Aha! Well this little output window helped out. I was unaware of this feature in VS Code.
Looks like the recent upgrade to Ubuntu 20 "knocked something loose" in my Python 3 install.
Fix:

sudo apt install python3-pip
pip3 install ipykernel

Result: Notebook now running as intended. Output:
Starting Jupyter from /usr/bin/python with command line --no-browser --notebook-dir="/home/user5/Documents" --config=/tmp/018cfca2-dc60-4b83-8d91-8e57f3e40541/jupyter_notebook_config.py --NotebookApp.iopub_data_rate_limit=10000000000.0
[I 13:54:38.750 NotebookApp] Serving notebooks from local directory: /home/user5/Documents
[I 13:54:38.750 NotebookApp] The Jupyter Notebook is running at:
[I 13:54:38.750 NotebookApp] http://localhost:8888/?token=0c39e77ecf1186e813caf7f813bc7fe63fcf3a48be4b2701
[I 13:54:38.750 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 13:54:38.753 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///home/user5/.local/share/jupyter/runtime/nbserver-7248-open.html
    Or copy and paste one of these URLs:
        http://localhost:8888/?token=0c39e77ecf1186e813caf7f813bc7fe63fcf3a48be4b2701
[I 13:54:39.086 NotebookApp] Creating new notebook in /
[I 13:54:39.134 NotebookApp] Kernel started: 37d9ed77-6db2-4f3d-b5e0-939ce733039b
[W 13:54:39.143 NotebookApp] delete /t-97898323-51d4-4eac-aa4d-03909c0319ad.ipynb
/usr/bin/python3: No module named ipykernel_launcher
[I 13:54:42.133 NotebookApp] KernelRestarter: restarting kernel (1/5), new random ports
/usr/bin/python3: No module named ipykernel_launcher
[I 13:54:45.141 NotebookApp] KernelRestarter: restarting kernel (2/5), new random ports
/usr/bin/python3: No module named ipykernel_launcher
[I 13:54:48.152 NotebookApp] KernelRestarter: restarting kernel (3/5), new random ports
/usr/bin/python3: No module named ipykernel_launcher
[I 13:54:51.158 NotebookApp] KernelRestarter: restarting kernel (4/5), new random ports
/usr/bin/python3: No module named ipykernel_launcher
[W 13:54:54.168 NotebookApp] KernelRestarter: restart failed
[W 13:54:54.169 NotebookApp] Kernel 37d9ed77-6db2-4f3d-b5e0-939ce733039b died, removing from map.
[C 13:54:59.123 NotebookApp] received signal 15, stopping
[I 13:54:59.123 NotebookApp] Shutting down 0 kernels
Starting Jupyter from /usr/bin/python with command line --no-browser --notebook-dir="/home/user5/Documents" --config=/tmp/d5d43df3-4b9e-4c96-be1e-ea9dc173a03b/jupyter_notebook_config.py --NotebookApp.iopub_data_rate_limit=10000000000.0
[I 13:58:05.636 NotebookApp] Serving notebooks from local directory: /home/user5/Documents
[I 13:58:05.636 NotebookApp] The Jupyter Notebook is running at:
[I 13:58:05.636 NotebookApp] http://localhost:8888/?token=829930c8e8e69746ba84ad40ac18bafe6a936434e479351a
[I 13:58:05.636 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[C 13:58:05.639 NotebookApp]

    To access the notebook, open this file in a browser:
        file:///home/user5/.local/share/jupyter/runtime/nbserver-9941-open.html
    Or copy and paste one of these URLs:
        http://localhost:8888/?token=829930c8e8e69746ba84ad40ac18bafe6a936434e479351a
[I 13:58:07.418 NotebookApp] Creating new notebook in /
[I 13:58:07.533 NotebookApp] Kernel started: 6de927a7-0e6b-413a-8e35-bcf0f69db2dc
[W 13:58:07.553 NotebookApp] delete /t-bea71f88-06a7-4d2c-9882-e0b0916688bd.ipynb
[I 13:58:08.060 NotebookApp] Creating new notebook in /jupyter
[I 13:58:08.086 NotebookApp] Kernel started: e55132a2-69b5-4a3d-8a35-7739eb8805ad
[W 13:58:08.095 NotebookApp] delete /jupyter/t-4409e58f-3942-4be9-a59b-8cdf1e1f9bf8.ipynb
[I 13:58:08.650 NotebookApp] Creating new notebook in /jupyter
[I 13:58:08.682 NotebookApp] Kernel started: 0ddb9eb0-cc9b-4d30-a79c-8abc03bcf2b0
[W 13:58:08.698 NotebookApp] delete /jupyter/t-ac09ef51-399a-4fb0-a4a4-4d5771c4a60e.ipynb


maybe you could use godep manage third dependency

Yeah, this is something we're looking into. We'll probably have dependencies pinned down before we reach 1.0.

Just interesting, what you think about using gb tool?

gb is a good tool. When I tried it, it didn't support cross-compilation which was a show-stopper. It does now, so I need to try again. I'm also waiting to see how the Go 1.5 vendor experiment goes.

@mholt checkin vendor to VCS feels so rude, just discovered glide which just locks version of deps (thinking using it for my projects too).

Nice. Yeah, and with Caddy we have somewhat of a unique situation since builds are done live in production. The updated build server that I've already started working on sort of does its own dependency management.

We might use the Go tool vendor feature coming with Go 1.6, so I'm going to close this. Vendoring at least certain dependencies is something I'll be looking into.


[Suggestion] Set name of active consolidated plugin based on chosen plugin inside of consolidated.

Hi, I actually don't know if it is possible at all, but it would be pretty cool if plugin could somehow rename its active instance, based of what plugin running inside of consolidated.
Example, If I put a lot of Consolidated plugins on mix, especially several on each channel, then I need to click on each of it, to found out what plugin is there. Since every plugin shows up on channel as Consolidated.
Since it would probably rely on DAW, and every DAW functions differently, I doubt that is even possible, but if it is...

Example DAW on picture: Reaper 7
I could rename every instance each time manually, buuttt.... I better then simply using individual plugins, rather than consolidated.

Yeah alas the daw APIs do not have a mechanism to rename the plugin. You are not the first to ask but I can’t figure out how to do this


refactor: use core/enable_if.hpp over utility.hpp

The later is deprecated. From utility.hpp:

// Use of this header is discouraged and it will be deprecated.
// Please include one or more of the headers below instead.

Superseded by: https://github.com/boostorg/odeint/pull/63


Transparency / Cutout doesn't work when entering AR preview

Description
I'm not sure how the model-viewer and ARCore interact, so not sure whether this is actually an ARCore issue and not for here. Still, currently it seems that having transparent textures on objects breaks when entering AR preview (and subsequently AR view).

Model-Viewer (note the circles + triangles)

AR Preview (note the black borders)

AR View (note the black borders)
Live Demo
https://cobalt-gondola.glitch.me/
Browser Affected
I guess all on Android, tested with Chrome
OS

[X] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[ ] Windows

Also posted this in https://github.com/google-ar/arcore-android-sdk/issues/796

Thanks @soraryu . This looks like an ARCore issue, not a <model-viewer> issue. I'll ask for feedback on this from the Scene Viewer folks.

@cdata, did you hear back from the Scene Viewer team? No one responded on the ar-core repo so far.

@soraryu Yah, sorry for letting this fall off the radar. This was determined to be a Scene Viewer bug, and work has been assigned to fix it.

Any news about this? Or a workaround to get transparency working? I know this is not a model viewer issue but noone had reacted at all in the ARCore repo. Please poke them again...

Hi @soraryu I regret that this issue has been assigned but not yet fixed. I'll follow-up with the team and let you know if there is anything else I can share.

After circling back with the team, I understand that the issue has been fixed (the bug wasn't updated to reflect this) and you should see it when ARCore updates to v1.11.

I can confirm this is fixed in v1.11. Thanks!


Clarify which API classes must be available to users

Description
The spec is not explicit about which classes and packages should be available to applications.
The closest I can find is this:

This document and implementations MUST comply with the following OpenTelemetry 1.13 specifications:

OpenTelemetry Overview
Tracing API
Baggage API
Context API
Resource SDK

The spec has several examples of using API classes, and the TCK also assumes that the autoconfigure SPI is available as the InMemorySpanExporterProvider implements one of its interfaces.
The spec should be more explicit about which API classes are required and we should have TCK tests to assert that they are available.

This involves spec clarification and TCK verification (load the classes and/or use the classes).

In the next call, we will work out the list of API classes to be exposed under this spec.

Here are the API packages I think are required.
Tracing API

io.opentelemetry.api
io.opentelemetry.api.trace
io.opentelemetry.api.common

Note: io.opentelemetry.api does depend on io.opentelemetry.api.metrics and io.opentelemetry.api.logs, though we only support the parts of it that relate to tracing.
Baggage API

io.opentelemetry.api.baggage
io.opentelemetry.api.baggage.propagation

Context API

io.opentelemetry.context
io.opentelemetry.context.propagation

Resource SDK

io.opentelemetry.sdk.resources

Autoconfigure SPI
This is the programmatic interface that allows users to register extensions when using the SDK Autoconfigure Extension (which we use for configuration). The spec currently isn't clear about whether or not support for the SPI is required, but the TCK currently requires it to register a SpanExporter.

io.opentelemetry.sdk.autoconfigure.spi
io.opentelemetry.sdk.autoconfigure.spi.traces
these then depend on the following packages

io.opentelemetry.sdk.trace
io.opentelemetry.sdk.trace.data
io.opentelemetry.sdk.trace.export
io.opentelemetry.sdk.trace.samplers
io.opentelemetry.sdk.common

WithSpan annotation
I see this now also contains an AddingSpanAttributes annotation which sets attributes on the current span without creating a new one. We should decide whether to support that.

io.opentelemetry.instrumentation.annotations

Semantic Conventions
We say that the implementation needs to follow semantic conventions. It makes sense to also expose the semantic convention APIs to the user. The TCK currently requires that these APIs are available, though we could change the TCK to package the classes in the test application.
Note that these packages are not stable.

io.opentelemetry.semconv.trace.attributes
io.opentelemetry.semconv.resource.attributes

@Azquelt since we are not sure which spec version we should link to, it might be problematic to link to the spec with a particular release version. We can discuss how best to provide the info on the call.

All of the links that I've provided above link to opentelemetry-java javadoc (or opentelemetry-java-instrumentation for the annotations), not to the opentelemetry spec.
I assume we're going to specify either a minimum version of opentelemetry-java, or a version of opentelemetry-java which implementations must be compatible with, in which case we can link to that version.

I wonder if we could divide the tests and, therefore, the required packages in 2 types:

end users.
integrators.


Mico benchmarks for two bitmap index equal query cases

What changes were proposed in this pull request?
This micro benchmarks are to test the functionality and performance
of directly traversing the row IDs in fiber caches of bitmap index file.
The first case is to just traverse the row IDs in one single fiber caches.
The second case is to traverse the row IDs across multi fiber caches
How was this patch tested?
mvn clean test package and all the test passed.

@carsonwang @yueawang @adrian-wang @linhong-intel Please help review when you are available. Thanks.

The first three are created in another PR #637. Please help review. Thanks.

This PR will be removed finally, because it's covered by #637 and #638. Thanks.


Comparasion with vllm

vllm can boost up to 24x compare with vanilla llama version, does lmdeploy have any speed test compare with it?

Mark, I tested Vllm, about 2x the performance of deepspeed.

@lucasjinreal why close this ...?

I have using vllm got a reasonable performance, there is no need to adopt other framework. Furturemore, one can expect TensorRTLM next month, which could be a killer in LLM faster inference.

Hi @KimmiShi,
Can you share some information about your test setting? Based on our setting, vllm is slower than deepspeed.

vllm's default benchmark uses sharegpt data and include input token in throughput computation.
For deepspeed and vllm, we use a batch of fake data and let the model generate to its max length (2048 new tokens for llama-7b), and compute only throughput of newly generated data. Vllm is only about half throughput of deepspeed.

It's import possible deepspeed faster than vllm, they are essentially different things. Just try PagedAtten, it's way more faster than you think.

It's impossible deepspeed faster than vllm, they are essentially different things. Just try PagedAtten, it's way more faster than you think.

How much throughput do you achieve with vllm (say on single A100)?

I have using vllm got a reasonable performance, there is no need to adopt other framework. Furthermore, one can expect TensorRTLM next month, which could be a killer in LLM faster inference.

Hello, could you please share some information about “ TensorRTLM” project? Haven’t found any info about it: no articles, no announcements - nothing :(

I have using vllm got a reasonable performance, there is no need to adopt other framework. Furthermore, one can expect TensorRTLM next month, which could be a killer in LLM faster inference.

Hello, could you please share some information about “ TensorRTLM” project? Haven’t found any info about it: no articles, no announcements - nothing :(

+1

killer

It's a secret project that has not announced yet. They give some companies tryout. Maybe in this month. But I don't think it any better than FT.

vLLM does not support quantization yet. How's the comparison performed? Are we comparing both under float16 precision?

vllm has little optimization about speed. only for throughput.
The advantage is paged attention which uses less GPU memory, and continuous batching which gives higher GPU occupancy.
But as the implementation is almost all in python, the GPU utilization is not high, maybe 80%.
Just test it yourself.
lmdeploy uses more GPU memory, but the kernels are more performant.

Hi i'm the maintainer of LiteLLM and we allow you to maximize throughput by load balancing between multiple LLM endpoints.
Thought it would be useful for people on this thread, I'd love feedback if not
Here's the quick start, to use LiteLLM load balancer (works with 100+ LLMs)
doc: https://docs.litellm.ai/docs/simple_proxy#model-alias
Step 1 Create a Config.yaml
model_list:
- model_name: openhermes
  litellm_params:
      model: openhermes
      temperature: 0.6
      max_tokens: 400
      custom_llm_provider: "openai"
      api_base: http://<IP_ADDRESS>:8000/v1
- model_name: openhermes
  litellm_params:
      model: openhermes
      custom_llm_provider: "openai"
      api_base: http://<IP_ADDRESS>:8001/v1
- model_name: openhermes
  litellm_params:
      model: openhermes
      custom_llm_provider: "openai"
      frequency_penalty : 0.6
      api_base: http://<IP_ADDRESS>:8010/v1

Step 2: Start the litellm proxy:
litellm --config /path/to/config.yaml

Step3 Make Request to LiteLLM proxy:
curl --location 'http://<IP_ADDRESS>:8000/chat/completions' \
--header 'Content-Type: application/json' \
--data ' {
      "model": "openhermes",
      "messages": [
        {
          "role": "user",
          "content": "what llm are you"
        }
      ],
    }
'

hello, but is LMDeploy still faster than vllm at this time, in fp16?

Here is the benchmark result on A100(80G) with llama3-8b.


Setting up develop environment for Android fails

After setting up server host in my Android phone according to http://facebook.github.io/react-native/docs/running-on-device-android.html#content, I got the following error message when running UIExplorer example.

[15:12:14]  request:/Examples/UIExplorer/UIExplorerApp.android.bundle?platform=android
[15:12:14]  find dependencies
[15:12:14]    find dependencies (221ms)
[15:12:14]  transform
transforming [========================================] 100% 349/349
[15:12:14]    transform (223ms)
[15:12:14]    request:/Examples/UIExplorer/UIExplorerApp.android.bundle?platform=android (501ms)
::ffff:<IP_ADDRESS> - - [Tue, 13 Oct 2015 07:12:18 GMT] "GET /flow/ HTTP/1.1" 404 - "-" "okhttp/2.4.0"

MAC OS X 10.11
node version 4.2.0
Android phone LG G2
Android version 4.2.2.

+1

@YorkShen it is not 'error'  ,you'd better take a screenshot of the redbox on your phone,that's the real error message .

@sospartan The App just crashed on my phone.

@YorkShen get stack trace from logcat .

@sospartan

--------- beginning of /dev/log/system
--------- beginning of /dev/log/main
W/ReactNativeJS( 8860): 'Warning: Native component for "RCTModalHostView" does not exist'
D/ReactNativeJS( 8860): 'Running application "UIExplorerApp" with appParams: {"initialProps":{},"rootTag":1}. DEV === true, development-level warning are ON, performance optimizations are OFF'

Problem fixed.
The UIExplorer still have dependencies of React Native 0.11, which will cause the problem above and the logcat is shown as following.

TypeError: expected dynamic type 'string', but had type 'int64

To fix this problem, one can follow the comment of https://github.com/facebook/react-native/issues/3033#issuecomment-146604308


feat: how it works section

Feature Request
Feature Proposal
Develop the "How it works", the fourth section of the landing page following the Figma design:

Closed by #25


NNVM fails to convert the onnx graph

Loading pretrained onnx model using nnvm.frontend.from _onnx() fails with error.
The model is based on MNIST dataset using chainer ,onnx-chainer framework example
onnx graph representation :
graph Graph (
%1828376209840[FLOAT, 1x784]
) initializers (
%/l3/b[FLOAT, 10]
%/l3/W[FLOAT, 10x100]
%/l2/b[FLOAT, 100]
%/l2/W[FLOAT, 100x100]
%/l1/b[FLOAT, 100]
%/l1/W[FLOAT, 100x784]
) {
%1828376210792 = FC[axis = 1, axis_w = 1](%1828376209840, %/l1/W, %/l1/b)
%1828376210960 = Relu(%1828376210792)
%1828376211072 = FC[axis = 1, axis_w = 1](%1828376210960, %/l2/W, %/l2/b)
%1828376211240 = Relu(%1828376211072)
%1828376211296 = FC[axis = 1, axis_w = 1](%1828376211240, %/l3/W, %/l3/b)
return %1828376211296
}
nnvm.frontend.from_onnx() error :
File “C:\NNVM\NNVM\master\nnvm\python\nnvm_ctypes\symbol.py”, line 181, in creator
ctypes.byref(sym_handle)))
File “C:\NNVM\NNVM\master\nnvm\python\nnvm_base.py”, line 75, in check_call
raise NNVMError(py_str(_LIB.NNGetLastError()))
nnvm._base.NNVMError: Required parameter units of int is not presented, in operator dense(name="")
Looks like dense operator needs  hidden units of the dense transformation ?
Any help is much appreciated
Thanks

units are inferred inside the front end.
Pls ref https://github.com/dmlc/nnvm/blob/d182c5398096e23346661ae8902a9ecd1d6d238c/python/nnvm/frontend/onnx.py#L385

Hi
Looks like "  _fully_connected(opset) "   method for dense operator is unused ?
(which internally calls " _infer_channels(... )" )
https://github.com/dmlc/nnvm/blob/d182c5398096e23346661ae8902a9ecd1d6d238c/python/nnvm/frontend/onnx.py#L396
So as temporary fix changed:
https://github.com/dmlc/nnvm/blob/d182c5398096e23346661ae8902a9ecd1d6d238c/python/nnvm/frontend/onnx.py#L426
to
  'FC': _fully_connected(opset),

Now nnvm.frontend.from_onnx()  passed . Is this fix ok ?


Fix engine app startup

The engine app currently adds two TMS layers and then immediately checks to make sure that their status isn't failed, but this causes the app to error out and not start up correctly.  Comparing the engine code to the demo app, it appears that the TMS layers are supposed to be loaded later in the startup process and so they're going to start out with the "layer closed" status.  Removing this check allows the engine app to start up and run correctly.
Without this fix, this is the output from the engine app (and then it exits):
[vsg info] texel_margin = 12
[vsg info] quad_margin = 6
[rocky info] Hello, world.
[rocky info] Welcome to rocky version 0.4.1
[rocky info] Using VSG 1.1.7 (so 14)
[rocky warning] Problem with layer "" : Layer closed

Thanks!


can't go get

my go version is :

this is os api issue, I think Windows did not support SysProcAttr, I will try fix this.

OK ,Thanks


Dark theme 17.04.2023

List of tasks:

resolved #70

@InnaLazarenko, everything looks good. My only suggestion is to not apply custom background-color and box-shadow for the header in dark mode.

@InnaLazarenko, everything looks good. My only suggestion is to not apply custom background-color and box-shadow for the header in dark mode.

'+


Implement test and fixture modifiers

Features summary
test.only, test.skip, fixture.only, fixture.skip (closes #246)
You can now skip specific fixtures or tests using .skip modifier. In contrast, you can run only specified tests or fixtures using .only directive.
.skip example:
fixture.skip `Fixture1`; // All tests in this fixture will be skipped

test('Fixture1Test1', () => {});
test('Fixture1Test2', () => {});

fixture `Fixture2`;

test('Fixture2Test1', () => {});
test.skip('Fixture2Test2', () => {}); // This test will be skipped
test('Fixture2Test3', () => {});

.only example:
fixture.only `Fixture1`;
test('Fixture1Test1', () => {});
test('Fixture1Test2', () => {});

fixture `Fixture2`;

test('Fixture2Test1', () => {});
test.only('Fixture2Test2', () => {});
test('Fixture2Test3', () => {});

// Only tests in Fixture1 and Fixture2Test2 will run

Note that reporter plugin now accepts additional skipped field in testRunInfo object, thus plugin now can decorate skipped tests in the distinct manner. All built-in reporters and plugin generator were updated to support this feature.
test.before and test.after hooks (closes #1108)
Test now supports test.before and test.after hooks that behave the same way as  fixture.beforeEach and fixture.afterEach hooks with the exception that hook will run only for the specified test. If fixture.beforeEach and fixture.afterEach hooks are specified as well, test-specific hook will override them.
Example:
fixture `Fixture1`
    .beforeEach(async t  => {...})
    .afterEach(async t  => {...});

test
    .before(async t => {...}) // Overrides fixture.beforeEach
   ('Test1', async t => {...});

fixture `Fixture2`;

test
    .after(async t => {...})
    .before(async t => {...})
    ('Test2', async t => {...});

Note for tech writers: Current fixture.beforeEach and fixture.afterEach hooks section in documentation is not quite accurate. It's worth mentioning that hooks are run for each test run of the given test. So e.g., if we have 3 browsers set for the test run, each hook will be executed in each browser right before and after the test.
t.ctx object (closes #841)
t.ctx is an object that is shared between  fixture.beforeEach, fixture.afterEach, test.before, test.after hooks and test itself. Each test run has it's own t.ctx object. This object can be used to share variables and other test-specific stuff between test functions without introducing global variables  (it's even more complicated in TestCafe since single test can be run in several browsers).
Example:
fixture `Fixture1`
    .beforeEach(async t  => {
          t.ctx.someVar = 123;
     })
    .afterEach(async t  => {
          console.log(t.ctx.someVar); // > 123
    });

test
    .before(async t => {
         console.log(t.ctx.someVar); // > 123
    })
   ('Test1', async t => {
        console.log(t.ctx.someVar); // > 123
   });

By default t.ctx is initialized to empty object without prototype (so it's safe to iterate its keys without hasOwnProperty check). However, you can assign anything to t.ctx and assigned value will be shared, e.g.:
t.ctx = 123;

test.page directive (closes #501)
You can now specify startup page for the particular test that will override page specified for the fixture. It was possible previously to navigate to the specific page in the test by calling t.navigateTo, but it had a drawback that test first navigated to the page specified for the fixture. Additional navigation now avoidable with test.page directive.
Example:
fixture `Some fixture`
    .page `http://page1`;

test('Test1', () => {}); // Will navigate to http://page1
test
    .page `http://page2`
   ('Test2', () => {}); // Will navigate to http://page2

test.httpAuth directive (closes #1109)
In addition to newly introduced HTTP authentication feature (#955) it's now possible to specify authentication credentials for particular test. If credentials are specified for fixture as well, they will be overridden by test-specific credentials.
Example:
test
    .httpAuth({ username: 'hey', password: 'yo' })
    ('Some test', async t => {});

Note that you can specify fixture and test directives before and after declarations, so all this cases are valid:
fixture.skip `Fixture name` .beforeEach(() => {});

fixture
    .page `http://page`
    `Fixture name`;

test
   .before(() => {})
   ('Test name', () => {})
   .after(() => {});

test('Some test', () => {}).skip;

\cc @helen-dikareva @AlexanderMoskovkin @churkin @AndreyBelym @lexkazakov @VasilyStrelyaev

Note for tech writers: Current fixture.beforeEach and fixture.afterEach hooks section in documentation is not quite accurate. It's worth mentioning that hooks are run for each test run of the given test. So e.g., if we have 3 browsers set for the test run, each hook will be executed in each browser right before and after the test.

I feel like it can be excessive. Test runs are our internal stuff. We should just say: "Your test needs some initialization code? Put it here!", And it is our job to ensure that it runs in every browser. Users shouldn't bother.


mmd2tex Translating to wrong beginning smart quote on multi-paragraph dialogue

When translating a multi-paragraph dialogue like this:
"Hi, Martin. Nice suit.

"Also, what about that vacation?"

The text is translated like this:
"Hi, Martin. Nice suit.

``Also, what about that vacation?''

Keeping the unsmart quote on the first line. LaTeX will then translate this into an ending quote, which looks strange at the beginning of a line. It should be translated by mmd2tex as:
``Hi, Martin. Nice suit.

``Also, what about that vacation?''

The first paragraph only has a single double quote, therefore it is not a smart quote (from a computer standpoint, not an English grammar standpoint).  So it is properly left alone.
If this is a construct you use often (I never use it), you could modify MMD to handle it however you desire, or use the double apostrophe syntax manually instead of the lone double quote -- they will be left alone and handled properly by LaTeX (but would not appear correctly in HTML):
``Hi, Martin.  Nice suit.

Otherwise, I think this is an edge case that will not be specifically handled by MMD.


Spacewalk Upgrade to Polkadot version 0.9.42

This PR updates the Spacewalk dependencies to 0.9.42 and adds changes to correspondingly to the code. This is related to this issue.
Some notable changes can be found in testchain/node/src/service.rs where the WasmExecutor had changed in between version, and the 4 new parameters required for the pallet balances.
Also,substrate-stellar-sdk was required to be updated, which is done in branch polkadot-v0.9.42.

rerunning the CI,

https://github.com/pendulum-chain/spacewalk/pull/495 has to be closed BEFORE CLOSING this.

I'll merge this without CI passing because the job probably failed because our SatoshiPay Stellar archives are currently broken.


Bjorncs/athenz identity provider service endpoint

We'll have to figure out a better way of determining the hostname later on.

java build succeeded


Cannot resolve debugger dependency

While setting up ballast I'm not able to properly define the debugger dependency. I always get the following error while syncing:
Could not find io.github.copper-leaf:ballast-debugger:4.0.0

I did a quick maven artifact search and the artifact indeed isn't available. There are some ballast related debug artifacts (ending with android-debug, but I'm not sure those are the same.

Alright, looks like the docs need some updating - the correct dependency is io.github.copper-leaf:ballast-debugger-client:4.0.0. 🤓

Reopening as @cjbrooks12 likely wants to update the docs before closing.

The docs are now updated
https://copper-leaf.github.io/ballast/wiki/modules/ballast-debugger/#installation


Firestore Samples

Work in progress - please note that add_data.rb's update_nested_fields and delete_data.rb's delete_collection currently do not work because of ongoing issues.
However, would appreciate any style suggestions in the meantime! First time doing Ruby in a while.

@frankyn Ready for another round of review - all ~50 samples are here now (tests coming soon). Thanks!

@frankyn Made all the code review style changes and testing changes. Ready for final review!

Yes, once the latest changes from master are merged, Kokoro should work.

Thanks @tbpg!, Pending Ryan to rebase branch.

cool, made all the changes

Pending KokoroCI.

@tbpg, firestore tests require a separate set of projects because Datastore and Firestore can't be enabled in the same project. :disappointed: At the moment, secrets.sh sets FIRESTORE_PROJECT_ID for these tests and may cause an issue as they're not designed for parallel runs.
@ryanmats, update helper method names to be different than method names used for samples, there's a conflict and the tests are calling the sample version of delete_collection.

Did the tests fail from running in parallel? The Go ones are OK. But, I can set up another Ruby Firestore project pool if necessary.

@tbpg no, the issue is coming from the tests using a helper method that has the same name as a sample method name.

latest commit should fix the helper method issue.

forgot to commit revised helpers.rb file which was causing failures - let's see how the tests run now

I'm working on increasing the quota. Will update when it's ready. You can force-submit if it's urgent since 2/3 projects are passing (and the 3rd is because of quota).

@ryanmats can you rebase to merge?


docs: add react-native usage guide

Attempts to address #472

LGTM! Anything else you wanna add or is this okay to merge? (asking because it's marked as a draft)

I wanted to add in a react-native example app with expo, but have run into issues setting up the expo app in the monorepo and haven't yet resolved it. We can have this merged and I could raise a new PR for the example once I have it ready.
I have the code here - https://github.com/VinitSarvade/tanstack-form/pull/1, but not ready until the errors are resolved.

@VinitSarvade we won't be able to support RN/Expo in our monorepo, as we're using PNPM which React Native notoriously doesn't support :(
0.73 is making strides in this regard, but it's okay to merge these docs without an example for now.
When PNPM support is made better in RN/Expo, let's merge it in!


Keyboard is presented over input bar during first access to view controller

New issue checklist

[Yes] I have read the README, documentation, and FAQ.
[Yes] Contributing guidelines confirmation: ____
[Yes] I have searched existing issues and this is not a duplicate.

General information

JSQMessagesViewController version: 7.3.4
iOS version: 10.3.2
Devices/Simulators: iPhone 7 Plus
Reproducible in the demo project? (Yes/No): -
Any related issues: https://github.com/jessesquires/JSQMessagesViewController/issues/2081

What happened?
When first time opening chat controller, I auto-generate the welcome message as shown on the screenshot (keyboard goes over input bar):

If I pop controller from the stack and re-access it again, it always works. So, apparently, first load is always the problem.
I have viewDidAppear() defined like:
override func viewDidAppear(_ animated: Bool) {
        super.viewDidAppear(animated)

        inputToolbar.contentView.textView.becomeFirstResponder()
}

I have already tried adding IQKeyboardManagerSwift to the project and that didn't help. Does anyone have an idea why is that happening?

I have the same issue however it's more intermittent. I initially thought it was related to rotation but I can't reproduce it frequently enough to debug.

@yurybelevskiy, thanks for submitting the issue. As for the issue, I was not able to replicate it in the demo project. Can you provide more info?

☝  same issue

Has anyone else had this issue?  I feel like it's something I'm missing... again keyboard simply obscures the input bar so that you can't send a message

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


Dataview queries don't render properly

Current behavior
Only the query code is shown. (Example - Verbs.md)
Expected behavior
List of pages (verbs in this case) to be shown.
Possible fixes
Convert query result to markdown

https://github.com/blacksmithgu/obsidian-dataview/issues/40

dataviewjs can produce markdown results


Unbelieveable Slow Opening of files - Windows 11 - Another Instance of Code is Running (Not Responding)

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

Didnt help

VS Code Version: 1.67.1 (system setup)
OS Version: Windows 11 Pro (21H2)

Steps to Reproduce:
I don't know how to reproduce this issue, I have searched everywhere, I'm using WinSCP as my FTP client and when I try to open files, it is extremely slow and crashes I have tried any other editor and i don't have the issue, it is specific to VSCode, I have run multiple debuggers and no issues arise so I am really stuck on this one... it started happening after the windows 11 update and can't find anything online to help with the issue.
Watch Video to Reproduce:
https://user-images.githubusercontent.com/13056905/169746679-8595719f-a30b-4860-9cda-7a23fc916198.mp4

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.67.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I have tried 1.67.2 and the issue still happens I have also tried rolling back versions further.

@roblourens has there been any update on this issue?

This only reproduces when opening folders via FTP not locally?

@bpasero I've just tested, this still happens when accessing the same files locally.
I have tested in any other editor including sublime text 3, atom, notepad, notepad++, WinSCP internal editor and PHPstorm without the issues. It is specific to VScode.
I've disabled all extensions and it still happens, re-installed, and it still happens. It isn't specific to any file time. It also runs fine with the same settings on my Macbook Pro so its specific to windows 11.
Is there anything I can run that will help you diagnose the issue?

To clarify, when you run code some-file-path from the command line, it takes seconds to open the file?

Hi @bpasero, I have just tested this, and yes the issue still happens when opening files using the terminal.

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

@bpasero Hi, sorry for the delayed response.
I have tested it in the VSCode Insider application and I have no issues... everything opens instantly again... so that editor has fixed the issue. I can't seem to replicate it in that editor, even with all the same extensions installed.
Im just going to run through the settings and compare the 2 to see if there is any difference. I will let you know if i find anything.

@bpasero Just FYI, I've finished going through all settings, I've matched everything as much as I can and it still happens, here is a video of both.
https://user-images.githubusercontent.com/13056905/171547925-e1b8e3f9-a949-412a-b863-9e656a28dae8.mp4

Ok thanks for testing, insiders will be stable early June, so I suggest you keep using insiders until then. It looks like we fixed this, not sure how though.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Configurable lsp location for the vscode extension

[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] I have searched the discussions and believe that my question is not already covered.

Feature Request

Add an option to use typst-lsp from PATH (or any absolute path), instead of relying the bundled excutable.
The bundled executable will not work on every linux distro.

Otherwise, building a static executable (with musl) could work out

Or wasm so that it would work for all OSs

I faced a similar issue and couldn't get the extension to work in vscode on my OS. I fixed it by hacking the binary used by the extension - here's how:

Install the typst-lsp from source:

cargo install -git https://github.com/nvarner/typst-lsp

Find the typst-lsp location being used by vscode. Open the "Output" pane at the bottom, and go to "Typst Language Server". Mine is stored at /mnt/home/mcranmer/.vscode/extensions/nvarner.typst-lsp-0.3.2-linux-x64/out/typst-lsp.
Replace this binary with a link to the compiled one. Update EXTENSION_TYPST_LSP and COMPILED_TYPST_LSP to your system's:

EXTENSION_TYPST_LSP=/mnt/home/mcranmer/.vscode/extensions/nvarner.typst-lsp-0.3.2-linux-x64/out/typst-lsp
COMPILED_TYPST_LSP=$HOME/.cargo/bin/typst-lsp
mv "${EXTENSION_TYPST_LSP}" "${EXTENSION_TYPST_LSP}.bkup"
ln -s $COMPILED_TYPST_LSP $EXTENSION_TYPST_LSP

This should be implemented in the latest release. See #87 for the PR that added it.


chore(package): update kronos-test-interceptor to version 3.1.1

Coverage remained the same at 47.097% when pulling 49638d1ba00996227c1eb24cbd8629f705760d06 on greenkeeper/kronos-test-interceptor-3.1.1 into 1a0e01fc4d7a26507b475246d76cbfa056bc8e9c on master.

Codecov Report

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

@@          Coverage Diff           @@
##           master    #220   +/-   ##
======================================
  Coverage    49.6%   49.6%
======================================
  Files           6       6
  Lines         127     127
======================================
  Hits           63      63
  Misses         64      64

Continue to review full report at Codecov.

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


Type 'UIColor' has no member 'secondarySystemBackground'

Getiing an error in private extension SystemNotification while compiling it for WatchOS with SwiftUI:
Type 'UIColor' has no member 'secondarySystemBackground'

Hi @29satnam
This has been fixed in the 0.5.2 release 👍


fix targetgroup arn lookup #529

This provides a way to retain the metric name arn and tags if at least one dimension filter matches. The current implementation is always using the last dimension lookup whatever that might be. This change does retain the metrics if it already matched previously.
With this change you can fix #529 using the following config:
"discovery":
  "jobs":
  - "enableMetricData": true
    "metrics":
    - "length": 3600
      "name": "ProcessedBytes"
      "period": 300
      "statistics":
      - "Sum"
    "regions":
    - "eu-west-1"
    "type": "alb"
  - "enableMetricData": true
    "metrics":
    - "length": 300
      "name": "HealthyHostCount"
      "period": 300
      "statistics":
      - "Minimum"
    - "length": 300
      "name": "UnHealthyHostCount"
      "period": 300
      "statistics":
      - "Maximum"
    searchTags:
      - key: Port
        value: .*
    "regions":
    - "eu-west-1"
    "type": "alb"

Note using the alb type twice. We use it with the tag we expect to be present on the targetgroup ARN.

Thanks :)


Allow opt-in to breaking out of missing frames

This builds on #863.
When a frame response is missing its expected turbo-frame element, we consider it an error. Normally this is what we want.
In certain specific cases, though, it's better if a response without a matching frame is treated as a full page instead. The classic example of this is a login page being rendered in response to an expired session.
To allow specific paths to be opted in to full reloads when they are returned in response to a missing frame, this adds support for an allowlist specified in a meta tag in the document:
<meta name="turbo-frame-escape-paths" content="/sessions/new /sign_up">

When a response is missing its frame, we check if its path matches anything in that list. If so, we perform a full page visit.
This configuration is app-wide, and would typically be included in an application layout.

We decided to take a different approach to this: #867 lets us solve the problem without introducing new configuration options.


Fix issue when max_score is 0

Hm, fair point. In this case they've skipped all the questions so they are definitely going to be getting the skipped message anyway, but if that were not the case should the user be in the high or the low risk group...I'm not sure, but it doesn't matter anyway.


not working with xml request

I am calling API with XML request but it goes inside  exception delivering event

@satish0563 Can you please elaborate the issue you are facing. What do you mean by calling API? which API you intend to call.

Closing this issue due to lack of response. Please log another issue with detail and logs if you need any assistance.

We had a similar issue, our XMLHttpRequest request always had the text type on iOS.
We used the following code to force the request type:
var req = new XMLHttpRequest();
req.responseType = 'document';
req.overrideMimeType('text/xml');


get pdg from cpg

after i run :
cpg.runScript("pdg-for-funcs-dump.sc")
i got a json file named "pdg-for-funcs.json".it looks like this:
{"functions":** [{
  "function" : "printSizeTLine",
  "id" : "io.shiftleft.codepropertygraph.generated.nodes.Method@1e0",
  "PDG" : [
  ]
},{
  "function" : "printShortLine",
  "id" : "io.shiftleft.codepropertygraph.generated.nodes.Method@1b4",
  "PDG" : [
  ]
},{
  "function" : "globalReturnsTrueOrFalse",
  "id" : "io.shiftleft.codepropertygraph.generated.nodes.Method@2d4",
  "PDG" : [
  ]
},{
  "function" : "<operator>.indirectFieldAccess",
  "id" : "io.shiftleft.codepropertygraph.generated.nodes.Method@376",
  "PDG" : [
  ]
},{
  "function" : "bad9",
  "id" : "io.shiftleft.codepropertygraph.generated.nodes.Method@322",
  "PDG" : [
  ]
},{
  "function" : "bad8",
  "id" : "io.shiftleft.codepropertygraph.generated.nodes.Method@31e",
  "PDG" : [

how could i read this? i am totally not understand this. could i transfer this to code again?

@fabsx00 thank you!

Hi, im running into the same issue, pdg for all functions are empty. Did you solve this issue?

https://github.com/ShiftLeftSecurity/codepropertygraph/pull/973

This fixes it. Note that those broken scripts will be removed. https://github.com/ShiftLeftSecurity/codepropertygraph/pull/974


Define generic multitest module

Related to #266
Something like Bank = Module<BankMsg, BankQuery>.
We can have a default NotImplemented implementation that we can use to handle all the other unsupported types of CosmosMsg, but include them in the switch. All have the same interface, which allows us to easy add support for other modules (Custom, Staking, IBC) without changing everything else.
Router should include multiple modules for these main types, but ::new() will just set as NotImplemented.

I was looking on this idea for half a day and I don't think it makes any sense. Those modules are not the same - Api is differing, as all modules should react on different enum variant.
Also most modules should probably contain no logic - just be mocked structures. I would just proceed with extracting better setup API (via #388), and then prepare transparent mockups of all needed subcomponents with mockall.


new page: query engine guide

Similar to clustering and storage engine guides in depth and length.

@jsternberg. @jwilder mentioned you would be a good person to help us with the query engine guide, similar to the clustering and storage engine guides. We really just need an outline of the topics and some bullet points or sentence fragments. Anything beyond that is gravy.

Just drop the notes on https://github.com/influxdata/docs.influxdata.com/blob/master/content/influxdb/v1.0/concepts/query_engine.md, they won't be discoverable on the docs site until we hook up the Hugo syntax.

Does EXPLAIN PLAN address the general need for a deep dive here?  We can also put this on the list for the IFQL engine.


The parameter of singal() can be omitted, just like useState().

Think about this, create a issue signal, and it's initial is undefined, then you should pass undefined to both generic parameter and function parameter.
const issue = signal<Issue | undefined>(undefined);

We can see that it leads to boilerplate code and the development experience is reduced.
The signal() can be defiened like this:
function signal<T>(value: T): Signal<T>;
function signal<T = undefined>(): Signal<T | undefined>;

I don't think it's a problem. Better to keep function monomorphic with the same amount of arguments

I don't think it's a problem. Better to keep function with the same amount of arguments (it's better for performance)

Even if you're right, but the class Signal has a optional parameter contructor, how to explain it?

Looks reasonable to me, if you want to PR it.

I don't think it's a problem. Better to keep function with the same amount of arguments (it's better for performance)

Even if you're right, but the class Signal has an optional parameter constructor, how to explain it?
It's not for public usage. But I see, probably it will think that it can have 0 params
https://github.com/preactjs/signals/blob/58befba577d02c5cac5292fda0a599f9708e908b/packages/core/src/index.ts#L531

Anyway I think it should be benchmarked. Check for deoptimizations and how much it slows other benchmarks

Anyway I think it should be benchmarked. Check for deoptimizations and how much it slows other benchmarks

This should be a type signature-only change. There will be no effect on the benchmarks

@XantreGodlike This is in relation to an already allowed paradigm, signals can be initiated with undefined or a missing initializer as you yourself link to for the Computed.prototype. This can't possibly affect benchmarks as it's merely a change in how the generic infers the starting value.

It's not we are starting to provide interface that allows different amount of args. It can cause performance slow down, depending on usage
https://jsbench.me/7slty3mtij/1

But probably impact will be insignificant

Did you read my comment? It's already ? allowed to be not there https://github.com/preactjs/signals/blob/main/packages/core/src/index.ts#L277

Did you read my comment? It's already ? allowed to be not there https://github.com/preactjs/signals/blob/main/packages/core/src/index.ts#L277

Got it. Sorry

Woo-hoo, glad to see my PR #116 don't need to celebrate its 2nd birthday.


No validation for environment.gnome3.excludePackages

The excludePackages option will silently ignore any packages that aren't optional packages for GNOME. This could be confusing. The same applies for the corresponding lxqt option.

no

Yea I ran into this when trying to get rid of gnome-terminal. Maybe we should just spit a warning when these packages are attempted to be excluded?

I think this stems from these program modules being enabled by default?
https://github.com/NixOS/nixpkgs-channels/blob/e0759a49733dfc3aa225b8a7423c00da6e1ecb67/nixos/modules/services/x11/desktop-managers/gnome3.nix#L366-L373
Something like this would work right? Or maybe an assertion would be better suited
programs.evince.enable = mkDefault !(lib.elem pkgs.gnome3.evince config.environment.gnome3.excludePackages);
...

@mvnetbiz that looks good to me. I didn't test it, but I can testify that geary, which I wanted to get rid of for a while now can be get rid of with programs.geary.enable = false.

Closed by #98510


[Question] Load model on CPU

I trained BiLSTM_CRF_Model on GPU (colab) and save it. I possible to load this model on device without GPU?
I have an error on loading:
No OpKernel was registered to support Op 'CudnnRNNV2' used by node layer_blstm/forward_cu_dnnlstm_1/CudnnRNNV2

Update to the latest version kashgari==1.0.0 and set kashgari.config.use_cudnn_cell = False (False is the default value). Then you can predict on CPU.

Thanks. It works. I just had to re-train the model with this setting


Assignment 02 edited

Final for assignment 02.

Looks good. Now you have the basic git commands (fork, clone, commit, push, pull request) under control.


EHPR-322 | Captcha

Changes

Fix some local development issue
Add Formik CaptchaField and can be extends to different Captcha component by using children. Here we use ClickCaptcha.

Initial state

Loading state

Completed state

@dbayly-freshworks Please review again, I've fixed issues from sonarqube. Thanks


Flutter 3.0

Hi,
looks like the flutter API changed for null safety on WidgetBindings
/C:/devtools/flutter/.pub-cache/hosted/pub.dartlang.org/fl_chart-0.36.4/lib/src/chart/pie_chart/pie_chart.dart(38,20): warning GBC99161D: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null. [C:\Solutions\Flutter\cryptowulf\build\windows\flutter\flutter_assemble.vcxproj]

This warning is already resolved and will be available in the next release version of lib.

Yes. It has just landed in the stable branch.
Check it out in 0.50.3


Possible out-of-memory issue of dataloader

Hello,
I have read through your code, but haven't run the code yet. One question about the dataloader implementation. According to
https://github.com/dandelin/ViLT/blob/master/vilt/datasets/base_dataset.py#L43
You load all the arrow files into memory. The pre-training data have hundreds of gigabytes. Is it possible that this may cause out-of-memory issue?
Thanks,

Hi @zhiqiangdon,
Apache Arrow's read_all() function is actually doing a lazy loading, so there will be no OOM issue.
Though if you call the .to_pandas() method, then Arrow will load the dataset eagerly and you will face the OOM issue.

Thanks @dandelin,
I see that you call .to_pandas() on the text column:
https://github.com/dandelin/ViLT/blob/master/vilt/datasets/base_dataset.py#L58
I guess this operation doesn't load the image data, right?

@zhiqiangdon
Yep, you are right. Arrow is columnar DB, so the data will be loaded column-wise manner.

Thanks @dandelin!


Merge patch/content/secondary into feature/body

Merge branch patch/content/secondary into feature/body using pull request.

Everything is done!


VMs start running even if the db url/credentials is incorrect or db i…

…s unreachable for servicebroker
[#154807154]

LGTM

LGTM

LGTM


Is it possible to have fzf complete environmental (shell) variables?

Category

[ ] fzf binary
[ ] fzf-tmux script
[ ] Key bindings
[x] Completion
[ ] Vim
[ ] Neovim

OS

[ ] Linux
[x] Mac OS X
[ ] Windows
[ ] Windows Subsystem for Linux

Shell

[x] bash
[ ] zsh
[ ] fish

Simple question: Is it possible to have fzf complete environmental (shell) variables when tab-completing a word preceded with the dollar sign $? Currently I have fzf completion enabled all the time by setting FZF_COMPLETION_TRIGGER='', but this messes up the default shell variable completion at times.

Probably not possible with the current implementation because it expands the current line to resolve $ENVVARs and ~ expressions. For example, for vim $HOME**<tab>, it is designed to find files inside $HOME directory instead of searching for environment variables that start with HOME.


WIP: Standardization/integration

Related to https://github.com/ovh-ux/ovh-manager-web/pull/258

PR to develop instead?

Yes, changed to develop :)


Eval operations at execution where state unknown

Closes: #805

Cancelling this in favour of #996, there’s just too much magic already and this change adds yet more. V3 will radically simplify and address these issues properly.


Start and open workspace

⚠ This PR depends on #6015 and #6219 and should not be merged in before those are.
However, it is being marked as ready as plans are to review + merge these PRs in quick succession.
Pull Request Description

Adds project stop and fullscreen icons
Adds spinner animation
Adds Ide component as a container for the IDE

Screencast
https://user-images.githubusercontent.com/4046547/224118329-9107e855-b517-4dc0-a445-7195662206ed.mp4
Important Notes
Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the
Scala,
Java,
and
Rust
style guides.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed: Enso GUI was tested when built using BOTH
./run ide build and ./run ide watch.

Not working after merging so I'm keeping it as a draft

Seems to work now, I didn't change anything though - backend might just have been having issues yesterday

:warning: this PR is not ready for merge, waiting on the backend's default version to be updated to at least 2023.1.1-nightly.2<IP_ADDRESS> so that initializing projects actually works

this force-push is just to change the environment back to production

@Nctdt can you intergrate here your icon my current project from https://github.com/enso-org/enso/pull/6064 and connect with logic? So we can switch between currently opened project and dashboard

@somebody1234 could you take over moving the current open project icon here from the PR https://github.com/enso-org/enso/pull/6064?

@PabloBuchu do yo mean mergin #6064 into here?

@somebody1234 two things:

When openning a project a loader covers the whole screen. Can we leave the top bar on top?
This also should be in the size of window. Currently its fixed and plus icon is partially hidden and scroll bar is forced

yup, but i think i'll need to make things work on the desktop IDE first? since the cloud dashboard pulls from the backend's version so local edits will never show up. it's probably theoretically possible to get cloud dashboard to work with the local backend, i could try if you think it's better to fix this before fixing authentication on desktop
yeah, same issue as above
:ok_hand: will investigate... sometime

not ready.
to do - i'll do these later:

confirm that i didn't mess anything up in dashboard.tsx
hide top bar
investigate & fix css issue

@somebody1234 let me know if we can add here handling opening project by project manager here if running in electron or we need separate PR for that

@PabloBuchu i think enough changes are needed that it should be a separate PR - it will take quite a while to do and will likely be quite a significant change to lots of files too

no changelog required, because if one is required it should be only done once, either on the first one (#6015) or the last one (not yet opened)

importantly however, this means there will be no way to get back to the dashboard (other than manually refreshing) until the IDE adds the event that we can listen to - since the switcher will no longer be visible.

FYI This PR only adds support for openning projects from a cloud. We will add integration with project manager in the upcoming one not to touch to many files at once

@somebody1234 please fix merge conflicts so the PR can be merged


Add Arm64 source and corrected version number Zoom.Zoom 5.10.0 (4306)

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

You will also need to update the version folder which you can do by pressing the . (dot) on your keyboard on this PR.


Invalid Date

I am passing date in this format yyyy-mm-ddTHH:MM but it says Invalid date.

Also tried sending as Moment object but still doesn't work.

Sorry. It works. There was an error on my end.


Incorrect conda command on installation page

Heya! I think the command on the Installation page is currently
conda install -c pytorch conda-forge pymde

but the channel should be immediately after the -c flag (and should prioritize the PyTorch channel)
conda install -c pytorch -c conda-forge pymde

Otherwise it fails with the following message:
guille@guille-mbp ~> conda install -c pytorch conda-forge pymde                                              (pymde)
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.

PackagesNotFoundError: The following packages are not available from current channels:

  - pymde
  - conda-forge

Current channels:

  - https://conda.anaconda.org/pytorch/osx-64
  - https://conda.anaconda.org/pytorch/noarch
  - https://repo.anaconda.com/pkgs/main/osx-64
  - https://repo.anaconda.com/pkgs/main/noarch
  - https://repo.anaconda.com/pkgs/r/osx-64
  - https://repo.anaconda.com/pkgs/r/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org

and use the search bar at the top of the page.

Thanks!

closed by commit 7a5b9d3d10f0fa1070701b1dc9861475a82918ea


Do not call AsyncTask.get() in UI thread

This patch ensures UI thread will not be blocked by HTTP response.
Closed #54.

Closing in preference to the Rx tack we have taken in 0.3.0.


Prolog misclassified as Perl

This file is incorrectly classified as Perl:
https://github.com/ciao-lang/devenv/blob/master/Manifest.pl

#3409 will fix it.


Remove unused $connect arg leftover from vscode notebooks change.

Was looking through my commit for enabling vscode notebooks and noticed this leftover $connect change that didn't get cleaned up.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.006%) to 41.969%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-database-projects/src/common/httpClient.ts
1
66.18%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
52.88%

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
28787

Relevant Lines:
63695

💛  - Coveralls


sum doesn't work

In the documentation it says,
@user.failed_logins.sum

should return total, but the sum function doesn't seem to exist.

Is it possible to retrieve the total sum though?

@user.failed_logins.all_values.inject(:+)

Is there a better way?

Given that you use rails, this should do:
@user.failed_logins.all_values.sum

See my above comments about the sum extension to Enumerables of ActiveSupport.

Oh, ofcourse! thanks.


A few errors in the DO Analysis UI

[ ] We shouldn't be showing this. Is this because of where the geometry is situated?

[ ] When there are measurements available, the dropdown also behaves incorrectly. It opens on top of the following input, it adds border-radius to the options list where there shouldn't be any, and the search box appears a few pixels to the left of the options list.

[ ] There shouldn't be any more line below the "Boundaries" point.
[ ] There's more margin than it should be between "Measurement" and "Normalize"

(Left: Mockup | Right: Production)
.carto used:
Demographics of the United Kingdom.zip

Stale issue. Closing 👋


investigate ray batching

Interactive Rendering with Coherent Ray Tracing
Ingo Wald, Philipp Slusallek, Carsten Benthin, and Markus Wagner


Code is not consistent (internally)

Hi,
1)
in src/Service/AbstractNavigationFactory.php
this seems to not be consistent (see: ServiceLocatorInterface / ContainerInterface)
    /**
     * Create and return a new Navigation instance (v2).
     *
     * @param ContainerInterface $container
     * @param null|string $name
     * @param null|string $requestedName
     * @return Navigation
     */
    public function createService(ServiceLocatorInterface $container, $name = null, $requestedName = null)
    {
        return $this($container, $requestedName);
    }

If i want to filter the pages with ZfcRbac (=>user rights) where should i do that?  in getPages() or better use preparePages() or even somewhere else?
Thanks!

Will be closed. An explanation can be found at the related PR.


[RELEASE] Release 3.9

Work Plan
Create release 3.9 :
Prior to the release work

[x] slack post advising of upcoming release & linking to issue
[x] advance warning in developer/community call
[x] final agreement to start branch in team call & identification of outstanding issues
[x] Agree required updates/versions for additional repos including egeria-ui, egeria-reactui, connectors etc

Branching & Correcting versions

[x] Create branch
[x] Reassign any issues not being worked on to the next release
[x] Update version for master (ie x.y-SNAPSHOT > x.y+1-SNAPSHOT)
[x] Update version for branch (ie x.y-SNAPSHOT -> x.y)

Final updates to the release

[x] Ensure any remaining fixes are merged into branch (and vice-versa to master)

Generate a release image for testing

[x] Start release pipeline manually to generate container image

Updating the React UI (as this is part of the notebook test). Note egeria-ui is out of scope other than inclusion of current release

[N/A] Create branch
[N/A] Update version in master
[N/A] Update version in new branch
[N/A] Ensure new container image is available for testing (there is no distinct release pipeline)

Updating the Helm Charts (egeria-charts repo)

[x] checker correct container images are on docker.io & quay.io (these are built by the 'merge' build of a release)
[x] update image versions for helm charts (egeria-charts repo) (using -prerelease for chart version)

Final tests

[x] Check swagger doc renders (no regressions)
[x] Verify odpi-egeria-lab chart (pods active/ready)
[x] Verify egeria-base chart (pods active/ready)
[x] Check notebooks (config, start, data catalog at a minimum)
[x] Check polymer UI (only possible to check it runs - no demo scenario for more)
[x] Check React UI (rex, tex, glossary author)
[x] CTS - graph
[x] CTS - inmemory

Final Docs

[x] Update release notes in egeria-docs

Final build and publish

[x] Run 'release' pipeline on branch to push candidates to oss.sonatype.org
[x] 'close' staging repo & Validate artifacts ok (number, structure, validations) on oss.sonatype.org
[x] Create final github releases for egeria (add link to egeria docs)
[x] Close repo on oss.sonatype.org (once updated) for egeria, release
[x] Check 'release' repo on oss.sonatype.org has artifacts
[x] Update final versions of egeria-charts to release ie x.y
[x] Publish that release is now shipped via slack #egeria-announce
[ ] Additional posts to social media
[x] Communicate to other repo owners ie for connectors so that they can be rebuilt/shipped as needed

Additional components

ReactUI

[N/A] Create final github release

PostGres Connector

[N/A] Create branch
[N/A] Update version in master
[N/A] Update version in new branch of connector, and of prereq egeria artifacts
[N/A] Run release action, check sonatype & release
[N/A] Create github release

I would like to propose we branch for the release on Thu 26 May.

Agreed in face2face meeting AMS that we will do the branch on 26 May

@davidradl I will do an initial version of our helm charts using the 3.8.1 version of the UI.
If you plan to make a 3.9 release, we can update the pre-release charts for testing to use the 3.9.0-rc version when avail. Please let me know which works for you.

prerelease charts now available for testing:
helm repo update && helm search repo egeria  --devel
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "strimzi" chart repository
...Successfully got an update from the "egeria" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
NAME                  	CHART VERSION     	APP VERSION	DESCRIPTION
egeria/egeria-base    	3.9.0-prerelease.0	3.9        	Egeria simple deployment (platform, react UI)
egeria/egeria-cts     	3.9.0-prerelease.0	3.9        	Egeria Conformance Test Suite deployment to Kub...
egeria/egeria-pts     	3.9.0-prerelease.0	3.9        	Egeria Performance Test Suite deployment to Kub...
egeria/odpi-egeria-lab	3.9.0-prerelease.0	3.9        	Egeria lab environment

The following issues were raised during testing:

#6548
#6549
#6550
odpi/egeria-docs#444

However none are critical or known regressions in stable code, so will not impact release

#6547 was also recently opened - the ui-lab fails to locate assets due to being in wrong zone - but it's likely this has been there in previous releases as this lab needs more elaboration. In addition the UI code level in the charts is back at 3.2.0 since the code is being refactored, so will leave as-is for the release

First cts test run (inmemory) has failed
    "testLabResults": {
        "class": "OpenMetadataConformanceTestLabResults",
        "testCaseCount": 5826,
        "testFailedCount": 1,
        "testPassCount": 5825,
        "testResultsFromWorkbenches": [
            {
                "class": "OpenMetadataConformanceWorkbenchResults",
                "failedTestCases": [
                    {
                        "class": "OpenMetadataTestCaseResult",
                        "conformanceException": {
                            "errorMessage": "CTS test repository-entity-reference-copy-lifecycle caught exception EntityNotKnownException from method getEntityDetail whilst trying to retrieve an entity of type APISchemaType.  Exception message was : OMRS-REPOSITORY-404-002 The entity identified with guid 3709ed6f-01c7-4901-bf6f-cdc8cba05334 passed on the getEntityDetail call is not known to the open metadata repository tut.  Method was invoked with parameters: entityGUID : 3709ed6f-01c7-4901-bf6f-cdc8cba05334",
                            "exceptionClassName": "java.lang.Exception"
                        },
                        "notSupportAssertions": [],
                        "successfulAssertions": [
                            "repository-test-case-base-01: Repository connector supplied to conformance suite.",
                            "repository-test-case-base-02: Metadata collection for repository connector supplied to conformance suite.",
                            "repository-entity-reference-copy-lifecycle-00: APISchemaType entity type definition matches known type  ",
                            "repository-entity-reference-copy-lifecycle-01: APISchemaType reference entity created; repository supports storage of reference copies.",
                            "repository-entity-reference-copy-lifecycle-02: APISchemaType reference entity can be retrieved as EntitySummary.",
                            "repository-entity-reference-copy-lifecycle-03: APISchemaType reference entity can be retrieved as EntityDetail.",
                            "repository-entity-reference-copy-lifecycle-04: APISchemaType reference entity matches the entity that was saved.",
                            "repository-entity-reference-copy-lifecycle-05: APISchemaType reference entity has no relationships.",
                            "repository-entity-reference-copy-lifecycle-06: APISchemaType reference entity status cannot be updated.",
                            "repository-entity-reference-copy-lifecycle-06: APISchemaType reference entity status cannot be updated.",
                            "repository-entity-reference-copy-lifecycle-07: APISchemaType reference entity properties cannot be updated.",
                            "repository-entity-reference-copy-lifecycle-08: APISchemaType reference entity type cannot be changed.",
                            "repository-entity-reference-copy-lifecycle-09: APISchemaType reference entity identity cannot be changed.",
                            "repository-entity-reference-copy-lifecycle-10: APISchemaType reference entity copy purged at TUT.",
                            "repository-entity-reference-copy-lifecycle-11: APISchemaType reference entity refresh requested by TUT.",
                            "repository-test-case-base-01: Repository connector supplied to conformance suite.",
                            "repository-test-case-base-02: Metadata collection for repository connector supplied to conformance suite."
                        ],
                        "testCaseDescriptionURL": "https://egeria.odpi.org/open-metadata-conformance-suite/docs/repository-workbench/test-cases/repository-entity-reference-copy-lifecycle-test-case.md",
                        "testCaseId": "repository-entity-reference-copy-lifecycle-APISchemaType",
                        "testCaseName": "Repository entity reference copy lifecycle test case",
                        "unsuccessfulAssertions": [
                            "Unexpected Exception Exception : CTS test repository-entity-reference-copy-lifecycle caught exception EntityNotKnownException from method getEntityDetail whilst trying to retrieve an entity of type APISchemaType.  Exception message was : OMRS-REPOSITORY-404-002 The entity identified with guid 3709ed6f-01c7-4901-bf6f-cdc8cba05334 passed on the getEntityDetail call is not known to the open metadata repository tut.  Method was invoked with parameters: entityGUID : 3709ed6f-01c7-4901-bf6f-cdc8cba05334"
                        ]
                    }
                ],
                "passedTestCases": [

poll counts were doubled in 7e4a90952fdd9373ef808bbc59f5869be033ec1a

@mandy-chessell ^^ let's discuss early next week

Initial release notes for 3.9 added. Any additions please submit a PR on egeria-docs

Agreed in team call 2021-05-31 :

Add notes on the cts, cohort registration #6353, discovery issues (at a minimum) to the release notes
Continue to ship the release
Investigate these three issues further in the next week

Will plan to do a bigger blog/announce for the 3.10 release to round-up the first part of the year's content


/src/docs/goals/mobility.md

This file is not finished. This document is part of setting up the site for the first round of feedback.
You'll find work in progress notes that might help fill out the doc, use your best judgement on what else belongs. Don't worry too much about linking -- that can be done when all documents are finished.

Attempted to close in #67:

i've removed the mobility doc because much of how it helps careers is in there. It doesn't feel like enough content to warrant a whole document though I've written drafts a couple times on mobility through aux. Feels too ethereal / unproven / not good grounding in examples for me to paint a meaningful picture.


Feature: register driver & operator #36

What does this PR do?

Create register page

Description of Task to be completed?

Allow an administrator to register a new driver or a new operator.

Form validation and display appropriate error messages on unsuccessful attempts

Responsiveness of the

How should this be manually tested?

Clone the repo

checkout to branch ft-register-36

Run npm install to install modules

Run npm  run start to start the development server

On the landing page click on the Sign up menu

What are the relevant Pivotal Tracker/trello stories?

https://trello.com/c/Sd4qDC5s/36-register-drivers-operators

Questions:

N/A

@PrinceNiyonshuti @PatrickNiyogitare28
you can review my PR i have done with the requested changes

@PatrickNiyogitare28 , you can review this PR again, I have done with the request changes


[Jsonifier] Updating to version v0.9.1

FIxes the following:
-Created the Expected and Unexpected classes to allow for compilation on CLANG15
-Modified the StringView class so that it could replace
std::string_view through the codebase.
-Modified the String class so that it could replace std::string through the codebase.
-Added an Error handling class called Derailleur for printing relevant index data, and for recovering from damaged json-input.
-Added support for removing keys from serializing/parsing at runtime.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

The usage has been tested successfully locally.
find_package(Jsonifier CONFIG REQUIRED)
target_link_libraries(main PRIVATE Jsonifier::Jsonifier)


Unable to upload health app bundles to Google Play

Opening a new issue since this one has been closed, but is still happening on the latest fastlane version even with the appropriate health apps declaration filled out in Google Play: https://github.com/fastlane/fastlane/issues/22204
NOTE: This does not happen when the app bundle is manually uploaded to Google Play, the error is specific to Google API uploads via fastlane
New Issue Checklist

[X] Updated fastlane to the latest version
[X] I read the Contribution Guidelines
[X] I read docs.fastlane.tools
[X] I searched for existing GitHub issues

Issue Description
When uploading an app bundle with health app features to Google Play, where a health apps declaration has been filled out accordingly, this error is thrown on our fastlane upload:
Google Api Error: Invalid request - You must let us know whether your app includes any health features.

I have reached out to Google to try and understand why we would get this error despite following their documentation but have yet to hear back. I saw Google had responded to the original poster indicating that they couldn't do anything as this is a fastlane issue (and the issue does not occur when uploading an app bundle manually), so I don't have high hopes if/when they do get back to me.
We need to use the health app features so removing the health permissions from our manifest isn't an option.
Command executed
       upload_to_play_store(
              track: 'internal',
              skip_upload_screenshots: true,
              skip_upload_images: true,
              package_name: ENV['APP_BUNDLE_ID'],
              aab: "#{ENV['DEPLOY_DIR']}/app-release.aab",
        )

Complete output when running fastlane, including the stack trace and command used
+--------------------------------------------------+
|                   Lane Context                   |
+------------------+-------------------------------+
| DEFAULT_PLATFORM | all                           |
| PLATFORM_NAME    | all                           |
| LANE_NAME        | all deploy_android_play_store |
+------------------+-------------------------------+
[20:51:55]: Called from Fastfile at line 44
[20:51:55]: ```
[20:51:55]:     42:	      retryBlock***
[20:51:55]:     43:	          platform :android do
[20:51:55]:  => 44:	            upload_to_play_store(
[20:51:55]:     45:	              track: 'internal',
[20:51:55]:     46:	              skip_upload_screenshots: true,
[20:51:55]: ```
[20:51:55]: Google Api Error: Invalid request - You must let us know whether your app includes any health features.

+-------------------------------------------+

[!] Google Api Error: Invalid request - You must let us know whether your app includes any health features.
|             fastlane summary              |
+------+----------------------+-------------+
| Step | Action               | Time (in s) |
+------+----------------------+-------------+
| 1    | opt_out_usage        | 0           |
| 2    | add_extra_platforms  | 0           |
| 3    | default_platform     | 0           |
| 💥   | upload_to_play_store | 52          |
| 💥   | upload_to_play_store | 55          |
| 💥   | upload_to_play_store | 51          |
+------+----------------------+-------------+

[20:51:55]: fastlane finished with errors

Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
14.7

Ruby
3.1.3

Bundler?
false

Git
git version 2.39.3 (Apple Git-146)

Installation Source
~/.rbenv/versions/3.1.3/bin/fastlane

Host
macOS 14.7 (23H124)

Ruby Lib Dir
~/.rbenv/versions/3.1.3/lib

OpenSSL Version
OpenSSL 3.2.1 30 Jan 2024

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
15.3

Swift Version
5.10

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.225.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.3.0

did_you_mean
1.6.1

babosa
1.0.4

colored
1.2

highline
2.0.3

commander
4.6.0

faraday-cookie_jar
0.0.7

sysrandom
1.0.5

fastlane-sirp
1.0.0

gh_inspector
1.1.3

google-cloud-env
1.6.0

naturally
2.2.1

rubyzip
2.3.2

security
0.1.5

terminal-notifier
2.0.0

terminal-table
3.0.2

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

set
1.0.2

public_suffix
6.0.1

addressable
2.8.7

artifactory
3.0.17

aws-eventstream
1.3.0

aws-sigv4
1.10.1

aws-partitions
1.1004.0

jmespath
1.6.2

aws-sdk-core
3.212.0

aws-sdk-kms
1.95.0

aws-sdk-s3
1.170.1

bundler
2.5.6

base64
0.2.0

nkf
0.2.0

rexml
3.3.9

CFPropertyList
3.0.7

dotenv
2.8.1

emoji_regex
3.2.3

excon
0.112.0

ruby2_keywords
0.0.5

faraday-retry
1.0.3

faraday-rack
1.0.0

faraday-patron
1.0.0

faraday-net_http_persistent
1.2.0

faraday-net_http
1.0.2

multipart-post
2.4.1

faraday-multipart
1.0.4

faraday-httpclient
1.0.1

faraday-excon
1.1.0

faraday-em_synchrony
1.0.0

faraday-em_http
1.0.0

faraday
1.10.4

faraday_middleware
1.2.1

domain_name
0.6.20240107

http-cookie
1.0.7

fastimage
2.3.1

httpclient
2.8.3

multi_json
1.15.0

jwt
2.9.3

signet
0.19.0

os
1.1.4

googleauth
1.8.1

mini_mime
1.1.5

retriable
3.1.2

trailblazer-option
0.1.2

declarative
0.0.20

uber
0.1.0

representable
3.2.0

google-apis-core
0.11.3

google-apis-androidpublisher_v3
0.54.0

google-apis-playcustomapp_v1
0.13.0

rake
13.2.1

digest-crc
0.6.5

google-apis-storage_v1
0.31.0

google-apis-iamcredentials_v1
0.17.0

google-cloud-errors
1.4.0

google-cloud-core
1.7.1

google-cloud-storage
1.47.0

json
2.8.1

mini_magick
4.13.2

optparse
0.6.0

plist
3.7.1

simctl
1.6.10

unicode-display_width
2.6.0

tty-screen
0.8.2

nanaimo
0.4.0

colored2
3.1.2

claide
1.1.0

atomos
0.1.3

xcodeproj
1.27.0

forwardable
1.3.2

logger
1.6.1

pathname
0.2.0

shellwords
0.1.0

cgi
0.3.5

date
3.2.2

timeout
0.2.0

stringio
3.0.1

securerandom
0.3.2

uri
0.11.0

ipaddr
1.2.4

io-wait
0.2.1

openssl
3.0.1

digest
3.1.0

io-nonblock
0.1.0

zlib
2.1.1

resolv
0.2.1

time
0.2.0

open-uri
0.2.0

mutex_m
0.2.0

net-http
0.3.0

net-protocol
0.1.2

english
0.7.1

erb
2.2.3

strscan
3.1.0

abbrev
0.1.0

io-console
0.5.11

tempfile
0.1.2

delegate
0.2.0

fileutils
1.6.0

tmpdir
0.1.2

singleton
0.1.1

open3
0.1.1

prettyprint
0.1.1

pp
0.3.0

find
0.1.1

ostruct
0.5.2

yaml
0.2.0

psych
4.0.4

generated on: 2024-11-12

Any update on this ?
We don't use any of the permissions mentioned here https://support.google.com/googleplay/android-developer/answer/13996367?sjid=10541869973483384753-NC#zippy=%2Cwhat-permissi[…]the-health-apps-policy and have filled the health-app consent form as well, submitting the build manually to play-storeworks, but not via fastlane, same error as mentioned in the description under Issue Description

Although not identical, we're facing a similar problem.
In our case, at first, we received the same error above stating the declaration of health features. After filling out the health apps declaration and sending it for review that error was gone. Then we started to get another similar error related to foreground services when using fastlane distribution: "Google Api Error: Invalid request - You must let us know whether your app uses any Foreground Service permissions."
After manually uploading aab to play console, now another declaration form appeared under the app content section mentioning that we must must declare the appropriate foreground service permission for each specific foreground service type.
I hope completing that declaration will solve the problem for us.

Same errors. Unable to deliver the Android package via Fastlane due to Google API health feature errors. No issues with the manual upload to Google Play Console.

Same issue here.

any updates on this? we're experiencing this as well

Issue is still occurring for us despite the health apps declaration form being reviewed and approved. Our app uses and declares health permissions. No update from Google support either, would be great if we could get some help from the fastlane team on this

Issue is still occurring for us despite the health apps declaration form being reviewed and approved. Our app uses and declares health permissions. No update from Google support either, would be great if we could get some help from the fastlane team on this

@rpekarek-tc After getting approval from app store, retrying my existing similarly kept failing. However, after incrementing my build version re-ubmission worked. Perhaps it's a caching issue somewhere.

This appears to be fixed in fastlane 2.226