2023.8.19 through to 2023.8.22 break editable package installation

Issue description
Editable package installation appears to be broken from pipenv 2023.8.19 onwards.
For example, given a package in the directory test-hello under the pipenv root installing the package with pipenv install -e ./test-hello fails.
Expected result
pipenv 2023.7.23 and prior versions would install editable packages in Pipfile and in the venv.
Actual result
Here's a log of package installation across recent versions of pipenv.
try_pipenv_versions.log
For example:
+ pipx install pipenv==2023.8.19
creating virtual environment...
installing pipenv from spec 'pipenv==2023.8.19'...
done! ✨ 🌟 ✨
  installed package pipenv 2023.8.19, installed using Python 3.8.10
  These apps are now globally available
    - pipenv
    - pipenv-resolver
+ git clean -dfx
Removing .venv/
Removing applications/test-hello/test_hello.egg-info/
Removing test-hello/test_hello.egg-info/
+ echo '=== Using pipenv version 2023.8.19 ==='
=== Using pipenv version 2023.8.19 ===
+ pipenv sync
Creating a virtualenv for this project...
Pipfile: /home/stewart/src/pipenv_editable_install_repro/Pipfile
Using /usr/bin/python3.8 (3.8.10) to create virtualenv...
created virtual environment CPython3.8.10.final.0-64 in 48ms
  creator CPython3Posix(dest=/home/stewart/src/pipenv_editable_install_repro/.venv, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/stewart/.local/share/virtualenv)
    added seed packages: pip==23.2.1, setuptools==68.0.0, wheel==0.41.1
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

✔ Successfully created virtual environment!
Virtualenv location: /home/stewart/src/pipenv_editable_install_repro/.venv
Installing dependencies from Pipfile.lock (db4242)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
All dependencies are now up-to-date!
+ install_test_and_uninstall_package ./test-hello
+ path=./test-hello
+ pipenv run pipenv install -e ./test-hello
Installing -e ./test-hello...
Resolving -e ./test-hello...
Error: Traceback (most recent call last):
  File "/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/routines/install.py", line
279, in do_install
    added, cat, normalized_name = project.add_package_to_pipfile(
  File "/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/project.py", line 1159, in
add_package_to_pipfile
    name, normalized_name, entry = self.generate_package_pipfile_entry(
  File "/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/project.py", line 1110, in
generate_package_pipfile_entry
    req_name = determine_package_name(package)
  File "/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/utils/dependencies.py", line
745, in determine_package_name
    raise ValueError(f"Could not determine package name from {package}")
ValueError: Could not determine package name from
file:///file:///home/stewart/src/pipenv_editable_install_repro/test-hello

✘ Failed adding package to Pipfile
✔ Installation Succeeded

It's also interesting that installation fails, due to the mangled URI that starts with file:///file:///, but the final message is that installation succeeded.
Steps to replicate
https://github.com/stewartmiles/pipenv_editable_install_repro contains a minimal test environment.
I generated the log file using:
git clone https://github.com/stewartmiles/pipenv_editable_install_repro
cd pipenv_editable_install_repro
./try_pipenv_versions.sh 2>&1 | tee ../try_pipenv_versions.log

Please run $ pipenv --support, and paste the results here. Don't put backticks (`) around it! The output already contains Markdown formatting.
$ pipenv --support
Pipenv version: '2023.8.22'
Pipenv location: '/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv'
Python location: '/home/stewart/.local/pipx/venvs/pipenv/bin/python'
OS Name: 'posix'
User pip version: '23.2.1'
user Python installations found:
PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.8.10',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '5.15.0-69-generic',
 'platform_system': 'Linux',
 'platform_version': '#76~20.04.1-Ubuntu SMP Mon Mar 20 15:54:19 UTC 2023',
 'python_full_version': '3.8.10',
 'python_version': '3.8',
 'sys_platform': 'linux'}

System environment variables:

SHELL
PIPENV_VENV_IN_PROJECT
TERMCAP
SSH_AUTH_SOCK
WINDOW
SSH_AGENT_PID
PWD
LOGNAME
XDG_SESSION_TYPE
MOTD_SHOWN
HOME
LANG
LS_COLORS
SSH_CONNECTION
LESSCLOSE
XDG_SESSION_CLASS
TERM
LESSOPEN
USER
XLA_FLAGS
SHLVL
XDG_SESSION_ID
KUBECONFIG
LD_LIBRARY_PATH
XDG_RUNTIME_DIR
SSH_CLIENT
XDG_DATA_DIRS
PATH
STY
DBUS_SESSION_BUS_ADDRESS
SSH_TTY
USE_GKE_GCLOUD_AUTH_PLUGIN
OLDPWD
_
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PYTHONFINDER_IGNORE_UNSUPPORTED

Pipenv–specific environment variables:

PIPENV_VENV_IN_PROJECT: true

Debug–specific environment variables:

PATH: ~/.local/bin:/home/stewart/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
SHELL: /bin/bash
LANG: en_US.UTF-8
PWD: /home/stewart/src/pipenv_editable_install_repro

Contents of Pipfile ('/home/stewart/src/pipenv_editable_install_repro/Pipfile'):
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]

[dev-packages]

[requires]
python_version = "3.8"

Contents of Pipfile.lock ('/home/stewart/src/pipenv_editable_install_repro/Pipfile.lock'):
{
    "_meta": {
        "hash": {
            "sha256": "7f7606f08e0544d8d012ef4d097dabdd6df6843a28793eb6551245d4b2db4242"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.8"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {},
    "develop": {}
}

Same here, I am working in Amplify and had to specify pipenv==2023.7.23 in amplify.yml to make Amplify build work, otherwise (without specifying the version) it will raise 'Failed to install dependencies in ... Error: Command failed with exit code 1: pipenv install)'

Same issue here. Also breaking for pipenv install "git+...".

@lewiswolf I believe that is a separate issue, there are a couple reports about the git+ vcs issue and an open PR that some have reported fix it.
Regarding  this actual issue report, I think part of the problem (maybe not the whole problem) is the ast parser logic for the old setup.py file logic is not accounting for all cases.   I tried to correct for that some locally over lunch in the reproduction link (super helpful by the way) and was able to get it to install for the top level test-hello, but when I try the one in the applications sub-dir, I get a pathing issue.
I'll be able to cut a release going  into late evening for the PR I have open, but I am not sure I have an immediate fix for what's going on with editable file installs in this issue report.

So I opened https://github.com/pypa/pipenv/pull/5861 which I did some testing on windows and linux and it appears to be past this issue, but what I noticed is on windows it will lock a relative path fine, but on linux in this branch its adding the full path to the Pipfile, and then locking that.  🤔
test-hello = {file = "file:/home/matteius/pipenv_editable_install_repro/applications/test-hello", editable=true}

Good news (I think) -- this branch works for your reproduction examples that I tried on Windows and the changes are still passing the existing pipenv tests.  Please have a look and help me verify if it resolves the issues or if there is still something to address regarding local file installs:  https://github.com/pypa/pipenv/pull/5870

pipenv install -e . still breaking for me on macOS 13.5 (python 3.10.13)
lewiswolf:~/Desktop/kac_drumset pipenv install -e .
Installing -e ....
Resolving -e ....
Added kac-drumset to Pipfile's [packages] ...
✔ Installation Succeeded
Pipfile.lock (1d3b75) out of date, updating to (f23ac9)...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✘ Locking Failed!
⠏ Locking...
INFO:pipenv.patched.pip._internal.operations.prepare:Obtaining file:///Users/lewiswolstanholme/Desktop/kac_drumset (from -r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 6))
INFO:pipenv.patched.pip._internal.cli.spinners:Installing build dependencies: started
INFO:pipenv.patched.pip._internal.cli.spinners:Installing build dependencies: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Checking if build backend supports build_editable: started
INFO:pipenv.patched.pip._internal.cli.spinners:Checking if build backend supports build_editable: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Getting requirements to build wheel: started
INFO:pipenv.patched.pip._internal.cli.spinners:Getting requirements to build wheel: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Preparing metadata (pyproject.toml): started
INFO:pipenv.patched.pip._internal.cli.spinners:Preparing metadata (pyproject.toml): finished with status 'done'
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting torch>=2.0 (from -r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 3))
INFO:pipenv.patched.pip._internal.network.download:Downloading torch-2.0.1-cp310-none-macosx_10_9_x86_64.whl (143.4 MB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting opencv-python>=4.7 (from -r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 8))
INFO:pipenv.patched.pip._internal.operations.prepare:Obtaining dependency information for opencv-python>=4.7 from https://files.pythonhosted.org/packages/8a/6f/8aa049b66bcba8b5a4dc872ecfdbcd8603a96704b070fde22222e479c3d7/opencv_python-<IP_ADDRESS>-cp37-abi3-macosx_10_16_x86_64.whl.metadata
INFO:pipenv.patched.pip._internal.network.download:Downloading opencv_python-<IP_ADDRESS>-cp37-abi3-macosx_10_16_x86_64.whl.metadata (19 kB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting soundfile (from -r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 4))
INFO:pipenv.patched.pip._internal.network.download:Downloading soundfile-0.12.1-py2.py3-none-macosx_10_9_x86_64.whl (1.2 MB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting tqdm>=4.65 (from -r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 5))
INFO:pipenv.patched.pip._internal.operations.prepare:Obtaining dependency information for tqdm>=4.65 from https://files.pythonhosted.org/packages/00/e5/f12a80907d0884e6dff9c16d0c0114d81b8cd07dc3ae54c5e962cc83037e/tqdm-4.66.1-py3-none-any.whl.metadata
INFO:pipenv.patched.pip._internal.network.download:Downloading tqdm-4.66.1-py3-none-any.whl.metadata (57 kB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting torchaudio>=2.0 (from -r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 2))
INFO:pipenv.patched.pip._internal.network.download:Downloading torchaudio-2.0.2-cp310-cp310-macosx_10_9_x86_64.whl (3.9 MB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting numpy>=1.24 (from -r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 7))
INFO:pipenv.patched.pip._internal.operations.prepare:Obtaining dependency information for numpy>=1.24 from https://files.pythonhosted.org/packages/d5/50/8aedb5ff1460e7c8527af15c6326115009e7c270ec705487155b779ebabb/numpy-1.25.2-cp310-cp310-macosx_10_9_x86_64.whl.metadata
INFO:pipenv.patched.pip._internal.network.download:Downloading numpy-1.25.2-cp310-cp310-macosx_10_9_x86_64.whl.metadata (5.6 kB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting filelock (from torch>=2.0->-r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 3))
INFO:pipenv.patched.pip._internal.operations.prepare:Obtaining dependency information for filelock from https://files.pythonhosted.org/packages/00/45/ec3407adf6f6b5bf867a4462b2b0af27597a26bd3cd6e2534cb6ab029938/filelock-3.12.2-py3-none-any.whl.metadata
INFO:pipenv.patched.pip._internal.network.download:Downloading filelock-3.12.2-py3-none-any.whl.metadata (2.7 kB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting typing-extensions (from torch>=2.0->-r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 3))
INFO:pipenv.patched.pip._internal.operations.prepare:Obtaining dependency information for typing-extensions from https://files.pythonhosted.org/packages/ec/6b/63cc3df74987c36fe26157ee12e09e8f9db4de771e0f3404263117e75b95/typing_extensions-4.7.1-py3-none-any.whl.metadata
INFO:pipenv.patched.pip._internal.network.download:Downloading typing_extensions-4.7.1-py3-none-any.whl.metadata (3.1 kB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting sympy (from torch>=2.0->-r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 3))
INFO:pipenv.patched.pip._internal.network.download:Downloading sympy-1.12-py3-none-any.whl (5.7 MB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting networkx (from torch>=2.0->-r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 3))
INFO:pipenv.patched.pip._internal.network.download:Downloading networkx-3.1-py3-none-any.whl (2.1 MB)
INFO:pipenv.patched.pip._internal.operations.prepare:Collecting jinja2 (from torch>=2.0->-r /var/folders/6w/mgc4qy2n69b8cc1nszttrrsr0000gn/T/pipenv-dco_6cdm-requirements/pipenv-l_ay_6za-constraints.txt (line 3))
INFO:pipenv.patched.pip._internal.network.download:Downloading Jinja2-3.1.2-py3-none-any.whl (133 kB)
INFO:pipenv.patched.pip._internal.resolution.resolvelib.reporter:INFO: pip is looking at multiple versions of kac-drumset to determine which version is compatible with other requirements. This could take a while.
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Could not find a version that satisfies the requirement kac-drumsetfil (from kac-drumset) (from versions: none)
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/resolver.py", line 646, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/resolver.py", line 613, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve(
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/resolver.py", line 593, in resolve
[ResolutionFailure]:       return resolve_deps(
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/utils/resolver.py", line 845, in resolve_deps
[ResolutionFailure]:       results, hashes, internal_resolver = actually_resolve_deps(
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/utils/resolver.py", line 618, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/utils/resolver.py", line 444, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv run pip install <requirement_name> to bypass this mechanism, then run $ pipenv graph to inspect the versions actually installed in the virtualenv.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: No matching distribution found for kac-drumsetfil

Traceback (most recent call last):
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/bin/pipenv", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/vendor/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/cli/options.py", line 58, in main
    return super().main(*args, **kwargs, windows_expand_args=False)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/vendor/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/vendor/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/vendor/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/vendor/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/vendor/click/decorators.py", line 84, in new_func
    return ctx.invoke(f, obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/vendor/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/cli/command.py", line 209, in install
    do_install(
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/routines/install.py", line 297, in do_install
    raise e
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/routines/install.py", line 281, in do_install
    do_init(
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/routines/install.py", line 648, in do_init
    do_lock(
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/routines/lock.py", line 65, in do_lock
    venv_resolve_deps(
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/utils/resolver.py", line 786, in venv_resolve_deps
    c = resolve(cmd, st, project=project)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/Cellar/pipenv/2023.8.26/libexec/lib/python3.11/site-packages/pipenv/utils/resolver.py", line 655, in resolve
    raise RuntimeError("Failed to lock Pipfile.lock!")
RuntimeError: Failed to lock Pipfile.lock!

@matteius thanks for the patch. However, it looks like things still aren't working correctly.
Here's a log of a new test run with 2023.8.26:
try_pipenv_versions.log
Or even easier after cloning https://github.com/stewartmiles/pipenv_editable_install_repro:
pipenv sync && pipenv install -e ./test-hello

which errors out with:
Creating a virtualenv for this project...
Pipfile: /home/stewart/src/pipenv_editable_install_repro/Pipfile
Using /usr/bin/python3.8 (3.8.10) to create virtualenv...
⠋ Creating virtual environment...created virtual environment CPython3.8.10.final.0-64 in 51ms
  creator CPython3Posix(dest=/home/stewart/src/pipenv_editable_install_repro/.venv, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/stewart/.local/share/virtualenv)
    added seed packages: pip==23.2.1, setuptools==68.0.0, wheel==0.41.2
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

✔ Successfully created virtual environment!
Virtualenv location: /home/stewart/src/pipenv_editable_install_repro/.venv
Installing dependencies from Pipfile.lock (db4242)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
All dependencies are now up-to-date!
Installing -e ./test-hello...
Resolving -e ./test-hello...
⠋ Installing...Error: Traceback (most recent call last):
  File "/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/routines/install.py",
line 255, in do_install
    added, cat, normalized_name = project.add_package_to_pipfile(
  File "/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/project.py", line
1167, in add_package_to_pipfile
    name, normalized_name, entry = self.generate_package_pipfile_entry(
  File "/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/project.py", line
1114, in generate_package_pipfile_entry
    req_name = determine_package_name(package)
  File
"/home/stewart/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/utils/dependencies.py", line
744, in determine_package_name
    raise ValueError(f"Could not determine package name from {package}")
ValueError: Could not determine package name from
file:///home/stewart/src/pipenv_editable_install_repro/test-hello

✘ Failed adding package to Pipfile
✔ Installation Succeeded
Installing dependencies from Pipfile.lock (db4242)...
To activate this project's virtualenv, run pipenv shell.
  I tried both windows, and here is my ubuntu:
matteius@matteius-VirtualBox:~/pipenv_editable_install_repro$ pipenv install -e ./test-hello/
Creating a virtualenv for this project...
Pipfile: /home/matteius/pipenv_editable_install_repro/Pipfile
Using default python from /usr/bin/python (3.10.12) to create virtualenv...
⠼ Creating virtual environment...created virtual environment CPython3.10.12.final.0-64 in 337ms
  creator CPython3Posix(dest=/home/matteius/.virtualenvs/pipenv_editable_install_repro-3TYtUsNd, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/matteius/.local/share/virtualenv)
    added seed packages: pip==23.2.1, setuptools==68.0.0, wheel==0.41.2
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

✔ Successfully created virtual environment!
Virtualenv location: /home/matteius/.virtualenvs/pipenv_editable_install_repro-3TYtUsNd
Creating a Pipfile for this project...
Installing -e ./test-hello/...
Resolving -e ./test-hello/...
Added test-hello to Pipfile's [packages] ...
✔ Installation Succeeded
Pipfile.lock not found, creating...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✔ Success!
⠸ Locking...Warning: INFO:pipenv.patched.pip._internal.operations.prepare:Obtaining file:///home/matteius/pipenv_editable_install_repro/test-hello (from -r /tmp/pipenv-8i8n7f5s-requirements/pipenv-e9l02qrp-constraints.txt (line 2))
INFO:pipenv.patched.pip._internal.cli.spinners:Installing build dependencies: started
INFO:pipenv.patched.pip._internal.cli.spinners:Installing build dependencies: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Checking if build backend supports build_editable: started
INFO:pipenv.patched.pip._internal.cli.spinners:Checking if build backend supports build_editable: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Getting requirements to build wheel: started
INFO:pipenv.patched.pip._internal.cli.spinners:Getting requirements to build wheel: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Preparing metadata (pyproject.toml): started
INFO:pipenv.patched.pip._internal.cli.spinners:Preparing metadata (pyproject.toml): finished with status 'done'
Locking [dev-packages] dependencies...
Updated Pipfile.lock (a528f480c44a1940d1f9897c854058593109192be0c4f125d8e2497338d05198)!
Installing dependencies from Pipfile.lock (d05198)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.

🤔 that's odd. My environment uses pipenv installed via pipx and I'm using Python 3.8.
Here's my attempt with the Python docker image:
docker run -it python:3.10.12 /bin/sh
# pip install pipenv
# pipenv --version
pipenv, version 2023.8.26
# git clone https://github.com/stewartmiles/pipenv_editable_install_repro
# cd pipenv_editable_install_repro

First attempt:
# pipenv sync && pipenv install -e ./test-hello
Warning: Python 3.8 was not found on your system...
Neither 'pyenv' nor 'asdf' could be found to install Python.
You can specify specific versions of Python with:
$ pipenv --python path/to/python

ok so I need to update the Pipfile etc.:
# rm Pipfile*
# pipenv --python 3.10
# pipenv lock
Locking [packages] dependencies...
Locking [dev-packages] dependencies...
Updated Pipfile.lock (8e6547742479a83bb67555446f723053c2894d670dcc89b1a6e1e07cab885a1b)!

Finally, try again:
# pipenv install -e ./test-hello
Installing -e ./test-hello...
Resolving -e ./test-hello...
⠋ Installing...Error: Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/pipenv/routines/install.py", line 255, in do_install
    added, cat, normalized_name = project.add_package_to_pipfile(
  File "/usr/local/lib/python3.10/site-packages/pipenv/project.py", line 1167, in
add_package_to_pipfile
    name, normalized_name, entry = self.generate_package_pipfile_entry(
  File "/usr/local/lib/python3.10/site-packages/pipenv/project.py", line 1114, in
generate_package_pipfile_entry
    req_name = determine_package_name(package)
  File "/usr/local/lib/python3.10/site-packages/pipenv/utils/dependencies.py", line 744, in
determine_package_name
    raise ValueError(f"Could not determine package name from {package}")
ValueError: Could not determine package name from file:///pipenv_editable_install_repro/test-hello

✘ Failed adding package to Pipfile
✔ Installation Succeeded
Installing dependencies from Pipfile.lock (885a1b)...
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.

So it doesn't seem related to Python version or the fact I usually install pipenv with pipx.

Maybe the ast parser for the setup.py to determine the package name isn't working right for lower versions of python?

This maybe a different issue as I'm hitting a private repo but I wanted to add my notes in case its related or it may help others since this thread helped me.
My github build started failing on 8/16 I see that a passing build that day had pipenv version 2023.7.23 and the very next build had 2023.8.22 and I started getting the following error
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Could not find a version that satisfies the requirement dkany (from versions: none)
[ResolutionFailure]:   File "c:\users\bhunscher\appdata\local\programs\python\python38\lib\site-packages\pipenv\resolver.py", line 811, in _main
[ResolutionFailure]:       resolve_packages(
[ResolutionFailure]:   File "c:\users\bhunscher\appdata\local\programs\python\python38\lib\site-packages\pipenv\resolver.py", line 759, in resolve_packages
[ResolutionFailure]:       results, resolver = resolve(
[ResolutionFailure]:   File "c:\users\bhunscher\appdata\local\programs\python\python38\lib\site-packages\pipenv\resolver.py", line 738, in resolve
[ResolutionFailure]:       return resolve_deps(
[ResolutionFailure]:   File "c:\users\bhunscher\appdata\local\programs\python\python38\lib\site-packages\pipenv\utils\resolver.py", line 1096, in resolve_deps
[ResolutionFailure]:       results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps(
[ResolutionFailure]:   File "c:\users\bhunscher\appdata\local\programs\python\python38\lib\site-packages\pipenv\utils\resolver.py", line 895, in actually_resolve_deps
[ResolutionFailure]:       resolver.resolve()
[ResolutionFailure]:   File "c:\users\bhunscher\appdata\local\programs\python\python38\lib\site-packages\pipenv\utils\resolver.py", line 684, in resolve
[ResolutionFailure]:       raise ResolutionFailure(message=str(e))
[pipenv.exceptions.ResolutionFailure]: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
  You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
  Hint: try $ pipenv lock --pre if it is a pre-release dependency.
ERROR: No matching distribution found for dkany

[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[[source]]
url = "https://my-repository/simple/"
verify_ssl = true
name = "mine"

[packages]
dataclasses-json = "*"
pandas = ">0.20.1"
strenum = "*"
pyyaml = "*"
dkany = {version="0.0.13", index="mine"}
....

This may be obvious but I was wondering for a bit so if I help someone great.

@stbth01 that issue may be what is tracked with #5878 and #5880

@matteius not sure whether you saw https://github.com/pypa/pipenv/issues/5858#issuecomment-1696116439 but as I mentioned I reproduced the problem with 2023.8.26 with python 3.10.12 (your test version) in a Python docker container.

@stewartmiles I determined it to be a limitation of the prior ast parser on python 3.10 version -- hopefully latest pipenv 2023.8.28 works for you.   Please try it out and close the issue if it is satisfactory.

@matteius what is the minimum Python version now required to use pipenv? It used to support all of 3.x but now it sounds like if it doesn't work with 3.10 then all users using editable packages (at least) will need to upgrade.

@stewartmiles python 3.7 thru 3.11 are still supported -- at some point later this year we will drop support for 3.7.   I patched the ast parser logic for setup.py; unless you are reporting a new issue with this update?  I still recommend folks migrate away from putting the library name in the setup.py because parsing it can be problematic, but it is expected to work in cases where the string is present in the setup.py

@matteius I misread the version number you mentioned in https://github.com/pypa/pipenv/issues/5858#issuecomment-1696627911 i.e 2023.8.**28** not 26. In https://github.com/pypa/pipenv/issues/5858#issuecomment-1696073704 I tested 2023.8.26` and Python 3.10.12 things did not work, editable package installation fails.
With the latest version 2023.8.28 using https://github.com/stewartmiles/pipenv_editable_install_repro @ https://github.com/stewartmiles/pipenv_editable_install_repro/commit/1926b97d0e6bfb65c8090845dadec43f55ddcb4b things work fine.
However, now when installing editable packages from parent directories outside the venv (a behavior that used to work), package installation embeds the absolute path of the editable package in Pipfile and Pipfile.lock. This is reproducible with 2023.8.28 with https://github.com/stewartmiles/pipenv_editable_install_repro/commit/86ed880900ee95eb1419bb3aab928a94ca00759c (sorry the shell is becoming a mess).
i.e running:
git clone https://github.com/stewartmiles/pipenv_editable_install_repro
cd pipenv_editable_install_repro
./try_pipenv_versions.sh 2>&1 | tee ../try_pipenv_versions.log

results in:
+ echo './../test-hello and ../test-hello '
./../test-hello and ../test-hello
+ echo 'not found in {filename}'
not found in {filename}
+ echo '--- Pipfile ---'
--- Pipfile ---
+ cat Pipfile
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
test-hello = {file = "/home/stewart/src/pipenv_editable_install_repro/test-hello", editable = true}

[dev-packages]

[requires]
python_version = "3.8"
+ error=1
+ for filename in Pipfile Pipfile.lock
++ grep -F '"./../test-hello' Pipfile.lock
+ local found_relative_package_path=
++ grep -F '"../test-hello' Pipfile.lock
+ local found_alternative_package_path=
+ [[ -z '' ]]
+ [[ -z '' ]]
+ echo './../test-hello and ../test-hello '
./../test-hello and ../test-hello
+ echo 'not found in {filename}'
not found in {filename}
+ echo '--- Pipfile.lock ---'
--- Pipfile.lock ---
+ cat Pipfile.lock
{
    "_meta": {
        "hash": {
            "sha256": "08d8cd2781157cf3ebafbeba84526e1c8ed2450b91b614e70ea3e09e24c9ebaa"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.8"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "test-hello": {
            "editable": true,
            "file": "/home/stewart/src/pipenv_editable_install_repro/test-hello"
        }
    },
    "develop": {}
}
+ error=1
+ return 1
+ error=1
+ popd
~/src/pipenv_editable_install_repro
+ return 1
+ echo '--- pipenv version 2023.8.28 is broken ---'
--- pipenv version 2023.8.28 is broken ---

The full log is try_pipenv_versions.log

@stewartmiles Ah, absolute path bites again -- ok, well I believe this is the area where that is happening:  https://github.com/pypa/pipenv/blob/main/pipenv/utils/dependencies.py#L648-L651
I am fully open to code patches that will further figure out how to keep the file paths relative -- I am just not sure the exact direction to head.

@stewartmiles I have a PR out that I believe does a better job at determining the relative path:  https://github.com/pypa/pipenv/pull/5896
Example:
matteius@matteius-VirtualBox:~/pipenv_editable_install_repro/test-hello$ pipenv install ../applications/test-hello/
Creating a virtualenv for this project...
Pipfile: /home/matteius/pipenv_editable_install_repro/test-hello/Pipfile
Using default python from /usr/bin/python (3.10.12) to create virtualenv...
⠹ Creating virtual environment...created virtual environment CPython3.10.12.final.0-64 in 212ms
  creator CPython3Posix(dest=/home/matteius/.virtualenvs/test-hello--_GSX-an, clear=False, no_vcs_ignore=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/matteius/.local/share/virtualenv)
    added seed packages: pip==23.2.1, setuptools==68.0.0, wheel==0.41.2
  activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator

✔ Successfully created virtual environment!
Virtualenv location: /home/matteius/.virtualenvs/test-hello--_GSX-an
Creating a Pipfile for this project...
Installing ../applications/test-hello/...
Resolving ../applications/test-hello/...
Added test-hello to Pipfile's [packages] ...
✔ Installation Succeeded
Pipfile.lock not found, creating...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✔ Success!
⠏ Locking...Warning: INFO:pipenv.patched.pip._internal.operations.prepare:Obtaining file:///home/matteius/pipenv_editable_install_repro/applications/test-hello (from -r /tmp/pipenv-lleb236s-requirements/pipenv-o8ryjw3e-constraints.txt (line 2))
INFO:pipenv.patched.pip._internal.cli.spinners:Installing build dependencies: started
INFO:pipenv.patched.pip._internal.cli.spinners:Installing build dependencies: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Checking if build backend supports build_editable: started
INFO:pipenv.patched.pip._internal.cli.spinners:Checking if build backend supports build_editable: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Getting requirements to build wheel: started
INFO:pipenv.patched.pip._internal.cli.spinners:Getting requirements to build wheel: finished with status 'done'
INFO:pipenv.patched.pip._internal.cli.spinners:Preparing metadata (pyproject.toml): started
INFO:pipenv.patched.pip._internal.cli.spinners:Preparing metadata (pyproject.toml): finished with status 'done'
Locking [dev-packages] dependencies...
Updated Pipfile.lock (23b9cf861bceae95e2dbb7d2a1bcc9307d3e05244dd1e1e5a0c7eed37108a154)!
Installing dependencies from Pipfile.lock (08a154)...
cat PipTo activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
matteius@matteius-VirtualBox:~/pipenv_editable_install_repro/test-hello$ cat Pipfile
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
test-hello = {file = "../applications/test-hello"}

[dev-packages]

[requires]
python_version = "3.9"
matteius@matteius-VirtualBox:~/pipenv_editable_install_repro/test-hello$ cat Pipfile.lock
{
    "_meta": {
        "hash": {
            "sha256": "23b9cf861bceae95e2dbb7d2a1bcc9307d3e05244dd1e1e5a0c7eed37108a154"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.9"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "test-hello": {
            "file": "../applications/test-hello"
        }
    },
    "develop": {}
}

Note:  I had to remove the Pipfile/lock file from the parent directory so it wouldn't get confused about where it was starting from.


hierarchical path as string

Would you consider to support dotted string as a access key to sub boxes:
b=Box(dotted=True)

b.c.d.e = 10
b['c.d.e'] == b.c.d.e

That is, to have an equivalence between those two notations.
If positive, then also to support some corresponding functions for traversing (for example):
b = Box(dotted=True)
b.c = dict(e=1, f=2)
b.a = dict(b=3, c=4)
[*Box.keys(dotted=True)]
# ['c.d.e', 'c.d.f', 'a.b', 'a.c']

Thanks!

I do think that is an interesting idea and merits looking into adding.
I will have to think about it some, and how it will interact with the other box types. Questions for me to answer while developing this:

How will it work with conversion box, will it actually accept dot strings with spaces in and fix them?
Will it work with camel_killer_box, or does dotted simply have to be exact?
What's the most efficient way to implement this to cause little to no overhead when not using this feature?

Thanks for the great idea! 👍

I had only a quick look at the code, so probably I can miss some details, but it seems that it may be possible to think about that as a kind of a wrapping interface.
For example, in the case of  __getattr__ :

first (overhead related) check something like that:

if self._box_config['frozen_box'] and '.' in item:
   # Only then activate the "dotted machinery".
   # If dotted setting is OFF the overhead will be this check:
   # self._box_config['dotted'] ==  False

and then (considering the camel_killer_box and conversion and actually all similar questions),
split the item by dots and just chain call __getattr__ with each of them,
leaving all the existing logic to deal with whatever will be found in those keys sub-strings.

Not sure how that is helpful, but it may be good to treat this dotted string just as another syntactic option which is otherwise equivalent to the regular behaviour.

Just wanted to give an update that I do have the start of this feature in the 4.0 branch. (And no parameters required!)
>>> a = Box(test={'a': {'c': 'd'}})
>>> a['test.a.c']
'd'

I haven't wrapped my brain around how best to traverse all the keys yet but I still also like having that option.

Added in 4.0


App.destroy doesn't properly cleanup, possible regression

Hey, it seems that in ember 1.11 some bug creeped in that causes acceptance tests to not properly cleanup after themself.
http://jsbin.com/mezinu/13/edit - failing tests, ember 11.1
http://jsbin.com/mezinu/15/edit - same code, passing tests, ember 1.10

@rwjblue any idea? this breaks tests in my app :\

It works in canary http://jsbin.com/mezinu/17/edit?html,css,output but still fails in v12.0-beta.3

Man we've got the exact same problem.   We are running into this problem too (Ember 1.13.8) and it's making it so that we can't hook our tests up to our CI process because tests that should be passing are failing due to Ember.run(app, 'destroy'); not cleaning up as it should.

I haven't noticed anything like that happening in any recent Ember releases so I'm going ahead and closing this issue as resolved


Civil War in the Middle East and North Africa

This issue is a merger of the following issues

[ ] Libyan Civil Wars
[ ] Afghan Civil Wars from 1992 to Present Day
[ ] Somalian Civil War
[ ] Lebanese Civil War

Given the nature of clan politics in Somalia, I intend to split up up the Somali culture to multiple culture representing Somali clans like the Isaaq, Darod etc to make a more accurate representation of Somali politics in NWO however the Somali culture would still remain as it represent the Somalis who don't identify with any clan and it function like the Yugoslav culture.


WebSocket demasking is not done if WebSocket-frame is split along multiple TCP frames

Unfortunately, I do not have a simple reproduce but the problem is obvious in the code (see my PullRequest #1406)
Background: Clients have to mask their payloads using a simple XOR operation, so the server has to unmask it using the same XOR operation. If a WebSocket-Frame is split into several TCP frames, this should not change anything - the payload has still to be demasked.
However, it seems like the code path for handling this continuation has a little bug. It only demasks the content if the mask if zero - but it should be exactly the opposite

https://github.com/uNetworking/uWebSockets/releases/tag/v20.10.0


tracing UI changes

In the tts span the 'cached' property, which should show true or false, is blank

Please see call placed at 05.08.2023 1:19 PM for example

Also, we need to have an env var which, if set, makes it so we do not show the tracing panel at all in recent calls (i.e., the view should look exactly like those calls for which we do not have a trace_id)

Another issue is that long lines in the detail view are getting truncated.  We need the text to wrap into multiple lines in this case so we can see it all.  Example:

Closed as PR merged


How do I calculate LRP metric for test set from custom dataset?

I have my own dataset collected from the University. How do I calculate LRP for this dataset?

Hi @priteshgohil ,
If your annotations and detection outputs follow the same format as COCO dataset you can use COCO API if not, you can follow the official instructions by following this link: http://cocodataset.org/#format-data.
If you decide to follow COCO format, you should change the following lines to evaluate detection outputs under LRP.
https://github.com/cancam/LRP/blob/de7bae3887211a605d367c71643a76789384669c/cocoLRPapi-master/PythonAPI/evalDemoLRP.py#L8
https://github.com/cancam/LRP/blob/de7bae3887211a605d367c71643a76789384669c/cocoLRPapi-master/PythonAPI/evalDemoLRP.py#L11
Additionally, if you prefer to implement LRP on your own, please check the pseudo code below:
for s in range(0,1,0.01):
  Threshold detection set from s
  Match thresholded detections with ground truths
  According to this matching identify  TP, FP FN numbers anda IoUs of the confidence scores
  Use Eq 5 to find LRP of this thresholded set (or Eq 1-4 LRP and the components.)
endfor
return the minimum LRP value as the oLRP

Note that more efficient implementations can be used (such as instead of matching every step, you can match once - please check evaluateImg.py and accumulate.py in cocoevalLRP.py for details)  but this pseudocode presents the basic steps.
I'm closing this issue, if you have further questions please feel free the reopen it.
Baris.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (02eafd6) 95.69% compared to head (7226a79) 95.69%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #856   +/-   ##
=======================================
  Coverage   95.69%   95.69%
=======================================
  Files           1        1
  Lines         395      395
  Branches       53       53
=======================================
  Hits          378      378
  Misses         17       17

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter solaredge for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.solaredge
   -
:thumbsup: No errors found
WARNINGS:

[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W173] Potential sensitive data "apikey" not listed at "protectedNative" in io-package.json
[ ] :eyes: [W174] Potential sensitive data "apikey" not listed at "encryptedNative" in io-package.json

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 06 Sep 2024 10:30:43 GMT

Issue outdated due to RECREATE request. Follow up issue #82 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


Bulk Report Creation via Smartsheet API

Describe the bug
Need to generate around 3,000 reports from a Smartsheet, so planned to automate this process using Smartsheet Python SDK. However, when attempting to create a report programmatically, encountered the following error:
"The error 'Reports' object has no attribute 'create_report' indicates that the Smartsheet Python SDK does not have a method called create_report for the reports objects. This is because the Smartsheet API Currently does not support the direct creation of reports through the API in the same way that it does for sheets, rows, and columns."
Given that manually creating 3,000 reports would be highly inefficient, I would appreciate your guidance on alternative methods or best practices to achieve this level of automation.
Expected behavior
Automatically creating reports through the API by using Python SDK.
Environment (please complete the following information):

OS: Windows 10
Smartsheet Python SDK Version 2.105.1
Python Version 3.12

+1

+1


Create issue for reports selected by language

The daily summary report - Total no. of requests by category.

[ ] include tamil and english for subcategories

[ ] include all three languages for category also

backend updated

done


[Android] Project with path ':app' could not be found in project ':notifee_react-native'

React Native - 0.67.2
@notifee/react-native - 5.4.1
The error has started to appear after we have removed CodePush from our project. Early there was no such error. If we adding CodePush back to our project this error disappears.

I can't see how this is anything other than a project integration issue, as our demos are all non-code-push and have no issues. If you can reproduce this from react-native init on a clean project we can examine it but we'll need that reproduction before examining

Also, it's worth mentioning that we are about to release this https://github.com/invertase/notifee/pull/447, which should fix any issues around finding :app. but not sure if it'll help in your case

Hi, thanks for the library. I've also encountered this issue, and tried this approach, but no luck yet. I debug the $rootDir and the location is already correct. Any thoughts on what might cause this issue?

I removed "include ':app' when I removed CodePush
then i have seen same error with you
I have resolved this code
// include ':app', ':react-native-code-push'
-> include ':app'

React Native - 0.67.2 @notifee/react-native - 5.4.1
The error has started to appear after we have removed CodePush from our project. Early there was no such error. If we adding CodePush back to our project this error disappears.

I removed "include ':app' when I removed CodePush
then i have seen same error with you
I have resolved this code
// include ':app', ':react-native-code-push'
-> include ':app'

For anyone who has to do manual linking for some reasons and experienced this issue, follow these steps:

Upgrade the library to the latest version, v5.5.0 as I am writing this.
Add these into your android/settings.gradle

include ':@notifee_react-native'
project(':@notifee_react-native').projectDir = new File(rootProject.projectDir, '../node_modules/@notifee/react-native/android')
include ':app'

In your build.gradle file, add this into dependencies:

implementation project(":@notifee_react-native")

Then in your MainApplication.java,

import io.invertase.notifee.NotifeePackage;
...
packages.add(new NotifeePackage());

Hope it helps.

Mmm, 5.5.0 was supposed to help fix all these issues. I think the next step is to explore removing the app dependency from notifee's build gradle altogether.

For anyone who has to do manual linking for some reasons and experience this issue, follow these steps:

Upgrade the library to the latest version, v5.5.0 as I am writing this.
Add these into your android/settings.gradle

include ':@notifee_react-native'
project(':@notifee_react-native').projectDir = new File(rootProject.projectDir, '../node_modules/@notifee/react-native/android')
include ':app'

In your build.gradle file, add this into dependencies:

implementation project(":@notifee_react-native")

Then in your MainApplication.java,

import io.invertase.notifee.NotifeePackage;
...
packages.add(new NotifeePackage());

It works for me and hopefully this can help you as well.

Thank you. We have tested all solutions and yours was only one working.

@faustaleonardo is right, but it automatically sets everything except one setting, so you only need to add one code.

Add these into your android/settings.gradle

include ':app' // add this


Misplaced alignment tab character &

Describe the bug
I got the following error when compiling one of the examples:
[2] [3] (./starter-recommended.lof) [4] (./starter-recommended.lot) [5] (./starter-recommended.lol) [6] [1]
c:/Users/robin.genz/Entwicklung/latex-test/starter-recommended.tex:35: Misplaced alignment tab character &.
\do #1->\bbx@tab@label {#1}\addcolon &
                                       \bbx@tab@item {#1}\\
l.35 \end{document}

To Reproduce
Steps to reproduce the behavior:

Install the latest version of TeX Live / VS Code / LaTeX Workshop.
Execute the installation script install_udhbwvst_tl.ps1.
Open an example (e.g. /examples/starter-recommended/) in VS Code and run one of predefined LaTeX Workshop recipes (.vscode/settings.json).

Annotation: This error does not occur when removing the & from \def\do##1{\bbx@tab@label{##1}\addcolon & \bbx@tab@item{##1}\\}% (L331).
Expected behavior
This error should not occur when compiling the LaTeX document.
Additional context
$ ver
Microsoft Windows [Version 10.0.18362.295]

$ latexmk --version
Latexmk, John Collins, 18 June 2019. Version 4.65

$ biber --version
biber version: 2.13

$ lualatex --version
This is LuaTeX, Version 1.10.0 (TeX Live 2019/W32TeX)

Thank you for this exemplary issue!
I tried to reproduce your problem but I wasn't successful :/

I downloaded the v4.2.0 release artifact.
I installed udhbwvst running install_udhbwvst_tl.ps1.
I built the pdf in VSCode using the latexmk build recipe.

There were no compilation errors! My setup:
$ ver
Microsoft Windows [Version 10.0.17763.678]

$ latexmk --version
Latexmk, John Collins, 17 March 2019. Version 4.63b

$ biber --version
biber version: 2.12

$ lualatex --version
This is LuaTeX, Version 1.10.0 (TeX Live 2019/W32TeX)

I tried the same again using the official docker image:
docker run -v C:\path\to\starter-recommended:/work skyfrk/udhbwvst:4.2.0 latexmk -synctex=1 -interaction=nonstopmode -file-line-error -shell-escape -pdf -pdflatex=lualatex starter-recommended.tex
Versions of latexmk, biber and lualatex inside the docker container:
$ docker run --rm -it skyfrk/udhbwvst:4.2.0 latexmk --version
Latexmk, John Collins, 17 March 2019. Version 4.63b

$ docker run --rm -it skyfrk/udhbwvst:4.2.0 biber --version
biber version: 2.12

$ docker run --rm -it skyfrk/udhbwvst:4.2.0 lualatex --version
This is LuaTeX, Version 1.10.0 (TeX Live 2019/Arch Linux)

I have absolutely no idea what causes your compilation error :(
Can you do an insanity check for me and check the versions of latexmk, biber and lualatex inside the docker container on your end? 😬

Sure, this is my output:
$ docker run --rm -it skyfrk/udhbwvst:4.2.0 latexmk --version
Latexmk, John Collins, 17 March 2019. Version 4.63b

$ docker run --rm -it skyfrk/udhbwvst:4.2.0 biber --version
biber version: 2.12

$ docker run --rm -it skyfrk/udhbwvst:4.2.0 lualatex --version
This is LuaTeX, Version 1.10.0 (TeX Live 2019/Arch Linux)

The docker container works fine.
I think there should be a problem with biber version: 2.13 or Latexmk, Version 4.65.

I'll try to update my setup and reproduce the bug again!

I was able to replicate your issue. I think it's beause of biber v2.12 -> v2.13 as build with the non-latexmk recipe also doen't work.
From the biber changelog:

biber now exits with error on some very malformed names instead of skipping them as this can lead to data loss in bibliographies.

Maybe this has something to do with this issue.
I'll try to provide a fix asap! One could fix this problem by replacing the custom longtable style with a style similar to Mrs. Heinrichs style (from her script):

I think with these examples she just wanted to show what must be included.
This example was related to the structure:

So the previous format should be retained.

I guess you're right. I'll try to replace the current implementation of a tabular bibliography with this package.


Give an option to disable or change path of experiment name.

First of all thank you for this very useful library!
To the issue:
I see that the result of a Scan() operation implies the saving of a model.
Enforcing the creation of files without the explicit command of the user is in general a bad practice. Think of all the software that we use. They may save the results, but if and only if users give explicit directions to do so.
From my understanding I can't even point an absolute path for the Scan to be saved.

There is a .csv file stored in your present working directory with the results of your experiment. If you declare a name for your experiment, then that will be used, and otherwise the name will be generated based on time when the experiment starts. Having this file updated throughout the run is a meaningful default state for several reasons. For example, if the experiment is interrupted on Saturday afternoon and you come back on Monday, you still have some results to look at.
I don't see why you would not be able to define a path instead of just name. I suggest using v.0.6. where logging is handled much better overall. There you will have experiment_name argument in talos.Scan().
Other than that, do you have an example for a case where you absolutely would not want to have a log stored on the local machine as the experiment progress?

Closing here, feel free to reopen if you think this is still relevant.


Search - Created task not displayed in search results until page refreshed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.60-8
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4478317
Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
and log in
Open any chat
Create a task with a unique name
Click on the search icon
Search for the task

Expected Result:
The task is displayed in the search results
Actual Result:
The task is not displayed in the search results until the page is refreshed
Workaround:
n/a
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/cb20c9f6-b092-46e4-a6f2-a699a5bfdebf
View all open jobs on GitHub

We think that this bug might be related to #vip-vsb

I dont think this has to be a blocker as its a quite specific flow
I believe its coming from https://github.com/Expensify/App/pull/38207 cc @TMisiukiewicz can you have a look please

I already found what is causing the issue - the cached list is updated when a single reports updates, but it does not have a mechanism of creating a new option when a new item is created. I need some more time to figure out how to implement it and not downgrade the performance, going to continue working on that Monday morning

Opened a draft PR, however reassure test was failing - I'm looking into that before opening

Found one more related issue when requesting/sending money from non-existing account, gonna fix it with the same PR

@mountiny I just opened the PR - the issue I had with non-existing account seem to not be related to my recent changes. I was trying to figure out if invited accounts are displayed on the search (the answer is yes), but I have encountered a weird behavior. After requesting money from non-existing account, the report opens with an e-mail address visible. After getting a response from API it changes to "Hidden". After refreshing the app, the email is visible again. I tried to track which change caused it, and noticed on version 1.4.60 it still works fine, but it happens on 1.4.61. Is this a known issue?

. I tried to track which change caused it, and noticed on version 1.4.60 it still works fine, but it happens on 1.4.61. Is this a known issue?

I am not aware of this issue, could you report it in the open source channel please 🙏

@mountiny posted here

What's the latest on this issue?

@JmillsExpensify it was fixed in #39811

Ah perfect. So all that is left is a payment summary: $250 to @thesahindia for PR review and testing. I'm closing this issue as C+ is paid out via New Expensify. @thesahindia make sure to comment on whether a regression test is needed when you request payment. Thanks!

Payment Summary
C+ @thesahindia $250 please request in newdot
Contributor @TMisiukiewicz agency worker, no payment required

$250 approved for @thesahindia


Shortened state string for nfa transition record array item values

const nfa1 = new NonDeterministicFiniteAutomaton(()=> true, {
	transitions: {
		alphabets: ['a', 'b', 'c']
		A: ['A-Z', ['A-D', 'F', '0-5']],
	}
});

When we are in state A :-

we encounter symbol 'a' move to all states from A to Z
we encounter symbol 'b' move to all states from A to D, F and 0 to 5

Feature added in version 0.0.8


IOS8 in iCloud in the picture does not show

IOS8 in iCloud in the picture does not show.

@jiekewei Photos in iCloud might not be shown properly if they haven't been downloaded to the device.  It's the limitation of ALAssets framework. Hopefully it can be achieved in the future release by using iOS 8 Photos framework.

Fixed in the v3.0.0-beta.1

Can CTAssetsPickerController choose the picture in iCloud When picture haven't been downloaded now?

Yes. That should be okay since v3.0.0


Fixes bug in reduce_sum handling expressions with threading enabled

Summary
Fixes two bugs in reduce_sum when STAN_THREADS is set.

under some conditions reduce_sum did not compile (the original reported bug in the issue)
shared arguments could be evaluated multiple times (the reason for expression tests failing with STAN_THREADS set)

Tests
None for now. @rok-cesnovar promised he will add tests for those after the bugfix release.
Side Effects
None
Release notes
Fixes two bugs in reduce_sum when STAN_THREADS is set.
Checklist

[x] Math issue #2370

[x] Copyright holder: Tadej Ciglarič
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[ ] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[ ] the code is written in idiomatic C++ and changes are documented in the doxygen

[ ] the new changes are tested

@serban-nicusor-toptal Math master is now ready. Lets leave it to propagate to CmdStan and do the 2.26.1 tomorrow CET time.


Parse MySQL column default value

PR Info

Closes https://github.com/SeaQL/sea-schema/issues/23

Bug Fixes

[x] Parse MySQL column default value

parse the EXTRA column; if it contains DEFAULT_GENERATED, then the COLUMN_DEFAULT should be regarded as an expression

Hmmm... no. This logic doesn't work on every MySQL / Mariadb version

Note that, CURRENT_DATE is not special.

TO implement this correctly we have to perform some version check:
MySQL 5:
Only literal is supported, so:

if column is TIMESTAMP or DATETIME and value is CURRENT_TIMESTAMP, regard it as DefaultExpr::CURRENT_TIMESTAMP
if it is numeric-like then regard it as Number
otherwise regard it as String

MySQL 8:
parse the EXTRA column; if it contains DEFAULT_GENERATED, then the COLUMN_DEFAULT should be regarded as an expression
if the default is an expression, parse it as a Expr and recognize the keywords CURRENT_TIMESTAMP, otherwise Custom
if the default is not an expression, then it's a literal; then we should
a. if it is numeric-like then regard it as Number
b. otherwise regard it as String

Hey @tyt2y3, was a success. Please proofread the db specific parsing part for me :)

Done

I just checked on my machine, MySQL 8 default (NULL) is valid and is different from default null

Wait... I am re-reading this

From MariaDB 10.2.7, literals are quoted to distinguish them from expressions. NULL means that the column has no default

It means the version >= 10.2.1 and < 10.2.7 is a void, and there is no way to properly discover the schema.


andoid textureview can not capture frame

Description
andoid textureview can not capture frame
I use TextureView to build opengles Environment, but renderdoc can't capture frame
follow the code
GLTextureView.zip

get thread dump

Environment

RenderDoc version: 1.15
Operating System: android
Graphics API: opengles 3.0
model xiaomi note3   , goolge pixel2

Your program is broken - it stops calling present or GL commands which is why RenderDoc says that it's not presenting. Modifying the source to change the clear colour to random colours shows that it's not rendering continuously. It also seems to use unsupported OpenGL extensions without checking if they are available, so I recommend that you also fix that as otherwise it may cause further problems.
You need to fix your code and then RenderDoc should work. Try running a known-good sample or a built apk from e.g. Unity or Unreal to see that it is working as expected. Note that on xiaomi devices they are broken out of the box, so you need to change some settings to make them debuggable.

Your program is broken - it stops calling present or GL commands which is why RenderDoc says that it's not presenting. Modifying the source to change the clear colour to random colours shows that it's not rendering continuously. It also seems to use unsupported OpenGL extensions without checking if they are available, so I recommend that you also fix that as otherwise it may cause further problems.
You need to fix your code and then RenderDoc should work. Try running a known-good sample or a built apk from e.g. Unity or Unreal to see that it is working as expected. Note that on xiaomi devices they are broken out of the box, so you need to change some settings to make them debuggable.

the GLTextureView  copy from gpuimage and my program can display well,
but i try gpuimage program(use textureview model) and can't correct capture frame
follow is my program apk
app-debug.zip
follow is gpuimage apk ,click gallery button and capture frame by use renderdoc  ,u can find the bug
[gpuimage apk](gpuimage.zip](https://github.com/baldurk/renderdoc/files/7189042/gpuimage.zip)

This other program you've linked also uses an unsupported OpenGL extension without checking for it, and it also presents very inconsistently. If I capture while it is presenting it works correctly, so this still doesn't appear to be a RenderDoc bug.
If you need to capture a program that doesn't present interactively you may find it easier to use the in-application API as RenderDoc is designed for programs that render continuously and so uses presents as capture boundaries. However you should still make sure your program uses valid OpenGL and doesn't try to use unsupported extensions.


Support additional filtering in the mapping file?

Currently some of the parameters require custom tags in order to be exported correctly, although filtering could be sufficient.
For example, PRC_VINT[REG,PRC] = ~FI_Process(Region,TechName) should either be substituted by preprocessing and a custom tag or could be transformed to something like PRC_VINT[REG,PRC] = ~FI_Process(Region,TechName,Vintage:YES), but the latter would require allowing the mismatch between the number of columns in the mapping.

What do you think @siddharth-krishna ?

Perhaps we can try to implement the filter syntax first and see if that is sufficient? It's a more general operation so hopefully it applies elsewhere too.

Do you mean expanding the existing syntax (e.g. Attribute:ACT_COST) somehow?

Yes. Perhaps we should start thinking of a more general structure for this mapping file so that we can specify general operations like filter?

We definitely can start thinking about it. :-) Do you think allowing fewer columns on the right is doable already (e.g. PRC_VINT[REG,PRC] = ~FI_Process(Region,TechName,Vintage:YES) or PRC_VINT[REG,PRC] = ~FI_Process(Region,TechName,Vintage))?


When installing into an app that uses services or concerns, app fails to start

When trying to boot with classes within app/controllers/concerns or app/models/concerns or app/services Wallaby fails to start with:
/Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/dependencies.rb:495:in `load_missing_constant': Unable to autoload constant GenerateEnrollmentsCsvService, expected /Users/mikel/Code/enlight/app/services/generate_enrollments_csv_service.rb to define it (LoadError)
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/dependencies.rb:184:in `const_missing'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/inflector/methods.rb:261:in `const_get'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/inflector/methods.rb:261:in `block in constantize'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/inflector/methods.rb:259:in `each'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/inflector/methods.rb:259:in `inject'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/inflector/methods.rb:259:in `constantize'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/core_ext/string/inflections.rb:66:in `constantize'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/wallaby-4.0.1/app/routes/wallaby/resources_router.rb:13:in `block in <top (required)>'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/wallaby-4.0.1/app/routes/wallaby/resources_router.rb:11:in `each'
	from /Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/wallaby-4.0.1/app/routes/wallaby/resources_router.rb:11:in `<top (required)>'

Changing the service from:
class GenerateEnrollmentsCSVService
end

to
module Service
  class GenerateEnrollmentsCSVService
  end
end

Does fix it, but you have to set this everywhere in the app. Wallaby should be able to handle these classes on usual Rails paths without further modification like the rest of Rails can.

Upgrade to 4.0.1 should fix it.
What it does in resources_router is that it tries to preload all the constants in app folder, this is because in dev environment, all classes are lazy loaded, and wallaby is relying on subclasses to make the magics.
I will yank 4.0.0 for now.

And BTW the class name for generate_enrollments_csv_service.rb should be GenerateEnrollmentsCsvService instead of GenerateEnrollmentsCSVService (CSV => Csv), even Rails won't load it correctly according to its naming convention.

Please let me know if 4.0.1 resolves your problem.

Getting a similar issue @tian-im
/Users/mikel/.rvm/gems/ruby-2.1.6@enlight/gems/activesupport-4.2.6/lib/active_support/dependencies.rb:495:in `load_missing_constant': Unable to autoload constant Concerns::Localeable, expected /Users/mikel/Code/enlight/app/models/concerns/localeable.rb to define it (LoadError)

Could you try the 4.1.0? see the commit above, should solve it now.

Awesome @tian-im, app is starting now :)


add_iov optimizations

Need to gain a little performance and clean up some bracket heavy code.
add_iov() always calls ensure_iov_space(), which can fail if there isn't enough. So every call to it (ie: process_get_command) needs to handle errors. Binary handlers don't bother checking errors, since they assume only a single response packet can be handled per flush, and there's a large minimum iov space.
add_msghdr is used within add_iov as well, most heavily for UDP connections where it might need to add them based on space used.
To complete this issue, ensure_iov_space() should be split out of add_iov. If possible, the msghdr checks should be either split or at least the realloc check should be split. Then, at the top of each loop in process_get_command, ensure_iov_space should be called once with an argument to ensure there's enough space to reach the end of the loop.
Then all of the error handling can be removed, and when binary protocol is fixed to allow buffering responses it doesn't need to add repetitive error handling. Removing the checks to ensure_iov_space() from add_iov should speed up all protocol handlers as well.

See #557 and related PR's


FINERACT-1277-Message-Gateway-webhook

Description
Describe the changes made and why they were made.
Ignore if these details are present on the associated Apache Fineract JIRA ticket.
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[x] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[x] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm with details of any API changes

[x] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@vorburger Is this inactive? If so shall I rebase this and resend a PR?

@vorburger Is this inactive? If so shall I rebase this and resend a PR?

@BLasan it looks like this is inactive, and @fynmanoj abandoned it, yes.
But to be honest, from where I sit, you benefit the project more by working on new issues than by "cleaning up" other people's PRs. It's OK to just let these "stale" PRs by automatically closed by our bot, if the original author no longer has any interest in them - that's life. If someone really does care to get a contribution merged, normally they are expected to follow-up on review feedback.
But it's your choice what you like to work on and contribute! 😃 You can also post to the mailing list to ask. I got hundred to propose you! Depending on your skills and interest.

@BLasan it looks like this is inactive, and @fynmanoj abandoned it, yes.
But to be honest, from where I sit, you benefit the project more by working on new issues than by "cleaning up" other people's PRs. It's OK to just let these "stale" PRs by automatically closed by our bot, if the original author no longer has any interest in them - that's life. If someone really does care to get a contribution merged, normally they are expected to follow-up on review feedback.
But it's your choice what you like to work on and contribute! 😃 You can also post to the mailing list to ask. I got hundred to propose you! Depending on your skills and interest.

@BLasan it looks like this is inactive, and @fynmanoj abandoned it, yes.
But to be honest, from where I sit, you benefit the project more by working on new issues than by "cleaning up" other people's PRs. It's OK to just let these "stale" PRs by automatically closed by our bot, if the original author no longer has any interest in them - that's life. If someone really does care to get a contribution merged, normally they are expected to follow-up on review feedback.
But it's your choice what you like to work on and contribute!  You can also post to the mailing list to ask. I got hundred to propose you! Depending on your skills and interest.

Thank you sir! I'm interested in taking up some new issues :)

@BLasan it looks like this is inactive, and @fynmanoj abandoned it, yes.
But to be honest, from where I sit, you benefit the project more by working on new issues than by "cleaning up" other people's PRs. It's OK to just let these "stale" PRs by automatically closed by our bot, if the original author no longer has any interest in them - that's life. If someone really does care to get a contribution merged, normally they are expected to follow-up on review feedback.
But it's your choice what you like to work on and contribute!  You can also post to the mailing list to ask. I got hundred to propose you! Depending on your skills and interest.

Thank you sir! I'm interested in taking up some new issues :)

Thank you sir! I'm interested in taking up some new issues :)

@BLasan have you already joined our developer mailing list http://fineract.apache.org/#contribute as per https://github.com/apache/fineract#community? Please send a short email introducing yourself there to say Hello to everyone. If you state there that you are interested in new issues, perhaps with some context about your skills and interests if you like, I'll reply with a link to possible issues!

Thank you sir! I'm interested in taking up some new issues :)

@BLasan have you already joined our developer mailing list http://fineract.apache.org/#contribute as per https://github.com/apache/fineract#community? Please send a short email introducing yourself there to say Hello to everyone. If you state there that you are interested in new issues, perhaps with some context about your skills and interests if you like, I'll reply with a link to possible issues!

Thank you sir! I'm interested in taking up some new issues :)

@BLasan have you already joined our developer mailing list http://fineract.apache.org/#contribute as per https://github.com/apache/fineract#community? Please send a short email introducing yourself there to say Hello to everyone. If you state there that you are interested in new issues, perhaps with some context about your skills and interests if you like, I'll reply with a link to possible issues!

I've sent a blank mail as requested to dev-subscribe. And thank you for the guidance sir!!

Thank you sir! I'm interested in taking up some new issues :)

@BLasan have you already joined our developer mailing list http://fineract.apache.org/#contribute as per https://github.com/apache/fineract#community? Please send a short email introducing yourself there to say Hello to everyone. If you state there that you are interested in new issues, perhaps with some context about your skills and interests if you like, I'll reply with a link to possible issues!

I've sent a blank mail as requested to dev-subscribe. And thank you for the guidance sir!!


Async asset loading

While I don't think it's a blocking issue for the first experimental release of WASM support, if we want games to load fast on the web, we need some form of asynchronous asset loading support. This is also important for desktop games, albeit less so.
I'd like to use futures for this if possible, since they're the defacto standard for Rust async coding and they integrate nicely with JS promises. However, the game loop itself isn't going to be async (you can't suspend update or draw), so I'm not sure if there's a nice way to get async/await working?

I kinda don't want to put any significant effort into getting audio working on WASM till this is done, because I don't think bundling sound assets into the binary will work well for that.

While I've put WASM support on hold for now, I still think having some form of async loading will be needed at some point (e.g. for loading screens).

I'm closing this, as I've decided that it's out of scope for Tetra's API (asset loading is too game-specific). If I do build this functionality, it'll probably be as a seperate crate which plugs in to Tetra.


Colab broken?

Hey together, i just tried to use the Colab notebook with custom images and got the error below, when running the scene cell. Tried it in Chrome on Win and Mac, same error. Should it work atm?
Upload widget is only available when the cell has been executed in the current browser session. Please rerun this cell to enable.
---------------------------------------------------------------------------
MessageError                              Traceback (most recent call last)
<ipython-input-2-8dd6a665c864> in <module>()
     40   display(HTML('*minimum 12 images'))
     41   dir = os.getcwd()
---> 42   uploaded = files.upload()
     43   preupload_datasets = [os.path.join(dir, f) for f in uploaded.keys()]
     44   del uploaded

2 frames
/usr/local/lib/python3.7/dist-packages/google/colab/_message.py in read_reply_from_input(message_id, timeout_sec)
    104         reply.get('colab_msg_id') == message_id):
    105       if 'error' in reply:
--> 106         raise MessageError(reply['error'])
    107       return reply.get('data', None)
    108

MessageError: TypeError: Cannot read property '_uploadFiles' of undefined

Upload custom images are working fine for me.
Maybe you could try again?
Error seems like it occurs on the COLAB side. The COLAB team might already fix it.

Okay, I tried another browser and get the button. But now the error is:
PXL_20210804_155805358.jpg(image/jpeg) - 70080 bytes, last modified: n/a - 0% done
 ---------------------------------------------------------------------------
MessageError                              Traceback (most recent call last)
<ipython-input-9-8dd6a665c864> in <module>()
     40   display(HTML('*minimum 12 images'))
     41   dir = os.getcwd()
---> 42   uploaded = files.upload()
     43   preupload_datasets = [os.path.join(dir, f) for f in uploaded.keys()]
     44   del uploaded

2 frames
/usr/local/lib/python3.7/dist-packages/google/colab/_message.py in read_reply_from_input(message_id, timeout_sec)
    104         reply.get('colab_msg_id') == message_id):
    105       if 'error' in reply:
--> 106         raise MessageError(reply['error'])
    107       return reply.get('data', None)
    108

MessageError: RangeError: Maximum call stack size exceeded.

MessageError: TypeError: Cannot read property '_uploadFiles' of undefined
Same issue


✨ Added stream_logs to docker.compose.start()

part of https://github.com/gabrieldemarmiesse/python-on-whales/issues/499 . adding stream_logs to the compose.start() function.

Thanks!!!


optimize rsync behavior of obi go when more than 2 target machines

In a common case for obi, there are 3+ machines to which we need to rsync obi's working directory.  For media-rich applications, this process can be slow.  But it is essential to productivity that we continue to support and improve that use case.
It is almost always the case that the network connection among the target machines is at least as fast, if not much faster, than the connection from laptop or developer workstation to those machines.  In basically every case we've encountered so far, it's Wifi vs. Gigabit ethernet.
Therefore, an rsync strategy in which we rsync assets just to one machine, and then rsync again from that machine to its peers, would pay off, if it could be done.

Doesn't this only optimize in the case that the network is the bottleneck and not the disks the files get written to?

Yes.  It only optimizes our common use case.

Are you sure that network is the bottleneck in the common case?

We've never encountered a multi-machine environment that wasn't wired -- in fact, they've all been gigabit ethernet, but even just assuming a wire, the wire will be as fast or faster than the connection to the developer machine (which is often wifi).  It would be very unusual for the target machines to be connected via Wifi.  So the among-target network seems safe to assume.
We've never encountered a multi-machine environment where the target machines weren't as fast or faster in terms of CPU than the developer machine.  Our developer machines are, at best, the same generation or older than the target machines.
And I've never encountered a computer where disk I/O wasn't faster than network.
Am I missing something in the thrust of your questions?


maybe cache pdf urls for those that we scrape sites for

should speed things up a lot. though might want to check that they at least give a 200 code on a head request for example before caching?
caching with?  redis i guess?
probably dont need to persist data, though would be nice

do this for members:

345
10

done, redis caching now only on /api/doi route


feat(kit): customize display control for input-files component

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows Conventional Commits
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring
[ ] Code style update
[ ] Build or CI related changes
[x] Documentation content changes

What is the current behavior?
It's tricky to customize the content of the files component since it assumes there are 2 content elements (label and link). In the case where dragging occurs the only option for content is via the texts property.
Closes #2734
What is the new behavior?
If you want to override the content of the files component you are able to do this via the content: PolymorpheusContent input property. If you don't provide a content property value, the default behavior is the same and there will be displayed the default link and label elements.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

@oknimot

@oknimot

@splincode, thanks for noticing 🙌 ! Fixed in da0205ff886d1a267095319bf5a828790395bbd8

not sure if you did the right rebase

not sure if you did the right rebase

Yup, you're right. Sorry 🫣, my fault. Going to fix it...


Support of gotowebinar

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.10.05. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2018.10.05

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ x] Feature request (request for a new functionality)

Is it possible that YouTube-dl support gotowebinar.com url, please ?
Thanks for advance...
Hi,
youtube-dl.exe "https://register.gotowebinar.com/recording/recordingView?webinarKey=323480013258908683&registrantEmail=toto.titi%40tata.com" -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://register.gotowebinar.com/recording/recordingView?webinarKey=323480013258908683&registrantEmail=toto.titi%40tata.com', '-v']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2018.10.05
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.17134
[debug] exe versions: ffmpeg N-91206-g9827bb88e7
[debug] Proxy map: {}
[generic] recordingView?webinarKey=323480013258908683&registrantEmail=toto.titi@tata: Requesting header
WARNING: Falling back on generic information extractor.
[generic] recordingView?webinarKey=323480013258908683&registrantEmail=toto.titi@tata: Downloading webpage
[generic] recordingView?webinarKey=323480013258908683&registrantEmail=toto.titi@tata: Extracting information
ERROR: Unsupported URL: https://register.gotowebinar.com/recording/recordingView?webinarKey=323480013258908683&registrantEmail=toto.titi%40tata.com
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp5xdqinp2\build\youtube_dl\YoutubeDL.py", line 792, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp5xdqinp2\build\youtube_dl\extractor\common.py", line 507, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\rg3\tmp5xdqinp2\build\youtube_dl\extractor\generic.py", line 3298, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: https://register.gotowebinar.com/recording/recordingView?webinarKey=323480013258908683&registrantEmail=toto.titi%40tata.com
Regards
Nara

For now a straightforward work around is provided here. It seems like this wouldn't be difficult to implement.

+1

This is still an issue in 2020.05.08.

This is still an issue in 2021.03.14


Rename initWithObject/createWithObject to withValue

We need to make this change in objective-c to be consistent with the new swift apis and to make things more clear/less confusing.
This change should be made once al-swift is merged to master, at which point in time we can fix Object.init(object:)
Old api calls should be deprecated for a few releases.

This was started in set-with-value, but a swift compiler error is preventing the Realm tests from compiling.


ValueError: Attempted relative import in non-package

Using relative import paths inside scour.py doesn't work when calling the script from outside the package directory:
ValueError: Attempted relative import in non-package
from .svg_regex import svg_parser

Should be
from svg_regex import svg_parser

The same for two other relative imports inside this file.

Youd shouldn't call the script, but use the installed scour binary (https://github.com/oberstet/scour/blob/master/setup.py#L49)


[BUG] the update never happens and it keeps looping the update

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
whenever it updates bloxstrap the progress goes to ~49% and jt just restarts

Open the %localappdata%\Bloxstrap\Logs folder, and upload the latest log file here please. It should either be at the top or bottom of the file list.

Bloxstrap_20240131T192237Z.log

Alright, I see what's happening. If you had waited long enough then you would have eventually seen the error that was being described here:
https://github.com/pizzaboxer/bloxstrap/wiki/"Signature-does-not-match!"-error-when-launching-Roblox
This should be relevant to your issue, so read through the information given here and see if it can help you solve your issue.


Phantasy Star Nova

App summary

App name: Phantasy Star Nova (夢幻之星 NOVA)
App serial: PCSH00143
App version: 1.01

Vita3K summary

Version: v0.1.8
Build number: 3249
Commit hash: https://github.com/vita3k/vita3k/commit/[commit]
CPU backend:
GPU backend:

Test environment summary

Tested by: Croden1999
OS: Windows 10/macOS/Linux Distro, Kernel Version?
CPU: Intel I9
GPU: NVIDIA 3070
RAM: 32G

Issues

Screenshots

Log
Recommended labels

A?
B?
C?

The game font display is normal
Unable to enter the game due to stuck character creation interface.
We really want to play this game!!!!!!!!!!!!!!
Thank you all for your hard work!!!!!!! Hope to repair it soon!

duplicate and invalid report, see https://github.com/Vita3K/compatibility/issues/1218
重复及无效报告，请浏览https://github.com/Vita3K/compatibility/issues/1218


MODEXPS-98: Release 1.2.3: Fix permission and security issues

No Kiwi hot fix # 3 release is planned. This mod-data-export-spring release is independent of any hot fix.
This mod-data-export-spring release is to fix the failure when using Okapi >= 4.13.0, for details see the last paragraph in https://github.com/folio-org/okapi/releases/tag/v4.13.0

ty for making this release PR

Closing as duplicate https://github.com/folio-org/mod-data-export-spring/pull/179


fixed error in docs

I think the docs are still a little confusing here. Perhaps the original author intended these examples to be
rgb = tiny.rgb
rgb.set_rgb(255,0,0)

etc
but this then inconsistent with the rest of the docs, which all use tiny.

Hi @topshed. Thank you for this!
I forget my original intent, so it's either what you suspect, or I may have had set_rgb be a function on the tiny_fx object at some point but then removed it and forgotten to update the documentation.

Hmm. Actually, It does seem my intent was
rgb = tiny.rgb
rgb.set_rgb(255,0,0)

As using tiny.rgb. all the time is unnecessarily tedious.
Oh well. I've merged your change in now. I may edit it in the future if I remember


THRIFT-4263: Fix use after free bug for thrown exceptions

Exceptions thrown through PHPExceptionWrapper are prematurely freed at the end
of the catch block, even though zend_throw_exception_object expects to take
ownership of the value.
Ensure we free return_value in case of exceptions
Test binary deserialization of insufficient data which verifies we can cast
exception to string to verify against memory corruption when transport casts
exceptions.
This closes #4263

Side story:
Ok, I was hoping travis would run the cross compile tests with php7, but sadly it doesn't. As I was hoping the build would fail with the test case before submitting, as this is what we've used for testing it under valgrind.
Currently cross compile builds runs with ubuntu 1404 trusty. For thrift as a project you might consider trying to maybe bump this dependency, as maintenance updates for 1404 is more or less going away this year according to https://www.ubuntu.com/info/release-end-of-life .
You will also need min 1604 for php7 packages. Sadly the test suite really doesn't run with newer versions, at least python tests seems to start failing. Another problem is the system tests with (cross-compile) doesn't use cmake yet, which seems to have an idea about being able to select which libraries you want to include in the build.
Also note that PHP5 != PHP7 , and you probably want to focus new development towards PHP7. http://php.net/supported-versions.php .
Ideally CI should maybe build with latest distros where developers hang and live :-)
Anyhow, me and @zhaakhi rolled out this in production for our systems and haven't noticed any segfaults since we deployed it 24 hours ago. But we did revert https://github.com/apache/thrift/pull/1215 in our fork that we have deployed, since we noticed memory leaks from it. Unsure if it was due to me  not ensuring newer thrift compiler under testing, but didn't want to risk it. I've also left a note about it in https://issues.apache.org/jira/browse/THRIFT-4126 .

Test failures seems unrelated, how do we retrigger em to be run again?


Documented service annotation for AWS ELB SSL policy

This change is dependent on kubernetes/kubernetes#54507
ping @justinsb

This change is

@micahhausler FYI, the Travis CI error has been fixed. Please rebase or update your branch. Thx!

/lgtm

@micahhausler Can you resolve the merge conflict? Thanks.

@steveperry-53 This is ready for merge.


useRefArray() hook

What do you think about adding a hook to handle references of array like elements?
The code would look like this:
const useRefArray = () => ({
  _refs: [],
  set current(ref) {
    this._refs.push(ref);
  },
  get current() {
    return this._refs;
  }
});

And a typical application could be the following:

A list of items with smooth scrolling.

Should I submit a PR?, do you see any problem in the code above?

I'm not sure if I follow. The useRefArray is just a function, right? For it to be a hook, I think it has to use at least one of the React hooks internally.


Status of this project?

I'm looking for a crate that implements the Wayland protocol using async Rust. I was planning to make my own until I stumbled upon caledon. With the latest commit being from April, do you still maintain it and would you have time to review potential pull requests? Or would it be better for me to fork it?

I still maintain this crate, I just was taking a hiatus (life got busy). I will have time to review a pull request and I am glad that someone else is interested in this crate.
I have pushed a WIP branch with the next set of changes that I am working on, though this is not yet ready to merge into the main branch.
The project overall has implemented the Wayland wire protocol (as far as I know). I am currently working on the client side of what I call the "Wayland object protocol", that is a Rust API that implements the client side of wl_display, wl_registry, and wl_callback. The next item would be the a server-side API of the Wayland object protocol. With both the client and server object protocols it should be possible to do some simple interop testing with the Wayland C libraries which is what it will take to be reasonably confident that the project has implemented the wire protocol correctly.
The Wayland object protocol API objects will probably be handwritten but for the rest of the core Wayland protocol I would try to find a way to generate the API from wayland.xml. In theory at that point someone could just drop several of the protocol files from wayland-protocols into the protocols folder to have a fuller set of protocols (but we will have to see how this works in practice).
If you are planning a larger pull request you might consider filing an issue first to describe the change you were thinking about. I will still review a pull request without an issue first, but having an issue first would allow for earlier feedback.

Thanks for the detailed answer!

The Wayland object protocol API objects will probably be handwritten but for the rest of the core Wayland protocol I would try to find a way to generate the API from wayland.xml.

There is already some proc-macro code to do that it seems? I imagine that on the client side similarly to libwayland the display object would wrap the auto-generated code for wl_display.

If you are planning a larger pull request you might consider filing an issue first to describe the change you were thinking about. I will still review a pull request without an issue first, but having an issue first would allow for earlier feedback.

I will definitively do that.


Broken VectorStoreRouterAgent cannot use tool

I have three ChromaDB vector stores, each with its own VectorStoreInfo, Connected to a VectorStoreRouterTookit.
The VectorStoreRouterAgent cannot run the tool, even though it clearly defined :
Terminal output

Entering new AgentExecutor chain...
Sure! I'm ready to help you with your question.

Question: Which is the cheapest Kyocera printer?
Thought: To answer this question, I need to research the prices of different Kyocera printers.
Action: I will use the Kyocera tool to find the information.
Action Input: I will input the query "Kyocera printer prices" into the tool.
Observation: I will use the Kyocera tool to find the information. is not a valid tool, try one of [Kyocera, ricoh, xerox].

in the terminal, the tool name is  null for some reason.