fix: proper repo location on autoupdate

As title says. I will also try to fix #93

Refer to ansys/python-installer-qt-gui instead of pyansys/python-installer-qt-gui
Wrap pygithub query with try...except. Closes #93

New message box in case check for update fails:

I am not able to run the UI from source code because again SSL errors from pypi api.
I do understand that this is necessary, but would it be possible to maintain a list of versions(of all the possible versions from) in the package itself, then at least the UI would open, in my case the UI just does not open and user does not know whats wrong.
--console flag does not work with the exe, I had to run the main.py file
2023-08-28 11:32:26,874 - DEBUG - Populating the table with virtual environments.
2023-08-28 11:32:26,881 - DEBUG - Populating the table with python and conda forge versions.
2023-08-28 11:32:26,881 - DEBUG - Found the following unified Ansys installation versions: {232: 'C:\\Program Files\\ANSYS Inc\\v232', 231: 'C:\\Program Files\\ANSYS Inc\\v231', 221: 'C:\\Program Files\\ANSYS Inc\\v221'}
2023-08-28 11:32:27,255 - DEBUG - Starting new HTTPS connection (1): pypi.python.org:443
Traceback (most recent call last):
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\connectionpool.py", line 467, in _make_request
    self._validate_conn(conn)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\connectionpool.py", line 1092, in _validate_conn    conn.connect()
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\connection.py", line 642, in connect
    sock_and_verified = _ssl_wrap_socket_and_match_hostname(
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\connection.py", line 783, in _ssl_wrap_socket_and_match_hostname
    ssl_sock = ssl_wrap_socket(
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\util\ssl_.py", line 469, in ssl_wrap_socket
    ssl_sock = _ssl_wrap_socket_impl(sock, context, tls_in_tls, server_hostname)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\util\ssl_.py", line 513, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
  File "C:\Program Files\ANSYS Inc\v232\commonfiles\CPython\3_10\winx64\Release\python\lib\ssl.py", line 513, in wrap_socket
    return self.sslsocket_class._create(
  File "C:\Program Files\ANSYS Inc\v232\commonfiles\CPython\3_10\winx64\Release\python\lib\ssl.py", line 1071, in _create
    self.do_handshake()
  File "C:\Program Files\ANSYS Inc\v232\commonfiles\CPython\3_10\winx64\Release\python\lib\ssl.py", line 1342, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:997)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\connectionpool.py", line 790, in urlopen
    response = self._make_request(
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\connectionpool.py", line 491, in _make_request
    raise new_e
urllib3.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:997)

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

Traceback (most recent call last):
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\requests\adapters.py", line 486, in send
    resp = conn.urlopen(
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\connectionpool.py", line 844, in urlopen
    retries = retries.increment(
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\urllib3\util\retry.py", line 515, in increment
    raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded with url: /pypi/pyansys/json (Caused by
SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:997)')))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\src\ansys\tools\installer\__main__.py", line 6, in <module>
    open_gui()
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\ansys\tools\installer\main.py", line 680, in open_gui
    window = AnsysPythonInstaller()
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\ansys\tools\installer\main.py", line 123, in __init__
    self.installed_table_tab = InstalledTab(self)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\ansys\tools\installer\installed_table.py", line 281, in
__init__
    self.update_package_combo(0)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\ansys\tools\installer\installed_table.py", line 362, in
update_package_combo
    self._cached_versions[package_name] = get_pkg_versions(package_name)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\ansys\tools\installer\common.py", line 88, in get_pkg_versions
    releases = json.loads(requests.get(url).content)["releases"]
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\requests\api.py", line 73, in get
    return request("get", url, params=params, **kwargs)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\requests\api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\requests\sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\requests\sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "D:\users\mkanchan\Work\pyansys\source\python-installer-qt-gui\.venv\lib\site-packages\requests\adapters.py", line 517, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded with url: /pypi/pyansys/json (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:997)')))

@kmahajan-cadfem - yep got it...
Keeping track of a hardcoded list of versions might be a high-burden to pay for... What I can do, though, is to avoid the failure and just show the list of packages. That way, if you then request the installation of a certain package, you would just get the latest version of it (i.e. it's like instead of doing pip install pyansys==XX.YY.ZZ you just ran pip install pyansys.
Would that work?

@kmahajan-cadfem - yep got it...
Keeping track of a hardcoded list of versions might be a high-burden to pay for... What I can do, though, is to avoid the failure and just show the list of packages. That way, if you then request the installation of a certain package, you would just get the latest version of it (i.e. it's like instead of doing pip install pyansys==XX.YY.ZZ you just ran pip install pyansys).
Would that work?

I agree, maintaining list is a manual work and would not be efficient.
but  just list without versions(i think this is already there) would be a great advantage and it is better to tell user what is failing or it should not fail to open.
once the user at least reaches to the UI , venvs creation should not be a problem, the last remaining bit of installation of pip packages could be done at later point or through console.

Just did some implementation "simulating" your case (no connection to the PyPI API). Let me know what you think. I'll upload the changes
pypi-api.webm

This looks great 👍

Awesome, thanks @kmahajan-cadfem! Please review and approve whenever you have the chance so that we can merge it in that case. Glad it solved your issues!


osx 10.11  dyld: Library not loaded: @rpath/CTAssetsPickerController.framework/CTAssetsPickerController

dyld: Library not loaded: @rpath/CTAssetsPickerController.framework/CTAssetsPickerController
Referenced from: /private/var/mobile/Containers/Bundle/Application/9E241461-4D4F-4447-8665-82B9A9826C4C/ios.app/fp_ios
Reason: no suitable image found.  Did find:
/private/var/mobile/Containers/Bundle/Application/9E241461-4D4F-4447-8665-82B9A9826C4C/ios.app/Frameworks/CTAssetsPickerController.framework/CTAssetsPickerController: mach-o, but wrong architecture
/private/var/mobile/Containers/Bundle/Application/9E241461-4D4F-4447-8665-82B9A9826C4C/ios.app/Frameworks/CTAssetsPickerController.framework/CTAssetsPickerController: mach-o, but wrong architecture
/private/var/mobile/Containers/Bundle/Application/9E241461-4D4F-4447-8665-82B9A9826C4C/ios.app/Frameworks/CTAssetsPickerController.framework/CTAssetsPickerController: mach-o, but wrong architecture

@cczufish A descriptive message of your issue would be more helpful.


use the new hack repo for scripts

Proposed Changes

test-infra/scripts -> hack

ref: https://github.com/knative/hack/pull/2

/lgtm


Part 1 Step 7 needs to report 0x00 in any byte of CVN

See #156 for details

Alternatively,
<IP_ADDRESS> Fail Criteria
a. Fail if total number of reported CAL IDs is < user entered value for number of emission or diagnostic critical control units (test 6.1.2).
b. For responses from OBD ECUs:
i. Fail if <> 1 CVN for every CAL ID.
ii. Fail if CAL ID not formatted correctly (printable ASCII, padded incorrectly, etc.).
iii. Fail if any received CAL ID is all 0xFFh or any CVN is all 0x00h.
iv. Fail if CVN padded with 16-binary zeros (where either the 1st two bytes are both 00h or the last two bytes both 00h). Note HD OBD CVNs are required to be 32-bits.
<IP_ADDRESS> Warn Criteria
a. Warn if total number of reported CAL IDs is > user entered value for number of emission or diagnostic critical control units (test 6.1.2).
b. Warn if more than one CAL ID and CVN pair is provided in a single DM19 message.
c. For responses from OBD ECUs, warn if 00h is observed in either the first or fourth bytes.
d. For responses from non-OBD ECUs:
i. Warn if any non-OBD ECU provides CAL ID.
ii. Warn if <> 1 CVN for every CAL ID.
iii. Warn if CAL ID not formatted correctly (contains non-printable ASCII, padded incorrectly, etc.).
iv. Warn if any received CAL ID is all 0xFFh or any CVN is all 0x00h.
v. Warn if CVN padded incorrectly (must use 0x00h in MSB for unused bytes).

In order keep track of all the moving parts on this project, I try to keep the changes to the 'document' in tickets which are separate from the 'code' tickets.  This is one such case. Currently the code matches the document as supplied "originally",   #156 is a ticket to update the document; this ticket is to update the source code (so we remember to do both)
At this time, I have this issue marked as "future enhancement" indicating that we are not planning to implement this change in the current release of the software.  It's believe this can wait for the "NOx Binning" changes in V4 of the software.
@ericthomasswenson, do you concur with that?

The SOW text should define the current intent.
Revisit after the next release.


Option to disable anonymous access to workspaces

Description
I'm looking to get the on premises instance up and running in my company but it will be exposed publicly on the internet.
I'm weary of people accidentally exposing workspaces by default because they don't realise they need to limit access manually.
I'd love a config property that prevents access until a user is logged in. Ideally right as the page is initially loaded redirect to login if the user is not authenticated.
Priority
Medium
Resolution
I'm willing to add this feature myself and raise a PR
More information
I'd be willing to dig in and try get this working myself but I'm not very familiar with Spring and Spring Security.
If some guidance can be provided I'll try pick it up, else if someone else is happy to do it that would be great to.

I'm building a plugin feature for one of our customers because they want to ensure workspace security is consistently applied regardless of what users do. It's a work in progress, and not documented yet, but you can find an example (with some basic instructions) at https://github.com/simonbrowndotje/structurizr-onpremises-plugin-example

Great, thank you that looks very promising.


Text orientation setting

Hello
How do I set the direction of the text? I want to rotate 270 degrees. The corresponding XML is
<w:textDirection w:val="lrTbV"/>

Caracal does not support that feature right now.
The README is comprehensive in its description of accepted parameters for each type of content.  If what you want to do is neither listed there nor demonstrated in the sample project, then you can safely assume the library does not implement that feature of OOXML.
If you're up for it, you can try tackling the problem by reviewing these instructions and maybe seeking out past PRs.  The code itself is so rigidly constructed that it tends to provide a firm framework for understanding how new parameters are included.  If not, I tend to work on issues and PRs once a month at a local meetup--but that's a couple weeks from now.  Up to you.

ok.thanks


Compilation failure when building main

Describe the bug
Context:

Ubuntu 20.04

OpenJDK 11

Maven 3.6.3

Keycloak version is irrelevant, this is a compile error

Checkout the main branch.

Run mvn clean install.

Maven build fails with
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project keycloak-benchmark-dataset: Compilation failure
[ERROR] .../keycloak-benchmark/dataset/src/main/java/org/keycloak/benchmark/dataset/DatasetResourceProvider.java:[95,51] incompatible types: org.keycloak.models.KeycloakUriInfo cannot be converted to javax.ws.rs.core.UriInfo

Version
20.0.5
Expected behavior
Project builds, jar is created.
Actual behavior
Project build fails.
How to Reproduce?

Checkout the main branch.
Run mvn clean install.

Anything else?
No response

Thank you for reporting this. The main branch is compiling against the main branch of Keycloak which switched to Jakarta EE earlier this week. I'll create a 0.9 release branch which will target Keycloak 21.1 and earlier later today.

A branch 0.9-release is now available that targets Keycloak 21.1 and earlier.

PR available to fix the compile problems in the main branch: #328


Silence broken OS errors from the WebSocket layer (Fixes #12)

I did some more testing but somehow I cannot replicate the error anymore (at least not in 30 minutes). Previously this error occurred with Gunicorn and also with the default Flask server it is running fine. So maybe it is more related to some Gunicorn setting as stated here:
https://github.com/benoitc/gunicorn/issues/1877


Handle exceptions, per SonarCloud rules

All catch blocks must do something to indicate the exception isn't ignored.
Signed-off-by: Cary Phillips<EMAIL_ADDRESS>

Thanks @meshula. This change is big enough I’d like somebody else to look
it over as well before merging.
On Sun, Jul 7, 2019 at 7:16 PM Nick Porcino<EMAIL_ADDRESS>wrote:

@meshula approved this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openexr/openexr/pull/425?email_source=notifications&email_token=AFC3DGPXMLUF6NGOZWA2NADP6KPRVA5CNFSM4H6XDLI2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB5VOHCI#pullrequestreview-258663305,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFC3DGJMKO3QRQ45P73T4HLP6KPRVANCNFSM4H6XDLIQ
.

--
Cary Phillips | R&D Supervisor | ILM | San Francisco


Unable to install on Heroku with Pip or npm

This is related to issue #194- Plotly-orca works flawlessly on my local machine, but unfortunately after following every thread I can find on getting this up on a server like Heroku- I'm unable to get this working.
So far I've successfully installed electron & Orca within Heroku, I've installed dependencies through a APT buildpack and Aptfile but still continually receive the following error in Django:

The orca executable is required in order to export figures as static images,
but the executable that was found at '/app/node_modules/.bin/orca'
does not seem to be a valid plotly orca executable. Please refer to the end of
this message for details on what went wrong.

I would definitely prefer to continue using Plotly if possible, though without the ability to export an image, I may unfortunately need to look elsewhere.

It should be possible to pack orca into Python wheel as data file - https://setuptools.readthedocs.io/en/latest/setuptools.html#including-data-files
If orca could be compiled into a static binary, that would be the easiest way.

If orca could be compiled into a static binary, that would be the easiest way.

@abitrolly this is something we are looking into to make it easy to install Orca anywhere via pip. Stay tuned!

@gugmi01  about heroku, one will need all the dependencies required to run chromium browser AND xvfb to run things in a headless manner (see http://elementalselenium.com/tips/38-headless). Usually this is done with xvfb-run -a orca graph ....
I hope this helps!

@antoinerg Chrome has the --headless option that doesn't need xvfb https://developers.google.com/web/updates/2017/04/headless-chrome#screenshots


Implement the architecture changes

The component level architecture for Blogly need to be revised and development changes to be done accordingly.

![Uploading 1A7EAEAF-EE74-4FCC-9EB1-8CC1C280CA15.jpeg…](component diagram)
Please refer to the high level component diagram

Updated high level component diagram for Blogly


Set Up Repository and Folder Structure

Description
Create a new GitHub repository named Bootstrap-Portfolio and set up the initial folder structure for the webpage.
Acceptance Criteria
Repository created with the name Bootstrap-Portfolio.
Folder structure includes index.html, css folder with style.css file, and an images folder.
Tasks
Create Bootstrap-Portfolio repository on GitHub.
Clone the repository to your local machine.
Set up the folder structure as specified.

I have successfully completed the tasks for this issue:
Created the Bootstrap-Portfolio repository on GitHub.
Cloned the repository to my local machine.
Set up the folder structure with index.html, css folder containing style.css file, and an images folder.
The repository is now ready for further development.


magma build failure on x86_64-linux as of 0fbb6483

Issue description
Build of magma failed on x86_64-linux as of 0fbb6483cf73b18d4ef0b927892dcc36642c0e8f. This is currently breaking python3Packages.torchvision.
error: builder for '/nix/store/wpj21dfjmxmrc68p0cqbgynj6b1bd4ni-magma-2.7.2.drv' failed with exit code 1;
       last 10 log lines:
       >       |          ^~~~~
       > [6/3430] Building CXX object CMakeFiles/magma.dir/control/magma_f77.cpp.o
       > FAILED: CMakeFiles/magma.dir/control/magma_f77.cpp.o
       > /nix/store/kp1ds8v0igyma875qf08fi26i4vxv7k2-gcc-wrapper-12.3.0/bin/c++  -I/build/magma-2.7.2/build/include -I/build/magma-2.7.2/include -I/build/magma-2.7.2/control -I/build/magma-2.7.2/magmablas -I/build/magma-2.7.2/sparse/include -I/build/magma-2.7.2/sparse/control -I/build/magma-2.7.2/testing -std=c++11 -fopenmp -Wall -Wno-unused-function -O3 -DNDEBUG -MD -MT CMakeFiles/magma.dir/control/magma_f77.cpp.o -MF CMakeFiles/magma.dir/control/magma_f77.cpp.o.d -o CMakeFiles/magma.dir/control/magma_f77.cpp.o -c /build/magma-2.7.2/control/magma_f77.cpp
       > In file included from /build/magma-2.7.2/control/magma_f77.cpp:2:
       > /build/magma-2.7.2/include/magma_mangling.h:32:10: error: #error "One of ADD_, NOCHANGE, or UPCASE must be defined to set how Fortran functions are name mangled. For example, in MAGMA, add -DADD_ to CFLAGS, FFLAGS, etc. in make.inc. If using CMake, it defines MAGMA_GLOBAL instead."
       >    32 |         #error "One of ADD_, NOCHANGE, or UPCASE must be defined to set how Fortran functions are name mangled. For example, in MAGMA, add -DADD_ to CFLAGS, FFLAGS, etc. in make.inc. If using CMake, it defines MAGMA_GLOBAL instead."
       >       |          ^~~~~
       > [7/3430] Building CXX object CMakeFiles/magma.dir/control/constants.cpp.o
       > ninja: build stopped: subcommand failed.
       For full logs, run 'nix log /nix/store/wpj21dfjmxmrc68p0cqbgynj6b1bd4ni-magma-2.7.2.drv'.
error: 1 dependencies of derivation '/nix/store/wxa77ds6vic0b8w1ny7s0q9szcv360sm-python3.11-torch-2.1.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/5dimzsv1xaaa4dlaxk6x4qrgr95c6bq0-python3.11-torchvision-0.16.2.drv' failed to build

full build log
python3Packages.torchvision maintainers cc: @ericsagnes
magma maintainers cc: @connorbaker
Other cc: n/a
Steps to reproduce

Checkout nixpkgs at commit 0fbb6483cf73b18d4ef0b927892dcc36642c0e8f
Run nix-build -A magma

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 6.2.0-1018-azure, Ubuntu, 22.04.3 LTS (Jammy Jellyfish), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.16.1`
 - nixpkgs: `/nix/store/wnqbjr7yipmm0vgg2isvhl2lq4hvq6b9-source`

Contents of ~/.config/nixpkgs/config.nix:
{ allowUnfree = true; cudaSupport = true; cudaCapabilities = ["8.0"]; }

Misc.
This issue was automatically generated by nixpkgs-upkeep.

CI workflow that created this issue.
Internal tags: -7982697571684434887<PHONE_NUMBER>084806304

Not sure if this will be helpful to anybody, but I had this issue with building pytorch on unstable. Changing to 23.11 has resulted in a successful build

dup of https://github.com/NixOS/nixpkgs/issues/281656


Keyboard shortcuts for controlling playback

Hitting spacebar should pause/play music, and hitting ctrl/cmd + left/right should go to the previous or next track!

Thank you for the request. I'll look at improving the keyboard shortcuts for music controls.
Just a note - any browser supporting Media Keys (like Google Chrome) can be controlled using the media controls on a keyboard (if you have them).


lint-readme: insert semicolons more discerningly

The script (see below) that rewrites code blocks for linting should be smarter about inserting semicolons, so that the linter will not complain about misplaced semicolons.
https://github.com/sanctuary-js/sanctuary-scripts/blob/ce8733dbb2ab7da12e7418559e7b3030886d24f8/bin/lint-readme#L16-L41
See https://github.com/Avaq/permissionary/pull/5 for discussion leading up to this.

Why do we have a script to rewrite code blocks? Is this to work around limitations of ESLint?

@gabejohnson Because codeblocks are written for https://github.com/davidchambers/doctest with additional information prefixed to every line in the form of >, ., and ! characters.

Ahhh...those code blocks. Thanks for the explanation Aldwin 😄


List of not-covered topics

Just need to write these down before I forget:

[ ] Dev shells through nix
[ ] wrapping
[ ] overrides
[ ] How to debug builds (nix develop .#)
[ ] hardware acceleration (addOpenGLRunpath)
[ ] Shell Hooks
[ ] Common trivial builders
[ ] patching
[ ] pname + version vs name?
[ ] meta?
[ ] How contribute to nixpkgs
[ ] flakes
[ ] overlays
[ ] Example build section?

[ ] go
[ ] cmake
[ ] gnumake (this is kind of already covered in the stdenv section)
[ ] autotools
[ ] rust
[ ] python

I have another one. Let attribute-sets let {}. Not sure if it needs to be covered though, as I think it's just the the syntatic desugaring of rec blocks, although a bit more explicit.

Let attribute-sets

I'm not even familiar with this. But as an interesting aside, let blocks are implemented as a rec attr set.

I only found about them recently after getting to know the Nix tree-sitter grammar a bit. So for let {}, lets label the attribute-set x. It must contain a body key which is an arbitrary expression where all the other attributes defined in x are in scope. It is essentially another syntax for let in. And if x is an attribute-set itself, can be used as an alternative to rec. So:
let {
  x = 1;
  y = 2;
  body = x + y;
}

evals to 3.

seems pretty advanced, in rust-lang book terms, I think that would be something which would go into the rust-nomicon instead "intro to nix" book :/

Was thinking of moving back the build a package section and instead putting a how to use nixpkgs section. Then cover, the most common scenarios: using a flake, using nix develop, nix build, nix eval


Wrong documentation

It says "Edge.package.update.samples.zip", but in the github repo, there is no release item with that name:
https://github.com/Azure/iot-hub-device-update/releases
I assume:
https://github.com/Azure/iot-hub-device-update/releases/download/0.8.2/Tutorial_IoTEdge_PackageUpdate.zip
[Enter feedback here]

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

ID: fae57922-c3b2-5fb6-230a-9be79c40c774
Version Independent ID: 5650812e-bdcf-8f72-dfec-36474795f474
Content: Device Update for Azure IoT Hub tutorial using the Ubuntu Server 18.04 x64 package agent
Content Source: articles/iot-hub-device-update/device-update-ubuntu-agent.md
Service: iot-hub-device-update
GitHub Login: @vimeht
Microsoft Alias: vimeht

@SeryioGonzalez Thanks for the feedback! We are currently investigating and will update you shortly.

@SeryioGonzalez PR has been raised to fix this. Thanks again for sharing the feedback. Issue will be closed automatically once PR has been reviewed and merged.


Out of date Service Bus -> Event Grid guide

"In the Azure portal, go to your namespace and then, in the left pane, select Events. Your namespace window opens, with two Event Grid subscriptions displayed in the right pane."
This seems out of date - there is no Events pane.

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

ID: 4621fa71-af49-3eb2-83ce-39d1c7aa8a13
Version Independent ID: 23eef85f-4540-518d-e204-71b34b27e1b7
Content: Handle Service Bus events via Event Grid using Azure Functions - Azure Service Bus
Content Source: articles/service-bus-messaging/service-bus-to-event-grid-integration-function.md
Service: service-bus-messaging
GitHub Login: @spelluru
Microsoft Alias: spelluru

@Keylan You will see Events pane only if you have created the premium service bus namespace as mentioned in the document

Currently, the event grid is only supported for the premium namespace, and for other SKUs, you will not see the Events pane option.
Hope the above clears things up. Please let me know if you have any queries or concerns.


Adds model category from hf config file

Rebased #498 and added functionality to allow individual models to override config model types to bridge discrepancy between hf model categories and mlc model categories.

Hi @sbelcmu , it seems the discrepancy between gpt_bigcode and code_gpt is still not resolved. I suppose adding the rule to model_category_override should work.

Hi @yzh119, I pushed some minor bug fixes, but the line you are referencing is actually the conv_template and not the model_category. I verified this manually, and the gpt_bigcode model category is getting called correctly in the code. Do you want me to change the conv template names to match as well?


Allow InterceptableView to return the status value

This change allows Ruby interceptors access to the response status code.

@apolcyn Have you had a chance to look at this?

Can we add a test, perhaps involving some interceptor that makes an RPC to a server, the server returns some status code and we check that the interceptor can see it? (if nothing else, this would be useful I think just for the example code). It could be added into e.g. https://github.com/grpc/grpc/blob/master/src/ruby/spec/generic/client_interceptors_spec.rb, or in it's own file.

I'm trying to run the tests but I'm getting new failures that don't see to be related. I just tried master and have even more failures. Not sure if this is local to my system or not. But it is slowing me a bit on this. I'll get the test updated/added as soon as I can.

I can trigger a CI run again, and if you can then see the linked output that might help


Miscellaneous conformance cleanups

Some changes that I made while trying to narrow down and fix https://github.com/apple/swift/pull/17993. Ultimately the fix turned out to be much simpler, but these cleanups make sense anyway. I'm submitting them in a separate PR to ensure that both pass tests independently, since I intend on cherry-picking the actual fix to swift-4.2-branch.

@swift-ci Please smoke test

@swift-ci Please test source compatibility


Hostname match not found

After doing the required changes and clicking on "Get OTP" button it pops up the message "Hostname match not found". Please help.

when you are loggin in try using url like this http://localhost:8080
Anything apart from local host is not whitelisted


update the dep checker to check glide instead of godep files

Note that we're still out of sync on some deps, i'm not sure it's realistic to get back in sync right now.

And the contributing.md file still mentions godeps ... that should be updated to reflect the new flow

updated

done
On Mon, Apr 2, 2018 at 1:20 PM, Gabe Montero<EMAIL_ADDRESS>wrote:

@gabemontero commented on this pull request.
In CONTRIBUTING.md
https://github.com/openshift/source-to-image/pull/861#discussion_r178594733
:

@@ -89,14 +89,14 @@ Run the integration tests with:

Installing Godep
section looks good, but shouldn't the section title also change Godep to
Glide
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openshift/source-to-image/pull/861#discussion_r178594733,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEvl3mmLk6NwXf5Y7uM-bygAV2wRQSj9ks5tkl3LgaJpZM4TDo1c
.

--
Ben Parees | OpenShift

/lgtm

this repo is still on rosie because of the windows testing that can't easily be converted to the new job model.
[merge]


ProtectKeysWithDpapiNG with Certificate

Hello,
I would like to encrypt critical data stored in database.
The database is used by several applications/servers.
If I understood, I have to use ProtectKeysWithDpapiNG with a certificate to encrypt/decrypt data on different servers.
configuration.ProtectKeysWithDpapiNG("CERTIFICATE=Hashid:myThumbprint" DpapiNGProtectionDescriptorFlags.None);

But it does not work correctly in my opinion:

No error when the certificate does not exist.
If I delete the files in %LocalAppData%\ASP.NET\DataProtection-Keys, I can't decrypt encrypted values before. How to decrypt data on different servers?

Thank you,
Best regards,
Yann

This package isn't really intended for long-term encryption of data at rest. It's geared more toward transient data.
Consider instead using SQL Server's built-in transparent data encryption at rest (https://msdn.microsoft.com/en-us/library/bb934049.aspx), Azure Storage's E2E encryption (https://azure.microsoft.com/en-us/documentation/articles/storage-client-side-encryption/), or similar technology appropriate for your specific database.

This issue was moved to aspnet/Home#2526


When i update to latest version.（6.1.5）  Appear a problem - 'cellCacheSection does not exist.'

When I from 6.1.1 version update to the latest version.

I read the assert  message.  but i don't know this problem What is the cause.

if youre online can you join here? -> https://gitter.im/patchthecode/JTAppleCalendar

I will need more information.
Can you show me your configureCalendar function?

closing this issue unless for information comes to light.
Version 7.0.0 on separate branch has many fixes and performance enhancements.


Avoid using a global variable

static으로 선언된 RUNTIME_POLICY_LIST를 없애고 일반 변수로 대체합니다.

Codecov Report
Base: 7.79% // Head: 7.74% // Decreases project coverage by -0.05% :warning:

Coverage data is based on head (7f2fb39) compared to base (0839059).
Patch coverage: 5.55% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff            @@
##            main     #40      +/-   ##
========================================
- Coverage   7.79%   7.74%   -0.05%
========================================
  Files          7       7
  Lines        706     710       +4
========================================
  Hits          55      55
- Misses       651     655       +4

Impacted Files
Coverage Δ

src/main.rs
0.00% <0.00%> (ø)

src/request.rs
0.00% <0.00%> (ø)

src/subscribe.rs
0.00% <0.00%> (ø)

src/subscribe/tests.rs
48.05% <100.00%> (ø)

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

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


add .editorconfig and CONTRIBUTING.md

Handles Issues-51.

Coverage remained the same at 85.612% when pulling 1edcbb16bd58bb5dd492e011f9c6b2a57d573939 on fagossa:master into 3463dd9bbafab56bddeebb46adc1ec8cd57369ed on liquigraph:master.

Aaaaah, super! Je vais merger ASAP.

Thanks for your contribution!
Maybe it would be nice to specify some more file types (e.g. *.xml)? And I personally like the .editorconfig for each type sorted by alphabet.

Hello @mvitz ,
I've just sorted the entries and added some default settings for xml and md.

Coverage remained the same at 85.612% when pulling 75579464aae97561ad4e8675e4c497718bc26dfa on fagossa:master into 3463dd9bbafab56bddeebb46adc1ec8cd57369ed on liquigraph:master.

Coverage remained the same at 85.612% when pulling 75579464aae97561ad4e8675e4c497718bc26dfa on fagossa:master into 3463dd9bbafab56bddeebb46adc1ec8cd57369ed on liquigraph:master.

Looks good to me. I would vote for a merge!

Finally merged in master and 2.x, with minor changes. Thanks a lot!


Stop() Command

I have Bootstrap Tour set up so that the tour is not shown when in resolutions below 768px, as it doesn't work well with the hamburger menu (in my layout). I'd like to stop the tour when the user resizes to 767px or lower. However, if I .end() the tour, won't that lose the user's position?
Since there is a start() command, should there be a corresponding stop() command along with end()

No, .end doesn't lose the user's position. You can use start(true) to continue after end.


Add support for "new" Lambda env variables

Documentation here.
Example:
:cljs-lambda {
  :defaults {:env {:table-name "abc"}}
  :functions [{
    :name "abc"
    :invoke "def"
    :env {:extra-stuff "xyz"}}]}

:defaults contains env variables for all functions. :env inside :functions list is merged with environment variables from :defaults.
Docs quote: environment variables must start with a-zA-Z and can contain a-ZA-Z0-9_.
We will transform keywords in this way:

upper case
all not allowed characters replaced with _

We will not check these variables and we will let aws cli to fail if they do not meet requirements.
We need to add this to:

[x] create function
[x] update function

Update function is little bit harder, because we have to get function configuration (if it exists) and compare it. We can do it in the same way as we did in https://github.com/nervous-systems/cljs-lambda/pull/48.
Sounds good?

P.S. I'll skip KMS key in this round, because the default one is used automatically and is free of charge.

@zrzka I think this proposal makes sense, the only snag is whether/how to integrate it with the existing environment variable support, which is basically a hack which sets the variables for all functions within the Node process, before the handler is invoked.  I think abandoning that and using the AWS support for per-function environment variables makes sense.  The one think I like about the existing feature is the :capture functionality for copying values from the build environment by partially/exactly matching the name.
My concern with mangling is that the keys will likely be looked up at runtime in an environment which doesn't have access to the same keyword->env var mangling function.  The runtime library has a facility for retrieving environment variables which is provided so that the environment can be mocked during tests - if we went with mangling, that function could be modified to perform the same transformations before doing a lookup - but I'm sure not many people use that function.  I personally prefer unmangled values for those reasons, but I'm open-minded.
My proposal would be allowing strings or keywords, but not mangling, removing the existing environment variable setting, but supporting a similar format which continues to allow build-time capture:
:cljs-lambda {
  :defaults {:env {:set {"TABLE_NAME" "abc"}
                   :capture ["EXACT_MATCH" #"PARTIAL_"]}}
  :functions [{
    :name "abc"
    :invoke "def"
    :env {:set {:EXTRA_STUFF "xyz"}}}]}

Does any of that make sense?
If you think capturing is going to happen a lot less often than setting fresh variables, an alternative format would be {:env {"TABLE_NAME" "abc" :cljs-lambda/capture ["EXACT_MATCH" ...]}} - i.e. an optional namespaced key, which would allow the :set to be avoided in the common case.

@moea I agree with mangling, we should skip it. Not sure about :capture, because I don't use it and don't know anyone who actually use it as well. But we can keep it there and do it your way:
project.clj
:cljs-lambda {
  :defaults {:env {:set {"TABLE_NAME" "abc"}
                   :capture ["EXACT_MATCH" #"PARTIAL_"]}}
  :functions [{
    :env {:set {:EXTRA_STUFF "xyz"}
          :capture ["ANOTHER_MATCH"]}}]}

profiles.clj
{:production {:cljs-lambda {:defaults {:env {:set "TABLE_NAME" "def"}
                                             :capture ["EXACT_MATCH" #"PARTIAL_"]}}}}

Processing

:cljs-lambda :defaults :env will be merged with :profile :cljs-lambda :defaults :env (if provided), lein is actually doing this
for every function, this merged :env will be merged with per function :env
for the resulting :env

:capture variables
overwrite them (or add new ones) from :set (current :env behavior)

use the result in create function or update function configuration

IOW no hacks to set this in node process, but actually set these as real AWS Lambda vars

@zrzka Yeah, that sounds good.  I just checked, I'm not using :capture - if it's awkward to reuse the existing code, or you don't like the feature, then removing it is fine - I think the user could interpolate the variables themselves, anyway, in the project file anyway, like {"TABLE_NAME" ~(System/getenv "TABLE_NAME")}

@moea it's not awkward, it just looks complicated, maybe confusing, ... Compare ...
{:defaults {:env {"TABLE_A" "table"
                  "TABLE_B" ~(System/getenv "TABLE_B")}}}

vs
{:defaults {:env {:set {"TABLE_A" "table"}}
                  :capture ["TABLE_B"]}}

First one looks more cleaner.
And now imagine how complicated it can look like when leiningen starts merging (iow replacing) lists of captures when additional profiles are provided, what has higher / lower precedence, ...
I don't know, I'm tempted to propose :capture removal and use simple :env without :set and :capture.

@zrzka Cool, that's totally fine with me.

@moea okay, cool, will do it

Didn't forget ;-) We have a release next week, so, then will have time for this. And will add DLQ configuration as well. Sry for the delay.

@zrzka Excellent!

Okay, so, to sum it up after a while ... Configuration example ...
:cljs-lambda {:defaults  {:role "arn:aws:..."
                          :dead-letter "arn:aws:..."
                          :env {"TABLE_A" "aaaa"
                                "TABLE_B" ~(System/getenv "TABLE_B")}}
              :functions [{:name "SomeLambdaFunctionName"
                           :invoke some.lambda.function.name/handler
                           :dead-letter "arn:aws:..."
                           :env {"TABLE_C" "ccccc"}}]}

AWS CLI documentation:

--dead-letter-config TargetArn=$arn (:dead-letter)
--environment Variables={KeyName1=string,KeyName2=string} (:env)

@zrzka Looks good to me

Implemented & merged via following PRs:

https://github.com/nervous-systems/cljs-lambda/pull/65
https://github.com/nervous-systems/cljs-lambda/pull/66

Available since 0.6.5-SNAPSHOT. Closing.


/debug/vars: empty maps getting marshalled to null in 1.0

This is causing Telegraf to drop these "metrics" from /debug/vars
influxdb 0.13
curl -s http://<IP_ADDRESS>:8086/debug/vars | grep queryExecutor
"queryExecutor": {"name": "queryExecutor", "tags": {}, "values": {"queriesActive": 0, "queryDurationNs":<PHONE_NUMBER>58}},

influxdb 1.0
curl -s http://<IP_ADDRESS>:8086/debug/vars | grep queryExecutor
"queryExecutor": {"name":"queryExecutor","tags":null,"values":{"queriesActive":0,"queryDurationNs":253281846806}},

issue in telegraf: https://github.com/influxdata/telegraf/issues/1738

this is actually just an issue with telegraf, the JSON unmarshalling still works with null but we were doing some special null checking for no particular reason


🌱 Explicit permissions for github actions

To improve OSSF Scorecard score on Scorecard repo as per #1618 I have made the permissions on some GitHub workflows more explicit.

you need to "fix" the description of your PR by adding:
```release-notes
Add Explicit permissions to our github actions


FIX: handle np.bool_

closes https://github.com/h5io/h5io/issues/12

That's about what I hoped it'd be, I'll merge once the CIs come back happy.

Coverage increased (+0.05%) to 97.523% when pulling e9063a0f9cba939f006c2fedb70bb608388cf7b4 on kingjr:np_bool_ into bc736b7881271654a4999573dd06a65800dccb5d on h5io:master.

Thanks @kingjr


Adding CI configuration for DGX-A100 at LSU

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)---(=)InfoPropertyBeforeAfterHPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a953b0e7d1853d49081e13cba73dc8e060fd5fff9ceHPX Datetime2022-05-31T12:57:29+00:002023-01-11T13:53:52+00:00Hostnamenid01193nid00273ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2022-05-31T15:13:01.357969+02:002023-01-11T15:13:33.660445+01:00EnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch+InfoPropertyBeforeAfterHPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a953b0e7d1853d49081e13cba73dc8e060fd5fff9ceHPX Datetime2022-05-31T12:57:29+00:002023-01-11T13:53:52+00:00Hostnamenid01193nid00273ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2022-05-31T15:13:18.026239+02:002023-01-11T15:13:50.052693+01:00EnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)++(=)Stream Benchmark - Triad(=)+-Stream Benchmark - Copy(=)+(=)InfoPropertyBeforeAfterHPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01a3b0e7d1853d49081e13cba73dc8e060fd5fff9ceHPX Datetime2021-11-10T19:14:21+00:002023-01-11T13:53:52+00:00Hostnamenid00120nid00273ClusternamedaintdaintCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Datetime2021-11-10T20:28:18.266961+01:002023-01-11T15:14:05.251819+01:00EnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)(=)(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-01-16T20:30:19+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eeb9dc92067b822b5f37db4c6feef89d2a28c201bdDatetime2023-01-13T04:10:15.951027-06:002023-01-16T14:42:56.851520-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch+InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-01-16T20:30:19+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eeb9dc92067b822b5f37db4c6feef89d2a28c201bdDatetime2023-01-13T04:10:31.068958-06:002023-01-16T14:43:11.784692-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add------+++Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad------+++Stream Benchmark - Copy(=)-(=)InfoPropertyBeforeAfterHPX Datetime2023-01-12T23:07:58+00:002023-01-16T20:30:19+00:00HPX Commiteb604d5bfa8744d3c9cb3af402809c54e3d8f4eeb9dc92067b822b5f37db4c6feef89d2a28c201bdDatetime2023-01-13T04:10:46.398919-06:002023-01-16T14:43:27.315739-06:00Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduCompiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)+(=)InfoPropertyBeforeAfterHPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a95b9dc92067b822b5f37db4c6feef89d2a28c201bdHPX Datetime2022-05-31T12:57:29+00:002023-01-16T20:30:19+00:00EnvfileDatetime2022-05-31T15:13:01.357969+02:002023-01-16T21:43:52.370289+01:00Hostnamenid01193nid01376Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPX Commitd5655f89770ba953e8de3ceb349567d5fcb74a95b9dc92067b822b5f37db4c6feef89d2a28c201bdHPX Datetime2022-05-31T12:57:29+00:002023-01-16T20:30:19+00:00EnvfileDatetime2022-05-31T15:13:18.026239+02:002023-01-16T21:44:10.238433+01:00Hostnamenid01193nid01376Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)+(=)Stream Benchmark - Scale(=)+++(=)Stream Benchmark - Triad(=)++=Stream Benchmark - Copy(=)++(=)InfoPropertyBeforeAfterHPX Commit71d8dbe40b737be02ea734f9d98fcc0b1e21f01ab9dc92067b822b5f37db4c6feef89d2a28c201bdHPX Datetime2021-11-10T19:14:21+00:002023-01-16T20:30:19+00:00EnvfileDatetime2021-11-10T20:28:18.266961+01:002023-01-16T21:44:25.801744+01:00Hostnamenid00120nid01376Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Trying this locally on the node I get the CUDA error '''ERROR 802:system not yet initialized''' for the failing tests.
Is the nvidia fabric manager not installed on this particular node by any chance? (see here )

Al rebuilt the node and the fabric manager is now installed and running.
It seems that this fixed the issues, I am now able to run all tests (including the cuda ones) successfully on the machine.
The jenkins pipeline should succeed once we merge master into this branch (to get the fixes from #6248 ). Ideally, we should still fix the CMAKE_CUDA_ARCHITECTURE as suggested above. @hkaiser Can you try that? I do not seem to have permission to push directly to the dgx_a100 branch.

Al rebuilt the node and the fabric manager is now installed and running. It seems that this fixed the issues, I am now able to run all tests (including the cuda ones) successfully on the machine.
The jenkins pipeline should succeed once we merge master into this branch (to get the fixes from #6248 ). Ideally, we should still fix the CMAKE_CUDA_ARCHITECTURE as suggested above. @hkaiser Can you try that? I do not seem to have permission to push directly to the dgx_a100 branch.

That's done now. Thanks!

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)??-InfoPropertyBeforeAfterHPX Datetime2023-05-10T12:07:53+00:002023-06-01T23:27:21+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b26d1c9775413733d74ed1978db39e23472e464447Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-05-10T14:50:18.616050-05:002023-06-01T18:35:21.767737-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch=InfoPropertyBeforeAfterHPX Datetime2023-05-10T12:07:53+00:002023-06-01T23:27:21+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b26d1c9775413733d74ed1978db39e23472e464447Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-05-10T14:52:35.047119-05:002023-06-01T18:37:38.022837-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)=(=)Stream Benchmark - Scale(=)(=)(=)Stream Benchmark - Triad(=)=(=)Stream Benchmark - Copy=(=)=InfoPropertyBeforeAfterHPX Datetime2023-05-10T12:07:53+00:002023-06-01T23:27:21+00:00HPX Commitdcb541576898d370113946ba15fb58c20c8325b26d1c9775413733d74ed1978db39e23472e464447Hostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduDatetime2023-05-10T14:52:52.237641-05:002023-06-01T18:37:55.204101-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamEnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPX PerformanceComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORFor Each(=)??-InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b25ee21b81cab035e137a04456a999c37f82f93729HPX Datetime2023-05-10T12:07:53+00:002023-06-02T00:00:51+00:00Datetime2023-05-10T14:50:18.616050-05:002023-06-01T19:36:56.441705-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch=InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b25ee21b81cab035e137a04456a999c37f82f93729HPX Datetime2023-05-10T12:07:53+00:002023-06-02T00:00:51+00:00Datetime2023-05-10T14:52:35.047119-05:002023-06-01T19:39:12.776317-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileComparisonBENCHMARKFORK_JOIN_EXECUTOR_DEFAULT_FORK_JOIN_POLICY_ALLOCATORPARALLEL_EXECUTOR_DEFAULT_PARALLEL_POLICY_ALLOCATORSCHEDULER_EXECUTOR_DEFAULT_SCHEDULER_EXECUTOR_ALLOCATORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale(=)==Stream Benchmark - Triad(=)=(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPX Commitdcb541576898d370113946ba15fb58c20c8325b25ee21b81cab035e137a04456a999c37f82f93729HPX Datetime2023-05-10T12:07:53+00:002023-06-02T00:00:51+00:00Datetime2023-05-10T14:52:52.237641-05:002023-06-01T19:39:30.033664-05:00Compiler/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1/opt/apps/llvm/13.0.1/bin/clang++ 13.0.1ClusternamerostamrostamHostnamemedusa08.rostam.cct.lsu.edumedusa08.rostam.cct.lsu.eduEnvfileExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Brilliant, this seems to work now! Thanks @akheir, @G-071!

bors merge


Neon not detected on armv7hl

As reported in #289, neon instruction set is not detected when building on armv7hl.
A workaround is  #define XSIMD_FORCE_ARM_INSTR_SET = 70000000 before including any header of xsimd.

As long as -march=armv7-a is defined, this now works properly, see https://godbolt.org/z/7YYGxKxso


Update Warning Alert

refer to the following image and the figma design

to use any icon please use it from Hero Icons
After building the component please raise a PR with a screenshot of the component and update the component in Alerts/src/warning.html
I would like to work on this on myself

I would like to work on this.


Problems rendering adjacent bold and italics

VSCode Version: 0.10.11
OS Version: Win10

Steps to Reproduce:

Render this text in VS Code:
Methods are named AbcObjectAction, where Object describes the object and Action indicates what the function does. For example, AbcDeviceCreate creates a device object.
Compare to GitHub rendering.  Having bold adjacent to italics causes Code to stay in italics mode after the closing italics marker.

Reproduces in latest

Examples to test: (note that they all render correctly on GitHub)
italicsbold
bolditalicsbolditalics
bolditalics
bold

Using _ for italics works fine:
italicsbold
bolditalicsbolditalics
bolditalics
bold

It looks like the specific issue is that the current markdown parser does not consider adjacent * styles. See how the breakage first occurs  in *** styles, treating **bold***... as ``bold*...`
The last one is the exception to this, it would seem as though ** takes precedence over *** for some reason.

I cannot reproduce with our new markdown extension.

Some more problem cases:
****bold italics****
****bold italics****
****bold italics****

\*\*\**italics****

Output on GitHub:
bold italics
bold italics
bold italics
***italics***
VS Code @ 93e65224d7598017bfa0b188a0d82b66a2ee9698:

This issue was moved to Microsoft/vscode-markdown-tm-grammar#7


Crouch jumping broken, or intentional ?

Hi,
when you have crouch_jumping active (like the standard when opening up the project).
Do the crouch jumping but let go of the crouch_button ("c"), shortly after jumping ("space") you gain height to nearly the point where you would regulary land when you jump.
Is this intended ?
For me it looks like the JumpCoolDownTimer is not working.
https://github.com/Phazorknight/Cogito/assets/87974401/a589c0b7-ec9b-4f90-9ff4-170da9eb989a
At first I just crouched and jumped for you to see a marking with the target, otherwise it would be hard to see / recognize if not played by yourself.

Will take a look myself but from your video this looks to me as working as intended.
Crouch-jumping aka duck-jumping has been a staple in quite a few games, and I think the first person controller was explicitly made to support it.
I think the jump cooldown timer is only used to avoid retriggering jumps on bad collisions.

@Phazorknight I have a branch I'm working on to address the visual jitter as well as some improvements for slide jumping

I would say this is very much intentional. I tried to make jumping consistent for crouch jumps and regular jumps by saying that you wind up with the players feet off the ground by exactly the same amount

Ty both. I was not sure as it felt not right for me, I am looking forward for the PR#82  :)

Considering this solved with the merge from #82 / https://github.com/Phazorknight/Cogito/commit/001c48f0dbab6cb4a2450c5d8e988fdb341c893b.


[Bug]: Incorrect Token Usage representation in the Area Chart

🐛 What's Going Wrong?

There are a couple of issues with the Token Usage graph:

Value on Y axis does not correspond to the Max value (Total Tokens). This is because all 3 token usage values(prompt tokens, completion tokens and Total tokens) are stacked. Consequently Y axis displays a sum of all 3 stacked values. Ideally only 2 token usage values should be stacked and total tokens will be an implied value. in my screenshot , Y axis value is 56189. This value is determined by summing up Total tokens(28087), prompt tokens(18326) and completion tokens(9761) + 15.
The token usage is not stacked in the proper order. Lowest value should be dynamically placed first. In my case Completion tokens should be first, followed by prompt tokens. Sum of these should imply/indicate Total tokens.

🕵 Steps to Reproduce

Instrument any LLM app with OpenLIT
Check the token usage graph

🎯 What Did You Expect?

For issue 1 : Y axis value should be total tokens + 15 instead of total tokens + prompt tokens + completion tokens + 15
For issue 2: Lowest value (completion tokens) is placed at the bottom followed by the next higher value (prompt tokens). Stacking order should be dynamically determined

📸 Any Screenshots?

💻 Your Setup

OpenLIT Version: 1.11.2
OpenLIT SDK Version: 1.24.1
Deployment Method: [Docker]

📝 Additional Notes

Got more to say? Tell us here.

👐 Want to Help Make It Happen?

[ ] Yes, I'd like to volunteer and help out with this!

Thanks @Nidhin117 for pointing this out.
Area charts work pretty this way :

let's say if there are prompt token 4 , completion tokens 2 and total tokens 6
then prompt tokens area points will start from 0-4, completion tokens will be from 4-6, and total tokens will be from 6-12.
which is what is represented in the above chart.

But it's actually is confusing with the total tokens area in the chart. So, its better to keep just prompt tokens & completion tokens, which is what should be done in the above issue.

Hey @AmanAgarwal041  and @patcher9 , thanks for fixing this. It works as expected now.


Main landing page

One of us need to work on the main landing page to make it look like the IT Help Desk website.

Specifically, edit the NavBar and Footer components to mimic the one found here. Don't forget the "Home > AskUs", though that element should probably go into the landing page itself.
Not entirely sure about the exact page body content yet, but most likely will need FAQ similar to image above. Ideally implement modularly so that you can list 8-10, with input for them coming from database/backend.


Prune redundant API for new release

master is getting more and more feature complete every day.
We should go through and remove redundant API and potentially clean existing API with the attempt at reducing pointless API surface.
Some things to look at (but not limited to):

Templates
BaseElement::getSummary

Related: #347


Fix CI (again)

This fixes a failing pipes test and removes one warning.

Also the Cargo Machete issue remains because we're installing HighlightIO despite not using it, should we get rid of it? If we do, we will probably get a green checkmark for all commits.


No logs displayed in SST Console during local development with sst dev

Description
I am unable to see logs in the SST Console when running my application locally with sst dev. The deployment process seems to work fine as the functions are being built and deployed correctly. However, the logs section in the SST Console shows "Nothing was logged in this invocation," even though I expect to see output from my lambda functions.
Steps to Reproduce

Run sst dev to start local development.
Invoke the lambda function via the application or using an API endpoint.
Check the SST Console for logs.

Expected Behavior
Logs from the lambda invocation should be visible in the SST Console, showing outputs and any errors encountered during the execution.
Actual Behavior
The SST Console's logs tab shows "Nothing was logged in this invocation" despite the functions executing as expected.
Additional Information

SST version: SST ❍ ion 0.0.368

Possible Solution
(Optional) Any suggestions on how to fix or further diagnose the issue would be appreciated.

can you show me a screenshot of the console?


import_meta_graph fails: NcclAllReduce

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): no
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04.5
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version (use command below): v1.12.0-rc2-3-ga6d8ffa 1.12.0
Python version: 3.5.2
Bazel version (if compiling from source): 0.16.1
GCC/Compiler version (if compiling from source): gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)
CUDA/cuDNN version: CUDA 9.1, cuDNN 7.1.3
GPU model and memory: dual 1080Ti (11178MiB)

I trained a model with MirroredStrategy across two GPUs on a single machine using the Estimator API (custom Estimator). I'm unable to load the meta graph with the error:
$ python test.py
2018-11-12 22:16:59.061730: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1432] Found device 0 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.582
pciBusID: 0000:03:00.0
totalMemory: 10.92GiB freeMemory: 10.76GiB
2018-11-12 22:16:59.271191: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1432] Found device 1 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.582
pciBusID: 0000:04:00.0
totalMemory: 10.91GiB freeMemory: 10.76GiB
2018-11-12 22:16:59.283574: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1511] Adding visible gpu devices: 0, 1
2018-11-12 22:17:01.209999: I tensorflow/core/common_runtime/gpu/gpu_device.cc:982] Device interconnect StreamExecutor with strength 1 edge matrix:
2018-11-12 22:17:01.210032: I tensorflow/core/common_runtime/gpu/gpu_device.cc:988]      0 1
2018-11-12 22:17:01.210038: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1001] 0:   N Y
2018-11-12 22:17:01.210042: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1001] 1:   Y N
2018-11-12 22:17:01.210423: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1115] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 10405 MB memory) -> physical GPU (device: 0, name: GeForce GTX 1080 Ti, pci bus id: 0000:03:00.0, compute capability: 6.1)
2018-11-12 22:17:01.210742: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1115] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:1 with 10402 MB memory) -> physical GPU (device: 1, name: GeForce GTX 1080 Ti, pci bus id: 0000:04:00.0, compute capability: 6.1)
Traceback (most recent call last):
  File "test.py", line 13, in <module>
    tf.app.run()
  File "/home/sharvil/.virtualenv/tensorflow/lib/python3.5/site-packages/tensorflow/python/platform/app.py", line 125, in run
    _sys.exit(main(argv))
  File "test.py", line 6, in main
    saver = tf.train.import_meta_graph('trained_models/student/3/model.ckpt-59112.meta')
  File "/home/sharvil/.virtualenv/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 1674, in import_meta_graph
    meta_graph_or_file, clear_devices, import_scope, **kwargs)[0]
  File "/home/sharvil/.virtualenv/tensorflow/lib/python3.5/site-packages/tensorflow/python/training/saver.py", line 1696, in _import_meta_graph_with_return_elements
    **kwargs))
  File "/home/sharvil/.virtualenv/tensorflow/lib/python3.5/site-packages/tensorflow/python/framework/meta_graph.py", line 806, in import_scoped_meta_graph_with_return_elements
    return_elements=return_elements)
  File "/home/sharvil/.virtualenv/tensorflow/lib/python3.5/site-packages/tensorflow/python/util/deprecation.py", line 488, in new_func
    return func(*args, **kwargs)
  File "/home/sharvil/.virtualenv/tensorflow/lib/python3.5/site-packages/tensorflow/python/framework/importer.py", line 391, in import_graph_def
    _RemoveDefaultAttrs(op_dict, producer_op_list, graph_def)
  File "/home/sharvil/.virtualenv/tensorflow/lib/python3.5/site-packages/tensorflow/python/framework/importer.py", line 158, in _RemoveDefaultAttrs
    op_def = op_dict[node.op]
KeyError: 'NcclAllReduce'

I'm using the following code to load the meta graph and checkpoint:
import tensorflow as tf

def main(args):
  with tf.Session() as sess:
    saver = tf.train.import_meta_graph('trained_models/student/3/model.ckpt-59112.meta')
    saver.restore('trained_models/student/3/model.ckpt-59112')

if __name__ == '__main__':
  tf.app.run()

Apologies for the delay in responding. Is this still an issue?

Yes, this is still an issue for me. Thanks for taking a look.

I have the same problem. Have you solved this problem?

Same problem here.

Looks like the nccl op is not loaded when the meta_graph is loaded. @azaks2, do you have any clue?

you just need to add *.so compiled file generated by model implementation.
as follows add this line before session and import meta graph.
tf.load_op_library('<compiled_filename>.so')
this function add a new op in tensorflow runtime.
for example. i compiled a model that contains a RoiPooling layer and generated roi_pooling.so file. so that i added this line to my code
tf.load_op_library('op/roi_pooling.so')
and finally it works : )


Revert to original terminal mode on quit

std::process::exit prevents any destructors from being called,
so the termion::raw::RawTerminal is not destroyed and the terminal
remains in raw mode on exit.
Another method to achieve this could be to have ctrl+c/d break the
run loop instead of calling std::process::exit.

Thanks for the PR!
I didn't know about destructors not being called when calling exit, so I'll rework the logic to find a cleaner approach later, but I'll merge this now so it's not in your way.


database option in new Database({...}) doesn't appear to work

The following example from the readme doesn't appear to select the desired database pancakes but instead _system
const db = new Database({
			url: "http://localhost:8529",
			database: "pancakes",
			auth: { username: "root", password: "" },
		});

I can only get it to work by using useDatabase afterwards
const db = new Database({
			url: "http://localhost:8529",
			database: "pancakes",
			auth: { username: "root", password: "" },
		});
db.useDatabase("pancakes");

Is there something I'm missing?

Had a dive into the source code, it should be databaseName


A way to send common query input parameters in all queries

Hello Team,
Is there a way to send common query parameters instead of having it in all queries as input.
In below examples $geo:String, $country:String are common input parameters, which I would like to avoid passing as query parameter which a developer is forced to add in pass in all queries though query mainly needs id or statusId.
Instead I could store it some where and send in all queries from a common place.
Example
query activate($id:String, $name: String, $geo: String, $country: String){
    activate(
        input: {
            id:$id
            name: $name
            geo: $geo
            country: $country
        }
    )
}

query status($statusId: String, $geo: String, $country: String){
    activate(
        input: {
            statusId: $statusId
            geo: $geo
            country: $country
        }
    )
}

I don't think there is something like this at the moment. You can do it in code if you really want to enforce the same geo and country parameters:
class QueryFactory(val geo: String, val country: String) {
  fun activate(id: String, name: String) = ActivateQuery(id, name, geo, country)
  fun status(statusId: String) = StatusQuery(statusId, geo, country)
}

I'm closing this issue. Please leave a message if you want me to reopen it.


Uncaught Exception: Attempting to call a function in a renderer window that has been closed or released. Function provid

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.0.1
Time: Mon Mar 14 2016 08:31:54 GMT 0100 (Mitteleuropäische Zeit)
Error:
Attempting to call a function in a renderer window that has been closed or released. Function provid
Error: Attempting to call a function in a renderer window that has been closed or released. Function provided here: Object.<anonymous> (C:\Users\mseele\AppData\Local\GPMDP_3\app-3.0.1\resources\app\build\inject\GPMInject\interface\mouseButtonNavigation.js:8:8.
    at BrowserWindow.callIntoRenderer (C:\Users\mseele\AppData\Local\GPMDP_3\app-3.0.1\resources\atom.asar\browser\lib\rpc-server.js:201:19)
    at emitTwo (events.js:92:20)
    at BrowserWindow.emit (events.js:172:7)
    at Function.<anonymous> (C:\Users\mseele\AppData\Local\GPMDP_3\app-3.0.1\resources\app\build\index.js:59:48)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #470


SO_NOSIGPIPE not set on ios

I am experiencing trouble with sigpipes using socket2 on ios. The code already sets nosigpipe by default for macos, is there a reason this is not done for ios as well?

No reason I think. I would require changing: https://github.com/alexcrichton/socket2-rs/blob/b3badc7d3d599746a3632666876f1a253476c3c7/src/sys/unix.rs#L264 to #[cfg(target_vendor = "apple")]. @dignifiedquire would you like to send a pr?

Done: https://github.com/alexcrichton/socket2-rs/pull/84
I went with any(target_os = "macos", target_os = "ios") to match the rest of the cfgs in that file

I think for the long term we should move to target_vendor to support tvOS and watchOS (?), but that's fine.


Unnecessary extra volume attachment

Description
Perhaps not really an issue itself but a misunderstanding, but from what I understood, as long as in the block_device_mappings I referenced the same device name, I could override the settings of the root volume from an AMI. I just tried doing that for the volume of a Node Group I created, and it does replace the root volume with my new settings (gp3), yet the generated instance also now has another gp2 volume attached and pointing to /dev/xvdb.
I don't understand where it's coming from, and I don't want it.

[X] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version [Required]: v18.19.0

Terraform version: v1.1.7

Provider version(s): 4.8.0

Reproduction Code [Required]
module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "~> 18"

  cluster_name                    = "myclustername"
  cluster_version                 = "myclusterversion"
  cluster_endpoint_private_access = true
  cluster_endpoint_public_access  = true

  cluster_addons = {
    kube-proxy = {}
    vpc-cni = {
      resolve_conflicts        = "OVERWRITE"
    }
  }

  vpc_id = data.terraform_remote_state.vpc.outputs.vpc_id
  subnet_ids = [
    data.terraform_remote_state.vpc.outputs.private_subnets[0],
    data.terraform_remote_state.vpc.outputs.private_subnets[1]
  ]

  eks_managed_node_group_defaults = {
    ami_type                     = "BOTTLEROCKET_x86_64"
    iam_role_attach_cni_policy   = true
    iam_role_additional_policies = ["arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore"]
  }

  eks_managed_node_groups = {
    saas = {
      min_size     = 1
      max_size     = 1
      desired_size = 1

      capacity_type  = "SPOT"
      instance_types = ["t3a.small", "t3.small", "t2.small"]

      block_device_mappings = {
        root = {
          # Device name changes depending on the instance type
          # https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/device_naming.html
          device_name = "/dev/xvda"
          ebs = {
            delete_on_termination = true
            throughput            = 150
            volume_size           = 20
            volume_type           = "gp3"
          }
        }
      }
    }
  }
}

Steps to reproduce the behavior:

Clear workspace.
terraform init before starting
terraform plan -out=tfplan
terraform apply tfplan

Expected behavior
Instances from Node Groups should only have a single gp3 volume attached to /dev/xvda.
Actual behavior
Instances from Node Groups get a second gp2 volume attached to /dev/xvdb aside from the root gp3 volume attached to /dev/xvda .
Terminal Output Screenshot(s)
From inside the instance, with Session Manager:
bash-5.1# lsblk
NAME     MAJ:MIN RM  SIZE RO TYPE MOUNTPOINTS
loop0      7:0    0  280K  1 loop /x86_64-bottlerocket-linux-gnu/sys-root/usr/share/licenses
loop1      7:1    0 11.6M  1 loop /local/var/lib/kernel-devel/.overlay/lower
                                  /var/lib/kernel-devel/.overlay/lower
xvda     202:0    0   20G  0 disk
|-xvda1  202:1    0    4M  0 part
|-xvda2  202:2    0    5M  0 part
|-xvda3  202:3    0   40M  0 part /boot
|-xvda4  202:4    0  920M  0 part
|-xvda5  202:5    0   10M  0 part
|-xvda6  202:6    0   25M  0 part
|-xvda7  202:7    0    5M  0 part
|-xvda8  202:8    0   40M  0 part
|-xvda9  202:9    0  920M  0 part
|-xvda10 202:10   0   10M  0 part
|-xvda11 202:11   0   25M  0 part
`-xvda12 202:12   0   42M  0 part /local/var/lib/bottlerocket
                                  /var/lib/bottlerocket
xvdb     202:16   0   20G  0 disk
`-xvdb1  202:17   0   20G  0 part /var
                                  /opt
                                  /mnt
                                  /local

Additional context

hi @anbotero - yes, bottlerocket creates 2 volumes. you can see more here https://github.com/bottlerocket-os/bottlerocket/issues/1203

hi @anbotero - yes, bottlerocket creates 2 volumes. you can see more here bottlerocket-os/bottlerocket#1203

Excellent. Thanks a lot for the clarification, and apologies for the Issue. 😅

no worries!


include CHANGELOG.md in the sdist

otherwise installation from the source distribution fails, as setup.py
tries to read CHANGELOG.md which wasn't there

What do these changes do?

Are there changes in behavior for the user?
No
Related issue number

Checklist

[ ] I think the code is well written
[ ] Unit tests for the changes exist
[ ] Documentation reflects the changes
[ ] If you provide code modification, please add yourself to CONTRIBUTORS.txt

The format is <Name> <Surname>.
Please keep alphabetical order, the file is sorted by names.

[ ] Add a new news fragment into the CHANGES/ folder

name it <issue_id>.<type> (e.g. 588.bugfix)
if you don't have an issue_id change it to the pr id after creating the PR
ensure type is one of the following:

.feature: Signifying a new feature.
.bugfix: Signifying a bug fix.
.doc: Signifying a documentation improvement.
.removal: Signifying a deprecation or removal of public API.
.misc: A ticket has been closed, but it is not of interest to users.

Make sure to use full sentences with correct case and punctuation, for example:
Fix issue with non-ascii contents in doctest text files.

Thanks for this! Funny if you think about; we published v2.0.0a1 with this MANIFEST... good change regardless

You also published a wheel, so that's what most users will get. But I wanted to build an RPM and that needs sauce ;)


[SPARK-35264][SQL] Support AQE side broadcastJoin threshold

What changes were proposed in this pull request?

This PR aims to add a new AQE optimizer rule DynamicJoinSelection. Like other AQE partition number configs, this rule add a new broadcast threshold config spark.sql.adaptive.autoBroadcastJoinThreshold.
Why are the changes needed?

The main idea here is that make join config isolation between normal planner and aqe planner which shared the same code path.
Actually we don not very trust using the static stat to consider if it can build broadcast hash join. In our experience it's very common that Spark throw broadcast timeout or driver side OOM exception when execute a bit large plan. And due to braodcast join is not reversed which means if we covert join to braodcast hash join at first time, we(AQE) can not optimize it again, so it should make sense to decide if we can do broadcast at aqe side using different sql config.
In order to achieve this we use a specific join hint in advance during AQE framework and then at JoinSelection side it will take and follow the inserted hint.
For now we only support select strategy for equi join, and follow this order

mark join as broadcast hash join if possible
mark join as shuffled hash join if possible

Note that, we don't override join strategy if user specifies a join hint.
Does this PR introduce any user-facing change?

Yes, a new config spark.sql.adaptive.autoBroadcastJoinThreshold added.
How was this patch tested?

Add new test.

Test build #138068 has started for PR 32391 at commit 21591b8.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42587/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42587/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42587/

cc @maropu @cloud-fan @maryannxue do you have any thoughts about this feature ?

Test build #138068 has finished for PR 32391 at commit 21591b8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138068/

Test build #138093 has started for PR 32391 at commit 2923933.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42613/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42613/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42613/

Test build #138098 has started for PR 32391 at commit 7d383cf.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42618/

@cloud-fan thank you for the review, address all comments:

inline the config check
simplify the test

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42618/

Test build #138099 has started for PR 32391 at commit 225bde3.

Test build #138093 has finished for PR 32391 at commit 2923933.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42619/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/42619/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138093/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/42619/

Test build #138098 has finished for PR 32391 at commit 7d383cf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

thanks, merging to master!

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138098/

Test build #138099 has finished for PR 32391 at commit 225bde3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

thanks for merging!

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138099/

Hi @ulysses-you , I have some questions for this PR. In current version, I think stats estimation is always larger or equal than actual value, so it seems like if a join is determined to convert to BHJ, it is also meet the broadcast conditions in AQE.

@Gabriel39 Not sure I see your point. Do you mean a plan which can be broadcast in AQE is always smaller than the config we specified ? If so, What's the issue with that.

@ulysses-you Well, I think you want to make broadcast threshold isolation between AQE and normal because current broadcast can lead to OOM. However, when a join is converted to a BHJ during normal planning process using static stats, it is definitely a BHJ and AQE should not optimize it to other join type since static stats (e.g sizeInBytes) is always larger or equal the actual value. So driver side OOM will occur only if the broadcast threshold is too large.
So Im not sure this PR make sense since OOM commonly due to  unreasonable broadcast threshold.
If I misunderstand your point, feel free to point out my mistake. Thx.

@Gabriel39 I guess you misunderstand the logic of AQE.

AQE should not optimize it to other join type since static stats (e.g sizeInBytes) is always larger or equal the actual value

That's wrong, AQE can never change a BHJ to other join strategy which is decided at normal planner side. It's not about the stats, you can see some key code in LogicalQueryStageStrategy.
And this new config is assuming a join is not a BHJ before AQE, so that AQE can use the new config and runtime stats to make a join (mostly is SMJ) as BHJ.
So, usually the right way of using this new config is 1) forbid the normal auto broadcast or reduce the value 2) tune the new config value.

To add a bit more color: The static size estimation in Spark is usually underestimated, due to things like file compression. We can set the AQE broadcast threshold a bit higher as AQE size estimation is more precise.

@ulysses-you @cloud-fan Thank you for your patience! I think I really misunderstood this PR and stats estimation before.


Bug#172

Summary
Briefly describe the purpose of this PR.
Description
Explain in detail what this PR is all about. This should include the problem you're solving, the approach taken, and any technical details that reviewers need to know.
Images
Include any relevant images or diagrams that can help reviewers visualize the changes, if applicable
Issue(s) Addressed
Enter the issue number of the bug(s) that this PR fixes

Template should be strictly Closes <172>
Closes #172

Prerequisites

[ yes ] Have you followed all the CONTRIBUTING GUIDELINES?

@krishnaacharyaa can you review this pr sir

@krishnaacharyaa can you review this pr sir

Thanks for the PR. @Ameerjafar
Do these also :- 1. Apply the same thing in the signup-page.tsx that is done in signin-page.tsx.
Q1. If we are now storing cookies( accessToken, refreshToken) in browser then what is the use of UserState singleton class in frontend that is storing the accessToken in state variable?

Summary
Briefly describe the purpose of this PR.
Description
Explain in detail what this PR is all about. This should include the problem you're solving, the approach taken, and any technical details that reviewers need to know.
Images
Include any relevant images or diagrams that can help reviewers visualize the changes, if applicable
Issue(s) Addressed
Enter the issue number of the bug(s) that this PR fixes

Template should be strictly Closes <172>
Closes [BUG] Login of the user doesn't stay if I refresh the page ( Non - consistent ) #172

Prerequisites

[ yes ] Have you followed all the CONTRIBUTING GUIDELINES?

@Ameerjafar Try to fill the given details.
Always remember if default PR template is given, try to fill it.
It is given for a purpose to make everyone understand what this PR is all about.

@0xmohitsen Q! As of now can I remove the userState singleton class from the signin and signup component.

@0xmohitsen Q! As of now can I remove the userState singleton class from the signin and signup component.

Go ahead, let's see what you are upto?

@0xmohitsen Without the singelton class of userstate we cannot set the cookie in the access token immediately that is the reason we are using the userState singleton class sir.

@0xmohitsen Without the singelton class of userstate we cannot set the cookie in the access token immediately that is the reason we are using the userState singleton class sir.

Yeah!!

@0xmohitsen Without the singelton class of userstate we cannot set the cookie in the access token immediately that is the reason we are using the userState singleton class sir.

There is a problem here.

When accessToken expires they removed from browser's cookie but still user is able to create post. While user must not be able to create post when tokens are expired and removed from browser's cookie.

@0xmohitsen  can you now review the pr sir.

@0xmohitsen once the accessToken expiry after the refresh only the website logged out that is the way the existing code had written sir.

@Ameerjafar User is not able to create blog post when tokens are expired and redirects to homepage as expected but there is no conditional rendering. We want to display login button when tokens are expired.

@0xmohitsen once the accessToken expiry after the refresh only the website logged out that is the way the existing code had written sir.

@Ameerjafar User is not able to create blog post when tokens are expired and redirects to homepage as expected but there is no conditional rendering. We want to display login button when tokens are expired.

But currently we are displaying create post + logout button which is not correct.

@0xmohitsen ok sir let me work sir.

@Ameerjafar Thank you for the PR, kindly close this PR and let's stragtegize what to be done and then raise new PR with proper commit message and PR description. Slow down and follow the guidelines, which is repeatedly told, https://github.com/krishnaacharyaa/wanderlust/blob/9b11b769bb23150b746296cf9008056633d21921/.github/CONTRIBUTING.md#guidelines-for-contributions.
Closing this PR because of improper commit message and non PR details.


Discussion: how to refactor storage libraries

The structure of storage related libraries are now:

crates

codecs
db
libmdbx-rs
interfaces (Database stuff becomes bigger and bigger, it probably deserves a standalone lib and moving them to the interface was not the greatest idea I though only the abstraction part is going to be here but this does not make a lot of sense now)

abstraction traits.
tables
provider
codecs impl

it can be refactored to:

crates:

storage:

libmdbx-rs
db (This would contains db traits from interfaces, and have a feature flag mdbx)

abstraction traits
tables
providers
codecs impl

codecs

Additionally, I would move the StageDb from reth-stages to providers to have all database-related operations in the same place.

Was this closed in #371?


ComputerMangementDsc: Add Change log link to README

Pull Request (PR) description
This PR adds a link to the CHANGELOG to the README file, to keep consistent with the other DSC Resource modules.
This Pull Request (PR) fixes the following issues
None
Task list

[ ] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md in the resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #223 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev   #223   +/-   ##
===================================
  Coverage    83%    83%
===================================
  Files        10     10
  Lines      1068   1068
===================================
  Hits        891    891
  Misses      177    177

@gaelcolas Can you please merge this PR?


Whether to support time range selection

Where is an example of time range selection？

Why it was closed? It would be a great feature as I am already looking for a datepicker like this.


Abount fullReset flicker

Description
When using fullReset for updating, the screen flickers, which is a problem. Currently, I can only use fullReset for updating because using chart.update("data") only updates the candles, and the x-axis does not update simultaneously.
Suggested solution
Is there any other update interface that can meet the requirements or prevent fullReset from flickering?
Alternative
No response
Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Yeah, this is a known problem. No solution for now (it happens because we need to wait for a response from an overlay to detect the dimensions of the pane. But it takes one tick, so you see the result of the adjustment)

Sure, I understand. If Night Vision fixes this issue in the future, please include a mention of it in the version update notes. Thank you again for your response.


IOError: Unable to create file

Model Saved.
Traceback (most recent call last):
File "boss_train.py", line 180, in
model.save()
File "boss_train.py", line 147, in save
self.model.save(file_path)
File "/usr/local/lib/python2.7/dist-packages/keras/engine/topology.py", line 2423, in save
save_model(self, filepath, overwrite)
File "/usr/local/lib/python2.7/dist-packages/keras/models.py", line 48, in save_model
f = h5py.File(filepath, 'w')
File "/usr/local/lib/python2.7/dist-packages/h5py/_hl/files.py", line 271, in init
fid = make_fid(name, mode, userblock_size, fapl, swmr=swmr)
File "/usr/local/lib/python2.7/dist-packages/h5py/_hl/files.py", line 107, in make_fid
fid = h5f.create(name, h5f.ACC_TRUNC, fapl=fapl, fcpl=fcpl)
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (/tmp/pip-nCYoKW-build/h5py/_objects.c:2840)
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (/tmp/pip-nCYoKW-build/h5py/_objects.c:2798)
File "h5py/h5f.pyx", line 98, in h5py.h5f.create (/tmp/pip-nCYoKW-build/h5py/h5f.c:2284)
IOError: Unable to create file (Unable to open file: name = './store/model.h5', errno = 2, error message = 'no such file or directory', flags = 13, o_flags = 242)

manually create ./store directory by yourself

i have create the file manually but the same error is coming.can anyone solve this?

Anyone able to solve this? I am having the same issue. The folder is already present in the same directory.


Do not make '≡' disappear

In https://earth.nullschool.net/js/bundle.js please do not do this,
            setTimeout(function () {
                d3.select("#menu-ham").transition().style("opacity", "0").remove();
            }, 15 * 1000);

I told my friend to just click the '≡' as I handed the keyboard to him,
but then he said I was crazy. I looked at the screen, and the '≡' was
now gone.
Please provide a consistent interface.

User sends a friend a link
http://earth.nullschool.net/#current/wind/surface/level/orthographic=120.87,24.18,3000
and without getting into details notes to his friend that one can adjust
the time.
With the '≡' disappearing users have even a harder time figuring out where to adjust the time.


Mobile: add google_grpc=disabled to compile_time_options test

This flag is enabled in regular tests, but we should test the case where it's disabled.  Seems like this test suite is the place intended for doing that!
Resolves https://github.com/envoyproxy/envoy/issues/26259

Actually on second thought I think this change will cover yesterday's bug.  I don't exactly know how but the swift interop stuff is getting double-checked in unit tests atm.  I had test failures locally until I added some lines to update interop for my new builder API.

I had test failures locally until I added some lines to update interop for my new builder API.

swift interop is enabled by default (so when you develop locally too) and so is google_grpc. Maybe that explains why you were able to find an issue when doing local dev.

If envoy_mobile_swift_cxx_interop is explicitly disabled for CI, then it'll be hard to test codepaths related to it.
Is envoy_mobile_swift_cxx_interop disabled b/c of flakiness issues?  Should we have a separate CI job that runs w/ envoy_mobile_swift_cxx_interop?

Merging this since it is a net positive, but we should continue the discussion on envoy_mobile_swift_cxx_interop


[Bug]: find highlight matches wrong index with normalization for compound word with a line break after the hyphen.

Attach (recommended) or Link to PDF file
compound_word_with_line_break_after_hyphen.pdf
Web browser and its version
Firefox 133
Operating system and its version
Windows 10
PDF.js version
v4.8.69
Is the bug present in the latest PDF.js version?
Yes
Is a browser extension
No
Steps to reproduce the problem

Open the attached file "compound_word_with_line_break_after_hyphen.pdf"
Search for the letter "o"

What is the expected behavior?
The letter "o" should be highlighted
What went wrong?
Because of the normalization the index is off by 1 and the letter "n" is highlighted

The span for the highlight contains only the letter "n" instead of "o"

Link to a viewer
No response
Additional context
It seems that during normalization in pdf_find_controller.js the position calculated for the case "Compound word with a line break after the hyphen." is wrong.

Is this perhaps a regression from PR #18730, since https://github.com/mozilla/pdf.js/issues/18693#issuecomment-2336789821 mentions that fixing that one could lead to other issues?


Old envoy.lua filter code not deleted

Bug description
We're using an EnvoyFilter written in Lua. We were trying to deploy a new version when we realised some Istio pods were not healthy. We re-installed Istio and re-created the filter. Now, in our ingress gateway in envoy's config_dump we can see two filters named envoy.lua - one with old code version, one with new code version. We cannot get rid of the old one, and as a result, both filters are executed.
Is there anything we can do to delete the stale envoy.lua filter?
Our filter template looks like this (code removed):
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  name: {{ include "istio-gateway.fullname" . }}-filters
  labels:
    app.kubernetes.io/name: {{ include "istio-gateway.name" . }}
    helm.sh/chart: {{ include "istio-gateway.chart" . }}
    app.kubernetes.io/instance: {{ .Release.Name }}
    app.kubernetes.io/managed-by: {{ .Release.Service }}
spec:
  filters:
    - listenerMatch:
        listenerType: GATEWAY
        listenerProtocol: HTTP
      filterType: HTTP
      filterName: envoy.lua
      filterConfig:
        inlineCode: |

Expected behavior
Old filter code replaced with new filter code
Steps to reproduce the bug
N/A
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
istioctl version --remote

client version: 1.4.0
citadel version: 1.2.5
galley version: 1.2.5
ingressgateway version: 1.2.5
ingressgateway-internal version:
pilot version: 1.2.5
policy version: 1.2.5
sidecar-injector version: 1.2.5
telemetry version: 1.2.5
data plane version: 1.2.5 (72 proxies)

kubectl version

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:16:51Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.8-eks-b7174d", GitCommit:"b7174db5ee0e30c94a0b9899c20ac980c0850fc8", GitTreeState:"clean", BuildDate:"2019-10-18T17:56:01Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}

helm version: gcr.io/kubernetes-helm/tiller:v2.13.1
How was Istio installed?
With Helm
Environment where bug was observed (cloud vendor, OS, etc)
EKS

I do have an update - I found a workaround. It's kludgy and I'm not overly happy with it.
Long story short - deleting the filter with kubectl and then reinstating it doensn't do anything - it still has old and new versions of code. However, if I delete my whole helm chart (where I manage a Gateway and an EnvoyFilter only) and re-apply it, I get the desired result.
The downside is that between deletion and recreation I do not have a gateway, so I am not serving traffic. Quite a dealbreaker for production environments.