Update pubgrub for faster range operations

This update pulls in https://github.com/pubgrub-rs/pubgrub/pull/177, optimizing common range operations in pubgrub. Please refer to this PR for a more extensive description and discussion of the changes.
The changes optimize that last remaining pathological case, bio_embeddings[all] on python 3.12, which has to try 100k versions, from 12s to 3s in the cached case. It should also enable smarter prefetching in batches (https://github.com/astral-sh/uv/issues/170), even though a naive attempt didn't show better network usage.
before 12s

after 3s

$  taskset -c 0 hyperfine --warmup 1 "../uv/target/profiling/main-uv pip compile ../uv/scripts/requirements/bio_embeddings.in"  "../uv/target/profiling/branch-uv pip compile ../uv/scripts/requirements/bio_embeddings.in"
Benchmark 1: ../uv/target/profiling/main-uv pip compile ../uv/scripts/requirements/bio_embeddings.in
  Time (mean ± σ):     12.321 s ±  0.064 s    [User: 12.014 s, System: 0.300 s]
  Range (min … max):   12.224 s … 12.406 s    10 runs

Benchmark 2: ../uv/target/profiling/branch-uv pip compile ../uv/scripts/requirements/bio_embeddings.in
  Time (mean ± σ):      3.109 s ±  0.004 s    [User: 2.782 s, System: 0.321 s]
  Range (min … max):    3.103 s …  3.116 s    10 runs

Summary
  ../uv/target/profiling/branch-uv pip compile ../uv/scripts/requirements/bio_embeddings.in ran
    3.96 ± 0.02 times faster than ../uv/target/profiling/main-uv pip compile ../uv/scripts/requirements/bio_embeddings.in

It also adds bio_embeddings[all] as a requirements test case.

The changes optimize that last remaining pathological case, bio_embeddings[all] on python 3.12, which has to try 100k versions, from 12s to 3s in the cached case.

Lol


Implement encoding functionality

Like the decoding feature set currently present, extend UIImage and NSImage to produce WebP files from their current contents.

Added! :D


Make welcome page configurable

coverage: 97.826% (+0.07%) from 97.753% when pulling 0c473bab248fba6ae765fe471ded9e468c81b314 on welcome-page into deee3dc324402c20288bc15f0af922203375c073 on master.


Save static image

I dabble in some graph theory, and it would be great to have a way to save your visualizations to a image and/or vector format for non-web formats. Something like matplotlib's img.savefig('my_path') would be awesome (even though it throws away all the interactive functionality).

hey @wronk,
We currently have an endpoint that exposes the visualizations as images, with the following URL structure:
/visualizations/<visualization-id>/screenshot/?width=<width-in-pixels>&height=<height-in-pixels>

e.g. running locally:
http://localhost:3000/visualizations/34cc6441-5078-4d7a-b29f-2032e0e39071/screenshot/?width=1024&height=768

there's a shortcut to this link that can be accessed from the "actions dropdown" on the server:

Awesome, thanks. Is there any way to do that within a script?

(assuming you are in the python client)
There's no builtin method in the client right now, but you could do it like this:
# imports and initialize client
import urllib
from lightning import Lightning
lgn = Lighting()

data = [1, 2, 3, 4, 5]
viz = lgn.line(data)

image_url = viz.get_perma_link() + '/screenshot'
# or with size parameters
# image_url = viz.get_perma_link() + '/screenshot?width=100&height=100'

# save it locally
# referenced from http://stackoverflow.com/questions/8286352/how-to-save-an-image-locally-using-python-whose-url-address-i-already-know
urllib.urlretrieve(image_url, "local-filename.png")

I would be happy to accept a PR encapsulating this functionality into the python client. If you want to take a shot it can be as straightforward as adding an additional method to the visualization class here

Yup I think that's what we're missing. Two things would probably be good to have:

A save_png method in the client when running against a server that can use the route @mathisonian pointed to

A way to do the same in the server-less mode, which will most likely need to work slightly differently.

We can start by adding (1) to the Python client, and then try to tackle (2).
---------------------------jeremyfreeman.net
@thefreemanlab
On Mon, Aug 31, 2015 at 2:58 PM, wronk<EMAIL_ADDRESS>wrote:

Awesome, thanks. Is there any way to do that within a script?
Reply to this email directly or view it on GitHub:
https://github.com/lightning-viz/lightning/issues/51#issuecomment-136512606

yeah, (2) is going to need to use something like http://html2canvas.hertzen.com/ or a similar approach

@mathisonian, I probably won't get to it anytime soon, but I'll let you guys know on this thread the moment it moves up on my priority list :)

sounds good @wronk, let us know if you run into anything else.
I've created an issue on the python client: lightning-viz/lightning-python#29, going to close this in favor of that one


Tokenising multiple words to multiple arguments

Discussed in https://github.com/PythonistaGuild/TwitchIO/discussions/449

Originally posted by DennisMinn May 13, 2024
I want to pass multiple arguments enclosed in either ' or ", but on the first argument is properly formatted, while the second argument is cut off. Is there a way to modify how the arguments is parsed?
class Bot(commands.Bot):
    def __init__(self):
        super().__init__(token='<access token>', prefix='!', initial_channels = ['<initial channel>'])

    @commands.command(name='addQA')
    async def add_qa(self, context: commands.Context, question: str, answer: str):
        print(question, answer)

Input from <initial channel> chatroom
!addQA "this is a question" "this is the answer"

Current Output
this is a question "this

Desired Output
this is a question this is the answer
```</div>

Potential fix that needs to be tested
    def process_string(self, msg: str) -> Dict[int, str]:
        while self.count < len(msg):
            loc = msg[self.count]

            if loc == '"' and not self.ignore:
                self.ignore = True
                self.start = self.count + 1
            elif loc == '"' and self.ignore:
                self.words[self.index] = msg[self.start:self.count]
                self.index += 1
                self.ignore = False
                self.start = self.count + 1
            elif loc.isspace() and not self.ignore:
                if self.start != self.count:
                    self.words[self.index] = msg[self.start:self.count]
                    self.index += 1
                self.start = self.count + 1

            self.count += 1

        if self.start < len(msg) and not self.ignore:
            self.words[self.index] = msg[self.start:len(msg)].strip()

        return self.words


Containers leftover after an initial tric run prevent future runs from working

I just ran tric run wpunit .... and it completed the run successfully. However, I believe because it's passing the response through from the tric command now as of one of the recent releases -- it's not finishing the process to remove the rest of the containers properly.
Maybe it's unrelated, but I can see the containers still there and subsequent runs of the tric run all fail because of container problems.

Error on re-run:

tric down resolves the problem for now as a workaround, but it would be great to fix this in an upcoming release.

Still happening as of 0.5.16

This issue is resolved with the release of 1.0.0 - now keeping the containers running is the goal! 💃


Adding IPv6 support

From what I read on IRC it should be more or less ready to merge into master now.
CC @punto- and @Faless for confirmation.

@punto- said it should be fine, so let's go. If it runs well in master, we'll also backport this for 2.1 as it's required by Apple.

Awesome! Now our new multiplayer is lagging behind :/
On Oct 26, 2016 09:33, "Rémi Verschelde"<EMAIL_ADDRESS>wrote:

Merged #6925 https://github.com/godotengine/godot/pull/6925.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/6925#event-836970173, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-Z217Qvaw8UHOPAF8dmgiZbRBMotBfks5q30iDgaJpZM4KgzS4
.

Yeah - we should probably start a review of existing enet forks that add ipv6 support. Upstream is not going anywhere anyway, the project seems mostly dormant, so if we find a well-maintained fork, we could grab their patches and try to keep in sync.

+1 to that
On Wed, Oct 26, 2016 at 5:20 PM, Rémi Verschelde<EMAIL_ADDRESS>wrote:

Yeah - we should probably start a review of existing enet forks that add
ipv6 support. Upstream is not going anywhere anyway, the project seems
mostly dormant, so if we find a well-maintained fork, we could grab their
patches and try to keep in sync.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/6925#issuecomment-256464995,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z24nvH26btI1mNStQCazF8jZ8Si29ks5q37X0gaJpZM4KgzS4
.


Switch to S3 + ECR.

This change is

Reviewed 1 of 1 files at r1.
Review status: :shipit: complete! all files reviewed, all discussions resolved

Comments from Reviewable

bors r+


Bug 1182464 - added info from failing container

@csrwng could you please have a look, since I'm modifying the expected error behavior slightly, I wanted to get rid of the hack that @smarterclayton didn't like, in favor of passing the error output (which is limited to 1024) up the stack.

LGTM

@mfojtik addressed your comments, how's that?

@soltysh LGTM

[merge]


windows ci failed with STATUS_DLL_INIT_FAILED

What type of bug is this?
Unexpected error
What subsystems are affected?
Standalone mode
Minimal reproduce step
Run the nightly CI
https://github.com/GreptimeTeam/greptimedb/actions/runs/9009678033/job/24754350747
What did you expect to see?
The CI is passed
What did you see instead?
The CI is failed
What operating system did you use?
Windows Server 2022
What version of GreptimeDB did you use?
latest
Relevant log output and stack trace
Caused by:
  for `benchmarks::bin/nyc-taxi`, command `'C:\a\greptimedb\greptimedb\target\debug\deps\nyc_taxi-1c449a394a7932c1.exe' --list --format terse` exited with code 0xc0000142: A dynamic link library (DLL) initialization routine failed. (os error 1114)

     Running `target\debug\sqlness-runner.exe`
error: process didn't exit successfully: `target\debug\sqlness-runner.exe` (exit code: 0xc0000142, STATUS_DLL_INIT_FAILED)
Error: Process completed with exit code 1.

On Windows Server 2022 there are some strange DDL issues.
1434:0d10 @ 09019093 - LdrpInitializeNode - ERROR: Init routine 00007FFDA6925700 for DLL "C:\Windows\SYSTEM32\vertdll.dll" failed during DLL_PROCESS_ATTACH
1434:0d10 @ 09019093 - LdrpInitializeProcess - ERROR: Running the init routines of the executable's static imports failed with status 0xc0000142
1434:0d10 @ 09019093 - _LdrpInitialize - ERROR: Process initialization failed with status 0xc0000142

After adding vertdll.dll from Windows 10 to target/debug/, the sqlness.exe could be executed.

The dumpbin command shows that we uses WaitOnAddress from the vertdll.dll
 .\dumpbin.exe -imports sqlness-runner.exe

Outputs:
vertdll.dll
            141C09710 Import Address Table
            1423918D8 Import Name Table
                    0 time date stamp
                    0 Index of first forwarder reference

                        7 WaitOnAddress
                        9 WakeByAddressSingle
                        8 WakeByAddressAll

I wonder if it is related to this issue https://github.com/rust-lang/rust/issues/123999

Some tests are failed on Windows Server 2019. We got a permission denied error while deleting a file. But the file is actually deleted.
2024-05-11T12:00:57.565505Z  INFO common_telemetry::logging: logs dir = /tmp/__unittest_logs
2024-05-11T12:00:57.566327Z  INFO mito2::cache::file_cache::tests: temp dir is C:\Users\ADMINI~1\AppData\Local\Temp\2\T8ZIFB
2024-05-11T12:00:57.777286Z DEBUG mito2::cache::file_cache: deleted file files/8589934592000.67b7aad5-1616-491e-9301-55e6dadfd2e3.parquet
2024-05-11T12:00:57.778244Z  WARN mito2::cache::file_cache: Failed to delete a cached file files/8589934592000.67b7aad5-1616-491e-9301-55e6dadfd2e3.parquet err=PermissionDenied (permanent) at delete => permission denied

Context:
   service: fs
   path: files/8589934592000.67b7aad5-1616-491e-9301-55e6dadfd2e3.parquet

Source:
   Access is denied. (os error 5)

Maybe another related issue: https://github.com/nextest-rs/nextest/issues/1493

The error still exists in the release action......
https://github.com/GreptimeTeam/greptimedb/actions/runs/9114277736/job/25057956421#logs

The error still exists in the release action...... https://github.com/GreptimeTeam/greptimedb/actions/runs/9114277736/job/25057956421#logs

Added a workaround for this in https://github.com/GreptimeTeam/greptimedb/pull/3969

Let's keep this open until https://github.com/nextest-rs/nextest/issues/1493 is fixed so we can upgrade the nextest that contains that patch.


fix: primary button color is switched to UNDP blue (is-link)

Thank you for submitting a pull request!
Description
fixes #2799
@balagurova I tried to paste some screenshots for pages which use new button color. Please review them
Particularly, I would like to know from you about the following points

what about secondary color?
color of some toggle buttons (access level switch, card/list biew switch, etc)
dialog's buttons

Home page

Data page

Default style edit page

Dataset edit page

Data upload

Map page

setting page

Type of Pull Request

[ ] Adding a feature
[x] Fixing a bug
[ ] Maintaining documents
[ ] Adding tests
[ ] Others ()

Verify the followings

[x] Code is up-to-date with the develop branch
[x] No build errors after pnpm build
[x] No lint errors after pnpm lint
[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check
[x] Make sure all the existing features working well

Changesets

[ ] If your PR makes a change under packages folder that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

Refer to CONTRIBUTING.MD for more information.
┆Issue is synchronized with this Wrike task by Unito

we decided not to change all buttons primary color to blue


labhub: Add usability with sub-groups

Closes https://github.com/coala/corobo/issues/202
Reviewers Checklist

[ ] Appropriate logging is done.
[ ] Appropriate error responses.
[ ] Handle every possible exception.
[ ] Make sure there is a docstring in the command functions. Hint: Lookout for
botcmd and re_botcmd decorators.
[ ] See that 100% coverage is there.
[ ] See to it that mocking is not done where it is not necessary.

ack ebf1554339c787769ec679eded8a6bf81adbf89a

@rultor merge

@rultor merge

@meetmangukiya OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@meetmangukiya Done! FYI, the full log is here (took me 2min)


python311Packages.aiortm: 0.6.4 -> 0.8.5

Diff: https://github.com/MartinHjelmare/aiortm/compare/refs/tags/v0.6.4...v0.8.5
Changelog: https://github.com/MartinHjelmare/aiortm/blob/v0.8.5/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 270083 run on x86_64-linux 1

4 packages built:

python310Packages.aiortm
python310Packages.aiortm.dist
python311Packages.aiortm
python311Packages.aiortm.dist


[Tizen] Rebase Murphy support to M41.

Rebase Murphy support to M41 and fix build failures.
BUG=XWALK-3418

@rakuco

Can you resubmit so we can check if the IVI slave is back to normal? Also, does this patch depend on rolling DEPS.xwalk first or is it independent from the patch in chromium-crosswalk?

Rolled DEPS.xwalk here since the patch in chromium-crosswalk and this one is dependent on each other.

The build was broken and I've fixed it in #2848. Can you please resubmit one last time so I can finally merge the PR?


Duplicate feeds after reloading

Newsboat version (copy the output of newsboat -v or the first line of git show):
newsboat 2.19.0 - https://newsboat.org/
Copyright (C) 2006-2015 Andreas Krennmair
Copyright (C) 2015-2020 Alexander Batischev
Copyright (C) 2006-2017 Newsbeuter contributors
Copyright (C) 2017-2020 Newsboat contributors

Newsboat is free software licensed under the MIT License. (Type `newsboat -vv' to see the full text.)
It bundles JSON for Modern C++ library, licensed under the MIT License: https://github.com/nlohmann/json
newsboat 2.19.0
System: Linux 5.5.11-arch1-1 (x86_64)
Compiler: g++ 9.3.0
ncurses: ncurses 6.2.20200212 (compiled with 6.2)
libcurl: libcurl/7.69.1 OpenSSL/1.1.1e zlib/1.2.11 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh2/1.9.0 nghttp2/1.39.2 (compiled with 7.69.1)
SQLite: 3.31.1 (compiled with 3.31.1)
libxml2: compiled with 2.9.10

Config file (copy from ~/.newsboat/config or ~/.config/newsboat/config):
external-url-viewer "urlview"

# key bindings
bind-key j down
bind-key k up
bind-key j next articlelist
bind-key k prev articlelist
bind-key J next-feed articlelist
bind-key K prev-feed articlelist
bind-key G end
bind-key g home
bind-key a toggle-article-read
bind-key n next-unread
bind-key N prev-unread
bind-key U show-urls

# Open in browsers
browser brave
macro , open-in-browser
macro v set browser "i3 exec mpv"; open-in-browser ; set browser w3m

Steps to reproduce the issue:

Reload feed of a source

Feeds got duplicated

Tried other RSS reader like QuiteRSS and it didn't happen
This looks similar to #256 but didn't happen with other reader so I don't think the problem lies in the source. Do you have any idea?

Other info you think is relevant:
RSS source: https://vtv.vn/trong-nuoc.rss

I believe this is an issue with the source.

GUIDs uniquely identify articlces. New GUID means new article. I guess QuiteRSS implements heuristics to smooth things out, but ultimately this is the publisher's fault. Please pester the site administrator to fix their RSS generator. They already provide unique <link>—they can simply use it as a GUID, too. If they refuse, you can implement that on your end with filter:.

Thanks for a nice report though!


Enable/disable  wasm gov message types

Summary
See #162 for context
When compiling a chain, you should be able to enable None of these, All of these, or Some of these. By default, none of the proposal types are enabled. There should be one function to easily register all proposals with the application. And there should be another function (or functions) that can be used to selectively enable some of these. The last 3 - MigrateContract, UpdateAdmin, ClearAdmin can all be enabled/disabled as a block, as giving access to governance to do one is close to giving access to all.

Add in code doc: https://github.com/CosmWasm/wasmd/pull/173#discussion_r450856050

It actually looks quite good now, they way you set this in app.go.
You can add another docstring somewhere if you wish, or just close this issue

I have added some inline doc. One note on the defaults: currently all wasm proposal types are enabled. The opposite was defined in the original issue. Should we keep them all enabled? That would make it easier with the CLI where all types are enabled, too.

Hmm... what I want to here is make two binaries - wasmd and wasmgovd which are 99% the same except for all government votes disabled in wasmd (permissionless network) and all enabled in wasmgovd (permissioned for cosmos hub proposal).
Ideally there should be minimal code copy and we can even pass in this set to app.go so we can use the same app package, just change the setup in main.
Maybe we can close this issue (which is done in the module level) and add a new one for the two binaries (on the cli/binary level)

In this case we could just pass the supported types to the NewWasmApp constructor function and we are done here.


Fix actions syntax error.

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Switching to other levels not functional using menu in release

What?
When in the final version of the product, one might one switch between OpenWorld and KettleDemo level. Seemingly only an issue in the executable.

Resolved
Must select all levels in the packaging, only kettle and openworld is included.


change default tls value type in values.yaml

Fixes #193

I believe the fixes are similar to #7, if additional work needs to be done to get this merged and clear the warning, I would love to do so


ModuleNotFoundError: No module named 'keyring.util.escape

I installed minidcos with
pip3 install --upgrade<EMAIL_ADDRESS>on a clean Ubuntu 18.04 in Virtualbox.
When I run minidcos docker doctor the output starts with
Error initializing plugin EntryPoint('Windows (alt)', 'keyrings.alt.Windows', None, Distribution('keyrings.alt', '3.0')).
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/keyring/backend.py", line 190, in _load_plugins
    init_func = ep.load()
  File "/usr/local/lib/python3.6/dist-packages/entrypoints.py", line 77, in load
    mod = import_module(self.module_name)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/keyrings/alt/Windows.py", line 9, in <module>
    from . import file_base
  File "/usr/lib/python3/dist-packages/keyrings/alt/file_base.py", line 13, in <module>
    from keyring.util.escape import escape as escape_for_ini
ModuleNotFoundError: No module named 'keyring.util.escape'
Error initializing plugin EntryPoint('file', 'keyrings.alt.file', None, Distribution('keyrings.alt', '3.0')).
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/keyring/backend.py", line 190, in _load_plugins
    init_func = ep.load()
  File "/usr/local/lib/python3.6/dist-packages/entrypoints.py", line 77, in load
    mod = import_module(self.module_name)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/keyrings/alt/file.py", line 11, in <module>
    from keyring.util.escape import escape as escape_for_ini
ModuleNotFoundError: No module named 'keyring.util.escape'
Error initializing plugin EntryPoint('pyfs', 'keyrings.alt.pyfs', None, Distribution('keyrings.alt', '3.0')).
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/keyring/backend.py", line 190, in _load_plugins
    init_func = ep.load()
  File "/usr/local/lib/python3.6/dist-packages/entrypoints.py", line 77, in load
    mod = import_module(self.module_name)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/keyrings/alt/pyfs.py", line 8, in <module>
    from keyring.util.escape import escape as escape_for_ini
ModuleNotFoundError: No module named 'keyring.util.escape'

After that, the the checks appear to work normally.

I'm surprised to see Windows in the output given the Ubuntu host.

@all
Hello all. I am also facing this issue; concerning the last two error lines:
from keyring.util.escape import escape as escape_for_ini
ModuleNotFoundError: No module named 'keyring.util.escape'
I tried to install minidcos with pip3 AND pip; but did not find out which one may be the most comfortable one and also get this error when executing ' minidcos docker doctor'.
Also when creating a cluster i get some error messages; but donno where they come from:
(miniDCOS) ________________________________________________________________________________
| ~/miniDCOS @ 9StrEtcH9 (debian)
| => minidcos docker create ./dcos_generate_config.sh --masters 3 --agents 11 --public-agents 3 --wait-for-dcos
Error initializing plugin EntryPoint('Gnome', 'keyrings.alt.Gnome', None, Distribution('keyrings.alt', '1.3')).
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/keyring/backend.py", line 190, in _load_plugins
init_func = ep.load()
File "/usr/local/lib/python3.5/dist-packages/entrypoints.py", line 77, in load
mod = import_module(self.module_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 673, in exec_module
File "", line 222, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/keyrings/alt/Gnome.py", line 11, in
from keyring.py27compat import unicode_str
ImportError: cannot import name 'unicode_str'
Error initializing plugin EntryPoint('Windows (alt)', 'keyrings.alt.Windows', None, Distribution('keyrings.alt', '1.3')).
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/keyring/backend.py", line 190, in _load_plugins
init_func = ep.load()
File "/usr/local/lib/python3.5/dist-packages/entrypoints.py", line 77, in load
mod = import_module(self.module_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 673, in exec_module
File "", line 222, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/keyrings/alt/Windows.py", line 9, in
from . import file_base
File "/usr/lib/python3/dist-packages/keyrings/alt/file_base.py", line 12, in
from keyring.util.escape import escape as escape_for_ini
ImportError: No module named 'keyring.util.escape'
Error initializing plugin EntryPoint('file', 'keyrings.alt.file', None, Distribution('keyrings.alt', '1.3')).
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/keyring/backend.py", line 190, in _load_plugins
init_func = ep.load()
File "/usr/local/lib/python3.5/dist-packages/entrypoints.py", line 77, in load
mod = import_module(self.module_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 673, in exec_module
File "", line 222, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/keyrings/alt/file.py", line 12, in
from keyring.util.escape import escape as escape_for_ini
ImportError: No module named 'keyring.util.escape'
Error initializing plugin EntryPoint('kwallet', 'keyrings.alt.kwallet', None, Distribution('keyrings.alt', '1.3')).
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/keyring/backend.py", line 190, in _load_plugins
init_func = ep.load()
File "/usr/local/lib/python3.5/dist-packages/entrypoints.py", line 77, in load
mod = import_module(self.module_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 673, in exec_module
File "", line 222, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/keyrings/alt/kwallet.py", line 6, in
from keyring.py27compat import unicode_str
ImportError: cannot import name 'unicode_str'
Error initializing plugin EntryPoint('pyfs', 'keyrings.alt.pyfs', None, Distribution('keyrings.alt', '1.3')).
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/keyring/backend.py", line 190, in _load_plugins
init_func = ep.load()
File "/usr/local/lib/python3.5/dist-packages/entrypoints.py", line 77, in load
mod = import_module(self.module_name)
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 673, in exec_module
File "", line 222, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/keyrings/alt/pyfs.py", line 8, in
from keyring.util.escape import escape as escape_for_ini
ImportError: No module named 'keyring.util.escape'
��� Determining DC/OS variant
��� Creating cluster
��� Installing DC/OS
HINT: I am in a virtualenv environment.
May be someone has a clue on this?
Regards,
Roger

This is frustrating.
msrestazure is a dependency of DC/OS Launch, which we vendor.
Let's take a look a the chain of events which lead to us installing a particular, old version of keychain which has this issue:
https://github.com/dcos/dcos-e2e/blob/feb3f8869597187da1d69b75294a58d8c29a44c3/indirect-requirements.txt#L4-L17
My ideal is to remove the dependency on DC/OS Launch and switch to Terraform, as per https://jira.mesosphere.com/browse/DCOS_OSS-4431.

I have reproduced this with:
$ docker run -it ubuntu bash

export LC_ALL=C.UTF-8
export LANG=C.UTF-8

apt update -y && \
apt install -y software-properties-common && \
apt upgrade -y python-apt && \
add-apt-repository -y ppa:deadsnakes/ppa && \
apt update -y && \
apt upgrade -y gcc python3-dev python3.6-dev libffi-dev libssl-dev git python3-pip && \
pip3 install --upgrade git+https://github.com/dcos/dcos-e2e.git && \

The error shows here:
minidcos --help


Reuse official test suite

We should be able to reuse this: https://raw.githubusercontent.com/ethereum/tests/develop/RLPTests/rlptest.json

I think we're fine for what we have. Considering how big effort was that in clarity to support TransactionTests I think we won't benefit much. Also, a lot of tests on Clarity side also touches RLP serialization/deserializations.
Those official tests wouldn't catch problems that could be found in static typed languages, so we'd have to build up our tests anyway. For example: is it easy to convert serde_json::Value into a RLP? Would it work well with different serializer?


fix(config): add Alarm Mapping to Yale YRD220, YRL210, and YRL220

I have confirmed that all 3 of these locks share the exact Alarm Mappings of previous Yale Zwave locks of the 100 series. I used the existing templates.
fixes: https://github.com/zwave-js/node-zwave-js/issues/2826

I'll let @vondruska verify too and then merge.

The alarm mapping for my lock is working for me @AlCalzone. And thanks @disforw for making the PR happen!

@AlCalzone , I mentioned this problem with my lock in another thread here and you asked me to post an issue in the Home Assistant forum but before doing so I searched there for similar issues. That search brought me right back here, following vondruska's trail. I don't really see the point of posting an identical problem over there since I'm sure they will just send me right back, but I will do so if you insist.
Ultimately, it seems that my Yale lock (YRD256) does not have correct alarm mappings. In ZWave2mqtt it is bunched together as YRD226 / YRC226 / YRC246 / YRD256 / YRC256 / YRD446. I believe those improper mappings cause my binary_sensor.assure.touchscreen_deadbolt_current_status to remain completely dormant since I installed weeks ago.
Can anything be done?  Thanks

Can you share the correct mappings as defined in your user manual along with the product IDs for your lock?

The manual for the "Yale Assure Lock SL Key Free Touchscreen Deadbolt" (YRD256) makes no mention of those mappings (found here), but I did find some information on the "Yale Z Plus Module" (Model: 2-YRMZW US) that it uses. The association table can be found here and on the following page.
Is that useful at all?  Thanks

The configuration table is on page 10 of the second link you provided, but it matches this link I found. Here
Please provide your product ID from the zwave-js GUI.

[14-114-0-productId] Product ID
1536
Is that what you're looking for?

Is that what you're looking for?

Product ID, Product type and firmware version are necessary to identify the device.

Sorry. Let's try this again:
Manufacturer ID: 297
Product type: 32770
Product ID: 1536
Unfortunately, under firmware it just says, "undefined". The closest thing I can find is "Z-Wave Plus: Version 1". Even the chart of my devices in ZWave2mqtt is only showing a "v" under FW.

I don't think the mappings are incorrect. They are the same across most Yale devices, but many of the non-standard ones have no corresponding notification value and stay as alarm level and type.
I've asked the HA devs to take a look here, since I have no clue what current_status is and how it is supposed to be updated.

Much appreciated. If there's anything I can do to help with testing please don't hesitate to ask.

So, from what I've understood:
current_status doesn't exist, unless you renamed it. The most similar values are either latchStatus, boltStatus, or doorStatus, which are known not to work on some locks.
The reason is that those are exposed via the Door Lock CC, but these locks don't use the Door Lock CC for reporting and send Locked/Unlocked notifications instead, which don't convey the information which of the above values need to be updated.
You should have some other entity though which correctly reflects the lock status.

That's super weird. I did rename the entities associated to the lock, but only to remove the brand name since I don't like my interface cluttered with advertising. So "binary_sensor.assure_touchscreen_deadbolt_current_status" became "binary_sensor.touchscreen_deadbolt_current_status" -- not much of a change since I didn't want to tamper with things too much in case I broke something. I hope that's not the case!
I don't see any other entity names that might indicate whether the lock is engaged or not, the closest being "sensor.assure_touchscreen_deadbolt_access_control_lock_state", but the reading that gives is "idle", which doesn't really intuitively seem like a lock state. The only way I can tell if it's locked at the moment is with the entity "lock.touchscreen_deadbolt", which changes from "lock" to "unlock" on the lovelace card, depending on it's state.

access_control_lock_state

That (currently) tells you if the lock is jammed or not (idle).

Re current_status: there are three lock-related labels that contain "current status":
"The current status of the latch" -> latchStatus
"The current status of the bolt" -> boltStatus
"The current status of the door" -> doorStatus
I'm not sure what HA makes of these or if it just picks one.

The only way I can tell if it's locked at the moment is with the entity "lock.touchscreen_deadbolt"

Ok i think this is the one you need to look at. There might also be another one that refers to the Door Lock CC's currentMode property. But again, not sure how this translates to HA.

I have one control, "lock.touchscreen_deadbolt", the following sensors available in Home Assistant:
sensor.touchscreen_deadbolt_access_control_lock_state   (= idle)
binary_sensor.touchscreen_deadbolt_current_status   (= open)
binary_sensor.touchscreen_deadbolt_power_management_power_applied   (=off)
binary_sensor.touchscreen_deadbolt_access_control_keypad_temporarily_disabled   (=off)
sensor.touchscreen_deadbolt_access_control_keypad_state
sensor.touchscreen_deadbolt_alarmlevel
sensor.touchscreen_deadbolt_alarmtype
sensor.touchscreen_deadbolt_power_management_battery_maintenance_status
sensor.touchscreen_deadbolt_power_management_power_status
as well as the following diagnostics:
binary_sensor.touchscreen_deadbolt_access_control_lock_jammed   (=OK)
sensor.touchscreen_deadbolt_battery_level   (=97%)
binary_sensor.touchscreen_deadbolt_low_battery_level   (=Normal)
sensor.touchscreen_deadbolt_node_status   (=alive)
binary_sensor.touchscreen_deadbolt_power_management_replace_battery_now    (= Normal)
binary_sensor.touchscreen_deadbolt_power_management_replace_battery_soon   (= Normal)
It seems that I'm out of luck, though in ZWave2Mqtt under Lock V2, I see a few values of interest:
"[14-98-0-latchStatus] The current status of the latch"   (= open),
"[14-98-0-boltStatus] The current status of the bolt"   (= locked),   and
"[14-98-0-doorStatus] The current status of the door"   (= open)
I have no idea how these could contradict each other.

Is there no lock entity somewhere? These are all sensors.

I have one control, "lock.touchscreen_deadbolt"

Maybe I'm misunderstanding the issue, but what else are you looking for?

I was looking for a sensor that I could use to change an icon based on the state of the lock so that I could confirm that the door is locked (or unlocked) at a glance. Also something to use in conditionals. I'm pretty new to Home Assistant, so maybe I'm looking at this all wrong, but isn't lock.touchscreen.deadbolt just a service that I can call in order to toggle its state?
Thanks

The lock.touchscreen_deadbolt entity's status will state locked or unlocked and the icon changes on it's own.
There is no reason to do any conditionals.
Example:

Lock is locked and I can unlock it.

Lock is unlocked and I can now lock it.

Thanks,
I am planning on changing an icon on the homescreen of my Android phone.
I have several reasons for conditionals. There are many cases where I would like to work the lock state into an automation, for example alerting me if the lock has been open for an extended period of time, or notifying me that the front door is unlocked if I try to initiate my bedtime routine. I don't really use the Home Assistant dashboard much, if I can avoid it.

You'll use the lock.touchscreen_deadbolt state for this. If you need help with that feel free to post on the Home Assistant forums or join the discord chat.

Got it.  Thanks!!


 I checked for coordinates and saw my ship was at the coordinates below. (You can't teleport to them because they are so far away)
http://tinyurl.com/y3csf9bb
debug-1.log.gz
latest.log
debug.log
2019-07-21-5.log.gz

http://tinyurl.com/y3ueyzwn
Another ship on the list is also in the ether

http://tinyurl.com/y6tv6nm4
So this time I could actually tp to the ship, but coords were under the world and the ship is not there

note: this happened on a 24/7 running server and the ship disappeared during a period of several hours? difficult to reproduce issue.

http://tinyurl.com/y33q93uf
Another ship under the world but within teleport range

Note: For ship last mentioned, I simply landed it and jumped off and started chopping trees and fighting mobs, then died and respawned, used /home to get to a location near death point and traveled back to where the ship previously was and it was gone.

http://tinyurl.com/y3oy39vz
Another ship in the ether

I had this happen to me too, don't know how to check the coordinates like that.

[12:18:41] [VW World Thread 0/INFO] [STDERR]: [valkyrienwarfare.mod.common.physics.collision.WorldPhysicsCollider:updatePotentialCollisionCache:487]: VW Cached Surrounding Chunks was null! This is going to cause catastophric terrible events!!
This makes me think that the ship collision with the world broke. Can you verify that the ship didn't fall below the world?

usually when chunk unloaded ships disappear.


Optimized assembly acceleration

Though we should definitely maintain a baseline profile which is pure Rust, it would be nice to be able to leverage optimized assembly implementations, and ideally formally verified ones which have been mechanically extracted from upstream sources.
One possible source of such assembly is the s2n-bignum project: https://github.com/awslabs/s2n-bignum

I wonder how it compares to Jasmin's https://github.com/haslab/libjbn

As a data point, the graviola crate has adopted assembly from s2n-bignum and seems to perform quite well: https://crates.io/crates/graviola


TabPanes should be pages

For clearness and better handling, especially in context of routing, TabPanes should be pages, that could be triggered by the route directly.
Convert the apps- and deployments-tabpane in Marathon to pages.
https://github.com/mesosphere/marathon/blob/master/src/main/resources/assets/js/components/Marathon.jsx#L464
Also the tabpanes for the tasks and configuration in the AppPageComponent should sort of a subpage.
https://github.com/mesosphere/marathon/blob/master/src/main/resources/assets/js/components/AppPageComponent.jsx#L154

@aldipower is that still open?

Due to a lot of refactorings, especially by implementing the react router, this task is kind of obsolete and only would produce more code overhead instead of simplicity.


Fix bug 17175

Fix bug reported at https://github.com/tensorflow/tensorflow/issues/17175

I signed it!

Used incorrect email in earlier commit. Fixed it.

Any idea why the "Ubuntu CC" check takes so long?

@ebrevdo Any idea why the tests take so long?
For the first commit (https://github.com/tensorflow/tensorflow/pull/17283/commits/0a4bad1a79e60718dc8620e1213adaa4bcc9d0fe) it finished in a few hours with all the 15 tests. Now it seems stuck with the Ubuntu CC test

Should improve by tomorrow.
On Fri, Mar 2, 2018, 8:09 PM Panos Ipeirotis<EMAIL_ADDRESS>wrote:

@ebrevdo https://github.com/ebrevdo Any idea why the tests take so long?
For the first commit (0a4bad1
https://github.com/tensorflow/tensorflow/commit/0a4bad1a79e60718dc8620e1213adaa4bcc9d0fe)
it finished in a few hours with all the 15 tests. Now it seems stuck with
the Ubuntu CC test
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/17283#issuecomment-370115732,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtim1kWrTvfeGx-dzsIVmJMSlKXO-t9ks5tahdfgaJpZM4ST7E6
.

@ebrevdo Can we get a forced run of the tests?

Re @ipeirotis running tests.


Update the documentation for now.sh deployment

Instead of building the app locally and deploying the static files to now.sh from the build folder, now-build and now-start scripts can be used to build and serve single-page applications remotely.
GENERATE_SOURCEMAP needs to be set to false so that the build process doesn't fail.

Why does the build fail with GENERATE_SOURCEMAP? We don't want to recommend this as a default.

Without GENERATE_SOURCEMAP=false I get the following error:

react-scripts build
Creating an optimized production build...
The build failed because the process exited too early. This probably means the system ran out of memory or someone called kill -9 on the process.

The source maps are also too big for now's 1MB file size limit, so they have to be removed if you try to run the production build locally before uploading it.

Would it be acceptable to remove the "now-build" script from the main part of the documentation, and add it as an "if the build fails, add this script" note?

I don't think we should recommend building on now; this should still be a local process due to the constraints imposed by now.

We can keep this PR open in case they bump the default memory available.

In that case, it would still be worth adding GENERATE_SOURCEMAPS = false to the documentation as a note, because without it the local build will usually generate a sourcemap >1MB, which will prevent the static files from being uploaded.

now imposes space/size restrictions on the files you upload for static hosting?
In that case, we should probably just remove the recommendation all together.

Ah, I see the max file size is just 1MB.
In this case, I'm not sure if we should just remove the recommendation to use Now or add a note that it doesn't scale for larger websites unless if you subscribe to a premium plan.

Closing as in the end a static deployment is preferable, as inactive static deployments don't get put to sleep.


If I use LibraryObject length of less than four,the page will missing

I have same problem :((((

If I'm not mistaken it requires a minimum of 4 items. 3 items get displayed at a time and it requires the fourth one to continue the cycling of images. At least one item has to be hidden.

If I'm not mistaken it requires a minimum of 4 items. 3 items get displayed at a time and it requires the fourth one to continue the cycling of images. At least one item has to be hidden.

I have same problem,3 or 4 items the page will missing

My solution is double your items  when item's length less than 3 or 4.
It works to me.


Fixed the size of text area during editing note description

fixed #164

@nitishsaini706 Could you attach a screenshot or a video which would depict the changes you made?

@Tess-Vanta
Sure, should I attach here in comment

Yes here

Not able to add height of text area so hard coded height to 5-6 rows

TO this


Fix main property in bower.json

Pointing to non-existent file causes file to not be included main-bower-files and similar automation.

Thanks for your contribution. Will release ASAP.

tag 1.0.2 created.


nixos/udev: Fix grep: warning: stray \ before /

Description of changes
This reverts commit dbe2325603420a89aa030994138bb54167fab81d, which was mistaken: / matches exactly the same things matched by \/ but without the warning.
Fixes #316561.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 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.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4280


Remove CommonJS support?

Do we really care about supporting CommonJS? I think we should still build for esm, so none typescript users can use the library.
If we do remove CommonJS support, then we can remove quite a bit of code from the repo.

Isn't CommonJS old/redundant anyway?
I can't remember.
Why did we support it in the first place?


Large uploads fail in web client

Description
I'm trying to upload large release binaries (~300MB) to a tagged release Gitea.
The following curl request works and attaches the upload to the release as expected:
curl -vv -X POST -H "Authorization: token $key" "https://$url/api/v1/repos/user/repository/releases/99/assets?name=linux.zip" -F<EMAIL_ADDRESS>
However, uploading the same attachment through the web interface will hang when the upload progress bar fills up. In my case, Gitea is running in a Docker container behind nginx, so eventually nginx times out. Gitea reports the nginx response as an error and the upload fails to be attached to the release.
I tried to test what would happen if I did the same upload on try.gitea.io but it appears to be down at the moment. I'll try to update this issue later when I'm able to test it there. Unfortunately, I couldn't figure out how to run my Gitea without nginx, since logging in doesn't seem to work.
I found an issue that might be related (#11906), but the fix for it appears to still exist.
Gitea Version
1.21.11
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/exodrifter/2ee2aee15835ea0e4e8f7e007c89b0af
Screenshots
Here's what the web interface looks like when the upload fails:

The error in plaintext:
 <title>504 Gateway Time-out</title>
504 Gateway Time-out

nginx

Git Version
2.34.1
Operating System
Ubuntu 22.04.4 LTS
How are you running Gitea?
We are running Gitea from docker, which is behind an nginx reverse proxy which is being run in a SWAG container.
Database
PostgreSQL

What is your nginx setting with respect to payload?

Check your client_max_body_size setting in nginx.

client_max_body_size is 0, which I believe disables checking of the client request body size.

There are some guesses for this problem:

The uploading on nginx side timeouts (eg: improper timeout setting, laggy network, browser proxy, etc)
The uploading on Gitea side timeouts

For the first case, you could try to double-check your config/environment.
For the second case, could you provide a reproducible setup with detailed steps? eg: a docker compose file, and the steps to reproduce. If it could be reproduced on a developer's machine, then it could be fixed soon.

I am planning on putting aside some time in two weeks to see if I can create a reproducible setup.

I was able to test this locally with a docker installation on 1.21.11 as well as on the demo site (which is on 1.23.0+dev-197-gab1948d4a3), and was unable to reproduce it.
I mistakenly assumed that if it worked with cURL that it would be a problem with Gitea, but it is clear to me now that is an issue with how the forward proxy is configured.


[Feature] Refresh and Access Tokens Implementation

Description
Implement Refresh and Access Tokens mechanism to improve security and user experience.
Create logic for token generation, validation (middleware), and renewal of Access Token using Refresh Tokens.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I have read the Contributing Guidelines
[X] I have read the Code Of Conduct
[X] I joined onboarding group for knowledge flow and direct conversation and support from admins  Curious Developers Community - Curious Connect
[X] The changes don't break the code
[X] Please attach the screenshots and video of the development work once it is done
[X] If you need any help please join the default  (Google Meet Link)

@ujjwalagrawal-1 yes you can start working on it

I also want to work in this

I also want to work in this

Can I also add logout route with that

@ujjwalagrawal-1 are you working on it?
if you have any questions regarding this issue you can connect with me on our Curious Developers Community - GSSoC  group
or Read this Article or watch this video , it will help you to understand what is Refresh and Access Token and why they are used.

@CDCNaman please Assign it to any Other


Fix routerlicious timeouts in compression related tests

The timeouts for these tests were being caused by 2 things:

Large messages being sent
grouped batching being enable by default, thus breaking the logic in the tests that looks for empty messages

I reduced the size of messages being sent and their respective configs, as well as fixing the logic that tries to force a reconnect based on messages sent/received.
AB#7969
AB#7944

This PR is copied over from @kian-thompson 's PR to be able to merge while he is OOF
https://github.com/microsoft/FluidFramework/pull/21271/files


Add GRPC Node Driver

I have a first draft of the GRPC service definition when we're ready for it.

See also #95

I'll close this issue as a dup and use the previous one (#95).


npm test fails with "Repository ado-extension-test-nuget-remote does not exist"

Describe the bug
I'm trying to run the tests locally, but npm test fails:
  JFrog Artifactory Extension Tests
    1) "before all" hook

  0 passing (2s)
  1 failing

  1) JFrog Artifactory Extension Tests
       "before all" hook:
     Error: Server responded to http://localhost:8081/artifactory/api/repositories/ado-extension-test-nuget-virtual-1599733507 with status code 400:
{
  "errors" : [ {
    "status" : 400,
    "message" : "Repository ado-extension-test-nuget-remote does not exist\n"
  } ]
}
      at Response.getBody (node_modules/http-response-object/lib/index.js:41:23)
      at createRepo (testUtils.js:289:101)
      at createTestRepositories (testUtils.js:166:5)
      at Object.initTests (testUtils.js:98:5)
      at Context.before (tests.js:24:19)

To Reproduce
Clone the repo, set the ADO_ environment variables properly and run npm test as described in the readme.
Expected behavior
I expected the tests to pass.
Versions

Artifactory Azure DevOps extension version: 1.10.2 (based on the Git tag)
Agent operating system: Ubuntu 20.04
JFrog Artifactory version: 7.7.3

Additional context
I installed Artifactory like this:
docker run --name artifactory -v ${JFROG_HOME}/artifactory/var/:/var/opt/jfrog/artifactory -d -p 8081:8081 -p 8082:8082 docker.bintray.io/jfrog/artifactory-pro:latest

I should add that export ADO_ARTIFACTORY_SKIP_TESTS=maven,gradle,npm,go,nuget,dotnet,conan,docker didn't help, and that the tests passed (with said value for ADO_ARTIFACTORY_SKIP_TESTS) once I created ado-extension-test-nuget-remote manually.

Hi @SimonAlling ,
Thanks for reporting this issue.
The tests suite couldn't create a remote nuget repository due to RTFACT-10628 and RTFACT-21536. Since these issues are now resolved, we should definitely add the repository creation to the tests init.
Thanks!

A NuGet remote repository will now be created by the tests suite.
Thanks @SimonAlling


Support multiple directories for backup in neo4j-admin backup helm chart

The current neo4j-admin helm chart does not work when bucketName has multiple sub-directories.

this is implemented for both v5 and v4.4
https://github.com/neo4j/helm-charts/pull/260
https://github.com/neo4j/helm-charts/pull/259
Will be of the next upcoming release


Custom scalars and mappings

Hi, would you be open to a PR allowing custom scalars to be added to the schema, or the ability to alter the (currently private) mappings?

Added #5


not working on iphone - safari

the pre cache stuff is not being saved , so it just doesnt opens even without internet

I think it simply because sw is not supported on safari.

This is the case indeed.
https://jakearchibald.github.io/isserviceworkerready/


update(content): add Display attribute to plugin post

What type of PR is this?
/kind content
Any specific area of the project related to this PR?
/area blog
What this PR does / why we need it:
The Falco Bridge plugin of another tool is using the 'Display' value to have a name for the field. => Adding 'Display' to all fields so that the example code can be used as a blueprint which is usable in this other tool.
Related falcosecurity/plugins#463

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

2cba39d update(content): add Display attribute to plugin post

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

Welcome @uhei! It looks like this is your first PR to falcosecurity/falco-website 🎉

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: uhei
Once this PR has been reviewed and has the lgtm label, please assign vjjmiras for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


my_git_prompt:12: command not found: current_branch

After last update started having my_git_prompt:12: command not found: current_branch.
Seems mortalscumbag theme is at fault here as it requires git in plugins which I did not have.
Adding git to plugins=(rake-fast bundler git) in ~/.zshrc fixed the issue.
Looks like got introduced by #4364

Guess I can fix and make PR for this myself.


Fix npm security audit errors. Use rollup instead of gobble

Fix npm security warnings. Due to minimatch and gobble.
Upgrade npm packages
Use rollup over gobble

@Rich-Harris Thanks for an awesome library. Please push a npm release if everything looks ok to you

@Rich-Harris Fixed npm security audit errors. Can you please take a look.


Event Handlers - Support auto preventDefault, stopPropagation and stopImmediatePropagation

Provide a way to auto call preventDefault, stopPropagation and stopImmediatePropagation in the event handler
I am currently thinking of:
<button .click="clickHandler:psi"></button>

p - preventDefault
s - stopPropagation
i - stopImmediatePropagation
p, s and i are all optional and can be placed in any order

Fixed in version 0.6.0


Fix license info.

This may be a bit farther than we want to go...but it is thorough!
The changes here acheive full complaince with https://reuse.software/
from Free Software Foundation Europe. It should also result in better
and more accurate per-file license metadata in systems like
https://clearlydefined.io/
We don't have to merge all of this, but I wanted to post it on this
simple repo to gather feedback on the approach.

@JSAssassin @TallTed this is a fix for #27. Let me know if you think it's too much (especially wrt to the .license files).
@plehegar this is a simple test suite repo that can stand in for the others as we discuss how to properly express copyright and license claims for W3C repos. No need to review this heavily, but I figured sharing a specific example might be helpful for context.

@BigBlueHat Appreciate the fix! I think this looks good, though I'd defer to @TallTed  since I don't know much about license requirements within the w3c org.

@BigBlueHat Just noticed, year 2023 will have to be updated to 2024 in all places. Thanks!

2023 will have to be updated to 2024

Or possibly to a range, starting from the actual first year of publication, and ending (for now) with 2024 ("to present" is not a valid copyright value).

Thanks, @TallTed. Running reuse lint on this branch results in:
# SUMMARY

* Bad licenses: 0
* Deprecated licenses: 0
* Licenses without file extension: 0
* Missing licenses: 0
* Unused licenses: 0
* Used licenses: BSD-3-Clause
* Read errors: 0
* files with copyright information: 22 / 22
* files with license information: 22 / 22

Congratulations! Your project is compliant with version 3.0 of the REUSE Specification :-)

@plehegar please let me know if you have any thoughts/concerns.
@msporny this clarifies the license state for this repo. I plan to follow this pattern (and send PRs) for all the other test repos--assuming you feel this is mergable.
Thanks!

@plehegar one open question is whether copyright of test suites are held by their contributors or by the W3C. This PR does still keep that mixed...a bit. The LICENSE file now says the "World Wide Web Consortium" owns the copyright, but each file still retains the copyright of the original author.
Does membership in the W3C + contributing to a repository owned by the W3C result in a copyright transference (as it would at The Apache Software Foundation)? or is copyright per file retained by the individual contributors and the W3C claims copyright on the aggregate work?
What's here now is the best I could discern from the documentation I've been able to find.


How can I visualize the result of the test set?

Is there a visualization tool?

there is no file that works out of the box. But you can check this file to get an idea for how to use open3d to visualize detections https://github.com/tianweiy/CenterPoint/blob/master/tools/visual.py

there is no file that works out of the box. But you can check this file to get an idea for how to use open3d to visualize detections https://github.com/tianweiy/CenterPoint/blob/master/tools/visual.py

thx.btw, when the model predicts the velocity,the out_channel of head change from 7 to 9, what is the other output except velocity?

you can see the mapping here https://github.com/tianweiy/CenterPoint/blob/3c64610e78756990c8f67732749806a7a83caa5a/det3d/datasets/waymo/waymo_common.py#L71

sorry to disturb you tianwei, I am trying single_infernece_ros.py in your code, and when processing the point cloud data,I meet this error:
[ERROR] [1648210357.932211]: bad callback: <function rslidar_callback at 0x7fa72e739e18>
Traceback (most recent call last):
File "/opt/ros/noetic/lib/python3/dist-packages/rospy/topics.py", line 750, in _invoke_callback
cb(msg)
File "./tools/single_infernece_ros.py", line 202, in rslidar_callback
scores, dt_box_lidar, types = proc_1.run(np_p)
File "./tools/single_infernece_ros.py", line 112, in run
voxels, coords, num_points = self.voxel_generator.generate(self.points)
File "/home/puzek/ljy_projects/CenterPoint/det3d/core/input/voxel_generator.py", line 29, in generate
max_voxels,
File "/home/puzek/ljy_projects/CenterPoint/det3d/ops/point_cloud/point_cloud_ops.py", line 149, in points_to_voxel
num_points_per_voxel = np.zeros(shape=(max_voxels,), dtype=np.int32)
TypeError: 'list' object cannot be interpreted as an integer
there is my publish demo:
`import rospy
from std_msgs.msg import String
import scipy.io as scio
from sensor_msgs.msg import PointCloud2
from sensor_msgs.msg import PointField
import numpy as np
import time
from std_msgs.msg import Header
from sensor_msgs import point_cloud2
import numpy as np
from sensor_msgs.msg import PointField
from sensor_msgs.msg import PointCloud2
def talker():
pub = rospy.Publisher('lidar_top', PointCloud2, queue_size=1)
rospy.init_node('node', anonymous=True)
rate = rospy.Rate(10)
while not rospy.is_shutdown():
    path = './data/nuScenes/v1.0-test/samples/LIDAR_TOP/n008-2018-08-01-15-34-25-0400__LIDAR_TOP__1533152214547215.pcd.bin'

    bin_pcd = np.fromfile(path, dtype=np.float32)
    pointstest = bin_pcd.reshape((-1, 5))[:, 0:5]
    cloud_arr = np.asarray(pointstest, np.float32)
    print(cloud_arr.shape)

    points = np.zeros_like(cloud_arr)
    points[:, 0] = cloud_arr[:, 2]
    points[:, 1] = cloud_arr[:, 0]
    points[:, 2] = cloud_arr[:, 1]
    points[:, 3] = cloud_arr[:, 3]
    points[:, 4] = cloud_arr[:, 4]
    msg = PointCloud2()
    msg.header.stamp = rospy.Time().now()
    msg.header.frame_id = "Velodyne"

    if len(points.shape) == 3:
        msg.height = points.shape[1]
        msg.width = points.shape[0]
    else:
        msg.height = 1
        msg.width = len(points)

    msg.fields = [
        PointField('x', 0, PointField.FLOAT32, 1),
        PointField('y', 4, PointField.FLOAT32, 1),
        PointField('z', 8, PointField.FLOAT32, 1),
        PointField('r', 12, PointField.FLOAT32, 1),
        PointField('t', 16, PointField.FLOAT32, 1)]
    msg.is_bigendian = False
    msg.point_step = 20
    msg.row_step = msg.point_step * points.shape[0]
    msg.is_dense = False
    msg.data = np.asarray(points, np.float32).tostring()

    pub.publish(msg)
    print('send!')
    rate.sleep()

if name == 'main':
talker()
rospy.spin()

`

I solved this by changing the max_voxel_num in the config file from a list to a integer.
The model trained on nuscenes dataset doesn't work well for my data collected by 16 thread lidar,I am doubting which hyperparameter will be useful to enhance the performance?

there are a few reasons.
All nuscenes model uses ten sweep for training so it may internally rely heavily on the motion cues for detection, making them worse for detecting based on single frame input.
Nuscenes lidar may be quite different from yours.
You could probably try model trained on Waymo with this file https://github.com/tianweiy/CenterPoint/blob/master/tools/simple_inference_waymo.py (may need some tiny syntax fix to work with current repo)

Thanks, I will try it, did you provide pretrained models on Waymo?

btw,my test data is a continuous ploud cloud data stream record by 16 line Velodyne lidar in 10 mins,is this satisfy the "motion cues"?

Thanks, I will try it, did you provide pretrained models on Waymo?

send me an email (I can't publish it due to Waymo license)

btw,my test data is a continuous ploud cloud data stream record by 16 line Velodyne lidar in 10 mins,is this satisfy the "motion cues"?

it depends on how you use the data. You need to do multiple sweep aggregation (transform lidar to current frame) to form the ten sweep inputs. The frequency may also need to match exactly to work well  https://github.com/tianweiy/CenterPoint/issues/291
Maybe you should first try Waymo single frame model and  see

I will try Waymo first
I noticed multi_sweep_inference_ros.py subscribe odom topic, what does it refer to?

i don't know (if you check git history this file is authored by some other people and I don't know anything about ros lol

there is no file that works out of the box. But you can check this file to get an idea for how to use open3d to visualize detections https://github.com/tianweiy/CenterPoint/blob/master/tools/visual.py

hello, tianweiy, how can i generate the file that should be passed to visual.py, the file seems include points and detections, is these any script in this project i can use?


High memory usage because of unbound internal buffering

By default there is no limit to the internal buffering to the _q data Array. This means that if the stream input is faster than the stream output (mongodb), then the nodejs process will grow unbound in RAM.
With the following test I reached 8.6GB in ram:
# create a large file
$ dd if=/dev/zero of=zero.10GB bs=10M count=1024

var mongodb = require('mongodb');
var gridstream = require('gridfs-stream');
var fs = require('fs');

var filename = 'zero.10GB';

mongodb.MongoClient.connect('mongodb://localhost:27017/test', {}, function(err, db) {

  var start = process.hrtime();

  var gfs = gridstream(db, mongodb);
  var writestream = gfs.createWriteStream({
    filename: filename
  });
  fs.createReadStream(filename).pipe(writestream)
    .on('progress', function logProgress(position) {
      console.log('gridfs-stream write progress', position);
    })
    .once('close', function gfsDone() {

      var diff = process.hrtime(start),
          time = diff[0]*1e9+diff[1];
      console.log('gridfs-stream write complete for "%s", total time was %dns.',filename,time);

      db.close(function() {process.exit();});
    });
});

With option limit: 1 (no buffering at all, the opposite extreme value) the nodejs process never uses more than 310MB in RAM, CPU load is also much lower (40s vs 100s), and the global time is only 7% slower (470s vs 438s).
With option limit: 10 we use the same RAM and CPU load as with limit: 1, and are now only 2% slower than with no limit (447s vs 438s).
I don't think it's reasonable to have an unlimited default. It's probably never reasonable to have no limit on internal buffering: the nodejs Stream API already handles buffering issues itself (see Stream2 documentation) so there is no need to do all this.
A quick fix: set a sane default value for limit, like 10.
A cleaner fix: use Stream2 API (from node 0.10), use npm package readable-stream if you want to support older nodejs versions: just implement _write() (see http://nodejs.org/api/stream.html#stream_api_for_stream_implementors).

V1.0.0 is just released with node 0.10 streams thanks to @riaan53 .

The new version is promising, but there is still an unbound internal buffering issue:
When the connection is not open yet, unbound buffering is done here:
https://github.com/aheckmann/gridfs-stream/blob/048a033c6185b03c6cef92f14801fbca50d22522/lib/writestream.js#L127-L135
It should not call done() until the chunk has been written to gridfs, ie after the store open.

Hi @triccardi-systran ,
Would you recommend to remove the buffering before store is open all together then? It usually only buffers 2-3 chunks before the store opens but obviously can take longer depending on where your db is hosted - if the gridtore does not open a error will occur and then the store will be closed. Currently it will only buffer while waiting for the sotre to open then done() is only called when the chunk is written.

Hi @riaan53 ,
Yes I recommend to never buffer internally unless strictly required (for example MongoDB GridStore does some internal buffering to align writes to the fixed chunk size, in this case it is required).
Why? Because node Stream2 already handles buffering, and it does this correctly (this is tunable with highWaterMark Stream option), see http://nodejs.org/docs/v0.10.36/api/stream.html#stream_buffering
Doing again another unnecessary buffering will disable the Stream2 one, and if not properly done can create issues, like this one: unbound buffering.
I understand that in practice the buffering is limited because the _store open is fast, but we never know (for example tcp can take some time to establish the connection, because of failing hardware on the network path, or slow mongodb server...), and we gain nothing to do the buffering ourselves: Stream2 will already do it and we thus have the performance benefit from it.

Ok cool - it makes sense. I will remove the done() call before the store is opened so no buffering will take place.
Please share any other issues/suggestions that you find.

done should be stored and called back when _open finishes, not just ignored.

@triccardi-systran
I have made the change - can you please review the it at https://github.com/riaan53/gridfs-stream/blob/master/lib/writestream.js#L122 ?
Thanks!

@riaan53
This seems to work, but I think it's strange to keep the this._q: we should at most buffer one chunk (and store its related done callback).
The current code is confusing: there is a queue of chunks, but only one done callback, and by chance there is no desynchronization between them (the current gridfs-stream 1.0.0 does have a desynchro: the current done() may be called for a previous chunk, this will probably break the highWaterMark Stream2 buffering control), and the code still handles _q.length > 1 with recursive call to _write.
Also, having _write() called some times externally with arguments, and other times internally without arguments is also confusing (many indirect tests in the code to check in which mode we are ( if (chunk)).
What I would do:

in _write:
if not yet opened, store the whole arguments in a _delayedWrite member and just return.
else call _writeInternal with the same arguments, where _writeInternal would call _store.write with the chunk argument, and call done() argument when finished.
in _open completion:
if _delayedWrite is set, call _writeInternal with all arguments from _delayedWrite.

Why moving the real _store.write() into another function? to keep the usual conventions on who calls _write, because _write and how it's called is part of the Stream2 API.
No more queue, no more "buffering" vocabulary: we just delay the first write until we are ready to process it.
I haven't thought about the _destroying state; although I don't understand what is the usefulness of public method destroySoon: compared to destroy it just writes some more chunks: it is useless unless the _store.close() is called (it isn't), isn't it?

@triccardi-systran , it seem like a more elegant solution and will make more sense for someone to maintain later on as we dont need to queue/buffer anymore. Will give it a go tonight or tomorrow and work the _flush in as well that you mentioned in the other issue.
Yes destroySoon will just write some more data. When calling destroySoon it sets _destroying and after the write is done it will do a _store.close() in the gridsotre write callback. I dont know the exact use case for this but I kept it as I do not want to break the API.

Oh ok, I didn't see the _store.close() was called in all cases, including when destroying.
Since it's 1.0.0 we could break the API and remove destroySoon: IMO it has really no value: there is no control of how many more chunks would have been written to GridFS (and the behavior has already changed with our buffering removed).
Also, always closing the _store is good to avoid GridFS chunks leaks, but it seems strange to me to write something invalid (because it misses parts of the data) on GridFS, and store nowhere the fact that it's invalid.
Maybe we could store an additional flag in metadata saying the stream write has failed; or maybe we could instead remove the temporary chunks (it's what does Amazon AWS S3: the upload is cancelled on error, and temporary data is deleted.) It could be an option of the stream, since both usage seem legit.

Hi @triccardi-systran ,
I have made the changes as discussed above and in https://github.com/aheckmann/gridfs-stream/issues/63 . Its much cleaner and less error prone now which I like - thank you for the help I appreciate it.
Changes include:

Removed destroySoon
Inherit from FlushWritable and implemented _flush
Implemented _delayedWrite and _writeInternal
Removed all _q and buffers and updated comments

https://github.com/riaan53/gridfs-stream/blob/master/lib/writestream.js
Let me know what you think and if there are any other improvements or suggestions.
Thanks!
Regards,
Riaan

@riaan53 Reviewed and patched here: riaan53/gridfs-stream/pull/2

@triccardi-systran Thank you so much! See my comments there as well. You can do the PR directly to aheckmann.
Regards,
Riaan

@triccardi-systran I'ld be happy to merge in your changes if you would create a pull request.

@Reggino See #67


Unable to Create Docker Image

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/microservice-tutorial/docker-image
Operating System: windows

Using - Docker version 19.03.8, build afacb8b

See announcement- https://github.com/dotnet/announcements/issues/104
You're currently running on Windows 10 Fall Creators Update/Windows Server, version 1709 which no longer supported. Please upgrade your Windows OS to a newer version.


Add logic to sync ArgoCD Applications

In the POC we used the ArgoCD cli to sync Applications.
PROs:

immediate implementation
argocd cli is well tested
CONs:
bake the CLI inside the controller

One feedback we got is to use an annotation. See https://github.com/argoproj/argoproj/issues/25#issuecomment-763811476
TODO
[ ] Decide between CLI and annotation, documenting why about the choice

Duplicate of #22


Bug in DateTimeWidget which leads to incorrect timezone import

Hi all,
thanks for this great project!
I'm living in central europe with day light saving (UTC+1 or UTC+2).  My exported DateTimeFields are written to json as UTC (as others have noted, eg. in #813). According to the code this step is not influenced by USE_TZ.
On import with USE_TZ = True, they are converted to aware datetimes with my default timezone, which is  incorrect (because they are UTC times!) and leads to dates jumping 1 or 2 hours back in time. If I repeat import/export cycles this will move them back in time even further...
Related issues:
Import does not adjust for timezone #465
Export not timezone sensitive #813
Possible solution:
Making the imported datatime timezone-aware but with the timezone correctly set to UTC gives me the expected results and correctly imported DateTimeFields (see diff below).
Sadly I've not enough experience to predict possible side effects of this change which is working for my situation.
@@ -182,8 +184,7 @@ class DateTimeWidget(Widget):
                 if settings.USE_TZ:
                     # make datetime timezone aware so we don't compare
                     # naive datetime to an aware one
-                    dt = timezone.make_aware(dt,
-                                             timezone.get_default_timezone())
+                    dt = timezone.make_aware(dt, timezone.utc)
                 return dt
             except (ValueError, TypeError):
                 continue

Thanks a lot for all your hard work!
Regards, Lukas Wolf

Hi,
is there a reason to prefer timezone.get_default_timezone() over timezone.get_current_timezone() here?
https://github.com/django-import-export/django-import-export/blob/3c082f98afe7996e79f936418fced3094f141c26/import_export/widgets.py#L182-L186
With get_current_timezone() one could override the default timezone for import/export operations only, if needed. (E.g. wrapping those operations with timezone.override.)
And if there is no need to override the default timezone, get_current_timezone() will return the default one.
(In the example above, the default timezone would be Central European, with UTC activated when importing data.)
Or maybe it would be possible to add an optional timezone parameter to the DateTimeWidget?


zmq multiprocessing start fail on windows

I have a problem with zmq multiprocessing, the code below works well on linux but fails on windows, zmq 4.2.5, python 2.7,
from multiprocessing import Process
from multiprocessing import Queue
class MessageHandler(Process):
    def init(self, zmq_context, msg_queue, zmq_url):
        super(MessageHandler, self).init()
        self.queue = msg_queue
        self.context = zmq_context
        self.url = zmq_url
    def run(self):
        self.sub = self.context.socket(zmq.SUB)
        self.sub.connect(self.url)
        self.sub.setsockopt(zmq.SUBSCRIBE, b'')
        while True:
            msg = self.sub.recv()
        self.queue.put_nowait(msg)
md_context = zmq.Context()
md_queue = Queue()
md_url = "tcp//<IP_ADDRESS>:9995"
md_handler = MessageHandler(md_context, md_queue, md_url)
md_handler.start()

Assert error as below:

Traceback (most recent call last):
File "C:/Code/achilles_recv.py", line 214, in
instance = SimpleStrategy()
File "C:/Code/achilles_recv.py", line 69, in init
StrategyBase.init(self, self.process_id)
File "C:\Code\base\StrategyBase.py", line 67, in `init`
self.init_connections()
File "C:\Code\engine\StrategyEngine.py", line 43, in init_connections
md_handler.start()
File "C:\ProgramData\Anaconda2\lib\multiprocessing\process.py", line 130, in start
self._popen = Popen(self)
File "C:\ProgramData\Anaconda2\lib\multiprocessing\forking.py", line 277, in init
dump(process_obj, to_child, HIGHEST_PROTOCOL)
File "C:\ProgramData\Anaconda2\lib\multiprocessing\forking.py", line 199, in dump
ForkingPickler(file, protocol).dump(obj)
File "C:\ProgramData\Anaconda2\lib\pickle.py", line 224, in dump
self.save(obj)
File "C:\ProgramData\Anaconda2\lib\pickle.py", line 331, in save
self.save_reduce(obj=obj, *rv)
File "C:\ProgramData\Anaconda2\lib\pickle.py", line 425, in save_reduce
save(state)
File "C:\ProgramData\Anaconda2\lib\pickle.py", line 286, in save
f(self, obj) # Call unbound method with explicit self
File "C:\ProgramData\Anaconda2\lib\pickle.py", line 655, in save_dict
self._batch_setitems(obj.iteritems())
File "C:\ProgramData\Anaconda2\lib\pickle.py", line 687, in _batch_setitems
save(v)
File "C:\ProgramData\Anaconda2\lib\pickle.py", line 306, in save
rv = reduce(self.proto)
File "stringsource", line 2, in zmq.backend.cython.context.Context.reduce_cython
TypeError: no default reduce due to non-trivial cinit

debug to find that zmq packege has not a function of "reduce"， could anyone help with this issue?

__init__ is run in the parent process, while run is in the subprocess. zmq sockets and contexts cannot be passed from one process to the next. Make sure to create a new Context in run and you might have more success.

Wow, it works! Thanks a lot!


Menu items should get greyed out if they are are no longer applicable

Testing #15811
Menu items should get greyed out if they are are no longer applicable. E.g. Undo/Redo commands should not be displayed if we are at the bottom/top of the undo stack. Same with back/forward. In the cases below, "back" and "redo" both appear to be valid commands, even though they won't do anything.

VSCode Version: Code - Insiders 1.8.0-insider (7499a9f3c565f4fbe5205e30c8664e5a5a11ae94, 2016-12-06T16:16:15.865Z)
OS Version: Windows_NT ia32 10.0.14965

https://github.com/Microsoft/vscode/issues/991


refactor(checkout): CHECKOUT-7449 consolidate all utility tools/files in new packages

What?

Created two new packages, dom-utils and error-handling-utils, to hold common dom/ui utility files and error handling utilities in checkout-js.

dom-utils => getAppliedStyles, parseAnchor, preventDefault and stopPropagation
error-handling-utils => ErrorBoundary and ErrorLogger

Update import path across the repo to use all of the above mentioned utilities from related package.

Why?
In the progress of building checkout monorepos, we copied many utiliy tools to different packages, and it resulted in duplication of those files. So to get rid of those duplicates and to better manage them in the future we moved them to related packages.
Testing / Proof
CI checks
@bigcommerce/team-checkout

Sorry, I missed this before.
Could you please update the owner file for the new packages?

Sorry, I missed this before. Could you please update the owner file for the new packages? https://github.com/bigcommerce/checkout-js/blob/master/.github/CODEOWNERS

@bc-peng Done


A question

Visual Studio uses .ixx as the extension name of module files, while clang uses .cppm instead. Is there an extension name that can be recognized by not only Visual Studio but also other compilers? If not, can I force the IDE and the compiler to accept extension names like .mpp?

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

ID: ad1fef9a-9c55-a8ab-faf4-8b9ceb9ff688
Version Independent ID: 0eadb3ed-bb38-58bc-b335-687b10f0fd31
Content: Overview of modules in C++
Content Source: docs/cpp/modules-cpp.md
Product: visual-cpp
Technology: cpp-language
GitHub Login: @corob-msft
Microsoft Alias: corob

@X-mcfirer
Making other extensions work here doesn't seem like an unreasonable thing to do. At present, I'm not aware of a way to change the extension used, but that doesn't mean there can't be. This is a product question/request best directed at the development team. I recommend using Developer Community to make your request as a suggestion, where it can pick up votes from fellow developers facing a similar prospect, and possibly turn into a work item for the implementers.
I'm closing the issue, as the documentation isn't wrong, yet. If you're successful, that may change in the future. Good luck!

Thank you very much and sorry for my late reply.
At 2020-02-03 17:47:59, "Colin Robertson"<EMAIL_ADDRESS>wrote:
@X-mcfirer
Making other extensions work here doesn't seem like an unreasonable thing to do. At present, I'm not aware of a way to change the extension used, but that doesn't mean there can't be. This is a product question/request best directed at the development team. I recommend using Developer Community to make your request as a suggestion, where it can pick up votes from fellow developers facing a similar prospect, and possibly turn into a work item for the implementers.
I'm closing the issue, as the documentation isn't wrong, yet. If you're successful, that may change in the future. Good luck!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'm not sure why a new file extension is needed in any compiler. It would be nice if folks kept it simple and just supported ".cpp", they are still just files conforming to the c++ spec after all. https://developercommunity.visualstudio.com/idea/978893/c-modules-consider-supporting-custom-extensions-ot.html

@BrennenSpirmont
Well, you could also argue that .h/.hpp extensions are not needed because they are just files conforming to the C++ spec after all.
The reason why we use these different extensions is for convenience, simple as that. We could give every single C++ file a .cpp extension, but why would you when it differentiates the intended use?

@X-mcfirer
If you know the command line options there is a way to use an extension other than .ixx as a module interface file.
The very first module blog post (the one introducing modules in Visual Studio 2015 Update 1 all the way back in 2015) states:
"If you want to use another extension on your interface file you also have to supply the switch /module:interface."
So if you put module generation stuff in a .cpp/.cxx/.cc file (the extension that cl.exe recognises as C++ source files) then it will produce a module interface. However, if you use an extension like .ipp with this switch then the compiler doesn't like it.
Since this works with files recognised as C++ source files then the other step you need to do is tell the compiler to recognise this file as a C++ source file. You can tell the compiler to recognise an arbitrary extension as a C++ source file by using /Tp (for a single file) or /TP (for all files passed in on the command line). So as an example:
cl /c /std:c++latest /experimental:module /module:interface /Tptest.ipp
or
cl /c /std:c++latest /TP /experimental:module /module:interface test.ipp
This works with any extension.

@DarranRowe I guess my issue is that each compiler chose a different extension (.cppm) and if nobody changes then it's going to be a pita to write multi-platform c++ modules. Also, "ixx" is the most bizarre of the choices in my opinion.
As for a dedicated module extension vs just using cpp. As I understand it, modules could completely replace the current header (interface)/source (implementation) file dynamic. With c++20, you could write a library/application that is entirely c++ modules and has no header files at all. This would bring c++ to a similar (simple/better) feature parity that every other modern language has (java/c#/python/etc). I'm probably being too optimistic, but heck, in 10 years, maybe new c++ developers won't even know what a ".h" file is.
Why not keep it simple and use ".cpp" for this file type? Or at least keep the extension intuitive and use what clang's using with ".cppm". Opening a folder and seeing a ".ixx" file without knowing about modules would be very confusing, at least with "cppm" you have a shot of intuiting "cpp module" and having some search terms.
All that being said, I didn't know about the flags to change the extension. Thanks for sharing them, this works for me.

@BrennenSprimont
One major thing to note, it is still protected by the /experimental option, this means that the implementation details are still not finalised yet.
Also I don't think that the .ixx extension is that weird if you remember one of the C++ file extensions is .cxx. Also, if you also remember that this file is for the module interface then it should also be just as easy to intuit "interface++".
Well anyway, you should expect the compiler team to add more extensions when it no longer requires the /experimental option to activate modules. Until then you should seriously consider the extension a placeholder.


[Snyk] Security upgrade github-pages from 214 to 224

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `rubygems` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

Gemfile
Gemfile.lock

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

479/1000  Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-RUBY-ACTIVESUPPORT-3237242
Yes
No Known Exploit

519/1000  Why? Has a fix available, CVSS 6.1
Cross-site Scripting (XSS) SNYK-RUBY-ACTIVESUPPORT-3360028
Yes
No Known Exploit

501/1000  Why? Recently disclosed, Has a fix available, CVSS 4.3
Information Exposure SNYK-RUBY-ACTIVESUPPORT-5851458
Yes
No Known Exploit

654/1000  Why? Has a fix available, CVSS 8.8
Integer Overflow or Wraparound SNYK-RUBY-COMMONMARKER-2415031
Yes
No Known Exploit

486/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 3.3
Out-of-bounds Read SNYK-RUBY-COMMONMARKER-3318398
Yes
Proof of Concept

429/1000  Why? Has a fix available, CVSS 4.3
Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318399
Yes
No Known Exploit

646/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 6.5
Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318400
Yes
Proof of Concept

536/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 4.3
Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-3318401
Yes
Proof of Concept

479/1000  Why? Has a fix available, CVSS 5.3
Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5603111
Yes
No Known Exploit

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5603112
Yes
Proof of Concept

641/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 6.4
Denial of Service (DoS) SNYK-RUBY-COMMONMARKER-5829860
Yes
Proof of Concept

589/1000  Why? Has a fix available, CVSS 7.5
Directory Traversal SNYK-RUBY-TZINFO-2958048
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Cross-site Scripting (XSS)
🦉 Directory Traversal

snyk-fix-88163dd55e94dbd9bce0dd8cec87cb96

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!kizzycamagu2, @S-Guerra, @DragonDare, @hishubho, @QuynhVir, @nmoreau, @f2pls, @GannoK, @tungplclhd, @HanDongWook, @GilbertzzzZZ, @RSlyn2, @American-Cryptformant, @owahlgren, @balaji-code, @hoanganhx86, @dalongmyself, @MoElaSec, @Agam-patel, @StanleyChristmas


Fix packaging

load dash, s
add autoload cookie(reference https://www.gnu.org/software/emacs/manual/html_node/elisp/Autoload.html)

dash and s functions are not autoloaded so it must be loaded. For example if M-x eping is evaluated before loading dash and s then the following error occurs.
call-interactively: Symbol’s function definition is void: -cons*

@syohex your quick response was impressive.
I have merged pull request #2 as it addresses these issues by eliminating them.
I will take require and autoload into account when creating other packages.
Thank you


Bug: Fails to upload to Cloudflare R2 S3-compatible Storage

What happened?
This is more of an FYI than a bug report, as I believe the solution for this lies at Cloudflare's end.
When attempting to use Cloudflare R2 for storage, uploads on the front-end UI seem to hang and never complete. Inspecting the logs; I see the following:
S3Error
    at parseError (/zipline/node_modules/minio/dist/main/internal/xml-parser.ts:26:13)
    at Object.parseResponseError (/zipline/node_modules/minio/dist/main/internal/xml-parser.ts:75:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Client.makeRequestStreamAsync (/zipline/node_modules/minio/dist/main/internal/client.ts:629:19) {
  amzRequestid: undefined,
  amzId2: undefined,
  amzBucketRegion: undefined
}
2024-05-09 07:41:30,411 PM info  [server::response] POST /api/upload -> 500

I believe this is something to do with compatibility between the minio SDK and Cloudflare R2. See related post here: https://community.cloudflare.com/t/r2-multipart-uploads-not-working-with-minio-client/396536/17
Version
latest (ghcr.io/diced/zipline or ghcr.io/diced/zipline:latest)
What browser(s) are you seeing the problem on?
Chromium-based (Chrome, Edge, Brave, Opera, mobile chrome/chromium based, etc)
Zipline Logs
S3Error
    at parseError (/zipline/node_modules/minio/dist/main/internal/xml-parser.ts:26:13)
    at Object.parseResponseError (/zipline/node_modules/minio/dist/main/internal/xml-parser.ts:75:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Client.makeRequestStreamAsync (/zipline/node_modules/minio/dist/main/internal/client.ts:629:19) {
  amzRequestid: undefined,
  amzId2: undefined,
  amzBucketRegion: undefined
}
2024-05-09 07:41:30,411 PM info  [server::response] POST /api/upload -> 500

Browser Logs
Failed to load resource: the server responded with a status of 500 ()
file:1 Uncaught SyntaxError: Unexpected token 'I', "Internal S"... is not valid JSON
    at JSON.parse (<anonymous>)
    at XMLHttpRequest.<anonymous> (file-97515cca25c3c76c.js:1:11944)

Additional Info
No response

I use R2 on my instance of Zipline without any issues so it's more than likely an issue with your config. Can you provide your config so that I can look for potential issues? Be sure to remove any important credentials such as your core secret etc.

Like the above said, the issue is probably due to a misconfiguration and it's also been 2 weeks with no response so I will be closing this as stale.

Like the above said, the issue is probably due to a misconfiguration and it's also been 2 weeks with no response so I will be closing this as stale.

Set DATASOURCE_S3_REGION to ENAM and DATASOURCE_S3_FORCE_S3_PATH to false (this only needs to be true if you want to specify a folder in the bucket that the files get uploaded to). DATASOURCE_S3_PORT is not needed and I have listed all of the required variables below.
- DATASOURCE_TYPE=s3
- DATASOURCE_S3_ACCESS_KEY_ID=<ACCESS_KEY_ID>
- DATASOURCE_S3_SECRET_ACCESS_KEY=<ACCESS_KEY_SECRET>
- DATASOURCE_S3_BUCKET=<BUCKET_NAME>
- DATASOURCE_S3_ENDPOINT=<ACCOUNT_ID>.r2.cloudflarestorage.com
- DATASOURCE_S3_REGION=ENAM
- DATASOURCE_S3_FORCE_S3_PATH=false
- DATASOURCE_S3_USE_SSL=true

If you are still having issues after modifying your config with the changes mentioned above, feel free to reply here.


Replace normalize with integer wrapper for quantity field

In a attempt to fix #1443
I don't see when can the BOM Item quantity be a decimal number and it was causing the error in the BOM export because the PyYAML library doesn't have a Decimal object representation.

Looks like float would work for YAML:
>>> import yaml
>>> dec = 1.23456
>>> print(dec)
1.23456
>>> type(dec)
<class 'float'>
>>> yaml.safe_dump(dec)
'1.23456\n...\n'
>>> dec = 1.2345600000
>>> yaml.safe_dump(dec)
'1.23456\n...\n'

But I'm not sure all the other formats would remove the trailing zeros...

Can we check the output format and choose 'float' if it is a yaml file?

I don't really find a good way to check the export format and pass it to the dehydrate_quantity method...

Ok, what does the output look like for a .csv file? Does it suppress the trailing zeros correctly?

@SchrodingersGat I tested all formats with float and CSV, TSV and XLS gets no decimal digits for integer quantities and the right amount of digits for decimal numbers, while XLSX, JSON and YAML get one digit for integer quantities and also the right amount of digits for decimal numbers.
So if we are okay that quantity of 10 becomes 10.0 for XLSX, JSON and YAML then float is a great option :smiley:

Seems like a reasonable compromise.

Thanks for the fix :)

No problem, thanks for merging 👍