Pipenv tries to install outdated dependency (nrel-pysam)

Be sure to check the existing issues (both open and closed!), and make sure you are running the latest version of Pipenv.
Check the diagnose documentation for common issues before posting! We may close your issue if it is very similar to one of them. Please be considerate, or be on your way.
Make sure to mention your debugging experience if the documented solution failed.
Issue description
pipenv wants to install nrel-pysam 2.1.1. This verison is outdated (and fails while installing/locking). The most recent version would be 2.2.2.
Debugging information
pip 20.2.3 tries to install 2.1.1, while 21.0.1 correctly taks 2.2.2. This might be related to this issue
Expected result
nrel-pysam 2.2.2 to be installed
Actual result
>>> pipenv install nrel-pysam --verbose

Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning.
Installing nrel-pysam...
Installing package: nrel-pysam
Writing supplied requirement line to temporary file: 'nrel-pysam'
Installing 'nrel-pysam'
⠸ Installing nrel-pysam...$ ['/Users/xxx/xxx/pysam-install-test/.venv/bin/pip', 'install', '--verbose', '--upgrade', '--exists-action=i', '-r', '/var/folders/wr/dxdc5_611jn910_m_7f7mtcm0000gn/T/pipenv-04o6ya5y-requirements/pipenv-4xce3vx8-requirement.txt', '-i', 'https://pypi.org/simple']
Adding nrel-pysam to Pipfile's [packages]...
✔ Installation Succeeded
Pipfile.lock not found, creating...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
⠏ Locking...
                          ROUND 1
Current constraints:
  nrel-pysam (from -r /var/folders/wr/dxdc5_611jn910_m_7f7mtcm0000gn/T/pipenvzyf_zub0requirements/pipenv-w9jaj3p6-constraints.txt (line 2))

Finding the best candidates:
✘ Locking Failed!
  found candidate nrel-pysam==2.1.1 (constraint was <any>)

Finding secondary dependencies:
  nrel-pysam==2.1.1 not in cache, need to check index

Steps to replicate
Nothing special, this happens in a freshly created virtual environment.

$ pipenv --support
Pipenv version: '2020.11.15'
Pipenv location: '/Users/xxx/Library/Python/3.8/lib/python/site-packages/pipenv'
Python location<EMAIL_ADDRESS>Python installations found:

3.9.1: /Library/Frameworks/Python.framework/Versions/3.9/bin/python3
3.9.1: /Library/Frameworks/Python.framework/Versions/3.9/bin/python3.9
3.9.1: /usr/local/bin/python3.9
3.8.8: /Users/xxx/xxx/pysam-install-test/.venv/bin/python3
3.8.8: /Users/xxx/xxx/pysam-install-test/.venv/bin/python3
3.8.8<EMAIL_ADDRESS>3.8.8<EMAIL_ADDRESS>3.8.5: /Library/Frameworks/Python.framework/Versions/3.8/bin/python3
3.8.5: /Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8
3.8.2: /usr/bin/python3
2.7.16: /usr/bin/python2
2.7.16: /usr/bin/python2.7

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.8.8',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '20.3.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST '
                     '2021; root:xnu-7195.81.3~1/RELEASE_X86_64',
 'python_full_version': '3.8.8',
 'python_version': '3.8',
 'sys_platform': 'darwin'}

System environment variables:

TERM_SESSION_ID
SSH_AUTH_SOCK
LC_TERMINAL_VERSION
COLORFGBG
ITERM_PROFILE
SQLITE_EXEMPT_PATH_FROM_VNODE_GUARDS
XPC_FLAGS
LANG
PWD
SHELL
__CFBundleIdentifier
SECURITYSESSIONID
TERM_PROGRAM_VERSION
TERM_PROGRAM
PATH
LC_TERMINAL
COLORTERM
COMMAND_MODE
TERM
HOME
TMPDIR
USER
XPC_SERVICE_NAME
LOGNAME
LaunchInstanceID
__CF_USER_TEXT_ENCODING
ITERM_SESSION_ID
SHLVL
OLDPWD
ZSH
UPDATE_ZSH_DAYS
PAGER
LESS
LSCOLORS
P9K_SSH
P9K_TTY
PS1
VIRTUAL_ENV
_
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /Users/xxx/xxx/pysam-install-test/.venv/bin:/usr/local/opt/python@3.8/bin:/Users/xxx/.bin:/Users/xxx/.krew/bin:/Library/Frameworks/Python.framework/Versions/3.9/bin:/Library/Frameworks/Python.framework/Versions/3.8/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin
SHELL: /bin/zsh
LANG: de_DE.UTF-8
PWD: /Users/xxx/xxx/pysam-install-test
VIRTUAL_ENV: /Users/xxx/xxx/pysam-install-test/.venv

Contents of Pipfile ('/Users/xxx/xxx/pysam-install-test/Pipfile'):
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
nrel-pysam = "*"

[dev-packages]

[requires]
python_version = "3.8"

@larsrinn I could not reproduce this on the latest version of pipenv==2021.11.23
mdavis@matt-VirtualBox:~/shared-projects/pipenv-4679$ pipenv install nrel-pysam --verbose

Using python: None

Path to python: /usr/bin/python3

Creating a virtualenv for this project...

Pipfile: /home/mdavis/shared-projects/pipenv-4679/Pipfile

Using /usr/bin/python3 (3.9.7) to create virtualenv...

⠧ Creating virtual environment...created virtual environment CPython3.9.7.final.0-64 in 339ms

  creator CPython3Posix(dest=/home/mdavis/.virtualenvs/pipenv-4679-bizcYG5S, clear=False, no_vcs_ignore=False, global=False)

  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/mdavis/.local/share/virtualenv)

    added seed packages: pip==21.3.1, setuptools==59.2.0, wheel==0.37.0

  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

✔ Successfully created virtual environment!

Virtualenv location: /home/mdavis/.virtualenvs/pipenv-4679-bizcYG5S

Creating a Pipfile for this project...

Installing nrel-pysam...

Installing package: nrel-pysam

Writing supplied requirement line to temporary file: 'nrel-pysam'

Installing 'nrel-pysam'

⠙ Installing nrel-pysam...$ /home/mdavis/.virtualenvs/pipenv-4679-bizcYG5S/bin/python -m pip install --verbose --upgrade --exists-action=i -r /tmp/pipenv-rtjqilp8-requirements/pipenv-7i7ppvvp-requirement.txt -i https://pypi.org/simple

Using source directory: '/home/mdavis/.virtualenvs/pipenv-4679-bizcYG5S/src'

Adding nrel-pysam to Pipfile's [packages]...

✔ Installation Succeeded

Pipfile.lock not found, creating...

Locking [dev-packages] dependencies...

Locking [packages] dependencies...

Building requirements...

Resolving dependencies...

Reporter.starting()

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.starting()

Reporter.adding_requirement(SpecifierRequirement('nrel-pysam'), None)

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.adding_requirement(SpecifierRequirement('nrel-pysam'), None)

Reporter.starting_round(0)

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.starting_round(0)

Reporter.adding_requirement(SpecifierRequirement('NREL-PySAM-stubs'), LinkCandidate('https://files.pythonhosted.org/packages/0c/45/5f98e2d21d1c47b8f9868e8c056a2c9260ddde64b6419a77ebe339048b3b/NREL_PySAM-2.2.4-cp39-cp39-manylinux1_x86_64.whl#sha256=9b30775d20c679f2f6c7f6b51a0d07ebdb681133e021039d583c3450ffcdca6a (from https://pypi.org/simple/nrel-pysam/)'))

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.adding_requirement(SpecifierRequirement('NREL-PySAM-stubs'), LinkCandidate('https://files.pythonhosted.org/packages/0c/45/5f98e2d21d1c47b8f9868e8c056a2c9260ddde64b6419a77ebe339048b3b/NREL_PySAM-2.2.4-cp39-cp39-manylinux1_x86_64.whl#sha256=9b30775d20c679f2f6c7f6b51a0d07ebdb681133e021039d583c3450ffcdca6a (from https://pypi.org/simple/nrel-pysam/)'))

Reporter.pinning(LinkCandidate('https://files.pythonhosted.org/packages/0c/45/5f98e2d21d1c47b8f9868e8c056a2c9260ddde64b6419a77ebe339048b3b/NREL_PySAM-2.2.4-cp39-cp39-manylinux1_x86_64.whl#sha256=9b30775d20c679f2f6c7f6b51a0d07ebdb681133e021039d583c3450ffcdca6a (from https://pypi.org/simple/nrel-pysam/)'))

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.pinning(LinkCandidate('https://files.pythonhosted.org/packages/0c/45/5f98e2d21d1c47b8f9868e8c056a2c9260ddde64b6419a77ebe339048b3b/NREL_PySAM-2.2.4-cp39-cp39-manylinux1_x86_64.whl#sha256=9b30775d20c679f2f6c7f6b51a0d07ebdb681133e021039d583c3450ffcdca6a (from https://pypi.org/simple/nrel-pysam/)'))

Reporter.ending_round(0, state)

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.ending_round(0, state)

Reporter.starting_round(1)

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.starting_round(1)

Reporter.pinning(LinkCandidate('https://files.pythonhosted.org/packages/36/81/b08a1fee0bd0c9adbd6c092dbe6677c5c7e6c5aed1db5c408d32160c82f3/NREL_PySAM_stubs-2.2.4-py3-none-any.whl#sha256=66223ed79dbf24298ce171a2faeefb1cb7ddf545a08e2628b45ffb1189b125fd (from https://pypi.org/simple/nrel-pysam-stubs/)'))

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.pinning(LinkCandidate('https://files.pythonhosted.org/packages/36/81/b08a1fee0bd0c9adbd6c092dbe6677c5c7e6c5aed1db5c408d32160c82f3/NREL_PySAM_stubs-2.2.4-py3-none-any.whl#sha256=66223ed79dbf24298ce171a2faeefb1cb7ddf545a08e2628b45ffb1189b125fd (from https://pypi.org/simple/nrel-pysam-stubs/)'))

Reporter.ending_round(1, state)

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.ending_round(1, state)

Reporter.starting_round(2)

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.starting_round(2)

Reporter.ending(State(mapping=OrderedDict([('nrel-pysam', LinkCandidate('https://files.pythonhosted.org/packages/0c/45/5f98e2d21d1c47b8f9868e8c056a2c9260ddde64b6419a77ebe339048b3b/NREL_PySAM-2.2.4-cp39-cp39-manylinux1_x86_64.whl#sha256=9b30775d20c679f2f6c7f6b51a0d07ebdb681133e021039d583c3450ffcdca6a (from https://pypi.org/simple/nrel-pysam/)')), ('nrel-pysam-stubs', LinkCandidate('https://files.pythonhosted.org/packages/36/81/b08a1fee0bd0c9adbd6c092dbe6677c5c7e6c5aed1db5c408d32160c82f3/NREL_PySAM_stubs-2.2.4-py3-none-any.whl#sha256=66223ed79dbf24298ce171a2faeefb1cb7ddf545a08e2628b45ffb1189b125fd (from https://pypi.org/simple/nrel-pysam-stubs/)'))]), criteria={'nrel-pysam': Criterion((SpecifierRequirement('nrel-pysam'), via=None)), 'nrel-pysam-stubs': Criterion((SpecifierRequirement('NREL-PySAM-stubs'), via=LinkCandidate('https://files.pythonhosted.org/packages/0c/45/5f98e2d21d1c47b8f9868e8c056a2c9260ddde64b6419a77ebe339048b3b/NREL_PySAM-2.2.4-cp39-cp39-manylinux1_x86_64.whl#sha256=9b30775d20c679f2f6c7f6b51a0d07ebdb681133e021039d583c3450ffcdca6a (from https://pypi.org/simple/nrel-pysam/)')))}))

INFO:pipenv.patched.notpip._internal.resolution.resolvelib.reporter:Reporter.ending(State(mapping=OrderedDict([('nrel-pysam', LinkCandidate('https://files.pythonhosted.org/packages/0c/45/5f98e2d21d1c47b8f9868e8c056a2c9260ddde64b6419a77ebe339048b3b/NREL_PySAM-2.2.4-cp39-cp39-manylinux1_x86_64.whl#sha256=9b30775d20c679f2f6c7f6b51a0d07ebdb681133e021039d583c3450ffcdca6a (from https://pypi.org/simple/nrel-pysam/)')), ('nrel-pysam-stubs', LinkCandidate('https://files.pythonhosted.org/packages/36/81/b08a1fee0bd0c9adbd6c092dbe6677c5c7e6c5aed1db5c408d32160c82f3/NREL_PySAM_stubs-2.2.4-py3-none-any.whl#sha256=66223ed79dbf24298ce171a2faeefb1cb7ddf545a08e2628b45ffb1189b125fd (from https://pypi.org/simple/nrel-pysam-stubs/)'))]), criteria={'nrel-pysam': Criterion((SpecifierRequirement('nrel-pysam'), via=None)), 'nrel-pysam-stubs': Criterion((SpecifierRequirement('NREL-PySAM-stubs'), via=LinkCandidate('https://files.pythonhosted.org/packages/0c/45/5f98e2d21d1c47b8f9868e8c056a2c9260ddde64b6419a77ebe339048b3b/NREL_PySAM-2.2.4-cp39-cp39-manylinux1_x86_64.whl#sha256=9b30775d20c679f2f6c7f6b51a0d07ebdb681133e021039d583c3450ffcdca6a (from https://pypi.org/simple/nrel-pysam/)')))}))

⠦ Locking...

✔ Success!

Updated Pipfile.lock (a77d98)!

Installing dependencies from Pipfile.lock (a77d98)...

  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 0/0 — 00:00:00
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
mdavis@matt-VirtualBox:~/shared-projects/pipenv-4679$ pipenv run pip freeze
NREL-PySAM==2.2.4
NREL-PySAM-stubs==2.2.4
mdavis@matt-VirtualBox:~/shared-projects/pipenv-4679$ pipenv --version
pipenv, version 2021.11.23


Configurable log format

Propose changes
Make structured logging configurable in JSON format.

@stefanprodan the requested changes have been applied accordingly.


Dashboard_CYPWaitsAccess

Thanks for sharing your SQL code!
Do you have the script that populates NHSE_Sandbox_MentalHealth.dbo.Dashboard_CYPWaitsAccess. I couldn't see it unless I've missed something? I'm trying to recreate the access metric so that I can break it down further (locality, age, ethnicity, etc).
Kind regards,
Alex

Hi Alex,
I'll get that code added today. The access metric is produced by NHS D and and all our code does is pick up the published values. NHS D made the logic (and code!) available via their meta data file, here: https://digital.nhs.uk/data-and-information/data-collections-and-data-sets/data-sets/mental-health-services-data-set/statistics-and-reports
This looks at each month individually. If you need a time series I can share some logic that does this in one go.

Hi Carl,
Thanks for getting back to me, that would be a great help.

closed as complete


Implement Trace Widening

At the moment, the underlying data flow analysis never performs widening.  Until now, that was not a problem.  Unfortunately, as we are generating more information ... it is becoming a problem.

Rough plan:

[ ] Add generic mechanism for state subsumption.  This requires two things: (1) ability to determine when one state subsumes another; (2) extended dedup when joining states which accounts for subsumption.
[ ] When widening is triggered, subsume states based on least difference.  For given k, merge all states with k or fewer different cells.  Perhaps initially just work with k=1
[ ] Trigger widening based on number of states contained (e.g. when hit n states then widening is triggered).

I think going forward, we want something a bit more general.  Specifically, we can apply a havoc analysis to determine suitable widening points and locations.

To be honest, it probably makes sense to go straight to havoc analysis no?


Add circle.yml file for configuring CircleCI

This patch adds a circle.yml file which configures CircleCI to run Scala/Java style checkers and the sql subproject's tests.

@marmbrus, should we also run Hive tests?

No, I don't think we'll be making any hive changes.


Super Better Grass

CurseForge link
https://curseforge.com/minecraft/mc-mods/super-better-grass
CurseForge Mod Distribution
Allowed
Modrinth link
https://modrinth.com/mod/super-better-grass
Source/other link
https://github.com/dima-dencep/super-better-grass
Mod file size
774 KB
License
(any other license)
What it does
OptiFine's Better Grass - #6 ported back to Fabric
Why should it be in the modpack
Because most people prefer to have the Better Grass from OptiFine that is "fancy", not "fast" (like in the currently bundled resource pack).
Why shouldn't it be in the modpack

Not yet available on MR
Untested
LambdAurora may not like this and as such, may try to take the mod down from the platforms (though the fork appears to follow the license properly)

Additional details
No response

Seems to be working just fine:

The mod has been removed from Modrinth for good, so any attempt to bring it back there by me would probably be frowned upon. Similar tensions have come up in the CurseForge listing comments, so... yeah, it's better to avoid adding it to FO.


Bug: Error in GithubIssuesPipeline

An error occurred while trying to map open GitHub issues to ontology using the GithubIssuesPipeline workflow. The error message was: 'AttributeError("'GithubIntegrationConfiguration' object has no attribute 'get_issues'")'. This needs to be investigated and resolved.

Fixed


labelComponent should be optional

Describe the bug
This bug occur when data object don't have labelComponent

Hi @ThucTrieu 👋
Thanks for pointing out this issue.
I will fix this and other typescript errors this weekend.
Till then, as a workaround you can pass empty callback function as the labelComponent inside the data objects.

This has been fixed in the latest version of the library.


[BUG] Volume node-specifier have unspecified behaviour with shared/ro

What did you do
k3d cluster create temp \
    --agents 1 \
	--k3s-arg --disable=traefik@server:0 \
	-v /etc/machine-id:/etc/machine-id:ro \
	-v /opt/temp:/opt/temp/gateway:shared@agent:0 \
	--port 80:80@loadbalancer \
    --port 443:443@loadbalancer

What did you expect to happen
It is not clear which of these are correct since they both succeed without error:
-v /opt/temp:/opt/temp/gateway:shared@agent:0

-v /opt/temp:/opt/temp/gateway@agent:0:shared

But neither appear to create shared volumes.
There needs to be:

documentation on how to use volume node-specifier with shared/RO flags
validation such that one of the two approaches above fail

Which OS & Architecture
Ubuntu 21.10

Which version of k3d
k3d version v5.0.1
k3s version v1.21.5-k3s2 (default)

Which version of docker
 Version:           20.10.9

Hi @nadenf , thanks for opening this issue!
:shared is an option offered by the runtime (i.e. docker), not k3d, so the following syntax is correct: -v /opt/temp:/opt/temp/gateway:shared@agent:0
The third part (modifiers) of the k3d nodefilter is unspecified for the volume flag right now, but I can certainly add some checks to it :+1:

Fixed by #871


Modularize flag parsing

Codecov Report

Merging #45 into master will increase coverage by 6.28%.
The diff coverage is 64.29%.

@@            Coverage Diff             @@
##           master      #45      +/-   ##
==========================================
+ Coverage   71.51%   77.78%   +6.28%
==========================================
  Files           8        8
  Lines         365      369       +4
==========================================
+ Hits          261      287      +26
+ Misses         86       63      -23
- Partials       18       19       +1

Impacted Files
Coverage Δ

main.go
79.21% <64.29%> (+23.54%)
:arrow_up:

Continue to review full report at Codecov.

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


Update README.md

Add one more variation

Wonderful, would you mind adding using this new system?
https://github.com/CodingTrain/Rainbow-Code/wiki/Community-Contributions-Guide
(Sorry things are in flux!)

Thanks for letting me know the new system.
I created a pull request.

@BruceChen034020 I can't seem find your new pull request, can you check again? As for this pr, the README's will be deprecated not long from now as mentioned in issue #400, so I'll close it.


MGDOBR-739 Check dev cluster ci failure sheriff notifiation

[MGDOBR-739]
PR owner checklist
Please make sure that your PR meets the following requirements:

[ ] Your code is properly formatted according to this configuration.
Run mvn clean verify -DskipTests so that imports are correctly set.
[ ] Your commit messages are clear and reference the JIRA issue e.g: "[MGDOBR-1] - $clear_explanation_of_what_you_did"
[ ] The layers in the kustomize folder have been updated accordingly.
[ ] All new functionality is tested
[ ] Pull Request title is properly formatted: MGDOBR-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

PR reviewer(s) checklist

[ ] Check if code and Github action workflows have been modified and if the modification is safe
[ ] If the modification is safe, add the safe to test label

How to trigger pipelines and use the bots:

Run the end to end pipeline
Annotate the pull request with the label: safe to test. If you want to run the pipeline again, remove and add it again.

Rebase the pull request
Comment with: /rebase.

Deploy BOT
Comment with `/deploy <dev,stable> when the PR has been merged to deploy to a target environment.

I hope this was closed as it's deemed unnecessary. A self-policing list of "sheriff on call" should be enough. I know all too well people were more than happy to chase me up when they believed I was the current sheriff.
Having raised type or script may seem nice but will be all too inflexible to included holidays, sickness etc. Communicate the rota but please don't automate the emails.


Added httpConnectionManagerConfigHelper to refactor config_test

Signed-off-by: Manish Kumar<EMAIL_ADDRESS>Commit Message: Refactored config_test.cc
Additional Description:
created createHttpConnectionManagerConfig() to improve readability.
Risk Level:
Testing: unit test
Docs Changes:
Release Notes:
includes partial fix to #11109

@mk46, thanks! Could you update the PR description? Thanks!

Hi @dio, I found
HttpConnectionManagerConfig config(parseHttpConnectionManagerFromV2Yaml(yaml_string), context_,                                      date_provider_, route_config_provider_manager_,                                      scoped_routes_config_provider_manager_, http_tracer_manager_);
is 48 times. Could you suggest how to refact it? Thanks!

@mk46 sorry, the Commit Message in the description, please? As per: https://github.com/envoyproxy/envoy/blob/master/PULL_REQUESTS.md#commit-message

@dio PTAL

Sorry, @mk46 could you merge master, please? Thanks!

/azp run envoy-presubmit


html_editor_enhanced: ^2.1.1[BUG]

Describe the bug
bug on the latest version null safety
To Reproduce
Steps to reproduce the behavior:

After installing the package just hot restart
FlutterApplication/flutter/.pub-cache/hosted/pub.dartlang.org/html_editor_enhanced-2.1.1/lib/src/widgets/toolbar_widget.dart:2286:74: Warning: Operand of null-aware operation '!' has type 'String' which excludes null.   result!.files.single.name!;

Expected behavior
not error
Device:
both real and emulator

Hi, this is a known bug and was fixed by 8923d247aced2bf9ca3c0fde39182b95fad6f781. I hope to push a new version to pub.dev soon, then this warning will go away. It does not cause any errors, you can use the package as normal.

I love the editor , will be waiting for the update soon , just that the
error annoys me though no effect


GPUParticles2D not visible when exporting a game

Godot version
4.0.1stable, master (2a275b9)
System information
Linux archlinux 6.1.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 24 Jan 2023 21:07:04 +0000 x86_64 GNU/Linux
Issue description
Particle systems are not showing when exporting a game on Linux. This might be related to #75270. However, some particles are showing, and some are not. But: It does not depend on the platform. It happens for all linuxbsd, windows and the web target. I'm not seeing errors, the particle systems are just not showing.
What I have tried

Checked if texture import settings are different for the different particle systems. They are not.
Created a test scene with all permutations of texture import settings in order to check which one might be the issue (fix alpha border, premult alpha, ... etc.). No success! Either all or none of them show up, depending or how I build the game (see below).
...
Checked if the images used on the textures are different. Of course the files contain different images, but their format is the same:

fd ".*particle.*png$" | xargs file
scenes/map_event_node/map_event_node_particle.png:          PNG image data, 512 x 512, 8-bit/color RGBA, non-interlaced
scenes/player/player_thruster_particle.png:                 PNG image data, 512 x 512, 8-bit/color RGBA, non-interlaced
tests/particle_systems/test_particle_both.png:              PNG image data, 512 x 512, 8-bit/color RGBA, non-interlaced
tests/particle_systems/test_particle_fix_alpha_border.png:  PNG image data, 512 x 512, 8-bit/color RGBA, non-interlaced
tests/particle_systems/test_particle_nothing.png:           PNG image data, 512 x 512, 8-bit/color RGBA, non-interlaced
tests/particle_systems/test_particle_premultiply_alpha.png: PNG image data, 512 x 512, 8-bit/color RGBA, non-interlaced

Steps to reproduce
Building a game with missing particle systems
Export the game using the Godot versions specified. Some particle systems show up and others aren't. I haven't been able to track down the root cause, since I simply don't know about Godot internals. However, I can confirm that it happens when I:

Build the game without removing the .godot directory beforehand
When I build the game using the commandline and the --headless option

However, I have been able to consistently create builds where all particle systems are showing up.
Building a game with all particle systems
This is what I have to do:

Remove the .godot folder
Launch the godot editor at least twice
Export using the godot editor or export using the cli but without --headless

1. requires 2. -- Otherwise the game is not exported at all.
And 3. is needed to consistently produce builds that contain all particle systems.
Minimal reproduction project
I have created a minimal reproduction project. However, the problem does not occur there. I have updated my game to use the very same settings as the minimal project (every rendering setting was identical), however the problem persisted.
Please let me know if you need any other information.
Thanks!

Related to https://github.com/godotengine/godot/issues/66842.

I also have this problem.
When I export my game from Windows, all GPUParticles2D show up. But when I export the game from headless Linux, some particle systems are missing.
Godot version: 4.1dev1

After acquing a macOS device, I have been able to verify this same behaviour based on the explanations I have given. If using --headless, at least for my specific project, I'm seeing no particle systems in the release build.


On Angular 1.x? Please use a different npm package!

Today, @alexw10 and I started working on the Angular 4+ version of this directive. In preparation for this project to eventually become Angular 4+ only, I cloned this repo and published a new npm package.
Starting today, you can install the Angular 1.x package with npm install --save angularjs-bootstrap-datetimepicker

@dalelotts The NPM package angular-bootstrap-datetimepicker contains Angular 1x code, not usable in NGX

I have not released the Angular 5.x version of this package as the latest yet - you can get it from npm by running
npm install --save angular-bootstrap-datetimepicker@next bootstrap moment open-iconic
I'm just wrapping up some of the final API's, how long until you go to production?

@dalelotts Thanks! No hurry, we just wanted to test it out and see if your component fits our needs.

@fbernhard let me know your thoughts! You can see the progress of the 2.0 release project here


The specified device interface or feature level is not supported on this system.

Hello, thanks for your effort. When I'm trying to run sample it shows following error after I try to hit record button
Error message: "The specified device interface or feature level is not supported on this system."

hey anpin,
unfortunately this is a known issue with the underlying library used. so for now the only way this works is by explicitly starting vvvv with the integrated graphics card.

@joreg thanks for quick response. I'm wondering if there is another way to workaround it since my project is already CPU heavy and a bit choppy in times. I'm thinking running it through Gstreamer could work (or getting a proper PC :)) . Also I'm wondering if the bug might cause another issue I had here, which is Skia off-screen accelerated renderer  is either shows black screen, or draws something completely different from what I can see in the non accelerated renderer and then crashes.

Actually I just looked back in the project with a fresh pair of eyes and it is not particularly heavy load, but still quite a bit choppy

re the original issue we'll have to wait for an update of the underlying library.
re the other issues you mentioned i suggest you open a forum thread on discourse.vvvv.org as they don't sound related to this library.


training with alexnet with my own data

Recently I want to use alex_net provided under example/image-classification with my own car-logo dataset. I prepare everything needed for training but finally got train and validation both around 20 per cent. I use the make_list.py and im2rec.py under tools to convert my data to the format required by mxnet and adjust some parameters for my own data. Because I can't find a script to compute the image mean value, I use the original mean value of alex net(r:123.68,g:116.779,b:103.939) for my net temporally and the image size is (3,63,63). I also change some value such as the first conv kernel into (5,5) with pad(1,1), num_class 42, wd 0.0005, lr 0.01,totally 80 epoch, lr-factor-epoch 20, num-examples 17551 and other relatively reasonable parameters. Can anybody fix this problem for me?

how many epoch you trained the model?
can you train inception model first?

@qiaohaijun 80 epoch

@UniqueAndys the alexnet need different initialization condition, try inception
are you familiar with caffe model?

@qiaohaijun Yeah, I have been using Caffe, you mean I using the caffe_converter under tools?I am goning to try it! But how can I initialization different part of the net in mxnet?Because I can't always use the caffe model.


Add syshooks and dobby specs to LEGACY_COMPONENTS

Allows removal of ctemplate dependency for builds where dobby
specs are not needed.
With LEGACY_PLUGIN=OFF, Dobby syshooks, legacy plugins and dobby
specs no longer function.

PR #25 brings in more legacy plugins and the gpu syshook is not yet converted to an RDK plugin, which would make merging this PR a bit too early.
Leaving as draft until the gpu syshook has been brought in as an rdk plugin so we can properly strip these legacy components from builds without LEGACY_PLUGIN=ON.
We'll also need to strip down the findRdkPlugins/mRdkPluginsInDevelopment bits of code in DobbyConfig afterwards.


Automatic unzipping for downloaded zip-archives

Description of the new feature / enhancement
Unzips any kind of archive that is downloaded to the Downloads folder. It also shows a notification with the current progress report during the process of unzipping. Should show a different notification after unzipping has finished and give you the option to open the folder in Windows Explorer and Visual Studio Code if it is installed (could also be extended to support any kind of software)
Features:

Have a system tray icon with different options

Enable: Provides the option to quickly enable/disable the tool
Notification: Enables notifications during unzipping
Auto delete zip: Automatically deletes the zip after unzipping has been completed

Example of an implementation I currently have:

Scenario when this would be used?
I often download zip files from the internet and want to directly use them without having to go through the manual labor to open File Explorer, go to downloads, select the file, and unzip the file.
Since any kind of data is usually zipped to save on download size this happens very frequently.
Use cases:

browsing GitHub and seeing cool repos where I want to inspect pieces of code quickly. I usually press download as zip since that is quicker than cloning especially when I don't want to commit anything.
sharing files between colleagues via gdrive/dropbox, etc is commonly downloaded as zip but then used as bare data on the computer itself.

Supporting information
No response

I would love this as a part of powertoys

But in Windows these days you can directly double click open the zip files like a folder.


backend/http: allow to force treating all requests as trusted for tracing purposes

Trusting client-provided parent trace IDs can be a security risk, as it can open the door to DoS attacks by allowing a client to send a large amount of requests with the sample flag set to true, causing the backend to generate a large amount of tracing data. This can affect the performance of the tracing backend, and sometimes also billing.
However, this could be useful for testing, so this PR introduces the QUICKPIZZA_TRACING_INSECURE env var which, when set to a truthy value, will always trust trace parent IDs from external requests.

I don't fully understand this. If the client doesn't send the traceID, we still create a new trace per request, don't we? :thinking:

@dgzlopes The logic for traces and their relationship is a bit convoluted, I'll try to summarize the current behavior here:

If incoming requests do not have any trace-related header, we generate traces either way. The root span for the trace will be an HTTP Server span, for the server who received the request.
If incoming requests do have a traceparent header, then we check the following:
a. If a trusted, secret header is also found, we assume this requests comes from one of our other (trusted) services. In this case, we take the traceparent header and we make the HTTP Server span a child of it. The traceparent header is also trusted for more things, e.g. to flag whether a request should be sampled
b. If there is no trusted header, the code will not make the HTTP Server span a child of the incoming trace, as it is not considered trusted. Instead, the code will make a weaker relationship (a link). The should-sample flag of the traceparent header is ignored

This is the default behavior encouraged by opentelemetry, as blindly trusting traceparent headers can have security implications: A client could force your code to sample every request it sends, DoSing your telemetry backend.
This PR introduces an env var for blindly trusting all requests: The traceparent header will be honored from external, untrusted requests, and generated spans will use the incoming, untrusted trace as a parent. This is useful for debugging purposes.
LMK if this helped made the thing more clear :)

@roobre I would eliminate WithPublicEndpoint() altogether or at least not make it the default (e.g., put it behind a feature flag). This is a demo application; to me, it only makes the codebase more complex (and harder to demo with k6 x Tempo).

A client could force your code to sample every request it sends, DoSing your telemetry backend.

The sampling flag is one thing, but you can also configure sampling at the following levels:

Application level (SDK)
Agent
Tracing backend

Having link association configured does not help avoid the denial of wallet attack.

The sampling flag is one thing, but you can also configure sampling at the following levels: [...]

Correct me if I'm wrong, but isn't the typical tracing setup to honor the tracing flag over the SDK configuration? Otherwise you would get incomplete traces, right?

Having link association configured does not help avoid the denial of wallet attack.

My current understanding is that it does help, as it prevents clients from overriding your sampling choices. I haven't read the full spec, so I might be wrong here.

This is a demo application; to me, it only makes the codebase more complex

This is a fair point, but I do not fully agree. I think that as a demo application, it should do things the way they are supposed to be done, or be very obvious in doing them wrong (so everybody can say "ah, that's because it's a demo"). Trusting all traces by default is, in my view, extremely non-obvious for people without prior experience manually instrumenting things. I'm worried about people looking at the code for examples and finding concealed bad practices that they could then get carried over to real projects.
As a final point, I think real applications or deployments could be configured with the equivalent of WithPublicEndpoint(), so I think it would be nice for the demo application to mimic whenever possible real application behavior.

and harder to demo with k6 x Tempo

This is important for me, I would not like to make it hard to use for demos. I'm hopeful that we can figure out a way to make the application easily demoable that without making the code deceptively dangerous to learn from.
Some alternatives to getting rid of this behavior are:

Keep this PR, but set QUICKPIZZA_TRACING_INSECURE=1 in the default deployment YAML. This way, the code still tells the full story, but demos work out of the box.
Work a bit more on the isPublic logic, for example by defining a header like X-Tracing-Trusted-Request that k6 (client) can send and would cause the application to consider the request trusted. I suspect this would be more similar to how things are done in the real world: Letting your gateway know somehow that a client is trusted to create root spans.

@Blinkuu LMK what you think about this. I hope we can find a solution that makes the application easily demoable without making the code deceive readers into bad practices.

@dgzlopes Any other thoughts on the PR? LMK if you have any remaining questions 😃

Awesome! I will raise a follow-up PR setting this var to 1 by default, so demo deployments work out of the box for k6 x tempo.


Does this module rely on d3-geo?

I do not see d3-geo in the dependencies but it seems to require d3-geo.
I found this issue when I use broswerify trying to create the map on the frontend.
This is the error message:

Error: Can't walk dependency graph: Cannot find module 'd3-geo' from '/node_modules/geo-albers-usa-territories/dist/geo-albers-usa-territories.js'
required by /node_modules/geo-albers-usa-territories/dist/geo-albers-usa-territories.js

Good catch! Indeed, it should be a dependency, or maybe a peerDependency.

@Booonfire Published as v0.1.0. Please let us know if this helps with your Browserify setup. Thanks!

@Booonfire Published as v0.1.0. Please let us know if this helps with your Browserify setup. Thanks!

Thanks for your help. I noticed that d3-geo was added both in devDependencies and peerDependency. When I install, npm warns that I need to install peer dependencies myself. So I guess npm will treat d3-geo as a peerDependency by default right?

That's right. Your code needs to independently have d3-geo as a dependency. This is to avoid pulling in multiple different copies of D3-geo with different versions.
I think this is the recommended approach for libraries set up like this. I know it's a common practice with React for example, to mark React as both a peer dependency and a dev dependency, for libraries that expose reusable components.

Alternatively it could be added as a dependency. I'm not sure if that might be best ... Open to advice!

Alternatively it could be added as a dependency. I'm not sure if that might be best ... Open to advice!

That's acceptable. I would recommend mentioning it on the README.md.

Added the following to README:

Note that this package marks d3-geo as a peerDependency, so you'll need to directly depend on d3-geo as well as this package. This is to avoid the possibility of bundling multiple copies of d3-geo.


cuSPARSE related test failures

Description
I'm seeing seven test failures - all from tests/sparse_test.py. There are three different error messages that all relate to cuSPARSE:

On entry to cusparseSpMM_bufferSize(): matrix B and C must be in column-major order

cuSparseTest.test_coo_matmat1
cuSparseTest.test_coo_matmat3
cuSparseTest.test_coo_matmat5
cuSparseTest.test_coo_sorted_indices_gpu_lowerings

On entry to cusparseSpMM_bufferSize(): opA != CUSPARSE_OPERATION_NON_TRANSPOSE is not supported with CUSPARSE_SPMM_COO_ALG2

cuSparseTest.test_coo_matmat6
cuSparseTest.test_coo_matmat7

On entry to cusparseSpMM_bufferSize(): CUSPARSE_SPMM_COO_ALG2 does not support 64-bit indices

cuSparseTest.test_coo_matmat_layout

For the first one, using the cuSparseTest.test_coo_matmat_layout test as an example. Though when running it outside of the testsuite I get the first error from it:
import jax.numpy as jnp
from jax import jit
from jax.experimental.sparse import coo as sparse_coo

d = jnp.array([1.0, 2.0, 3.0, 4.0])
i = jnp.array([0, 0, 1, 2])
j = jnp.array([0, 2, 0, 0])
shape = (3, 3)

x = jnp.arange(9).reshape(3, 3).astype(d.dtype)

def f(x):
  return sparse_coo._coo_matmat(d, i, j, x.T, spinfo=sparse_coo.COOInfo(shape=shape, rows_sorted=True))

result_jit = jit(f)(x)

Gets me the traceback:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'jit' is not defined
>>> from jax import jit
>>> result_jit = jit(f)(x)
 ** On entry to cusparseSpMM_bufferSize(): matrix B and C must be in column-major order

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "<stdin>", line 2, in f
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/experimental/sparse/coo.py", line 542, in _coo_matmat
    return coo_matmat_p.bind(data, row, col, B, spinfo=spinfo, transpose=transpose)
jax._src.source_info_util.JaxStackTraceBeforeTransformation: RuntimeError: jaxlib/gpu/sparse.cc:538: operation gpusparseSpMM_bufferSize( handle.get(), op_A, GPUSPARSE_OPERATION_NON_TRANSPOSE, &alpha, mat_a,
 mat_b, &beta, mat_c, C.type, GPUSPARSE_SPMM_COO_ALG, &buffer_size) failed: invalid value

The preceding stack trace is the source of the JAX operation that, once transformed by JAX, triggered the following exception.
--------------------

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

Traceback (most recent call last):                                                                                File "<stdin>", line 1, in <module>
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/traceback_util.py", line 163, in reraise_with_filter
ed_traceback
    return fun(*args, **kwargs)
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/pjit.py", line 237, in cache_miss
    outs, out_flat, out_tree, args_flat = _python_pjit_helper(
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/pjit.py", line 185, in _python_pjit_helper
    out_flat = pjit_p.bind(*args_flat, **params)
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/core.py", line 2559, in bind
    return self.bind_with_trace(top_trace, args, params)
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/core.py", line 346, in bind_with_trace
    out = trace.process_primitive(self, map(trace.full_raise, args), params)
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/core.py", line 789, in process_primitive
    return primitive.impl(*tracers, **params)
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/pjit.py", line 1286, in _pjit_call_impl
    compiled = _pjit_lower(
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/pjit.py", line 1372, in _pjit_lower
    return _pjit_lower_cached(jaxpr, in_shardings, out_shardings, *args, **kwargs)
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/pjit.py", line 1437, in _pjit_lower_cached
    return pxla.lower_sharding_computation(
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/profiler.py", line 314, in wrapper
    return func(*args, **kwargs)
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/interpreters/pxla.py", line 2991, in lower_sharding_
computation
    lowering_result = mlir.lower_jaxpr_to_module(
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/interpreters/mlir.py", line 739, in lower_jaxpr_to_m
odule
    lower_jaxpr_to_fun(
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/interpreters/mlir.py", line 1021, in lower_jaxpr_to_
fun
    out_vals, tokens_out = jaxpr_subcomp(ctx.replace(name_stack=callee_name_stack),
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/_src/interpreters/mlir.py", line 1155, in jaxpr_subcomp
    ans = rule(rule_ctx, *map(_unwrap_singleton_ir_values, in_nodes),
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/experimental/sparse/coo.py", line 587, in _coo_matmat_gpu
_lowering
    return [coo_matmat_hlo(data, row, col, B, shape=shape,
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jaxlib/gpu_sparse.py", line 311, in _coo_matmat_hlo
    buffer_size, opaque = gpu_sparse.build_coo_matmat_descriptor(
jax._src.traceback_util.UnfilteredStackTrace: RuntimeError: jaxlib/gpu/sparse.cc:538: operation gpusparseSpMM_bufferSize( handle.get(), op_A, GPUSPARSE_OPERATION_NON_TRANSPOSE, &alpha, mat_a, mat_b, &beta,
mat_c, C.type, GPUSPARSE_SPMM_COO_ALG, &buffer_size) failed: invalid value

The stack trace below excludes JAX-internal frames.
The preceding is the original exception that occurred, unmodified.

--------------------

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

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jax/experimental/sparse/coo.py", line 587, in _coo_matmat_gpu
_lowering
    return [coo_matmat_hlo(data, row, col, B, shape=shape,
  File "/rds/projects/b/branfosj-bear-apps/devel/2022a/branfosj-1/EL8-ice/software/jax/0.4.4-foss-2022a-CUDA-11.7.0/lib/python3.10/site-packages/jaxlib/gpu_sparse.py", line 311, in _coo_matmat_hlo
    buffer_size, opaque = gpu_sparse.build_coo_matmat_descriptor(
RuntimeError: jaxlib/gpu/sparse.cc:538: operation gpusparseSpMM_bufferSize( handle.get(), op_A, GPUSPARSE_OPERATION_NON_TRANSPOSE, &alpha, mat_a, mat_b, &beta, mat_c, C.type, GPUSPARSE_SPMM_COO_ALG, &buffer
_size) failed: invalid value

What jax/jaxlib version are you using?
0.4.4 for both (compiled from source)
Which accelerator(s) are you using?
GPU
Additional system info
Python 3.10.4, CUDA 11.7.0, cuDNN <IP_ADDRESS>, NCCL 2.12.12
NVIDIA GPU info
The node used has 4 GPUs, but I am inside a cgroup with access to just one.
$ nvidia-smi
Fri Feb 24 09:55:57 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 520.61.05    Driver Version: 520.61.05    CUDA Version: 11.8     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA A100-SXM...  On   | 00000000:31:00.0 Off |                    0 |
| N/A   31C    P0    72W / 500W |      0MiB / 81920MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

Further debugging: This looks to be a CUDA 11.7.0 issue. If I switch to 11.7.1 then I do not see the failure in the code included above.
From the CUDA 11.7.1 release notes:

Improved COO cusparseSpMM Alg2 with support for batched computation, custom row/col-major layout for B/C, and mixed-precision computation.

Thanks for the report! It's proven pretty difficult to write correct lowering code across cusparse versions. Hopefully cusparse will stabilize more in the near future. cc/ @tlu7

I think this has been addressed.


allow users to easily verify the gemm/trmm GPU results with the netlib cblas through client

Although we have tested and seen green lights on extensive platforms including mainstream CPUs & GPUs, we still keep seeing users reporting failures on particular processors & environment.  Many of them are beyond our resources.  clBLAS team is a very small group.  So we always encourage users to debug their failures.  Except the gtest framework already integrated in clBLAS which hard coded various configurations  (by configurations, I mean, matrix size, transpose option, etc),  we have actually provided the "client" tool to test the BLAS routines' performance.
Users can specify whatever configurations through command lines.
One thing is missing that users can not verify/validate the correctness through client.
So, starting from today, users can easily do it if they are unsure of the result of clBLAS gemm & trmm.
Changes:

(1)update readme: Netlib BLAS is preferred over ACML as the CPU reference BLAS. Instruction of geting Netlib on Ubuntu/Windows is given.

(2)now users can validate the correctness of gemm & trmm through client by adding a command "-v 1" (v is verify/validate, -v 0 or nothing will disable the validation). To allow (2), You must have installed with Netlib as discussed in (1).

(3) fix the indentation

More BLAS routines validations will follow.

This change is

Hey @tingxingdong
Windows build is failing


Switch from autoincrementing ids to UUIDs for applications (Security)

Avoid using autoincrementing ids for applications. Else it is trivial to check how many applications there were. Also it is easier to guess paths to files in that case.

Because the attack is not absolutely clear I classify this as low-priority.

I dont know which severity this has to lets add both labels.

As discussed, we don't believe that this is a security vulnerability.
We only expose this ID to (very few) authenticated users who could make conclusions about the number of applications sent to other regions/projects (which is okay).


Introduce limits for StoredValue

Why would we want to introduce limits? Users have to pay for every byte that is stored as StoredValue.


Non-processor related cleaners

Replaces https://github.com/EdgeApp/edge-currency-plugins/pull/151

We should work towards removing all lines of eslint-disable-next-line @typescript-eslint/no-explicit-any.

Replaced by: https://github.com/EdgeApp/edge-currency-plugins/pull/191


Add a flamegraph

For many types of visualization, especially related to performance monitoring, a heatmap is one of the best visualizations. Consider adding this to d3.compose

These are definitely interesting! Should be very doable with d3.compose. We're looking into developing a collection of user-generated / custom charts and components that can be simply plugged in to your project and I'll make sure this is included with them.
(also, tangentially related to https://github.com/CSNW/d3.compose/issues/34 in way, since a linear scale would fit better than ordinal with this type of chart)


feat(functional): make the functional api client a pure function.

Summary
Currently, the functional api client does not support tree-shaking.
This PR solves the problem.
Fixes #97
Test Plan
I'll update the snapshot testing.
Example output
...

export const RolloutService_SetRolloutImage = <RequestOption>(apiClient: ApiClient<RequestOption>, params: Params$RolloutService_SetRolloutImage, option?: RequestOption): Promise<Response$RolloutService_SetRolloutImage$Status$200["application/json"]> => {
    const url = `/api/v1/rollouts/`;
    const headers = {
        "Content-Type": "application/json",
        Accept: "application/json"
    };
    return apiClient.request("PUT", url, headers, params.requestBody, undefined, option);
};
export const RolloutService_UndoRollout = <RequestOption>(apiClient: ApiClient<RequestOption>, params: Params$RolloutService_UndoRollout, option?: RequestOption): Promise<Response$RolloutService_UndoRollout$Status$200["application/json"]> => {
    const url = `/api/v1/rollouts/`;
    const headers = {
        "Content-Type": "application/json",
        Accept: "application/json"
    };
    return apiClient.request("PUT", url, headers, params.requestBody, undefined, option);
};
export const RolloutService_Version = <RequestOption>(apiClient: ApiClient<RequestOption>, option?: RequestOption): Promise<Response$RolloutService_Version$Status$200["application/json"]> => {
    const url = `/api/v1/version`;
    const headers = {
        Accept: "application/json"
    };
    return apiClient.request("GET", url, headers, undefined, undefined, option);
};

...

I don't know why but the url variable is corrupted now...

@hrsh7th
Thank you for your cooperation. We have created #109 based on this idea, which has been committed as Co-authored, so please check it out.

Fixed by #109. Closing.


fix(codeowners): fix codeowners

Overview

I think our CODEOWNERS file was only requiring us on PRs that change styleguide. Now we are required on everything.

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: [ABC-123]
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change
[ ] This PR includes testing instructions tests for the code change
[ ] The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

I have a test branch against this one here that is working as intended.
PR Links and Envs

Repository
PR Link
PR Env

Monolith
Monolith PR
Monolith Env

Portal
Portal Link
Portal Env

Another Repo
Another Link
Another Env

🚀 Styleguide deploy preview ready!https://65143cc45310d2007e9ca002--gamut-preview.netlify.appDeploy Logs


ibm-spectrum-scale-csi-attacher-1 pod is in CrashLoopBackOff  status

ibm-spectrum-scale-csi-attacher-1 pod is in CrashLoopBackOff  status
<EMAIL_ADDRESS>ibm-spectrum-scale-container-native]# oc get pods -o wide
NAME                                               READY   STATUS             RESTARTS   AGE    IP              NODE                             NOMINATED NODE   READINESS GATES
csi-scale-fsetdemo-pod-291491-dup                  1/1     Running            0          125m   <IP_ADDRESS>   worker2.csi250.cp.fyre.ibm.com   <none>           <none>
csi-scale-fsetdemo-pod-291548                      1/1     Running            0          73m    <IP_ADDRESS>   worker2.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-2fg7g                       3/3     Running            0          45m    <IP_ADDRESS>    worker0.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-8kd8n                       3/3     Running            0          46m    <IP_ADDRESS>    worker1.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-attacher-0                  1/1     Running            2          129m   <IP_ADDRESS>   worker2.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-attacher-1                  0/1     CrashLoopBackOff   49         129m   <IP_ADDRESS>     master2.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-operator-5dcbb798dd-pqmmj   1/1     Running            0          129m   <IP_ADDRESS>   worker2.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-provisioner-0               1/1     Running            1          129m   <IP_ADDRESS>   worker2.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-resizer-0                   1/1     Running            1          129m   <IP_ADDRESS>   worker2.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-snapshotter-0               1/1     Running            1          129m   <IP_ADDRESS>   worker2.csi250.cp.fyre.ibm.com   <none>           <none>
ibm-spectrum-scale-csi-xckbn                       3/3     Running            0          45m    <IP_ADDRESS>    worker2.csi250.cp.fyre.ibm.com   <none>           <none>

Events:
  Type     Reason          Age                   From               Message
  ----     ------          ----                  ----               -------
  Normal   Scheduled       40m                   default-scheduler  Successfully assigned ibm-spectrum-scale-csi/ibm-spectrum-scale-csi-attacher-1 to master2.csi250.cp.fyre.ibm.com
  Normal   AddedInterface  40m                   multus             Add eth0 [<IP_ADDRESS>/22] from openshift-sdn
  Normal   Created         39m (x5 over 40m)     kubelet            Created container ibm-spectrum-scale-csi-attacher
  Normal   Started         39m (x5 over 40m)     kubelet            Started container ibm-spectrum-scale-csi-attacher
  Warning  Unhealthy       38m (x5 over 40m)     kubelet            Liveness probe failed: Get "http://<IP_ADDRESS>:8080/healthz/leader-election": dial tcp <IP_ADDRESS>:8080: connect: connection refused
  Normal   Killing         38m (x5 over 40m)     kubelet            Container ibm-spectrum-scale-csi-attacher failed liveness probe, will be restarted
  Warning  BackOff         5m9s (x145 over 38m)  kubelet            Back-off restarting failed container
  Normal   Pulled          17s (x19 over 40m)    kubelet            Container image "us.gcr.io/k8s-artifacts-prod/sig-storage/csi-attacher:v3.4.0" already present on machine
<EMAIL_ADDRESS>volsnapshot_testcases]#

Expected behavior
ibm-spectrum-scale-csi-attacher-1 pod should be in Running state
Data Collection and Debugging
<EMAIL_ADDRESS>volsnapshot_testcases]# oc version
Client Version: 4.8.27
Server Version: 4.8.27
Kubernetes Version: v1.21.6+bb8d50a
<EMAIL_ADDRESS>volsnapshot_testcases]#

Images Used
quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-driver@sha256:a85cbd5d4ff9f1fe95e90d6ad8a030016bf4907bf1ec3e44a89855cddf0ea933
quay.io/ibm-spectrum-scale-dev/ibm-spectrum-scale-csi-operator@sha256:1a74a2b5f004671c090ab9ea37e0cf69e5b83222c6291f1e30b971fa4bb0f2ea

on another CNSA cluster
<EMAIL_ADDRESS>cnsa]# oc get pods -n ibm-spectrum-scale-csi
NAME                                               READY   STATUS             RESTARTS        AGE
ibm-spectrum-scale-csi-6vj6s                       3/3     Running            0               4m26s
ibm-spectrum-scale-csi-8t5v8                       3/3     Running            0               3m35s
ibm-spectrum-scale-csi-attacher-0                  0/1     Error              4 (62s ago)     2m13s
ibm-spectrum-scale-csi-attacher-1                  0/1     CrashLoopBackOff   7 (2m18s ago)   13m
ibm-spectrum-scale-csi-operator-556c9cdf4c-mkxhf   1/1     Running            0               13m
ibm-spectrum-scale-csi-provisioner-0               1/1     Running            4 (3m39s ago)   6h4m
ibm-spectrum-scale-csi-resizer-0                   1/1     Running            4 (3m39s ago)   6h4m
ibm-spectrum-scale-csi-sfmjs                       3/3     Running            0               2m36s
ibm-spectrum-scale-csi-snapshotter-0               1/1     Running            4 (3m39s ago)   6h4m
<EMAIL_ADDRESS>cnsa]#

I see, pod ibm-spectrum-scale-csi-attacher-1 is scheduled to node master2.csi250.cp.fyre.ibm.com, This node doesn't seem to have a driver instance running on it. This could be the reason why the pod is in crashLoopBack in first cluster. @Vrushal can you share the output of oc get pods -o wide of the second cluster?

@nitishkumar4 we still not able to understand why pods are getting scheduled on the master nodes and I did see that :NoSchedule op=Exists  toleration is getting set on attacher pod

verified the fix


Move qpstest.proto to a common area (test/proto) instead of test/cpp/qps

Fixes #3553

LGTM (and one question).


pod install

I am Working on Xcode 9.4.1 and Swift 4.1. But This Pod (pod 'adbutler-ios-sdk', '~> 1.0.2') not install.
Error in coming Unable to find a specification for adbutler-ios-sdk (~> 1.0.2) in Terminal

Hello EmizenIphoneTeam, This repo was created a couple of years ago by a developer no longer with our team.  We are currently working on a new swift 4.1 SDK which should be available soon.  In the meantime, try changing your pod name to AdButler (according to the podspec file in this repo, that is the correct name)

when is coming new pod for xcode 10.0 and swift 4.1 ?. Because i urgent needed upadated pod .

Are you unable to use version 1.0.1?

Yes
On Fri, Oct 12, 2018, 1:08 AM William Prevett<EMAIL_ADDRESS>wrote:

Are you unable to use version 1.0.1?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/adbutler/adbutler-ios-sdk/issues/1#issuecomment-429090909,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AoRsabgoG2c0hhK5JBqihPPSj6ssB-Mkks5uj54dgaJpZM4WpQYy
.

I downloaded the pod and it seems to work for me.  If you are using swift 4.1 you will need to add this to the ABImageView tap function @objc func tap().  if you need more help send me an email<EMAIL_ADDRESS> We don't have an estimate right now on when the newer SDK will be available.  If it's urgent, give me a shout.


Add basic MiMa configuration

Current coverage is 80.89% (diff: 100%)

Merging #398 into master will not change coverage

@@             master       #398   diff @@
==========================================
  Files            63         63
  Lines          1989       1989
  Methods        1831       1831
  Messages          0          0
  Branches        158        158
==========================================
  Hits           1609       1609
  Misses          380        380
  Partials          0          0

Powered by Codecov. Last update 360a61c...7df1a29


Fix GHA removing label

This isn't an issue... The branch needs to be named bugfix/... 🙃
Closes #274


examples files

my yaml file references an external file with examples:
  parameters:
    - name: 'id'
      in: 'path'
      description: 'Id of the object'
      required: true
      schema:
        type: 'string'
        format: 'guid'
      examples:
        camera:
          $ref: 'examples.json'

but when I run my raft_local.py job, I get this compiler error:
Unhandled exception. System.AggregateException: One or more errors occurred. (Could not resolve the JSON path '/work_dir_7bd549a8-96e8-4301-8b02-0e3d2125e37b/examples.json' with the full JSON path '/work_dir_7bd549a8-96e8-4301-8b02-0e3d2125e37b/examples.json'.)
---> System.InvalidOperationException: Could not resolve the JSON path '/work_dir_7bd549a8-96e8-4301-8b02-0e3d2125e37b/examples.json' with the full JSON path '/work_dir_7bd549a8-96e8-4301-8b02-0e3d2125e37b/examples.json'.
---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.IO.FileNotFoundException: Could not find file '/work_dir_7bd549a8-96e8-4301-8b02-0e3d2125e37b/examples.json'.
clearly RESTler in the docker container tries to find the examples file in its workdir but can't. How do you get RAFT to copy the examples files into the container so that RESTler can resolve them?

You can pass the folder with examples to docker container by mounting it. See this example: https://github.com/microsoft/rest-api-fuzz-testing/blob/b992047f6b593008e9093ef59b17e261762445d5/cli/samples/restler/running-against-raft-common-file-share/fuzz.json#L4

that example shows how to pass compile output as input to later RESTler stages. How do you tell the compiler to use the file share mount that you set up in the config? If I only mount a share as shown in the example, I still get the error.

you can mount any file share. The example passes a result of compile step to run.
But you can create an example share same way and pass it to compile step.
see this example:
https://github.com/microsoft/rest-api-fuzz-testing/blob/main/cli/samples/restler/replay-a-bug/replay-common-file-share.json
this example mounts a file share to replay a RESTler bug.
So you can mount any file share and pass it to RESTler

I have this configuration:
{
"readOnlyFileShareMounts": [
{
"fileShareName": "specifications",
"mountPath": "/specifications"
},
{
"fileShareName": "examples",
"mountPath": "/examples"
}
],...
"tasks": [
{
"toolName": "RESTler",
"outputFolder": "restler",
"keyVaultSecrets": [ "TOKEN" ],
"authenticationMethod": {
"Token": "Token"
},
"targetConfiguration": {
"apiSpecifications": [
"http://host.docker.internal:8000/openapi_cams_only.yaml"
],
"endpoint": "http://host.docker.internal/managementserver/rest"
},
"toolConfiguration": {
"tasks": [
{
"task": "Compile",
"runConfiguration": {
"inputFolderPath": "/examples"
},...
but I still get the same error - does the swagger compile step know to look in the share mount or do I need to do something else in my configuration?

you need to change your Compile task and ExamplesDirectory there:
        /// The directory where the compiler should look for examples.
        /// If 'discoverExamples' is true, this directory will contain the
        /// example files that have been discovered.
        /// If 'discoverExamples' is false, every time an example is used in the
        /// Swagger file, RESTler will first look for it in this directory.
        ExamplesDirectory : string

"tasks": [
  {
    "toolName": "RESTler",
    "outputFolder": "compile",
    "toolConfiguration": {
      "task": "Compile",
    "compileConfiguration" : {
     "exampleConfigFilePath " : "/examples"
    }
    }
  }
]

Here is a good example that uses compile configuration section 👍
https://github.com/microsoft/rest-api-fuzz-testing/blob/main/cli/samples/restler/running-against-raft/compile.json

I added this to my configuration:
"compileConfiguration":
{
"useRefreshableToken": true,
"discoverExamples": false,
"useBodyExamples": true,
"useQueryExamples": true,
"examplesDirectory": "Examples",
"exampleConfigFilePath": "/examples"
}
and I changed the reference in my yaml file to:
examples:
camera:
$ref: '../examples/examples.json'
now I get a different error so i assume that worked:
Unhandled exception. System.AggregateException: One or more errors occurred. (Unable to cast object of type 'NJsonSchema.JsonSchema' to type 'NSwag.OpenApiExample'.)
---> System.InvalidCastException: Unable to cast object of type 'NJsonSchema.JsonSchema' to type 'NSwag.OpenApiExample'.
at NJsonSchema.References.JsonReferenceBase1.NJsonSchema.References.IJsonReferenceBase.set_Reference(IJsonReference value)    at NJsonSchema.JsonSchemaReferenceUtilities.JsonReferenceUpdater.VisitJsonReferenceAsync(IJsonReference reference, String path, String typeNameHint)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action`1 replacer)
my examples.json file looks like this:
{
"parameters": {
"id": "09b11ea3-085c-4641-a84a-ce2f68a09a53"
}
}

Where do you get the failure from ? is it happening in RAFT or RESTler ?

It's coming from RAFT - here's the full stack trace:
Unhandled exception. System.AggregateException: One or more errors occurred. (Unable to cast object of type 'NJsonSchema.JsonSchema' to type 'NSwag.OpenApiExample'.)
---> System.InvalidCastException: Unable to cast object of type 'NJsonSchema.JsonSchema' to type 'NSwag.OpenApiExample'.
at NJsonSchema.References.JsonReferenceBase1.NJsonSchema.References.IJsonReferenceBase.set_Reference(IJsonReference value)    at NJsonSchema.JsonSchemaReferenceUtilities.JsonReferenceUpdater.VisitJsonReferenceAsync(IJsonReference reference, String path, String typeNameHint)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action1 replacer)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action1 replacer)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action1 replacer)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action1 replacer)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action1 replacer)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action1 replacer)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action1 replacer)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj, String path, String typeNameHint, ISet1 checkedObjects, Action1 replacer)    at NJsonSchema.Visitors.AsyncJsonReferenceVisitorBase.VisitAsync(Object obj)    at NJsonSchema.JsonSchemaReferenceUtilities.JsonReferenceUpdater.VisitAsync(Object obj)    at NJsonSchema.JsonSchemaReferenceUtilities.UpdateSchemaReferencesAsync(Object rootObject, JsonReferenceResolver referenceResolver, IContractResolver contractResolver)    at NJsonSchema.Infrastructure.JsonSchemaSerialization.FromJsonAsync[T](String json, SchemaType schemaType, String documentPath, Func2 referenceResolverFactory, IContractResolver contractResolver)
at NSwag.OpenApiDocument.FromJsonAsync(String data, String documentPath, SchemaType expectedSchemaType, Func2 referenceResolverFactory)    at NSwag.OpenApiDocument.FromFileAsync(String filePath)    --- End of inner exception stack trace ---    at Microsoft.FSharp.Control.AsyncResult1.Commit() in F:\workspace_work\1\s\src\fsharp\FSharp.Core\async.fs:line 349
at Microsoft.FSharp.Control.AsyncPrimitives.RunSynchronouslyInCurrentThread[a](CancellationToken cancellationToken, FSharpAsync1 computation) in F:\workspace\_work\1\s\src\fsharp\FSharp.Core\async.fs:line 882    at Microsoft.FSharp.Control.AsyncPrimitives.RunSynchronously[T](CancellationToken cancellationToken, FSharpAsync1 computation, FSharpOption1 timeout) in F:\workspace\_work\1\s\src\fsharp\FSharp.Core\async.fs:line 890    at Microsoft.FSharp.Control.FSharpAsync.RunSynchronously[T](FSharpAsync1 computation, FSharpOption1 timeout, FSharpOption1 cancellationToken) in F:\workspace_work\1\s\src\fsharp\FSharp.Core\async.fs:line 1154
at Restler.Workflow.swaggerDocs@88-1.Invoke(String fp) in D:\a\1\s\src\compiler\Restler.Compiler\Workflow.fs:line 88
at Microsoft.FSharp.Primitives.Basics.List.map[T,TResult](FSharpFunc2 mapping, FSharpList1 x) in F:\workspace_work\1\s\src\fsharp\FSharp.Core\local.fs:line 248
at Microsoft.FSharp.Collections.ListModule.Map[T,TResult](FSharpFunc2 mapping, FSharpList1 list) in F:\workspace_work\1\s\src\fsharp\FSharp.Core\list.fs:line 75
at Restler.Workflow.generateGrammarFromSwagger(String grammarOutputDirectoryPath, FSharpOption1 swaggerDoc, Config config) in D:\a\1\s\src\compiler\Restler.Compiler\Workflow.fs:line 88    at Restler.Workflow.generateRestlerGrammar(FSharpOption1 swaggerDoc, Config config) in D:\a\1\s\src\compiler\Restler.Compiler\Workflow.fs:line 247
at Program.main(String[] argv) in D:\a\1\s\src\compiler\Restler.CompilerExe\Program.fs:line 37

@LYDE1234 If you are referencing the example from the specification, and they are in the same directory (or a sub-directory with relative path from the specification), you do not need the ExampleConfigFilePath or an example config file.  If that works for you, just omit the above file path from config.json, put the example in the same directory as the spec, and hopefully the issue will be resolved.
I believe the reason for your error is you are referencing the example config file in your specification yaml.  The specification should only reference actual examples (like the one you provided which contains "id").  The example config file should only be referenced in config.json, and the example config file contains a list of request types, which point to one or more examples.
See https://github.com/microsoft/restler-fuzzer/blob/main/docs/user-guide/Examples.md for more details.


theoretical minimum: install wasm-pack

Had to install wask-pack

It sounds like a bug, cargo-make should install it automatically.

cargo-make should install it automatically

I thought so too but it didn't.

Could you try it with changes in https://github.com/David-OConnor/seed-quickstart/issues/10. please?

Closing, since this is an issue with the quickstart repo.


Unescaped Slashes Aint Welcome Around 'Ere

Seeing as unespcaped slashes are not allowed, and various tools will escape them or just not know what to do with one due to the behavior being undefined, we should probably define it.
Closes https://github.com/OAI/OpenAPI-Specification/issues/2204
Might close https://github.com/OAI/OpenAPI-Specification/issues/892

I will investigate URI Templates to identify all the allowed characters and we will update to include all disallowed chars.

Hola soy novato desde cero e cometido un sin fin de errores y al parecer e afectado a terceros sin no sé si se pueda seguir trabajando con este repocitorio estoy esperando respuesta de la plataforma ojalá y me den luz verde para seguir adelante gracias

Bueno de verdad que no se de donde empezar ni terminar alguien lo puedes
hacer terminar??? Y si hay ganancias los repartemo de entre los que
aportamos todos parejo cómo ven??
El jue., 29 oct. 2020 9:59 a. m., Darrel<EMAIL_ADDRESS>escribió:

@darrelmiller commented on this pull request.
In versions/3.1.0.md
https://github.com/OAI/OpenAPI-Specification/pull/2218#discussion_r514374465
:

@@ -75,6 +75,8 @@ Path templating refers to the usage of template expressions, delimited by curly

Each template expression in the path MUST correspond to a path parameter that is included in the Path Item itself and/or in each of the Path Item's Operations.
+The value for these path parameters MUST NOT contain unescaped forward slashes (/).
I believe we should also outlaw ? and # as they would change the meaning
of the URL.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/OAI/OpenAPI-Specification/pull/2218#pullrequestreview-519823358,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQW4FH2PKE6DOWUIOENV2N3SNGGNFANCNFSM4MSVTYPA
.

@leonmende the de facto language for this repository is English, for better or worse. Could you provide a translation with any future comments to save the majority of recipients from having to do it? I would also ask that you refrain from making general comments about contributing to the project on existing technical issues or unrelated PRs. Please raise a new issue if you have an on-topic one. "Profits" and cryptocurrencies (except where related to APIs) are not on-topic.

Implemented all feedback:

Removed the RFC mention
number sign not hash
"forward query string" lol

@leonmende the de facto language for this repository is English, for better or worse. Could you provide a translation with any future comments to save the majority of recipients from having to do it? I would also ask that you refrain from making general comments about contributing to the project on existing technical issues or unrelated PRs. Please raise a new issue if you have an on-topic one. "Profits" and cryptocurrencies (except where related to APIs) are not on-topic.

Le pido disculpas no haré más y a decir verdad creo que estoy fuera de lugar y con su permiso me retiro!!

I apologize I will not do more and to tell the truth I think I am out of place and with your permission I am leaving !!


Respect ignore config when publishing

Resolves https://github.com/changesets/changesets/discussions/783
TODO:

[ ] Confirm the correctness of the approach (should we read ignore elsewhere?)
[ ] Add tests
[ ] Add .changesets/*.md (what semver type is it?)

I don’t have capacity to continue this PR, but feel free to recycle the diff, if needed. Thanks for this awesome package 👏


Add site to render_content hookspec

https://github.com/render-engine/render-engine/blob/b4d2f9d9e27e84bde4c6a1a177e6776ada59a500/src/render_engine/site.py#L189-L190
Currently you can't access content from the site in this plugin.
Adding sites to the render-content-hookspect allows or things like accessing routes from the route-list.

Warning
This may be a breaking change for plugins

I think we need to continue solidifying the plugin spec before implementing


August 2025 Test Campaign #4

Script to package up the toolchain for off air wave file-> audio;
./radae_rx.sh model19_check3/checkpoints/checkpoint_epoch_100.pth ~/Downloads/websdr_recording_2024-09-06T19_55_45Z_14180.0kHz.wav - -v 2 --auxdata

@tmiw https://github.com/drowe67/radae/pull/26/commits/729146704b534ac9776e8d939e1dc2ff6fb9a467 is an attempt a fixing that small tmax issue we discussed via email a few hours ago.


Workaround for the COPY function

#1
Check it and let me know.

Please make the changes I mentioned in Issues.

@maddypie changes are made !
😄


Originating element not set

With e.g.
@GenerateTypeAdapter
@AutoValue
public abstract class Foo {
    abstract String bar();
    @SerializedName("Baz") abstract String baz();
    abstract int quux();
    abstract String with_underscores();

    // The public static method returning a TypeAdapter<Foo> is what
    // tells auto-value-gson to create a TypeAdapter for Foo.
    public static TypeAdapter<Foo> typeAdapter(Gson gson) {
        return new Foo_GsonTypeAdapter(gson);
    }
}

and dependencies
implementation group: 'com.google.auto.value', name: 'auto-value-annotations', version: '1.7'
annotationProcessor("com.ryanharter.auto.value:auto-value-gson:1.1.1")
implementation("com.ryanharter.auto.value:auto-value-gson-runtime:1.1.1")

incremental annotation processing fails because it does not pass the originating element when generating com.example.myapplication.Foo_GsonTypeAdapter.
Both Gradle Java compilation and KAPT fail to run incrementally.
The issue seems to be that AutoValueGsonExtension.generateClass does not set originating element for the TypeSpec.Builder it is using to write the class.

@ZacSweers was just looking into that prior to a release. @ZacSweers, does it look like that might be the issue?

On it!

I think my confusion was that we were hiding this behind autovalue's guard of originating elements, but I guess the rules are different if we're not generating it into a nested type anymore?


chore(main): release sdk 5.0.0

:robot: I have created a release beep boop
5.0.0 (2024-03-23)
⚠ BREAKING CHANGES

sdk: Refactor public functions to use parameter object ⚙

Bug Fixes

sdk: Update README.md (b79742e)
Update SDK README.md (330323c)

Miscellaneous Chores

sdk: Monthly check ✨ (bee15fb)

Code Refactoring

sdk: Refactor public functions to use parameter object ⚙ (53e81b5)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/paraspell/xcm-tools/releases/tag/sdk-v5.0.0 :sunflower:


Add missed markupsafe to modal.py

See Issue #2 and its comments.

@deb17 Please review when you can, thanks.


Unable to identify anything during the certificate phase

I'm trying to conditionally request a client certificate with kong.client.tls.request_client_certificate() in the certificate phase, however, I don't find anything I can use to identify the request.
Almost none of the methods are available in the certificate phase, however according to the docs of the mtls plugin (https://docs.konghq.com/hub/kong-inc/mtls-auth/#client-certificate-request), the SNI should be available.
Is there a way to get the SNI in the certificate phase?

I remember I've answered the same question before but cannot find the record...
The plugin implemented the logic to interfere certificate with an internal interface. The internal interface is not accessible from external plugins (Go, Python, JS), and is very dangerous to implement yourself even with Lua plugins.
So sadly we don't have a way to do it for Python.

Hmm, that makes the whole certificate phase pretty useless, since we can't figure out what request we are handling. You can only request a client certificate for all requests.
I understand that the mtls plugin isn't open source, but by denying access to this information from other plugins, there is no solution but to use the closed source plugin?

@michaelarnauts
Sorry. I confirmed with @fffonion offline and it's possible to do what you want (just not the way I expected when I wrote down the answer).
kong.nginx.get_var("ssl_server_name") can be used to get the Nginx variable "ssl_server_name".
Ref:
https://kong.github.io/kong-python-pdk/kong.html#kong.kong.nginx.get_var
(Note the document is not accurate. Will create a fix for that.)
http://nginx.org/en/docs/http/ngx_http_ssl_module.html#:~:text=%24-,ssl_server_name,-returns the server

@StarlightIbuki thanks for the update. I'll try to find some time to test the kong.nginx.get_var() method.

@StarlightIbuki @fffonion
I've tried the suggested kong.nginx.get_var("ssl_server_name"), but I get back the following error.
It seems that this is thrown due to a patch that kong made itself: https://github.com/Kong/kong/blob/a9ff98a168924b8135eda010f3c79bc91c157908/build/openresty/patches/ngx_lua-0.10.21_02-dyn_upstream_keepalive.patch#L1030
Python code:
    def certificate(self, kong: kong.kong):
        kong.log.debug("---- Certificate execution -----")
        kong.log.debug("nginx var ssl_server_name = %s" % kong.nginx.get_var("ssl_server_name"))

Kong logs:
...
2023/05/31 14:19:15 [info] 1245035#0: *595 [mtls-auth-prod:1245061] DEBG - [22:19:15] rpc: #2 return: {'Data': {'Method': 'kong.log.debug', 'Args': ('---- Certificate execution -----',)}, 'EventId': 0}, context: ngx.timer
2023/05/31 14:19:15 [debug] 1245037#0: *606 [kong] mp_rpc.lua:161 [mtls-auth-prod] ---- Certificate execution -----
2023/05/31 14:19:15 [info] 1245035#0: *595 [mtls-auth-prod:1245061] DEBG - [22:19:15] rpc: #3 method: plugin.Step args: [{'EventId': 0}], context: ngx.timer
2023/05/31 14:19:15 [info] 1245035#0: *595 [mtls-auth-prod:1245061] DEBG - [22:19:15] rpc: #3 return: {'Data': {'Method': 'kong.nginx.get_var', 'Args': ('ssl_server_name',)}, 'EventId': 0}, context: ngx.timer
2023/05/31 14:19:15 [error] 1245037#0: *606 lua entry thread aborted: runtime error: ...local/share/lua/5.1/kong/runloop/plugin_servers/init.lua:41: API disabled in the current context
stack traceback:
coroutine 0:
        [C]: in function 'error'
        /usr/local/openresty/lualib/resty/kong/var.lua:111: in function '__index'
        ...local/share/lua/5.1/kong/runloop/plugin_servers/init.lua:41: in function 'method'
        ...cal/share/lua/5.1/kong/runloop/plugin_servers/mp_rpc.lua:161: in function 'call_pdk_method'
        ...cal/share/lua/5.1/kong/runloop/plugin_servers/mp_rpc.lua:317: in function 'bridge_loop'
        ...cal/share/lua/5.1/kong/runloop/plugin_servers/mp_rpc.lua:336: in function 'handle_event'
        ...local/share/lua/5.1/kong/runloop/plugin_servers/init.lua:274: in function <...local/share/lua/5.1/kong/runloop/plugin_servers/init.lua:273>
        /usr/local/share/lua/5.1/kong/init.lua:351: in function 'execute_plugins_iterator'
        /usr/local/share/lua/5.1/kong/init.lua:879: in function 'ssl_certificate'
        ssl_certificate_by_lua:2: in main chunk, context: ssl_certificate_by_lua*, client: xxx.xxx.xxx.xxx, server: <IP_ADDRESS>:443
2023/05/31 14:19:15 [info] 1245037#0: *605 SSL_do_handshake() failed (SSL: error:1417A179:SSL routines:tls_post_process_client_hello:cert cb error) while SSL handshaking, client: xxx.xxx.xxx.xxx, server: <IP_ADDRESS>:443

Sorry for the confusion. I thought the API is available for certificate phase but it's actually not.
Ping @fffonion for help on this issue. Do we have any workaround for this?

Also sorry for replying late. Please feel free to ping me when you think it takes too long.

yes, sorry this was an oversight, the approach doesn't work in certificate phase. we will need a new PDK API that calls ngx.ssl.server_name() to extract SNI, there's no such support exists in kong yet.

yes, sorry this was an oversight, the approach doesn't work in certificate phase. we will need a new PDK API that calls ngx.ssl.server_name() to extract SNI, there's no such support exists in kong yet.

That's unfortunate. Is this planned, or something where I could help?

@michaelarnauts this is currently not on our roadmap. PRs are welcomed, https://github.com/Kong/kong/pull/9512 is a good example on how to add such function in PDK. Note you only need to implement at kong/lua side, no extra effort needed on python-pdk side.


[Bug] Umd distribution no longer being included in the release packages

Describe the Bug
Every version of the library since 2.0.0-beta.27 has been missing dist/umd from the release packages, despite there being no documented removal of it (that I could find) and the 2.0.0 migration guide stating that it should still exist.

Steps to Reproduce

navigate to https://www.npmjs.com/package/@cornerstonejs/core
click the code tab
navigate to /dist, note the lack of umd
click the versions tab
go to any version before 2.0.0-beta.27
check /dist again
go to version 2.0.0-beta.27
check /dist again

The current behavior
The umd distribution is missing from the library, contradicting the documentation.
The expected behavior
Either:

The umd distribution is re-added to the published package
The documentation is updated to reflect that it has been removed

OS
Windows 10
Node version
v18.20.4
Browser
Chrome 130.0.6723.117

Yes that is intentional, use ESM, it works


Reference superclass explicitly in the mixin demo

Hey Lit team,
The playground example on the live site is not working, the second element is not rendered correctly because super.styles does not work here. So I implemented a quick fix to replace super.styles with Highlightable(LitElement).styles.
Actually the Lit documentation also mentions about explicitly referencing the superclass instead of using super: https://lit.dev/docs/components/styles/#inheriting-styles-from-a-superclass
Thanks,

/gcbrun

Fixed sample is here:
https://pr841-fd214f1---lit-dev-5ftespv5na-uc.a.run.app/docs/composition/mixins/#creating-mixins-for-litelement
Original sample is here:
https://lit.dev/docs/composition/mixins/#creating-mixins-for-litelement
Verified that it works in JavaScript, but fails in TypeScript.
I'm inclined to merge this but /cc @kevinpschaaf as resident expert in case there's some other way we should be doing this.

It would be better to not apply the mixin twice, so would you mind pulling the HilightableLitElement out as a const in element-two.ts? ala this: https://lit.dev/playground/#gist=0b5486728fc473c171200ca60cbc6bd2
Also, in looking at this I realized it would be safest for the mixin to also be defensive about being applied to a class that already has styles, so I've updated the highlightable.ts to do that also. Mind folding these changes in?

Thanks Arthur and Kevin!
Yeah caching the mixin makes sense, it will improve the performance a bit. I also applied your suggestion in the highlightable.ts. Can you take another look on my changes?
Arthur, you said it failed in TS, can you elaborate it more?

/gcbrun


Highlight query matched chars

Probably will work well after this https://github.com/jacek-kurlit/pik/issues/2
Since we will have matched indexes we can think about handling too long values in process table

This one will be possible only if we use fuzzy search for all types of queries.

This one will be possible only if we use fuzzy search for all types of queries.

Yes that was my plan - replace contains query with fuzzy to provide hightlight and better UX

It seems this conversation is scattered across the issues :)
This is my comment from another thread:

What do you think about applying this to the rest of the types of queries? I guess it will only be Cmd and probably Args. I don't think it is good to add it for ports search.

Implementation ready it just waits for general refactor because there is a lot to do before it can be merged


Implementation of MeetingIssueCreator class that handles issues for working meetings

The class that handles issues for working meetings and its help are to implement.

The code was checked with the following call:
from dynpy.utilities.creators import MeetingIssueCreator
help(MeetingIssueCreator)


Updating to Chromium 86.0.4240.183

Please respond if you would like to update ungoogled-chromium to the new stable Chromium version.
Notes for the developer
Once you claim it, it is advisable that you create a Draft Pull Request for increased visibility:

Finally, make sure to reference this issue in your PR.
Feel free to ask questions and discuss issues here along the way. Thanks!
Notes for others
Feel free to raise issues or questions throughout the process. However, please refrain from asking ETAs unless no visible progress has been made here or on the developer's PR for a while (e.g. 2 weeks).
Note on the Chromium version
According to Google's Git repository, this is because 86.0.4240.124 -> 86.0.4240.175.

I plan on working on this.


docs-bug(MatFormField): custom form field example: why MAT_FORM_FIELD is injected

Documentation Feedback
In the cusom form field example I see the line
@Optional() @Inject(MAT_FORM_FIELD) public _formField: MatFormField,

But the related guide say nothing about these injection.
Also from the code it's unclear why it's injected.  _formField is not used anywhere.
Could explain in the docs why it's injected? Or remove it if it's unnecessary

Confirmed that the injection is not needed - probably leftover from something else and can just be removed. Feel free to send a PR to remove it.

I stumbled against this same issue and I would like to make a PR, if it's ok with you @AlexElin  @annieyw

as I was investigating more I found that  _formField is used indeed in the template here:
https://github.com/angular/components/blob/ad248652e7da31398176fe11878b59805e440b5a/src/components-examples/material-experimental/mdc-form-field/mdc-form-field-custom-control/example-tel-input-example.html#L3
@annieyw would you please take another look into it?

@ammarnajjar ah thanks for pointing it out, I must've missed it when I looked at the example initially. In that case _formField should be kept in.
Closing this as this is resolved.

@annieyw currently the Improving accessibility chapter is not aligned with the actual code.
In the guide we see     [attr.aria-labelledby]="parentFormField?.getLabelId()"
But the actual code is [attr.aria-labelledby]="_formField?.getLabelId()">
Because of that a docs reader can't find anything by seacrhing _formField in the docs.
So a small change is required and the issue could be reopened


Marking required fields in OpenApi swagger document

Currently in the version of the OpenApi dll we are using, the required fields aren’t marked. For eg:
In the Leads/QualifyLead the Odata XML shows that these fileds: CreateAccount, CreateContact, CreateOpportunity, Status are Nullable=false (meaning required)

But the OpenApi swagger doesn’t show that these fields are required:

Steps to reproduce
Use any bound/unbound action and check the metadata and compare the OpenApi swagger generated and you will notice the nullable fields are not set as required.
Expected result
The OpenApi swagger marks the required fields and returns it as a part of the swagger document
Actual result
Currently in the version of the OpenApi dll we are using, the required fields aren’t marked.

Which version of the conversion library are you using?

I think currently we are using 1.1.2

I am assuming the upgrade fixed this issue. Please re-open if this is still a problem.


Show instance for UtxoState

This PR introduces a Show instance for UtxoState, and is related to #266.
I'm not sure where to put the instance declaration: either I put it next to the definition of UtxoState, but it makes a cyclic dependency graph, or I put it next to the definition of prettyUtxoState, and it feels kind of lost.

Check #265 for insight on the dependency cycle issue.
I am not in favor of re-introducing a Show instance for UtxoState that is based on PrettyCooked. See my opinion on issue #266


Poolable Component instances always have their reset() method called

This is an extension of PR #303, ensuring Poolable Component instances have reset() called on them regardless of if their respective Pools are full. The previous PR handled the case where if the EntityPool was full no Components would be reset(), this PR covers the case where if individual ComponentPools are full the Components are not being reset().

After discussing stuff with mgsx we agreed Components having their reset() method called shouldn't be a guaranteed thing. I understand why as it introduces unnecessary overhead catering for a use case that isn't ideal in the first place.


Update to support metadata service v3

What is this PR for?
Resolved https://github.com/line/line-fido2-server/issues/11
Overview or reasons

Official termination of MDS v2 support (until October 2022)
https://fidoalliance.org/metadata/
https://fidoalliance.org/legacy-mds2-information
https://fidoalliance.org/specs/mds/fido-metadata-service-v3.0-ps-20210518.html#metadata-blob-payload-entry-dictionary

Tasks

Modify MdsFetchTask to support v3.
Delete common class libraries for messages (common-1.3-SNAPSHOT.jar) and move associated classes.
Add a column to the METADATA table. (biometricStatusReports)
Refactor Mds-related code. (Added helper, util, exception handling classes)
Add test code.

How to test

You can perform unit tests using the MdsV3MetadataHelperTest class.

@haxelion nim,
I modified the code for the part you commented on.
I appreciate your help!

I first only reviewed the data model itself and compared it with the spec. I made several specific comments but I have a more general question:
How do you differentiate between required and non required field in your lombok based data model?

Basically, you can simply declare that it is a required field through the final keyword or @NonNull.
    @NonNull
    private String id;

    final private String data;

As you may know, an exception occurs when there is no required field when creating that data object.
Are you considering the verification process for the required fields?

@kj84park nim, thank you very much for the fixes. I tend to prefer when the data model enforces the spec requirement but I don't think it's a threat model in this case as the metadata service is a trusted and authenticated source. Let me take a deeper look at the logic now.

@haxelion nim,
All the modifications have been completed.
Please check them out
Thank you again for your feedback.
For your reference, I referred to the document below for AuthenticatorGetInfo class.
https://fidoalliance.org/specs/fido-v2.1-ps-20210615/fido-client-to-authenticator-protocol-v2.1-ps-errata-20220621.html#authenticatorGetInfo