haproxy: 2.8.4 -> 2.9.0; Enable QUIC support

Description of changes
This enables switching SSL Libraries.
In addition, this switches to PCRE2 and Lua 5.4 from PCRE and Lua 5.3.
Should have no functional differences, apart from the added QUIC support which needs to be configured in HAProxy.
This also adds more test cases, specifically for SSL, mutual TLS and QUIC.
According to the recent SSL Library Support Wiki Page, OpenSSL 3.X is not the best choice by far.
I would really like WolfSSL, as that seems to be the one with the best performance yet there are still many unimplemented features.
It requires a different build config, but that's the way wolfssl intends to be used.
However, in order to make this easier to merge without worrying about breakage, it still defaults to OpenSSL (3.X)
A future PR might flip the switch, though.
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

[x] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
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

[x] Fits CONTRIBUTING.md.

I saw #202922, but that is IMO not the way to go.
OpenSSL 3.X is not recommended for HAProxy.
As a direct quote from SSL Library Support Wiki Page:

At this point, OpenSSL 3.x is basically only usable for personal sites. Users seeking anything serious performance-wise will need to stay on version 1.1.1 provided by their vendor or to recompile one of the alternate libraries below.

Put the effort in to make it work with WolfSSL, which is the best option at the moment.
Should be less user-facing breakage than LibreSSL, actually!

Actually, I'll rework the WolfSSL derivation first.

Hey @SuperSandro2000, thank you kindly for reviewing.
The wolfssl changes are from #262594, I just needed to base the HAProxy changes on top - but I implemented your feedback (or tried, at least).
As for the sslPkgs stuff, I am not sure how to do it better as I'd need to detect if it's OpenSSL, OpenSSL with QuicTLS-compatible API (QuicTLS, BoringSSL, LibreSSL) or WolfSSL.
Do you have a suggestion?

I added some tests.
WolfSSL presumably requires a new release to get functioning HTTPS Client Certificate Authentication and I couldn't figure out if there's just a small patch to fix it between the 800+ commits that happened since the last release, so I think using it as default is only wise once that happens.
Sad, the performance difference is quite drastic!
No QUIC tests yet, as I couldn't seem to get them working at all.
curlHTTP3 with the --http3-only flag didn't seem to want to connect.
QUIC does function with a browser in all the supported implementations (apart from OpenSSL, which doesn't seem to have one).
HAProxy does not seem to support cert auth under QUIC at the moment, unsure what causes that. I opened an issue upstream: https://github.com/haproxy/haproxy/issues/2322

Hello,
Quite honestly migrating to any other SSL library for HAProxy will remove a lot of features, neither LibreSSL nor WolfSSL implement the ClientHello callback which allows to have a dual ECDSA/RSA certificate for a same domain  for example.
And a lot of reg-tests are not working.
With WolfSSL only 15/30 SSL tests are working when using the latest 2.9-dev and the latest wolfssl commit.
It is a totally different stack not based on OpenSSL but they developed an OpenSSL compatibility API that does not provide the whole Openssl features. We hope to have a better support for it, but it's still considered experimental for HAProxy.
If you don't care about the performances issues of OpenSSL/quicTLS 3.x (it could be enough for small setups):

QUIC with a full-featured haproxy you should consider openssl with USE_QUIC_OPENSSL_COMPAT=1. This will allow you to use QUIC with a standard openssl library (without the quictls patchset). The only limitation is that it does not provide the 0-rtt feature for QUIC.
It was developed in version 2.9-dev but I backported it in 2.8 so it will be available in the next 2.8.4 version.

If you want a full-featured HAProxy with a full-featured QUIC, quictls is the best choice.

For other libraries:

Regarding boringSSL we don't really work on  it anymore, the API changes a lot and it's a rolling release cycle, we don't even build it on the per-push CI.

There is also the choice of AWSLC, but it's not in a release version yet, I'll probably backport the build fixes in 2.8 for it. We recently fixes the issue of QUIC for it, but it lacks some ciphers for QUIC.

Regards,

Hey @wlallemand, thank you so much for chiming in!
My current patch changes our default to QuicTLS as it is OpenSSL 3.X right now.
Thank you for confirming that it does result in a full-featured HAProxy with QUIC!
Perhaps changing back to OpenSSL 3.X after the next 2.8.4 release is something to consider.
This patch also allows one to optionally switch to a different implementation, like WolfSSL, but it won't be the default for a long time. I abandoned that idea pretty "quicly". ;)
But I will remove BoringSSL as an option in this patch, good to know that it is not something you really work on anymore!
Thank you so much!

Small update, we released haproxy 2.8.4, you can now enable USE_QUIC_OPENSSL_COMPAT=1 to have QUIC with an non-patched version of openssl.

Update on this:

Bumped to 2.9.0, it removes the need for some workarounds.
Enabled USE_QUIC_OPENSSL_COMPAT for OpenSSL. All providers enable QUIC now.
Default to OpenSSL again to reduce breakage of existing setups to zero.

@vifino I'm not aware of any issue of this kind with the openssl compat layer, it could be a bug or a limitation of the current achitecture. Did you had the same issue with 2.8.4?  Better open an issue on the haproxy github indeed! thanks.


Add a Linux installer

R&D required to understand how best to achieve this.  To do later.  Windows is the focus currently.

Reserach what is the best way and check with @veebs  before you start.
I would be happy with a zip file of binaries you download, unzip and it just works.  Are there any dependancies that needs to be installed?


[Bug]run prover  connect to  timed out

🐛 Bug Report
2024-02-23T15:09:52.110739Z DEBUG No connected peers
2024-02-23T15:09:53.113218Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:10:17.113516Z DEBUG No connected peers
2024-02-23T15:10:18.114887Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:10:42.114190Z DEBUG No connected peers
2024-02-23T15:10:43.115605Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:11:07.115937Z DEBUG No connected peers
2024-02-23T15:11:08.116329Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:11:32.116631Z DEBUG No connected peers
2024-02-23T15:11:33.118057Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:11:57.117406Z DEBUG No connected peers
2024-02-23T15:11:58.118871Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:12:22.119172Z DEBUG No connected peers
2024-02-23T15:12:23.120521Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:12:47.120786Z DEBUG No connected peers
2024-02-23T15:12:48.122160Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:13:12.121469Z DEBUG No connected peers
2024-02-23T15:13:13.122876Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:13:37.123098Z DEBUG No connected peers
2024-02-23T15:13:38.124427Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-23T15:14:02.124660Z DEBUG No connected peers
2024-02-23T15:14:03.126033Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
Steps to Reproduce
setup by the guide. and run ./run-prover.sh
Expected Behavior
port 3030/tcp no open but the OS firewall are closed.
Your Environment
snarkOS Version: mainnet-latest  [v2.2.7]
Rust Version:1.74.1
Computer OS:Ubuntu 22.04

snarkOS Version: mainnet-latest  [v2.2.7]

Compiling error:
error: could not parse/generate dep info at: /home/rootadmin/snarkOS/target/release/deps/version_check-2eacf4551749794c.d
Caused by:
failed to write /home/rootadmin/snarkOS/target/release/.fingerprint/version_check-2eacf4551749794c/dep-lib-version_check
Caused by:
No such file or directory (os error 2)
Removed 6714 files, 2.5GiB total
error: could not write output to /home/rootadmin/snarkOS/target/release/deps/pkg_config-ef0de09c30e211bf.pkg_config.8f35a4c55af25689-cgu.05.rcgu.o: No such file or directory
error: failed to write /home/rootadmin/snarkOS/target/release/deps/libzerocopy-b8126872e162cabe.rmeta: No such file or directory (os error 2)
error: couldn't create a temp dir: No such file or directory (os error 2) at path "/home/rootadmin/snarkOS/target/release/deps/rmetag8L0NY"
error: could not compile zerocopy (lib) due to previous error
error: couldn't create a temp dir: No such file or directory (os error 2) at path "/home/rootadmin/snarkOS/target/release/deps/rmetagRr9hJ"
error: could not compile allocator-api2 (lib) due to previous error
error: could not compile ppv-lite86 (lib) due to previous error
error: could not compile pkg-config (lib) due to previous error
error: could not write output to /home/rootadmin/snarkOS/target/release/deps/vcpkg-f5768767b1829c57.vcpkg.c61bebd8048b8b10-cgu.15.rcgu.o: No such file or directory
error: could not compile vcpkg (lib) due to previous error
error: couldn't create a temp dir: No such file or directory (os error 2) at path "/home/rootadmin/snarkOS/target/release/deps/rmetaSkLTpV"
error: could not compile memchr (lib) due to previous error

I reinstalled it and it doesn't generate an error anymore, but it still times out on the connections.
🧭 Starting a prover node on Aleo Mainnet (v0) at <IP_ADDRESS>:4130.
2024-02-25T07:02:11.342571Z DEBUG No connected peers
2024-02-25T07:02:12.344044Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-25T07:02:36.343784Z DEBUG No connected peers
2024-02-25T07:02:37.345144Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-25T07:03:01.345361Z DEBUG No connected peers
2024-02-25T07:03:02.346798Z  WARN Unable to connect to '<IP_ADDRESS>:4130' - timed out
2024-02-25T07:03:26.346092Z DEBUG No connected peers
only 4130 opened.

I encountered the same problem.

me too

Any solution for this, it's stuck on my node for a couple week

Bro, did you solve the problem?

+1

Same issue as https://github.com/AleoNet/snarkOS/issues/3113.

It looks like you were running a prover on Mainnet before Mainnet was officially launched. Please reopen this issue if you still experience similar problems.


Pattern: Card Section Images - Card font text is not readable, while theme (g90 and g100) is changed.

Detailed description
Devices - Windows, Mac and Mobile
Browsers - Firefox, chrome and Safari
Issue :- When a user changes the theme, the background color is merged with the card heading / copy text and not readable for the user.
Steps to reproduce the issue

Open the Storybook URL on the browser
Select Content Section images
From Knobs, change the "theme" to g90 or g100
Verify background color and card heading , text

Additional information

@Praveen-sr: can you test this with this [URL] (https://ibmdotcom-react.s3.us-south.cloud-object-storage.appdomain.cloud/deploy-previews/1539/index.html?path=/story/patterns-sections-cardsectionimages--default) and let me know is it as expected or not thanks!

@mkothur Re tested the issue on provided URL, working as expected now on windows, Mac and Mobile. Thanks!


Remove tar dependency and used platform specific dependencies for different formats

@nathanbabcock you can merge it, if everything looks fine. I don't have write access to the repo


[SUP1-201] Fix bug switching apps in management UI

From SyncLinear.com | SUP1-201

test

Still running into issues, the dropdown menu is sticky
https://www.loom.com/share/93926e13ba0748dab24dbbe6dbb61353

Where are you running into this? I can't reproduce it in prod or locally? Have you pulled from head recently?

The problem was that the link wasn't spanning the whole row in the menu. I fixed that in the above PR.


onwards is misspelled in the config creation

https://github.com/fastai/nbdev/blob/4cd11a3de4d526475170cab158f655e9f855edd0/nbdev/config.py#L76

@kevinbird15 want to make a PR?

sure, I can


Why do you throttle the speed?

I've modified the code so that it can parallelize and use multiple threads but it wouldn't make much sense if the download is throttled. If you are fine with it it'd try to clean up a bit and create a pr in a few days

Any update on this? It works really well but it is incredibly slow for me.

Basically it isn't needed but if you (often) download a large map with high detail the target server will eventually time out your connection or even block your IP.
The timeout is to prevent that.


Throw two errors and Caller can catch

Is your feature request related to a problem? Please describe.
There are two case that I get error but cannot catch it when init 3DS 2.0 flow via call createFormAction(data, config).
Case 1:
The error occurs when I pass wrong data pass to  createFormAction.
I change token filed in data which getting from Adyen and API https://checkoutshopper-test.adyen.com/checkoutshopper/v1/submitThreeDS2Fingerprint gets 500 error.

Case 2:
I using Charles to change the param paymentData pass, and https://checkoutshopper-test.adyen.com/checkoutshopper/v1/submitThreeDS2Fingerprint get 422 error.

Describe the solution you'd like
I add onError in configuration and pass configuration to new AdyenCheckout(configuration), but cannot catch these two errors.
Could you throw these two errors to onError event?

Hey @Kerita .
What version of the SDK are you using? Could you also test this scenarios with the latest library version?

Closing this as the issue is stale. Please reach out if the problem persists.


Add rocky_tf_monitor in noetic/distribution.yaml

Please Add This Package to be indexed in the rosdistro.
tf_monitor
The source is here:
https://github.com/rkoyama1623/tf_monitor.git
Checks

[x] All packages have a declared license in the package.xml
[x] This repository has a LICENSE file
[x] This package is expected to build on the submitted rosdistro

New package review:

[x] At least one of the following must be present

[x] Top level license file: https://github.com/rkoyama1623/tf_monitor/blob/main/LICENSE
[ ] Per package license files

[x] License is OSI-approved: MIT
[x] License correctly listed in package.xmls

[x] tf_monitor: https://github.com/rkoyama1623/tf_monitor/blob/main/package.xml

[x] Public source repo: https://github.com/rkoyama1623/tf_monitor/tree/main/
[ ] Source repository contains ROS packages and each package meets REP-144 naming conventions

[ ] tf_monitor

@audrow I could a second opinion on this package name before approving the name.
The name is accurate but I'm not sure if it counts as too general.

I think the package name here could be confusing, because we already have a tf2_monitor command available from geometry2: https://github.com/ros2/geometry2/blob/rolling/tf2_ros/src/tf2_monitor.cpp .  I know that is for ROS 2, but I still think this could be confusing.
How about rkoyama_tf_monitor instead?

Holding for Noetic sync

@nuclearsandwich, @clalancette, Thank you for your considerations and naming suggestion.
rkoyama is my personal name:laughing:. I'd like to use a little more generic name.
I named this ros package rocky_tf_monitor, since this tool is used to inspect rocky tf topics, and rocky is a bit like my name.

I named this ros package rocky_tf_monitor, since this tool is used to inspect rocky tf topics, and rocky is a bit like my name.

That sounds good to me.


SQLDB refactor to support multiple firewall rules

1.) Adds a new FirewallRule struct
2.) Replaces firewall rule provisioning params with slice of FirewallRule
3.) Updates ARM template to use go template for firewall rules
4.) Updates Docs
Closes #248

Looks like this PR still needs changes that were already applied to it's sibling PRs for Postgres and MySQL?

Too fast for me! I was running the tests locally :)


[docs] Update Hexo dependencies for cross-repo consistency.

This PR is part of a series of semi-automated PRs which aims to bring Hexo and
its dependencies to their latest stable versions and align all of Apollo's
Hexo-based doc configurations with the same patterns.  For
repositories that are not docs-only (i.e. docs are included in the repository's
greater purpose), there are not any changes to the non-docs portion.
The Apollo repositories which are receiving this PR are those listed at:
https://github.com/meteor/hexo-theme-meteor/#readme
Notes:

The new npm versions in this PR have been well-tested with other docs
repositories and should function well.
This also introduces two other npm scripts: npm run clean and npm test.
It's recommended that a repository whose hexo generate depends on artifacts
from the rest of the repository incorporate this new npm test into their
TravisCI build to ensure that changes to the repository do not break the docs
generation (for example, where TypeScript or JSDoc integrations exist).  This
will ensure a PR which breaks docs gets detected on the PR, rather than at a
later, less convenient time.
(not included in this PR) A future PR of a similar nature will re-align the
themes between the various Apollo repositories, through use of a npm-based
theme. This should allow Renovateapp to auto-update the docs with the latest
hexo-theme-meteor (whenever one is published) and remove the need for Git
submodules (at least where they're used for docs).

And finally, I will manually access each of these PRs and check their Netlify
deploy previews and merge as appropriate (hopefully with great success!).

The Netlify docs preview deployment looks correct to me! :shipit:
I'll defer to this repo's maintainers as a matter of uncertainty about merge/squash policy, but please land at your convenience! :wink:
(Also, happy to adjust/answer any questions.)


License of the SMP2020 dataset (FewJoint)

Hi, Yu Tai,
Thanks for your contribution to few-shot joint learning.
I'd like to reorganize the dataset for my research.
So, I would like to know the license of the FewJoint dataset.
Best,
Gordon Lee.

Hi, Yu Tai, Thanks for your contribution to few-shot joint learning. I'd like to reorganize the dataset for my research. So, I would like to know the license of the FewJoint dataset. Best, Gordon Lee.

Hi, you are free to use it with proper citation, and here is a newer data version:
https://github.com/AtmaHou/FewShotJoint/tree/master/data


Add support for formatting Emacs Lisp by reindenting it

BTW:
Please add support for fish-shell script:
add this in apheleia-formatters:
    (fish_indent . ("fish_indent"))

add this in apheleia-mode-alist:
    (fish-mode . fish_indent)

so I don't have to make a PR.

I added fish-indent as requested, since the change was straightforward. However, it's unclear what Apheleia should do with Emacs Lisp code. Reindent it? Or run some more sophisticated formatter?

I didn't find a simple emacs-lisp-formatter, but emacs-format-all just write a function to format the emacs-lisp buffer
https://github.com/lassik/emacs-format-all-the-code/blob/master/format-all.el#L798-L808

What I recommended is to supported all the languages that emacs-format-all-the-code supports which is listed in https://github.com/lassik/emacs-format-all-the-code#supported-languages, sorry, maybe this is too much to make such a recommendation.
Angular/Vue (prettier)
Assembly (asmfmt)
ATS (atsfmt)
Awk (gawk)
Bazel Starlark (buildifier)
BibTeX (Emacs)
C/C++/Objective-C (clang-format, astyle)
C# (clang-format, astyle)
Cabal (cabal-fmt)
Clojure/ClojureScript (node-cljfmt)
CMake (cmake-format)
Crystal (crystal tool format)
CSS/Less/SCSS (prettier)
Cuda (clang-format)
D (dfmt)
Dart (dartfmt, dart-format)
Dhall (dhall format)
Dockerfile (dockfmt)
Elixir (mix format)
Elm (elm-format)
Emacs Lisp (Emacs)
F# (fantomas)
Fish Shell (fish_indent)
Fortran Free Form (fprettify)
Gleam (gleam format)
GLSL (clang-format)
Go (gofmt, goimports)
GraphQL (prettier)
Haskell (brittany, fourmolu, hindent, ormolu, stylish-haskell)
HTML/XHTML/XML (tidy)
Java (clang-format, astyle)
JavaScript/JSON/JSX (prettier, standard)
Jsonnet (jsonnetfmt)
Kotlin (ktlint)
LaTeX (latexindent, auctex)
Ledger (ledger-mode)
Lua (lua-fmt, prettier plugin)
Markdown (prettier)
Nginx (nginxfmt)
Nix (nixpkgs-fmt, nixfmt)
OCaml (ocp-indent)
Perl (perltidy)
PHP (prettier plugin)
Protocol Buffers (clang-format)
PureScript (purty, purescript-tidy)
Python (black, yapf)
R (styler)
Racket (raco fmt)
Reason (bsrefmt)
ReScript (rescript format)
Ruby (rubocop, rufo, standardrb)
Rust (rustfmt)
Scala (scalafmt)
Shell script (beautysh, shfmt)
Snakemake (snakefmt)
Solidity (prettier plugin)
SQL (pgformatter, sqlformat)
Svelte (prettier plugin)
Swift (swiftformat)
Terraform (terraform fmt)
TOML (prettier plugin)
TypeScript/TSX (prettier)
V (v fmt)
Verilog (iStyle)
YAML (prettier)

Currently apheleia only supports:
((cc-mode . clang-format)
    (c-mode . clang-format)
    (c++-mode . clang-format)
    (css-mode . prettier)
    (elixir-mode . mix-format)
    (fish-mode . fish-indent)
    (go-mode . gofmt)
    (haskell-mode . brittany)
    (html-mode . prettier)
    (java-mode . google-java-format)
    (js3-mode . prettier)
    (js-mode . prettier)
    (json-mode . prettier)
    (latex-mode . latexindent)
    (LaTeX-mode . latexindent)
    (php-mode . nil)
    (python-mode . black)
    (ruby-mode . prettier)
    (rustic-mode . rustfmt)
    (rust-mode . rustfmt)
    (sass-mode . prettier)
    (terraform-mode . terraform)
    (TeX-latex-mode . latexindent)
    (TeX-mode . latexindent)
    (tuareg-mode . ocamlformat)
    (typescript-mode . prettier)
    (web-mode . prettier)
    (yaml-mode . prettier))

I suppose it would be okay to add Elisp; this should be doable using https://github.com/raxod502/apheleia/pull/63 that was recently merged. It would be best to open a separate issue about formatter parity with format-all-the-code, though. See also https://github.com/lassik/emacs-format-all-the-code/issues/170, which I just filed.

I think this can be closed, there's now a lisp-indent formatter available. Please reopen if still necessary.


"GenerateSW has been called multiple times" error when running in dev mode

This is a fresh clone of the latest commit.
This also causes a service error when visiting the webpack server in the browser.

$ next dev
ready - started server on <IP_ADDRESS>:3000, url: http://localhost:3000
> [PWA] Compile client (static)
> [PWA] Auto register service worker with: /Users/annazhang/git/3d-nft/3d-nft/node_modules/next-pwa/register.js
> [PWA] Service worker: /Users/annazhang/git/3d-nft/3d-nft/.next/sw.js
> [PWA]   url: /sw.js
> [PWA]   scope: /
> [PWA] Build in develop mode, cache and precache are mostly disabled. This means offline support is disabled, but you can continue developing other functions in service worker.
> [PWA] Compile server
> [PWA] Compile server
event - compiled client and server successfully in 2.8s (1021 modules)
wait  - compiling / (client and server)...
warn  - GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
warn  - GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.
wait  - compiling /404 (client and server)...
warn  - GenerateSW has been called multiple times, perhaps due to running webpack in --watch mode. The precache manifest generated after the first call may be inaccurate! Please see https://github.com/GoogleChrome/workbox/issues/1790 for more information.```

same here!

This error isn't too much of an issue, because when your code gets auto-updated in the browser it re-calls the function. aka, expected behavior. You wont see this error in a production mode, and the function will not be called multiple times. This only happens on your local env.
The issue further down the pipe is the fact that the SW does not install at all for me, even in a production env because "the app does not work offline". I also had to copy the sw.js to the /public directory manually, to fix the 404 error in production env. I assume that would also fix your local issue, but thats hacky. Shouldn't have to copy that file anywhere.

This error isn't too much of an issue, because when your code gets auto-updated in the browser it re-calls the function. aka, expected behavior. You wont see this error in a production mode, and the function will not be called multiple times. This only happens on your local env.
The issue further down the pipe is the fact that the SW does not install at all for me, even in a production env because "the app does not work offline". I also had to copy the sw.js to the /public directory manually, to fix the 404 error in production env. I assume that would also fix your local issue, but thats hacky. Shouldn't have to copy that file anywhere.

copy the sw.js to the /public directory manually work for me!

Thanks!
next-pwa was not up to date with the latest version of nextjs but everything should be fine now:
https://github.com/shadowwalker/next-pwa/commit/1e6af5fa9f6a807930f451adb5ab5078d5cda451#diff-38fcdef48d4c9636b640c40cb75b5278d405ab90f1b0960895900a068436f4cb
Please try again with a fresh install of react-three-next and close the issue if that fixes your problem :)


Add issue and pull request templates

This PR will help contributor write issue or pull request description correctly.

lgtm


Updated changelog and package.json for v.1.32.1

Codecov Report

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

@@          Coverage Diff          @@
##           master   #521   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          54     54
  Lines        1737   1737
  Branches      261    261
=====================================
  Hits         1737   1737

Flag
Coverage Δ

#builder
100% <ø> (ø)
:arrow_up:

#runtime
100% <ø> (ø)
:arrow_up:

#srcapp
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Is traffic routed through TOR?

What is missing
Is the communication between the app and the backend routed in a way that will prevent leaking IPs by design for example using the TOR network?
Why should it be included
Since there is no way (Im aware of) to audit the backend and ensure the logs are deleted an app users should not have to "trust" it to use it.
At least for things like remote updating the configuration.
Where should it be included
In the codebase and documentation.

I think this is necessary since you "trust" Apple and/or Google if you use a smartphone to use this app.

Yes, you do have the choice to trust Apple or Google. Yet you have no choice but to place trust in telekom with the backend.

Please, there's already 200+ comments about this in #13 that don't lead anywhere. Opening new issues for the same thing doesn't help at all, it just makes the discussions repeat even more than they already do.
No, the traffic is not routed through Tor. No, the server knowing client IPs is not a security issue.

@Leseratte10 those are different things in #13 voices concerns with manipulating data stored on the device whereas this ticket voices concerns with metadata stored on the server.

@Leseratte10 those are different things in #13 voices concerns with manipulating data stored on the device whereas this ticket voices concerns with metadata stored on the server.

Such issues are also discussed there. At a certain point you will have to trust every backend, at least to a certain extent. However, you will be able to see which data is sent to the server. As @Leseratte10 already pointed out, this will most probably be the IP address only (and the maintainers already confirmed that the IP will be deleted after a short period of time).

We don't want to add 40M clients to the TOR network. No one knows if the network would withstand that. Also the load on the mobile networks would increase significantly.

It wouldn't. And it wouldn't be what Tor was designed for. It was designed for people in dictatorships like China, or people that have to fear a political prosecution for their statements. Not because people's feelings are hurt because one server knows a phone's IP that doesn't get logged long-term.

It was designed for people in dictatorships like China, or people that have to fear a political prosecution for their statements.

It was also designed to protect journalists in those dictatorships. Or whistleblowers.
The more „regular” people hop onto the network, the better those people get protected. (Because the noise increases)

No one knows if the network would withstand that.

The state could host exit nodes. I'm sure, Deutsche Telekom has infrastructure for doing so.

Also the load on the mobile networks would increase significantly.

You're already zero-rating videos of certain service providers. That could be another exemption.
(I'd prefer net neutrality, personally)

It has already been broken before.
So does iOS and Android. Nevertheless those are used, too.

You rarely hear of TOR hacks, though.

It has already been broken before.
So does iOS and Android. Nevertheless those are used, too.

You rarely hear of TOR hacks, though.

All it takes is one entrypoint ;)
The people that initially made Tor are likely also the best to know their weaknesses.
They have no incentive to report to the public when they find vulnerabilities.
And we know they did so in the past (hiding vulnerabilities), seems reasonable to think they continue being the same way.


Fixed connection release when body isn't run, as well as thread affinity

This PR fixes three issues in the async-http-client implementation:

When the body of the response was never sequenced, the upstream connection would never be closed and would ultimately end up stuck in TCP CLOSE_WAIT
The fiber continuation of the Response was run on an AHC thread, rather than on the pool governed by the relevant ContextShift. In order to avoid breaking bincompat, this was fixed by forking a fiber to run the async callback
Under certain circumstances, when the body of an HTTP was empty, the prior implementation could deadlock. This is fixed by adding a callback to onComplete. Note that, by law, Cats Effect async callbacks ignore repeated invocations, so it's safe to put this here without a latch to guard it.

It's worth noting that there is still a known issue with this fix: namely, if you start running the body stream and then the controlling fiber is almost immediately canceled, then the connection can leak. This can happen because we cannot uninterruptibly call subscribe and start the stream (which would register the finalizer that runs cancel). The only way to fix this is to change fs2-reactive-streams' .stream function to take an F[Unit] representing the subscription effect, which it would then sequence and manage itself in a properly bracketed fashion.
This case is very unlikely, and at least things are better than they were.

Cherry-picked onto series/0.21.


Variables: chaining var declarations

There's a bit in "Variables" suggesting that var statements shouldn't be chained together. For example:
// bad
    var items = getItems(),
        goSportsTeam = true,
        dragonball = 'z';

    // good
    var items = getItems();
    var goSportsTeam = true;
    var dragonball = 'z';

Generally this is suggested because it's harder to make a syntax mistake. However, this will be caught by using "use strict", so I'm not sure it's necessary.
Do we want to keep this advice or remove it?

I discussed this with @peterpratt and TP today, and we agreed that we'd leave the guidance in, since the syntax mistake would not pick-up overwriting of global variables.
I'll add something in the guidance to explain this.


fix: fix typos in keys of i18n

Types

[x] 🪚 Refactors
[x] 🧹 Chores

Changelog
replace every deugger to debugger

closed because of duplication here #1175


Ubuntu 14.04  - Unable to locate package dotnet-dev-1.0.0-preview4-004223

Thanks for your interest in .NET Core.
There is a problem with installing preview4 on the Travis build agent.
Part of .travis.yaml:
language: csharp
sudo: required
dist: trusty
os:
  - linux
[..]
before_install:
  - sudo sh -c 'echo "deb [arch=amd64] https://apt-mo.trafficmanager.net/repos/dotnet-release/ trusty main" > /etc/apt/sources.list.d/dotnetdev.list'
  - sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 417A0893
  - sudo apt-get update
  - sudo apt-get install dotnet-dev-1.0.0-preview4-004223

Error:

Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dotnet-dev-1.0.0-preview4-004223
E: Couldn't find any package by regex 'dotnet-dev-1.0.0-preview4-004223'

mistake, moved to https://github.com/dotnet/cli/issues/5146


Add a paragraph on Python exceptions.

I'd move the sentence about using the appropriate standard Python exception to the top: that's the thing we want to emphasize. Most of the time you don't need to define your own exception.
The final sentence should say:  ``pex_exceptions`` should not be caught unless there is no equivalent python binding (e.g. lsst.pex.exceptions.LengthError).

Oh, and please link the statement about defining a module-specific exception to the python docs. This might be a good link: https://docs.python.org/3/tutorial/errors.html#user-defined-exceptions

I want people to at least consider a module-specific exception each and every time.  I think they're underused (perhaps not massively, but at least somewhat).
Saying "should not be caught" has the wrong implication to me: that they should be allowed to pass through to higher-level code for some reason.  But the point about stating this in terms of C++ exceptions that have no Python equivalent is a good one.
I'll edit later tonight.

Is that a bit better, @parejkoj ?

Self-approved and merged.


Can not train with gpt2?

Hi, I really like your project, but I tried to train with gpt2, it does not work. Will you release some instructions for gpt2? Thank you for your work

what exact error did you get?

It looks the only parameter I should set is --model_checkpoint="gpt2", is that correct? Then I got an error that there is no set_num_special_tokens() method in modeling_gpt2, then I replaced it with set_tied(), but it still does not work. The error is
INFO:/home/yuli23/huggingface/test_origin/transfer-learning-conv-ai/utils.py:Tokenize and encode the dataset INFO:train.py:Build inputs and labels INFO:train.py:Pad inputs and convert to Tensor INFO:train.py:Build train and validation dataloaders INFO:train.py:Train dataset (Batch, Candidates, Seq length): torch.Size([131438, 2, 280]) INFO:train.py:Valid dataset (Batch, Candidates, Seq length): torch.Size([7801, 20, 184]) Traceback (most recent call last):   File "train.py", line 251, in <module>     train()   File "train.py", line 230, in train     tb_logger = TensorboardLogger(log_dir=None)   File "/home/yuli23/huggingface/testvenv/lib/python3.6/site-packages/ignite/contrib/handlers/tensorboard_logger.py", line 355, in __init__     self.writer = SummaryWriter(log_dir=log_dir)   File "/home/yuli23/huggingface/testvenv/lib/python3.6/site-packages/tensorboardX/writer.py", line 254, in __init__     self._get_file_writer()   File "/home/yuli23/huggingface/testvenv/lib/python3.6/site-packages/tensorboardX/writer.py", line 310, in _get_file_writer     self.file_writer = FileWriter(logdir=self.logdir, **self.kwargs) TypeError: __init__() got an unexpected keyword argument 'log_dir'

If I want to train it with gpt2, I think the only parameter I should set is --model_checkpoint="gpt2", and first is there is no set_num_special_tokens method in modeling_gpt2, and I replaced it with set_tied() in train.py, but I got some type errors.
TypeError: init() got an unexpected keyword argument 'log_dir'
I did install all the requirements and I use pytorch = 0.4.1, thanks for your explanation.

I'm running into similar problem!

Oh yes you are right, gpt2 depend on a PR of pytorch-pretrained-bert (https://github.com/huggingface/pytorch-pretrained-BERT/pull/597) which is not merged and released yet. I have to finish cleaning up the test for it.
If you want to use it in the meantime you can install pytorch-pretrained-bert from source like this:
git clone https://github.com/huggingface/pytorch-pretrained-BERT.git
cd pytorch-pretrained-BERT
git checkout attention
pip install -e .

It should work

This problems occurs for both gpt2 and openai-gpt. I did checkout to attention branch but I'm still obtatining similar problem:(

What is your exact error?

Traceback (most recent call last):
File "./train.py", line 250, in
train()
File "./train.py", line 229, in train
tb_logger = TensorboardLogger(log_dir=None)
File "/home/dial/pfb30/scripts/poly/env/lib/python3.5/site-packages/ignite/contrib/handlers/tensorboard_logger.py", line 355, in init
self.writer = SummaryWriter(log_dir=log_dir)
File "/home/dial/pfb30/scripts/poly/env/lib/python3.5/site-packages/tensorboardX/writer.py", line 254, in init
self._get_file_writer()
File "/home/dial/pfb30/scripts/poly/env/lib/python3.5/site-packages/tensorboardX/writer.py", line 310, in _get_file_writer
self.file_writer = FileWriter(logdir=self.logdir, **self.kwargs)
TypeError: init() got an unexpected keyword argument 'log_dir'

You should update to the latest version of pytorch ignite (this change to tensorboardX was included here)

I'm unable to train with GPT-2 since the class defined here misses the function set_num_special_tokens.

You should update to the latest version of pytorch ignite (this change to tensorboardX was included here)

I have the latest version of ignite (verified by trying to pip install it again on my Amazon Deep Learning AMI EC2 instance after doing source activate pytorch_p36). I still get the same error that @budzianowski is referring to.

Created an issue in the Ignite repo, it looks like we need to downgrade from tensorboardX 1.7 or install the latest ignite from master: https://github.com/pytorch/ignite/issues/534

@thomwolf in train.py, you'll have to change this line:
checkpoint_handler = ModelCheckpoint(tb_logger.writer.log_dir, 'checkpoint', save_interval=1, n_saved=3)

to
checkpoint_handler = ModelCheckpoint(tb_logger.writer.logdir, 'checkpoint', save_interval=1, n_saved=3)

This is because in the latest version of tensorboardX (not in PyPI, in GitHub master branch), they've renamed log_dir to logdir.

Thanks for help, now it's up and running for me talking nicely!

Oh yes you are right, gpt2 depend on a PR of pytorch-pretrained-bert (huggingface/pytorch-pretrained-BERT#597) which is not merged and released yet. I have to finish cleaning up the test for it.
If you want to use it in the meantime you can install pytorch-pretrained-bert from source like this:
pip uninstall pytorch-pretrained-BERT
git clone https://github.com/huggingface/pytorch-pretrained-BERT.git
cd pytorch-pretrained-BERT
git checkout attention
pip install -e .

It should work

@thomwolf can you merge to master from the attention branch and release this if it hasn't already been done yet? Thanks!

pip install tensorboardX < 1.7 works!

Should be fixed on master!


Upgrade tutorial tiles from old tilemaps into user's project

fixes https://github.com/microsoft/pxt-arcade/issues/2568
corresponding pxt-arcade PR: https://github.com/microsoft/pxt-arcade/pull/2727
The issue was when we initiate the tilemap block, we try to decode all the tiles, but the tiles don't exist in the project. This will add all the custom tiles to the user's tileset -- it looks like this for Side Scroller:

Questions I have:

Should I be worried about adding another decompile in? Should I try to store what we had before and use that?
Is it best to separate out the XML upgrade logic into pxt-arcade? Or should I move it to here?

Try out the upload hereee: https://arcade.makecode.com/app/5f84aab6ae563167ac13981b277805cda8157511-9d50993b91
The tutorials we have with the old tilemaps are:

Barrel Dodger
Simple Extensions
Maze
Side Scroller
Setting the Scene
Breadcrumb Trail

ooo good point @jwunderl. Do we expect that there are third party tutorials that we don't want to break?

this issue has been fixed with a different change >< Closing this PR!

@livcheerful what change?

It does it in https://github.com/microsoft/pxt/blob/106dd01ff00d3605c4ae43e3007a27c0c99eb8f1/webapp/src/app.tsx#L1539
But I'm still not sure what the specific change is yet... I was worried that it was always fixed and I just didn't try to repro on beta? But then I wouldn't have seen it in my local build right?? I'm gonna hunt for it


Syntax for Creating variables is incorrect

For the page:  https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-event-quickstart
When the article instructed me to create the variables for site name, storage id and endpoint with the following lines:
sitename=<your-site-name>
storageid=$(az storage account show --name <storage_account_name> --resource-group <resource_group_name> --query id --output tsv)

endpoint=https://$sitename.azurewebsites.net/api/updates

I receive an error:
PS Azure:\> endpoint=https://$sitename.azurewebsites.net/api/updates
endpoint=https://$sitename.azurewebsites.net/api/updates : The term 'endpoint=https://$sitename.azurewebsites.net/api/updates' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ endpoint=https://$sitename.azurewebsites.net/api/updates
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (endpoint=https://$s\u2026tes.net/api/updates:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

I was able to determine what was wrong right away and I don't mean to be nit-picking, but this is an otherwise excellent tutorial that helped me learn about how I can use the EventGrid subscriptions.

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

ID: 0b3f0c06-5644-ae2a-71b8-f2c8572d3f15
Version Independent ID: 4dc6c7c6-13e6-0e47-9480-fa9f6bbb8c8a
Content: Send Azure Blob storage events to web endpoint - Azure CLI
Content Source: articles/storage/blobs/storage-blob-event-quickstart.md
Service: storage
Sub-service: blobs
GitHub Login: @normesta
Microsoft Alias: normesta

@srife Thanks for your question. We are checking on this and will respond to you soon.

@srife I tried the exact commands in my lab and I am not receiving any error. I would really appreciate it if you can elaborate on your findings? (How did you resolve it? If possible please include a screenshot)

Here is an image of what I saw while setting the variable and how I fixed it:

While creating this, I noticed that my Cloud Shell defaults to PowerShell, so I switched over to Bash and it worked just fine, although I did have to add the quotation marks:

I double checked the instructions at the top of the document on launching the Cloud Shell to see if I had missed a step to set the Cloud Shell environment and I saw that I did not.
I also had issues when typing in the multi-line commands using the "" to go to a new line without executing the command and I was getting an error.  I now realize that the reason is that I was in PowerShell.  It would have worked if I had used a "`" instead.  Here is an image.

I've recently taken a bunch of Microsoft Learn learning paths and modules and in those, they always were pretty specific about what environment you were writing scripts in.  In the steps "To run the code in this article" you may wish to add "Ensure the environment is set to Bash" on step 1.

@srife I understand. Thanks for including all the details. The title of the article and the introduction clearly talks about using CLI "Quickstart: Route storage events to web endpoint with Azure CLI". Azure CLI implies using all the commands in bash.
PS commands are in a completely different syntax and the parameters are passed in a different way. I will add a step to the doc to set in bash mode before running the commands.

I'm glad it was something simple.
Thanks for you efforts.


(feature) Copy an existing job

Trello card URL:
https://trello.com/c/tEijeDTC/562-hiring-staff-ui-user-can-make-a-copy-of-an-existing-job
Changes in this PR:
A hiring staff can make a copy of an existing published or pending job (not a draft or expired job).
The Published and Pending job tables now feature a Duplicate link.
Clicking this link calls dup on the original vacancy.
The copied vacancy is updated to have a draft status.
The copied vacancy's publish_on date is updated to today if the original vacancy's publication date is before today (because a new vacancy cannot have a publish_on date in the past).
The copied vacancy's title is also updated to be "Copy of {original vacancy job title}".
The hiring staff is then shown the Review page, from which they can edit or publish their new job.
The copied vacancy is a completely new record with a new id.

 Hiring staff UI: user can make a copy of an existing job

I have a couple of questions here:

Do we need to record the id of the vacancy a copied vacancy was copied from?
Do we need a new event logged, e.g. vacancy.duplicated?
Is the text OK for the Duplicate button and the error message I show if a vacancy cannot be copied?

This PR is dependent on the hiring staff UI changes, so if #668 goes through then this one should be placed on hold 😢


[RFC] Add a link to MacroLibX

Repo link: https://github.com/420verfl0w/MacroLibX/
MacroLibX is yet another MLX rewrite by 42Angoulême students, using SDL and Vulkan.
Its main difference with https://github.com/codam-coding-college/MLX42/ is that it aims in keeping the same API and tries to be a drop-in replacement, with only greater performance in added benefits.
It's still in its early stages, so I'm starting this issue as a draft and as a Request For Comments on both:

if it should be included in the extension, as I think diversity in MLX implementations would benefit people the most
if not, what would be the improvements necessary for its inclusion (if any)?

Hello,
I like the part where it aims to be a drop-in replacement to the standard minilibx.
Diversifying the choice in MLX libraries was never really the intention of the addition of MLX42. The requirement for adding a link to a project like this would be that the project must be accepted and deemed helpful by the staff of a handful of 42 campuses from all over the world. Both MLX42 and Find Peers, projects that are currently featured by Improved Intra, meet these requirements.
I suggest fleshing out your repository a tad bit more, getting rid of bugs and finding support from students, then come back to me and we can discuss more.


ESC should remove nimfix error annotations in source file

/cc @Varriount let me know if you need more details/description

My biggest concern is that this would conflict with other plugins. Plus, users can create their own key combos.
Given that there's already a command in the command palette, would this really add anything substantial?

how do I remove the red error annotations here?

@timotheecour The used can create a custom hotkey using the same command that is run from the command palette .

the same command that is run from the command palette

[ ] sorry for being thick... which command is that?

[ ] related question, where are these defined in code?
insert_snippet etc

grepping for it I only see:
Default (Linux).sublime-keymap:2:35:    {"keys": ["f12"], "command": "gotodef", "context":
Default (OSX).sublime-keymap:2:35:    {"keys": ["f12"], "command": "gotodef", "context":
Default (Windows).sublime-keymap:2:35:    {"keys": ["f12"], "command": "gotodef", "context":

but I'm not seeing it defined in py file in NimLime repo,  as follows:
class gotodef(sublime_plugin.WindowCommand):


Feature request: Pylint usability improvements

It would be useful to be execute pylint only for one (current) file (and bind a keyboard shortcut to it).
Also it would be nice to have error messages in error window (messages in messages) and not everything crammed into warnings.

Thanks for the suggestions!

Would love this feature also!
In the meanwhile, you could add a new "External Tools" in the Tools menu:
Title: PyLint
Command: C:\Python27\Scripts\pylint.exe (or whatever you use)
Arguments: --output-format=msvs $(ItemDir)$(ItemFileName)$(ItemExt)
Initial directory: $(ProjectDir)
Use Output windows: checked
Regards

Maybe it is possible to integrate with the existing Visual Studio features for code styles?


rPackages: fix Bioc pkgs needing internet connection

Description of changes
Added two remaining failing Bioc packages to skipping load check, because they try to access internet while testing package load upon installation.
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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

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

Could you make them discrete commits?

Okay, done


[Android] seek progress glitches on 8.0.0

Describe the bug
Hi!  I use the slider as a track progress bar for a music app. since updating to 8.0.1, seeking on the progress bar glitches the current point back to 0/sometimes back at times. v7 works fine.
To Reproduce
This is the repo, to build, do yarn; cd example; yarn; yarn start.
https://github.com/lovegaoshi/react-native-track-player/tree/bug/slider
Expected behavior
see description.
Screenshots
n/A
Please complete the following information:
Android, slider lib v8
Additional context
N/A

Can you provide a minimal reproducible example? Maybe on snack expo?

Seeing the same issue, and I believe it's a problem when using a controlled value prop.
I've made a demo on snack expo that shows the issue on both Android & iOS. As you drag the slider thumb back and forth, it fights over its position on the track between the actual value and another value (commonly 0).
https://snack.expo.dev/@jticknerfrogco/rn-slider-controlledvalue-issue?platform=android
As @lovegaoshi said, v7 works fine - it's just a problem in v8.

Thanks a lot for the feedback and example. I noticed that some parts of the code got missing during the refacto of v8. It should be solved in v8.0.2. Please report any issue you might encounter with it.

@Sharcoux Yep, working now on 8.0.2. Just FYI, I think you left some logging turned on in the 8.0.2 release. Seeing eventToValue logs flooding my console

tysm! im not quite well versed in snack, really appreciate the example and
fix!
On Wed, Oct 30, 2024, 1:56 AM Justin Tickner @.***>
wrote:

@Sharcoux https://github.com/Sharcoux Yep, working now on 8.0.2. Just
FYI, I think you left some logging turned on in the 8.0.2 release. Seeing
eventToValue logs flooding my console
—
Reply to this email directly, view it on GitHub
https://github.com/Sharcoux/slider/issues/101#issuecomment-2446228663,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZMOVVXBWHWDLOTS4ISJMD3Z6CNL3AVCNFSM6AAAAABQT4TDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBWGIZDQNRWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Table(react-aria-components): [data-hovered] does not work for <Row/>

🐛 Bug Report

Documentation mentions [data-hovered] selector for <Row/>. In reality, it does not work (the data attribute is not applied)
🤔 Expected Behavior

data-hovered attribute should be applied when row is hovered
😯 Current Behavior

data-hovered is not applied
💻 Code Sample

https://codesandbox.io/s/objective-field-7mq4g6?file=/src/App.js
in the example, I used data-focus-visible which works as expected when row is focused. data-hovered is also used, but styles are not applied when row is hovered with a mouse pointer.

I believe the hover state only applies when the row is actually interactive, e.g. selectable or actionable. If you add selectionMode or onAction props to your sandbox I do see the hover state. I think this was intentional so users could know when a row is pressable. You could always use the regular CSS :hover pseudo I guess. Not sure how we'd make this behavior changeable otherwise.

I believe the hover state only applies when the row is actually interactive, e.g. selectable or actionable. If you add selectionMode or onAction props to your sandbox I do see the hover state. I think this was intentional so users could know when a row is pressable. You could always use the regular CSS :hover pseudo I guess. Not sure how we'd make this behavior changeable otherwise.

Ah! Got it. That makes sense, thank you. In that case, I'd maybe suggest mentioning in the docs. It might save some time for others in the future.

It's particularly troublesome when using the tailwind-css-react-aria-components plugin without a prefix, as it overrides the default tailwind hover selector, but doesn't work due to the data-rac being present but the data-hovered never being added unless you have a selectionMode other than none.

Use the prefix option of the Tailwind plugin so that hover: is native and rac-hover: is RACs version.

We may also in the future add a prop to enable hover states even when an element is non-interactive. We discussed changing the default behavior, but it introduced more complications such as inconsistency between hover and press states, what to do with read only components, etc. Hover states on non-interactive elements seem to be more of an edge case than the common case (table rows being a more prominent example), so we'd rather keep that as the default for now.

Hello!
I believe that it's the exact same problem with Tags in a TagGroup. I try to use the tailwind hover: selector but it does not work due to the data-rac attribute.
Adding selectionMode="single" to the TagGroup does not seem to help but the [&:hover]: trick mentionned above by @devongovett works! 🙏
Surprisingly, the data-hovered attribute is added in the tags documentation examples... not sure what differs.
FWIW, my use-case is to use the href: <Tag href="..."> so there should be no selectionMode anyway.
The same issue on table rows and tags seem to be two sides of the same coin, so I did not open a specific issue, let me know if you'd rather want me to open another issue.
Best


Source member list refresh at top refreshes all current source files. Could be slow.

Is there a way to only refresh the selected source file in case a developer has several source files in their list ?
Ex: Click on source file and then click the refresh icon at the top.
If this change is made title it: "Refresh Selected Source File" instead of "Refresh Member List"
Another option would be to just re-add the Right-Click option at the source file level to just refresh the selected source file.
Either way the idea is to NOT have to refresh all members across all my source files in the list all the time.

As far as I could tell there isn't a particularly easy way or obvious way to do it. I will leave it open.

You had a right-click before at the source file level.   Was that just triggering a refresh of entire list for all source files ?  I'm guessing  you are calling the refresh code for each source file., but I didn't dig in and look.

@richardschoen Even the right-click option that was there before was refreshing the entire menu.

@worksofliam @richardschoen I have a little attempt to add this functionality. It involves a bit of in-memory caching so it might not be very performant. But, I think I was able to get it working with this commit.
Summary:

when building tree view of members, check cache for key 'LIB/SPF'

If exists, pull from cache
else, query IBM i for member list

refresh at top of member browser works as before
right click context menu "Refresh Source File" added

performs targeted refresh on 'LIB/SPF', while reading other member lists from cache

changed refresh logic in individual member commands if autorefresh enabled

create, delete, rename, updateText performs targeted refresh on LIB/SPF
copy does targeted refresh on source and destination

I still want to test it out more because my knowledge of the vscode extension API and JavaScript as a whole is lacking.
So, I'm afraid it may have side effects I'm not aware of yet.

@barrettotte That change makes a lot of sense, actually. I like it.
Whenever you feel ready, make a PR and I'd love to take it for a whirl. Thanks a lot.

Thanks @barrettotte for getting this one!


Open Source Compatibility check

Is there an easy way to utility to check if Delta code written on Databricks is Delta Open source compatible.
This can be useful in environments which dev/test in cloud but production needs to be on-premise.
Curious to hear thoughts on this.

This is a good question. Nothing like this exists, though I will note you can run OSS Delta Lake in the cloud (just not on Databricks).
One thing I will say is that our long-term goal is for OSS Delta Lake and Managed Delta Lake to be 100% API compatible. I don't believe that lock-in where you cannot run you application outside of a given platform without rewriting it is a good model and that was a big part of our motivation to create this open source project.
This is not true today as we need to improve Apache Spark's ability to plug-in custom implementations of DML amongst other things, but we are actively working towards this.

@marmbrus appreciate the response !
Looking forward to ADLS/S3/Minio support and eventual 100% API compatibility between managed and OSS delta lake.

Our internal (Databricks Delta) and external (OSS Delta) ensures that we maintain compatibility between any tables written any where to compliant with the protocol, and therefore readable anywhere. Whenever there are protocol change that are incompatible with previous version of delta lake, both DBR versions and Delta OSS release versions, then we track those changes as reader/writer protcol versions in the protocol, and handle them appropriately. Further documentation specific to such features will clarify the compatibility.
Closing this issue.


Fixing sqlserver connector

@ChengJie1053  - try approving the workflow again - apache master has the code that passed all tests and I've just merged it.

@ChengJie1053 - try approving the workflow again - apache master has the code that passed all tests and I've just merged it.

Ok, thank you


[Update Snap] Hedera, SilentShard

Checklist
All items in the list below needs to be satisfied.

[ ] Is the summary of the change documented in this ticket?
[ ] Has a MetaMask Snaps team member reviewed whether the changes need to be vetted?
[ ] If there are changes that need to be vetted, attach a description and the relevant fixes/remediations to this issue.
[ ] The corresponding pull request in this repo has been merged.

Hedera

Change Summary:

Added a new API to create a smart contract
Added a new API to update a smart contract
Added a new API to delete a smart contract
Added a new API to call a smart contract function
Added 3 new APIs to get smart contract function, bytecode and info
Added a new API to execute ethereum transactions on the Hedera network
Some bug fixes and optimizations
Updated the max query payment to be 5 Hbar so the queries don't fail

Source Diff: https://github.com/hashgraph/hedera-metamask-snaps/compare/v0.3.1...v0.4.2
Version to be allowListed : 0.4.2
Version to be delisted : 0.3.1

SilentShard

Change Summary: Fix for an issue being caused to the Silent shard snap users on the firefox browsers
Source Diff: https://github.com/silence-laboratories/silent-shard-snap/compare/1.2.8...1.2.9
Version to be allowListed : 1.2.9
Version to be delisted : 1.2.8 , 1.2.7, 1.2.6


Invalid namespace

I'm trying to connect to my webserver via laravel echo but got the following response
32:44/socket.io,"Invalid namespace"

I'm using the following configuration
location /socket.io {
	    proxy_pass http://<IP_ADDRESS>:6001;
	    proxy_http_version 1.1;
	    proxy_set_header Upgrade $http_upgrade;
	    proxy_set_header Connection "Upgrade";
	}

And laravel echo configuration
window.io = require('socket.io-client');

window.Echo = new Echo({
    broadcaster: 'socket.io',
    host: 'https://my-site.com/socket.io',
    auth: {
        headers: {
            'Authorization': 'Bearer some token here'
        }
    }
});

window.Echo.join('channel').joining((user) => {
    console.log('joining');
}).leaving((user) => {
    console.log('leaving');
})

32:44/socket.io,"Invalid namespace"
Well, it means the namespace is not valid
use this instead host: 'https://my-site.com',


[SUPPORT] how to config hudi table TTL in S3? The table_meta can be separated into a directory?

How to configure TTL policy in hudi data table? Can the metadata （.hoodie ）be separated into a directory?
Only configure the appropriate TTL for the data directory, so that data cleaning can also use hierarchical storage and different life cycles, and the data can also be automatically cleaned by relying on the object storage service, and there is no cost.
EG:
s3://big-data-eu/hudi/data/bi_ods/table_name/dt=20231211/data
< 30 days STANDARD S3

30 days delete by TTL with no cost.
=================================

< 15 days STANDARD S3

15 days GLACIER_IR
105 days  delete by TTL with no cost.

s3://big-data-eu/hudi/table_meta/bi_ods/table_name/.hoodie
As mentioned above, if there are many data tables under the data storage and the storage periods are the same, I can just configure the storage period for the directory and rely on the object storage to automatically clean up the historical data at no cost.
EG:
s3://big-data-eu/hudi/data/30days/bi_ods/table_name/dt=20231211/data
< 30 days STANDARD S3

30 days delete by TTL with no cost.

s3://big-data-eu/hudi/data/90days/bi_ods/table_name/dt=20231211/data
< 30 days STANDARD S3
30days < 90days GLACIER_IR

90 days delete by TTL with no cost.
....
=================================

< 15 days STANDARD S3

15 days GLACIER_IR
105 days  delete by TTL with no cost.

s3://big-data-eu/hudi/table_meta/bi_ods/table_name/.hoodie

@zyclove Dont think if there is a way to point the different directory outside table directory OR having any such TTL configuration.

@zyclove Dont think if there is a way to point the different directory outside table directory OR having any such TTL configuration.

Why can't we consider storing metadata and data files independently? The data TTL can be more flexible and convenient. Can it be mentioned and submitted in subsequent planning meetings? Thanks

May be a good idea but i guess we may have already explored. Adding @nsivabalan @yihua @danny0405 @codope

so that data cleaning can also use hierarchical storage and different life cycles
can you elaborate more detail about this? I working with partition TTL management and hope to understand your need!


Create a box layout for the audio component

Fixes

Fixes #228 by @zackkrida
Description

This PR uses the AudioTrack composability introduced in #207 to provide a Box layout for the audio.
Technical details

The box layout is currently in the design phase, and there are certain feedback points to address, but this PR serves as a PoC for the composability of the track.
Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@dhruvkb is the global audio player work happening here? that makes sense if so, just curious

@zackkrida no that's happening in the global_audio branch, but there are some good developments there that I wanted to use in this branch.

Also, this PR is very much a draft, the box design has changed a lot from this implementation and the states aren't documented in detail in Figma. So this will be WIP for the foreseeable future.

@dhruvkb @panchovm Just noting here that the box states seem to be better documented now, and that this PR will also likely change based on the work in #460.

I think I'll just close this and combine the work into #504.


[Translate ru] Fundamentals -> toc_base

Check out a review request at GitLocalize

Thanks for the contribution! Due to the way DevSite works, we can't translate _book.yaml, _project.yaml, _toc.yaml, _footer.yaml, _redirects.yaml, _upper-tabs-*.yaml files. I'm going to close this for now. Thanks


Issue with masking and backspace

Say you have something like 123-45-678. The dashes are the masked characters. If you delete until 123-45-6__ and then hit backspace again, your cursor will end up before the 2nd dash. If you try and type anything from that position, nothing will happen.

+1, the cursor needs to be moved to after the mask symbols

Any news?

+1, also it's not very comfortable to me when I pressing at mask before input (for example, for mask +7 *** I could click between + and 7)

Hi guys. I have the same trouble with this library and fixed it. I hope after review this pull will be merged. Any way you can check the source code and take it into your project.


BUG:

Describe the bug:

Link to the blitz that caused the error
https://stackblitz.com/edit/node-wk8pgg?file=package-lock.json
Steps to reproduce:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior:

Version of webcontainer:
Hash: 57be275669708b1d42e233d60c80159bef577631
Screenshots:

Desktop (please complete the following information):
Browser name  = Chrome
Full version  = 90.0.4430.212
Major version = 90
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36 OPR/76.0.4017.154
performance.memory = {
"totalJSHeapSize": 54467877,
"usedJSHeapSize": 46405125,
"jsHeapSizeLimit":<PHONE_NUMBER>
}
Additional context:

@YukeshM could you provide more information and fill in the required fields as well as a decent title? Otherwise it's hard for us to help you out.

@YukeshM could you provide more information and fill in the required fields as well as a decent title? Otherwise it's hard for us to help you out.

here I found the bug

Thanks for the screenshot, unfortunately this is not enough information. When you click the report bug button we expect everyone to describe what bug you encounter, steps to reproduce the issue and last but not least, a decent issue title.
I'm not on my computer right now so I will have a look if I can quickly see if there goes something wrong when I open the project.

here after I will describe the issue sir, thanks for your reply


Implement rollback for VM Save To Template

Author Name: Tino Vázquez (Tino Vázquez)
Original Redmine Issue: 3881, https://dev.opennebula.org/issues/3881
Original Date: 2015-07-21

In case of error or VM deletion

Using #1326 to track this


Localisation

String Localiser.internationalise(String key)
String Localiser.process(String template) - Templater.process(...) where the placeholder resolver is Internationaliser::localise (#45).
Default keys:

enchanted.error.invalid-usage
enchanted.error.invalid-sender
enchanted.error.internal-error

I actually think this implementation is too out of the scope of Enchanted. Enchanted is a command library and the only localisation needed is for error messages.
This should be as simple as a CommandExecutor.sendLocalisedMessage(String localisedMessasge) method, and possible a CommandResult as well.


How to migrate to 3.0 to 3.1 ?

If i migrate the package version from 3.0.x to 3.1.x, I cannot access to the previous database data.
Steps to Reproduce

Setup a database with Isar 3.0 :

isar = await Isar.open(
      [MySchema],
);

Fill the database with data
Migrate the package from 3.0.x to 3.1.x
As the backlog mentioned it is now required to explicitly specify the directory attribute :

final dir = await getApplicationDocumentsDirectory();
isar = await Isar.open(
      [MySchema],
      directory: dir.path,
);

With this modification, the isar database does not reference the old database. If I downgrade the package version and if I remove the directory attribute I can reference again my original database.
There is no migration guide with this breaking change, so my question is: with Isar 3.1.x, how to reference my database created with Isar 3.0.x ?
Details

Platform:  Android Emulator on Windows / Pixel 7.
Flutter version: 3.7.10.
Isar version: 3.1.0

[x] I searched for similar issues already
[x] I filled the details section with the exact device model and version
[x] I am able to provide a reproducible example

I'd check where your old database was stored and set the directory to the same location 🙂

I'm also having this issue

@simc In 3.0.x the default directory was nsdocumentdirectory for iOS and getDataDirectory for Android but even when I use final dir = await getApplicationDocumentsDirectory(); which says in the documentation:

Example implementations:
NSDocumentDirectory on iOS and macOS.
The Flutter engine's PathUtils.getDataDirectory API on Android.

But it still results in not showing the previous data.

@Romain-Guillot  I think I figured it out. I reverted back to 3.0.5 and I printed out the original directory of my Isar instance and it says it was the ApplicationSupport directory.
I upgraded back to 3.1.0 and I pointed to the parent of the application support directory and everything is working now:
final dir = await getApplicationSupportDirectory();
final isar = await Isar.open(
        [YourSchema],
        directory: dir.parent.path);

Thanks a lot for your investigation @alexrabin, it seems to work on my devices.

@simc Can you add this into the documentation for the upgrade guide form 3.0.X to 3.1.X?

Thanks a lot, @alexrabin for your effort in figuring this out!
In my case:
Isar 3.0.5 --> Isar 3.1.0+1
Flutter 3.3.10 --> Flutter 3.7.12
Just using the application support directly works on both Android and iOS:
final Directory isarDbStorageDirectory = await getApplicationSupportDirectory();

final Isar isar = await Isar.open(
  [YourSchema],
  directory: isarDbStorageDirectory.path, // Android ✅ & iOS ✅
);

Maybe someone else runs into the same scenario.

For Windows, what should be the directory?


Unittest for listFileParents(block_name, child_parent_id_list=None)

Unite tests should include both client side tests and server side tests.
API listFileParents( child_block_name, child_lfn_list)
returns [{child_parent_id_list: [(cid1, pid1), (cid2, pid2), ... (cidn, pidn)]}]
Negative tests: if missing any of the inputs, the API should failed.
input: single item of LFN list and single dataset.
input: long list of LFN and single dataset.
input: long list of LFN and long list of datasets.
All input tests should insert and read back to compare them. The test fails when they are different.

@yuyiguo, I create the separate issues for unittest. You can assign this to me.
What are we comparing here? RunLumis?

All input tests should insert and read back to compare them. The test fails when they are different.

To test correctly, we need to insert child and parent files with run lumis with existing APIs, with correct run lumi information and api need to check whether it gives the same parents.

Yuyi, can you point me which unittest need to be updated?
I can see Client side
https://github.com/dmwm/DBS/blob/master/Client/tests/dbsclient_t/unittests/DBSClientReader_t.py
But server side there are multiple places.
under business_t,  dao_t, web_t
Also read unittest, I didn't see the code for populating the data (in Client code), Could you point me the code for insert if it need to be inserted.

all server side tests are done at web_t level.

Negative tests: if missing any of the inputs, the API should failed.
input: single item of LFN list and single dataset.
input: long list of LFN and single dataset.
input: long list of LFN and long list of datasets.
All input tests should compare the result with listFileParents(logical_file_name). The test fails when they are different.

Could you point me how you currently insert data for unittest? It seems none of the unittest I see compares the data, is there a reason for that?

Stop by my office, I can show you how to do the DBS unit tests.
From: ticoann<EMAIL_ADDRESS>Reply-To: dmwm/DBS<EMAIL_ADDRESS>Date: Thursday, July 12, 2018 at 10:00 AM
To: dmwm/DBS<EMAIL_ADDRESS>Cc: Yuyi Guo<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [dmwm/DBS] Unittest for listFileParents(listofchildLFNs, listofParentDatasets) (#571)
Could you point me how you currently insert data for unittest? It seems none of the unittest I see compares the data, is there a reason for that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dmwm_DBS_issues_571-23issuecomment-2D404542725&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=8bursUuc0V63OwREQMBG2Q&m=levdQ-zqT8wCt0oPBkcJqZCPYxKCY3fA0xQipwcTyyI&s=slrDMCLui2dF8pDAjXbK5OEkRDEtn434DSRpRRZxETo&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABsXTtoM7SBcuyMRBw1uBrfXUcGYrmzyks5uF2SBgaJpZM4VM8kd&d=DwMCaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=8bursUuc0V63OwREQMBG2Q&m=levdQ-zqT8wCt0oPBkcJqZCPYxKCY3fA0xQipwcTyyI&s=VQQfHXd91V9wzFOZcm5QvhuyT0xPSiv0sC4od-Upfn0&e=.

@ticoann
The tests are needed on both server and client sides. Some tests have the only server side  and the others are only at client side. The server side tests are  as important as the client side because we can test without starting a new server.  They are very useful. Could you please fill in the missing tests on both sides?
The below is what I see that new tests need to create or improve for the existing one.

DBSClientWriter.insertFileParents: need negative tests on missing required inputs.
DBSWriterModel.insertBulkBlock: need negative tests on giving both file and dataset parentages.
Validation tests need to compare child-parent pair, not only the list length.


dlog: Fix issue where the fast-logging broke backward compat

This PR is on top of https://github.com/datawire/dlib/pull/34, go merge that first.

https://github.com/datawire/dlib/pull/28 changed the Logger interface, breaking any existing implementors of the interface.  That's not OK.
So revert that interface (and add a comment about how it's frozen), and add an opt-in OptimizedLogger interface for Jose's optimizations.

Since I consider the non-optimized logger a design flaw

I don't think I agree. I think keeping the required-interface minimal and letting dlog handle as much complexity as it can is a good thing.

A 2.0 version would be good for three reasons.

It wouldn't require this somewhat cludgy solution with casts everywhere.
It would give the 1.2 implementers a chance to simply stay put while at the same time give them an incentive to improve their implementation.
It would give Telepresence a version that doesn't break us.

My motivation for calling the old version flawed is that unnecessary string manipulation is expensive and the added complexity is very trivial. In fact, in most cases it's just delegated to another log implementation.


Lazily create module.[[ImportMeta]] object

Previously, this object was created on every module
instantiation. Instead, this patch lazily creates the object only when
import.meta is used.
The previous behavior was not observable to JavaScript, but was
observable through the embedding API.

@domenic ptal

That's neat! I lazily create import.meta in @std/esm too!

Do we need any of this complexity around import.meta being lazily loaded? Everything can be lazy loaded if it's not observable to script.

@bterlson my first reaction was to leave things as-is, too. But on balance this patch seems to make the spec easier to read, since it centralizes all import.meta stuff in one place instead of intruding into STMR instantiation and requiring other subclasses of MR to do their own [[ImportMeta]] creation. So, given that it's basically an editorial change anyway, I thought it'd make sense to accept.


Separated templates and directory list

Pull Request Description
Closes https://github.com/enso-org/cloud-v2/issues/490:

Make templates collapsible
Add scroll-based shadow to templates
Move scrollbars from body to templates and directory listing

Important Notes
None
Screenshots/Screencasts
screen-recorder-thu-jun-08-2023-19-46-49.webm
"New blank project" button:

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

@indiv0 could you QA this?

Could we have an "add new empty project" button in collapsed mode? Like in Excel:

And will this state be remembered between sessions?

 { [TRACE_ALL]

❌ Potential issue w/ DOM validation, see screenshot

Known issue, not introduced in this PR, fixed in a separate PR per this discussion

✅ Nodes in Cloud project are visible
✅ [INFO] logs appear in console
✅ Logs appear with console.log("Hello")
✅ [FRP] logs appear in the output
✅ IDE rebuilds for edits in app/gui/**/*.rs
✅ IDE does not reload for edits in app/gui/**/*.rs

Expected behaviour per this discussion

✅ IDE rebuilds for edits in app/ide-desktop/lib/dashboard/src/authentication/src/**/*.tsx
✅ IDE does not reload for edits in app/ide-desktop/lib/dashboard/src/authentication/src/**/*.tsx

Expected behaviour per this discussion

Screenshot

Scenario 3
ENSO_BUILD_TARGET=dir \
    ./run ide build \
    --skip-wasm-opt \
    --wasm-profile=dev \
    --backend-source=release \
    --backend-release=nightly \
    --skip-version-check \
    --profiling-level=objective \
    --wasm-log-level=info \
    --wasm-uncollapsed-log-level=info
./dist/ide/mac-arm64/Enso.app/Contents/MacOS/Enso \
    -feature-preview.new-dashboard \
    -debug.dev-tools \
    -debug \
    --inspect=5858 \
    -authentication

Enabled logs at https://github.com/enso-org/enso/blob/cfb2f2916eb1d81f521c5af238e42c2b227f65d3/app/gui/view/graph-editor/src/component/visualization/container.rs#L128 by replacing:

ensogl::define_endpoints! {

with:
ensogl::define_endpoints! { [TRACE_ALL]

✅ Nodes in Cloud project are visible
✅ [INFO] logs appear in console
✅ Logs appear with console.log("Hello")
✅ [FRP] logs appear in the output

Screenshot

Scenario 4
cd app/ide-desktop
npm run build-dashboard

✅ Command ran successfully

Screenshot

Scenario 5
cd app/ide-desktop
npm run watch-dashboard

✅ Command ran successfully
✅ GUI at http://localhost:8080 opens
❌ Potential issue w/ DOM validation

Known issue, not introduced in this PR, fixed in a separate PR per this discussion

❌ Potential issue w/ serviceWorker.js

Not an issue, red-herring that will be fixed in this PR, per this discussion

✅ IDE does not rebuild for edits in app/gui/**/*.rs
✅ IDE rebuilds for edits in app/ide-desktop/lib/dashboard/src/authentication/src/**/*.tsx
✅ IDE reloads for edits in app/ide-desktop/lib/dashboard/src/authentication/src/**/*.tsx
❌ Potential issue w/ images for templates not loading (e.g. http://localhost:8080/visualize.png)

Known issue, not introduced in this PR, per this discussion

✅ Nodes in Cloud project are visible

Screenshot

drive section having scroll shadows: the figma design didn't have them so i didn't add them - @PabloBuchu do you think it should be added?
new blank workbook: yeah it should probably be here. will add sometime
templates collapsed state is the same in both local and cloud view: intentional - while your point is valid, i feel like if they don't want to use templates for local dev they probably don't want to use templates for remote dev?
glsl error: will try reproing sometime

new blank workbook: Could we open an issue to track this?

Failed to open Cloud project due to failure to open .glsl files
@indiv0 Unfortunately I can't repro - you might have to do some further investigation? Or it might just be that that specific version is missing some shaders in the S3 bucket

I do get different errors on FF though:

But given that they come from Rust I don't think this PR is the cause

Attempted a re-QA of scenario 5 to reproduce the .glsl issue. Issue did not reoccur but I ran into the same selection menu issues reported in #7061, so proper QA is blocked until that issue is resolved. Here is a screenshot with error logs for reference:

I have 15' mac and the templates looks like this.. (the 10px scroll looks nasty imho).. also there is no margin / padding around... @somebody1234 even on your first screen recording I see such small scroll... can we somehow make it to fit the screen and make the scroll appear if the user display is smaller?
https://github.com/enso-org/enso/assets/2855109/4daeb1f6-0f88-4b87-9a28-4a5f930bbbd4

@indiv0 @somebody1234 regarding the scenario 5 I was able to open cloud project and do stuff so I think the bug was fixed.
waiting for the fix for templates and then we could merge

When templates are collapsed, I don't think we need to create a separate button for new project, as there is already + button next to the "projects" header.

i use the "screen recorder" chrome extension, but the issue is probably that it's stored as a webm. it's easy enough for me to convert to mp4 though

@somebody1234  Why suddenly templates are narrowed? Is this issue only on my machine? Also as Wojtek said please remove this New blank project button

@PabloBuchu first issue: was on develop but not here. fixed after merge
second issue: "new project" button removed.

QA 🟢 @somebody1234 please merge once the CI is completed


Animated 'useNativeDriver' was not specified

I tired to solve this and found answers that we need to explicitly set this value but i don't see where where to set this value

Pull request to fix this: https://github.com/jpapillon/react-native-carousel-pager/pull/24


Surplus Limb adds about 200SP to base spell power for ele shaman

Describe the bug
Adding Surplus Limb adds Surplus spell power
To Reproduce
Steps to reproduce the behavior:

Go to 'Ele Shaman sim
Scroll over Spell DMG magnifying glass
See base spell power
Click on 'off hand'
Select Surplus Limb
Look again at Spell DMG magnifying glass.
Enjoy 210 extra Spellpower!

Expected behavior
A clear and concise description of what you expected to happen.
Sim Links and Screenshots
If applicable, add links to your sim settings or screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Good catch! It thought that Surplus Limb was an offhand weapon and was applying flametongue weapon to it. I should probably just disable offhand weapons at all if you don't have the talent.
Fixed in: https://github.com/wowsims/wotlk/pull/339


Pin pyopenssl

Pinned pyopenssl==21.0.0 in kowalski/requirements_ingester.txt, otherwise pymongo==3.12.0 cannot be used with python==3.7

@virajkaram Why are there 50 some commits?

closing due to messed up commit history, will reattempt.


Disabling SmoothMode for some HTML classes may solve typing lag issues in large projects

It is known that using SmoothMode in the following programming language environments can cause lag issues when typing and popping suggestions:

Rust+rust analyzer
C #+ NET 8.0+C # Dev+C # extension
C #+Unity+C # Dev+C # extension
F #+ NET 8.0+C # Dev+Ionide

SmoothMode will work properly in the following programming languages:

C
Haskell

Based on experience, lagging may be related to suggestion pop windows. You can try turning off support for suggestion in SmoothMode to get a good typing experience.

This message was translated using machine translation. I apologize for any inappropriate expressions.

https://github.com/BrandonKirbyson/VSCode-Animations/assets/11296891/47916609-c3f2-4392-9261-00b59421f8cb

I suggest SmoothMode not to use the "Exclude" method to specify the classes to be animated, but to use the "Include" method to specify which classes to be animated, so that both performance and animation performance are more controllable.

Thank you for all the information, I tested it out and turns out smooth mode is already fully disabled in the suggestion popups. It is most likely this is then caused because of so many other elements having css transitions. I'll keep looking into this but that's just a quick update.

I just published a new version that fixed a couple other things, could you maybe check if it's working any better for you?

I just published a new version that fixed a couple other things, could you maybe check if it's working any better for you?

Thank you for your efforts. v2.0.2 did not solve the problem of typing lag.

Ok thanks for checking that, I'll keep looking into it.

This issue seemed to have been non-existent or relatively minor in the previous version of vscode, until it suddenly became more severe after a certain version was released later.

In version 2.0.2, lag seems to have been alleviated.


(Feature Request) Add bulk change for project Language Version

Hi,
I got into a little trouble in our company, when we use .NET 4.0 on all of our projects, but VS2015 by default builds in C# 6.0. When I committed my code, build server failed, because I accidentally used one C# 6.0 construct (object initializer).
So it would be really nice, if your Migrator could also bulk set the Language Version of all projects.

Thanks!

I'll try to do that as part of redesign to WPF window

https://docs.microsoft.com/en-us/visualstudio/extensibility/creating-and-managing-modal-dialog-boxes?view=vs-2015&redirectedfrom=MSDN


fix: Update property assignment in CodeGenerator

Description
Fixed an issue where we did not use the correct property for generating the binding code. We used the Property name instead of the original name of the uxml. This caused the binding to fail.

This pull request is included in version 1.5.2