typeahead: Apply some better behavior from mobile; test emoji typeahead more

The two non-test, non-NFC commits here are:

typeahead: Don't stop midphrase matching when a second word is typed.
For example, if a user's name is "Simon Peyton Jones", we'll already
match that name on the queries "Pey" or "Peyton", as well as on
"Simon P".  We should do so on "Peyton J" or "Peyton Jones", too.
Similarly, if the user is looking for an emoji of a face in the moon
and they start by typing ":moon", we'll show them both 🌝 "moon face"
and 🌚 "new moon face", along with some other moon-related results.
If they go on to make it ":moon " or ":moon f", though -- as one very
naturally would in order to eliminate things like "waxing moon" and
"moon ceremony" -- then we mysteriously eliminate 🌚 "new moon face".
Instead, the query "moon f" should match both 🌚 and 🌝.
Found this while comparing the web/shared implementation with the
mobile implementation of emoji search.  The new behavior here
reflects what we already do for emoji search in mobile, both in the
compose box's typeahead and in the add-a-reaction screen.  The
existing behavior here seems pretty annoying, so fixing it will be
part of switching on mobile to the shared code (zulip/zulip-mobile#4636)
without regressing the user experience.

typeahead: Normalize spaces for sorting emojis, just like for filtering.
And add a pair of tests.  The first one (with an underscore) passed
already; the second (with a space) passes only with this change.

We also add more tests for existing behavior.
This doesn't cover matching an emoji literally, as in #21714. It looks like #21778 will cover that, and in the meantime mobile can continue to do that part for itself -- it's only an extra line or two of code.
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Thanks for the review! Revised and rebased.

Merged, thanks @gnprice!


needs a little extra explanation on retention

If items in the mailbox are held by a retention policy, such as a record label, or mailbox retention policy from compliance center policies - retention - when the license is removed is that data still retained? Or does the account need to be "deleted" instead of unlicensing it as a way to make sure that data is retained for the length of the retention period or record label policy?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0d850211-99b4-faf7-09fc-4621919dd74b
Version Independent ID: 9b294f13-b1e3-291e-25a1-75f7c5755b6c
Content: Unassign licenses from users - Microsoft 365 admin
Content Source: microsoft-365/admin/manage/remove-licenses-from-users.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@msbemba

@msbemba Thank you very much for the contribution and updating the documentation with PR. @joshfolcik Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Updated to selenium standalone 3.12.0 and fix start up parameters order.

Hello team, I implemented a quick fix to be able to start selenium standalone server 3. This version of selenium requires that the java parameters are swapped so the jar file goes at the end. I have also updated the chrome driver to version 2.38 which is the maximum version that works with this setup.
I hope it helps.

Thank you! The CI tests seem to be failing the same way they have been. Any idea why this may be?

Hello Brian,
How can I see the CI test results? I was not aware of them. I just tested
it all locally.
On Fri, 22 Jun 2018 at 15:51, Brian Scaturro<EMAIL_ADDRESS>wrote:

Thank you! The CI tests seem to be failing the same way they have been.
Any idea why this may be?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/peridot-php/webdriver-manager/pull/18#issuecomment-399449374,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKOw2KULlAGl9TWdixeT3CUiaA9zfpBks5t_PZRgaJpZM4Uw3pI
.

--
Marc Andreu Fernàndez.

@marcandreuf no worries - here is the link for the PR's build.

Hello Brian,
I fix all Unit and Integration test for Php7.0. I see that the CI build
still fails for PHP 5.6 and 5.5. I am not sure how to solve those errors.
Sorry, it has been a long time not working in PHP. Could you let me know
how to fix the remaining errors?
Many thanks
Marc,
On Fri, 22 Jun 2018 at 17:03, Brian Scaturro<EMAIL_ADDRESS>wrote:

@marcandreuf https://github.com/marcandreuf no worries - here is the
link
https://travis-ci.org/peridot-php/webdriver-manager/builds/394808354?utm_source=github_status&utm_medium=notification
for the PR's build.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/peridot-php/webdriver-manager/pull/18#issuecomment-399473318,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKOw5wycmkX1l6vIHfRWHR4R-UjSo7oks5t_QdNgaJpZM4Uw3pI
.

--
Marc Andreu Fernàndez.

@marcandreuf thanks! The remaining errors don't look PHP related. It seems like the selenium process is not generating logs. I think that failing test does not really provide a ton of value, as I believe it is mostly leveraged outside of the CLI.
Could you include a change to .travis.yml with our changes? Would you mind removing the hhvm entries (hhvm, and hhvm-nightly) from the build matrix here
We probably no longer need the fast finish either. This chunk here could be deleted as well:
matrix:
  fast_finish: true
  allow_failures:
    - php: hhvm-nightly
    - php: 7

If the app is working as you intended, you can delete the tests that are failing. If things are passing in more recent PHP versions, then I would be content to just remove those tests if you are ok with that

Hello Brian,
Looks like the CI is happy finally :-)
Best regards,
Marc


Some jwt error after make start the newest dataset-server

My system is Windows10 and use the newest version of Docker Desktop, which the wsl engine was go on to execute docker together with WSL2. My WSL2 system is Ubuntu-22.04, and I cloned the newest version of datasets-server in it. Then I ran make start to build the server and successfully execute and can be shown in Docker Desktop dashboard.
When i saw the log about them,  I found the worker docker: api, rows and search docker occred the same error as follows, which make the proxy docker receive 502 when i requests them:
2023-10-27 15:11:50 INFO:     Stopping parent process [1]
2023-10-27 15:11:52 INFO:     Uvicorn running on http://<IP_ADDRESS>:8180 (Press CTRL+C to quit)
2023-10-27 15:11:52 INFO:     Started parent process [1]
2023-10-27 15:11:53 Process SpawnProcess-2:
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_exceptions.py", line 10, in map_exceptions
2023-10-27 15:11:53     yield
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_backends/sync.py", line 174, in start_tls
2023-10-27 15:11:53     raise exc
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_backends/sync.py", line 169, in start_tls
2023-10-27 15:11:53     sock = ssl_context.wrap_socket(
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/ssl.py", line 501, in wrap_socket
2023-10-27 15:11:53     return self.sslsocket_class._create(
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/ssl.py", line 1041, in _create
2023-10-27 15:11:53     self.do_handshake()
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/ssl.py", line 1310, in do_handshake
2023-10-27 15:11:53     self._sslobj.do_handshake()
2023-10-27 15:11:53 socket.timeout: _ssl.c:1112: The handshake operation timed out
2023-10-27 15:11:53
2023-10-27 15:11:53 The above exception was the direct cause of the following exception:
2023-10-27 15:11:53
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_transports/default.py", line 66, in map_httpcore_exceptions
2023-10-27 15:11:53     yield
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_transports/default.py", line 228, in handle_request
2023-10-27 15:11:53     resp = self._pool.handle_request(req)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection_pool.py", line 262, in handle_request
2023-10-27 15:11:53     raise exc
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection_pool.py", line 245, in handle_request
2023-10-27 15:11:53     response = connection.handle_request(request)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection.py", line 99, in handle_request
2023-10-27 15:11:53     raise exc
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection.py", line 76, in handle_request
2023-10-27 15:11:53     stream = self._connect(request)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection.py", line 156, in _connect
2023-10-27 15:11:53     stream = stream.start_tls(**kwargs)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_backends/sync.py", line 174, in start_tls
2023-10-27 15:11:53     raise exc
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/contextlib.py", line 137, in __exit__
2023-10-27 15:11:53     self.gen.throw(typ, value, traceback)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
2023-10-27 15:11:53     raise to_exc(exc) from exc
2023-10-27 15:11:53 httpcore.ConnectTimeout: _ssl.c:1112: The handshake operation timed out
2023-10-27 15:11:53
2023-10-27 15:11:53 The above exception was the direct cause of the following exception:
2023-10-27 15:11:53
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/src/libs/libapi/src/libapi/jwt_token.py", line 177, in fetch_jwt_public_key_json
2023-10-27 15:11:53     response = httpx.get(url, timeout=hf_timeout_seconds)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_api.py", line 189, in get
2023-10-27 15:11:53     return request(
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_api.py", line 100, in request
2023-10-27 15:11:53     return client.request(
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 814, in request
2023-10-27 15:11:53     return self.send(request, auth=auth, follow_redirects=follow_redirects)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 901, in send
2023-10-27 15:11:53     response = self._send_handling_auth(
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 929, in _send_handling_auth
2023-10-27 15:11:53     response = self._send_handling_redirects(
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 966, in _send_handling_redirects
2023-10-27 15:11:53     response = self._send_single_request(request)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 1002, in _send_single_request
2023-10-27 15:11:53     response = transport.handle_request(request)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_transports/default.py", line 228, in handle_request
2023-10-27 15:11:53     resp = self._pool.handle_request(req)
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/contextlib.py", line 137, in __exit__
2023-10-27 15:11:53     self.gen.throw(typ, value, traceback)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_transports/default.py", line 83, in map_httpcore_exceptions
2023-10-27 15:11:53     raise mapped_exc(message) from exc
2023-10-27 15:11:53 httpx.ConnectTimeout: _ssl.c:1112: The handshake operation timed out
2023-10-27 15:11:53
2023-10-27 15:11:53 The above exception was the direct cause of the following exception:
2023-10-27 15:11:53
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/src/libs/libapi/src/libapi/jwt_token.py", line 220, in get_jwt_public_keys
2023-10-27 15:11:53     payload = fetch_jwt_public_key_json(
2023-10-27 15:11:53   File "/src/libs/libapi/src/libapi/jwt_token.py", line 181, in fetch_jwt_public_key_json
2023-10-27 15:11:53     raise RuntimeError(f"Failed to fetch the JWT public key from {url}. ") from err
2023-10-27 15:11:53 RuntimeError: Failed to fetch the JWT public key from https://huggingface.co/api/keys/jwt.
2023-10-27 15:11:53
2023-10-27 15:11:53 The above exception was the direct cause of the following exception:
2023-10-27 15:11:53
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
2023-10-27 15:11:53     self.run()
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/multiprocessing/process.py", line 108, in run
2023-10-27 15:11:53     self._target(*self._args, **self._kwargs)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/uvicorn/_subprocess.py", line 76, in subprocess_started
2023-10-27 15:11:53     target(sockets=sockets)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/uvicorn/server.py", line 60, in run
2023-10-27 15:11:53     return asyncio.run(self.serve(sockets=sockets))
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
2023-10-27 15:11:53     return loop.run_until_complete(main)
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
2023-10-27 15:11:53     return future.result()
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/uvicorn/server.py", line 67, in serve
2023-10-27 15:11:53     config.load()
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/uvicorn/config.py", line 483, in load
2023-10-27 15:11:53     self.loaded_app = self.loaded_app()
2023-10-27 15:11:53   File "/src/services/api/src/api/app.py", line 28, in create_app
2023-10-27 15:11:53     return create_app_with_config(app_config=app_config, endpoint_config=endpoint_config)
2023-10-27 15:11:53   File "/src/services/api/src/api/app.py", line 37, in create_app_with_config
2023-10-27 15:11:53     hf_jwt_public_keys = get_jwt_public_keys(
2023-10-27 15:11:53   File "/src/libs/libapi/src/libapi/jwt_token.py", line 232, in get_jwt_public_keys
2023-10-27 15:11:53     raise JWTKeysError("Failed to create the JWT public keys.") from err
2023-10-27 15:11:53 libapi.exceptions.JWTKeysError: Failed to create the JWT public keys.
2023-10-27 15:11:53 Process SpawnProcess-1:
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_exceptions.py", line 10, in map_exceptions
2023-10-27 15:11:53     yield
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_backends/sync.py", line 174, in start_tls
2023-10-27 15:11:53     raise exc
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_backends/sync.py", line 169, in start_tls
2023-10-27 15:11:53     sock = ssl_context.wrap_socket(
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/ssl.py", line 501, in wrap_socket
2023-10-27 15:11:53     return self.sslsocket_class._create(
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/ssl.py", line 1041, in _create
2023-10-27 15:11:53     self.do_handshake()
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/ssl.py", line 1310, in do_handshake
2023-10-27 15:11:53     self._sslobj.do_handshake()
2023-10-27 15:11:53 socket.timeout: _ssl.c:1112: The handshake operation timed out
2023-10-27 15:11:53
2023-10-27 15:11:53 The above exception was the direct cause of the following exception:
2023-10-27 15:11:53
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_transports/default.py", line 66, in map_httpcore_exceptions
2023-10-27 15:11:53     yield
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_transports/default.py", line 228, in handle_request
2023-10-27 15:11:53     resp = self._pool.handle_request(req)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection_pool.py", line 262, in handle_request
2023-10-27 15:11:53     raise exc
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection_pool.py", line 245, in handle_request
2023-10-27 15:11:53     response = connection.handle_request(request)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection.py", line 99, in handle_request
2023-10-27 15:11:53     raise exc
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection.py", line 76, in handle_request
2023-10-27 15:11:53     stream = self._connect(request)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_sync/connection.py", line 156, in _connect
2023-10-27 15:11:53     stream = stream.start_tls(**kwargs)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_backends/sync.py", line 174, in start_tls
2023-10-27 15:11:53     raise exc
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/contextlib.py", line 137, in __exit__
2023-10-27 15:11:53     self.gen.throw(typ, value, traceback)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
2023-10-27 15:11:53     raise to_exc(exc) from exc
2023-10-27 15:11:53 httpcore.ConnectTimeout: _ssl.c:1112: The handshake operation timed out
2023-10-27 15:11:53
2023-10-27 15:11:53 The above exception was the direct cause of the following exception:
2023-10-27 15:11:53
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/src/libs/libapi/src/libapi/jwt_token.py", line 177, in fetch_jwt_public_key_json
2023-10-27 15:11:53     response = httpx.get(url, timeout=hf_timeout_seconds)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_api.py", line 189, in get
2023-10-27 15:11:53     return request(
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_api.py", line 100, in request
2023-10-27 15:11:53     return client.request(
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 814, in request
2023-10-27 15:11:53     return self.send(request, auth=auth, follow_redirects=follow_redirects)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 901, in send
2023-10-27 15:11:53     response = self._send_handling_auth(
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 929, in _send_handling_auth
2023-10-27 15:11:53     response = self._send_handling_redirects(
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 966, in _send_handling_redirects
2023-10-27 15:11:53     response = self._send_single_request(request)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_client.py", line 1002, in _send_single_request
2023-10-27 15:11:53     response = transport.handle_request(request)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_transports/default.py", line 228, in handle_request
2023-10-27 15:11:53     resp = self._pool.handle_request(req)
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/contextlib.py", line 137, in __exit__
2023-10-27 15:11:53     self.gen.throw(typ, value, traceback)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/httpx/_transports/default.py", line 83, in map_httpcore_exceptions
2023-10-27 15:11:53     raise mapped_exc(message) from exc
2023-10-27 15:11:53 httpx.ConnectTimeout: _ssl.c:1112: The handshake operation timed out
2023-10-27 15:11:53
2023-10-27 15:11:53 The above exception was the direct cause of the following exception:
2023-10-27 15:11:53
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/src/libs/libapi/src/libapi/jwt_token.py", line 220, in get_jwt_public_keys
2023-10-27 15:11:53     payload = fetch_jwt_public_key_json(
2023-10-27 15:11:53   File "/src/libs/libapi/src/libapi/jwt_token.py", line 181, in fetch_jwt_public_key_json
2023-10-27 15:11:53     raise RuntimeError(f"Failed to fetch the JWT public key from {url}. ") from err
2023-10-27 15:11:53 RuntimeError: Failed to fetch the JWT public key from https://huggingface.co/api/keys/jwt.
2023-10-27 15:11:53
2023-10-27 15:11:53 The above exception was the direct cause of the following exception:
2023-10-27 15:11:53
2023-10-27 15:11:53 Traceback (most recent call last):
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
2023-10-27 15:11:53     self.run()
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/multiprocessing/process.py", line 108, in run
2023-10-27 15:11:53     self._target(*self._args, **self._kwargs)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/uvicorn/_subprocess.py", line 76, in subprocess_started
2023-10-27 15:11:53     target(sockets=sockets)
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/uvicorn/server.py", line 60, in run
2023-10-27 15:11:53     return asyncio.run(self.serve(sockets=sockets))
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
2023-10-27 15:11:53     return loop.run_until_complete(main)
2023-10-27 15:11:53   File "/usr/local/lib/python3.9/asyncio/base_events.py", line 647, in run_until_complete
2023-10-27 15:11:53     return future.result()
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/uvicorn/server.py", line 67, in serve
2023-10-27 15:11:53     config.load()
2023-10-27 15:11:53   File "/src/services/api/.venv/lib/python3.9/site-packages/uvicorn/config.py", line 483, in load
2023-10-27 15:11:53     self.loaded_app = self.loaded_app()
2023-10-27 15:11:53   File "/src/services/api/src/api/app.py", line 28, in create_app
2023-10-27 15:11:53     return create_app_with_config(app_config=app_config, endpoint_config=endpoint_config)
2023-10-27 15:11:53   File "/src/services/api/src/api/app.py", line 37, in create_app_with_config
2023-10-27 15:11:53     hf_jwt_public_keys = get_jwt_public_keys(
2023-10-27 15:11:53   File "/src/libs/libapi/src/libapi/jwt_token.py", line 232, in get_jwt_public_keys
2023-10-27 15:11:53     raise JWTKeysError("Failed to create the JWT public keys.") from err
2023-10-27 15:11:53 libapi.exceptions.JWTKeysError: Failed to create the JWT public keys.

At first I thought the main error is network and i use ping huggingface.co and curl https://huggingface.co/api/keys/jwt in these dockers, but I had 200 request later, which means the network in dockers are not the main reason cause the prolems.
Can anyone give a solutions or mothod to solve this bug, thanks !

Good catch.
It should be fixed with https://github.com/huggingface/datasets-server/pull/2022


gpscorrelate: 2.0 → 2.1

Description of changes

changelog: https://github.com/dfandrich/gpscorrelate/releases/tag/2.1
2.0 build is broken: https://hydra.nixos.org/build/254924700

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 301632 run on aarch64-darwin 1

1 package built:

gpscorrelate


US 01.08.01

As an organizer, I want to see on a map where users are checking in from.
Acceptance criteria

UI is implemented as per storyboard
Collect attendee location data and store to Firebase

Unknown

The clarity at which user location data is displayed (exact location? what if many users are in a close proximity to each other?)
What API will be used to implement a scrollable map in-app

This still needs to be tested on whether it works with Firebase properly.


True OpenAI drop-in replacement by InferenceClient

Closes https://github.com/huggingface/huggingface_hub/issues/2369 @lappemic
Goal is to be able to use InferenceClient exactly the same way as OpenAI client. To do so we need to:

[x] rename model to base_url => added an alias for it
[x] rename model_id to model
[x] rename token to api_key => added an alias for it
[x] add alias for client.chat.completions.create

@philschmid could you have a look at it and confirm it meets your expectations? See tests for real example (here and here)
Sync + stream=False
client = InferenceClient(
    base_url="https://api-inference.huggingface.co/models/meta-llama/Meta-Llama-3-8B-Instruct",
    api_key="my-api-key",
)
output = client.chat.completions.create(
    model="meta-llama/Meta-Llama-3-8B-Instruct",
    messages=[
        {"role": "system", "content": "You are a helpful assistant."},
        {"role": "user", "content": "Count to 10"},
    ],
    stream=False,
    max_tokens=1024,
)
assert output.choices[0].message.content == "1, 2, 3, 4, 5, 6, 7, 8, 9, 10!"

Sync + stream=True
client = InferenceClient()
output = client.chat.completions.create(
    model="meta-llama/Meta-Llama-3-8B-Instruct",
    messages=[
        {"role": "system", "content": "You are a helpful assistant."},
        {"role": "user", "content": "Count to 10"},
    ],
    stream=True,
    max_tokens=1024,
)

for chunk in output:
    print(chunk.choices[0].delta.content)

Async + stream=False
    client = AsyncInferenceClient(
        base_url="https://api-inference.huggingface.co/models/meta-llama/Meta-Llama-3-8B-Instruct",
        api_key="my-api-key",
    )
    output = await client.chat.completions.create(
        model="meta-llama/Meta-Llama-3-8B-Instruct",
        messages=[
            {"role": "system", "content": "You are a helpful assistant."},
            {"role": "user", "content": "Count to 10"},
        ],
        stream=False,
        max_tokens=1024,
    )
    assert output.choices[0].message.content == "1, 2, 3, 4, 5, 6, 7, 8, 9, 10!"

Async + stream=True
client = AsyncInferenceClient()
output = await client.chat.completions.create(
    model="meta-llama/Meta-Llama-3-8B-Instruct",
    messages=[
        {"role": "system", "content": "You are a helpful assistant."},
        {"role": "user", "content": "Count to 10"},
    ],
    stream=True,
    max_tokens=1024,
)

chunked_text = [chunk.choices[0].delta.content async for chunk in output]

TODO:

[x] document this properly (see inference.md)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@philschmid could you have a look at it and confirm it meets your expectations?

from experience, a very tough test to pass usually 🤣

Thanks for the reviews!


[bug|Feature]: Check for Reasonable CFee when Channel is not opened by us

Background
There are nodes on the network which do not support Anchor Channels but they enforce really low fees on the Commitment transaction. In this mempool conditions its really dangerous because first you risk losing funds when the outgoing HTLC is not confirmed by time and secondly you will also risk losing 2 channels because the channel with the corresponding incoming HTLC will FC too. I recommend adding rigorous checks for the fees of the Commitment Transaction especially for non-anchor channels, or at least give the user a config setting to decide whether he wanna enforce stricter rules for non-initiated channel-fee updates.
The node doing this for now is Bcash_Is_Trash but without a reasonable fee-check this could attract some bad behaviour.
Some examples:
https://mempool.space/tx/0d95150553b81da7ad2e03f5c2d2668c34513d9990a28f46a2278ca258d66e8c
https://mempool.space/tx/de2364ce92b22163e3dddb0af66df50b5a43b6055150c9f0de60fa2bb3345893

Do you want to be able to only accept anchor channels? That can be done with a channel acceptor. We want to make it be the default and only channel type, but not all other implementations support the final version of it.

recommend adding rigorous checks for the fees of the Commitment Transaction especially for non-anchor channels,

If we can and find fees that are very low, controlled by the initiator, what do you propose we do? Force close is the only thing one can do, but then if the fees are already too low, you'd enter a limbo state for the channel. I guess this is better than having HTLCs, and not being able to actually resolve them on chain.

I agree, using the channel-acceptor is the best way to prevent this kind of behaviour. Checking the fees and not allowing any HTLC on the commitment transaction would lead to many more force-closes I guess and too strict behaviour.
Thinking it through again it's definitely something which should be handled on upper layers not in lnd. Thanks for your thoughts

How to bump fee for these transactions? I have one now...
Maybe, Transaction Accelerator is helpful. but It costs 75 USD for a single transaction now

Apologies for necromancing a closed issue, but with the mempool going back down to near 1sat/vB last week, the Bcash_Is_Trash node is really wreaking havoc with force closes. My node had a non-anchor channel with this node which was opened by them, that had to force close with the following error log entries:
2023-10-03 12:50:42.916 [ERR] HSWC: ChannelLink(2f1fba221a8daf6217e86d00e74943bc127f61e60ff8616ccec140a502320871:8): failing link: ChannelPoint(2f1fba221a8daf6217e86d00e74943bc127f61e60ff8616ccec140a502320871:8): unable to accept new commitment: commitment fee per kw 250 sat/kw below fee floor 253 sat/kw with error: invalid commitment
2023-10-03 12:50:42.916 [ERR] HSWC: ChannelLink(2f1fba221a8daf6217e86d00e74943bc127f61e60ff8616ccec140a502320871:8): link failed, exiting htlcManager
2023-10-03 12:50:42.916 [INF] HSWC: ChannelLink(2f1fba221a8daf6217e86d00e74943bc127f61e60ff8616ccec140a502320871:8): exited
2023-10-03 12:50:42.916 [INF] HSWC: ChannelLink(2f1fba221a8daf6217e86d00e74943bc127f61e60ff8616ccec140a502320871:8): stopping
2023-10-03 12:50:42.917 [WRN] PEER: Peer(0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f): Force closing link(723985:1100:8)

and the transaction is now stuck without me being able to do anything about it except hope and wait the mempool clears.
https://mempool.space/tx/db1ecbd132b815505db3a6cee4beebc7c9e00cf6a36e6d44797099c969e667c3
Tried to find contact details for the Bcash_Is_Trash node operator to ask them to CPFP the transaction but it is proving to be futile. Some other people are resorting to sending messages on amboss.space to beg and plead for a CPFP:

Here are some other examples of this tragedy taking place:
https://mempool.space/tx/be065bb22552ca53f26841733ea844da70fba72dd08506245cbb234e34e59c84#vin=0
https://mempool.space/tx/cadc7bbdf7499f86bd12f867107c9ee8efcff4d3dcfd7cd1d3ce36e3b1258685#vin=0
https://mempool.space/tx/7d027ca0bdd411b613ce68b567dc1d62689bd5e5e86cc0787093da73d36e881e#vin=0
https://mempool.space/tx/f58bc779bd8a74dd33f6ca2e80da1d62865f0ccd2af6c4094737ac7b85e3ad3e#vin=0
https://mempool.space/tx/7bb78ab6d9b9e4606b20b5c5b49c1bce3d8daec621ff767c6bec754913a94630#vin=0
https://mempool.space/tx/f9c55670f53f471f5dd759baf4679bb954a48617915b1172850e531db7ca52ed#vin=0
https://mempool.space/tx/1f0cb7d5da42bb2d76f13a2578c1ec2f71fb57a979c57ab14993b8a36345207d#vin=0
https://mempool.space/tx/6eb0b9127af4af4cf533238fad6f49559ef91f7e2bc29707aa91cb8688ed98e7#vin=0
https://mempool.space/tx/ae109dd3eccb1b7611e0f46c73e4f697153adc156a48bc3e5714e23c884f2df0#vin=0
https://mempool.space/tx/22a5c21790379a4a10b88b7551b3adb1774e93a6b231049139c6c1efe1670a70#vin=0
https://mempool.space/tx/6368fea16448e7fb5284e8ce0453ba044145eb4e07d7b52d601cb1b3e1590f43#vin=0
and those are just from the first few pages of the Bcash_Is_Trash channel list on Amboss.
I really hope we have an easier way to force anchor channels. Using channel acceptor seems to be too daunting for non-techies like myself.


⚠ Games API Endpoint has degraded performance

In 93aea03, Games API Endpoint (https://games.roblox.com) experienced degraded performance:

HTTP code: 200
Response time: 4202 ms

Resolved: Games API Endpoint performance has improved in 8a4356e.


Implement ConvertTo-Sixel

Use https://github.com/saitoha/libsixel to support converting graphics to sixel

Interesting...


Data not comming through, not sure why

Hi @jodeleeuw, I'm finally giving this a test. First, thanks for the amazing interface and instructions, the setup went very smoothly and I found it ridiculously easy and seamless to do. So hats down to you for all that hard work I think it is a big game changer in psychological science 🎩
Unfortunately, while I think I have set up everything correctly, no data is sent, and I'm not sure exactly.
I've set up this minimal example where it only has a prompt to ask for an ID and then ends by displaying the data:

experiment code
experiment

Is there anything that jumps to your eyes as to why it doesn't work (i.e., datapipe shows 0 sessions, and there is no error message at the end)? Thanks!

Hey @DominiqueMakowski,
Thanks for the kind words!
I think the error might be because you are using version 0.1 of the pipe plugin. Try changing the <script> to reference 0.3. I'm not sure why the documentation in the jspsych-contrib repo didn't update to the latest version. That's supposed to happen automatically.

Amazing it worked, cheers!
Small suggestion: while there is the little "loading" screen with the rotating circle, maybe we could add a message being displayed like "Please wait while the data is being saved"
Anyway, thanks again ☺

Thanks, that's a good idea. I've added an issue here: https://github.com/jspsych/jspsych-contrib/issues/81


Updates nuxt version to align with current released nuxtJS

Fixes downstream audit failures in repos consuming this package

.

This doesn't make much sense to me. 2.15.8 should be compatible with >=2.9.0.

I think that's up to application authors to assess. A vulnerability existing in a dependency does not mean it is exploitable, and I don't think it should be up to plugin / library authors to enforce this via a peer dep

It's up to you but even creating a hard version requirement to address a vulnerability still won't allow a bypass of the audit errors in the application author repos. Not sure what value maintaining support for a version NuxtJS themselves haven't even released a patch version to since Aug 28, 2019 is. They are moving to NuxtJS v3 in a few days as well which will further deprecate their older versions.


Merge 11-20 updates to live

:warning: Validation status: warnings

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/visual-basic-user-interface-help.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

Language/Reference/User-Interface-Help/add-ins-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/ampersand-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/caret-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/comparison-operators.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/debug-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/edit-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/file-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/format-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/help-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/insert-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/item-is-not-a-valid-control-type-error-720.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/like-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/minus-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operator-summary.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operators-keyword-summary.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/or-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/readme.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/run-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/tools-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/userform-command-bar.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/view-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-language-reference.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/window-menu-commands.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/xor-operator.md
:white_check_mark:Succeeded
View

Language/Reference/dialog-boxes.md
:white_check_mark:Succeeded
View

Language/Reference/menus-commands.md
:white_check_mark:Succeeded
View

Language/Reference/window-elements.md
:white_check_mark:Succeeded
View

api/TOC.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-user-interface-help.md

Line 23: [Warning] Invalid file link:(~/Language/Reference/Language/Reference/ambiguous-selection.md).
Line 292: [Warning] Invalid file link:(~/Language/Reference/Language/Reference/keyword-not-found.md).
Line 528: [Warning] Invalid file link:(~/Language/Reference/Language/How-to/user-defined-type-may-not-be-passed-byval.md).
Line 529: [Warning] Invalid file link:(~/Language/Reference/Language/How-to/user-defined-type-not-defined.md).
Line 530: [Warning] Invalid file link:(~/Language/Reference/Language/How-to/user-defined-type-without-members-not-allowed.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

.openpublishing.redirection.json
:warning:Warning

Details

Language/Reference/User-Interface-Help/visual-basic-user-interface-help.md
:warning:Warning
View
Details

Language/Reference/User-Interface-Help/add-ins-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/ampersand-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/caret-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/comparison-operators.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/debug-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/edit-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/file-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/format-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/help-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/insert-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/item-is-not-a-valid-control-type-error-720.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/like-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/minus-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operator-summary.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operators-keyword-summary.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/or-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/readme.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/run-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/tools-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/userform-command-bar.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/view-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-definitions.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-language-reference.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-menus.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/window-menu-commands.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/xor-operator.md
:white_check_mark:Succeeded
View

Language/Reference/dialog-boxes.md
:white_check_mark:Succeeded
View

Language/Reference/menus-commands.md
:white_check_mark:Succeeded
View

Language/Reference/window-elements.md
:white_check_mark:Succeeded
View

api/TOC.md
:white_check_mark:Succeeded
View

.openpublishing.redirection.json

[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'access/concepts/miscellaneous/ado-syntax-indexes.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
Learn more: https://review.docs.microsoft.com/en-us/help/contribute/redirect-articles?branch=master#3-master-redirection-file

Language/Reference/User-Interface-Help/visual-basic-user-interface-help.md

Line 528: [Warning] Invalid file link:(~/Language/Reference/How-to/user-defined-type-may-not-be-passed-byval.md).
Line 529: [Warning] Invalid file link:(~/Language/Reference/How-to/user-defined-type-not-defined.md).
Line 530: [Warning] Invalid file link:(~/Language/Reference/How-to/user-defined-type-without-members-not-allowed.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

Language/Reference/User-Interface-Help/visual-basic-user-interface-help.md
:warning:Warning
View
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

Language/Reference/User-Interface-Help/add-ins-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/ampersand-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/caret-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/comparison-operators.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/debug-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/edit-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/file-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/format-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/help-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/insert-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/item-is-not-a-valid-control-type-error-720.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/like-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/minus-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operator-summary.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/operators-keyword-summary.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/or-operator.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/readme.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/run-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/tools-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/userform-command-bar.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/view-menu.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-definitions.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-language-reference.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-menus.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/window-menu-commands.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/xor-operator.md
:white_check_mark:Succeeded
View

Language/Reference/dialog-boxes.md
:white_check_mark:Succeeded
View

Language/Reference/menus-commands.md
:white_check_mark:Succeeded
View

Language/Reference/window-elements.md
:white_check_mark:Succeeded
View

access/Concepts/Miscellaneous/ado-syntax-indexes.md
:white_check_mark:Succeeded
View

api/TOC.md
:white_check_mark:Succeeded
View

Language/Reference/User-Interface-Help/visual-basic-user-interface-help.md

Line 528: [Warning] Invalid file link:(~/Language/Reference/How-to/user-defined-type-may-not-be-passed-byval.md).
Line 529: [Warning] Invalid file link:(~/Language/Reference/How-to/user-defined-type-not-defined.md).
Line 530: [Warning] Invalid file link:(~/Language/Reference/How-to/user-defined-type-without-members-not-allowed.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix license header

TL;DR
Fix license header by using a year parameter
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
With this, we will not be forced to use 2021 forever.
Tracking Issue
Remove the 'fixes' keyword if there will be multiple PRs to fix the linked issue
NA
Follow-up issue
NA

We could also retrospectively updating all headers according to git commit history but that would be a massive change. Do we want to do this?
It is also worth noting that spotless license header thing does not support package-info.java, so those files we can only do manually.


Merging sustsidequest feature from dev to release for test

Merging the sustainable building side quest to dev for further testing.

PR approved


Log handshakes as previous state UNINITIALIZED

Summary
When logging during the INIT and TRYOPEN steps of the handshake for both connection and channel. Change the previous state from NONE to UNINITIALIZED. See comment
Should be applied to both 03-connection and 04-channel handshake steps. Please assign yourself or comment on the issue if you will be handling it. May be backported.

For Admin Use

[x] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Hi @GNaD13. Sorry, I missed your message and just saw it now... I think I am going to close this issue now, because its partly solved by https://github.com/cosmos/ibc-go/pull/3384 and it will be completely solved with https://github.com/cosmos/ibc-go/issues/3385. Thank for volunteering, I hope you can find another issue to work on. :)


Integrating this package back to TWP

Earlier this package was createed for separating the Ssl SNI and ALPN features, but it is not really easy, since not enough to modify the ALPN in the SSL hello message.
So now this package contains 3 type of functions:
Streams: buffered, copy (Alpn adder streems are not really useful)
SSL parser, which is I think not really releated to this package.
And a buffer pool class
Stream classes are quite TWP specific, implements that methods which are needed for TWP,
I think they are not a big deal, everybody implements it when needed. (In that way as they need)
In my opinion currently it just makes harder to modify something in it. (Which - i guess - willl be done for TPW, and probably it is a breaking change for direct users)
So maybe you should consider merging back this package to TWP.
Do you think that anybody uses it directly?
I think we should wait for other user opinions, and if there are a lot of users who are against the merge, then leave it. Otherwise merge it to TWP.

Agree. Let's leave this package as it is. And we can copy this project into TWP repository as a new project.

You can create a PR if you wish to do that.

I imported it there.

I've revoked previously the push access you had since I wasn't sure you will be active again. I've restored it. Also, I created a branch rule that requires at least one approval for any PR to be merged and restrict direct commits to master, beta or stable branches. I will create my changes through pull requests in the future unless I need direct access to debug build issues.

thanks:)


Generated browser-Dockerfile fails to install edge

It is currently not possible to generate new browser images containing edge.
Runing with node 16.17.0, npm 8.15.0, and yarn 1.22.19 you get:
$ git clone https://github.com/cypress-io/cypress-docker-images
$ cd cypress-docker-images
$ yarn
[... install packages ...]
$ yarn add:browser  16.17.0 --edge
yarn run v1.22.19
$ node ./scripts/generate-browser-image 16.17.0 --edge
creating "browsers/node16.17.0-edge"
Saved browsers/node16.17.0-edge/Dockerfile
Saved browsers/node16.17.0-edge/README.md
Saved browsers/node16.17.0-edge/build.sh

Please add the newly generated folder browsers/node16.17.0-edge to Git. Build the Docker container locally to make sure it is correct.

** outputFolder : browser/node16.17.0-edge
** image : { name: 'browser', tag: 'node16.17.0-edge' }

Generated circle.yml
Saved CHANGELOG.md at [...]/browsers/CHANGELOG.md
Saved README.md at [...]/browsers/README.md
Do you want to commit this change? (y/n)n
Done in 7.94s.
$ cd browsers/node16.17.0-edge/
$ ./build.sh
Building cypress/browsers:node16.17.0-edge
[+] Building 9.9s (11/12)
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 2.62kB                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/cypress/base:16.17.0                                                                                9.1s
 => [1/8] FROM docker.io/cypress/base:16.17.0@sha256:158c406df6d039d27d407a00c0caa05db6224e01d335911c3f5a3003b35fcc09                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 753B                                                                                0.0s
 => CACHED [2/8] RUN node --version                                                                                0.0s
 => CACHED [3/8] COPY ./global-profile.sh /tmp/global-profile.sh                                                                                0.0s
 => CACHED [4/8] RUN cat /tmp/global-profile.sh >> /etc/bash.bashrc && rm /tmp/global-profile.sh                                                                                0.0s
 => CACHED [5/8] RUN apt-get update &&   apt-get install -y   fonts-liberation   git   libcurl4   libcurl3-gnutls   libcurl3-nss   xdg-utils   wget   curl     gnupg   dirmngr   && rm -rf /var/lib/apt/li  0.0s
 => CACHED [6/8] RUN wget --no-verbose /usr/src/libappindicator3-1_0.4.92-7_amd64.deb "http://ftp.us.debian.org/debian/pool/main/liba/libappindicator/libappindicator3-1_0.4.92-7_amd64.deb" &&   dpkg -i   0.0s
 => ERROR [7/8] RUN node -p "process.arch === 'arm64' ? 'Not downloading Edge since we are on arm64: https://techcommunity.microsoft.com/t5/discussions/edge-for-linux-arm64/m-p/1532272' : process.exit(1  0.7s
------
 > [7/8] RUN node -p "process.arch === 'arm64' ? 'Not downloading Edge since we are on arm64: https://techcommunity.microsoft.com/t5/discussions/edge-for-linux-arm64/m-p/1532272' : process.exit(1)" ||   (curl https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg   install -o root -g root -m 644 microsoft.gpg /etc/apt/trusted.gpg.d/ &&   sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/edge stable main" > /etc/apt/sources.list.d/microsoft-edge-dev.list' &&   rm microsoft.gpg &&   apt-get update &&   apt-get install -y microsoft-edge-dev &&   ln -s /usr/bin/microsoft-edge /usr/bin/edge):
#11 0.373 usage: gpg [options] --dearmor [file]
#11 0.377   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
#11 0.377                                  Dload  Upload   Total   Spent    Left  Speed
100   983  100   983    0     0   3201      0 --:--:-- --:--:-- --:--:--  3191
#11 0.684 (23) Failed writing body
------
executor failed running [/bin/sh -c node -p "process.arch === 'arm64' ? 'Not downloading Edge since we are on arm64: https://techcommunity.microsoft.com/t5/discussions/edge-for-linux-arm64/m-p/1532272' : process.exit(1)" ||   (curl https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg   install -o root -g root -m 644 microsoft.gpg /etc/apt/trusted.gpg.d/ &&   sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/edge stable main" > /etc/apt/sources.list.d/microsoft-edge-dev.list' &&   rm microsoft.gpg &&   apt-get update &&   apt-get install -y microsoft-edge-dev &&   ln -s /usr/bin/microsoft-edge /usr/bin/edge)]: exit code: 2
$

The generated Dockerfile is:
# WARNING: this file was autogenerated by generate-browser-image.js
# using
#   yarn add:browser -- 16.17.0 --edge
#
# build this image with command
#   docker build -t cypress/browsers:node16.17.0-edge .
 'Not downloading Edge since we are on arm64: https://techcommunity.microsoft.com/t5/discussions/edge-for-linux-arm64/m-p/1532272' : process.exit(1)" || \
  (curl https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg \
  install -o root -g root -m 644 microsoft.gpg /etc/apt/trusted.gpg.d/ && \
  sh -c 'echo "deb [arch=amd64] https://packages.microsoft.com/repos/edge stable main" > /etc/apt/sources.list.d/microsoft-edge-dev.list' && \
  rm microsoft.gpg && \
  ## Install Edge
  apt-get update && \
  apt-get install -y microsoft-edge-dev && \
  ## Add a link to the browser that allows Cypress to find it && \
  ln -s /usr/bin/microsoft-edge /usr/bin/edge)

# versions of local tools
RUN echo  " node version:    $(node -v) \n" \
  "npm version:     $(npm -v) \n" \
  "yarn version:    $(yarn -v) \n" \
  "debian version:  $(cat /etc/debian_version) \n" \
  "Chrome version:  n/a \n" \
  "Firefox version: n/a \n" \
  "Edge version:    $(edge --version) \n" \
  "git version:     $(git --version) \n" \
  "whoami:          $(whoami) \n"

# a few environment variables to make NPM installs easier
# good colors for most applications
ENV TERM=xterm
# avoid million NPM install messages
ENV npm_config_loglevel=warn
# allow installing when the main user is root
ENV npm_config_unsafe_perm=true

The problem was introduced with https://github.com/cypress-io/cypress-docker-images/commit/f2e8fc5851ab7dca43e570bb7d1742af8a749d83 in #700 in generate-browser-images.js: multiple RUN commands were combined but the continuation of the commands was slightly off.


0...n relationship in .xsd

Hi,
First of all, thank you for this library, it's very helpful !
I am a perfect newbie to coding and github so please accept all my apologies if I make mistakes or misuse in the following attempt.
I think I've an issue with XmlProvider and my .xsd scheme.
In my .xsd I have a Node "Reason" that is descendant of the Node "Point" with attributes minOccurs = 0 and maxOccurs = unbounded.
I was expecting the type "Point" to be created with an argument for "Reason" typed as an Option<Reason[]>. Instead of that the type "Point" requires an array of Reason[] and it's not optional.
here is the part of the .xsd
<xs:complexType name="Point">
	<xs:sequence>
		<xs:element name="Reason" type="Reason" minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>
</xs:complexType>

the behavior is the same with all the relationships build on minOccurs = 0 and maxOccurs = "unbounded". When minOccurs = 1 or maxOccurs = 1, it works fine.
I hope to be clear enough. If it's not an issue in XmlProvider, can you tell me how I can create a "Point" with no "Reason" ?
Roland

Hi @RolandTLH , I think the type provider is behaving as expected: when maxOccurs is unbounded (actually as soon as it is greater than one) an array is needed.
The only case in which we get an Option is when minOccurs = 0 and maxOccurs = 1, as you can see in the getMultiplicity function.
If you need a Point with no Reason just use an empty array.

Hi @giacomociti . Thank you for the answer and the solution. It works. I thought without trying that I couldn't pass an empty array. I guess it's the main lesson here : I should always try first.


Add stac-api-validator

Description
Adds stac-api-validator to CI. Doesn't include features and item-search validation, but includes comments in the validation script saying why.
IMO this could be a good check to make sure updates are still producing valid STAC API, but is potentially risky because stac-api-validator is still under pretty active development. I've pinned the version to a known good-enough version to help guard againt unexpected regressions that aren't our fault.
Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
I've run the validation script locally.
Checklist:

[x] I have performed a self-review
[x] Code is linted and styled (./scripts/format)

Looks good, thanks! Will keep an eye out for flake, per your comment, but is a good addition.


Fix refresh 'Project Settings' window

Fixes #80808 and #25865
After clicking on a tab window (General or Input Map) an update is forced.
Tests: https://github.com/godotengine/godot/issues/80808#issuecomment-1687175715

After clicking on a tab window (General or Input Map) an update is forced.

There is ProjectSettings.settings_changed signal. You can connect to it and update the editor (if it's visible) on any setting change, without having to click on a tab.

There is ProjectSettings.settings_changed signal. There is no similar signal for InputMap yet.

settings_changed ( ) Emitted when any setting is changed, up to once per process frame.
ok thank you, I'll check if this is already suitable. The input fields already react to changes, but if new settings are inserted or removed, it must be updated in the dialog first. I think new signals are necessary settings_added, settings_removed ?

ProjectSettings.settings_changed is unfortunately not yet suitable. The signal would have to pass the parameters name, old_value and new_value.
I added settings_changed anyway to remember timestamp for last update. Multiple plugins could change a lot of values. Only 'Refresh' after clicking on a tab window seems to be the best solution. Update only, when the user needs to see it.

Is this PR still needed? Otherwise I will close to clean up my list.

Is this PR still needed? Otherwise I will close to clean up my list.

Assuming that the two linked bugs are still reproducible, I would suppose so? I don't know if the solution is correct (haven't reviewed in depth) but it still seems something worth improving.

Deleted by mistake.
I'll leave it deleted, it's been a long time, I can't remember what I was doing.


Add "use_cwd" flag to cloning

Hey Kasper 👋
I've added a "clone into cwd" funtionality.
However, it's not a particular beautiful solution and the extend of testing it is "works on my machine" 🙈
I've never tried making a cli before. So I'm completely a rookie when it comes to conventions etc. So if there's anything here, let me know.
Furthermore, I can see the "gh auth token" fix wasn't applied either. So I made one too.
Fire away 😅

Don't mind the testing too much, I've got some backported settings from lunar-clone, which enables some proper testing stuff.

@kjuulh I've added some changes based on the PR comments and what we talked about IRL.
Please also see if you can run it on your machine (would make me feel a bit safer 😅)
Let me know what you think.

I'll get some of my changes backported to this repo. So that we can get away from the environment variable. =D


Add Scapy presentation from Troopers Conference

Looks like a cool video, thanks for the contribution and sorry for the delay!


Converter Error : for converting saved-model to tflite

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
TensorFlow installed from (source or binary): pip install tensorflow
TensorFlow version (or github SHA if from source): 2.3.0 , also installed tf-nightly

Command used to run the converter or code if you’re using the Python API
If possible, please share a link to Colab/Jupyter/any notebook.
# Copy and paste here the exact command

import tensorflow as tf
saved_model_dir = 'C:\Users\diksh\Desktop\Fine_Tuned_Model\saved_model'
model = tf.saved_model.load(saved_model_dir)
model.signatures[tf.saved_model.DEFAULT_SERVING_SIGNATURE_DEF_KEY].inputs[0].set_shape([1, 256, 256, 3])
tf.saved_model.save(model, "saved_model_updated", signatures=model.signatures[tf.saved_model.DEFAULT_SERVING_SIGNATURE_DEF_KEY])
Convert
converter = tf.lite.TFLiteConverter.from_saved_model(saved_model_dir='saved_model_updated', signature_keys=['serving_default'])
converter.optimizations = [tf.lite.Optimize.DEFAULT]
converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS, tf.lite.OpsSet.SELECT_TF_OPS]
tflite_model = converter.convert()
TFLite Interpreter to check input shape
interpreter = tf.lite.Interpreter(model_content=tflite_model)
interpreter.allocate_tensors()
Get input and output tensors.
input_details = interpreter.get_input_details()
output_details = interpreter.get_output_details()
Test the model on random input data.
input_shape = input_details[0]['shape']
print(input_shape)
The output from the converter invocation
Exception                                 Traceback (most recent call last)
~\AppData\Roaming\Python\Python37\site-packages\tensorflow\lite\python\convert.py in toco_convert_protos(model_flags_str, toco_flags_str, input_data_str, debug_info_str, enable_mlir_converter)
198                                                  debug_info_str,
--> 199                                                  enable_mlir_converter)
200       return model_str
~\AppData\Roaming\Python\Python37\site-packages\tensorflow\lite\python\wrap_toco.py in wrapped_toco_convert(model_flags_str, toco_flags_str, input_data_str, debug_info_str, enable_mlir_converter)
37       debug_info_str,
---> 38       enable_mlir_converter)
39
Exception: :0: error: loc("Func/StatefulPartitionedCall/input/_0"): requires all operands and results to have compatible element types
:0: note: loc("Func/StatefulPartitionedCall/input/_0"): see current operation: %1 = "tf.Identity"(%arg0) {_class = ["loc:@Func/StatefulPartitionedCall/StatefulPartitionedCall/input/_702"], device = ""} : (tensor<1x256x256x3x!tf.quint8>) -> tensor<1x256x256x3xui8>
During handling of the above exception, another exception occurred:
ConverterError                            Traceback (most recent call last)
 in
11 converter.optimizations = [tf.lite.Optimize.DEFAULT]
12 converter.target_spec.supported_ops = [tf.lite.OpsSet.TFLITE_BUILTINS, tf.lite.OpsSet.SELECT_TF_OPS]
---> 13 tflite_model = converter.convert()
14
15 ## TFLite Interpreter to check input shape
~\AppData\Roaming\Python\Python37\site-packages\tensorflow\lite\python\lite.py in convert(self)
1074         Invalid quantization parameters.
1075     """
-> 1076     return super(TFLiteConverterV2, self).convert()
1077
1078
~\AppData\Roaming\Python\Python37\site-packages\tensorflow\lite\python\lite.py in convert(self)
898
899     return super(TFLiteFrozenGraphConverterV2,
--> 900                  self).convert(graph_def, input_tensors, output_tensors)
901
902
~\AppData\Roaming\Python\Python37\site-packages\tensorflow\lite\python\lite.py in convert(self, graph_def, input_tensors, output_tensors)
631         input_tensors=input_tensors,
632         output_tensors=output_tensors,
--> 633         **converter_kwargs)
634
635     calibrate_and_quantize, flags = quant_mode.quantizer_flags(
~\AppData\Roaming\Python\Python37\site-packages\tensorflow\lite\python\convert.py in toco_convert_impl(input_data, input_tensors, output_tensors, enable_mlir_converter, *args, **kwargs)
572       input_data.SerializeToString(),
573       debug_info_str=debug_info_str,
--> 574       enable_mlir_converter=enable_mlir_converter)
575   return data
576
~\AppData\Roaming\Python\Python37\site-packages\tensorflow\lite\python\convert.py in toco_convert_protos(model_flags_str, toco_flags_str, input_data_str, debug_info_str, enable_mlir_converter)
200       return model_str
201     except Exception as e:
--> 202       raise ConverterError(str(e))
203
204   if distutils.spawn.find_executable(_toco_from_proto_bin) is None:
ConverterError: :0: error: loc("Func/StatefulPartitionedCall/input/_0"): requires all operands and results to have compatible element types
:0: note: loc("Func/StatefulPartitionedCall/input/_0"): see current operation: %1 = "tf.Identity"(%arg0) {_class = ["loc:@Func/StatefulPartitionedCall/StatefulPartitionedCall/input/_702"], device = ""} : (tensor<1x256x256x3x!tf.quint8>) -> tensor<1x256x256x3xui8>
# Copy and paste the output here.

Also, please include a link to the saved model or GraphDef
# Put link here or attach to the issue.

Failure details
If the conversion is successful, but the generated model is wrong,
state what is wrong:

Producing wrong results and/or decrease in accuracy
Producing correct results, but the model is slower than expected (model generated from old converter)

RNN conversion support
If converting TF RNN to TFLite fused RNN ops, please prefix [RNN] in the title.
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

Please could you share a very, very minimal but complete standalone or colab example that we could copy, past and run to reproduce your issue?

Here is the link with the jupyter notebooks and saved model data
https://drive.google.com/drive/folders/1MCvDti2ygukqw6fGE18WpnFOSzR_AanF?usp=sharing
Im working on a team where i have been requested to convert the saved_model to a tflite.
The "FLIR_retraining.ipynb" is the file to retrain the model.
and the "TFLite_converter.ipynb" is a shorter version that I have been trying to use for the conversion.
Thank you.

@dikshantjn,
I was able to reproduce the error with TF v2.3.
However, with the latest TF-nightly I was able to run the code without any issues. Please find the attached gist. Thanks!

I'm still getting the same error:
":0: error: loc("Func/StatefulPartitionedCall/input/_0"): requires all operands and results to have compatible element types
:0: note: loc("Func/StatefulPartitionedCall/input/_0"): see current operation: %1 = "tf.Identity"(%arg0) {_class = ["loc:@Func/StatefulPartitionedCall/StatefulPartitionedCall/input/_702"], device = ""} : (tensor<1x256x256x3x!tf.quint8>) -> tensor<1x256x256x3xui8>"

@amahendrakar
Thank you .... I was able to convert the model to tflite in colab, previously I was trying it on my windows PC
I am now trying to save it on my drive using :
tflite_file = 'Fine_Tuned_Model/head_detector.tflite'
open(tflite_file, "wb").write(tflite_model)
But it is not generating any files
Please help

@dikshantjn,
I was able to write the head_detector.tflite file to disk without any issues, please find the gist of it here.
Could you please share the gist of the Colab notebook you are running? Thanks!

@amahendrakar here is the colab
https://colab.research.google.com/drive/1_9l_DcyNuVV1NxU3PsmSMjWeI9nTEwNS?usp=sharing

@amahendrakar .... with the latest version of tf-nightly, the  order of output tensors changes. If you could help me understand that and what is the meaning of each of them

@dikshantjn,
Could you please submit a new issue from this link and fill in the template, so that we can track the issue there. Thanks!

@amahendrakar .... with the latest version of tf-nightly, the order of output tensors changes. If you could help me understand that and what is the meaning of each of them

I faced this issue too. Had to debug the shape of each output to get it to work.
Regardless, it worked. Not with the current tf-nightly build but with the one used in the gist posted by @amahendrakar https://colab.research.google.com/gist/amahendrakar/3c9f9d7540e521fa298398a6e5538bee/43211-tf-nightly.ipynb


fix: fix missing embedding_types

Fix #50

Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 95.83%. Comparing base (0ba089b) to head (9469ab0).
Report is 2 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #51   +/-   ##
========================================
  Coverage    95.83%   95.83%
========================================
  Files           17       17
  Lines          336      336
========================================
  Hits           322      322
  Misses          14       14

Components
Coverage Δ

core
100.00% <ø> (ø)

api
88.52% <0.00%> (ø)

tests
100.00% <ø> (ø)


[release-2.7] Added sonar project properties file to repo

Related issue: https://github.com/stolostron/backlog/issues/24274
Signed-off-by: dislbenn<EMAIL_ADDRESS>

/lgtm
/approve


Error in MICN model

Hello.
MICN model does not run. Some mismatch with array size. Error shown below for 'scripts/long_term_forecast/ETT_script/MICN_ETTh1.sh' case.
File "/home//Time-Series-Library/models/MICN.py", line 209, in forward
dec_out = self.forecast(x_enc, x_mark_enc, x_dec, x_mark_dec)
File "/home//Time-Series-Library/models/MICN.py", line 166, in forecast
dec_out = self.dec_embedding(seasonal_init_dec, x_mark_dec)
File "/home//Time-Series-Library//python3.9/site-packages/torch/nn/modules/module.py", line 727, in _call_impl
result = self.forward(*input, kwargs)
File "/home/***/Time-Series-Library/layers/Embed.py", line 124, in forward
x = self.value_embedding(
RuntimeError: The size of tensor a (816) must match the size of tensor b (768) at non-singleton dimension 1

Hello,
Thank you for your feedback. According to our testing, you can temporarily solve this problem by changing --label_len from 48 to 96 in 'scripts/long_term_forecast/ETT_script/MICN_ETTh1.sh'.
This issue may be caused by the mismatch between the official implementation of MICN and our framework.as label_len must be equal to seq_len.If possible, we will fix this issue in the next commit.

Thank a lot for your reply!


Have an opinionated MDX setup

It would be great if this tool optionally included all the MDX packages you would need, so you could remove dependencies from your repository like mdx-bundler (and esbuild which is needed for it).

Thanks for this great suggestion @leerob. This has now been released with https://github.com/contentlayerdev/contentlayer/releases/tag/v0.0.28


feature request: Define fields that are not arguments to the constructor

Discussed in https://github.com/pydantic/pydantic/discussions/5929

Originally posted by felix-hilden May 30, 2023
I'd like to define a field that is not available in the model arguments. So to define an instance attribute with either a default or a default factory, and no way to change it when constructing the model (assigning is fine). To essentially achieve this:
class Foo:
    def __init__(self, a: int, b: str = ""):
        self.a = a
        self.b = b
        self.c = generate_c()  # or without the call as just a default value

Does Pydantic support this? I didn't find relevant arguments to Field that would do it, or any information when searching online. I see that private (ignored) fields are available, but I'd like for this to be compatible with validation and inheritance. So I could write for example:
class Foo(BaseModel):
    a: int
    b: str = ""
    c: int

class Bar(Foo):
    c: int = Field(default_factory=list, no_init=True)
```</div>

Just a quick note — if we do this, I think we should almost certainly use init: bool = True as the default argument, because then it will play nice with Intellisense thanks to @dataclass_transform.

👍🏻 It's about PEP 681 allover again.


Add affiliation for Vaastav Anand

Codecov Report

Merging #85 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #85   +/-   ##
======================================
  Coverage    99.5%   99.5%
======================================
  Files           8       8
  Lines         204     204
  Branches       35      35
======================================
  Hits          203     203
  Partials        1       1


chore: add travis and goreleser

The intention of this commit is to allow to have binary releases of vals tool on Github
But tests aren't passing :(

@aldor007 Hey! Thanks for the PR. Just confirming, but why did you remove pkg/providers/gcpsecrets/gcpsecrets_test.go ?

Hi @mumoshu
I've removed pkg/providers/gcpsecrets/gcpsecrets_test.go because of the cycle that this file is making.
# github.com/variantdev/vals/pkg/providers/gcpsecrets
import cycle not allowed in test
package github.com/variantdev/vals/pkg/providers/gcpsecrets (test)
	imports github.com/variantdev/vals
	imports github.com/variantdev/vals/pkg/providers/gcpsecrets

https://travis-ci.com/github/aldor007/vals/builds/161295846
I was thinking how to fix it but in this test, I can't see any assertion so IMO it is not checking anything
Sadly tests aren't passing event after this change
https://travis-ci.com/github/aldor007/vals/builds/161478400

Thanks!
For vals_awssecrets_test.go, it won't pass without actual AWS credentials. So please feel free to skip it on CI for now.
For Vault-related tests, I thought I had to run a vault devserver for that to pass.
Finally, pkg/providers/gcpsecrets/gcpsecrets_test.go seems like an incomplete test that seems to not work at all. Sry for back and forth but please feel free to remove it!

@aldor007 I've just finished setting up automated binary releases with goreleaser and GitHub Actions. This work has been the source of inspiration for that! Thanks for your contribution.


[ACS JobRouter] Test proxy migration

update all tests using test proxy
recordings updated

Related to issue: https://github.com/Azure/azure-sdk-for-python/issues/26512
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Support Project Reactor for message handlers

I want to return Mono<?> or Flux<?> from my @MessageHandler methods and have Axon Framework utilize that efficiently. The framework must subscribe on the correct thread and wire interceptors to the flow.
Currently, Axon does not even subscribe to these.
I don't know what could be a solution for constructor command handlers, looks like the user has to subscribe themselves in there.

Project Reactor is currently only used for the Subscription Query solution, but even then it's still an optional dependency within Axon. The idea behind this is that Axon Framework should rely on as few other libraries/frameworks as possible to do it's core business.
At first, we were not even using Project Reactor, but practically building our own Mono and Flux implementations to support the Subscription Query.
Taking this stance, we will not start using Project Reactor throughout, which is exemplified in issue #752 as well (which in essence is about the same topic).
As such, I'll be closing this issue as a wont fix. In the mean time, I'd like to ask you to check the existing list of issue prior to creating a duplicate of sorts.

Thanks for the answer! I've actually looked at this issue before creating this one. #752 does not have any info, it was just closed.
What do you mean it's optional dependency? It's actually required for subscription queries, so Axon is tied to this already.

#752 does not have any info, it was just closed.
I see the discrepancy, sorry for thoughtlessly pointing you towards it. The reason for closing is the fact of making it a required dependency, as said, which we do not want to enforce on any of the framework users. As soon as the thought behind Project Reactor is part of Java for example, I am sure we'll reconsider it.

What do you mean it's optional dependency?
It's tagged optional in the settings, meaning that if you do not utilize the subscription query, your application will not pull in the Project Reactor repository at all.


Images and videos not being sent properly on MacOS Montery

Images or videos that are sent from Bluebubbles with the server on MacOS Montery show as corrupted files to the recipient and on iMessage on the Mac.

I've fixed this for the upcoming 1.3.0 release, hopefully today


Add metric group table cassandra

Resolves
https://jira.rax.io/browse/CERES-487
What
Implement a new table for metricGroup in cassandra.
How
Created a new entity metricGroup
How to test
Run junit tests for DataWriteService and QueryService
Why
After architecture review
TODO
TBD: Need to work on the tests

Need to do some more research, changing the status to DRAFT

Please ignore my last comment. I was kind of confused this and Abhi's PR.


Any plan to make the code and the model public soon?

I would like to know if the code and and the model weights will be public anytime soon.

We will release the code as soon as possible after eccv :)
Thank you for your patience and understanding.

I understand, thank you for your amazing work!
I would like to know if the trained model will also be public.

Yes. The trained model will be released with our code.
Thanks.

Great news :)


Reduce estimated fam xp

Believe at best we'll have still suit for 1 extra xp per turn. This made it so short order was picked instead of pocket prof for me

Let's do, like, 3 and then figure something better out later


very bad UI (for me) as a new comer (I am forced to use this tool since my workplace purchased a license...)

I just want to use this for simple sketching, trying to find basic UI icons should not take more than 1 min (not my 1st tool)
I am in 5 min and I see no clear step by step - when I clicked help -> I landed in help dedicated for developers, nice but not relevant...
I am always open to the idea it is something only I am missing and everyone else get easily.
I can always go to youtube to find a solution, so probably this will be my path forward - but I suspect if I wasted a few minutes on this , so does others.

Mild skill issue. 😂

@Gadi4Checkout could you provide us a bit more details about the issues you were facing or things you would like us to improve? Is this generally a lack of help/guidelines on how to use the editor?


docs: MAINTAINERS file and LGTM configuration

Signed-off-by: Tibor Simko<EMAIL_ADDRESS>

LGTM


Update SP data model with a "relationship" between minerIds

What
The dashboard today is minerId (SP instance in Filecoin protocol) focused.  In reality, we know that SP operations (whether individuals, entities, etc.) are often composed of multiple minerIds.  Ideally in the data model we'd have this relationship so it would be possible to bring up the performance an "SP entity/operation", looking at an aggregate view across multiple related minerIds.
Why
This came up in https://protocollabs.notion.site/2024-12-03-Client-Success-Meeting-150837df73d4801eb9cae595e2ea1d7c?pvs=4 .  It's relevant from a market perspective given onramps/aggregators care about making deals with an actual "SP entity/operation" rather than a specific minerId.
How
I (@biglep) don't know the way to accomplish this.  There is no mapping on chain of minerId to peerId.  Maybe we can look at the origin address of WindowPoSt messages and aggregate that way?  (I assume that is still an approximation, but likely gets decently close.).  I also assume other thought has been given to this in the past.
Other Notes

Maybe this belongs in https://github.com/davidgasquez/filecoin-data-portal and this issue just become about rendering that relationship?

This is an interesting question @BigLep! In the past, I've used some manually curated lists mapping provider_ids to "Entities" but that doesn't scale. Also, some entities want to remain private.
There have been many approaches to this problem, not sure if your idea has been explored though! The approach I'm using is to rely on the Filecoin's scores provided by Nova Energy (API). That only covers a handful of providers for some Entities since they have to apply and get reviewed.


 Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Hi @kuaikuai
Thank you, could you add a test and a brief description of the context this would be happening ?

https://github.com/elastic/go-elasticsearch/issues/274

the test code as the following:
package main
import (
"os"
"time"
"fmt"
"net/http"
"net/http/pprof"
"strings"
"bytes"
"sync/atomic"
"github.com/elastic/go-elasticsearch/v7"
)
type CountingTransport struct {
count uint64
}
func (t *CountingTransport) RoundTrip(req *http.Request) (*http.Response, error) {
var buf bytes.Buffer
atomic.AddUint64(&t.count, 1)
if t.count % 500 != 0 {
    return nil, fmt.Errorf("some error")
}
req.Header.Set("Accept", "application/yaml")
req.Header.Set("X-Request-ID", "foo-123")

res, err := http.DefaultTransport.RoundTrip(req)

buf.WriteString(strings.Repeat("-", 80) + "\n")
fmt.Fprintf(&buf, "%s %s", req.Method, req.URL.String())

if err != nil {
    fmt.Fprintf(&buf, "ERROR: %s\n", err)
} else {
    fmt.Fprintf(&buf, "[%s] %s\n", res.Status, res.Header.Get("Content-Type"))
}
buf.WriteTo(os.Stdout)
return res, err

}
func main() {
tp := new(CountingTransport)
hosts := []string{"http://x.x.x.x:9200","http://y.y.y.y:9200"}
es, err := elasticsearch.NewClient(elasticsearch.Config{Addresses: hosts, Transport: tp, Username:"elastic", Password:"Mam123456*"})
if err != nil {
fmt.Printf("err: %v\n", err)
return
}
for i := 0; i < 5; i++ {
go func() {
for {
es.Info()
time.Sleep(time.Millisecond * 10)
}
}()
}
r := http.NewServeMux()
r.HandleFunc("/debug/pprof/", pprof.Index)
http.ListenAndServe("<IP_ADDRESS>:6060", r)
}
in addition to speed up the testing, I change estransport/connection.go:
from:
var (
defaultResurrectTimeoutInitial      = 60 * time.Second
defaultResurrectTimeoutFactorCutoff = 5
)
to
var (
defaultResurrectTimeoutInitial      = 30 * time.Second
defaultResurrectTimeoutFactorCutoff = 3
)
I don't known how long the test have ran. when I check it again, use curl command:
curl http://<IP_ADDRESS>:6060/debug/pprof/goroutine?debug=1
1 @ 0x43c1c5 0x44db45 0x44db2e 0x46e3a7 0x47b465 0x8d22bd 0x8d223d 0x8d65b0 0x75bf48 0x89c2cd 0x8db163 0x472081
0x46e3a6	sync.runtime_SemacquireMutex+0x46								/home/yxf/go1.16.2/src/runtime/sema.go:71
0x47b464	sync.(*Mutex).lockSlow+0x104									/home/yxf/go1.16.2/src/sync/mutex.go:138
0x8d22bc	sync.(*Mutex).Lock+0x11c									/home/yxf/go1.16.2/src/sync/mutex.go:81
0x8d223c	github.com/elastic/go-elasticsearch/v7/estransport.(*statusConnectionPool).OnSuccess+0x9c	/home/yxf/compile/test/src/github.com/elastic/go-elasticsearch/v7/estransport/connection.go:138
0x8d65af	github.com/elastic/go-elasticsearch/v7/estransport.(*Client).Perform+0x88f			/home/yxf/compile/test/src/github.com/elastic/go-elasticsearch/v7/estransport/estransport.go:295
0x75bf47	github.com/elastic/go-elasticsearch/v7/esapi.InfoRequest.Do+0x487				/home/yxf/compile/test/src/github.com/elastic/go-elasticsearch/v7/esapi/api.info.go:107
0x89c2cc	github.com/elastic/go-elasticsearch/v7/esapi.newInfoFunc.func1+0x12c				/home/yxf/compile/test/src/github.com/elastic/go-elasticsearch/v7/esapi/api.info.go:21
0x8db162	main.main.func1+0x42										/home/yxf/compile/test/src/fs/main.go:57
1 @ 0x43c1c5 0x44db45 0x44db2e 0x46e3a7 0x47b465 0x8d8c5e 0x8d8b14 0x472081
0x46e3a6	sync.runtime_SemacquireMutex+0x46									/home/yxf/go1.16.2/src/runtime/sema.go:71
0x47b464	sync.(*Mutex).lockSlow+0x104										/home/yxf/go1.16.2/src/sync/mutex.go:138
0x8d8c5d	sync.(*Mutex).Lock+0x1bd										/home/yxf/go1.16.2/src/sync/mutex.go:81
0x8d8b13	github.com/elastic/go-elasticsearch/v7/estransport.(*statusConnectionPool).scheduleResurrect.func1+0x73	/home/yxf/compile/test/src/github.com/elastic/go-elasticsearch/v7/estransport/connection.go:262

I made a mistake with my first commit. In the second commit, I only changed the lock method. Can you help me review it?
@Anaethelion

I've taken some time to dig through this and I agree with @thomas-long-f3 comment.
Properly locking the connection pool should be enough to prevent the deadlock, I've pushed a change to your branch directly to reflect that.
@kuaikuai would you take some time to validate my version on your side ?

I've taken some time to dig through this and I agree with @thomas-long-f3 comment.
Properly locking the connection pool should be enough to prevent the deadlock, I've pushed a change to your branch directly to reflect that.
@kuaikuai would you take some time to validate my version on your side ?

Thanks for your help. I have validated your version and it looks good to me.

@thomas-long-f3, the change is OK.

Thank you for you help @Anaethelion, I think this code has a hidden bug maybe.
func (cp *statusConnectionPool) OnSuccess(c *Connection) error {
    // Short-circuit for live connection
    if !c.IsDead {
        return nil
    }

    cp.Lock()
    defer cp.Unlock()

    c.Lock()
    defer c.Unlock()
    /*
       In certain scenarios, another OnSuccess(c) might have occurred before this pass.
       As a result, c.IsDead is now false, and c is already in cp.live.
       Then, cp.resurrect will add c to cp.live twice, causing the connection pool to become corrupted.
    */
    c.markAsHealthy()
    return cp.resurrect(c, true)
}

@Anaethelion
My 2nd commit is a little complex, But the impact of its complexity is minor.
If you want the code to be simpler, I agree with @thomas-long-f3 comment too.

Acknowledged that removing this lock require some more refactoring, I'd prefer @kuaikuai version.
I'll update the PR accordingly.

I still believe that the commited code has a bug.
Why don't we check whether c.IsDead is false?
If I am wrong, please tell me why.
func (cp *statusConnectionPool) OnSuccess(c *Connection) error {
	c.Lock()
	// Short-circuit for live connection
	if !c.IsDead {
		c.Unlock()
		return nil
	}
        c.Unlock()

        // At that moment between c.Unlock() and cp.Lock(), if another OnSuccess(c) is executed, it could modify cp.

	cp.Lock()
	defer cp.Unlock()
	c.Lock()
	defer c.Unlock()
	// here, why we don't check c.IsDead?
	// If the previous OnSuccess(c) has already executed cp.resurrect, now this function should not call cp.resurrect(c, true).
	c.markAsHealthy()
	return cp.resurrect(c, true)
}

I don't see that happening while OnSuccess is also called under a lock at the client level.

I don't see that happening while OnSuccess is also called under a lock at the client level.
@Anaethelion
Okay, I understand now. Thank you for your help!


Remove redundant backslash from regexp

Coverage remained the same at 99.973% when pulling b824ba6595aac2f615f16e6606c2abfb4fe3d9bb on denisx:patch-1 into 7ea50b0d489958202531ce62c15dc6cbf769aab3 on andrewplummer:master.

Ok this is merged now... thanks and sorry for the delay!


Sitemap unavailable to users with access to only one locale of multisite

In a multisite installation with locales on one of the subsites, a user can be added to a group which has permission to only see a specific locale of the subsite. In that situation, the user can not see the sitemap they have access to because they don't have access to the default sitemap and therefore don't have access to the site and local switchers.
For example, concretecms.com (default) and concretecms.org (additional site) are both using the same multisite installation. Several localizations of the .org site have been set up with groups for each locale. Each locale group has permission to access the sitemap for that matching locale of the .org site.
Log in as as a user in a locale group and visit the sitemap. The sitemap loaded will be the one specified in the cookie (set to the default locale for the site):
. There's no way to switch to the sitemap the user has access to in this case:

Manually changing the cookie to the Sitemap Tree ID of the locale which the user has access to will allow the correct sitemap to be loaded:

Fixed and will be included in 9.0.2


geo: URIs are treated as phone numbers

This is a bug. I'm using the FDroid version on LineageOS.
A geo: URI will be shown as two phone numbers. This is due to #1077 (I've tested by building the app with various autoLink values).
I suppose a solution could be using autoLink="web|email" (or maybe "web|email|map") and custom code to Linkify geo: and phone numbers. A solution for geo: URIs could be a custom pattern and Linkify.addlinks like in
https://github.com/siacs/Conversations/blob/master/src/main/java/eu/siacs/conversations/utils/GeoHelper.java
https://github.com/siacs/Conversations/blob/master/src/main/java/eu/siacs/conversations/ui/adapters/MessageAdapter.java
I'd love to do this, but I don't understand where to start: where is the code adding an incoming message to a room?
Related: #1329 #2350

Also, #1140

We will see what we can do to improve this


fix individual packaging  deployment

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en .
allow individual packaging.
add included env variables load.

Already fixed in 1.4.0


Trouble adding ui-sortable as a dependency of application.

Error message
 Uncaught Error: [$injector:modulerr] http://errors.angularjs.org/1.4.5/$injector/modulerr?p0=swurveys&p1=Error%3…0at%20d%20(http%3A%2F%2Flocalhost%3A8000%2Flib%2Fangular.min.js%3A19%3A385)
Added library via src file in project 'ui-sortable'. Do I have to do a bower install for it to work?

The error provided does not actually refer to ui-sortable.
Can you elaborate more on your configuration or even better provide an example codepen/jsfiddle.
Please refer to the (many) codepen examples that are available in README.

Solved