pipenv fails to parse platform-specific requirement in Pipfile when using a versioning scheme

Issue description
When installing a package with a platform specifier for windows whilst on mac, along with a package version like the following
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
python-magic = "==0.4.*"
python-magic-bin = { version = "==0.4.*", markers="sys_platform == 'win32'" }

[dev-packages]

[requires]
python_version = "3.11"
python_full_version = "3.11.1"

i'm getting the following error
pipenv.patched.pip._internal.exceptions.InstallationError: Invalid requirement: 'python-magic-bin0.4.*'

It feels like there's a parsing issue. If I wildcard the version it works fine and it appears the == has been stripped away. What's also weird to me though is that in the stdout output it clearly skips the dependency due to it being 'win32'.
Non verbose output:

(pipfile-bug) ➜  pipfile-bug pipenv install
Pipfile.lock (9df141) out of date: run `pipfile lock` to update to (4a8526)...
Running $ pipenv lock then $ pipenv sync.
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✔ Success!
⠙ Locking packages...Warning: Could not find a matching version of python-magic-bin==0.4.*; sys_platform == "win32" for your environment, its dependencies will be skipped.

Traceback (most recent call last):
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_vendor/packaging/requirements.py", line 102, in __init__
    req = REQUIREMENT.parseString(requirement_string)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_vendor/pyparsing/util.py", line 256, in _inner
    return fn(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_vendor/pyparsing/core.py", line 1190, in parse_string
    raise exc.with_traceback(None)
pipenv.patched.pip._vendor.pyparsing.exceptions.ParseException: Expected string_end, found '.'  (at char 19), (line:1, col:20)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_internal/req/constructors.py", line 371, in _parse_req_string
    req = get_requirement(req_as_string)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_internal/utils/packaging.py", line 45, in get_requirement
    return Requirement(req_string)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_vendor/packaging/requirements.py", line 104, in __init__
    raise InvalidRequirement(
pipenv.patched.pip._vendor.packaging.requirements.InvalidRequirement: Parse error at "'.*'": Expected string_end

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/pipenv", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/cli/options.py", line 58, in main
    return super().main(*args, **kwargs, windows_expand_args=False)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/decorators.py", line 92, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/cli/command.py", line 209, in install
    do_install(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/routines/install.py", line 93, in do_install
    do_init(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/routines/install.py", line 624, in do_init
    do_update(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/routines/update.py", line 61, in do_update
    do_lock(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/routines/lock.py", line 66, in do_lock
    venv_resolve_deps(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/resolver.py", line 899, in venv_resolve_deps
    return prepare_lockfile(
           ^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/locking.py", line 148, in prepare_lockfile
    lockfile_entry = get_locked_dep(project, dep, pipfile, current_entry)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/locking.py", line 131, in get_locked_dep
    lockfile_entry = clean_resolved_dep(project, dep, is_top_level, current_entry)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 277, in clean_resolved_dep
    potential_hashes = unearth_hashes_for_dep(project, dep)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 189, in unearth_hashes_for_dep
    install_req, markers, _ = install_req_from_pipfile(dep["name"], dep)
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 1097, in install_req_from_pipfile
    install_req, _ = expansive_install_req_from_line(
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 996, in expansive_install_req_from_line
    parts = parse_req_from_line(pip_line, line_source)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_internal/req/constructors.py", line 399, in parse_req_from_line
    req: Optional[Requirement] = _parse_req_string(req_as_string)
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_internal/req/constructors.py", line 385, in _parse_req_string
    raise InstallationError(msg)
pipenv.patched.pip._internal.exceptions.InstallationError: Invalid requirement: 'python-magic-bin0.4.*'

Verbose output

pipfile-bug pipenv install --verbose
Pipfile.lock (9df141) out of date: run `pipfile lock` to update to (51a332)...
Running $ pipenv lock then $ pipenv sync.
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
Could not find a matching version of python-magic-bin==0.4.*; sys_platform == "win32" for your environment, its dependencies will be skipped.
INFO:pipenv.patched.pip._internal.resolution.resolvelib.factory:Ignoring python-magic-bin: markers 'sys_platform == "win32"' don't match your environment
INFO:pipenv.patched.pip._internal.resolution.resolvelib.reporter:Reporter.starting()
INFO:pipenv.patched.pip._internal.resolution.resolvelib.reporter:Reporter.adding_requirement(SpecifierRequirement('python-magic==0.4.*'), None)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting python-magic==0.4.* (from -r
/var/folders/n4/hqk2v4vx52qbpt0h8cl_3__c0000gn/T/pipenv-8l0qtcv3-requirements/pipenv-2tgqli6m-constraints.txt (line 2))
INFO:pipenv.patched.pip._internal.network.download:Using cached python_magic-0.4.27-py2.py3-none-any.whl.metadata (5.8 kB)
INFO:pipenv.patched.pip._internal.resolution.resolvelib.reporter:Reporter.starting_round(0)
INFO:pipenv.patched.pip._internal.resolution.resolvelib.reporter:Reporter.pinning(LinkCandidate('https://files.pythonhosted.org/packages/6c/73/9f872cb81fc5c3bb48f7227872c28975f998f3e7c2b1c16e
95e6432bbb90/python_magic-0.4.27-py2.py3-none-any.whl (from https://pypi.org/simple/python-magic/) (requires-python:>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*)'))
INFO:pipenv.patched.pip._internal.resolution.resolvelib.reporter:Reporter.ending_round(0, state)
INFO:pipenv.patched.pip._internal.resolution.resolvelib.reporter:Reporter.starting_round(1)
INFO:pipenv.patched.pip._internal.resolution.resolvelib.reporter:Reporter.ending(State(mapping=OrderedDict([('python-magic',
LinkCandidate('https://files.pythonhosted.org/packages/6c/73/9f872cb81fc5c3bb48f7227872c28975f998f3e7c2b1c16e95e6432bbb90/python_magic-0.4.27-py2.py3-none-any.whl (from
https://pypi.org/simple/python-magic/) (requires-python:>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*)'))]), criteria={'python-magic':
Criterion((SpecifierRequirement('python-magic==0.4.*'), via=None))}, backtrack_causes=[]))
INFO:pipenv.patched.pip._internal.network.download:Using cached python_magic-0.4.27-py2.py3-none-any.whl (13 kB)
⠹ Locking packages...
✔ Success!
Warning: Error generating hash for python-magic-bin.
Traceback (most recent call last):
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_vendor/packaging/requirements.py", line 102, in __init__
    req = REQUIREMENT.parseString(requirement_string)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_vendor/pyparsing/util.py", line 256, in _inner
    return fn(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_vendor/pyparsing/core.py", line 1190, in parse_string
    raise exc.with_traceback(None)
pipenv.patched.pip._vendor.pyparsing.exceptions.ParseException: Expected string_end, found '.'  (at char 19), (line:1, col:20)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_internal/req/constructors.py", line 367, in _parse_req_string
    req = get_requirement(req_as_string)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_internal/utils/packaging.py", line 45, in get_requirement
    return Requirement(req_string)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_vendor/packaging/requirements.py", line 104, in __init__
    raise InvalidRequirement(
pipenv.patched.pip._vendor.packaging.requirements.InvalidRequirement: Parse error at "'.*'": Expected string_end

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/bin/pipenv", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/cli/options.py", line 58, in main
    return super().main(*args, **kwargs, windows_expand_args=False)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/decorators.py", line 92, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/vendor/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/cli/command.py", line 209, in install
    do_install(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/routines/install.py", line 93, in do_install
    do_init(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/routines/install.py", line 624, in do_init
    do_update(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/routines/update.py", line 61, in do_update
    do_lock(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/routines/lock.py", line 66, in do_lock
    venv_resolve_deps(
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/resolver.py", line 899, in venv_resolve_deps
    return prepare_lockfile(
           ^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/locking.py", line 148, in prepare_lockfile
    lockfile_entry = get_locked_dep(project, dep, pipfile, current_entry)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/locking.py", line 131, in get_locked_dep
    lockfile_entry = clean_resolved_dep(project, dep, is_top_level, current_entry)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 277, in clean_resolved_dep
    potential_hashes = unearth_hashes_for_dep(project, dep)
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 189, in unearth_hashes_for_dep
    install_req, markers, _ = install_req_from_pipfile(dep["name"], dep)
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 1097, in install_req_from_pipfile
    install_req, _ = expansive_install_req_from_line(
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 996, in expansive_install_req_from_line
    parts = parse_req_from_line(pip_line, line_source)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_internal/req/constructors.py", line 395, in parse_req_from_line
    req: Optional[Requirement] = _parse_req_string(req_as_string)
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/patched/pip/_internal/req/constructors.py", line 381, in _parse_req_string
    raise InstallationError(msg)
pipenv.patched.pip._internal.exceptions.InstallationError: Invalid requirement: 'python-magic-bin0.4.*'

Steps to replicate
mkdir pipfile-bug
cd pipfile-bug
pipenv install --python 3.11

Add following to Pipfile
python-magic = "==0.4.*"
python-magic-bin = { version = "==0.4.*", markers="sys_platform == 'win32'" }

Install
pipenv shell
pipenv install

$ pipenv --support
Pipenv version: '2024.0.1'
Pipenv location: '/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv'
Python location: '/usr/local/Cellar/pipenv/2024.0.1/libexec/bin/python'
OS Name: 'posix'
User pip version: '24.0'
user Python installations found:
PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.12.3',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '23.5.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 23.5.0: Wed May  1 20:09:52 PDT '
                     '2024; root:xnu-10063.121.3~5/RELEASE_X86_64',
 'python_full_version': '3.12.3',
 'python_version': '3.12',
 'sys_platform': 'darwin'}

System environment variables:

__CFBundleIdentifier
PATH
SHELL
SECURITYSESSIONID
TERM
USER
COMMAND_MODE
TMPDIR
LaunchInstanceID
TERMINAL_EMULATOR
SSH_AUTH_SOCK
XPC_FLAGS
TERM_SESSION_ID
__CF_USER_TEXT_ENCODING
LOGNAME
LC_CTYPE
XPC_SERVICE_NAME
HOME
SHLVL
PWD
OLDPWD
PYENV_ROOT
PYENV_SHELL
ZSH
PAGER
LESS
LSCOLORS
LS_COLORS
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH
PIPENV_ACTIVE
VIRTUAL_ENV
VIRTUAL_ENV_PROMPT
PS1
_
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:

PIPENV_ACTIVE: 1

Debug–specific environment variables:

PATH: /Users/oliverfarren/.pyenv/versions/3.9.13/bin:/Users/oliverfarren/.pyenv/versions/3.6.0/bin:/Users/oliverfarren/.pyenv/versions/3.8.13/bin:/Users/oliverfarren/.pyenv/versions/3.11.1/bin:/Users/oliverfarren/.pyenv/versions/3.7.13/bin:/Users/oliverfarren/.pyenv/versions/3.6.15/bin:/Users/oliverfarren/.pyenv/versions/3.10.4/bin:/Users/oliverfarren/.pyenv/versions/3.8.5/bin:/Users/oliverfarren/.pyenv/versions/3.11.4/bin:/Users/oliverfarren/.pyenv/versions/3.8.10/bin:/Users/oliverfarren/.pyenv/versions/3.8.16/bin:/Users/oliverfarren/.pyenv/versions/3.7.16/bin:/Users/oliverfarren/.local/share/virtualenvs/pipfile-bug-h7gOS49K/bin:/Users/oliverfarren/.pyenv/shims:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/TeX/texbin
SHELL: /bin/zsh
PWD: /Users/oliverfarren/Documents/repos/pipfile-bug
VIRTUAL_ENV: /Users/oliverfarren/.local/share/virtualenvs/pipfile-bug-h7gOS49K

Contents of Pipfile ('/Users/oliverfarren/Documents/repos/pipfile-bug/Pipfile'):
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
python-magic = "==0.4.*"
python-magic-bin = { version = "==0.4.*", markers="sys_platform == 'win32'" }

[dev-packages]

[requires]
python_version = "3.11"
python_full_version = "3.11.1"

Contents of Pipfile.lock ('/Users/oliverfarren/Documents/repos/pipfile-bug/Pipfile.lock'):
{
    "_meta": {
        "hash": {
            "sha256": "da18a2f144044fef4c7f2fe1352f85c1dbfdc6a81298c726b067991b9a9df141"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_full_version": "3.11.1",
            "python_version": "3.11"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {},
    "develop": {}
}

@OliverFarren could you re-check with latest pipenv?   I was not able to reproduce this one ...
matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv-triage
$ cd issue-6231

matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv-triage/issue-6231
$ pipenv install --python 3.11
Creating a virtualenv for this project
Pipfile: C:\Users\matte\Projects\pipenv-triage\issue-6231\Pipfile
Using C:/Users/matte/.pyenv/pyenv-win/versions/3.11.5/python.exe3.11.5 to create virtualenv...
created virtual environment CPython3.[==  ] 11.5Creating virtual environment....final.0-64 in 3543ms
  creator CPython3Windows(dest=C:\c\users\matte\.virtualenvs\issue-6231-PydLobCd, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=C:\Users\matte\AppData\Local\pypa\virtualenv)
    added seed packages: pip==24.2, setuptools==73.0.1, wheel==0.44.0
  activators BashActivator,BatchActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

Successfully created virtual environment!
Virtualenv location: C:\c\Users\matte\.virtualenvs\issue-6231-PydLobCd
Creating a Pipfile for this project...
Pipfile.lock not found, creating...
Locking [packages] dependencies...
Locking [dev-packages] dependencies...
Updated Pipfile.lock (ace7e9784a57c9841694abb0b34b2c60c71c5820bbe44603aad915ceb02cba3b)!
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
Installing dependencies from Pipfile.lock (2cba3b)...

matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv-triage/issue-6231
$ vim Pipfile

matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv-triage/issue-6231
$ pipenv shell
Launching subshell in virtual environment...
bash: /c/Users/matte/appdata/Local/Packages/PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0/LocalCache/local-packages/Python310/Scripts/virtualenvwrapper.sh: No such file or directory

matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv-triage/issue-6231
$ pipenv  install
Pipfile.lock (2cba3b) out of date: run `pipenv lock` to update to (e0502f)...
Running $ pipenv lock then $ pipenv sync.
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
Success!
Locking [dev-packages] dependencies...
Updated Pipfile.lock (82e322fddcfda772b9a1f273761c0338e140911a70716500e7ae3fc83ae0502f)!
Installing dependencies from Pipfile.lock (e0502f)...
All dependencies are now up-to-date!
Installing dependencies from Pipfile.lock (e0502f)...

matte@LAPTOP-N5VSGIBD MINGW64 ~/Projects/pipenv-triage/issue-6231
$ pipenv run pip freeze
python-magic==0.4.27
python-magic-bin==0.4.14

## Analysis of Pipenv Issue #6231

**1. Problem Summary:**

The issue describes a problem in Pipenv's parsing of package specifiers within the Pipfile when a versioning scheme (like "==0.4.*") and platform-specific markers are used together. This leads to an `InstallationError` during the locking process due to the version specifier being incorrectly stripped away and the package name being concatenated with the partial version string.

**2. Comment Analysis:**

* The maintainer's comment provides a log output showing that Pipenv successfully recognizes the platform-specific marker and skips the dependency as expected.
* However, the error still occurs during the locking process, indicating a problem in how the package specifier is processed.

**3. Proposed Resolution:**

The problem is likely caused by the order of operations when handling the `version` and `markers` keys within the `python-magic-bin` package definition. Here's a breakdown of the likely scenario:

1. **Version Parsing:** Pipenv initially parses the `version` key, encountering the "==0.4.*" scheme. It correctly interprets this as a wildcard version, potentially replacing it with "*".
2. **Marker Handling:**  Next, the `markers` key is processed. However, at this stage, the `version` key may have already been modified, leading to an incomplete package specifier.
3. **Requirement Construction:** During the construction of the `InstallRequirement` object, the incomplete specifier "python-magic-bin0.4.*" (without the "==") is used, resulting in the `InvalidRequirement` error.

To resolve this, Pipenv should handle the `version` and `markers` keys **simultaneously**, ensuring that the full package specifier, including the version scheme and markers, is used during `InstallRequirement` construction.

**4. Code Snippet (pipenv/utils/dependencies.py):**

```python
def install_req_from_pipfile(name, pipfile):
    # ... (Existing Code) ...

    # Combine version and markers before constructing the requirement string
    version = pipfile.get("version", "").replace("==", "")
    markers = pipfile.get("markers", "")
    req_str = f"{name}{extras_str}{version}{markers}"

    install_req, _ = expansive_install_req_from_line(
        req_str,
        # ... (Existing Arguments) ...
    )

    # ... (Rest of the code) ...
```

**5. Additional Steps:**

* **Unit Tests:**  Introduce test cases specifically targeting the combination of versioning schemes and platform-specific markers to prevent regressions.
* **Investigate Underlying Parser:** It's worth investigating if the PyParsing library used for requirement parsing could handle this situation more gracefully, potentially by preserving the original version specifier even when wildcards are used.
* **Improve Error Messages:** The current error message is cryptic. Improve it to clearly indicate the source of the error, mentioning the missing "==" operator.

This fix should ensure that Pipenv correctly parses and processes package definitions with both versioning schemes and platform-specific markers, leading to a more robust locking process.

@OliverFarren When you get a chance, could you check this issue report against https://github.com/pypa/pipenv/pull/6276
Its a larger Pr than just this issue, but since I put a ton of work into refactoring the install routine methods and ensuring we actually don't do full lock resolution when installing packages, but I included a possible refactor based on the above analysis re-run through Claude, so its possible it won't work, too.   The larger refactor was done by me, the human.

@OliverFarren When you get a chance, could you check this issue report against #6276
Its a larger Pr than just this issue, but since I put a ton of work into refactoring the install routine methods and ensuring we actually don't do full lock resolution when installing packages, but I included a possible refactor based on the above analysis re-run through Claude, so its possible it won't work, too. The larger refactor was done by me, the human.

Hey @matteius I had a look at the PR and it possibly addresses this issue? Looking at the verbose output stack trace above
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 1097, in install_req_from_pipfile
    install_req, _ = expansive_install_req_from_line(
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2024.0.1/libexec/lib/python3.12/site-packages/pipenv/utils/dependencies.py", line 996, in expansive_install_req_from_line
    parts = parse_req_from_line(pip_line, line_source)

I can this addition of the PR may be a positive change:
https://github.com/pypa/pipenv/blob/c16303083a020773ac94cf9a6ad8325704a8e82b/pipenv/utils/dependencies.py#L1135-L1138
Once the PR is merged and there's a new release, happy to update and try and reproduce


[Nox.Ui] Cryptocash.Ui Implement Infrastructure.Security.ApplicationIdentity config settings

as agreed in 16/Aug/23 meeting ad config for the following:
AzureAuth = Infrastructure.Security.ApplicationIdentity
infrastructure:
  security:
    userIdentity:
      provider: AzureAd
      azureAdOptions:
        instance: https://login.microsoftonline.com
        domain: xxx
        tenantId: xxx (vault secret)
        clientId: xxx (vault secret)
        callBackPath: /signin-oidc
        signedOutCallBackPath: /signout-callback-oidc

job1: update Nox.Solution support & validate settings - see NoxSimpleTypeDefinition = expects instance, domain etc - validation

Covered in https://regusit.atlassian.net/browse/NOX-157


CUDA kernel failed : invalid device function

Hey,
Really good job with the implementation!
I am running into the following error when I try to use your implementation of the FlowNet3D:
CUDA kernel failed : invalid device function

Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

It does not show the line the error is raised.
Which CUDA version are you using? I am using 10.1

I went followed the forward pass step by step in debug mode, I found the that problem comes from this line:
https://github.com/hyangwinter/flownet3d_pytorch/blob/051ead641270e76008119ecc4937f898b9118897/lib/pointnet2_utils.py#L28
Any ideas of what could cause the problem?

Hi,
My CUDA version is 10.0. The problem looks like the extension is not compiled properly. I found several pages for you that might cause this error:
https://stackoverflow.com/questions/28451859/cuda-invalid-device-function-how-to-know-architecture-code
https://stackoverflow.com/questions/17599189/what-is-the-purpose-of-using-multiple-arch-flags-in-nvidias-nvcc-compiler
But in fact, BuildExtension in setuptools will determine the arch flags according to the model of the GPU. The GPU I use is RTX 2080 Ti, so the output when I compile is as follows:
/usr/local/cuda/bin/nvcc -I/root/anaconda3/lib/python3.6/site-packages/torch/include -I/root/anaconda3/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -I/root/anaconda3/lib/python3.6/site-packages/torch/include/TH -I/root/anaconda3/lib/python3.6/site-packages/torch/include/THC -I/usr/local/cuda/include -I/root/anaconda3/include/python3.6m -c src/sampling_gpu.cu -o build/temp.linux-x86_64-3.6/src/sampling_gpu.o -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr --compiler-options '-fPIC' -O2 -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_EXTENSION_NAME=pointnet2_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -gencode=arch=compute_75,code=sm_75 -std=c++11

You can check whether -gencode=arch matches your GPU or downgrade CUDA version to 10.0.
Hope these are helpful to you, beat wishes 😃

Thanks =)
I am not very skilled myself in CUDA, how can I check that? I did not find anything online that I could use.

This page shows the relationship between GPUs and their compute capability. For example, my RTX 2080 Ti compute capability is 7.5, so the parameter of arch and code is compute_75 and sm_75 respectively.

Hey,
Really good job with the implementation!
I am running into the following error when I try to use your implementation of the FlowNet3D:
CUDA kernel failed : invalid device function
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
It does not show the line the error is raised.
Which CUDA version are you using? I am using 10.1

This page shows the relationship between GPUs and their compute capability. For example, my RTX 2080 Ti compute capability is 7.5, so the parameter of arch and code is compute_75 and sm_75 respectively.

I encountered the same problem.
My GPU is RTX 2080 Ti  and the CUDA version is 10.1. When I run the install command in setup.py and try to start training, the following error appears:
CUDA kernel failed : invalid device function
Segmentation fault (core dumped)

It seems that mismatched NVCC vs CUDA Runtime version is the root cause.
Please refer to this issue for more information:
https://github.com/facebookresearch/detectron2/issues/62#issuecomment-542447753


Tests

Write tests that can be executed automatically to ensure correctness (also integration tests)

Just merged a PR implementing auto. unit tests in Jenkins. Integration tests will follow.


Preserve policy is on by default

Rather than offering preserve_policy as an option, the service broker will be updated so that this is on by default and there is no option to delete policy when a service instance is deprovisioned.
Open questions:

What happens when multiple service instances are provisioned in a space with preserve_policy on?
TBD other open questions from XA

Tasks

[ ] Code updated to remove policy preservation option
[ ] Tests updated
[ ] README updated
[ ] Tile updated to remove form option
[ ] Docs updated


List.getItems() is not a function

Hello experts! I am currently writing a test that should allow to validate the number of items that a list can have. However, I am encountering the error "List.getItems is not a function", which is strange to me, since the selector is perfectly capable of finding the list.
This is my test

These are the results of the 'List' variable, so you can see that the domId was found

This is my output

I also tried with 'getAggregation("items")', but it returns 0, which can't be feasible since it seems to return the correct value when I get the 'StandardListItem'.

My team and I started using wdi5 very recently, so we are still learning. I look forward to your comments!
Thank you in advance.

the selector is perfectly capable of finding the list.

try adding interaction: "root" to the selector:
selector: {
   interaction: "root",
   controlType: "sap.m.List",
  // …
}

this property stems from the OPA5 matchers we‘re using and is a well know trap 🪤 😄
documentation for this is upcoming in #285

That seems to have worked out perfectly! Thank you very much for resolving my questions so quickly.
I will keep an eye out for further updates and will follow your advice.
Best regards!


Ignore disabled checks passed to -XepPatchChecks

Rather than throwing an NoSuchElementException.
Fixes #3908.

@oxkitsune these PRs are generally merged with the PR text as commit message, so I would also add this sentence to the PR body (just like in the commit message):

That's already the case right? It should be good like it is right now.

I would swear that my browser didn't show it. But I must have been confused. :thinking:

Thanks for this fix!
I finally did some internal testing of this, and one thing I encountered is that this changes of behaviour of things like -Xep:DeadException:WARN -XepPatchChecks:GetClassOnClass--previously refactorings weren't emitted for DeadException even though it was explicitly enabled, because it wasn't listed in -XepPatchChecks. With this change refactorings are emitted for DeadException.
Do you have thoughts on what the least surprising behaviour here would be?

Do you have thoughts on what the least surprising behaviour here would be?

Personally I think it would make the most sense, if checks passed to -Xep:PatchChecks are the only checks emitting patches, unless they're explicitly disabled.

Do you have thoughts on what the least surprising behaviour here would be?

Personally I think it would make the most sense, if checks passed to -Xep:PatchChecks are the only checks emitting patches, unless they're explicitly disabled.
E.g.
-Xep:DeadException:WARN -XepPatchChecks:GetClassOnClass

would emit patches for GetClassOnClass, and warnings for DeadException.
-Xep:DeadException:OFF -XepPatchChecks:GetClassOnClass,DeadException

would emit just patches for GetClassOnClass

That sounds good to me.
I think that there isn't an order that applyOverrides and filter can be called in that does quite what we want here: calling applyOverrides first causes #3908, and calling filter first causes refactorings to be emitted for checks that are explicitly enabled with -Xep: flags.
I wonder if it makes sense of -XepPatchChecks to just override any -Xep:...:[OFF|WARN|ERROR] flags. That would mean that we went back to the pre-2.19 behaviour where refactorings were emitted for -Xep:CheckName:OFF -XepPatchChecks:CheckName. Would that work for you?

I wonder if it makes sense of -XepPatchChecks to just override any -Xep:...:[OFF|WARN|ERROR] flags. That would mean that we went back to the pre-2.19 behaviour where refactorings were emitted for -Xep:CheckName:OFF -XepPatchChecks:CheckName. Would that work for you?

I'll need to find some time later to think this through more thoroughly, but I wonder whether we'll regret that if #947 is ever merged (still hoping :wink:): then -XepPatchChecks: (without further args) would enable patching for all checks, and realistically users will want to apply some exclusions.
That said, we have the #947 change in our fork, and right now we do have this "patch all except those that are OFF" behavior, with a baseline more recent than 2.19.
Easiest is perhaps to first add a few more tests, and then assess impact on #947.

I'll need to find some time later to think this through more thoroughly

My too, I think :)
The existing logic only calls filter if !namedCheckers.isEmpty(), if we keep that part and do the rest of what I described, I think that would interact well with #947
i.e. something like:
                  ScannerSupplier toUse = ErrorPronePlugins.loadPlugins(scannerSupplier, context);
                  ImmutableSet<String> namedCheckers = epOptions.patchingOptions().namedCheckers();
                  if (!namedCheckers.isEmpty()) {
                    toUse = toUse.filter(bci -> namedCheckers.contains(bci.canonicalName()));
                  } else {
                    toUse = toUse.applyOverrides(epOptions);
                  }
                  return ErrorProneScannerTransformer.create(toUse.get());

Rebased this branch to include the changes of #947 (diff applied cleanly; thanks for merging @cushon!), which should make it marginally easier to reason about the solution space. (Actual reasoning still TBD :sweat_smile:)

Hey @cushon apologies for the inactivity :sweat_smile:
I've just applied the suggestions and I'm happy with this solution!

Hey @cushon apologies for the inactivity 😅 I've just applied the suggestions and I'm happy with this solution!

No worries, thanks for coming back to this!


feat: allow overriding data file with CLI arguments

Description
Users should be able to pass CLI data arguments and use a --data-file at the same time.  Let's just take inspiration from the helm values file and give highest priority to data values passed at the command line.
from the helm doc site:

The list above is in order of specificity: values.yaml is the default, which can be overridden by a parent chart's values.yaml, which can in turn be overridden by a user-supplied values file, which can in turn be overridden by --set parameters.

@yajo I'm a little confused about the coverage failure, it looks like codecov is stating this PR reduces test coverage on other test files (ref)?  Would love some clarification or help here.

https://github.com/copier-org/copier/pull/1332#issuecomment-1728329806: Some upload error on codecov: https://github.com/copier-org/copier/actions/runs/6251262443/job/16972001045?pr=1332#step:12:51
Gotta check that.

I updated the token, hoping (not much) it fixes codecov uploads forever.

@yajo/@sisp still not quite sure what to do about these codecov errors;  can you provide any guidance? Given that the "dropped" coverage seems to occur other test files, would you be OK admin merging this one without the codecov/project task passing?

@yajo the rebase fixed this;  should be all set for a final review!


In production mix.version() not updating app.js hash

Environment:

Laravel Mix version: 2.1.11
Node Version: 8.7.0
NPM version: 5.6.0
OS: OSX High Sierra 10.13.3
Laravel Installer 1.5.0
Laravel Framework 5.6.16

Description:
On a fresh install, when I run npm run production, mix will not update the hash on app.js. The hash that is written appears not to change even though the file being compiled has changed.
Steps to Reproduce:

Install new Laravel project
Install Composer dependencies
Install Node Modules
npm run production to create initial mix-manifest
Add "In production" version conditional to webpack.mix.js
	if (mix.inProduction()) { mix.version(); }
Edit resources/scss/app.scss THEN npm run production

RESULT: The css hash in mix-manifest updates as expected

Edit resources/js/app.js THEN npm run production

RESULT: The js hash does not change

Could not reproduce.
Are you making significant changes in app.js ?

@ankurk91 No, the changes were not extensive. Sample app js:
require('./bootstrap');

window.Vue = require('vue');

Vue.component('example-component', require('./components/ExampleComponent.vue'));

const app = new Vue({
    el: '#app'
});

var test='test';
var test2='test';
var test3='testing';
var testFuncton = function(){
	console.log('Test function');
}

It appears that the simple variables/functions I add at the bottom of the file do not trigger a hash update.
HOWEVER, I did notice that if I put them in a separate file and imported them (e.g. import './test.js'), it triggered a hash change.
Also, if I remove the Vue component or comment out the app const, the hash gets updated.

 Maybe it strips  and ignores?

From what I gather it doesn't do webpack style hashing on JS files declared in your mix file when running npm run prod. Instead, it'll add an ?id= for each recognized asset in the mix file in the manifest.json. When using the mix() blade function, it'll take the file within the argument and find the respective entry in the manifest and then use that entry as the asset file.
If you you really want to add your own webpack style hashing on your JS, you will have to override the webpack config entry point to use [name].[yourhashofchoice].js

@ikudosi Thanks for your feedback. I'm going to close the issue as it's not really affecting me at the moment, and it doesn't seem like anyone else has noticed it.

I have this problem too. Is this all right now?

@heimuya My solution was to move notable changes to external files.


Add Terrain CopyRegion method

We compile our maps including our terrain to a model file using TerrainRegion instances. It would be great to be able to generate that TerrainRegion through our remodel script. We also need Terrain.MaxExtents for it to work.
Thank you :)

I don't know how hard this can be but I can give it a try!


FIX: Solving the issue of the default subset name appearing when expo…

…rting a task

Motivation and context

How has this been tested?

Checklist

[X] I submit my changes into the develop branch
[ ] I have added a description of my changes into the CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[X] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Issue : https://github.com/opencv/cvat/issues/6451

@kirill-sizov
Thank you! I've resolved the conflicts.
While this PR works, it might not be perfect. I kindly ask the main contributors to review it in line with the intention of my changes and hope for its integration.

@kirill-sizov Thank you. I've modified the code according to your guide comments. Please check.

@kirill-sizov Thank you. I've modified the code according to your guide comments. Please check.

Resolved in #8176


Add retries when writing to net.Conn

Retry with exponential back-off when writing to the network fails.  The
initial delay time is 100ms.
Capture write errors when sending the close performative.
Fixed up some misbehaving tests that were uncovered due to the above
changes.
Updated Go version to 1.13 as there are some features used that first
appeared in that version.

For context on the Go 1.13 bump, there are places in the code base (e.g. buffer.go) that intentionally shift right too much.

@jhendrixMSFT This draft was mostly committed in other PRs.  Should this be closed?

Not yet.

Based on our discussion, this is not required.


feat: png data -> pixel data

[x] issue #8
[x] follows contribution guide
[ ] code change includes tests
[ ] breaking change

Hey, I wanted to get this done a couple days ago, but got pulled into a few things.
I wanted to write tests but I'm not sure where to do it, so I tested it manually with curl and an 8x1 image.
Let me know if this is what was indeed expected :)

Hey @thomas192 , wil you be able to address the comment soon? If not, no worries, I can just merge what you have so far and have someone else work on that part.

Hey @thomas192 , wil you be able to address the comment soon? If not, no worries, I can just merge what you have so far and have someone else work on that part.

Hello Brandon, sorry my attention is elsewhere at the moment. I should have let you know.

Hi @b-j-roberts can you please assign me to work on this.

Hi @b-j-roberts I can handle this

Hello Brandon, sorry my attention is elsewhere at the moment. I should have let you know.

No worries. I can assign the rest to someone else and will reward you for the work here after it's merged.


Update documentation

Clean up code (and mostly comments) in ranker_obj (and rename to ranking per Kenny's request).
Looking to remove dead code (and clean live code) in this PR too but I don't know enough to know what can be removed.

While we're in here cleaning things up, what say we add Black like we have in the other repos. This code is definitely not Black.

Yeah you're absolutely right. No colors anymore.


Nuking 'Help'

I propose we nuke the Query Reference for WorkBench and Roam panel. (or redirect it to https://github.com/dvargas92495/roamjs-workbench) @dvargas92495

Most of the basics are covered with Roam Help
Now that users can set their own keyboard shortcuts, static shortcuts that are displayed won't match
Many links are outdated, 404, etc

Anytime we start a sentence with "I propose we nuke...", Im already 90% of the way on board.
In this case, the remaining 10% checks out too. This panel was first created before Roam built out their help menu, do Im down to get rid of it


Support Locust v1.0.x

Locust seems to have released new version with v1.0.x . It would be great to have this supported here. Example would be like
FROM python:3.8.1-alpine3.11

COPY docker-entrypoint.sh /

RUN    apk --no-cache add --virtual=.build-dep build-base git \
    && apk --no-cache add zeromq-dev libffi-dev \
    && python3 -m pip install --no-cache-dir<EMAIL_ADDRESS>\
    && apk del .build-dep \
    && chmod +x /docker-entrypoint.sh \
    && mkdir /locust
WORKDIR /locust
EXPOSE 8089 5557 5558

ENTRYPOINT ["/docker-entrypoint.sh"]

@youngkih Sorry, for the late answer. Would you consider creating a PR?

@youngkih Sorry, for the late answer. Would you consider creating a PR?

Hi @karol-brejna-i , sure, but seems like i don't have the access to push my change
locust-1.0.3 ✔ $ git push origin locust-1.0.3
ERROR: Permission to karol-brejna-i/docker-locust.git denied to youngkih.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Could you grant access to create PR for this change?

@youngkih the usual workflow would look like this:

You fork the repo
You make a dedicated branch (on the forked repo)
You make desired changes
You commit the changes (after validating if the image works, adding it to examples, etc.)
You create a pull request

Then I would be able to accept and merge the PR.
Please, go ahead and try. It's a bit of work, but on the other hand -- it would be your Open Source contribution!

@youngkih the usual workflow would look like this:

You fork the repo
You make a dedicated branch (on the forked repo)
You make desired changes
You commit the changes (after validating if the image works, adding it to examples, etc.)
You create a pull request

Then I would be able to accept and merge the PR.
Please, go ahead and try. It's a bit of work, but on the other hand -- it would be your Open Source contribution!

@karol-brejna-i Thanks for the detailed instruction! Would love to try it out, will let you know when i open a PR 🙏

@karol-brejna-i I've opened https://github.com/karol-brejna-i/docker-locust/pull/16, please help take a look. I'll close this issue, let's keep track of this update with the PR


How CAS server identify differency domain name

Hi dev CASino team,
This gem so helpful, after setup. My app is work fine. However, i don't know how it work when when can't share cookie, local Storage, session Storage cross a domain.
Example I have 2 web side with 2 domain is abc.com and xyz.com . I have CAS server have domain like account.abc.com.
step 1: I sign in to abc.com side, it direct me to account.abc.com
step 2: i put username and password. server verify true.
step 3: abc.com side: receive server ticket verify true and  make me sign in success in abc.com site.
when side xyz.com sign in, my server xyz.com automatic verify with account.abc.com server and make me login.
So, problem here. how account.abc.com  identify xyz.com side. what and where info browser save

Please help. I take a lot of time for this. and this talk very important.

@flameA : You can debug the casino gem to understand the whole process of ticket generation and ticket verification. May be this will help you sso casino blog.
Cheers

I'm not sure if I understood your usecase excatly but it sounds like you want to automatically login a user after a completed sign up in an application independent from CASino.
You may have a look at Auth-Token-Login, it works for me in several projects like a charm.

Not sure why OP went silent after even pinging me on Twitter.


Property "url" in structure "default" is required but no value was given.

I wanted to change a page from external link to default content page. I think the error occurs because the tab for content is missing.

Happens also when the page was an internal link

It's also a duplicate of #1674, which is tagged to version 1.2, should that be solve before? However, the fix suggested there, is probably not too easy to implement.

@danrot 1.2 or Hotfix.

Fact is, that when a client want to change a page from external or internal link to a standard content page, he gets an error. I solved it by deleting the page and create a new one


[onTurnError] unhandled error: TypeError: Cannot read property 'map' of undefined

Hi team,
i am using one of the bot framework sample where "qnamaker-all-features(https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs/49.qnamaker-all-features) enabled code is available in node js.
Most of the time i am trying see what would be the fix for this issue every time persisting : -  [onTurnError] unhandled error: TypeError: Cannot read property 'map' of undefined which leads for error and bot is responding like :-

please do suggest me on this or either provide me the solutions ASAP.

@Bradrajkumar - Thank you for the report. You might be interested in this issue: https://github.com/microsoft/BotBuilder-Samples/issues/2417
Is there any chance you've included quotes in your .env file?

@Bradrajkumar - Are you still working on this?

I am closing this issue due to inactivity. We are still happy to provide help if you need any, though it may be a good idea to make a new post if that's the case. Please have a look at this to find out the best places to ask for help, and consider asking questions on Stack Overflow.

I am also having this issue and I have checked the .env file, there is no quotes. I am not sure what I am missing, this is happening for both QnA samples

I am also having this issue and I have checked the .env file, there is no quotes. I am not sure what I am missing, this is happening for both QnA samples


Update build.gradle

commons-collections is no longer used in this project, previously it was only used for a null check in FallbackMethod.java

Thanks @Psynbiotik !


[Paddle]Add chapter_natural-language-processing-applications

hi, @cheungdaven

it seems the error is timeout:
A cell timed out while it was being executed, after 1200 seconds.

can you adjust timeout 1200 seconds to longer, maybe 40minutes, the paddlepaddle's multigpu doesn't support jupyter notebooks, it's friendly to python scripts,  there are:
# 单机多卡启动，默认使用当前可见的所有卡
$ python -m paddle.distributed.launch train.py

# 单机多卡启动，设置当前使用的第0号和第1号卡
$ python -m paddle.distributed.launch --selected_gpus='0,1' train.py

or
# 使用方式1：仅传入训练函数
# 适用场景：训练函数不需要任何参数，并且需要使用所有当前可见的GPU设备并行训练
if __name__ == '__main__':
    dist.spawn(train)

the docs is https://www.paddlepaddle.org.cn/documentation/docs/zh/guides/model_convert/update_cn.html#danjiduokaqidong
but the second way is multiprocessing, it seems that the jupyter doesn't work well on a multiprocessing way, I got some errors on my local machine

Hi @w5688414. To ensure the notebook be user-friendly and easy to compile, we cannot extend the timeout limit.  Maybe you can try different solutions ? (like reduce the training iterations, we a lower accuracy is expected.)

@d2l-bot please rebuild

@cheungdaven hello， could you review it again? thanks!!!

LGTM @tngt @w5688414 , thank you for the contribution.


[Tokyo Mirage Sessions ♯FE] Static FPS doesn't support the Japanese game

Graphic breaks when resolution is increased with latest version 1.15.4
There is no problem with 1.15.3

Static60FPS does not work well in Japanese version
This is good if it is possible, but can you cope?

As of http://cemu.info/patreon/changelog/cemu_1_15_5.txt, the graphical bugs are fixed. Changed the title to reflect your other problem.
Could you please send us a screenshot of the View RPL Modules window in Cemu's Debug toolbar?

Screen shot
Thank you

Please.
Is it difficult to handle static 60 FPS?

Sorry, was away for a few days.
The 60FPS patch is for the unpatched EU version only. Since I don't own the game, I'm not sure what the difference/meaning is of the "uncensored" thing.

I am an unpatched JP version
It was known from the folder name that only the EU version is currently supported, but I thought it would be nice if I could get it compatible with the JP version.


Pin PyYAML 6.0.1 to get around https://github.com/yaml/pyyaml/issues/601

https://phabricator.wikimedia.org/T342144

neat!

This works because of the yaml/pyyaml#702 workaround (which forces a dependency on Cython < 3.0) that was pulled into the pyyaml 6.0.1 release. yaml/pyyaml#731 is touted as a better fix (not requiring Cython < 3.0) for yaml/pyyaml#601 (and yaml/pyyaml#728 if it gets backported to a 5.x branch).


Add PoH armour case items

I noticed that the armour case wasn't included, so I've added all of the items that can be stored in it.

Any updates on this? It would be really nice to have the armour case items added to the plugin

Closes #39


Unhandled rejection Error: 400

Hello!
I have been trying to get snoowrap working with my project. My package.json for snoowrap looks like "snoowrap": "^1.21.0",.
I have tried with setting up with a script app, installed app, and web app.
Oauth setup
I call to a URL that looks like https://www.reddit.com/api/v1/authorize?client_id=${redditAPI.clientId}&response_type=code&state=randomString&redirect_uri=https://google.com&duration=permanent&scope=identity,history,read,edit
I get the url param code that gets attached to https://google.com.
I then set up snoowrap like so:
redditClient = new Snoowrap({
  userAgent: redditAPI.userAgent,
  clientId: redditAPI.clientId,
  clientSecret: "",
  refreshToken: oauthCode
});

And I get Unhandled rejection Error: 400:

I also tried with a web app that has a client secret:
redditClient = new Snoowrap({
  userAgent: redditAPI.userAgent,
  clientId: redditAPI.clientId,
  clientSecret: redditAPI.clientSecret,
  refreshToken: oauthCode
});

And get the same result.
Script log in
I tried with a script app as well by doing:
redditClient = new Snoowrap({
  userAgent: "test",
  clientId: "CLIENT_ID",
  clientSecret: "CLIENT_SECRET",
  username: "USERNAME",
  password: "PASSWORD"
});

and I get bluebird.js?f684:1581 Unhandled rejection Error: "Invalid grant" error returned from reddit. (You might have incorrect credentials.):

No actually oauth code is not the refresh token, it's used to get the refresh token, you have to use this to get the requester after getting the code:
var r = await snoowrap.fromAuthCode({
   code: code,
   clientId: config.clientId,
   clientSecret: '',
   redirectUri:  config.redirectUri
})

Then just save the refresh token from r.refreshToken to use it in future without having to login again.
PS: on browser, you don't have to pass the userAgent at new snoowrap().

No actually oauth code is not the refresh token, it's used to get the refresh token, you have to use this to get the requester after getting the code:
var r = await snoowrap.fromAuthCode({
   code: code,
   clientId: config.clientId,
   clientSecret: '',
   redirectUri:  config.redirectUri
})

@iMrDJAi  why there isn't anything about this function in the documentation?

why there isn't anything about this function in the documentation?

See https://not-an-aardvark.github.io/snoowrap/snoowrap.html#.fromAuthCode__anchor


how to remove  empty option from drop down.

Hi , I want to remove empty option from json:from which is created through below json
{
"type": "object",
"required": ["editors_used"],
"properties": {
"editors_used": {
"type": "array",
"title": "What editors do you use?",
"minItems": 1,
"items": {
"type": "string",
"enum": [
"vim", "emacs", "sublime", "kate"
],"default":"vim"
},
"additionalItems": false
}
}
}

What do you mean? You require 1 item in order to be valid, what empty option are you talking about?

I need a gist of what you are doing to be able to help, this doesn't provide enough information for me to support your issue.
The example demo has a "Save to Gist" button you can use to create one from a schema and form definition.


CLI not using ?result=true API option

in action.go: func (s *ActionService) Invoke(actionName string, payload interface{}, blocking bool) (*Activation, *http.Response, error) { suggests the CLI is doing a blocking invoke and projecting the result later. Is this intended vs using the additional ?result=true option - @dubeejw?

@dubeejw thoughts?


Deployment Failing After Upgrade to 0.36.8 due to CDK Bootstrap

Describe the bug
Using version 0.35.4, I'm able to deploy an ASP.NET Core web application to Amazon ECS using Fargate successfully.
Upon upgrade to 0.36.8, I'm no longer able to deploy the same app to a new deployment using the same profile, region, and settings.
Logs
Generating AWS Cloud Development Kit (AWS CDK) deployment project
Deploying AWS CDK project
 ⏳  Bootstrapping environment aws://{{redacted}}/us-east-1...
 ✅  Environment aws://{{redacted}}/us-east-1 bootstrapped (no changes).

current credentials could not be used to assume 'arn:aws:iam::{{redacted}}:role/cdk-hnb659fds-lookup-role-{{redacted}}-us-east-1', but are for the right account. Proceeding anyway.

✨  Synthesis time: 61.29s

ASPNetWebApp1: deploying...
current credentials could not be used to assume 'arn:aws:iam::{{redacted}}:role/cdk-hnb659fds-deploy-role-{{redacted}}-us-east-1', but are for the right account. Proceeding anyway.

 ❌  ASPNetWebApp1 failed: Error: ASPNetWebApp1: SSM parameter /cdk-bootstrap/hnb659fds/version not found. Has the environment been bootstrapped? Please run 'cdk bootstrap' (see https://docs.aws.amazon.com/cdk/latest/guide/bootstrapping.html)
    at CloudFormationDeployments.validateBootstrapStackVersion (C:\Users\shovlia\.aws-dotnet-deploy\node_modules\aws-cdk\lib\api\cloudformation-deployments.ts:521:13)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
ASPNetWebApp1: SSM parameter /cdk-bootstrap/hnb659fds/version not found. Has the environment been bootstrapped? Please run 'cdk bootstrap' (see https://docs.aws.amazon.com/cdk/latest/guide/bootstrapping.html)

A CloudFormation stack was not created. Check the deployment output for more details.

Expected behavior
Per https://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/deployment-tool-setup-env.html, the deploy tool is supposed to use a temporary/private CDK installation, and I believe it does attempt to bootstrap CDK here: https://github.com/aws/aws-dotnet-deploy/blob/ad20940dc567aa7228245488e3f5506e3df49681/src/AWS.Deploy.Orchestration/CdkProjectHandler.cs#L83
I have this version installed locally:
> cdk --version
1.91.0 (build 0f728ce)

I suspect that with the upgrade to CDK V2 in 0.36.8, it's failing to bootstrap V2 correctly.
Environment (please complete the following information):

CLI Version: [eg. 1.0.0]  0.36.8
Include the output of dotnet --info

> dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.201
 Commit:    ef40e6aa06

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.19042
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.201\

Host (useful for support):
  Version: 6.0.3
  Commit:  c24d9a9c91

Additional context
Add any other context about the problem here.

This is a :bug: bug report

Believe this is addressed by https://github.com/aws/aws-dotnet-deploy/pull/480

The fix is out for this bug.


iOS cocoapods versions

I'm trying to run pod install, and I'm getting the following error. Any help?
[!] CocoaPods could not find compatible versions for pod "GoogleMLKit/MLKitCore":
  In Podfile:
    RNMLKitFaceDetection (from `../node_modules/@react-native-ml-kit/face-detection`) was resolved to 1.1.1, which depends on
      GoogleMLKit/FaceDetection (= 2.6.0) was resolved to 2.6.0, which depends on
        GoogleMLKit/MLKitCore (= 2.6.0)

    RNMLKitTextRecognition (from `../node_modules/@react-native-ml-kit/text-recognition`) was resolved to 1.1.1, which depends on
      GoogleMLKit/TextRecognition (= 2.2.0) was resolved to 2.2.0, which depends on
        GoogleMLKit/MLKitCore (= 2.2.0)

I tried that and can't find it. Maybe because your ios version is 9?

Make sure you have the latest version of @react-native-ml-kit/text-recognition (currently it's 1.2.0 and the error says you're using 1.1.1).

Thank you again! Sorry for the issue

Hey! guys I'm facing this issue when in pod install or pod update
can anyone help me how it resolve.
using OS: 13.0
react-native: 0.63.4
"react-native-text-recognition": "^1.0.0",

[!] CocoaPods could not find compatible versions for pod "react-native-text-recognition":
In Podfile:
react-native-text-recognition (from ../node_modules/react-native-text-recognition)

Specs satisfying the react-native-text-recognition (from ../node_modules/react-native-text-recognition) dependency were found, but they required a higher minimum deployment target.


[Bug]: Loaded ESM module can't refer to mapped imports from package.json:{imports...}

Version
29.0.3
Steps to reproduce

Clone the gist https://gist.github.com/danfuzz/42911f598060bc255c1421ca27a616cf.
Run the script do-test from the gist. (It will install Jest locally, create a src directory that has the structure that I found to be problematic, and then run Jest on the test in that directory.)

Expected behavior
I expected to see the test run.
Actual behavior
The following output:
 FAIL  tests/Thing.test.js
  ● Test suite failed to run

    Cannot find module '#x/Thing' from 'index.js'

      at Resolver._throwModNotFoundError (../jest/node_modules/jest-resolve/build/resolver.js:487:11)
          at async Promise.all (index 0)
          at async Promise.all (index 0)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.17 s
Ran all test suites matching /Thing/i.

Additional context
I believe what's going on is that, somehow, when Jest loads (or causes to be loaded) an ESM module due to an import in a test file, the imports binding from the loaded module's package.json is being ignored. For reference, here's what's in it for this example:
{
  "imports": {
    "#x/*": "./export/*.js",
    "#p/*": "./private/*.js"
  }
}

(I don't think the #p binding is necessary for reproduction; I thought it might be handy to pre-emptively answer the question of what the bigger intention is with this arrangement.)
Environment
System:
    OS: macOS 12.4
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 18.7.0 - /opt/homebrew/bin/node
    npm: 8.15.0 - /opt/homebrew/bin/npm

Duplicate of #12270

Thanks for the quick response! Apologies, I failed to find the existing issue when I tried to search for similar bugs.


Run dbmigrate jobs in the same way as upload-assets jobs.

Argo is still sometimes failing syncs by trying to change the (immutable) Job objects for the dbmigrate jobs. Change them to run in the same way as the upload-assets jobs, which don't seem to have this problem.
This makes the dbmigrate job run as a presync hook, whereas previously it just ran as part of the main sync. I think presync is probably somewhat preferable since the failure mode when the job fails is both safer (because it holds up the rollout) and more visible (because it holds up the rollout!)
As a bonus, we get to ditch a bunch of somewhat complicated guff from
the Helm chart.
Example of a sync getting stuck with the previous config:
one or more synchronization tasks completed unsuccessfully, reason:
error when replacing "/dev/shm/761223060":
Job.batch "signon-dbmigrate-0-1-4-37f8bf3" is invalid:
[spec.selector:
Required value, spec.template.metadata.labels:
Invalid value:
map[string]string{"app.kubernetes.io/component":"web", "app.kubernetes.io/instance":"signon", "app.kubernetes.io/managed-by":"Helm", "app.kubernetes.io/name":"signon", "helm.sh/chart":"signon-0.1.4"}:
`selector` does not match template `labels`, spec.selector:
Invalid value:
"null":
field is immutable, spec.template:
Invalid value:
core.PodTemplateSpec{ObjectMeta:v1.ObjectMeta{Name:"signon-dbmigrate-0-1-4-37f8bf3", ...}}
field is immutable]. Retrying attempt #2 at 3:17PM.

I dunno if there was a reason we made these not be presync hooks in the first place? I'm hoping it was just a stab in the dark workaround from before we figured out how to get these to work reliably, and/or when we were running buggy versions of Argo.

Huh, not sure why this wasn't PreSync in the first place - we'd want migrations to run before the new application version is deployed. But good catch, hopefully there isn't a hidden reason why we didn't do this originally.


Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
yes i added a new song and character

Not a bug, you messed something up

Error details?


does Multithreaded Reads support? how to read fast ?

i use parquet-dotnet to read big parquet file, but it seems little slow. read all rowgroups pyarrow take 14 seconds, but parquet-dotnet take 42 seconds.
`        private void ReadParquet(string file)
{
//遍历读取所有rowgroup   c# 42秒    python_pyarrow 14秒
        using (var reader = ParquetReader.OpenFromFile(file))
        {
            //var schema = reader.Schema;
            var dataFields = reader.Schema.GetDataFields();
            var cnt = reader.RowGroupCount;

            for (var i = 0; i < cnt; i++)
            {
                using (var groupReader = reader.OpenRowGroupReader(i))
                {
                    var columns = dataFields.Select(groupReader.ReadColumn);

                    foreach(var column in columns)
                    //Parallel.ForEach(columns, column =>
                    {
                        var data = column.Data;
                    }
                    //);

                    //foreach (DataField field in reader.Schema.GetDataFields())
                    //{
                    //    var dataColumn = groupReader.ReadColumn(field);
                    //}
                }
            }
        }

    }`

https://arrow.apache.org/docs/python/parquet.html
Multithreaded Reads
Each of the reading functions by default use multi-threading for reading columns in parallel. Depending on the speed of IO and how expensive it is to decode the columns in a particular file (particularly with GZIP compression), this can yield significantly higher data throughput.

I did my own multi-thread implementation by splitting the fields into groups so I had one group per CPU core.
Example: If your parquet file has 48 fields and you have a 12 thread CPU (E.g. 6 cores with hyper threading), you would have 12 groups with 4 fields each.
And then I run a ParallelAsync.ForEachAsync to start one thread per group. Each thread then has its own ParquetReader that it uses to read the same file in parallel.
    List<string> fieldsToLoad = ...
    var fieldGroups = new List<(int, List<string>)>();
foreach (List<string> fields in UtilityMethods.Split(fieldsToLoad, (int)(fieldsToLoad.Count / Environment.ProcessorCount)))
{
	fieldGroups.Add((i++, fields));
}

task = ParallelAsync.ForeachAsync(fieldGroups, Environment.ProcessorCount,
	async fieldGroup =>
	{
		await Task.Run(() =>
		{
			using (Stream parquetStream = new FileStream(this.OpenFilePath, FileMode.Open, FileAccess.Read))
			using (var parquetReader = new ParquetReader(parquetStream, new ParquetOptions() { TreatByteArrayAsString = true }))
			{
				DataTable result = UtilityMethods.ParquetReaderToDataTable(parquetReader, fieldGroup.Item2, this.CurrentOffset, this.CurrentMaxRowCount, cancellationToken.Token);
				//Do whatever you want with the data now.
			}
		});
	});

while (!task.IsCompleted && !((BackgroundWorker)sender).CancellationPending)
{
	task.Wait(1000);
}


Add expressions inside queries

Jira issue: https://jira.hyperledger.org/browse/IR-1028
Signed-off-by: i1i1<EMAIL_ADDRESS>

Description of the Change

Benefits

Possible Drawbacks

Usage Examples or Tests [optional]

Alternate Designs [optional]

@i1i1 I didn't find any motivation - can you share a link to RFC or a Jira issue?

@humb1t added to pr description


Add error logs for jetty

Part of https://github.com/wso2/product-is/issues/14087
Fixing below logs:
[2022-07-07 11:04:49,220] []  WARN {org.eclipse.jetty.util.ssl.SslContextFactory.config} - Trusting all certificates configured for Client@35cfb0c2[provider=null,keyStore=null,trustStore=file:///Users/piraveena/Documents/wso2is-6.0.0-alpha2/repository/resources/security/client-truststore.jks]
[2022-07-07 11:04:49,220] []  WARN {org.eclipse.jetty.util.ssl.SslContextFactory.config} - No Client EndPointIdentificationAlgorithm configured for Client@35cfb0c2[provider=null,keyStore=null,trustStore=file:///Users/piraveena/Documents/wso2is-6.0.0-alpha2/repository/resources/security/client-truststore.jks]
[2022-07-07 11:04:49,345] []  WARN {org.eclipse.jetty.util.ssl.SslContextFactory.config} - Trusting all certificates configured for Client@67585101[provider=null,keyStore=null,trustStore=file:///Users/piraveena/Documents/wso2is-6.0.0-alpha2/repository/resources/security/client-truststore.jks]
[2022-07-07 11:04:49,346] []  WARN {org.eclipse.jetty.util.ssl.SslContextFactory.config} - No Client EndPointIdentificationAlgorithm configured for Client@67585101[provider=null,keyStore=null,trustStore=file:///Users/piraveena/Documents/wso2is-6.0.0-alpha2/repository/resources/security/client-truststore.jks]

This logs are printed when solrclient get initialised with registry indexing https://github.com/wso2/carbon-registry/blob/v4.8.7/components/registry/org.wso2.carbon.registry.indexing/src/main/java/org/wso2/carbon/registry/indexing/solr/SolrClient.java#L143. Hiding these logs since registry indexing are not used in IS

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2717937638

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2717937638
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2722508326

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2722508326
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2723792055

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2723792452

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2723792452
Status: success

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2723792055
Status: success


CAMPD About Page- 508 issue

Context
Testing for 1819 complete. 1 issue found, heading levels skip from H2 (release notes) to H4 for each of the expandable items. Suggest changing H4 to H3

All visual headings are now tagged with html heading tags the the heirarchy is logical, closing ticket


Detection status known issues

[x] :exclamation: storeing to a server outside local machine DOES NOT WORK. :exclamation: #830

The ZIP is assembled in a way that the plist files and the metadata.json still contains the local path, such as /home/username/project/main.cpp, which does NOT exist on the remote server, as files are unpacked to some temporary directory.

[12:56:29] [29586] <140389142992640> - plist_parser.py:132 parse_plist() - Parsing plist: /tmp/tmp7LlvMP/reports/main.cpp_ea274a983107bcd3ad4c1f6c69a3656a.plist
[12:56:29] [29586] <140389142992640> - report.py:90 generate_report_hash() - Failed to generate report hash.
[12:56:29] [29586] <140389142992640> - report.py:91 generate_report_hash() - /home/username/project/main.cpp does not exists!

  File "/home/somebody/dstest/CodeChecker/lib/python2.7/libcodechecker/server/client_db_access_handler.py", line 1503, in massStoreRun
    file_ids[file_name] = file_path_to_id[file_name]
KeyError: '/home/username/project/main.cpp'

[x] store prints Success to the user even if storing failed. #828
[x] The suppressions in the file content are currently not stored.
[x] CodeChecker store command needs to be given a report directory which is created by CodeChecker analyze command, i.e. the format of its content is important: it should contain the plist files and the metadata.json. CodeChecker store should work if the provided report directory contains only plist files. Moreover this command should also work with only one or more plist files given.
[x] Storage crashes if a plist file contains a source file path which is not stored in the database and not sent in the .zip file.
[x] A test case should check whether a reopened or unresolved bug is shown with the latest version of the given source code.

Can we close this? Everything is fixed? @bruntib @dkrupp

#859 is still pending as a PR.

We can close this now. #859 was merged.


Responsive design page in Figma, as Octopos Prime product service

Description:
This will be the page where we serve the octopos prime product, which is clearly being drawn by the design team. For this reason, a responsive design is required for this page.
Loom Link:
https://www.loom.com/share/43ded882eac047ddbb4df416ef7075bf
Figma Link:
https://www.figma.com/design/hnvVfV2xzpcPW1ZkybkDxe/OctopOSPrime-web-site?node-id=105%3A38&t=XO1kkfrlpsucLaFq-1

We decided to move another way.


Missing RELEASE_3_10 branch

There seems to be a problem with code.bioconductor.org: release 3.10 seems missing and it is not possible to reach it via url such as https://code.bioconductor.org/browse/ReactomePA/blob/RELEASE_3_10/DESCRIPTION (but it works for RELEASE_3_9  and RELEASE_3_11). The error I see is : Oops!fatal: Path '0/DESCRIPTION' does not exist in 'RELEASE_3_1'

Originally posted by @llrs
https://community-bioc.slack.com/archives/CLF37V6C8/p1657624818724169

This was fixed some time ago when the site was moved to a new kubernetes instances and all the packages were cloned again.


Deprecate or remove magic -1 stretchy size

units.Pct(100) should be used instead. That is much clearer and conveys what it is supposed to do (take up as much as 100% of the surrounding container). -1 doesn't mean anything and is very unclear. Unfortunately, units.Pct(100) does not seem to fully work now, so the computation of percentages may need to be fixed.

Also, the default size of elements should be the size of their content (just like the default values for width and height are auto in CSS). This will remove the need for setting a stretchy max size in almost all cases.

This has been removed with the new Grow based layout structure.


Remove recaptcha detected error

I need the recaptcha html page, can you remove the "RuntimeError: Cloudflare reCaptcha detected, unfortunately you haven't loaded an anti reCaptcha provider correctly via the 'recaptcha' parameter." ?

rgr i'll see what i can do for you

Release 1.1.29 should sort you out refer to https://github.com/VeNoMouS/cloudscraper#return_response


Please fix it.

When I run the 'clear' Unix command. The middle Display window does not change. Please fix it.

@JamesLinus
What do you mean by Middle Display Window?
Please provide more info or screenshots and try to make the title more descrptive than just Please fix it.. Something like, Problems with clearing upterm would be better.

If this issue has not been updated with more clarity, it should be closed 🙂

ok, lets close it


Add class for inline icons

A simple class for nicely-aligned inline icons.
I don't think this should really go into utilities, but because the individual packages may be deprecated soon (#48) I just put it here to avoid making whole new package.

@tysongach I agree that this could probably be broken into two more general components. Perhaps a row component and an icon component. Despite my comments about flexbox earlier ☝, I think combining the two to create inline icons is the more atomic approach.


[FLINK-11867]Mistaking in checking filePath's value

What is the purpose of the change
		Preconditions.checkNotNull(filePath, "The file path must not be null."); 		Preconditions.checkNotNull(filePath.isEmpty(), "The file path must not be empty.");
The second line of code has no effect
Brief change log

Changing the to check the filePath's value and the hint

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no, restore state when failover using RestartPipelinedRegionStrategy.
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

@Tom-Goong this PR is almost LGTM now except the title. Actually this is not the build system component. If hard to distinguish which part of this PR belongs to, you could just remove the build system component.
By the way, if no need to rebase master branch, not to use force push to update PR.

@Myasuka thanks。 Title of the PR and component of related Jira have modefied.
It seems that I need to be more flexible.

Thanks @Tom-Goong for your contribution and @Myasuka for review.
LGTM, merging.


Is it recommended to use Vac bypass loader while using Osiris? Or is Osiris from the source code, compiled everyday before playing enough?

Better use VAC Bypass


Change donut title (Interior text) dynamically with chart loads

Is there a way to make the title inside the donut chart change to the sum of all the data values, updating automatically with every data load into the chart?

You can use this to change the title dynamically.
d3.select('#div_id .c3-chart-arcs-title').node().innerHTML = "new title";
where div_id is the id of the div to which your chart is bounded.
you may have to write the logic to calculate some on your own

and how can we change font and color dynamically?

I was able to do it following vishal-kony's advice. However it will be better if c3 library provides a chart for this. Something like
chart.updateTitle('donut','new title');

Any update?


update documentation

[ ] add detailed tool description in each process block
[ ] add help and other docs outlined here

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Make visualizing forc log output pretty

Right now log data is pretty visually hard to parse with Forc.
It would be nice to simplify this or have a simplified view or option available

For this program (as an exampe):
script;

fn log_b256(value: b256) {
    asm(r1: value, r2: 32) {
        logd zero zero r1 r2;
    }
}

fn main() {
    let k:b256 = 0xef86afa9696cf0dc6385e2c407a6e159a1103cefb7e2ae0636fb33d3cb2a9e4a;

    log_b256(k);
}

The forc run return looks like this:
[LogData { id:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000, ra: 0, rb: 0, ptr: 10472, len: 32, digest: be240c408b034a8f3e67813d85c05d5379e02c17d4012440a4bf73450aa8935d, data: [239, 134, 175, 169, 105, 108, 240, 220, 99, 133, 226, 196, 7, 166, 225, 89, 161, 16, 60, 239, 183, 226, 174, 6, 54, 251, 51, 211, 203, 42, 158, 74], pc: 10416, is: 10352 }, Return { id:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000, val: 0, pc: 10420, is: 10352 }, ScriptResult { result: InstructionResult { reason: RESERV00, instruction: Instruction { op: 0, ra: 0, rb: 0, rc: 0, rd: 0, imm06: 0, imm12: 0, imm18: 0, imm24: 0 } }, gas_used: 424 }]

Could look like this:
Logs Returned by Execution:

LogData:
    Register A: 0
    Register B: 0
    Data: 0xef86afa9696cf0dc6385e2c407a6e159a1103cefb7e2ae0636fb33d3cb2a9e4a

Having some kind of easy to parse clean version would be nice. If I want all the other program details I could just maybe flag an option for it.

To clarify a little bit, forc run needs to return in a more human-readable format. Does this include prunings of the fields in the output? (If so which fields will be staying?) or we are going to just format and keep every field?

Ah right. id and digest are also hashes and so should also be displayed in hex. I'm not sure either about which approach is best. cc @Voxelot for help on what the client emits.

Looking at the receipt.rs I think the following fields should be converted into hex in the output:

All id fields
All to fields
All asset_id fields
All digest fields
All data fields

I converted these fields to hex in the default output and added a flag --verbose to keep printing as we do now to address the following part:

If I want all the other program details I could just maybe flag an option for it.

Currently, I am not happy with the code quality of my implementation of the formatting section and now working on refactoring that part. Current outputs with different flags are as the following:

cargo run --bin forc -- run --path my_test

{"LogData":{"data":"ef86afa9696cf0dc6385e2c407a6e159a1103cefb7e2ae0636fb33d3cb2a9e4a","digest":"be240c408b034a8f3e67813d85c05d5379e02c17d4012440a4bf73450aa8935d","id":"0000000000000000000000000000000000000000000000000000000000000000","is":10352,"len":32,"pc":10416,"ptr":10488,"ra":0,"rb":0}}
{"Return":{"id":"0000000000000000000000000000000000000000000000000000000000000000","is":10352,"pc":10424,"val":0}}
{"ScriptResult":{"gas_used":435,"result":"Success"}}

cargo run --bin forc -- run --path my_test --pretty-print

{
  "LogData": {
    "data": "ef86afa9696cf0dc6385e2c407a6e159a1103cefb7e2ae0636fb33d3cb2a9e4a",
    "digest": "be240c408b034a8f3e67813d85c05d5379e02c17d4012440a4bf73450aa8935d",
    "id": "0000000000000000000000000000000000000000000000000000000000000000",
    "is": 10352,
    "len": 32,
    "pc": 10416,
    "ptr": 10488,
    "ra": 0,
    "rb": 0
  }
}
{
  "Return": {
    "id": "0000000000000000000000000000000000000000000000000000000000000000",
    "is": 10352,
    "pc": 10424,
    "val": 0
  }
}
{
  "ScriptResult": {
    "gas_used": 435,
    "result": "Success"
  }
}

cargo run --bin forc -- run --path my_test --verbose

[LogData { id:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000, ra: 0, rb: 0, ptr: 10488, len: 32, digest: be240c408b034a8f3e67813d85c05d5379e02c17d4012440a4bf73450aa8935d, data: [239, 134, 175, 169, 105, 108, 240, 220, 99, 133, 226, 196, 7, 166, 225, 89, 161, 16, 60, 239, 183, 226, 174, 6, 54, 251, 51, 211, 203, 42, 158, 74], pc: 10416, is: 10352 }, Return { id:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000000, val: 0, pc: 10424, is: 10352 }, ScriptResult { result: Success, gas_used: 435 }]

cargo run --bin forc -- run --path my_test --verbose --pretty-print

[
    LogData {
        id: 0x0000000000000000000000000000000000000000000000000000000000000000,
        ra: 0,
        rb: 0,
        ptr: 10488,
        len: 32,
        digest: 0xbe240c408b034a8f3e67813d85c05d5379e02c17d4012440a4bf73450aa8935d,
        data: [
            239,
            134,
            175,
            169,
            105,
            108,
            240,
            220,
            99,
            133,
            226,
            196,
            7,
            166,
            225,
            89,
            161,
            16,
            60,
            239,
            183,
            226,
            174,
            6,
            54,
            251,
            51,
            211,
            203,
            42,
            158,
            74,
        ],
        pc: 10416,
        is: 10352,
    },
    Return {
        id: 0x0000000000000000000000000000000000000000000000000000000000000000,
        val: 0,
        pc: 10424,
        is: 10352,
    },
    ScriptResult {
        result: Success,
        gas_used: 435,
    },
]

Although the data field started to look better, serde_json converts other fields (such as digest and id) into a more verbose version. I can do the same formatting I am doing for the data field to those fields as well.

Currently, I went ahead with the mentioned approach but depending on any input from @Voxelot, I can implement this differently. Also not sure about whether we want to keep the --verbose flag.

While we can make various enhancements to upstream crates to improve the rendering here and there, I think there's a good argument for forc to have its own log rendering system that has complete control over the format it outputs to users. For example, what may be a good way to serialize types for an API (JSON) may not be the most friendly format for CLI usage.
That said, I can't think of a case where we'd want to serialize a b256 as an [int], which is the default behavior. I almost all areas of our stack would be simplified if we made a custom serialize/deserialize impl for key! types that used hex serialization.
https://github.com/FuelLabs/fuel-types/blob/master/src/types.rs#L30

logged an issue here: https://github.com/FuelLabs/fuel-types/issues/31

How hard would it be to implement hex serialization in fuel-types? If not to hard, then maybe it's better to just change it there once.

Pretty simple, it's a good first issue if someone wants to pick it up.
However, without its own receipt printing adapter, forc would never be able to customize the output enough to end up with what Nick originally posted.
Logs Returned by Execution:

LogData:
    Register A: 0
    Register B: 0
    Data: 0xef86afa9696cf0dc6385e2c407a6e159a1103cefb7e2ae0636fb33d3cb2a9e4a

Okay that extra formatting isn't really needed at this time. The only important thing is hex-formatting hashes and indenting the JSON.

@kayagokalp do you think you could tackle https://github.com/FuelLabs/fuel-types/issues/31 as a prerequisite to resolving this issue, instead of manually choosing specific fields to hex-format as per your current approach?

Yep, getting started to work on that one 👍

Related #884, w.r.t. more flexibility around logging in general.

This doesn't look like a serialization problem. We might cause some long-term trouble if we custom the base type to serve some specific display use.
It looks to me that we need to implement a customized Display to these types, without touching sensible aspects such as serialization. That way, we have absolute freedom to manipulate the format as we wish, without ever having to worry with any potential side-effects that might be caused when we interfere with serialization strategies.
If we really want to stick to the strategy of customizing the serde serialization, we need to use custom with attributes. For reference: serde-hex
Serde, by design, will force us to perform the undesirable update of the raw types in order to affect its consumers. This alternative, however, is less worse, because we still use proc macros and will (likely) still be compatible with future version upgrades.
cc @kayagokalp

This was primarily motivated by the fact that whenever people want to JSON serialize fuel-types, they use the serde_json adaptor. The ABI specifies that the receipts should be JSON serializable, and that they should use hex encoding for all the byte arrays and numeric types:
https://github.com/FuelLabs/fuel-specs/blob/master/specs/protocol/abi.md#panic-receipt
Relying only on the Display trait for rendering these types will make it very difficult for downstream consumers of these types to serialize them to JSON in a usable way. Leading to many wrappers or new types and other clunky workarounds.
The downside is, hex string serialization is not the most efficient serialization format in all use-cases (esp db storage in fuel-core for example). However, the alternative is customizing our own version of serde_json to follow our formatting conventions and then educating users to use our custom adapter instead.
To me, it seems like simplifying the most common serialization usecases that users will most frequently encounter and then working around that in places like db storage is preferable to adhering to strict principles that inconvenience users.

Put another way, here are all the places we would use serde with our types:

GraphQL API JSON
JSON chainspec configuration
Logging
Database storage

3/4 cases, which are all the user-facing ones, we would want to serialize receipts according to the ABI spec. The only case where we wouldn't want serde_json to match the ABI spec is in the database, which is non-user facing and where we can internally optimize as needed.

After these comments, I feel like we should continue with custom hex serialization implementation but just to work around this issue we can always go down the Display or Debug path too.

had a chat with the client team and @vlopes11 agreed that we can go ahead and make serde the defacto serialization method for pretty user-facing stuff, since for networking we'll likely use protobufs and on the db we can use something else like borsch or just manually serialize these types optimally for the db ourselves.

@kayagokalp you might already be aware of this, but just in case:
Keep in mind that if we do need to format just one particular field in a way that differs from the default serialization, that serde provides nice ways of allowing custom field serialization/deserialization even if that type has an existing Serialize/Deserialize implementation that differs to what we want.
There are some great docs on how to achieve this here.

@mitchmindtree , thanks for the tip! Currently the default serialization of key! types are merged (fuel-types#34 and released. Once an update to the fuel-tx is ready (which switches fuel-types to v0.5.0 and possibly adds a serialize(with..) annotation to Vec<u8> fields (data)) we will be able to use it directly. But I wasn't aware of this and it seems super helpful.

This is unblocked after https://github.com/FuelLabs/sway/pull/1683, opening up the PR 🎉