pip-sync: fatal error with subprocess.CalledProcessError

I am receiving this stacktrace:
# pip-sync
Uninstalling alabaster-0.7.7:
  Successfully uninstalled alabaster-0.7.7
Uninstalling autobahn-0.11.0:
  Successfully uninstalled autobahn-0.11.0
Uninstalling Babel-2.1.1:
  Successfully uninstalled Babel-2.1.1
Uninstalling backports-abc-0.4:
  Successfully uninstalled backports-abc-0.4
Uninstalling chardet-2.3.0:
  Successfully uninstalled chardet-2.3.0
Uninstalling cloudpickle-0.1.1:
  Successfully uninstalled cloudpickle-0.1.1
Uninstalling contextlib2-0.4.0:
  Successfully uninstalled contextlib2-0.4.0
Uninstalling cssselect-0.9.1:
  Successfully uninstalled cssselect-0.9.1
Uninstalling distribute-0.7.3:
  Successfully uninstalled distribute-0.7.3
Uninstalling django-contrib-comments-1.6.2:
  Successfully uninstalled django-contrib-comments-1.6.2
Uninstalling django-user-accounts-1.3.1:
  Successfully uninstalled django-user-accounts-1.3.1
Uninstalling husl-4.0.3:
  Successfully uninstalled husl-4.0.3
Uninstalling microsofttranslator-0.7:
  Successfully uninstalled microsofttranslator-0.7
Uninstalling pyOpenSSL-0.15.1:
  Successfully uninstalled pyOpenSSL-0.15.1
Uninstalling service-identity-14.0.0:
  Successfully uninstalled service-identity-14.0.0
Uninstalling snowballstemmer-1.2.1:
  Successfully uninstalled snowballstemmer-1.2.1
Uninstalling sphinx-rtd-theme-0.1.9:
  Successfully uninstalled sphinx-rtd-theme-0.1.9
Uninstalling txaio-2.2.0:
  Successfully uninstalled txaio-2.2.0
/usr/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
Collecting Beaker==1.6.4
/usr/local/lib/python2.7/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
  Downloading Beaker-1.6.4.tar.gz (54kB)
    100% |████████████████████████████████| 57kB 1.4MB/s
Collecting Cython==0.21
  Downloading Cython-0.21.tar.gz (1.5MB)
    100% |████████████████████████████████| 1.5MB 281kB/s
Collecting Django==1.7
  Downloading Django-1.7-py2.py3-none-any.whl (7.4MB)
    100% |████████████████████████████████| 7.4MB 64kB/s
Collecting Fabric==1.10.0
  Downloading Fabric-1.10.0.tar.gz (208kB)
    100% |████████████████████████████████| 212kB 1.4MB/s
Collecting Jinja2==2.7.3
  Downloading Jinja2-2.7.3.tar.gz (378kB)
    100% |████████████████████████████████| 380kB 1.6MB/s
Collecting Logbook==0.7.0
  Downloading Logbook-0.7.0.tar.gz (147kB)
    100% |████████████████████████████████| 147kB 2.9MB/s
Collecting Mako==1.0.0
  Downloading Mako-1.0.0.tar.gz (470kB)
    100% |████████████████████████████████| 471kB 710kB/s
Collecting Markdown==2.5.1
  Downloading Markdown-2.5.1.tar.gz (288kB)
    100% |████████████████████████████████| 290kB 1.7MB/s
Collecting Mezzanine==3.1.10
  Downloading Mezzanine-3.1.10-py2.py3-none-any.whl (5.7MB)
    100% |████████████████████████████████| 5.7MB 80kB/s
Collecting Nikola==7.1.0
  Downloading nikola-7.1.0.tar.gz (1.5MB)
    100% |████████████████████████████████| 1.5MB 306kB/s
Collecting Paste==<IP_ADDRESS>
  Downloading Paste-<IP_ADDRESS>.tar.gz (523kB)
    100% |████████████████████████████████| 524kB 937kB/s
Collecting Pillow==2.5.3
  Downloading Pillow-2.5.3.zip (6.9MB)
    100% |████████████████████████████████| 6.9MB 68kB/s
Collecting PyMySQL==0.6.2
  Downloading PyMySQL-0.6.2-py2.py3-none-any.whl (63kB)
    100% |████████████████████████████████| 65kB 6.3MB/s
Collecting Pygments==1.6
  Downloading Pygments-1.6.tar.gz (1.4MB)
    100% |████████████████████████████████| 1.4MB 305kB/s
Collecting Pyro4==4.28
  Downloading Pyro4-4.28-py2.py3-none-any.whl (141kB)
    100% |████████████████████████████████| 143kB 1.3MB/s
Collecting RBTools==0.6.2
  Could not find a version that satisfies the requirement RBTools==0.6.2 (from versions: 0.7.5)
No matching distribution found for RBTools==0.6.2
Traceback (most recent call last):
  File "/usr/local/bin/pip-sync", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/piptools/scripts/sync.py", line 68, in cli
    pip_flags=pip_flags))
  File "/usr/local/lib/python2.7/site-packages/piptools/sync.py", line 145, in sync
    check_call(['pip', 'install'] + pip_flags + sorted(to_install))
  File "/usr/local/lib/python2.7/subprocess.py", line 511, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['pip', 'install', 'Beaker==1.6.4', 'Cython==0.21', 'Django==1.7', 'Fabric==1.10.0', 'Jinja2==2.7.3', 'Logbook==0.7.0', 'Mako==1.0.0', 'Markdown==2.5.1', 'Mezzanine==3.1.10', 'Nikola==7.1.0', 'Paste==<IP_ADDRESS>', 'Pillow==2.5.3', 'PyMySQL==0.6.2', 'Pygments==1.6', 'Pyro4==4.28', 'RBTools==0.6.2', 'Radicale==0.9', 'SQLAlchemy==0.9.7', 'Scrapy==0.22.0', 'South==1.0', 'Sphinx==1.2.3', 'Trac==1.0.1', 'Twisted==14.0.2', 'Unidecode==0.04.16', 'WTForms==2.0.1', 'WebOb==1.4', 'WebTest==2.0.16', 'Werkzeug==0.9.6', 'Whoosh==2.5.7', 'Yapsy==1.10.423', 'argh==0.25.0', 'argparse==1.2.1', 'aspen==0.34', 'backports.ssl-match-hostname==<IP_ADDRESS>', 'beautifulsoup4==4.3.2', 'bleach==1.4', 'blinker==1.3', 'bootstrap-admin==0.3.0', 'buildbot==0.8.9', 'certifi==14.05.14', 'colorama==0.3.2', 'commando==0.3.4', 'cssutils==1.0', 'decorator==3.4.0', 'django-admin-tools==0.5.2', 'django-ajax-selects==1.3.5', 'django-appconf==0.6', 'django-autofixture==0.9.1', 'django-autoslug==1.7.2', 'django-classy-tags==0.5.1', 'django-compressor==1.4', 'django-crispy-forms==1.4.0', 'django-dajaxice==0.6', 'django-debug-toolbar==1.2.1', 'django-evolution==0.6.9', 'django-extensions==1.4.0', 'django-facebook==6.0.1', 'django-fluent-dashboard==0.3.6', 'django-geoip==0.5.1', 'django-inplaceedit==1.3.0', 'django-jsonfield==0.9.13', 'django-mptt==0.6.1', 'django-notification==1.2.0', 'django-pdb==0.4.0', 'django-pipeline==1.3.25', 'django-registration==1.0', 'django-rosetta==0.7.4', 'django-simple-captcha==0.4.2', 'django-su==0.4.7', 'django-tagging==0.3.2', 'django-tastypie==0.12.0', 'django-threadedcomments==0.9.0', 'django-tinymce==1.5.3', 'doit==0.26.0', 'dynpool==1.0.5', 'easy-thumbnails==2.1', 'ecdsa==0.11', 'eventlet==0.15.2', 'feedparser==5.1.3', 'filebrowser-safe==0.3.6', 'filesystem-tree==1.0.1', 'fswrap==0.1.2', 'future==0.13.1', 'futures==2.2.0', 'grappelli-safe==0.3.13', 'greenlet==0.4.4', 'html5lib==0.999', 'httplib2==0.9', 'hyde==0.8.8', 'lockfile==0.10.2', 'mailer==0.7', 'natsort==3.5.1', 'nose==1.3.4', 'numpy==1.9.0', 'oauth2==1.5.211', 'oauthlib==0.6.3', 'paramiko==1.15.1', 'pbr==0.10.0', 'pecan==0.7.0', 'pelican==3.4.0', 'pep8==1.5.7', 'pexif==0.13', 'pip-tools==0.3.5', 'polib==1.0.5', 'progressbar==2.3dev', 'pyactiveresource==2.1.0', 'pyinotify==0.9.4', 'pymongo==2.7.2', 'pyparsing==2.0.2', 'pysqlite==2.6.3', 'python-daemon==1.5.5', 'python-dateutil==2.2', 'python-memcached==1.53', 'python-twitter==2.0', 'pytz==2014.7', 'queuelib==1.2.2', 'raven==5.0.0', 'reportlab==3.1.8', 'requests-oauthlib==0.4.1', 'requests==2.4.1', 'serpent==1.7', 'simplejson==3.6.3', 'six==1.8.0', 'sorl-thumbnail==11.12.1b', 'sqlalchemy-migrate==0.9.2', 'sqlparse==0.1.12', 'tornado==4.0.2', 'tzlocal==1.1.1', 'virtualenv==1.11.6', 'w3lib==1.10.0', 'waitress==0.8.9', 'watchdog==0.8.1', 'wsgiref==0.1.2']' returned non-zero exit status 1

This was a while ago. I'll close for now. If a similar issue still occurs with the latest version, fell free to reopen with your requirements.in/txt.

@vphilippon I would like that you reopen, after update again all the packages, I get the following now:
# pip-sync
Traceback (most recent call last):
  File "/usr/local/bin/pip-sync", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/piptools/scripts/sync.py", line 53, in cli
    requirements = sync.merge(requirements, ignore_conflicts=force)
  File "/usr/local/lib/python2.7/site-packages/piptools/sync.py", line 73, in merge
    key = ireq.link or ireq.req.key
AttributeError: 'Requirement' object has no attribute 'key'

That's a different issue, yet a known issue that should be fixed in the upcoming v1.10.
I'll reopen for tracking purposes.

Not sure which is the proper way to update, since it seems revert back to 1.4.2:
[~]# pip install --upgrade pip
Requirement already up-to-date: pip in /usr/local/lib/python2.7/site-packages
[~]# pip install pip-tools
Requirement already satisfied: pip-tools in /usr/local/lib/python2.7/site-packages
Requirement already satisfied: first in /usr/local/lib/python2.7/site-packages (from pip-tools)
Requirement already satisfied: click>=6 in /usr/local/lib/python2.7/site-packages (from pip-tools)
Requirement already satisfied: six in /usr/local/lib/python2.7/site-packages (from pip-tools)
[~]# pip install -U  pip-tools
Collecting pip-tools
  Downloading pip_tools-1.10.1-py2.py3-none-any.whl
Collecting setuptools (from pip-tools)
  Downloading setuptools-36.5.0-py2.py3-none-any.whl (478kB)
    100% |████████████████████████████████| 481kB 868kB/s
Requirement already up-to-date: first in /usr/local/lib/python2.7/site-packages (from pip-tools)
Collecting click>=6 (from pip-tools)
  Downloading click-6.7-py2.py3-none-any.whl (71kB)
    100% |████████████████████████████████| 71kB 5.0MB/s
Collecting six (from pip-tools)
  Downloading six-1.11.0-py2.py3-none-any.whl
Installing collected packages: setuptools, click, six, pip-tools
  Found existing installation: setuptools 28.8.0
    Uninstalling setuptools-28.8.0:
      Successfully uninstalled setuptools-28.8.0
  Found existing installation: click 6.2
    Uninstalling click-6.2:
      Successfully uninstalled click-6.2
  Found existing installation: six 1.10.0
    Uninstalling six-1.10.0:
      Successfully uninstalled six-1.10.0
  Found existing installation: pip-tools 1.4.2
    Uninstalling pip-tools-1.4.2:
      Successfully uninstalled pip-tools-1.4.2
Successfully installed click-6.7 pip-tools-1.10.1 setuptools-36.5.0 six-1.11.0
[~]# pip-sync
Uninstalling cycler-0.10.0:
  Successfully uninstalled cycler-0.10.0
Uninstalling pycrypto-2.6.1:
  Successfully uninstalled pycrypto-2.6.1
Not uninstalling wsgiref at /usr/local/lib/python2.7, as it is in the standard library.
Collecting click==6.2
  Using cached click-6.2-py2.py3-none-any.whl
Collecting pip-tools==1.4.2
  Using cached pip_tools-1.4.2-py2.py3-none-any.whl
Collecting six==1.10.0
  Downloading six-1.10.0-py2.py3-none-any.whl
Requirement already satisfied: first in /usr/local/lib/python2.7/site-packages (from pip-tools==1.4.2)
Installing collected packages: click, six, pip-tools
  Found existing installation: click 6.7
    Uninstalling click-6.7:
      Successfully uninstalled click-6.7
  Found existing installation: six 1.11.0
    Uninstalling six-1.11.0:
      Successfully uninstalled six-1.11.0
  Found existing installation: pip-tools 1.10.1
    Uninstalling pip-tools-1.10.1:
      Successfully uninstalled pip-tools-1.10.1
Successfully installed click-6.2 pip-tools-1.4.2 six-1.10.0
[~]# pip-sync
Traceback (most recent call last):
  File "/usr/local/bin/pip-sync", line 11, in <module>
    sys.exit(cli())
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 716, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 696, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 889, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python2.7/site-packages/click/core.py", line 534, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/piptools/scripts/sync.py", line 53, in cli
    requirements = sync.merge(requirements, ignore_conflicts=force)
  File "/usr/local/lib/python2.7/site-packages/piptools/sync.py", line 73, in merge
    key = ireq.link or ireq.req.key
AttributeError: 'Requirement' object has no attribute 'key'

pip-tools seems to be in the requirements.txt, pinned to 1.4.2. Either it got included by mistake by a previous pip-tools version, or it's in your requirement.in.
So
1 - Make sure pip-tools is not in your requirements.in*
2 - Re-run pip-compile to freshen your requirements.txt
3 - Run pip-sync

If you actually want to have pip-tools in your requirements.in (and know what you're doing), then keep it, but run pip-compile --upgrade-package pip-tools, then run pip-sync.

I only have a requirements.txt file. After remove pip-tools 1.4.2 from the requirements file and update pip-tools to latest, when I run pip-sync, it seems to work perfectly now without traces.

Allrighty, I'm glad you're on the road.
Closing

I would like to re-open this. I am attempting to run this while building a Docker image based on python:3.10.3-bullseye. It breaks intermittently. pip-compile prints:
#15 7.764 Traceback (most recent call last):
#15 7.764   File "/venv/bin/pip-compile", line 8, in <module>
#15 7.764     sys.exit(cli())
#15 7.764   File "/venv/lib/python3.10/site-packages/click/core.py", line 1130, in __call__
#15 7.765     return self.main(*args, **kwargs)
#15 7.765   File "/venv/lib/python3.10/site-packages/click/core.py", line 1055, in main
#15 7.765     rv = self.invoke(ctx)
#15 7.765   File "/venv/lib/python3.10/site-packages/click/core.py", line 1404, in invoke
#15 7.765     return ctx.invoke(self.callback, **ctx.params)
#15 7.765   File "/venv/lib/python3.10/site-packages/click/core.py", line 760, in invoke
#15 7.766     return __callback(*args, **kwargs)
#15 7.766   File "/venv/lib/python3.10/site-packages/click/decorators.py", line 26, in new_func
#15 7.766     return f(get_current_context(), *args, **kwargs)
#15 7.766   File "/venv/lib/python3.10/site-packages/piptools/scripts/compile.py", line 408, in cli
#15 7.766     dist = meta.load(os.path.dirname(os.path.abspath(src_file)))
#15 7.766   File "/venv/lib/python3.10/site-packages/pep517/meta.py", line 71, in load
#15 7.766     path = Path(build_as_zip(builder))
#15 7.766   File "/venv/lib/python3.10/site-packages/pep517/meta.py", line 58, in build_as_zip
#15 7.766     builder(dest=out_dir)
#15 7.766   File "/venv/lib/python3.10/site-packages/pep517/meta.py", line 53, in build
#15 7.766     _prep_meta(hooks, env, dest)
#15 7.766   File "/venv/lib/python3.10/site-packages/pep517/meta.py", line 28, in _prep_meta
#15 7.766     reqs = hooks.get_requires_for_build_wheel({})
#15 7.766   File "/venv/lib/python3.10/site-packages/pep517/wrappers.py", line 172, in get_requires_for_build_wheel
#15 7.766     return self._call_hook('get_requires_for_build_wheel', {
#15 7.766   File "/venv/lib/python3.10/site-packages/pep517/wrappers.py", line 322, in _call_hook
#15 7.767     self._subprocess_runner(
#15 7.767   File "/venv/lib/python3.10/site-packages/pep517/wrappers.py", line 75, in quiet_subprocess_runner
#15 7.767     check_output(cmd, cwd=cwd, env=env, stderr=STDOUT)
#15 7.767   File "/usr/local/lib/python3.10/subprocess.py", line 420, in check_output
#15 7.767     return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
#15 7.767   File "/usr/local/lib/python3.10/subprocess.py", line 524, in run
#15 7.767     raise CalledProcessError(retcode, process.args,
#15 7.767 subprocess.CalledProcessError: Comm
[Dockerfile.txt](https://github.com/jazzband/pip-tools/files/8391959/Dockerfile.txt)
and '['/venv/bin/python3', '/venv/lib/python3.10/site-packages/pep517/in_process/_in_process.py', 'get_requires_for_build_wheel', '/tmp/tmp_pbx08qh']' returned non-zero exit status 1.
------
failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Unknown desc = failed to build LLB: executor failed running [/bin/sh -c pip install pip-tools     && pip-compile --generate-hashes     && pip install -r requirements.txt     && pip install pytest black]: runc did not terminate sucessfully
make: *** [image] Error 1

I uploaded my dockerfile as Dockerfile.txt (so the file uploader would accept it).

@lsiden Please share your setup.py, it may not be quite valid with current versions of setuptools. You may want to look at these comments.

@lsiden Please note that this issue is very old, and was created for a problem encountered in usage of pip-sync, while your issue occurs during pip-compile.
I think probably it's the same stuff discussed at #1603, but if it's not, please open a new issue. Thanks!


Sketch: Fill, Opacity, and Stroke

Issue #474
Done:

Fill Feature
Stroke Feature
Opacity Feature
Improved Arrow Shape

Next:

I would Like to implement Undo and Redo feature.
I would Like to redesign the Sketch Layout.

WOC:

I have participate in DWOC, SWOC, MWOC, and CrossWOC.

Screenshots

Opacity

Stroke

Fill

Improved Arrow Shape

Feedback:

For the stroke style, we need an option for going back to the usual stroke style ( ___) from the other two
Keep the opacity only for the fill color and not the boundary of the shapes
For the Fill Color, try to add an option for selecting the color using color picker
It would be great if you could add some descriptive icons(like Stroke Style, Stroke Width, Opacity, Fill Color, Stroke Color  ) so that the menu bar is easy to understand


AdMob.createBanner  stop the app functions

Banner and interstitial working fine but when we use function AdMob.createBanner it stop the app. Once banner is loaded app functions running fine. Please help me about this issue.

What happened as you mentioned when "it stops the app"? And, which platform please, iOS or Android?

it stop the app function for example all buttons not work, i am using android platform

It may take some CPU time for network activity to load ad resource from Google AdMob server.

How we handle this issue?

+1 for this issue, this issue give my client a teribble UX, do you have any workaround? using timeout has no effect

You may try using time of the splash screen to initialize the banner.

Hi,
I think the 'stop' problem is related to these issues: #370 (reported by me several months ago) and #403.
I myself still using the older version of the plugin (cordova-plugin-admobpro v2.12.0 and cordova-plugin-extension v1.2.9), the last known version without the stop/freeze problem.
@floatinghotpot Please kindly solve this issue. Thanks.


ilm:1.1.2

I am submitting

[ ] a new package
[x] an update for a package

Changelog

Improve template and removed old config options.

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Thanks!


Update claims in TokenService and add mobile phone claim

Fix for #1049 thanks to @kallievz
I've checked this and it works. I'm simply creating a pull request with a fix from @kallievz
Description:
Replaced JwtRegisteredClaimNames with ClaimTypes for NameIdentifier, Email, and Name in the GetClaims method. Added a new claim for ClaimTypes.MobilePhone to include the user's phone number.

It also fixes #1050


VSCode 1.44.2 stops working via proxy

VSCode Version: 1.44.2
OS Version: Windows 7, Windows 10, x64

Steps to Reproduce:

You need to work behind a proxy.
Install VSCode 1.43.1 (User)
Set up proxy settings in Settings, Http:Proxy e.g. "http://user:password@my.proxy.com:8080"
Click Help->Check for Updates... and wait "new version available" notification
Click "Restart to update"
After restart, make sure if you use 1.44.2 version
Also make sure if proxy settings are the same
Click Help->Check for Updates... and get "net::ERR_PROXY_CONNECTION_FAILED" error

Does this issue occur when all extensions are disabled?: No extensions installed.

Same problem here.
VS Code version 1.44.2
Windows 10 1909 18363.720
Problem: Can not install extensions, and get "net::ERR_PROXY_CONNECTION_FAILED" error, no matter a proxy is set in settings.json or not. Behind a proxy, it just won't work normal as usual. Switching to network not required with a proxy works fine.
After uninstalling this version(1.44.2) and clear all the VS Code config files in ~/.vscode and User/AppData/Roaming/Code, I tried installing version 1.45.0 insider, still not working behind a proxy. Uninstall it, then reinstall version 1.44.1, it works behind a proxy! But then it auto updated again... So I have to reinstall it again and set update.mode = none...

I'm not seeing anything obviously proxy-related in the diffs between 1.44.1 and 1.44.2
https://github.com/microsoft/vscode/compare/1.44.1...1.44.2

The user setting http.proxy doesn't affect extension or VS Code downloads in 1.43 or 1.44. (It will with 1.45.)
@deepak1556 Are you aware of changes between 1.43 and 1.44 that could affect proxy handling?
@Ynewtime Can you confirm it works with 1.44.1? Did you mean 1.43.1?

There was no updates to the electron runtime between 1.43 and 1.44. This definitely seems like an error from the user system.
@Ynewtime does the proxy setup work with chrome/edge on your system ? Did you try configuring the proxy at the system level instead of defining http.proxy variable ?

@deepak1556 Taking into account that there were no changes except VSCode update, and there were no such errors fot all updates before 1.44.2, which kind of an error from the user system do you mean?

net::ERR_PROXY_CONNECTION_FAILED usually refers to an unreachable proxy server. Can you confirm if other applications like chrome/edge are operating with the proxy ?
Can you also launch code with --log-net-log=<path>/netlog.json and attach the log here.

Same problem behind a corporate proxy needing authentication (kerberos but no totally sure about that).
Usually my vscode uses the proxy through http_proxy / https_proxy environment variable and is was working fine (version check / update / extension / ...) until recently (probably because of the last insider version update I installed, i was stuck to 1.45 of 17 april).
I tested to use instead px proxy (https://github.com/genotrance/px) that act as a proxy handling the authentication to the corporate proxy and HTTPS_PROXY=http://localhost:3128 (same for http_proxy variable) and it's working as a workaroung waiting the fix.
VSCode -> read http[s]_proxy env variable -> connect to localhost px proxy -> authenticate to corporate proxy -> internet
My current insider version is based on electron 7.2.2, next version 7.2.3(https://github.com/electron/electron/releases/tag/v7.2.3) is mentioning : Security: Ensure proxy object is created in the correct context a9bead2, may be it is the cause...
May be upgrading to electron v7.2.3 for 1.45 is enough instead of waiting bigger electron v8 upgrade (as mentioned in https://github.com/microsoft/vscode/issues/94862)

@s-kocher can you open a new issue with the relevant details, of when did this issue start, what was the last known working version.
Also can you launch code with --log-net-log=netlog.json , perform some requests (search extensions, update check) and attach the generated log file in the new issue.
7.2.3 release has nothing to do with any network related operations, please ignore it.

I've also faced this issue and latest insider build seems fixed it.
Version: 1.45.0-insider
Commit: bd262894bbaac5156d5bf832160b7056c91decea
Date: 2020-04-22T17:16:24.886Z
Electron: 7.2.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.17763

@s-kocher can you try the latest insiders , I think your case should be addressed by https://github.com/microsoft/vscode/issues/94862#issuecomment-617630954

The user setting http.proxy doesn't affect extension or VS Code downloads in 1.43 or 1.44. (It will with 1.45.)
@deepak1556 Are you aware of changes between 1.43 and 1.44 that could affect proxy handling?
@Ynewtime Can you confirm it works with 1.44.1? Did you mean 1.43.1?

Yes, it works with 1.44.1. I am using it right now(with proxy).

There was no updates to the electron runtime between 1.43 and 1.44. This definitely seems like an error from the user system.
@Ynewtime does the proxy setup work with chrome/edge on your system ? Did you try configuring the proxy at the system level instead of defining http.proxy variable ?

Actually, no proxy setup needed to work with chrome/edge, which means no matter I setup a proxy a not, behind my company's proxy, chrome will always work.

For more information:
Sorry for the delay. I test 1.44.2 today and it works behind the proxy! Installing extensions and checking for updates, etc., both work now as usual.
Version: 1.44.2 (user setup)
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T16:36:23.138Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

No proxy config was set though, no matter in settings.json, system level proxy or http[s]_proxy environment, I am not sure if this issue was resolved by my company's IT system or not. But now behind proxy, 1.44.1 and 1.44.2 works.
BTW, I have some powershell proxy configs to solve the SSL certification failed issues because my company use self-signed certifications. I don't know if this would help though:
[System.Net.WebRequest]::DefaultWebProxy = [System.Net.WebRequest]::GetSystemWebProxy()
[System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials

And I also install the 1.45.0-insiders to test if it work behind the proxy, unfortunately, it doesn't. Same net::ERR_PROXY_CONNECTION_FAILED error.
Version: 1.45.0-insider (user setup)
Commit: bd262894bbaac5156d5bf832160b7056c91decea
Date: 2020-04-22T17:16:24.886Z
Electron: 7.2.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

@deepak1556
After the last @Ynewtime message, I tried to reproduce the issue again and couldn't. VSCode 1.44.2 now works with proxy for me.
So my initial problem is gone now. Thanks!

@Ynewtime Do you have HTTP_PROXY, HTTPS_PROXY or NO_PROXY environment variables set? Could you retry with todays insiders build (that has a small fix)?

@Ynewtime Do you have HTTP_PROXY, HTTPS_PROXY or NO_PROXY environment variables set? Could you retry with todays insiders build (that has a small fix)?

No, not working, with or without proxy environment variables(i.e. system http_proxy and https_proxy). Same error. I would like to post a screenshot but I am not allowed to upload files without permission, sorry.
Version: 1.45.0-insider (user setup)
Commit: 0778354f3a6a2c21b7f738a5e6b02e2f1c765e73
Date: 2020-04-27T05:42:11.567Z
Electron: 7.2.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Log(Window) output:
[2020-04-28 08:05:55.477] [renderer1] [error] net::ERR_PROXY_CONNECTION_FAILED: Error: net::ERR_PROXY_CONNECTION_FAILED
    at SimpleURLLoaderWrapper.<anonymous> (electron/js2c/browser_init.js:2623:21)
    at SimpleURLLoaderWrapper.emit (events.js:203:13)

Extensions sidebar output:
We cannot connect to the Extensions Marketplace at this time, please try again later.

@Ynewtime Can you launch code with --log-net-log=netlog.json, perform some requests (search extensions, update check) and attach the generated log file?

@Ynewtime Can you launch code with --log-net-log=netlog.json, perform some requests (search extensions, update check) and attach the generated log file?

Problem solved, must be my company's proxy issue. My company provide proxies for different regions, I used to use the HK one and encoutered with the ERR_PROXY_CONNECTION_FAILED error with insiders version, but after I switched to different proxy, the error appear no more. So this should be my problem. And thanks for your patience!

Thanks. Marking as duplicate of #94862 where we solved an issue with 1.44.

I had the same problem, but something seems to have changed on the Windows side... I used a local script for automatic proxy settings, it worked for a long time, but a few weeks ago I installed an update for Windows and then I had to switch the proxy settings to "Automatically detect settings" and from then on everything works properly, including VS code


Add EntitiesQuery

Todos

[x] Filter out the following types in the SQL query (the type is stored in the sql table type):

+-----------------------------------------+
| name                                    |
+-----------------------------------------+
| applet                                  |
| article                                 |
| course                                  |
| text-exercise                           |
| text-exercise-group                     |
| video                                   |
+-----------------------------------------+

[x] Filter out trashed objects (the property trashed is stored in the column uuid.trashed)
[ ] Filter out entities from a configurable list of taxonomies / the following construct can help: https://github.com/serlo/serlo.org-database-layer/blob/099c7241b3bbc8f36e3ebc1c6e1b0f2bf629e669/src/uuid/model/taxonomy_term.rs#L168-L197

[ ] Everything under https://de.serlo.org/community/87993/community (taxonomy_term.id == 87993) besides everything under https://de.serlo.org/community/106081/neue-fächer-und-themen (taxonomy_term.id == 106081)
[ ] Everything under https://de.serlo.org/informatik/75211/baustelle (taxonomy_term.id == 75211)

[x] Add Parameter "instance" (optional) which filters for the instance (= column instance.subdomain)
[x] Parameter "first" which determine the number of returned values (should be smaller then 10_000, otherwise there shall be an error)
[x] Add Parameter "lastModified" and return only entites last modified after this date

Note: There a still things to consider before we can finish this task. However we know for sure that we need the above features.

[X] Add feature tests

The output shall be changed from a dict of the form { entityIds: number[] } to a dict { entitties: object[] }. The objects shall the same as in https://nbviewer.org/github/serlo/evaluations/blob/2f19c47fa4ca91cb80ac77f29407edf1f6c3f617/Export of metadata to BIRD.ipynb#Fetching-metadata-from-the-DB The code also contains SQL statements and methods how to compute the values.


New guideline: usage of gateways

We want to have a general guideline about usage of API gateways. The main question is whether we generally want to describe the API "before" or "behind" the gateway?

Gateway usage should be "transparent" (in either of the two meanings):

either have the gateway invisible, i.e. only document what's outside of the gateway
or have it clearly documented, i.e. for each header/... make it clear whether it's applicable inside/outside of the gateway.

SHOULD document external (client-side) view
MAY also document view "behind the gateway", if it's intended to be called that way

if so, make it clear which headers normally come from the gateway (and should not be provided when using the gateway)

From the meeting:

This should go into the "General Guidelines" section, possibly after rule 101.

Happy birthday :tada:

We got several cases during the last few years where this rule would have been useful. We just should add it.


Modrinth page needs to be updated to add 1.19 as a supported version

The 1.18.2 version works in 1.19, suggesting that 1.19 be added to Minecraft versions supported on the Modrinth page

done


Blind fix for exclude warnings for SPM

Removes the excluded folders from the SPM package manifest.

FYI this hasn't been tested yet, I was also putting it up to see what kind of permissions I had on this repo. 😄

@downie-hatch Once you merge this, you'll need to tag a release version for it, then update the version consumed in our repo, then these warnings should go away.
Thanks for doing this!  There is a ticket for this, btw.

@downie-hatch @scottmarchant
Our repo is currently pointing to a commit, not a tag. We should probably fix this in this MR though and use a tag. Will need to rebase this change onto the commit has in the image here.

I think this jist of this PR has already been merged into master. I bet if you pull the lastest into this MR that it will be equivalent. master has the exclude file list commented out (not fully removed). But same thing.
https://github.com/hatch-baby/EasyTipView/blob/master/Package.swift
I think this PR can be closed.

Closing this PR. This fix already exists in master. This PR is also 9 months old.


[BUG] =mu4e: Cannot open load file: No such file or directory, mu4e

The load-path list seems incomplete for mu4e.

Have you installed mu on your system? See email/mu4e/README.org

Thank you for the quick reply.
mu is properly installed. I just figured out that the mu4e.el is installed into /usr/share/emacs/site-lisp/mu4e/.
I'm uncertain whether this is always the default directory and thus adding it to the load-path by default is save, but at least there should be some hint in the README.org, that load-path may have to be adjusted.

Adjusting your load-path shouldn't be necessary. Emacs should pre-populate load-path with the directories in /usr/share/emacs/site-lisp/* (but you need to run doom refresh to ensure this new value for load-path is correctly cached).

That was probably it. I didn't run doom refresh!


ng test ends with "Executed 0 of 0 ERROR"

I'm using Windows 10 (10.0.14388.0 (rs1_release.160709-1635)), node 6.9.1 and angular-cli 1.0.0-beta.18.
I created a new ng project with angular-cli and ran ng test. I got the following output:
λ ng test
23 10 2016 10:52:02.889:WARN [karma]: No captured browser, open http://localhost:9876/
23 10 2016 10:52:02.897:INFO [karma]: Karma v1.2.0 server started at http://localhost:9876/
23 10 2016 10:52:02.898:INFO [launcher]: Launching browser Chrome with unlimited concurrency
23 10 2016 10:52:02.909:INFO [launcher]: Starting browser Chrome
23 10 2016 10:52:03.840:INFO [Chrome 55.0.2883 (Windows 10 0.0.0)]: Connected on socket /#1G7vpI_QqAJgLKdyAAAA with id 55321352
Chrome 55.0.2883 (Windows 10 0.0.0): Executed 0 of 0 ERROR (0.003 secs / 0 secs)

I can't see any actual error message from the command line or from Karma's Chrome instance's console.
UPDATE: Actually this might be related to the warning "No capture browser" even though browser seems to open just fine.

More info: I managed to get tests running with PhantomJS. Here's a diff of changes I applied on top of clean new project created by angular-cli:
λ git diff
warning: LF will be replaced by CRLF in karma.conf.js.
The file will have its original line endings in your working directory.
diff --git a/karma.conf.js b/karma.conf.js
index e28922a..1e68bfe 100644
--- a/karma.conf.js
+++ b/karma.conf.js
@@ -7,7 +7,7 @@ module.exports = function (config) {
     frameworks: ['jasmine', 'angular-cli'],
     plugins: [
       require('karma-jasmine'),
-      require('karma-chrome-launcher'),
+      require('karma-phantomjs-launcher'),
       require('karma-remap-istanbul'),
       require('angular-cli/plugins/karma')
     ],
@@ -32,7 +32,7 @@ module.exports = function (config) {
     colors: true,
     logLevel: config.LOG_INFO,
     autoWatch: true,
-    browsers: ['Chrome'],
+    browsers: ['PhantomJS'],
     singleRun: false
   });
 };
diff --git a/package.json b/package.json
index 49045ee..47ba454 100644
--- a/package.json
+++ b/package.json
@@ -36,6 +36,7 @@
     "karma-chrome-launcher": "^2.0.0",
     "karma-cli": "^1.0.1",
     "karma-jasmine": "^1.0.2",
+    "karma-phantomjs-launcher": "^1.0.2",
     "karma-remap-istanbul": "^0.2.1",
     "protractor": "4.0.9",
     "ts-node": "1.2.1",
warning: LF will be replaced by CRLF in package.json.
The file will have its original line endings in your working directory.

And here's output from ng test after these changes:
λ ng test
23 10 2016 11:20:32.271:WARN [karma]: No captured browser, open http://localhost:9876/
23 10 2016 11:20:32.280:INFO [karma]: Karma v1.2.0 server started at http://localhost:9876/
23 10 2016 11:20:32.281:INFO [launcher]: Launching browser PhantomJS with unlimited concurrency
23 10 2016 11:20:32.291:INFO [launcher]: Starting browser PhantomJS
23 10 2016 11:20:33.757:INFO [PhantomJS 2.1.1 (Windows 8 0.0.0)]: Connected on socket /#qeFdT5g9lMDdgEyrAAAA with id 10589115
PhantomJS 2.1.1 (Windows 8 0.0.0): Executed 3 of 3 SUCCESS (0.157 secs / 0.526 secs)

Any ideas what's wrong? Can this problem be reproduced on Linux or macOS?

I have this problem on macOS Sierra

@erikdonohoo Your hunch was correct. I created a new project with angular-cli beta 18 and Chrome 54 and it ran fine:
24 10 2016 12:18:39.227:WARN [karma]: No captured browser, open http://localhost:9876/
24 10 2016 12:18:39.235:WARN [karma]: Port 9876 in use
24 10 2016 12:18:39.237:INFO [karma]: Karma v1.2.0 server started at http://localhost:9877/
24 10 2016 12:18:39.238:INFO [launcher]: Launching browser Chrome with unlimited concurrency
24 10 2016 12:18:39.294:INFO [launcher]: Starting browser Chrome
24 10 2016 12:18:41.182:INFO [Chrome 54.0.2840 (Windows 10 0.0.0)]: Connected on socket /#ocdvVd7R6QGHxgnXAAAA with id 96648423
Chrome 54.0.2840 (Windows 10 0.0.0): Executed 3 of 3 SUCCESS (0.157 secs / 0.15 secs)

As soon as I updated to Chrome 55 (which is beta btw), I managed to reproduce the problem:
24 10 2016 12:33:06.002:WARN [karma]: No captured browser, open http://localhost:9876/
24 10 2016 12:33:06.015:INFO [karma]: Karma v1.2.0 server started at http://localhost:9876/
24 10 2016 12:33:06.016:INFO [launcher]: Launching browser Chrome with unlimited concurrency
24 10 2016 12:33:06.026:INFO [launcher]: Starting browser Chrome
24 10 2016 12:33:07.530:INFO [Chrome 55.0.2883 (Windows 10 0.0.0)]: Connected on socket /#nw4KgkJ_-Xo5O9ziAAAA with id 82518644
Chrome 55.0.2883 (Windows 10 0.0.0): Executed 0 of 0 ERROR (0.003 secs / 0 secs)

There seems to be something strange with the configuration generated with angular-cli. I have another proprietary project which isn't generated with angular-cli and with it Karma runs tests in Chrome 55 just fine:
> karma start --browsers Chrome

24 10 2016 12:33:49.025:INFO [preprocessor.karma-typescript]: Using Typescript 2.0.3
24 10 2016 12:33:51.167:WARN [karma]: No captured browser, open http://localhost:9876/
24 10 2016 12:33:51.176:INFO [karma]: Karma v1.3.0 server started at http://localhost:9876/
24 10 2016 12:33:51.176:INFO [launcher]: Launching browser Chrome with unlimited concurrency
24 10 2016 12:33:51.237:INFO [launcher]: Starting browser Chrome
24 10 2016 12:33:51.890:INFO [Chrome 55.0.2883 (Windows 10 0.0.0)]: Connected on socket /#VJ7Qv4cFsOzTneT4AAAA with id 17303171
Chrome 55.0.2883 (Windows 10 0.0.0): Executed 102 of 102 SUCCESS (0.273 secs / 0.219 secs)

As this is a proprietary project, I'm not at liberty to provide a public repo but here are package.json and karma.conf.js from that project if they provide any additional insight: https://gist.github.com/VilleSalonen/ad5b4c9b442d810ffcbff39faac8a868
I tested whether the problem is with Karma v1.2.0 used by angular-cli's configuration by upgrading manually to v1.3.0 but the problem persists:
24 10 2016 12:35:40.720:WARN [karma]: No captured browser, open http://localhost:9876/
24 10 2016 12:35:40.728:INFO [karma]: Karma v1.3.0 server started at http://localhost:9876/
24 10 2016 12:35:40.730:INFO [launcher]: Launching browser Chrome with unlimited concurrency
24 10 2016 12:35:40.737:INFO [launcher]: Starting browser Chrome
24 10 2016 12:35:42.204:INFO [Chrome 55.0.2883 (Windows 10 0.0.0)]: Connected on socket /#RK-kdDC1XbvATKccAAAA with id 10819690
Chrome 55.0.2883 (Windows 10 0.0.0): Executed 0 of 0 ERROR (0.003 secs / 0 secs)

I suppose the most obvious difference is the Karma version. The CLI doesn't do anything specific regarding tests, it just starts karma and runs a webpack plugin to compile the specs.
Can you test if updating the versions of Karma and plugins used helps with Chrome 55?

@filipesilva I will test that and report back

this one is biting us now that 55 is rolling out...

Just wondering what the status on this is. I upgraded Chrome last night unaware of it and getting the following:
Chrome 55.0.2883 (Mac OS X 10.12.1): Executed 0 of 0 ERROR (0.003 secs / 0 secs)

results when running ng test

that is the status... we're manually rolling back to 54 for now to get around the issue.
I haven't figured out if it's the way the cli configures karma or if it's the karma chrome plugin -- karma-chrome-launcher

I am having this same issue... Attempted upgrade to Karma 1.3.0 and have the same results.

https://github.com/angular/angular-cli/issues/2125
see @jtsom 's answer:
In the karma.conf.js file, add:
 mime: {       'text/x-typescript': ['ts','tsx']     },
works for me.

My patch to add this to the CLI was approved recently - new projects should include it. Older ones will need to add it.

I still have the same error, and in my karma.conf.js I already have the mime defined

mime: { 'text/x-typescript': ['ts','tsx'] }, works for me, thanks @penghuili

This works on Chrome 55.0.2883. Thanks @penghuili

@sebastiannm Many people report that mime setting fixes the problem. Are you sure that it doesn't fix it for you? If you are could you post your whole karm.conf.js?

@VilleSalonen I used the latest angular-cli and that came with it:
// Karma configuration file, see link for more information
// https://karma-runner.github.io/0.13/config/configuration-file.html

module.exports = function (config) {
  config.set({
    basePath: '',
    frameworks: ['jasmine', 'angular-cli'],
    plugins: [
      require('karma-jasmine'),
      require('karma-chrome-launcher'),
      require('karma-remap-istanbul'),
      require('angular-cli/plugins/karma')
    ],
    files: [
      { pattern: './src/test.ts', watched: false }
    ],
    preprocessors: {
      './src/test.ts': ['angular-cli']
    },
    mime: {
      'text/x-typescript': ['ts','tsx']
    },
    remapIstanbulReporter: {
      reports: {
        html: 'coverage',
        lcovonly: './coverage/coverage.lcov'
      }
    },
    angularCli: {
      config: './angular-cli.json',
      environment: 'dev'
    },
    reporters: config.angularCli && config.angularCli.codeCoverage
              ? ['progress', 'karma-remap-istanbul']
              : ['progress'],
    port: 9876,
    colors: true,
    logLevel: config.LOG_INFO,
    autoWatch: true,
    browsers: ['Chrome'],
    singleRun: false
  });
};

@sebastiannm Did you try it on a brand new angular-cli project without making any changes to it? I'm using Windows 10, angular-cli beta 22.1, node 7.2.1 and Chrome 56.0.2924.21 beta (64-bit) and ng test works fine: Chrome 56.0.2924 (Windows 10 0.0.0): Executed 3 of 3 SUCCESS (0.227 secs / 0.221 secs) My karma.conf.js is identical to yours.
What platform are you running on?

@VilleSalonen Ok the issue was on my test, because I migrated from angular-seed and they follow a different structure apparently. So I actually, I had no tests.
Thanks

Okay, good to know. Then the issue has been resolved.

I came across the same problem, Chrome Version: 55.0.2883.87.  Mime Type fixed the problem for me. Thanks a lot for that...

Same here ! :)

Chrome 55 gave me the same problem, thanks for the PhantomJS workaround.  Unfortunately I get automatic updates on my workstation and similar issues happen quite often

For anybody arriving here even though they don't use Angular while searching for this error, adding mime: {       'text/x-typescript': ['ts','tsx']     } to karma.conf.js did indeed fix it for me when using a Chrome version of 55.

I had the same issue in Chrome version 56.
Setting the mime fixed it as well.

Guys, I'm having the same issue, but adding the mime it seems just to get worse: instead of getting "Executed 0 of 0 ERROR" I just get "Chrome 56.0.2924 (Windows 10 0.0.0) ERROR". Anywan having a clue on what's going on?  Thanks!

Same setup and issue for me as @alextorino

had the same error as @alextorino and @utahdoug
tested with both Chrome 56.0.2924 and Firefox 51.0.0
updating Karma and plugins to latest didn't help
tested a fresh ng new foobar (after updating updating angular-cli -g) and ng test ran fine
so did a 'manual' compare between my project and the new foobar-project, updated numerous files, did a clean npm install
it took a while but it works now

Problem is back for me: Chrome 62.0.3202 (Mac OS X 10.13.0): Executed 0 of 0 ERROR (0.003 secs / 0 secs)
.. doing npm test (project is ejected)
Did a ng new karma-test and grabbed the changes I could see (which was few).
Didn't help.

On npm test  I am getting below error -
Chrome 62.0.3202 (Windows 10 0.0.0) ERROR: '[Script Loader]', ReferenceError{}
Chrome 62.0.3202 (Windows 10 0.0.0): Executed 33 of 33 SUCCESS (3.196 secs / 3.132 secs)

Updated angular from 5 to 7 after that tried running test with command ng test and getting error "no spec found" and Chrome 73.0.3683 (Linux 0.0.0): Executed 0 of 0 ERROR (0.029 secs / 0 secs).
Can anyone help me how to fix this? i have tried all possible scenarios to fix this


SyntaxError: Missing parentheses in call to 'print'

Got these errors while executing RATattack.py on windows7
File "D:\HACK\RAT\Windows\RAT-via-Telegram-update\RATAttack.py", line 138
print tofile
SyntaxError: Missing parentheses in call to 'print'
any idea?

This is a Python 2.7 project, you're probably running on 3.x


Increase concurrent requests from HttpSys

There obviously is a limit of how many concurrent requests HttpSys will send in to the pipeline. However we have not been able to find and increase this limit.
The documentation appears very sketchy on this. We have tried adjusting MaxAccepts, but it does not appear to have any effect.
        _host = new WebHostBuilder()
            .UseHttpSys(options =>
            {
                options.Authentication.Schemes = AuthenticationSchemes.NTLM | AuthenticationSchemes.Negotiate;
                options.Authentication.AllowAnonymous = true;
                options.MaxConnections = -1;
                options.MaxAccepts = 200;
            })

On my developer machine it looks like the limit is 28 concurrent requests. How can we increase that?

No, there's not a concurrent request limit. MaxAccepts deals with how many threads are dedicated to pulling requests from Http.Sys and dispatching them to Asp.Net, but the requests are processed asynchronously once dispatched. MaxConnections is the only other limit.
How did you observe your 28 figure? How are you generating load on the client, and with what client?

the requests are processed asynchronously once dispatched.

Ok. So I have 200 threads pulling requests of the request queue. How is the actual work started then? Is that ThreadPool.QueueUserWorkItem(request) ?

How are you generating load on the client, and with what client?

Well in production, we have all kinds of clients, From Excel and SAS scripts to different client systems in C#, C++, Python or Java, I believe we even have a few clients in COBOL :-)

How did you observe your 28 figure?

That was observed in our test-system, I wrote a small C# program which submitted a few hundred requests to the service in less than a millilsecond; Each of them takes about 10 seconds to process. I could see that after the service had started processing 28 requests it did not start processing new ones.
Anyway from you description it sounds like http.sys is not my limitation. We should be able to start plenty of concurrent requests.  Could be our pool of SQL-Connections or another ressource is exhausted.
Before you close this thread, I would appreciate if you could elaborate on how requests are processed asynchronously?
My original confusion about limit on concurrent requests was nicely answered. Thanks

200 is likely overkill for MaxAccepts. 3-5 per CPU is usually adequate.

How is the actual work started then? Is that ThreadPool.QueueUserWorkItem(request)

Yes.
FYI the C# client (HttpClient or HttpWebRequest) does have concurrent request limits that you have to disable.

Each of them takes about 10 seconds to process.

That's pretty expensive. Are they ever blocked synchronously during this time? If so your real bottleneck might be threadpool starvation. If you block existing threads no more work can be scheduled, and new threads are injected slowly.

200 is likely overkill for MaxAccepts. 3-5 per CPU is usually adequate.

Yes got it. I thought it was concurrent requests. You could consider improving your documentation. It is a little sketchy....

FYI the C# client (HttpClient or HttpWebRequest) does have concurrent request limits that you have to disable.

We are using the HttpClient, and I did not know that. Thanks.

That's pretty expensive. Are they ever blocked synchronously during this time?

Yes. They are bulk-requests. So there are actually 50.000 transactions in one request.
We try to use Task and async everywhere. But I will comb our code for any synchronous work.
Thanks. I now understand that there is no limit (at least no obvious limit) on concurrent requests.

We can adjust total number of allowed connection with the MaxConnections property
Is it also possible to adjust the number of connections allowed for a single client?
To mitigate a Slowloris attack
https://en.wikipedia.org/wiki/Slowloris_(computer_security)#Mitigating_the_Slowloris_attack
"While there are no reliable configurations of the affected web servers that will prevent the Slowloris attack, there are ways to mitigate or reduce the impact of such an attack. In general, these involve increasing the maximum number of clients the server will allow, limiting the number of connections a single IP address is allowed to make"

Is it also possible to adjust the number of connections allowed for a single client?

Nothing built in, you'd have to do that manually in middleware. Nor do I see how that's much of a mitigation.
The built in mitigation for slowloris is to ensure the client sends and receives at a minimum data rate.

The concurrent request limits you mentioned, must be on the servicepoint manager, right ?
DefaultConnectionLimit

On .NET 4.x yes. Core has a different implementation.

To anyone struggling with the same issue of not enough concurrency in request processing, I finally figured this one out.
The problem is easily visualized. Just add middleware something like this to your pipeline:
public class CountRequests : IMiddleware
{
    private static long _count = 0;
    private static long _totalCount = 0;

    public async Task InvokeAsync(HttpContext context, RequestDelegate next)
    {
        Console.WriteLine($"Started new request. Running requests: {Interlocked.Increment(ref _count)}");
        await next(context);
        Console.WriteLine($"Ended request. Running requests {Interlocked.Decrement(ref _count)} Finished {Interlocked.Increment(ref _totalCount)}");
    }
}

Add a longing running controller to your api. Could be something like this:
[Route("api/[controller]")]
[ApiController]
public class WaitController : ControllerBase
{
    [HttpGet]
    public void Get()
    {
        Thread.Sleep(10 * 1000);
    }
}

Then flood your WaitController with 1000 requests, and watch how they are only started very slowly one by one. That was the problem I was struggling with.
The key to a solution is @Tratcher's confirmation that HttpSys will start request processing using ThreadPool.QueueUserWorkItem. So concurrent requests are limited by the threadpools algorithm for starting threads.
Adding this statement will dramatically increase concurrent requests:
      ThreadPool.SetMinThreads(1000, 100);

Another solution is to return Tasks from your controller.
Your controllers are propably long running because they are I/O bound. So propably a better solution is to release the threadpool threads by changing your controller to return Tasks.
Something like this
[Route("api/[controller]")]
[ApiController]
public class WaitController : ControllerBase
{
    [HttpGet]
    public async Task<string> Get()
    {
        await Task.Delay(10_000);
        return "Hello";
    }
}

Another solution is to return Tasks from your controller.

Absolutely. AspNetCore is a fully async stack so your actions should all be async as well. Blocking thread pool thread will cause starvation. Raising your threadpool limit is only a temporary mitigation.


[CI] dev unit tests seems broken because of test in mina_net2

Blocking PRs in Mina

https://app.zenhub.com/workspaces/core-crypto-621fcb82b7d49700156fd060/issues/gh/minaprotocol/mina/13910
https://github.com/MinaProtocol/mina/pull/13885

Seems to happen only on Berkeley

@nholland94 confirms it is fixed now. Closing.


This is pull request for the .github/ISSUE_TEMPLATE.md file

I have created the markdown file and wrote down some headings to make the issue reporting structured.
https://github.com/mayn/packerlicious/issues/42

Coverage remained the same at 81.637% when pulling da35fcd2ce987996c924ecb7bfe5a2230ae47d19 on develop-build:master into 75cb7db047307611b64a2e27acd33e022238918d on mayn:master.

see for #44 for an example of the format I'm looking for. Thanks!


Update README.md

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/manifest/sbom-transmitter?version=dev:76cc4e634171986f1d34553e7b6a26ae8db75324

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/manifest/sbom-transmitter?version=dev:f6e7d6f1513fa9c6005eee91526b16e734a66ffb

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/manifest/sbom-transmitter?version=dev:f6e7d6f1513fa9c6005eee91526b16e734a66ffb


Auto complete template names

I am using llm the way it is presented in the docs; eg: llm -t roast 'Why are you submitting this issue?'
But some of my template names look like git-describe-changes and git-generate-commit-message.
It would be nice if after typing llm -t  one could hit tab to get autocompletion for the available template names.

You can try simonw/llm#261 for initial support on this.


HOSTEDCP-1832: Document konnectivity in HyperShift

What this PR does / why we need it:
Adds a more detailed description of Konnectivity and how it's implemented in HyperShift
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #HOSTEDCP-1832
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[x] This change includes docs.

/lgtm


gui.MouseX & gui.MouseY fucked up

Having this installed fucks up gui.MouseX and gui.MouseY for all other addons:
https://github.com/HandsomeMatt/3d2d-vgui/blob/master/3d2dvgui.lua#L88-L95
You probably should fall back to x, y = gui.MousePos() if x and y are 'nan'
https://github.com/HandsomeMatt/3d2d-vgui/blob/master/3d2dvgui.lua#L48

I disabled this in my version since I noticed the same thing, but it doesn't really appear to do anything anyway?

It fucks up every DermaMenu() for one. That's how I noticed this shit and messing around with 3d2d vgui

I think this was a hack for some weird stuff VGUI used to do, I'll change it so it doesn't use it.


Question about num_points in Detr3DCrossAtten

why only set num_points == 1 in code ?  Whether num_points > 1 will be better ?

Hi.
we tried setting num_points > 1, but training is unstable when using more num points.
So, currently, with this set of code, using num_points=1 is the best.


HBASE-27230 RegionServer should be aborted when WAL.sync throws Timeout.

Porting of change for HBASE-27230 to branch-2. (#4641)
Change-Id: I4a413143681376235a250d164fec36ff9eb377b4

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  4s
branch-2 passed

+1 :green_heart:
compile
2m 33s
branch-2 passed

+1 :green_heart:
checkstyle
0m 40s
branch-2 passed

+1 :green_heart:
spotless
0m 46s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 35s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 46s
the patch passed

+1 :green_heart:
compile
2m 27s
the patch passed

+1 :green_heart:
javac
2m 27s
the patch passed

-0 :warning:
checkstyle
0m 38s
hbase-server: The patch generated 1 new + 28 unchanged - 0 fixed = 29 total (was 28)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m 10s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

-1 :x:
spotless
0m 37s
patch has 21 errors when running spotless:check, run spotless:apply to fix.

+1 :green_heart:
spotbugs
1m 39s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 12s
The patch does not generate ASF License warnings.

28m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5711

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux b922e446d8cc 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ac01d72d94

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/1/artifact/yetus-general-check/output/diff-checkstyle-hbase-server.txt

spotless
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/1/artifact/yetus-general-check/output/patch-spotless.txt

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/1/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
3m 39s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  3s
branch-2 passed

+1 :green_heart:
compile
0m 51s
branch-2 passed

+1 :green_heart:
shadedjars
5m 27s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 28s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 57s
the patch passed

+1 :green_heart:
compile
0m 51s
the patch passed

+1 :green_heart:
javac
0m 51s
the patch passed

+1 :green_heart:
shadedjars
5m 22s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 27s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
227m  9s
hbase-server in the patch passed.

254m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5711

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4b9df5c08937 5.4.0-172-generic #190-Ubuntu SMP Fri Feb 2 23:24:22 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ac01d72d94

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/1/testReport/

Max. process+thread count
4544 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 48s
branch-2 passed

+1 :green_heart:
compile
2m 27s
branch-2 passed

+1 :green_heart:
checkstyle
0m 37s
branch-2 passed

+1 :green_heart:
spotless
0m 43s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 32s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 50s
the patch passed

+1 :green_heart:
compile
2m 27s
the patch passed

+1 :green_heart:
javac
2m 27s
the patch passed

+1 :green_heart:
checkstyle
0m 38s
the patch passed

+1 :green_heart:
whitespace
0m  1s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
9m  8s
Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6.

+1 :green_heart:
spotless
0m 43s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 41s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

28m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5711

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux 93ca53fb9911 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ac01d72d94

Default Java
Eclipse Adoptium-11.0.17+8

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 41s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 35s
branch-2 passed

+1 :green_heart:
compile
0m 38s
branch-2 passed

+1 :green_heart:
shadedjars
5m  8s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 14s
the patch passed

+1 :green_heart:
compile
0m 39s
the patch passed

+1 :green_heart:
javac
0m 39s
the patch passed

+1 :green_heart:
shadedjars
5m  4s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 23s
the patch passed

_ Other Tests _

-1 :x:
unit
209m 34s
hbase-server in the patch failed.

231m 35s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5711

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3b17a94fbeea 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ac01d72d94

Default Java
Temurin-1.8.0_352-b08

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/testReport/

Max. process+thread count
4248 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
2m 49s
branch-2 passed

+1 :green_heart:
compile
0m 50s
branch-2 passed

+1 :green_heart:
shadedjars
5m 23s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 27s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 52s
the patch passed

+1 :green_heart:
compile
0m 51s
the patch passed

+1 :green_heart:
javac
0m 51s
the patch passed

+1 :green_heart:
shadedjars
5m 22s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 27s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
225m 55s
hbase-server in the patch passed.

250m  0s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5711

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 4bb4a6f0e3b2 5.4.0-172-generic #190-Ubuntu SMP Fri Feb 2 23:24:22 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / ac01d72d94

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/testReport/

Max. process+thread count
4516 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/2/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

retest

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+1 :green_heart:
mvninstall
3m  3s
branch-2 passed

+1 :green_heart:
compile
0m 44s
branch-2 passed

+1 :green_heart:
shadedjars
5m 44s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 25s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 44s
the patch passed

+1 :green_heart:
compile
0m 44s
the patch passed

+1 :green_heart:
javac
0m 44s
the patch passed

+1 :green_heart:
shadedjars
5m 42s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 26s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
239m 54s
hbase-server in the patch passed.

264m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5711

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b289f15de5bb 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 39b9b2be67

Default Java
Eclipse Adoptium-11.0.17+8

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/3/testReport/

Max. process+thread count
4441 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/3/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

-1 :x:
mvninstall
3m  8s
root in branch-2 failed.

+1 :green_heart:
compile
0m 47s
branch-2 passed

+1 :green_heart:
shadedjars
5m 52s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 28s
branch-2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 51s
the patch passed

+1 :green_heart:
compile
0m 48s
the patch passed

+1 :green_heart:
javac
0m 48s
the patch passed

+1 :green_heart:
shadedjars
5m 46s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 29s
the patch passed

_ Other Tests _

-1 :x:
unit
250m 48s
hbase-server in the patch failed.

276m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/3/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5711

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3b8ae63bac91 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 39b9b2be67

Default Java
Temurin-1.8.0_352-b08

mvninstall
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/3/artifact/yetus-jdk8-hadoop2-check/output/branch-mvninstall-root.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/3/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/3/testReport/

Max. process+thread count
4346 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5711/3/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

I think it is not harm to include this on branch-2.
@bbeaudreault Do you want this to be landed to branch-2.6 as well?
Thanks.


Smart selectors fail to find search bar using text placeholder

Is your feature request related to a problem? Please describe.
Smart selectors do not work when deal with search bar placeholders using text inside the bar as target
Related to https://github.com/getgauge/taiko/issues/1625
So, if you go to https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_search_placeholder and then run: write("AAAA", textBox("Filter items")) - Taiko won't write into the search bar
Running: write("AAAA", textBox({placeholder: "Filter items"})) - it'll work
_In the best case, the functionality already exists but I'm missing something - if so, I'd appreciate some pointers :)
Describe the solution you'd like
To be able to interact with elements with placeholders visually available
Describe alternatives you've considered
write("AAAA", textBox("Filter items")) should work just like write("AAAA", textBox({placeholder: "Filter items"}))
Additional context
This is an example of the kind of input with placeholders:

Lookforward this feature!

@NivedhaSenthil  Currently, Taiko works only on label in textBox
https://github.com/getgauge/taiko/blob/480cb4726d8afa05d235695eed34db7d6b33cdc6/lib/elementWrapper/textBoxWrapper.js#L21
placeholder attribute would be present only on input tag. I'm thinking the current function https://github.com/getgauge/taiko/blob/480cb4726d8afa05d235695eed34db7d6b33cdc6/lib/elementWrapper/textBoxWrapper.js#L6
Will check with label and input tag for the given value. Thougts?

Will check with label and input tag for the given value. Thougts?

This makes sense, because the placeholder is mostly used like a label for text fields. In most cases the label is ommitted when there is a placeholder. In case there is a label with the same text Taiko should pick the placeholder.

Thank you @zabil @saikrishna321 - you rock!


[Question] Location of builtin autocompletion configuration

Hi guys, I tried to ask my question on stackoverflow without any answer https://stackoverflow.com/questions/57921084/where-is-the-monaco-editor-autocompletion-located
So I ask again here :

I'm creating a PromQL language support for monaco-editor and I'd want to send you a PR to integrate it as a default language.
That said, nice work ! It took me a while to understand the tokenizer, but the result fits perfectly our needs.
It's basically composed by two main configuration objects:

Syntax highlighting (ILanguage)
Code auto-completion (CompletionItemProvider )

[ok] Syntax highlighting
I found that the languages definition and syntax highlighting definition are located in this repository : https://github.com/microsoft/monaco-languages
[??] Auto completion
I didn't manage to find where are located the default autocompletion definitions for these languages ?
Where should I send the PR to add a new language autocomplete ?
Further searches
I found that some languages have some specific repositories which contains well some completion items, like:

typescript https://github.com/microsoft/monaco-typescript
css https://github.com/microsoft/monaco-css
...
Now what about the other languages, like Java, Python ... ?

Thanks !

@celian-garcia I believe Monaco only comes with support for JavaScript/TypeScript, CSS, JSON, and HTML by default and that is why those monaco-abc repositories exist. There is no code completion for other languages such as Java and Python by default.

Ah okay I see, thanks for your quick answer :)
So if I understood correctly, I will keep my repository as separated and people who need it just have to use it as a plugin.
Last question : do you think it's worth it to follow some guidelines/architecture in the repo https://github.com/celian-garcia/monaco-languages-promql to facilitate the integration for somebody who want to use it ?
I thrown an eye to the monaco-abc repositories which are very more complex that my little one ^^

@celian-garcia Yes, I think a separate repository makes sense as it would be consistent with the other repositories out there.
I've never integrated other languages into Monaco so I can't speak for the difficulty of it. I am sure whatever documentation you can provide would be much appreciated by the wider community though. :)

Okay, I will try to be as closest as possible to these repos and make more documentation on the "vanilla" integration. (since I already did the angular and react integration).
Thank you for your time !


[spdlog] build failure on x64-linux

Host Environment

OS: Linux Ubuntu x64 20.04
Compiler: gcc 10.2.0

To Reproduce
Steps to reproduce the behavior:
./vcpkg install spdlog
Failure logs

install-x64-linux-dbg-out.log

Hi @VelocityRa
Thanks for posting this issue.
I cannot reproduce this on my local with Ubuntu 18.04, gcc 9.2.0.
Have you installed system library fmt on your local? If so, could you please remove fmt first, then try to rebuild this?

Hi @NancyLi1013
fmt got forcefully rebuilt as expected (since the spdlog port depends on it)
Same issue after that.
command.txt
(the dbg-out.log is the same so I'm not posting it again.)
Perhaps you have to use my env to repro (Ubuntu 20.04 with GCC 10.2.0).

Tried it again, building everything from scratch (clearing all of vcpkg_installed, its caches, etc) and it worked!
Thanks.


Document merge policy in Readme

For each merge request there is a review time for 10 working days (working days: Mo-Fr). If there no blocking comment it can be merged. Otherwise it needs to be resolved. If for some reason a resolution of a blocking comment is not feasible, a decision is made by the EBU Timed Text working group.

@nigelmegitt and @frans-ebu: please review.

Is there an exception to this, for example can people request a limited additional time to review in case they know they are unable to review within the standard 10 days?

That would be fine with me. Do you want to propose a text how this should/could be handled? Is this a chairs decision or should the review time be extended automatically.

@tairt I suggest automatic extension by 5 additional working days if anyone asks for it, and anything beyond that is a chairs decision.

@nigelmegitt Ok. Fine with me.


Backport: Don't failfast on branch V1.0

Don't Failfast in the 1.0 tests.

test-me-please

Build failed due to VirtualBox fun:
17:14:37 [Cilium-PR-Ginkgo-Tests-Validated@2] Running shell script
17:14:38 + cd<EMAIL_ADDRESS>17:14:38 + K8S_VERSION=1.10 vagrant up --no-provision
17:14:38 Bringing machine 'runtime' up with 'virtualbox' provider...
17:14:39 Bringing machine 'k8s1-1.10' up with 'virtualbox' provider...
17:14:39 Bringing machine 'k8s2-1.10' up with 'virtualbox' provider...
17:14:39 ==> runtime: Checking if box 'cilium/ubuntu' is up to date...
17:14:48 ==> runtime: Machine not provisioned because `--no-provision` is specified.
17:14:48 ==> k8s1-1.10: Checking if box 'cilium/ubuntu' is up to date...
17:14:49 ==> k8s1-1.10: Machine not provisioned because `--no-provision` is specified.
17:14:51 ==> k8s2-1.10: Checking if box 'cilium/ubuntu' is up to date...
17:14:52 ==> k8s2-1.10: Clearing any previously set forwarded ports...
17:14:54 There was an error while executing `VBoxManage`, a CLI used by Vagrant
17:14:54 for controlling VirtualBox. The command and stderr is shown below.
17:14:54
17:14:54 Command: ["modifyvm", "cb76074f-ecc0-4c25-99a4-a66cf537f24c", "--natpf1", "delete", "ssh"]
17:14:54
17:14:54 Stderr: VBoxManage: error: The machine 'test_k8s2-110_1524150607827_67331' is already locked for a session (or being unlocked)
17:14:54 VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MachineWrap, interface IMachine, callee nsISupports
17:14:54 VBoxManage: error: Context: "LockMachine(a->session, LockType_Write)" at line 525 of file VBoxManageModifyVM.cpp

test-me-please

test-me-please


Raycasts should only run after initial frame is loaded

In this example scene, you can see that the raycasts don't work because the floor is not yet loaded when the rays are fired. However, when we do hot-reload, since the model of the floor was already in memory, the raycasts work well.
https://github.com/decentraland/sdk7-goerli-plaza/tree/main/bird-field
This PR to an ADR makes very relevant clarifications about the topic:
https://github.com/decentraland/adr/pull/222/files

The first frame of a scene is either sent by the scene code or by the runtime (via main.crdt as stated in ADR-133). The physics phase of this initial frame MUST only be executed after all its messages have been processed and all the models have been loaded.

This enables the scene to embed Raycast queries that will hit the models being loaded in this first frame.

The raycasts system should already be running after the 1st frame. The problem described in this issue sounds more like it happens because meshes take more than 1~2 frames to actually load.
I'll see if I can implement something not too costly for waiting to have at least 1st-frame meshes loaded first.


Allow building of the repo in parts on macOS.

adds configure time macOS detection
makes the journald related things linux only

What's the reason for adding this compatibility?  The modules will never be used on OSX (as far as I know).

@kaysoky my motivation was that I wanted them to be buildable on macOS so that developers can at least tinker with them locally on their Apple machines. My hope is that if things are easy to build, new build issues (e.g. due to Mesos being bumped) can get caught and fixed quicker.


HTTP Proxy with Auth not being used

Hello, I have been trying to use proxies with user auth with chrome and no luck so far, my last attempt was using this format:
`httpproxy := selenium.Proxy{
Type: "manual",
HTTP: "http://" + (streamproxysorted[2] + ":" + streamproxysorted[3] + "@" + streamproxysorted[0] + ":" + streamproxysorted[1]),
//HTTPPort: httpport,
}
		caps := selenium.Capabilities{
			"browserName": "chrome",
		}
		if desiredProxyType == "HTTP" {
			fmt.Println("proxy activated")
			//httpport, _ := strconv.Atoi(streamproxysorted[1])
			caps.AddProxy(httpproxy)

		}`

It doesnt throw me any error  ( I think ) but when I check ip, still no proxy being used.

Hi, did u solve this problem?

up

Hi, did u solve this problem?

@pgshow did u solve it?

Nope


Custom Node Support

Ability to add custom nodes into 2.0

This is now in 2.0 master. Any bugs found with it will be filed separately.


Implement Read::read_exact

In the current, Read trait does not have read_exact method, it should be supported like https://docs.rs/monoio/latest/monoio/io/trait.AsyncReadRentExt.html#tymethod.read_exact

Hi @ethe , for S3File struct, will the behavior of read_exact be the same as read?

Yes, I think so, S3File always read exactly.

Thanks @ethe . Is fusio open for contributions at this moment? If yes I would love to take this issue.

Sure, I would love to.

I open a PR for the basic default implementation of read_exact: https://github.com/tonbo-io/fusio/pull/51, but this PR is still valid and needs to be continue:

[ ] specific Read implementations, for example there are more efficient way to read exactly on S3
[ ] ReadDyn support

I open a PR for the basic default implementation of read_exact: #51, but this PR is still valid and needs to be continue:

[ ]  specific Read implementations, for example there are more efficient way to read exactly on S3
[ ]  ReadDyn support

RE: specific Read implementations
Does it mean the implementations for all backend storages (S3File, TokioFile, MonoioFile)? If it's the case I'm working on it now.
RE: ReadDyn support
Could you please elaborate more on this part?

Does it mean the implementations for all backend storages (S3File, TokioFile, MonoioFile)? If it's the case I'm working on it now.

Yes, I think so

Could you please elaborate more on this part?

in #51 , I just implemented read_exact for Read, fusio has another set of object safe traits which includes DynRead, we should also implement define and implement read_exact for it.

Does it mean the implementations for all backend storages (S3File, TokioFile, MonoioFile)? If it's the case I'm working on it now.

Yes, I think so

Could you please elaborate more on this part?

in #51 , I just implemented read_exact for Read, fusio has another set of object safe traits which includes DynRead, we should also implement define and implement read_exact for it.

Ah okay, got it. So it's DynRead not ReadDyn 👍


Dynamic Sources and Sinks

Ability to create channels dynamically and attach sources, sinks, and processors to those channels.
Detail:
I want to create a microservice that allows me to use a rest service POST to dynamically create channels that provide multiple inputs to a processor service, and route the output of the service to the output of the channel that the input came in on.
I have a message that contains a string that I want to put onto a kafka topic that I don't know about until runtime, have the microservice pick it up, transform it, then send it out on another kafka topic that I don't know until runtime.
I want to "register" a channel with something like:
{ "producer":"kafka-output-topic",
"consumer":"kafka-input-topic",
"transformer":"some transformer thing"
}
And when registered, I want my "channel registry" to start up a message consumer, add a transform function, and start up a message producer to send the results out on. Maybe a dynamic IntegrationFlow?
When I send the service a DELETE method which identifies the channel to shutdown, then stop the consumer and producer. Stop the dynamic IntegrationFlow?
I may already be able to do this, but am unable to figure out how with my limited experience with Spring Cloud Streams and Spring Integration.
If it's already possible to do this, then just say so, and I'll go back to try to figure it out. :-)

I have the same request and wondering if there is existing solution in current Spring Cloud Stream project. If so, any sample code.
Really appreciate it!

Hi,
Spring Cloud Stream provides support for dynamic destination resolver via BinderAwareChannelResolver. For every event, the dynamic destination can be resolved and the corresponding channels can either be looked up or created at runtime.  I wonder if this helps achieve your case. You can find related discussion in SO here

@ilayaperumalg  thank you :)

Hi @george-smith If the above comment doesn't provide enough detail, please feel free re-open this with your case in detail. Thanks!

Hi, it seems that BinderAwareChannelResolver provides dynamic source registration but not dynamic sink registration.
Am I missing something?

@reda-alaoui That's right. BinderAwareChannelResolver is for the producer only. You can see the related discussion here

Hello @ilayaperumalg,
Is it possible to have only dynamic producer and not dynamic consumer ?
If yes can you please point me an example or reference guide please.

@SharathPS  please do not comment on the closed issues given that it's closed. Also we do not use this issue tracker for Q&Q. We have a dedicated Stack Overflow channel for it.


Multiple Interfaces in wifi/ethernet

Hi, in the wifi module, we are required to give one interface.
For ethernet, I don't want to make a new module.
I'm just interested in knowing the total download and upload speed.
Would it be possible to see the speed from multiple interfaces (except lo) combined ?

Hi, yeah that's doable.. the module is already iterating all interfaces when querying packet stats.

Thanks :)


Not generating input image's colors when depth maps passed

Hello Authors, first of all thanks so much for the amazing work.
I am trying to run zero123plus pipeline with depth control net.  When I use the depth_image, then the input image's pixels/colors are completely disregarded by the model. The model still generate (kind of) consistent 6 images with respect to depth, but the initial input image colors are no where to be seen.
I tested with your blue and yellow kid chair and one of my test models. I am sharing the pipeline and as well as the input and output results. It'd be a great help for me if you can look into this.
`
pipeline = DiffusionPipeline.from_pretrained(
"sudo-ai/zero123plus-v1.1", custom_pipeline="sudo-ai/zero123plus-pipeline",
torch_dtype=torch.float16
)
pipeline.add_controlnet(ControlNetModel.from_pretrained(
"sudo-ai/controlnet-zp11-depth-v1", torch_dtype=torch.float16
), conditioning_scale=0.75)
pipeline.scheduler = EulerAncestralDiscreteScheduler.from_config(
pipeline.scheduler.config, timestep_spacing='trailing'
)
pipeline.to('cuda:0')
result = pipeline(cImage, depth_image=dImage,  num_inference_steps=35).images[0]
`

I found the solution. The scheduler doesnt work when you wish to use depth maps. Use something else or just comment it out and it will work.

What version of diffusers are you using? The snippet works on my side.


Documentation for creating DMatrix from Apache Arrow

Following #7512 it would be great to see some documentation on Apache Arrow usage in DMatrix. I had to look at the tests to figure out how to use it with python, but I'm not sure about what limitations there are.
For instance, I discovered that categorical types are not yet supported. Are there other disadvantages? The main advantage I have found (also should be documented) was zero-copy coming from other arrow-based libraries, like polars.

I also noticed that pyarrow 8.x is not supported. One has to use 7.0.0 in order to avoid
Traceback (most recent call last):
  File "/itf-fi-ml/home/thomasaar/kaggle/convert.py", line 18, in <module>
    dtrain = xgb.DMatrix(
  File "/itf-fi-ml/home/thomasaar/.conda/envs/kaggle/lib/python3.10/site-packages/xgboost/core.py", line 532, in inner_f
    return f(**kwargs)
  File "/itf-fi-ml/home/thomasaar/.conda/envs/kaggle/lib/python3.10/site-packages/xgboost/core.py", line 643, in __init__
    handle, feature_names, feature_types = dispatch_data_backend(
  File "/itf-fi-ml/home/thomasaar/.conda/envs/kaggle/lib/python3.10/site-packages/xgboost/data.py", line 930, in dispatch_data_backend
    return _from_arrow(
  File "/itf-fi-ml/home/thomasaar/.conda/envs/kaggle/lib/python3.10/site-packages/xgboost/data.py", line 567, in _from_arrow
    rb_iter = iter(data.to_batches(use_async=True))
  File "pyarrow/table.pxi", line 3759, in pyarrow.lib.Table.to_batches
TypeError: to_batches() got an unexpected keyword argument 'use_async'

That error is fixed in the latest branch but we haven't made a release for it yet. Apologies for the inconvenience.
As for categorical data, it's experimental. We are still working on it for better coverage. I will update the document to reflect the support status.

If I may add, it would be very nice to have a better technical documentation of DMatrix, in general. I think it is a very central "piece" in xgboost (the most detailed info is maybe found in C API Reference DMatrix)

Thank you for the comment. Let's document every possible inputs.

Closing in favor of https://github.com/dmlc/xgboost/issues/8541 .


Error "No NVIDIA driver on your system"

I am using the ml-workspace docker for my DL model training in a GPU server. Here, the host workstation server has Linux OS. The host server has in total 8 GPUs (each of 40 GB), around 250 CPU threads and no display. After starting the ml-workforce docker through the command shown below, I am further using ssh to transfer the port in my Mac system. The technical specifications are as follows:
Technical details:

Workspace version : 0.13.2
Docker version : 19.03.13
Host Machine OS (Windows/Linux/Mac): Linux
Command used to start the workspace :

Run the docker in the workstation: docker run -p 8081:8080 --name "bio-dgi-workspace2" -v "${PWD}:/workspace" --restart always mltooling/ml-workspace:latest
Transfer the port to the local via ssh: ssh -NfL 8087:localhost:8081<EMAIL_ADDRESS>

Browser (Chrome/Firefox/Safari): Safari

Now when I try to train my model, I am getting an error of No NVIDIA Driver found in your system. Although it is already installed in the host machine. Can anyone suggest why I am getting this error and how to fix it? I have attached the screenshot for your reference.

Thanks.

I have found an error in my command itself. I have not mentioned the --gpus argument in the docker command. My updated command is as follows:
docker run -p 8081:8080 --name "bio-dgi-workspace4" -v "${PWD}:/workspace" --gpus all --restart always mltooling/ml-workspace-gpu:latest
Now, I am not getting any such error. But the new issue I am getting is that there is no gpu utility while training my DL model, even after categorically adding the GPU_ID as an environment variable (shown below)
os.environ["CUDA_DEVICE_ORDER"] = "PCI_BUS_ID"
os.environ["CUDA_VISIBLE_DEVICES"] = "0"
Screenshot is attached below:

Can anybody tell me why there is no GPU utility?