pipenv failed to install package with dot in name

Issue description
pipenv vesion 2018.10.9 failed to install package with dot in name:
pipenv install dogpile.cache

Expected result
dogpile.cache installed succesfully
Actual result
pipenv install -v dogpile.cache
Installing dogpile.cache…
⠋Installing u'dogpile.cache'
$ ['/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/bin/pip', 'install', '--verbose', '--upgrade', 'dogpile-cache', '-i', u'https://pypi.org/simple']
Created temporary directory: /tmp/pip-ephem-wheel-cache-daJvc_
Created temporary directory: /tmp/pip-req-tracker-2F3rqD
Created requirements tracker '/tmp/pip-req-tracker-2F3rqD'
Created temporary directory: /tmp/pip-install-1El2qM
Collecting dogpile-cache
  1 location(s) to search for versions of dogpile-cache:
  * https://pypi.org/simple/dogpile-cache/
  Getting page https://pypi.org/simple/dogpile-cache/
  Looking up "https://pypi.org/simple/dogpile-cache/" in the cache
  Request header has "max_age" as 0, cache bypassed
  Starting new HTTPS connection (1): pypi.org:443
  https://pypi.org:443 "GET /simple/dogpile-cache/ HTTP/1.1" 304 0
  Analyzing links from page https://pypi.org/simple/dogpile-cache/
    Skipping link https://files.pythonhosted.org/packages/44/ed/f0ea13fbf9626121c58aa1333b74aee612f3d784abab5da5b4e2ca0bc539/dogpile.cache-0.2.0.tar.gz#sha256=670c24d96cd9e75e1b90bf00493ef1ad3d1c699552a9cbe1ce5182c7c021edf4 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/d0/9e/ce6448bd30fb20a5be98cc8be521c565d30af14bf4eaff828789264617f6/dogpile.cache-0.2.1.tar.gz#sha256=a82fc1c18c36d74c9dbc00a86905890ff37bc4bc65ef0794182060d904a9e60c (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/47/c7/9eba204c269f0e4a2607d013faba3730c0ac74d0d62ed2d07db201d7ed29/dogpile.cache-0.2.2.tar.gz#sha256=a237df3522f3d079032145fcedc9d94b97610a4ad0ecb6d2f1f4cde517fd06b0 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/f0/10/f952d55f07803427786df1835d1ebe9f90a615a09b7f89ad3582038d59a2/dogpile.cache-0.2.3.tar.gz#sha256=6371b6f19c0286a3f1048ccbd37240fea0046558673a3f5b61601e4215563839 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/91/ff/fa0809c57bcdca12f7086772b2189909063f792397eb8a924ed6de3a09e9/dogpile.cache-0.2.4.tar.gz#sha256=fedbe44ee754635510392c82151066ba6dd5dfb715430aea3fe08e2b0fcae488 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/30/20/586472a1333495c0cb4f73a89ed3dbd0d1575e758b1eedba462818327fde/dogpile.cache-0.3.0.tar.gz#sha256=51010544fd679f61e20438c66f8117f924e78f631320e8903c9ba4241c8f9683 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/89/5b/97d650cc9820ea799cce9b974611898e0d83ccc6924434c60e4553f2269b/dogpile.cache-0.3.1.tar.gz#sha256=4cdc3959d08755af629995f45b25c6c507d71704b28cd0eafd1f3105c73e906f (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/a9/e9/1327ae3975bc353bd1eae89420dd4f6841308abf0a3d169c864b75455ace/dogpile.cache-0.4.0.tar.gz#sha256=06fa35aa892507f5ba4a0cda1279772d70dcfa8fb81fd8fccdcc858eae93d282 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/4d/82/b117284ebb9d12ee4bed7130662ae27ce8ffae05c8a0b68a52c0c411f366/dogpile.cache-0.4.1.tar.gz#sha256=d2a1f0459755cf71d91f4397b02dbb8ec101b5ccd1f036cf6322e595eabb462a (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/9c/f4/b43fa52203059e11e0b900df3aa82536b0f7f7958616fe321e3b800947ff/dogpile.cache-0.4.2.tar.gz#sha256=beec3b5486e0f1062fd692520c373c45bc41292c785650395c05d3aad5ec5276 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/ff/1e/292a8cef43518c6c3056e70bda6563e199c4f57594418d2a7edb243ed034/dogpile.cache-0.4.3.tar.gz#sha256=b3425e159a548634f3a1ccb9a934971ab4180ba1954479475c5aa81bfaa7186b (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/0b/aa/ee0a873384bee4c8f3ef7ab6d169e5c6e73d3a36a388c712066cec0dc56e/dogpile.cache-0.5.0.tar.gz#sha256=d02d15ad150783a284d0e0ebc69dcbac9b3c64784f4a4b2dada206173cf55c98 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/9a/c4/61feabeeae0ef2831c756fcfd09634caad9764e293f57895acebd3d3c40b/dogpile.cache-0.5.1.tar.gz#sha256=1f3165222bc23418cb9d3f1a2c9d554a091f412e5bc871ea0c48a19b576d06c0 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/10/32/df085e387dcb76ac115698e4016b9a866cb48fc82ecc80d33af8ef2e12e9/dogpile.cache-0.5.2.tar.gz#sha256=acdcb69e7eb8421678172fe8709d6d92bf7249022a70e4d7c84316d4e2d1d1b5 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/a4/d8/5d193515f11dd8c98f0295227f59a386a6d0e57ee687c979708259479392/dogpile.cache-0.5.3.tar.gz#sha256=2fe8c1a329830a9ada865a69cc5ebb2c2e6f2dbda3a6d4dbf5155c7d5194344b (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/5f/1e/2cca4354f23e3fe0d900abb846a238ade652d5467011dff157b4d557b713/dogpile.cache-0.5.4.tar.gz#sha256=9eab7a5dc05ad1b6573144c4a2717226b5c38811f9ec29b514e774535a91ea24 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/cd/7b/5d55589ee0accfa700abf5ad04823e66253931902e5bb07aa5c22e7dc7aa/dogpile.cache-0.5.5.tar.gz#sha256=30387ca6c146a627c69b700c56c16a3059b43727f11b28d9f918941f072860d6 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/c0/7d/55967422ed24acb39e9d9b6d6288f22907136e68d728594cf8e2c16d7215/dogpile.cache-0.5.6.tar.gz#sha256=f80544c5555f66cf7b5fc99f15431f3b35f78009bc6b03b58fe1724236bbc57b (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/07/74/2a83bedf758156d9c95d112691bbad870d3b77ccbcfb781b4ef836ea7d96/dogpile.cache-0.5.7.tar.gz#sha256=dcf99b09ddf3d8216b1b4378100eb0235619612fb0e6300ba5d74f10962d0956 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/16/15/8de884814301e26d273d51f0b07ad605f71cb7fad37deec096da4d2f031d/dogpile.cache-0.6.0.tar.gz#sha256=1b65aba2dde75cb577f275b5f3f4fcc635d21b3dc6781b98cef57bd009d93185 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/f6/a0/6f2142c58c6588d17c734265b103ae1cd0741e1681dd9483a63f22033375/dogpile.cache-0.6.1.tar.gz#sha256=69b52dc56bb52d974e9e9fb2764e1311abcd1fd625de07b4e5c05550ac9b40c0 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/9d/a9/ba70aadc6170841a1c6145e9039d4b1c2a4ef8c44cd0ca9b09ab79be9120/dogpile.cache-0.6.2.tar.gz#sha256=73793471af07af6dc5b3ee015abfaca4220caaa34c615537f5ab007ed150726d (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/94/bf/1b07b1a18733d22aad9660ed43f23a48c55a3573ae3e9dbc8dec9cd352ba/dogpile.cache-0.6.3.tar.gz#sha256=e9747f5e31f8dea1b80d6204358885f943f69e53574d88005438ca3651c44553 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/b6/3d/35c05ca01c070bb70d9d422f2c4858ecb021b05b21af438fec5ccd7b945c/dogpile.cache-0.6.4.tar.gz#sha256=a73aa3049cd88d7ec57a1c2e8946abdf4f14188d429c1023943fcc55c4568da1 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/65/24/7bd97e9d486c37ac03ef6ae3a590db1a8e02183e5d7ce9071bcca9d86c44/dogpile.cache-0.6.5.tar.gz#sha256=631197e78b4471bb0e93d0a86264c45736bc9ae43b4205d581dcc34fbe9b5f31 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/48/ca/604154d835c3668efb8a31bd979b0ea4bf39c2934a40ffecc0662296cb51/dogpile.cache-0.6.6.tar.gz#sha256=044d4ea0a0abc72491044f3d3df8e1fc9e8fa7a436c6e9a0da5850d23a0d16c1 (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
    Skipping link https://files.pythonhosted.org/packages/ee/bd/440da735a11c6087eed7cc8747fc4b995cbac2464168682f8ee1c8e43844/dogpile.cache-0.6.7.tar.gz#sha256=fca7deb7c276b879b01c15c5d39b3c05701dc43b263ec3fef1e52cb851cf88ab (from https://pypi.org/simple/dogpile-cache/); Missing project version for dogpile-cache
Cleaning up...
Removed build tracker '/tmp/pip-req-tracker-2F3rqD'
Exception information:
Traceback (most recent call last):
  File "/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/local/lib/python2.7/site-packages/pip/_internal/cli/base_command.py", line 143, in main
    status = self.run(options, args)
  File "/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/local/lib/python2.7/site-packages/pip/_internal/commands/install.py", line 318, in run
    resolver.resolve(requirement_set)
  File "/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 102, in resolve
    self._resolve_one(requirement_set, req)
  File "/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 256, in _resolve_one
    abstract_dist = self._get_abstract_dist_for(req_to_install)
  File "/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 209, in _get_abstract_dist_for
    self.require_hashes
  File "/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/local/lib/python2.7/site-packages/pip/_internal/operations/prepare.py", line 218, in prepare_linked_requirement
    req.populate_link(finder, upgrade_allowed, require_hashes)
  File "/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/local/lib/python2.7/site-packages/pip/_internal/req/req_install.py", line 164, in populate_link
    self.link = finder.find_requirement(self, upgrade)
  File "/home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/local/lib/python2.7/site-packages/pip/_internal/index.py", line 621, in find_requirement
    'No matching distribution found for %s' % req
DistributionNotFound: No matching distribution found for dogpile-cache

Error:  An error occurred while installing dogpile.cache!
  Could not find a version that satisfies the requirement dogpile-cache (from versions: )
No matching distribution found for dogpile-cache

Steps to replicate

Start from fresh environment
Run pipenv install dogpile.cache

pipenv --support
$ pipenv --support
Pipenv version: '2018.10.9'
Pipenv location: '/usr/local/lib/python2.7/dist-packages/pipenv'
Python location: '/usr/bin/python'
Python installations found:
Traceback (most recent call last):
File "/usr/local/bin/pipenv", line 11, in
sys.exit(cli())
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/click/core.py", line 764, in call
return self.main(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/click/core.py", line 717, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/click/core.py", line 1114, in invoke
return Command.invoke(self, ctx)
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/click/decorators.py", line 64, in new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/click/decorators.py", line 17, in new_func
return f(get_current_context(), *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/pipenv/cli/command.py", line 142, in cli
get_pipenv_diagnostics()
File "/usr/local/lib/python2.7/dist-packages/pipenv/help.py", line 33, in get_pipenv_diagnostics
python_paths = finder.find_all_python_versions()
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/pythonfinder/pythonfinder.py", line 108, in find_all_python_versions
major=major, minor=minor, patch=patch, pre=pre, dev=dev, arch=arch
File "/usr/local/lib/python2.7/dist-packages/pipenv/vendor/pythonfinder/models/path.py", line 221, in find_all_python_versions
return [c for c in sorted(path_filter, key=version_sort, reverse=True)]
AttributeError: 'list' object has no attribute 'as_python'

This problem does not happen in 2018.7.1
$ pipenv install dogpile.cache
Installing dogpile.cache...
Requirement already satisfied: dogpile.cache in /home/cuonglm/.local/share/virtualenvs/python-pVLxsDDq/lib/python2.7/site-packages (0.6.7)

Adding dogpile.cache to Pipfile's [packages]...
Pipfile.lock not found, creating...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
Updated Pipfile.lock (c96445)!
Installing dependencies from Pipfile.lock (c96445)...
  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 1/1 — 00:00:00
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.
$ pipenv --version
pipenv, version 2018.7.1

I open another bug report in pip repo https://github.com/pypa/pip/issues/5877
I don't know it's pipenv problem, which pass a normalize name, according to PEP 503 or egg_info_matches problem

This is a duplicate of https://github.com/pypa/pipenv/issues/3000 which is itself a duplicate of https://github.com/pypa/pipenv/issues/2956.

Maybe issues like #2956 should be kept open until a new version that fixes it is relesed, not closed as soon as a fix is commited to git.
For many people it doesn't work because they don't install from master but they cannot find the original github issue because it is already closed.

@mesa Unfortunately that isn’t really a viable option, at least not at the moment. We don’t have the person/time to actively hunt down issues and close them manually, and have to rely on the integrated issue-closing feature of GitHub to keep us on top of things. I am certainly open (and I believe others would be) if there is a technically realistic solution to this, or if there is spare personnel resource for this job (would you be that person?).

I'm in the same boat as @messa -- I searched for "dot" in the open issues. When I didn't find any, I created yet another issue. I might suggest adding a "fix version" label to issues that are fixed in master but not yet released.
When that version is released, you can just find all the issues with that tag and close them. Not sure if that is still to much work -- hopefully it would save a bit of work in closing the duplicate issues that inevitably get generated in the current workflow.

I’ve sort of implied this in my previous comment, but I’ll be more blunt here. @rcoh Do you want to take the job and do the tagging from now on? This does not happen automatically.

@WestFlame I am trying to install stompest.async and this is what I am getting Could not find a version that matches stompest-async

@WestFlame I had to go to Pipfile and change the package name there which was replaced with stompest-async while it should have been stompest.async, this fixed my problem


[nrf fromlist] wifi: Check WPA-PSK passphrase length

When WPA-PSK was introduced the passphrase length check was missed.
Upstream PR: https://github.com/zephyrproject-rtos/zephyr/pull/65933

for information:

also, https://github.com/nrfconnect/sdk-nrf/pull/13288 was merged by mistake, v2.5-branch reverted back to https://github.com/nrfconnect/sdk-nrf/commit/a2f1f79998e8722c2c17265954b9c05f5a9924f1


documentation: fixed some path finding issues that leads into 404

Some links within the documentation were leading to 404 pages, because the paths were wrong

Still missing one, couldn't find the proper markdown file 😅

Thanks for the work here, you mind rebasing with main and verifying if the links still need to be fixed?
If so, please use markdown link identifiers in the bottom of the document. We started adding them all there so that it's easier to update/fix links across the project. If you scroll to the bottom you can see how it works.

I think these have been fixed. If not feel free to open a new PR. Thanks!


Add radar_msgs from astuff_sensor_msgs

Status
PRODUCTION / DEVELOPMENT
Description
The platform_automation_msgs repository no longer ships the radar_msgs package (see https://github.com/astuff/platform_automation_msgs/pull/5). This PR adds the astuff_sensor_msgs repository instead (https://github.com/astuff/astuff_sensor_msgs)

Or perhaps it'd just be better to pin the platform_automation_msgs module to a revision that still contained the radar_msgs package. The latest tagged revision still has it:
https://github.com/astuff/platform_automation_msgs/tree/v1.7.0

@esteve radar_msgs does not seems to be used in Autoware. Is it beneficial to add radar_msgs as submodule? Or another reason?

@kfunaoka that's true, radar_msgs is not being used in Autoware, but it was spun off from platform_automation_msgs, so using the latter's master branch now requires astuff_sensor_msgs to be in the workspace. We can avoid adding a new submodule for astuff_sensor_msgs by pinning the platform_automation_msgs submodule to the latest tagged release (1.7) which still shipped with radar_msgs. I've submitted https://github.com/CPFL/Autoware/pull/1420 instead, which just uses a tagged release for platform_automation_msgs

@esteve I understand. Autoware requires platform_automation_msgs, and platform_automation_msgs requires astuff_sensor_msgs. So #1417 or #1420 is required. It is difficult to select which one is better. For now, platform_automation_msgs v1.7 is good for us. #1420 is selected tentatively.

I'm closing this in favor of #1420 However, in the long term, it'd be better if the message packages are released into the ROS index (https://github.com/astuff/platform_automation_msgs/issues/7)


Implement a generic toggle container

Purpose:
To allow the construction of toggle contexts, where components such as accordions, off-canvas menus, slide-out menus, and similar can be implemented without any additional javascript required.
The functionality will be as follows:

A toggle-container class will define the toggle container or wrapper and the scope of the toggle context.
A toggle container may optionally include data-fade-in-duration and data-fade-out-duration data attributes, controlling the transitions of it's child elements.
The toggle container will typically wrap toggle-activator and toggle-item pairs linked by id, and making use of data-target attributes.
A toggle activator can be any html element capable of receiving mouse or touch events.
A toggle item can be any html element that can be shown and hidden.
Toggle activators and toggle items can be linked by id or CSS selector strings.
Any other html content can be sandwiched between toggle activators and toggle items, or between toggle activator / toggle item pairs.
Expose event callbacks.

If a toggle container is not defined, then the context for toggle activators and toggle items will be the html document.

Implemented new toggle container.


disasm: add support for codedatalog

Closes #124

Codecov Report

Merging #134 (13f9ce0) into main (f4022a0) will decrease coverage by 0.33%.
The diff coverage is 19.69%.

@@            Coverage Diff             @@
##             main     #134      +/-   ##
==========================================
- Coverage   50.46%   50.13%   -0.34%
==========================================
  Files          94       95       +1
  Lines        7815     7867      +52
==========================================
  Hits         3944     3944
- Misses       3654     3704      +50
- Partials      217      219       +2


[FAB-17952] Fix test-network to use the latest version of fabric-ca

To get rid of hard-coded versioning and use the latest version of fabric-ca in test-network, this patch modifies the existence check logic of the fabric-ca-client binary in the same way as peer and orderer.
Also, this patch updates addOrg3.sh to use cai <ca_imagetag> option.
Type of change

Bug fix

Description
Currently, test-network mainly uses the previous version (1.4.6) of fabric-ca.
Also, addOrg3.sh in test-network is not using the cai <ca_imagetag> option (This may use non-existent version or a hard-coded 1.4.4 version).
So, this should catch up with the latest version (latest or 1.4.7).
Related issues

https://jira.hyperledger.org/browse/FAB-17952

Lovely update. Thank you for this.

@lehors @nikhil550 Thank you for your reviews.

Thank you for your contribution!


Add expand attribute to SectionBlock

The API docs list the attribute expand, which is currently missing from the SDK version in SectionBlock class.
Category (place an x in each of the [ ])

[ ] slack_sdk.web.WebClient (sync/async) (Web API client)
[ ] slack_sdk.webhook.WebhookClient (sync/async) (Incoming Webhook, response_url sender)
[X] slack_sdk.models (UI component builders)
[ ] slack_sdk.oauth (OAuth Flow Utilities)
[ ] slack_sdk.socket_mode (Socket Mode client)
[ ] slack_sdk.audit_logs (Audit Logs API client)
[ ] slack_sdk.scim (SCIM API client)
[ ] slack_sdk.rtm (RTM client)
[ ] slack_sdk.signature (Request Signature Verifier)

Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

I am willing to also contribute a PR with this - I might need some help with it (feedback via code review), but in general I think I understand how the model definition works.

@henrinormak Thank you for raising this, @henrinormak! If you are able to open a PR for this, I would be happy to give you a code review! If not, let me know and I can open a PR for this!


Crashed in the Erebus with this mod installed

https://pastebin.com/2TrrMdTZ
I removed the mod and was able to move freely in the Erebus.

This is similar to the issue that was happening with AoA (direct mob spawner tile creation)
@vadis365 Could you change this line to
TileEntityMobSpawner tile =  (TileEntityMobSpawner) Blocks.MOB_SPAWNER.createTileEntity(world, getDefaultState());

Vadis mentioned he would be able to put the fix in, so hopefully that gets resolved quickly.

Closed as of https://github.com/vadis365/TheErebus/commit/3b43aa404e8930954b585098d569463d70d3d007

Nearly. One of the other custom spawners was missed, so this is still an issue with the Fly Spawner specifically. I'll get it patched to work with Apotheosis later as a sort of 'luke warm fix' later.


esp-idf v4.2 rmt_set_tx_thr_intr_en() panic

Hi @bbulkow, thanks for this great port. Cloning this repo fresh, copying the sdkconfig.4-1 to sdkconfig, and running the example against esp-idf v4.1 results in an rmt_set_tx_thr_intr_en() panic as described on this esp-idf issue (stacktrace copied below). I understand this is an issue introduced in esp-idf v4.1 as you discussed on this other esp-idf issue.
I'm just wondering, what would you suggest users of your fork to do in this situation? It's somewhat difficult to follow where this interrupt handler issue is headed and whether it would be solved by the espressif team, or if your port needs to address it. Should we just stick to v4.0 for now? I have some ota over ble bugs that were fixed in 4.2 and I'm looking to upgrade, but this is the one issue holding me up.
Thanks again!
EDIT: What I'm mainly asking is if there is a way to use fastled with esp-idf 4.2, whether that be this library or not. I was having trouble getting arduino-esp32 to run again esp-idf 4.2 which is why I moved from using the main FastLED library to this port so I could ditch arduino-esp32 entirely. But now there's this RMT issue. So if there is another port or approach to getting fastled and esp-idf to play nicely together, I'm all ears!
 entering app main, call add leds
 set max power
create task for led blinking
W (384) FastLED: controller init
Guru Meditation Error: Core  0 panic'ed (LoadProhibited). Exception was unhandled.
Core 0 register dump:
PC      : 0x400d55a0  PS      : 0x00060833  A0      : 0x800d4818  A1      : 0x3ffaf8a0
0x400d55a0: rmt_set_tx_thr_intr_en at /Users/drewandre/esp/esp-idf/components/driver/rmt.c:389 (discriminator 2)

A2      : 0x00000000  A3      : 0x3ffb1390  A4      : 0x00000020  A5      : 0x3ffb1390
A6      : 0x000000b0  A7      : 0x00000000  A8      : 0x00000034  A9      : 0x00000000
A10     : 0x00000001  A11     : 0x00009470  A12     : 0x3ff560b0  A13     : 0xefffffff
A14     : 0xfff7ffff  A15     : 0xffffffbf  SAR     : 0x00000020  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000000  LBEG    : 0x400014fd  LEND    : 0x4000150d  LCOUNT  : 0xfffffffd

ELF file SHA256: 005f4b4fdb53c297

Backtrace: 0x400d559d:0x3ffaf8a0 0x400d4815:0x3ffaf8d0 0x4008294d:0x3ffaf910 0x400d424f:0x3ffaf940 0x400d4641:0x3ffaf9a0 0x400d3b56:0x3ffaf9e0 0x400d1e54:0x3ffafa10
0x400d559d: rmt_ll_set_tx_limit at /Users/drewandre/esp/esp-idf/components/soc/esp32/include/hal/rmt_ll.h:177 (discriminator 2)
 (inlined by) rmt_set_tx_thr_intr_en at /Users/drewandre/esp/esp-idf/components/driver/rmt.c:389 (discriminator 2)

0x400d4815: _ZN18ESP32RMTController4initEv$part$2 at /Users/drewandre/Downloads/my-test-project/build/../components/FastLED-idf/platforms/esp/32/clockless_rmt_esp32.cpp:119

0x4008294d: ESP32RMTController::showPixels() at /Users/drewandre/Downloads/my-test-project/build/../components/FastLED-idf/platforms/esp/32/clockless_rmt_esp32.cpp:92
 (inlined by) ESP32RMTController::showPixels() at /Users/drewandre/Downloads/my-test-project/build/../components/FastLED-idf/platforms/esp/32/clockless_rmt_esp32.cpp:147

0x400d424f: CPixelLEDController<(EOrder)10, 1,<PHONE_NUMBER>u>::show(CRGB const*, int, CRGB) at /Users/drewandre/Downloads/my-test-project/build/../components/FastLED-idf/platforms/esp/32/clockless_rmt_esp32.h:359
 (inlined by) CPixelLEDController<(EOrder)10, 1,<PHONE_NUMBER>u>::show(CRGB const*, int, CRGB) at /Users/drewandre/Downloads/my-test-project/build/../components/FastLED-idf/controller.h:408

0x400d4641: CFastLED::show(unsigned char) at /Users/drewandre/Downloads/my-test-project/build/../components/FastLED-idf/controller.h:90
 (inlined by) CFastLED::show(unsigned char) at /Users/drewandre/Downloads/my-test-project/build/../components/FastLED-idf/FastLED.cpp:59

0x400d3b56: _fastfade_cb(void*) at /Users/drewandre/Downloads/my-test-project/build/../components/FastLED-idf/FastLED.h:506
 (inlined by) _fastfade_cb at /Users/drewandre/Downloads/my-test-project/build/../main/main.cpp:103

0x400d1e54: timer_process_alarm at /Users/drewandre/esp/esp-idf/components/esp_common/src/esp_timer.c:306
 (inlined by) timer_task at /Users/drewandre/esp/esp-idf/components/esp_common/src/esp_timer.c:327

Rebooting...

Closing as this was resolved by updating to the esp-idf release/v4.2 branch.


Kind of strange import issue

Keep in mind that if you import another canister's file into your own project, then it will become part of your canister and the candid will get generated for it. So if you want to share types, you need to make the files stand-alone.

This might take a lot of complex static analysis to solve, the workaround is to just put canister types into their own files that are imported explicitly when they are to be used.

We believe this to be fixed (@lastmjs is pretty stinkin' sure, @dansteren has doubts)


Animation velocity

How to change animation velocity for showing/hiding menu?
EDIT:
Ok, I found, but I think there should be public property for setting this.

How do you set the velocity?
I see PanInfo struct but I don't see how I can set the left menu slide animation speed/velocity.
Care to share saltwat5r? :D

I believe it's called animationDuration in case anyone in the future stumble upon this :D


repartition documentation doesn't specify whether the size will be reflected on output

Noticed a difference between memory usage and storage size and I think this would be a good thing to note within the documentation that partition sizes won't necessarily be reflected when storing on disk. Moving the issue here from https://github.com/geopandas/dask-geopandas/issues/210#issue-1306025315

@drstewart19 Welcome, and thanks for opening this issue! I agree the docs can be improved here, would you be interested in submitting a PR?

@pavithraes thank you for the welcome! I am more than happy to submit a PR.


Stefan-Maxwell diffusion and convective transport

I have implemented Stefan Maxwell multicomponent diffusion for the simplified case of ideal gases at constant pressure and temperature in the corresponding Pluto notebook
Before proceeding I have two questions:

What is the most convenient way to express the gas phase species composition? Weng et al use mass fractions, the Stefan-Maxwell implementation was based on mole fractions. I believe the choice here could be informed by how the address question 2.
How to incorporate the convective transport into the Stefan-Maxwell framework? Weng et al compute a mass averaged velocity from Darcy's equation of porous media transport.

Well, need to think deeper about it.
In our paper, we used partial pressures, and the averaged gas phase velocity just would come from Stefan-Maxwell (but is not needed).
We used convection only for the species dissolved in the liquid phase, there the liquid velocity was used as the convection velocity.
Also note that we introduced a saturation curve parametrization which we hoped can be well adapted to the more hydrophobic matrix.

Thanks a lot for your input.
After taking another look at your paper, I believe that for the gas phase species transport the employed mean transport pore model (MTPM) described in reference 26 in your paper is a modification of the Stefan-Maxwell formulation that also accounts for convective transport based on Darcy's law. It compares the MTPM with the dusty gas model, which yielded similar results in their case. I plan to include one of these models for the gas phase transport within the porous media.


Box prints error when .env_override is not present

The .env_override file is only generated by github-actions for testing, and will not be generated by normal use. Fix so that this prints a sensible message.

Fixed in #181


Issue 128

Standalone model report complete content-wise. Remains some TODOs to clean up code, move to PDS tools library and generally make sure it is robust and the numbers compare visavis the R version.

Process Mining is going to get some abbreviation competition with Mr. Mann if he keeps thinking of new plots ;)

Will send a new one in - most remarks left as TODOs for now


feat(run): Tokens expire after 1 hour - use Tokensource instead.

The current example manually adds a token to each client request. For some longer running services, this becomes an issue since the client is usually instantiated when launching the service, requests made after 1 hour of the initial client instantiation will fail since the token will have expired by then.
Rather use the TokenSource methodology where the underlying token is validated and only refreshed when needed.

@grayside you mentioned that you would like to see the changes made to the request_auth.go file, and not inside the NewConn() function.   Not sure whether this is possible, without changing the signature of the pingRequestWithAuth method - which receives conn *grpc.ClientConn parameter.  The Tokensource is added via the options with the grpc.Dial(host, opts...) method which returns a connection.

In light of @grayside 's comments above, it seems like we want to address this in a different way, so i'll reopen your initial issue #2139 and close this PR. All updates (and PRs) will be linked to your issue, so you can stay up to date on our progress.
Thanks for your patience!


A small request.

1; ".ts" and ".mkv" extensions do not open.
2; Need mobile support ".ts" and ".mkv". It plays ".mp4". Others are troubled.

Sure I will do it sooner or later because now I (myself) need this too 😉
Please wait, while in these days life are tough for me...


Error when running RoslynPad 14.1 on MacOS

Hi!
When I try to run the .net Core version for Mac/Linux as described in instructions, I get the following error.
dotnet RoslynPad.dll
Error:
  An assembly specified in the application dependencies manifest (RoslynPad.deps.json) was not found:
    package: 'System.Drawing.Common', version: '4.5.0'
    path: 'runtimes/unix/lib/netcoreapp2.0/System.Drawing.Common.dll'

Duplicate of #249 - you're missing some files when unzipping


Py3 support

when django-datatable==0.1.5 some files (like tables/utils.py) aren't py3 compatible.
The code seems fixed in the repo but no version was published whit that changes

pip install<EMAIL_ADDRESS>solved the issue, but still a new version would be better

@matheusjardimb Thanks for your feedback, checkout v0.2.0 on pypi please.


Add logic to set MSBuildExtensionsPath to Mono's xbuild directory

I'm cherry-picking this change from https://github.com/OmniSharp/omnisharp-roslyn/pull/915, since it's unrelated to that PR.
Fixes #892
Fixes https://github.com/OmniSharp/omnisharp-vscode/issues/1597
Fixes https://github.com/OmniSharp/omnisharp-vscode/issues/1624
Fixes https://github.com/OmniSharp/omnisharp-vscode/issues/1396
Related PR: https://github.com/mono/msbuild/pull/22

Got additional changes coming for this.

I kicked off the build again

@filipw: This isn't ready yet. Got another important change coming that actually fixes this.

👍

@filipw: Do you want to take another look?

looks good!
maybe at some point we can allow passing in mono locations too, in case you run a customized build or a local from a custom location

@filipw: Maybe. I'm not sure that's a very common scenario though. At least, I've never heard an ask for it.

OK. Got one more change to make.

OK. I've done more testing on this today and it seems to work reasonably well.


[Name lookup] Add a test & don’t look for a module with a special name.

A fix for SR-10949 and a test.

@swift-ci please smoke test and merge


Really basic data-types for snooze improvements.

This is a nothing change, but putting it up as a heads up that I am going to start pushing through a series of improvements to snooze. They are basically of the form:

Convert to a unified snooze structure for maintaining the client registry rather than 1 snooze bag per service.
Add first-class support for snooze uri's so services can use them as location headers.
A neater api for constructing requests and handling responses.
First class support for passport style request-id threading.
Support for outbound request logging for internal services.

This is basically a first cut at some of the extra types that will be needed to do the above.

@charleso

:+1:


Error while trying to authorize org

Summary
Since last two days, I have encountered error in both existing and brand new projects, when I get "Cannot read property 'getInstance' of undefined " while trying to authorize an org (sandbox).
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc

Clone the repository.
Try to authorize an org with command "sfdx force:auth:web:login --setalias sandbox --instanceurl https://test.salesforce.com --setdefaultusername --dev-debug"

Expected result
A browser window with login option should appear.
Actual result
I got an error "ERROR running force:auth:web:login:  Cannot read property 'getInstance' of undefined"
Additional information
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.69.0 win32-x64 node-v12.13.0
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.7.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/lwc-dev-server 2.5.1
├─ @oclif/plugin-help 2.2.3
└─ @oclif/plugin-update 1.3.9
@salesforce/sfdx-diff 0.0.6
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.12.0 (core)
generator 1.1.3 (core)
salesforcedx 49.5.0
├─ custom-metadata 1.0.8
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7
├─ salesforcedx-templates 49.2.0
└─ salesforce-alm 49.5.0
sfdmu 3.5.10
sfdx-cli 7.69.0 (core)
OS and version:
Windows 10 Pro x64
Debug log
debuglog.txt

I receive the same error when running "force:org:list" and other commands.
Temporary workaround: install an older version of the CLI. It may cause other problems, but it allowed me to finally start working today:      sfdx plugins:install<EMAIL_ADDRESS>

I would also recommend you to do an uninstall of salesforce-alm plugin : sfdx plugins:uninstall salesforce-alm and see if that resolves the issue.


libmaxminddb: 1.7.1 -> 1.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/libmaxminddb/versions.
meta.description for libmaxminddb is: C library for working with MaxMind geolocation DB files
meta.homepage for libmaxminddb is: https://github.com/maxmind/libmaxminddb
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.8.0 with grep in /nix/store/4q8vkd3s0swfy417n0cnp7hnnx8a98bn-libmaxminddb-1.8.0
found 1.8.0 in filename of file in /nix/store/4q8vkd3s0swfy417n0cnp7hnnx8a98bn-libmaxminddb-1.8.0

Rebuild report (if merged into master) (click to expand)

1389 total rebuild path(s)

1389 package rebuild(s)

First fifty rebuilds by attrpath
almanah
ansible
ansible-doctor
ansible-later
ansible-lint
ansible_2_13
ansible_2_14
ansible_2_15
barman
beancount
breezy
browsr
buildbot
buildbot-full
buildbot-ui
cabal2nix
calcurse
cantor
ceph
ceph-client
ceph-csi
ceph-dev
certbot-full
chatgpt-retrieval-plugin
chia
chia-dev-tools
compactor
conan
crackmapexec
credslayer
datalad
dbmonster
deface
deja-dup
dep2nix
devpi-client
dnstwist
duplicity
duply
dvc
dvc-with-remotes
easyocr
echidna
evolution
evolution-ews
evolutionWithPlugins
executor
fava
flatpak-builder
frigate

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4q8vkd3s0swfy417n0cnp7hnnx8a98bn-libmaxminddb-1.8.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libmaxminddb https://github.com/r-ryantm/nixpkgs/archive/c1bb6baf1c228048d63d2f5085a2a81933e189b1.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c1bb6baf1c228048d63d2f5085a2a81933e189b1#libmaxminddb

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4q8vkd3s0swfy417n0cnp7hnnx8a98bn-libmaxminddb-1.8.0
ls -la /nix/store/4q8vkd3s0swfy417n0cnp7hnnx8a98bn-libmaxminddb-1.8.0/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @ajs124 for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/maxmind/libmaxminddb/releases.
meta.description for libmaxminddb is: C library for working with MaxMind geolocation DB files
meta.homepage for libmaxminddb is: https://github.com/maxmind/libmaxminddb
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.9.1 with grep in /nix/store/f36qnfdv73hw3lrl77qfdnhcj29hkakg-libmaxminddb-1.9.1
found 1.9.1 in filename of file in /nix/store/f36qnfdv73hw3lrl77qfdnhcj29hkakg-libmaxminddb-1.9.1

Rebuild report (if merged into master) (click to expand)

2081 total rebuild path(s)

2081 package rebuild(s)

First fifty rebuilds by attrpath
aitrack
almanah
ansible
ansible-doctor
ansible-later
ansible-lint
ansible_2_14
ansible_2_15
ansible_2_16
asn1editor
barman
beancount
breezy
browsr
buildbot
buildbot-full
buildbot-ui
cabal2nix
calcurse
cantor
ceph
ceph-client
ceph-csi
ceph-dev
certbot-full
cfripper
chatgpt-retrieval-plugin
coconut
compactor
conan
crackmapexec
credslayer
datalad
dbmonster
deface
deja-dup
dep2nix
devpi-client
dnstwist
duplicity
duply
dvc
dvc-with-remotes
easyocr
echidna
esphome
evolution
evolution-ews
evolutionWithPlugins
executor

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f36qnfdv73hw3lrl77qfdnhcj29hkakg-libmaxminddb-1.9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libmaxminddb https://github.com/r-ryantm/nixpkgs/archive/bfe565b38722e3e26356d00c9da8a7a24b1a1e2e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/bfe565b38722e3e26356d00c9da8a7a24b1a1e2e#libmaxminddb

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/f36qnfdv73hw3lrl77qfdnhcj29hkakg-libmaxminddb-1.9.1
ls -la /nix/store/f36qnfdv73hw3lrl77qfdnhcj29hkakg-libmaxminddb-1.9.1/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @ajs124 @dasJ for testing.


Send buttons and axes data

Right now only Gyro + Accelaration is sent to a client.
Add buttons and axes too.
Explore possibility of sending also touch input (it's not part of Steam Deck Controls HID device, would have to be acquired with another method).

Hid Frame and cemuhook telegram are described with field names and comments. It just has to be mapped accordingly in CemuhookAdapter. Then Cemuhook Server has to pull the data from adapter at the same time when it pulls motion data.

This would be useful to essentially replace a Wii U Gamepad one for one with a steam deck.


[Basic] DistributedLock

Add Basic.DistributedLock modeled after NSDistributedLock. It uses Foundation.NSDistributedLock on macOS and _DistributedLock on other platforms.

Is this for locking Workspace operations? We already have a FileLock implementation that we can use to do that: https://github.com/apple/swift-package-manager/blob/master/Sources/Basic/Lock.swift#L37

Is this for locking Workspace operations?

unlikely tbh. flock is a better approach - FileLock could use some thread safety though.
to be honest, I found it not implemented and had some fun reverse-engineering

You should try adding it in corelibs-foundation if it's missing there :)


Fix invalid memory usage when using Image.convert

Fixes #46479
rofs points to the input pixel which does not have to be 4 bytes long.
AddressSanitizer only complains on 3.x probably because allocation on master is always rounded to power of 2.

It raises errors since there are branches where rgba may not be fully initialized, as it depends on max_bytes:
ore/io/image.cpp: In member function 'void Image::convert(Image::Format)':
core/io/image.cpp:439:12: error: 'rgba[1]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  439 |    uint8_t rgba[4];
      |            ^~~~
core/io/image.cpp:439:12: error: 'rgba[2]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
core/io/image.cpp:457:44: error: 'rgba[1]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  457 |     wofs[0] = uint8_t((uint16_t(rgba[0]) + uint16_t(rgba[1]) + uint16_t(rgba[2])) / 3);
      |                                            ^~~~~~~~~~~~~~~~~
core/io/image.cpp:439:12: note: 'rgba[1]' was declared here
  439 |    uint8_t rgba[4];
      |            ^~~~
core/io/image.cpp:457:64: error: 'rgba[2]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  457 |     wofs[0] = uint8_t((uint16_t(rgba[0]) + uint16_t(rgba[1]) + uint16_t(rgba[2])) / 3);
      |                                                                ^~~~~~~~~~~~~~~~~
core/io/image.cpp:439:12: note: 'rgba[2]' was declared here
  439 |    uint8_t rgba[4];
      |            ^~~~
core/io/image.cpp:457:64: error: 'rgba[2]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  457 |     wofs[0] = uint8_t((uint16_t(rgba[0]) + uint16_t(rgba[1]) + uint16_t(rgba[2])) / 3);
      |                                                                ^~~~~~~~~~~~~~~~~
core/io/image.cpp:457:64: error: 'rgba[2]' may be used uninitialized in this function [-Werror=maybe-uninitialized]
  457 |     wofs[0] = uint8_t((uint16_t(rgba[0]) + uint16_t(rgba[1]) + uint16_t(rgba[2])) / 3);
      |                                                                ^~~~~~~~~~~~~~~~~

Does it calculate gray values correctly though? For example for:
https://github.com/godotengine/godot/blob/34c1a2beaa8ae92a445b85458d3681f60cd5216f/core/io/image.cpp#L555-L557
https://github.com/godotengine/godot/blob/34c1a2beaa8ae92a445b85458d3681f60cd5216f/core/io/image.cpp#L430-L431
which is (red, green), no alpha, no gray -> (red), no alpha, gray it would convert (255, 255) to (170) because it would treat blue as zero. Is it intended and that's how this method is supposed to work? Or should it in such case calculate the output gray value only based on the available input channels?

Calling Image.get_pixel() on RG(255, 255) gives you Color(1, 1, 0, 1) instead of Color(1, 1, 1, 1). From this perspective, the gray value of that color is indeed 0.7255.
Other conversions such as RG to RGB also treat missing color component as 0. So converting RG -> L directly is the same as converting RG -> RGB -> L. I think the current behavior is acceptable.

Thanks!

Cherry-picked for 3.5.

Cherry-picked for 3.4.5.


I just want to point out

wild world and Let's go the City are missing both their snow and rain versions. I've got the tunes on my flash drive if you need them.

Hey AnimeGedk01,
Thanks for the offer but it's on the coding part that we could do with some help. So unless you can find someone to help in that way too these files won't be much use. But still thanks!

Hi @AnimeGeek01 - this is being worked on very soon!
We appreciate your offer, but we wouldn't want you getting in trouble distributing those files.

Song have been added in PikaDude/ac-music-extension-revived#1


Reverse Maneuver Icons

Here are high resolution scans of the reverse left, reverse straight and reverse right maneuvers from a quadjumper dial.  I hope you can use them.

Feel free to contact me at<EMAIL_ADDRESS>if there is a better way to submit these to you.

These have been added - Thanks for the scans!


[5.4][Build] Add and use option to alter default location of module cache in Linux

Explanation: Introduce a mechanism to relocate the default location of the clang module cache under the current build directory and adopt that for Linux presets, so to reduce the likelihood of issues in reading the module cache
Cherry picks #35711, #35743
Resolves: rdar://73574479
Scope: addition of an opt-in flag to build-script
Risk: Low -- the same code is used for main CI runs
Testing: Swift CI

@swift-ci please test

@swift-ci please nominate


Update all dependencies

Summary
Provide a summary of the change...
Checklist

[ ] Tested changes end to end
[ ] Any config changes added to all environment files
[ ] For Flex features added, ensure the feature list on the README on the project root folder is updated
[ ] Completed README template for new features

[ ] Feature summary - high level summary of what the feature does
[ ] Flex User Experience with animations - animations with descriptions if necessary of the user experience in Flex
[ ] Setup and dependencies - description of any setup steps required for this feature
[ ] How does it work? - description of plumbing supporting feature

[ ] Added PR Label "ready-for-review"
[ ] Requested one or more reviewers for the PR

Successfully tested all CI workflows after updates.


Need to store data for this email update

I want to contribute.. I use ASP.Net core and MySql if accepted..

@SahityaRoy it will be easier for me to do the same as I already have same functionality in contact form so it will be better to store this data in same database.


Optimizations & compact classes

Some classes where deprecated for compact ones.
A good amount of bugs where fixed too.

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update log values

Firewall Actions:
simulate -> log
drop -> block
Old log is removed.
Firewall Source:
sanityCheck -> validation
IP Class:
whitelist -> allowlist
Deprecates WAFFlags and WAFMatchedVar.

Any changes under products/logs/src/content/log-fields/_partials/ must be done on the internal logshare-api repo, otherwise any change here will be lost (as the contents of these files are based on the templates there).
I think you have updated some there, but make sure all are up-to-date.


Switch CircleCI from docker executor to machine executor

The docker executor does not support docker volume mounting within

Okay, looks like this has resolved the docker volume mounting issue. Apparently this is a known caveat of the docker-type executors on circleci, and you need to use a machine-type executor to have volume mounting capabilities for docker commands run within. The commands are now working the same as they did when I tested locally. Nice work on the pytests @gshiroma, and sorry they've taken so long to integrate with our CI system!


EAS HMP-parity test improvements

A number of improvements to fix tests failing when they shouldn't. The new "Offload migration and idle pull" test needs an updated bart.  Trappy also has a new version, so update both modules while we are at it.

We should have done the submodules update on Friday, but we forgot it. Could you please add the update to devlib as well in the third commit? Otherwise we could push a separate PR for submodules' updates...

@Michele why don't you just push a patch which progress all the submodules... than this PR from Javi will just skip the submodules update patch.

@derkling yes, that's what I was thinking... Let's do it! :smile:

ok, rebased on top of master and dropped the submodules update

Could you also remove the hard-coded values in WakeMigration? Like this one:
https://github.com/JaviMerino/lisa/blob/2e2242e77ddaefd34e0e10d8d1d7d1703b1766bf/tests/eas/hmp_parity.py#L632

Few comments but overall is a really good and valuable rework of these tests, thanks @JaviMerino for the effort! Once fixed the two remaining minor nits it's ok for me to merge, @mdigiorgio can you do it?

Sure :+1:

The new upload removes OFFLOAD_MIGRATION_MIN_BIG_RESIDENCY and the hardcoded values in WakeMigration.


Add a couple things to the email verification

Add a timeout system and re-request email-verification to the system (1 new db column, 1 new endpoint)

Completed by commit #44adb25


port forward for Gadgetron

https://github.com/CCPPETMR/CCPPETMR_VM/blob/4536ce8db9409bd3575b79b3de08d0037cba769b/vagrant/Vagrantfile#L36
forwards 8888. Should add 9001 and 9002 for Gadgetron, removing one step for the user.

By the way, no need to do this before the PSMR course.


Errors are passed incorrect from csqldb Object

After experimenting with the php native connector I've figured out that errors that occur within the csqldb Object are not passed through the cubeSQLServer Object. So checking for errors always returned false in that case:

The reason was that the defined properties of the csqldb object were called errcode and errmsg while the exception handler created new properties called errorcode and errormsg.
In the upcoming pull request I've changed the properties to errorcode and errormsg and fixed the referencing of the cubeSQLServer methods to point to the same.
After that the errors get passed correctly:

I checked the code for further occurrences of the terms errcode and errmsg but none were left so the error-handling should be correct now for all types of errors.

Very good catch, thanks a lot!


English version

need english version

thanks for your suggestion :smile:

maybe I can help, I translated some pages and remove all your personal information. We can keep two branches.

@godlzr
Thank you for the translation. Could you please submit a PR to deveop branch and help me finish I18N.
A small suggestion,keep the coffeescript for the moment :smile:
Thank you once again :clap:


spotify: Add nightly

Instllation, uninstallation and application itself is working well.
Currently being tested. I will see in few days how updates are behaving in custom folder

Worked for like a couple times until I hit this.
Htting Retry will hang the installer forever. So will an attempt to abort it. (Only way is to bring it down via Task Manager).
Since then, the installation is now bricked. I have a suspicion that this might be happening to Premium users and might be due to the offline mode feature (download stuff).
Repro Steps

Log in from a premium account;
Download your list of liked songs;
Reboot (I guess);
Congratulations, your installation is bricked.

As a side note, though, it'd be awesome if we could keep data in persist (login info, downloaded songs, etc.) and only delete it if we uninstalled with -p - even if that meant that we had to mess with the AppData directory (basically replace the AppData/Roaming/Spotify directory with a junction to scoop/persist/spotify)


Rename v1beta1 clients for test

Changes

This commit renames the v1beta1 apiVersion of clients and adds the apiVersion to ./parse/yaml.go for test.
/kind misc
cc @lbernick @XinruZhang
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[n/a] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[n/a] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[n/a] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind misc

/retest

/retest

/retest
The codes in CI are not updated.

/retest

Needs to incorporate the changes at https://github.com/tektoncd/pipeline/commit/2d38f5fa840291395178422d34b36b1bc739e2a2

/lgtm


Change DPI

Would it be possible to implement a way to change the dpi on the headunit?

I believe this will require us to decode and act as man-in-the-middle for the AA communication. We currently simply pass through all communication as is. While not impossible, this would certainly add much more complexity.


[GF Profile] Add checks for descriptions

Marc requested changes to descriptions in https://github.com/google/fonts/pull/1908#issuecomment-507170360 that we should have checks for.

Description.en_us.html: mention the upstream url, e.g amaticsc
This is checked by com.google.fonts/check/description/git_url
Description.en_us.html: mention that the fonts are vf
This is checked by com.google.fonts/check/description/variable_font

And those checks were indeed executed correctly on the Inter PR:


TravelChannel is broken again

Much love and whats with the spamsville...
Hope it doesnt bury this, but right now travel channel is broken again.
seems like some patchwork is needed
got this - https://www.travelchannel.com/shows/ghost-adventures/episodes/ripleys-believe-it-or-not
to turn into this - https://sni-i.akamaihd.net/i/0284/0284476_,6,5,4,3,2,1,.mp4.csmil/master.m3u8
and it works with streamlink, please fix when you get the time.
Thanks so much your totally awesome!

Much love and whats with the spamsville...
Hope it doesnt bury this, but right now travel channel is broken again.
seems like some patchwork is needed
got this - https://www.travelchannel.com/shows/ghost-adventures/episodes/ripleys-believe-it-or-not
to turn into this - https://sni-i.akamaihd.net/i/0284/0284476_,6,5,4,3,2,1,.mp4.csmil/master.m3u8
and it works with streamlink, please fix when you get the time.
Thanks so much your totally awesome!

getting buried now

thanks swizzy figure my legit bug sandwich is easier to find now, dude spend that time tweeting POTOUS or something hahaha


feat: generate the trace of execution

Generate the trace of a cairo execution. Include in the CI a way to run and generate the trace with another battle tested VM (such as the python or rust cairo VM) and compare both generated traces.

The trace has been implemented, still needs to handle diff testing with another VM and integrate it in the CI.
Re-scoped in #59


Error mounting IMG (wrong fs type, bad option, bad superblock)

Hi,
i have problem like in this #176
2 different machines (both Linux Mint 20.2 based on Ubuntu 20.04, x86_64) and i get error:
mount: /mnt/sdm: wrong fs type, bad option, bad superblock on /dev/loop26, missing codepage or helper program, or other error
mount: /mnt/sdm/boot: mount point does not exist
? Error mounting IMG '2023-12-11-raspios-bookworm-armhf-lite.img'

i run command from documentation: sudo sdm --customize --plugin user:"adduser=bls|password=mypassword" --plugin L10n:host --plugin disables:piwiz --regen-ssh-host-keys --restart 2023-12-11-raspios-bookworm-armhf-lite.img
sdm v11.4
mini-nspawn output is ok without errors
i work with freshly downloaded latest 2023-12-11-raspios-bookworm-armhf-lite.img image
thank you

i have found error in linux dmesg:
EXT4-fs (loop40): VFS: Can't find ext4 filesystem

@gitbls done, i successfully burnt with sdm img to medium and i was able sdm --mount this medium

Thx. That confirms for me that it's a bug in old Ubuntu and Mint releases, and will work around it.

sudo sdm --customize --plugin apps:"apps=@myapps" 2023-12-11-raspios-bookworm-armhf-lite.img
i get this error:
* Mount IMG '2023-12-11-raspios-bookworm-armhf-lite.img'
mount: /mnt/sdm: wrong fs type, bad option, bad superblock on /dev/loop40, missing codepage or helper program, or other error
? IMG '' already attached to a loop device

OK, thx. Will instrument up more logging to see what's going on.

here is output:
* Mount IMG '2023-12-11-raspios-bookworm-armhf-lite.img'
Before 'new' mount
mount: /mnt/sdm: wrong fs type, bad option, bad superblock on /dev/loop40, missing codepage or helper program, or other error
Before 'old' mount
? IMG '' already attached to a loop device

Strange. Investigating...

Please try this version.
sdm-cparse.zip

there are some errors, but i think it works:)
in output there are czech words, translation:
odpojení selhalo: Takové zařízení nebo adresa neexistuje - unmount failed: this device or address does not exists
připojeno - mounted
odpojeno, odpojen - unmounted
* Mount IMG '2023-12-11-raspios-bookworm-armhf-lite.img'
Before 'new' mount
Before 'old' mount
% Delete dangling loop device '/dev/loop40'
  /dev/loop40<PHONE_NUMBER>      0         1  0 /home/ondicz/sdm/2023-12-11-raspios-bookworm-armhf-lite.img   0     512
losetup: /dev/loop40: odpojení selhalo: Takové zařízení nebo adresa neexistuje
mount: /dev/loop40p2 připojeno do /mnt/sdm.
mount: /dev/loop40p1 připojeno do /mnt/sdm/boot/firmware.
After 'old' mount
* Start Configuration
> Command Line: /usr/local/bin/sdm --customize --plugin apps:apps=@myapps
  2023-12-11-raspios-bookworm-armhf-lite.img
* Host Information
   Hostname: rimmer
   uname: Linux rimmer 5.4.0-172-generic #190-Ubuntu SMP Fri Feb 2 23:24:22 UTC 2024 x86_64
  x86_64 x86_64 GNU/Linux
   os-release Name: Linux Mint 20.3
   Version: 20.3 (Una) (una)
   Like OS: ubuntu
   sdm Version: V11.4
* IMG Information
   Name: 2023-12-11-raspios-bookworm-armhf-lite.img
   Date: 2023-12-11
   RasPiOS Version: 12
   RasPiOS Architecture: 32-bit armhf
   os-release Version: 12 (bookworm)
% sdm will use systemd-nspawn on this 'x86-64' host
  Retry the command with --chroot if this fails
* Plugins selected:
   * apps
       Args: apps=@myapps
> IMG '2023-12-11-raspios-bookworm-armhf-lite.img' has 299532 1K-blocks (0,3GB, 0,3GiB) free
> Copy sdm to /usr/local/sdm in the IMG
* Start Phase 0 image customization
> Run Plugins Phase '0'
> Run Plugin 'apps' (/mnt/sdm/usr/local/sdm/plugins/apps) Phase 0 with arguments: 'apps=@myapps'
* Plugin apps: Start Phase 0
> Plugin apps: Keys/values found:
   apps: @myapps
?  file '/home/ondicz/sdm/myapps' not found
? Plugin 'apps' exited with failure
umount: /mnt/sdm/boot/firmware odpojen
umount: /mnt/sdm odpojen

Great! I will make the "odpojenf" and the "Delete dangling loop devices" messages go away, so it will be pretty seamless.
This will be in the next release, coming soon. I'll update this thread when it's available.

one more thing. Could you check and see if there are any unexpected, sdm-ish looking loop devices hanging around after you run sdm?
sudo losetup -a

Thx

one more thing. Could you check and see if there are any unexpected, sdm-ish looking loop devices hanging around after you run sdm?
sudo losetup -a

Thx

i see only my snap applications

Could I convince you to try this updated version just to make sure I didn't duff it?
sdm-cparse.zip
Thx!

sure, here it is:
* Mount IMG '2023-12-11-raspios-bookworm-armhf-lite.img'
mount: /dev/loop40p2 připojeno do /mnt/sdm.
mount: /dev/loop40p1 připojeno do /mnt/sdm/boot/firmware.
* Start Configuration
> Command Line: /usr/local/bin/sdm --customize --plugin apps:apps=@myapps
  2023-12-11-raspios-bookworm-armhf-lite.img
* Host Information
   Hostname: rimmer
   uname: Linux rimmer 5.4.0-172-generic #190-Ubuntu SMP Fri Feb 2 23:24:22 UTC 2024 x86_64
  x86_64 x86_64 GNU/Linux
   os-release Name: Linux Mint 20.3
   Version: 20.3 (Una) (una)
   Like OS: ubuntu
   sdm Version: V11.4
* IMG Information
   Name: 2023-12-11-raspios-bookworm-armhf-lite.img
   Date: 2023-12-11
   RasPiOS Version: 12
   RasPiOS Architecture: 32-bit armhf
   os-release Version: 12 (bookworm)
% sdm will use systemd-nspawn on this 32-bit x86-64 host
  Retry the command with --chroot if this fails
* Plugins selected:
   * apps
       Args: apps=@myapps
> IMG '2023-12-11-raspios-bookworm-armhf-lite.img' has 299512 1K-blocks (0,3GB, 0,3GiB) free
> Copy sdm to /usr/local/sdm in the IMG
* Start Phase 0 image customization
> Run Plugins Phase '0'
> Run Plugin 'apps' (/mnt/sdm/usr/local/sdm/plugins/apps) Phase 0 with arguments: 'apps=@myapps'
* Plugin apps: Start Phase 0
> Plugin apps: Keys/values found:
   apps: @myapps
?  file '/home/ondicz/sdm/myapps' not found
? Plugin 'apps' exited with failure
umount: /mnt/sdm/boot/firmware odpojen
umount: /mnt/sdm odpojen

Thanks!

This is all fixed 🤞in V11.5. Please test/verify. Thx!

v11.5 is ok

Excellent. Thanks for helping me sort this out. Still strange that I coudn't repro it here on Mint 20.2 😵


Cross v0.1.15 Breaks f64 Modulus on i686

The following code worked for cross v0.1.14, so any issues were introduced with the latest release.
Targets

i686-unknown-linux-gnu

x86_64 works fine, so the issue only occurs on 32-bit x86.
Failing Code
fn main() {
    let value: f64 =<PHONE_NUMBER>0414620.0;
    let base: f64 = 17.0;
    println!("value % base = {:?}", value % base);
}

Results
value % base = -4.0

The value is negative for the float modulus, rather than 15.0.  Running with target x86_64-unknown-linux-gnu prints the expected result (15.0).
Minimal Steps to Reproduce

Create a repository (cargo new --bin sample).
Copy the failing code into main.rs.
Run the binary on i686 (cross run --target i686-unknown-linux-gnu).

Finally, this code works with cargo run --target i686-unknown-linux-gnu.

Update: Running the generated binary without qemu produces the desired result, while running it with Qemu fails. This seems to be a bug in Qemu.
$ uname -a
Linux ahuszagh.localdomain 5.2.7-100.fc29.x86_64 #1 SMP Thu Aug 8 05:30:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ qemu-i386 --version
qemu-i386 version 3.0.1 (qemu-3.0.1-4.fc29)
cross --version
cross 0.1.15
cargo 1.37.0 (9edd08916 2019-08-02)
$ target/i686-unknown-linux-gnu/debug/sample
value % base = 15.0
$ qemu-i386 target/i686-unknown-linux-gnu/debug/sample
value % base = -4.0

Compiling the binary with an older version of cross (v0.1.14) and then executing it with a newer version of Qemu fails:
$ qemu-i386 --version
qemu-i386 version 3.0.1 (qemu-3.0.1-4.fc29)
$ cross --version
cross 0.1.14
cargo 1.37.0 (9edd08916 2019-08-02)
$ cross build --target i686-unknown-linux-gnu
    Finished dev [unoptimized + debuginfo] target(s) in 0.10s
$ target/i686-unknown-linux-gnu/debug/sample
value % base = 15.0
$ qemu-i386 target/i686-unknown-linux-gnu/debug/sample
value % base = -4.0

Confirmed a Qemu bug. Will file upstream.
Source
a.c
#include <math.h>
#include <stdio.h>

int main()
{
    double x =<PHONE_NUMBER>0414620.0;
    double y = 17.0;
    double z = fmod(x, y);
    printf("%f\n", z);
    return 0;
}

Compile Command
$ gcc --version
gcc (GCC) 8.3.1 20190223 (Red Hat 8.3.1-2)
$ gcc a.c -o a -m32 -lm

Calling
$ ./a
15.000000
$ qemu-i386 a
-4.000000

@reitermarkus This is a separate issue from #314.
First, cross v0.1.14 did not use qemu for i686. No version of qemu works, on i686 (really the i387, since this is all going to be done by the FPU), to my understanding. I've tested 2.10.0, 3.0.1, 4.1.0, and the latest commit as of testing.
I've filed the bug upstream, and is available here:
https://bugs.launchpad.net/qemu/+bug/1843205
As the bug is upstream, and no working versions of qemu seem to exist, I'm not sure if there's anything cross should do, since the alternative is the i686 target only works on x86.

So it should work running natively inside the Docker container?

Yes, on x86 or x86_64. In practice, I doubt anyone will be running cross on anything other than x86 or ARM.

We could check uname -m, and if the value is i386, i486, i586, i686, or x86_64, then just run the binary natively.

Non-x86 hosts aren't supported at the moment, and I doubt there is any demand for it, so this should be fine.
Look at the linux-runner script, we can make CROSS_RUNNER default to native with the uname check, otherwise to qemu-user.

Would something like this work? If we're assuming the host is x86, then we don't need to check the machine hardware name: every host should be able to run an i686 binary (this bug doesn't occur for x86_64).
diff --git a/docker/linux-runner b/docker/linux-runner
index 9e1e1e7..1d58759 100755
--- a/docker/linux-runner
+++ b/docker/linux-runner
@@ -14,7 +14,14 @@ arch=$1
 shift

 if [ "$CROSS_RUNNER" = "" ]; then
-    CROSS_RUNNER=qemu-user
+    if [ "$arch" = i686 ]; then
+        # override 32-bit x86 targets to run natively (assume host is x86).
+        # workaround for upstream issue in qemu for the i386 target
+        # https://bugs.launchpad.net/qemu/+bug/1843205
+        CROSS_RUNNER=native
+    else
+        CROSS_RUNNER=qemu-user
+    fi
 fi

 # select qemu arch

Yes, I think that should work. I think we should default to native on all targets where this is possible.


there is something missing and cannot work as doc said.

Type of issue
Missing information
Feedback
I have followed doc to create my first winui app, I chosed windows app dev and installed VS successfully. Then I created a new project of winui blank app, it just has so many error info, like this:
错误	XLS0414	未找到类型“Application”。请确保不缺少程序集引用并且已生成所有引用的程序集。
Page URL
https://learn.microsoft.com/zh-cn/windows/apps/get-started/start-here?tabs=vs-2022-17-10
Content source URL
https://github.com/MicrosoftDocs/windows-dev-docs/blob/docs/hub/apps/get-started/start-here.md
Author
@GrantMeStrength
Document Id
2a20f1ff-c80a-902a-559d-e4294dde69e4

just need to download the Windowsappsdk，maybe it's the network problem.


Basic Authentication

While I understand the Exchange PowerShell Module doesn't pass the username and password using basic authentication, company policies, and government security requirements prevent us from enabling WinRM basic authentication. Is there another method to connect to Exchange PowerShell such as the Azure CLI? What other workarounds are available? I did not have this issue with the previous version and MFA/modern authentication.

@officedocsbot assign @yogkumgit

Hi @mltytskr, thank you for your feedback.
I understand there is no way at the moment. You can see similar threads:
https://github.com/MicrosoftDocs/office-docs-powershell/issues/4504
https://github.com/MicrosoftDocs/office-docs-powershell/issues/4306
You can provide this feedback either on the Exchange Team´s blog or in the Office 365 Admin/Exchange Admin UserVoice forum.


Error Setup failed for custom integration uptime_kuma

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
In Logs i'm getting this error
Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6'].
👟 Reproduction steps
By turning on my HA OS.
👀 Expected behavior
That I will not get any errors.
😓 Actual Behavior
Setup failed for custom integration uptime_kuma: Requirements for uptime_kuma not found: ['pyuptimekuma==0.0.6'].
🐻 Uptime-Kuma Version
0.6.0
💻 Operating System and Arch
Ubuntu 20.4
🌐 Browser
Google Chrome
🐋 Docker Version
No response
🟩 NodeJS Version
No response
📝 Relevant log output
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: Uptime Kuma
 It is a self-hosted monitoring tool like "Uptime Robot"
-----------------------------------------------------------
 Add-on version: 0.6.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (amd64 / qemux86-64)
 Home Assistant Core: 2023.3.1
 Home Assistant Supervisor: 2023.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service uptime-kuma: starting
s6-rc: info: service uptime-kuma successfully started
s6-rc: info: service legacy-services: starting
[12:20:04] INFO: Starting Uptime Kuma...
s6-rc: info: service legacy-services successfully started
Welcome to Uptime Kuma
Your Node.js version: 18
2023-03-06T12:20:04+02:00 [SERVER] INFO: Welcome to Uptime Kuma
2023-03-06T12:20:04+02:00 [SERVER] INFO: Node Env: production
2023-03-06T12:20:04+02:00 [SERVER] INFO: Importing Node libraries
2023-03-06T12:20:04+02:00 [SERVER] INFO: Importing 3rd-party libraries
2023-03-06T12:20:06+02:00 [SERVER] INFO: Creating express and socket.io instance
2023-03-06T12:20:06+02:00 [SERVER] INFO: Server Type: HTTP
2023-03-06T12:20:06+02:00 [SERVER] INFO: Importing this project modules
2023-03-06T12:20:06+02:00 [NOTIFICATION] INFO: Prepare Notification Providers
2023-03-06T12:20:06+02:00 [SERVER] INFO: Version: 1.20.1
2023-03-06T12:20:06+02:00 [PLUGIN] WARN: Warning: In order to enable plugin feature, you need to use the default data directory: ./data/
2023-03-06T12:20:06+02:00 [DB] INFO: Data Dir: /data/
2023-03-06T12:20:06+02:00 [SERVER] INFO: Connecting to the Database
2023-03-06T12:20:06+02:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-03-06T12:20:06+02:00 [DB] INFO: SQLite Version: 3.39.4
2023-03-06T12:20:06+02:00 [SERVER] INFO: Connected
2023-03-06T12:20:06+02:00 [DB] INFO: Your database version: 10
2023-03-06T12:20:06+02:00 [DB] INFO: Latest database version: 10
2023-03-06T12:20:06+02:00 [DB] INFO: Database patch not needed
2023-03-06T12:20:06+02:00 [DB] INFO: Database Patch 2.0 Process
2023-03-06T12:20:06+02:00 [SERVER] INFO: Load JWT secret from database.
2023-03-06T12:20:06+02:00 [PLUGIN] WARN: Skip scanning plugin directory
2023-03-06T12:20:06+02:00 [SERVER] INFO: Adding route
2023-03-06T12:20:06+02:00 [SERVER] INFO: Adding socket handler
2023-03-06T12:20:06+02:00 [SERVER] INFO: Init the server
2023-03-06T12:20:07+02:00 [SERVER] INFO: Listening on 3001

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting
-----------------------------------------------------------
 Add-on: Uptime Kuma
 It is a self-hosted monitoring tool like "Uptime Robot"
-----------------------------------------------------------
 Add-on version: 0.6.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (amd64 / qemux86-64)
 Home Assistant Core: 2023.3.1
 Home Assistant Supervisor: 2023.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service uptime-kuma: starting
s6-rc: info: service uptime-kuma successfully started
s6-rc: info: service legacy-services: starting
[12:20:04] INFO: Starting Uptime Kuma...
s6-rc: info: service legacy-services successfully started
Welcome to Uptime Kuma
Your Node.js version: 18
2023-03-06T12:20:04+02:00 [SERVER] INFO: Welcome to Uptime Kuma
2023-03-06T12:20:04+02:00 [SERVER] INFO: Node Env: production
2023-03-06T12:20:04+02:00 [SERVER] INFO: Importing Node libraries
2023-03-06T12:20:04+02:00 [SERVER] INFO: Importing 3rd-party libraries
2023-03-06T12:20:06+02:00 [SERVER] INFO: Creating express and socket.io instance
2023-03-06T12:20:06+02:00 [SERVER] INFO: Server Type: HTTP
2023-03-06T12:20:06+02:00 [SERVER] INFO: Importing this project modules
2023-03-06T12:20:06+02:00 [NOTIFICATION] INFO: Prepare Notification Providers
2023-03-06T12:20:06+02:00 [SERVER] INFO: Version: 1.20.1
2023-03-06T12:20:06+02:00 [PLUGIN] WARN: Warning: In order to enable plugin feature, you need to use the default data directory: ./data/
2023-03-06T12:20:06+02:00 [DB] INFO: Data Dir: /data/
2023-03-06T12:20:06+02:00 [SERVER] INFO: Connecting to the Database
2023-03-06T12:20:06+02:00 [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-03-06T12:20:06+02:00 [DB] INFO: SQLite Version: 3.39.4
2023-03-06T12:20:06+02:00 [SERVER] INFO: Connected
2023-03-06T12:20:06+02:00 [DB] INFO: Your database version: 10
2023-03-06T12:20:06+02:00 [DB] INFO: Latest database version: 10
2023-03-06T12:20:06+02:00 [DB] INFO: Database patch not needed
2023-03-06T12:20:06+02:00 [DB] INFO: Database Patch 2.0 Process
2023-03-06T12:20:06+02:00 [SERVER] INFO: Load JWT secret from database.
2023-03-06T12:20:06+02:00 [PLUGIN] WARN: Skip scanning plugin directory
2023-03-06T12:20:06+02:00 [SERVER] INFO: Adding route
2023-03-06T12:20:06+02:00 [SERVER] INFO: Adding socket handler
2023-03-06T12:20:06+02:00 [SERVER] INFO: Init the server
2023-03-06T12:20:07+02:00 [SERVER] INFO: Listening on 3001

Sorry, thanks!


[Support Request]: S3 configuration is unclear in docs

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
Hello — I'm trying to configure Bookstack to use S3 for image uploads, per the documentation.
I cannot get it to work and I suspect I'm not providing the right values for bucket & region, but the format of the value Bookstack expects is unclear from the documentation.

Is bucket supposed to be the full https://<bucket-name>.s3.us-east-2.amazonaws.com? or just <bucket-name>?
Is region supposed to be a full us-east-2.amazonaws.com or just us-east-2?

Could someone provide insight into the expected format for those? An update to the docs with an example configuration would be helpful as well.
Exact BookStack Version
v21.08.3
Log Content
No response
PHP Version
No response
Hosting Environment
Ubuntu 20.04 (LTS) x64, installed via official installation script

Hi @chrisaalid,

Bucket is just <bucket-name>.
Region is just us-east-2.

I won't update the docs yet with an example, as I don't want to complicate them where this has not been previously reported as an issue, since I don't think there's any suggestion these values would be urls, but I'll keep this in mind in the event it becomes a common question.
Since the question has been answered I'll close this off but just shout if further clarification is needed.

Hi @chrisaalid,

Bucket is just <bucket-name>.
Region is just us-east-2.

I won't update the docs yet with an example, as I don't want to complicate them where this has not been previously reported as an issue, since I don't think there's any suggestion these values would be urls, but I'll keep this in mind in the event it becomes a common question.
Since the question has been answered I'll close this off but just shout if further clarification is needed.


Build cmus with opus

The expression for cmus currently says (and has been saying so for more than a year)
# can't make these work, something is broken
[...]
#, opusSupport ? true, opusfile ? null

Opus support would be really interesting so maybe whatever was broken in the past works now, or there is some way to fix it? At any rate, this should be looked into again.

Looks like this has been resolved.


node-red-contrib-ifttt crashed the whole Node-Red instance when internet is down

26 Feb 10:07:08 - [red] Uncaught Exception:
26 Feb 10:07:08 - TypeError: Cannot read property 'hasOwnProperty' of undefined
    at Request._callback (/home/pi/.node-red/node_modules/node-red-contrib-ifttt/nodes/ifttt.js:37:34)
    at self.callback (/home/pi/.node-red/node_modules/node-red-contrib-ifttt/node_modules/request/request.js:185:22)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at Request.onRequestError (/home/pi/.node-red/node_modules/node-red-contrib-ifttt/node_modules/request/request.js:881:8)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at TLSSocket.socketErrorListener (_http_client.js:387:9)
    at emitOne (events.js:116:13)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
26 Feb 10:07:25 - [info]
Welcome to Node-RED
===================
26 Feb 10:07:25 - [info] Node-RED version: v0.19.4
26 Feb 10:07:25 - [info] Node.js  version: v8.11.1
26 Feb 10:07:25 - [info] Linux 4.14.79+ arm LE

Solved by replacing the error message in ifttt.js, line 37 by a no-brainer string containing a generic error message

Oh, man - I misread this as node-red-contrib-ifttt crashes whole internet and got chills...
The fix is in and the new version 0.2.1 is up on github and published to NPM.
Thank you for detecting and reporting this.

Oh, man - I misread this as node-red-contrib-ifttt crashes whole internet and got chills...
The fix is in and the new version 0.2.1 is up on github and published to NPM.
Thank you for detecting and reporting this.


Fix for SQLAlchemy 1.4+ where is no _join_entities() attribute

Fixes: #60

I still need to take a look at Travis builds (newer Python, etc.).  So please don't merge.

Travis is dead for open source projects - it would be better to move to GitHub Actions but that would be another issue imho :-)

Actually, it still works to some extent ... @bkabrda can you give me admin access here?  Or at least reconfigure against travis-ci.com?

Turns out I can not be added as admin here, so let's go without CI now.


[Discuss] need to add the daemonstatus api for the new version of scrapyd

Hi all:
since the scrapyd server has add the new api of daemonstatus.json
here is the code
https://github.com/scrapy/scrapyd/blob/master/scrapyd/webservice.py
here is the doc
https://scrapyd.readthedocs.org/en/latest/api.html#daemonstatus-json
i think may be need to update the code and add this new api to the project

daemonstatus.json is not in a scrapyd release yet
but I don't see why it shouldn't make it to the next.

Yup, as @Digenis noted in #5, this is not in a stable branch yet.
It has also changed within the last month so I'm not certain we should be relying on it being a stable API just yet.

but I don't see why it shouldn't make it to the next.

@Digenis do you have any more information on this? I can't find much info set in stone about scrapyd's release process.

The change was only a bugfix.
I don't think we should drop daemonstatus from scrapyd
There are other recently introduced features that should be dropped.
The reason you can't rely on it is because it's not tagged in a release yet.
Regarding releases, there are currently no conventions.
The odd-even convention for unstable-stable releases
is finally abandoned by scrapy.
I'm currently doing an effort to fix the setups of existing releases of scrapyd
which have erroneously remained with obsolete scrapy dependencies
and python2.6 support for too long. I think the setup scripts are important
because of the amount of people who accidentally end up with broken installations.
I'm done with the 1.0 branch, I'll do the same on 1.1
and then some cleanup and testing towards a 1.2 release.
Any help on this is welcome.

Thanks @Digenis.
I will likely start work on supporting daemonstatus in a branch our side so that we are ready to release as soon as scrapyd is at the point where it can be.
I'll leave this ticket open to track progress.

daemonstatus.json is now stable. Please add it.


feat(ci): add automated image builds

Description
Please explain the changes you made here.
Which issue(s) does this PR fix

Fixes https://github.com/janus-idp/backstage-showcase/issues/545

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

@nickboldt PTAL?

https://github.com/janus-idp/backstage-showcase/pull/590/files#r1357024623


omit --configsvr during initdb

Currently, initdb omits both --auth and --replSet when adding the initial user for authentication.
When running a config server, initdb uses --configsvr for the standalone mongod server. I'm wondering if this option can be omitted just like --auth and --replSet. For the default dbpath, we would always provide a --dbpath $dbPath during initdb, similar to how initdb always overrides the port.
This request is motivated by the work done in: https://jira.mongodb.org/browse/SERVER-51733

So is this not correct way to get the /data/configdb properly seeded? Why would this setup cause mongod to crash after the rs.initiate?

run mongod --configsvr
create an "admin" user
stop mongod
run mongod --configsvr --auth --replSet 'myreplica'
run rs.initiate() via mongo

There is a bug in 4.4 that would cause mongod to crash in this situation. The fix is already in the latest development version but not in 4.4 yet. The suggestion to the initdb steps here will avoid the crash for existing versions of 4.4 and will also work for earlier versions of mongod.

This is no longer an issue now that the bug is fixed in 4.4.3. See SERVER-51733


[Bug] gpinitsystem failed with missing library.

Cloudberry Database version
cloudberry-db-1.4.0-1.el7.aarch64.rpm
What happened
I've installed CBDB bianry with
yum install -y /tmp/cloudberry-db-1.4.0-1.el7.aarch64.rpm
When try to run gpinitsystem I met following error:
2023-09-07 17:37:37.339676 CST,,,p4957,th-1550045184,,,,746,,cmd979,seg-10000,,,x746,sx1,"FATAL","XX000","could not load library ""/usr/local/cloudberry-db-1.4.0/lib/postgresql/quicklz_compressor.so"": libquicklz.so: cannot open shared object file: No such file or directory",,,,,,"
-- EOF
RESET ALL;
CREATE FUNCTION gp_quicklz_constructor(internal, internal, bool) RETURNS internal
LANGUAGE C VOLATILE AS '$libdir/quicklz_compressor.so', 'quicklz_constructor';
COMMENT ON FUNCTION gp_quicklz_constructor(internal, internal, bool) is 'quicklz constructor';
",,"internal_load_library","dfmgr.c",246,1    0xcb54ec postgres errstart (elog.c:579)
2    0xcbc0f0 postgres  (dfmgr.c:246)
3    0xcbc618 postgres load_external_function (dfmgr.c:122)
4    0x7fb8b4 postgres fmgr_c_validator (discriminator 5)
5    0xcbe31c postgres OidFunctionCall1Coll (fmgr.c:1143)
6    0x7fb0fc postgres ProcedureCreate (pg_proc.c:783)
7    0x899674 postgres CreateFunction (discriminator 8)
8    0xb3c9a0 postgres  (utility.c:2038)
9    0xb3b400 postgres standard_ProcessUtility (utility.c:1270)
10   0xb388f4 postgres  (palloc.h:172)
11   0xb38e10 postgres  (pquery.c:1515)
12   0xb3a284 postgres PortalRun (pquery.c:970)
13   0xb34e8c postgres  (postgres.c:1940)
14   0xb377e4 postgres PostgresMain (postgres.c:5573)
15   0x6c23a0 postgres main (main.c:205)
16   0xffffa4142724 libc.so.6 __libc_start_main + 0xf0
17   0x6d1724 postgres  + 0x6d1724
Seems libquicklz.so is not installed, I don't need to use qucklz as compression method, how to bypass this issue?
What you think should happen instead
No response
How to reproduce
yum install -y /tmp/cloudberry-db-1.4.0-1.el7.aarch64.rpm
gpinitsystem
Operating System
[root@mdw tmp]# cat /etc/os-release NAME="CentOS Linux" VERSION="7 (AltArch)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (AltArch)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7:server" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/"  CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7"
Anything else
No response
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

I've compared x86 version and arm version, the library exists in x86 binary however NOT found in arm version.
X86 binary (cloudberry-db-1.4.0-1.el7.centos.x86_64.rpm)
[root@i-jj075kh1 lib]# ls -l /usr/local/cloudberry-db/lib/libquicklz*
lrwxrwxrwx 1 root root    19 Sep  8 09:53 /usr/local/cloudberry-db/lib/libquicklz.so -> libquicklz.so.1.5.0
lrwxrwxrwx 1 root root    19 Sep  8 09:53 /usr/local/cloudberry-db/lib/libquicklz.so.1 -> libquicklz.so.1.5.0
-rwxr-xr-x 1 root root 19256 Aug  3 10:21 /usr/local/cloudberry-db/lib/libquicklz.so.1.5.0
Arm binary (cloudberry-db-1.4.0-1.el7.aarch64.rpm)
[root@mdw /]# ls -l /usr/local/cloudberry-db/lib/libquicklz*
ls: cannot access /usr/local/cloudberry-db/lib/libquicklz*: No such file or directory

Already fixed in next release


histogram for entity ages

@solson

Boilerplate: I'm going to refocus this project on rfcbot, since that's the primary usage rusty-dash.com is seeing.


relax restriction on ActiveSupport, add CHANGELOG

Version has already been bumped, v0.13.0 hasn't been pushed to rubygems yet.

@kgilpin this was the change we talked about. Looks like you've made changes here since the last push to rubygems. I wanted to check and make sure it's ok to release those, too.


Firefox settings iframe broken

As described, I believe it has something to do with permissions. I'm struggling to figure out what's causing this, there are no traces for me in the network tab. The url of the iframe is correct and loads when opened in a new tab but firefox just refuses to load it when on SEQTA.

ummm. actually for some reason it works once submitted to the addons store. But I'm not sure why it isn't working in dev. Still pretty important to fix!

ummm. actually for some reason it works once submitted to the addons store. But I'm not sure why it isn't working in dev. Still pretty important to fix!

I have the same issues with other extensions when I run as dev. I think it may be a firefox thing

I'll close this for now because it is sorta working. But I've got some ideas for fixing it down the track a bit.

Probably put this as not planned instead of closing it as completed.


Move baca service implementation out of root module

Codecov Report

Merging #9 (52a4bb2) into master (36106a2) will increase coverage by 1.12%.
The diff coverage is 93.68%.

@@            Coverage Diff             @@
##           master       #9      +/-   ##
==========================================
+ Coverage   88.63%   89.75%   +1.12%
==========================================
  Files          33       32       -1
  Lines        1425     1425
==========================================
+ Hits         1263     1279      +16
+ Misses        162      146      -16

Impacted Files
Coverage Δ

src/baca/api/baca_service.rs
89.55% <91.66%> (+6.41%)
:arrow_up:

src/baca/api/request.rs
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


changed naming scheme for attributes

the idea of changing this naming scheme was to make it easier when passing commands in by:

removing spaces
removing special characters
standardized arguments to be lowercase

I made a Python GUI appthat uses the majority of this code with some changes to naming scheme. I'm working on additional functionality but if any of my code helps, please take it!


option to use only on Wifi

Please add an option to only "Use on Wifi". Various apps support such an option, like F-Droid or Linphone, and having such an option on RK would come in handy to avoid RK being available on 3G networks...

As mentioned you can use a Firewall solution and/or an SSH Server on Android to use RK more securly :smile:
But it would probably make sense to only bind on addresses for wifi …
Currently it binds to all addresses
tcp6       0      0 :::2323                :::*                   LISTEN


Bring back form-control-sm

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the contributing guidelines

Proposal
According to Cyriaque : "In some exceptional cases we provide components with a lower dont 14 px font size such a Small button or Small quantity selector" :
Therefore we need to put back small inputs (i.e. form controls with CSS class .form-control-sm) into Boosted.
Motivation and context
It will be helpfull to simply use CSS class '.form-control-sm intead of doing weird things like what we have done for the quantity selector (i.e. '$input-padding-y-sm: divide($input-padding-y, 2) !default; // Boosted mod').

Since the .form-control-sm is back in Boosted, should we try to take a look at this one again ?

Closing it since .form-control-sm is back to Boosted via https://github.com/Orange-OpenSource/Orange-Boosted-Bootstrap/pull/1230.
Create a new one to see if using .form-control-sm in our Boosted specific small form controls can be useful.


Update team-settings.rst

Formatting and minor grammar changes.

@thefactremains, this update was for https://mattermost.atlassian.net/browse/MM-22064 but it looks like the content already includes what we discussed. PLMK whether this is the case or it should be updated/revised.


bigint: Fix calculation of size for multiply temporaries

When x.len() and y.len() are both equal and odd, we have x1.len() + y1.len() + 1
(the required size to multiply x1 and y1) > y.len() + 1
This fixes #187

Great! Can you add the test that failed #187?

Done

Thanks a lot!
@homu r+ 1e65e9d

:zap: Test exempted - status


GPL versus MIT license

Do you have a particular intention in mind by licensing your NPM module under GPLv3? The legal implications of GPL on a JavaScript library have never been tested in a court of law, but I would still be hesitant to depend on your module just in case there was a chance it would trigger a viral license on any proprietary code I had running through the build system. You may want to consider the more community standard MIT license, which is more permissive.

Point taken, let me fix that.

Thanks for pointing it out, MIT it is.


ambient: remove redundant "!exludePod"

Please provide a description of this PR:
See https://github.com/istio/istio/pull/41426#discussion_r995867982
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[x] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @imroc. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@howardjohn @dhawton

/ok-to-test

@imroc: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@imroc: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test unit-tests-arm64

unit-tests_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@imroc: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test unit-tests-arm64

unit-tests_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test unit-tests

lint_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@imroc: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test unit-tests-arm64

unit-tests_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test unit-tests

lint_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test lint

gencheck_istio_exp
61b60e14706ff69f20eb87e70539dcf759b6292a
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I see, the


Layout issue with EntityGrid.getQuickSearchFields()

If you activate the feature where the user can select a column for quicksearch by implementing EntityGrid.getQuickSearchFields(), the resulting layout is not looking nice. Some css seems to be missing.

Should be fixed with 81ca0f8f859337319261410ca6bf59cd173f85d1