Add bootstrap tools for aarch64-darwin and add to supportedSystems

Motivation for this change
Fully enable aarch64-darwin, follow up to #105026.
Bootstrap tools come from https://github.com/NixOS/nixpkgs/pull/105026#issuecomment-843389914. The hashes that nix uses for executable files is not the same as the sha256 of their contents, so the executable tools do not match the comment. I applied the regular TOFU approach.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I don't understand why my hashes don't match what you put here, do you know whats up?
Maybe we could use the hashes I provided here? #105026 (comment)

IIUC when nix hashes an executable file it uses a nested file format to encode the executable metadata, which affects the hash. It should be the difference between nix-hash $file and nix-hash --flat $file. The matching hash is non-executable, so it’s a flat hash.

I confirmed most of the hashes here aren't right with nix-prefetch-url:
[grahamc@hyperchicken:~]$ (for f in bootstrap-tools.cpio.bz2  bzip2  cpio  mkdir  sh; do url="https://tarballs.nixos.org/stdenv-darwin/aarch64/20acd4c4f14040485f40e55c0a76c186aa8ca4f3/$f"; nix-prefetch-url "$url"; done; )
path is '/nix/store/cn4c1gcqd84v5ybx07kkspprd8w5nshx-bootstrap-tools.cpio.bz2'
1v2332k33akm6mrm4bj749rxnnmc2pkbgcslmd0bbkf76bz2ildy
path is '/nix/store/9xi1jm60gbi5wb2n3bnbimrjh8nka763-bzip2'
1c7a2civpwviwr917xrn0dxgch59c7ajs5va2b3qfga0ll70zcca
path is '/nix/store/as2w0c2g5rn7d9rmnqb4vnlx9drhbz3q-cpio'
1pay9iaj6332nb5ikw36ch0ds2c94s2jxfgxg22aaaqld0yaajwv
path is '/nix/store/v8gi3b5960xz6wh1qfqn6j7rvahzc2qp-mkdir'
0n3644mwpnqmc90ds1x8q0rhkasp1zcdlk3bm84749p0smrd654k
path is '/nix/store/1bxpipz2w1qqa1w442fprcjs17prm0hj-sh'
132qg34xrl56isis2qx9q779znig16flg1yisfapqg6y4kc71fxl

[grahamc@hyperchicken:~]$ (for f in bootstrap-tools.cpio.bz2  bzip2  cpio  mkdir  sh; do url="https://tarballs.nixos.org/stdenv-darwin/aarch64/20acd4c4f14040485f40e55c0a76c186aa8ca4f3/$f"; nix-prefetch-url "$url"; done; )
path is '/nix/store/cn4c1gcqd84v5ybx07kkspprd8w5nshx-bootstrap-tools.cpio.bz2'
1v2332k33akm6mrm4bj749rxnnmc2pkbgcslmd0bbkf76bz2ildy
path is '/nix/store/9xi1jm60gbi5wb2n3bnbimrjh8nka763-bzip2'
1c7a2civpwviwr917xrn0dxgch59c7ajs5va2b3qfga0ll70zcca
path is '/nix/store/as2w0c2g5rn7d9rmnqb4vnlx9drhbz3q-cpio'
1pay9iaj6332nb5ikw36ch0ds2c94s2jxfgxg22aaaqld0yaajwv
path is '/nix/store/v8gi3b5960xz6wh1qfqn6j7rvahzc2qp-mkdir'
0n3644mwpnqmc90ds1x8q0rhkasp1zcdlk3bm84749p0smrd654k
path is '/nix/store/1bxpipz2w1qqa1w442fprcjs17prm0hj-sh'
132qg34xrl56isis2qx9q779znig16flg1yisfapqg6y4kc71fxl

[grahamc@hyperchicken:~]$ for f in bootstrap-tools.cpio.bz2  bzip2  cpio  mkdir  sh; do printf "%s: %s\n" "$f" "$(nix-hash --flat --base32 --type sha256 /nix/store/71mly5hl2qxmm1fmp1jwn2qwbdbwxpvs-stdenv-bootstrap-tools-aarch64-apple-darwin/on-server/$f)"; done
bootstrap-tools.cpio.bz2: 1v2332k33akm6mrm4bj749rxnnmc2pkbgcslmd0bbkf76bz2ildy
bzip2: 1c7a2civpwviwr917xrn0dxgch59c7ajs5va2b3qfga0ll70zcca
cpio: 1pay9iaj6332nb5ikw36ch0ds2c94s2jxfgxg22aaaqld0yaajwv
mkdir: 0n3644mwpnqmc90ds1x8q0rhkasp1zcdlk3bm84749p0smrd654k
sh: 132qg34xrl56isis2qx9q779znig16flg1yisfapqg6y4kc71fxl

[grahamc@hyperchicken:~]$ for f in bootstrap-tools.cpio.bz2  bzip2  cpio  mkdir  sh; do printf "%s: %s\n" "$f" "$(nix-hash --base32 --type sha256 /nix/store/71mly5hl2qxmm1fmp1jwn2qwbdbwxpvs-stdenv-bootstrap-tools-aarch64-apple-darwin/on-server/$f)"; done
bootstrap-tools.cpio.bz2: 1y2jkykx13r7f3a0w9kjnp62rp4yp3zddcq9c9xp86qz0lgn2qi7
bzip2: 1khs8s5klf76plhlvlc1ma838r8pc1qigk9f5bdycwgbn0nx240q
cpio: 17pxq61yjjvyd738fy9f392hc9cfzkl612sdr9rxr3v0dgvm8y09
mkdir: 1m9nk90paazl93v43myv2ay68c1arz39pqr7lk5ddbgb177hgg8a
sh: 17m3xrlbl99j3vm7rzz3ghb47094dyddrbvs2a6jalczvmx7spnj

This change is not required?
--- a/pkgs/top-level/release.nix
+++ b/pkgs/top-level/release.nix
@@ -180,7 +180,7 @@ let
           # Cross compiled bootstrap tools
           aarch64-darwin =
             let
-              bootstrap = import ../stdenv/darwin/make-bootstrap-tools.nix { system = "x86_64-darwin"; crossSystem = "aarch64-darwin"; };
+              bootstrap = import ../stdenv/darwin/make-bootstrap-tools.nix { system = "aarch64-darwin"; };
             in {
               # Distribution only for now
               inherit (bootstrap) dist;

This change is not required?

I'd rather keep it cross-built so that in the future we can easily re-bootstrap it without using a known good aarch64-darwin machine.

This change is not required?
--- a/pkgs/top-level/release.nix
+++ b/pkgs/top-level/release.nix
@@ -180,7 +180,7 @@ let
           # Cross compiled bootstrap tools
           aarch64-darwin =
             let
-              bootstrap = import ../stdenv/darwin/make-bootstrap-tools.nix { system = "x86_64-darwin"; crossSystem = "aarch64-darwin"; };
+              bootstrap = import ../stdenv/darwin/make-bootstrap-tools.nix { system = "aarch64-darwin"; };
             in {
               # Distribution only for now
               inherit (bootstrap) dist;

The bootstrap tools can be built either cross or native. Currently the cross compiled tools have had more testing, so I’m inclined to keep them for now. I’ve also seen reports that natively rebuilt tools behave slightly differently (shows up as a dylib not found error when building expat), so until I’ve investigated that I think we’re best to stick with the tools that we know to work.

This change is not required? (saw it somewhere on the IRC)
--- a/pkgs/top-level/release.nix
+++ b/pkgs/top-level/release.nix
@@ -180,7 +180,7 @@ let
           # Cross compiled bootstrap tools
           aarch64-darwin =
             let
-              bootstrap = import ../stdenv/darwin/make-bootstrap-tools.nix { system = "x86_64-darwin"; crossSystem = "aarch64-darwin"; };
+              bootstrap = import ../stdenv/darwin/make-bootstrap-tools.nix { system = "aarch64-darwin"; };
             in {
               # Distribution only for now
               inherit (bootstrap) dist;

Maybe we should leave the cross bootstrap job for now and add a native boostrap job as well? At least until we are happy?

I thought so, thanks for explanation @grahamc @thefloweringash

The test attribute from bootstrap would be nice (ran natively on aarch64-darwin).  But not necessarily in this PR.

I think this should be merged as soon as possible, to allow for the aarch64-darwin builders to find as many regressions as possible

What tier of support are we shooting for here? https://github.com/NixOS/rfcs/blob/master/rfcs/0046-platform-support-tiers.md

What tier of support are we shooting for here? https://github.com/NixOS/rfcs/blob/master/rfcs/0046-platform-support-tiers.md

I would say that this will eventually replace x86_64-darwin, so it should be on similar footing. Which seems to be tier 1.

I see it in Tier 2 in that non-normative appendix.  And I failed to find a current normative table :-)

If we're going for tier-3 I think we should remove it from supportedSystems. If we're going for tier-2 we'll need to get builders for it for ofborg. x86-64-darwin is currently listed at tier-2, but I think practically considered to be tier-1.

Tier 2 sounds good.

I think it is too early to add it to supportedSystems today. I think instead we should have it be its own jobset and potentially its own channel until it has some time to simmer, and get full support in to ofborg.

OK, so for this moment I just pushed the bootstrap hashes to staging-next as 5d22db3c5e (with typo in commit message) and I modified the staging-next jobset to include aarch64-darwin.

Agreed. My main concern is if we have "Apple M1 Support" in the release notes, I would just like for that platform to be usable. Higher tier support can come later when other pieces are in place.

:+1:

But I would like to mention that x86_64-darwin was in a limbo state for a long time due to ofborg's lack of build capacity and stagnating contributions for that platform. Also the very real concern about people not having hardware to support a platform (especially for apple, which is expensive, and other issues).

Yes, that was no good. I should have asked much sooner for the foundation to fund it. I've also started the process to request an additional x86_64-darwin machine and 2x aarch64-linux machines for ofborg.

Also, shoutout to @stephank for doing 100+ darwin fixes for ZHF partying_face

:partying_face: :tada: yes, thank you!

Agreed. My main concern is if we have "Apple M1 Support" in the release notes, I would just like for that platform to be usable. Higher tier support can come later when other pieces are in place.

But I would like to mention that x86_64-darwin was in a limbo state for a long time due to ofborg's lack of build capacity and stagnating contributions for that platform. Also the very real concern about people not having hardware to support a platform (especially for apple, which is expensive, and other issues).

Yes, that was no good. I should have asked much sooner for the foundation to fund it. I've also started the process to request an additional x86_64-darwin machine and 2x aarch64-darwin machines for ofborg.

Also, shoutout to @stephank for doing 100+ darwin fixes for ZHF partying_face

yes, thank you!

Could we reassign 2 aarch64-darwin machines from hydra to ofborg? If that makes it easier than buying new hardware and wiring it up.

I've opened https://github.com/NixOS/nixpkgs/pull/124887 and this PR is no longer needed.


AFNetworking 3.0

It would be great that CargoBay support AFNetworking 3.0. Any though about it?

Yes (+1),
Because CargoBay (2.1.1) using AFNetworking (2.6.3)
I can not using the AFNetworking (3.0) when write the new api.
So troublesome ...


Add experimental track dependency support

WIP. closes #1396.
Marked as :internal as this API is undocumented and experimental.
Draft as we need some sort of cleanup that is guaranteed not destructive to the Rally dependencies

What is the status of this? As far as I can tell the tests pass, the failure is a transient one.
@elasticmachine please run tests

@pquentin The failure seems legit. I will fix the test, document the feature, then re-request your review when it's ready.

Reviewers, I've removed the "experimental" designation from the description and ":internal" from the labels. Our incubation period/process for experimental features is not well-defined, and I think bringing one more thing out of experimental state without a defined process just adds to our team's considerable tech debt.

Late to the party, but I'll take a look at this today.


Redirection to Moodle not working properly on Safari

Redirection to Moodle with an access token isn't properly working on Safari, showing the Moodle login page instead.

This is due to a "feature" in Safari in which iFrame can't set cookies for other sites.
A temporary workaround is to "Enable multidomains cookies" in Safari preferences.
This issue will resolve itself if (when) Moodle is hosted on the same site as the portal.
Otherwise, a user prompt might be required to allow storage access (to be implemented, requiring some refactoring).


Website Theme

The portfolio could use a theme its way too colorful and could also use a different layout.
Todo

[ ] Get a color palette with about 5 colors
[ ] Some good fonts can help the website stand out

Kindly assign me please to this. I would love to work with this

Kindly assign me please to this. I would love to work with this

Please list the task you want to do.

I can get a color pallette combination of 5 colors. If you have a color suggestion, it'll be OK too

Let's work with something not too bright. You can go ahead.

Alright.
Thank you

can you assign this project to me

plz assign me


Option for showing doc-string.

From call_signature function doc-string I guess that not showing doc-string in preview window was conscious choice. I for one found those useful and was a bit disappointed to not find them here after coming from jedi-vim.
This PR would add option for user to specify if they want to have doc-strings shown in theirs preview window. With default value being no doc-string.

Sorry about that.  The completion preview drove me nuts, so I forgot it was an option.  :see_no_evil:

@miniukof Thanks!
I will test it. please wait a little :)

@miniukof LGTM.
Thanks !!


Ritesh/add meta tags

changes:
-updated the title
-uploaded images banner image and favicon image
-added meta tags including og tags and twitter tags
-added favicon
test cases:
-title is showing

test cases for:
-are meta tags working
-is favicon working

changed title , favicon and metatags


Including latest version in package payload

As a consumer of the API (i.e. https://bower.herokuapp.com/packages/jquery), I want to be able to access the current version number that is defined in the package definition.

Yes, dupicate


Lens doesn't show connected cluster data

Have updated LENS with the latest version and now it shows that cluster is connected but doesn't show cluster data (namespaces, pods etc.), just gray screen and that's it. Start application with logs and got message that certificate is missing.
Expected behavior
Choose existing cluster and see all its data
Screenshots

Environment (please complete the following information):

Lens Version: 5.3.2-latest.20211201.1
OS: macOS Monterey V.12.0.1
Installation method (e.g. snap or AppImage in Linux): dmg

Logs:
Last login: Thu Dec  9 14:55:57 on ttys003
user@users-MacBook-Pro ~ % /Applications/Lens.app/Contents/MacOS/Lens ; exit;
info:    ▪ 📟 Setting Lens as protocol client for lens:// +0ms
info:    ▪ 📟 Protocol client register succeeded ✅ +3ms
info:    ▪ [APP-PATHS]: initializing +0ms
info:    ▪ 🚀 Starting Lens from "/Applications/Lens.app/Contents/MacOS/Lens" +124ms
info:    ▪ 🐚 Syncing shell environment +1ms
info:    ▪ 💾 Loading stores +1s
info:    ▪ [USER-STORE]: LOADING from  ... +2ms
info:    ▪ [USER-STORE]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/lens-user-store.json +22ms
info:    ▪ [CLUSTER-STORE]: LOADING from  ... +20ms
info:    ▪ [CLUSTER-STORE]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/lens-cluster-store.json +12ms
info:    ▪ [HOTBAR-STORE]: LOADING from  ... +1ms
info:    ▪ [HOTBAR-STORE]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/lens-hotbar-store.json +2ms
info:    ▪ [EXTENSIONS-STORE]: LOADING from  ... +0ms
info:    ▪ [EXTENSIONS-STORE]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/lens-extensions.json +1ms
info:    ▪ [FILESYSTEM-PROVISIONER-STORE]: LOADING from  ... +1ms
info:    ▪ [FILESYSTEM-PROVISIONER-STORE]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/lens-filesystem-provisioner-store.json +1ms
info:    ▪ [WEBLINK-STORE]: LOADING from  ... +0ms
info:    ▪ [WEBLINK-STORE]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/lens-weblink-store.json +2ms
info:    ▪ 🔌 Starting LensProxy +10ms
info:    ▪ [LENS-PROXY]: Proxy server has started at <IP_ADDRESS>:60065 +21ms
info:    ▪ 🔎 Testing LensProxy connection ... +1ms
info:    ▪ ⚡ LensProxy connection OK +18ms
info:    ▪ 🖥  Starting WindowManager +5ms
info:    ▪ 🧩 Initializing extensions +117ms
info:    ▪ [EXTENSION-DISCOVERY] loading extensions from /Users/sergei.budkevich/Library/Application Support/Lens +0ms
info:    ▪ [EXTENSION-INSTALLER] installing dependencies at /Users/sergei.budkevich/Library/Application Support/Lens +215ms
info:    ▪ [WINDOW-MANAGER]: Loading Main window from url: http://localhost:60065 ... +493ms
info:    ▪ [EXTENSION-INSTALLER] dependencies installed at /Users/sergei.budkevich/Library/Application Support/Lens +942ms
info:    ▪ [EXTENSION-DISCOVERY] watching extension add/remove in /Users/sergei.budkevich/.k8slens/extensions +2ms
Native extraction module not loaded, msgpackr will still run, but with decreased performance. Cannot find module 'msgpackr-extract'
Lens Cloud Extension activated
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +76ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/extension-store/lenscloud-lens-extension/auth-token-store.json +2ms
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +2ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/extension-store/lens-survey/preferences-store.json +1ms
telemetry main extension activated
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +41ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/extension-store/lens-telemetry/preferences-store.json +0ms
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +5ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/extension-store/lenscloud-lens-extension/select-space-store.json +1ms
info:    ▪ [EXTENSION-STORE-T]: LOADING from  ... +430ms
info:    ▪ [EXTENSION-STORE-T]: LOADED from /Users/sergei.budkevich/Library/Application Support/Lens/extension-store/lenscloud-lens-extension/startup-store.json +1ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+0ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+92ms
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+0ms
info:    ┏ [IPC-RENDERER]: adding extension listener +15ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'deleteOneCluster',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +2ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'deleteOneSpace',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┗ [1] { channel: 'logOut', extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' } }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'createWeblink',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +1ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'deleteOneWeblink',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'loadRemoteSpacesClusters',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'createOneSpace',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'leaveOneSpace',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┗ [1] { channel: 'selectSpace', extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' } }
spaceId 3f9e7e2f-5f3f-4155-975c-18a5ce27c41b not found, selecting Personal Space
ERROR: Personal Space not found, space not found from spaces.
info:    ┏ [IPC-RENDERER]: adding extension listener +489ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'network:offline',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +1ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'network:online',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'provisionDevCluster',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +1ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'removeDevCluster',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'stopDevClusterEvent',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ┏ [IPC-RENDERER]: adding extension listener +0ms
info:    ┃ [1] {
info:    ┃ [2]   channel: 'startDevClusterEvent',
info:    ┃ [3]   extension: { name: 'lenscloud-lens-extension', version: '5.3.2-latest.20211201.1' }
info:    ┗ [4] }
info:    ▪ [EXTENSION]: enabled<EMAIL_ADDRESS>+0ms
info:    ▪ [WINDOW-MANAGER]: Main window loaded +921ms
info:    ▪ [KUBECONFIG-SYNC]: starting requested syncs +1s
info:    ┏ [KUBECONFIG-SYNC]: starting sync of file/folder +1ms
info:    ┗ [1] { filePath: '/Users/sergei.budkevich/Library/Application Support/Lens/kubeconfigs' }
info:    ┏ [KUBECONFIG-SYNC]: starting sync of file/folder +0ms
info:    ┗ [1] { filePath: '/Users/sergei.budkevich/.kube' }
info:    ▪ 📡 Checking for app updates +2ms
info:    ▪ [AUTO-UPDATE]: electron-updater: Checking for update +0ms
info:    ▪ [KUBECONFIG-SYNC]: ignoring '/Users/sergei.budkevich/.kube/.DS_Store' due to ignore glob: .DS_Store +5ms
info:    ▪ [WINDOW-MANAGER]: Main window has reported that it has loaded +42ms
info:    ▪ [AUTO-UPDATE]: electron-updater: Update for version 5.3.2-latest.20211201.1 is not available (latest version: 5.3.2-latest.20211201.1, downgrade is disallowed). +298ms
info:    ▪ [UPDATE-CHECKER]: update not available from latest, will check latest channel next +1ms
info:    ▪ [STORE]: SAVING /Users/sergei.budkevich/Library/Application Support/Lens/extension-store/lenscloud-lens-extension/auth-token-store.json +1s
[LENS-SPACES-EXTENSION]: Connecting to catalog api of Space id 3f9e7e2f-5f3f-4155-975c-18a5ce27c41b...
[LENS-SPACES-EXTENSION] Error getSpaceCa(), retrying... Error: Certificate authority missing for Space siarhei.budkevich catalog api https://3f9e7e2f-5f3f-4155-975c-18a5ce27c41b.catalog.lc-staging1.staging-k8slens.cloud
    at e.startingDelay [as request] (/Applications/Lens.app/Contents/Resources/extensions/lenscloud-lens-extension/dist/main.js:23:553236)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
[LENS-SPACES-EXTENSION] Error getSpaceCa(), retrying... Error: Certificate authority missing for Space siarhei.budkevich catalog api https://3f9e7e2f-5f3f-4155-975c-18a5ce27c41b.catalog.lc-staging1.staging-k8slens.cloud
    at e.startingDelay [as request] (/Applications/Lens.app/Contents/Resources/extensions/lenscloud-lens-extension/dist/main.js:23:553236)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
info:    ┏ APP:ACTIVATE +14s
info:    ┗ [1] { hasVisibleWindows: true }
info:    ┏ [CLUSTER]: activate +3s
info:    ┃ [1] {
info:    ┃ [2]   id: '5ea24b78ea4ba376e0a8b65f547d153a',
info:    ┃ [3]   name: 'gke_third-hope-267810_us-central1-a_hackathon-cluster',
info:    ┃ [4]   ready: false,
info:    ┃ [5]   online: false,
info:    ┃ [6]   accessible: false,
info:    ┃ [7]   disconnected: true
info:    ┗ [8] }
info:    ┏ [CLUSTER]: bind events +0ms
info:    ┃ [1] {
info:    ┃ [2]   id: '5ea24b78ea4ba376e0a8b65f547d153a',
info:    ┃ [3]   name: 'gke_third-hope-267810_us-central1-a_hackathon-cluster',
info:    ┃ [4]   ready: false,
info:    ┃ [5]   online: false,
info:    ┃ [6]   accessible: false,
info:    ┃ [7]   disconnected: true
info:    ┗ [8] }
info:    ┏ [CLUSTER]: reconnect +1ms
info:    ┃ [1] {
info:    ┃ [2]   id: '5ea24b78ea4ba376e0a8b65f547d153a',
info:    ┃ [3]   name: 'gke_third-hope-267810_us-central1-a_hackathon-cluster',
info:    ┃ [4]   ready: false,
info:    ┃ [5]   online: false,
info:    ┃ [6]   accessible: false,
info:    ┃ [7]   disconnected: true
info:    ┗ [8] }
[LENS-SPACES-EXTENSION] Error getSpaceCa(), retrying... Error: Certificate authority missing for Space siarhei.budkevich catalog api https://3f9e7e2f-5f3f-4155-975c-18a5ce27c41b.catalog.lc-staging1.staging-k8slens.cloud
    at e.startingDelay [as request] (/Applications/Lens.app/Contents/Resources/extensions/lenscloud-lens-extension/dist/main.js:23:553236)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Some manipulations with kubeconfig, removed and download them one more time and seems that it's ok now


bob: update tests and version file (v1.0.0 -> v1.2.0)

Please update the version specified in the bob version file from 1.0.0 to 1.2.0.
This update has been caused by the application of a new input policy, and a new rule being added to Bob's behaviour (resulting in test suite changes).
Please update the test suite to match the canonical data. The reference solution will also require an update to pass the new test suite.
This pairs with issue #127.

I'll take a look at this one.


Use thread-safe API in GeoIP 1.5.x

(copied from issue #6)
@dryski wrote:

libgeoip included a thread-safe API in its 1.5.0 release in October 2012. This would allow the removal of all mutexes from the Go API. The work required is not that large and I'm willing to do it. Most distributions are probably still on earlier versions, although Ubuntu Saucy will include 1.5.1. Should I begin this work?

Any update on this issue?

Any update on this issue?


Add GUI tests

I think this should be a top priority. The GUI keeps breaking because we don't have automatic tests.
Probably we should use https://pytest-qt.readthedocs.io.

Closed by #37


Anaconda Workflow & meta.yaml

Reference Issues/PRs
#100
What does this implement/fix? Explain your changes.
Added

Anaconda workflow

Changed

Anaconda installation instruction added to README.md
Package's dependencies added to meta.yaml

Any other comments?
Do not merge this PR right before/after #104 due to probable silent merge conflicts.

@sadrasabouri LGTM, Thank you so much for your work.
According to this issue it seems that the default access is write-all and sometimes(as discussed in the thread) in some projects suddenly this warning is getting raised and it is ok, even if you have not changed anything, so, I think it does address questions you raised in the last meeting, I tried to downgrade the workflow's access level from default write-all to read-all and it is now ok.

@sadrasabouri, could you please rebase this PR and resolve any conflicts? Then ping me for the final review. 🔥

@sadrasabouri I think something went wrong during the rebase process. I can't see any changes in meta.yml.

meta.yml has been changed in last PR.


Default_url_options is being ignored

In my rspec_helper.rb I defined;
Rails.application.routes.default_url_options[:host] = 'lvh.me'

It works fine for non-feature specs but doesn't work for feature specs. Host for urls are equal to "www.example.com" in feature specs.
I've debugged and in feature_example_group.rb file, default_url_options is always an empty hash.
https://github.com/rspec/rspec-rails/blob/master/lib/rspec/rails/example/feature_example_group.rb#L18
found the following solution for this issue;
https://github.com/beydogan/rspec-rails/commit/b590c82573b27bd8a1be967811b4835119260f09
Is this valid?

What problem is this solving for you? I'd like to understand where this is causing an issue.

@cupakromer  The problem is; when I set default_url_options in my spec/rails_helper.rb or environments/test.rb. It's being ignored in feature specs.
I set like following;
Rails.application.routes.default_url_options[:host] = 'lvh.me'

But in a feature spec;
posts_url is equal to http://www.example.com/posts instead of http://lvh.me/posts
sorry about my English

Ok, I dug into this a bit. It's a little more complicated that it seems. Here's what is going on.
The Rails test cases, the RSpec example groups are a thin shim on top of these, setup an attribute default_url_options. If this is not set or defined, then the call chain falls back on whatever the current routes scope has configured. By default it has nothing configured for :host and the value is nil.
If we removed or comment out the line:
default_url_options[:host] ||= ::RSpec::Rails::FeatureExampleGroup::DEFAULT_HOST

You would get the following error:
Missing host to link to! Please provide the :host parameter, set
default_url_options[:host], or set :only_path to true

The reason your proposed solution in #1276 appears to work is simply because the example's default_url_options is nil and so it falls back to the routes which you have customized in the spec/rails_helper.rb. For other spec types, which don't have a :host option set by default, the route generation falls back to the session set by Rails' test case. This depending on the spec type and is normally set to a default of www.example.com or pulled from a request, but is all handled by Rails' test cases. This is not set for feature specs, because the session is handled by Capybara which does not set something for it.
So unfortunately, your solution is basically a no-op and is the same as deleting that if block. For the majority of cases, people don't customize the host option and they would get the above exception.
We could change it to:
if respond_to?(:default_url_options)
  default_url_options[:host] ||= (
    app.routes.default_url_options[:host] ||
    ::RSpec::Rails::FeatureExampleGroup::DEFAULT_HOST
  )
end

However, this will cause other problems:
require 'rails_helper'

Rails.application.routes.default_url_options[:host] = 'lvh.me'
RSpec.feature "Relative path hosts set by Capybara", type: :feature do
  it "causes a mismatch between the URLs" do
    visit widgets_path
    expect(current_url).to eq widgets_url
  end
end

Results in a failure:
Failures:

  1) Relative path hosts set by Capybara causes a mismatch between the URLs
     Failure/Error: expect(current_url).to eq widgets_url

       expected: "http://lvh.me/widgets"
            got: "http://www.example.com/widgets"

       (compared using ==)
     # ./spec/features/capybara_mismatch_spec.rb:7:in `block (2 levels) in <top (required)>'

This is because Capybara uses Capybara.default_host to generate the "full" URL under the hood. The default host just happens to be "www.example.com". However, it won't actually use that web server. It just uses the value to generate the full URL while still using it's local server. You have to configure Capybara to use an external app host.
There's another wrinkle. Capybara expects the "http://" part in the URL, if it's not present the URL is created as: "http:///widgets". I'm not sure this is a bug, you'd have to ask them. So while Rails is happy to have "lvh.me", Capybara would need "http://lvh.me".
We are tightly coupled to Capybara right now. As you can see from the feature example group file it's essentially just all code necessary to handle Capybara's design decisions. It also causes a lot of confusion for newer users who do not understand this tight dependency.
I really do not want to add yet another special case for Capybara. Let me think on this a bit. I have a potential solution in mind but will need to think on it for a day.
I hope this helps understand what's happening.

Any fix?

Not yet, see @cupakromer's comments above, you can try setting the Capybara default host as a work aorund?

@JonRowe I'm not using Capybara. Same thing in controller tests.

This issue only affects feature tests, which use Capybara.

Again. This issue in controllers tests too.
Only way to fix it is:
[ApplicationController, ActionController::Base].each do |klass|
  klass.class_eval do
    def default_url_options(options = {})
      { :host => "example.com" }.merge(options)
    end
  end
end

Can you elaborate what symptoms you are seeing; It's possible you are suffering from the symptoms of the rails behaviour (which we cannot fix) or a different bug altogether.

I'm testing subdomains and instead of _path helpers using _url in my controller. It's only what I set.

Sorry you're going to have to elaborate further, when reporting issues it's best to actually provide an example showing what you're trying to do, and the unexpected outcome of that attempt. Even better if it's actually executable (but please... don't point me to a rails app repo, I don't have time to comb through an entire app).

I'm still having lots of problems when testing route_url using different subdomains.
Any thoughts?

Facing the same issue in features spec with Rspec and Capybara.
Tried adding the config in application.rb
   Rails.application.default_url_options[:host] = Figaro.env.domain_name
Further tried overriding Capybara config
Capybara.configure do |config|   config.default_host = Figaro.env.domain_name end
But  'about_us_url' returns "http://www.example.com/about_us" instead of "http://localhost:3000/about_us". This causes email specs to fail where we check if the url has been added to an email.

For emails you also have to configure ActionMailer::Base.default_url_options

That is configured. This issue it is not related to email. While running any spec if I debug and check what urls are generated with 'xyz_url' method, it always prepends it with with 'http:www.example.com/'.

RSpec doesn't have any value for this url, it comes from Capybara or from your config.

While debugging the spec if I check value of
self
it gives

#RSpec::ExampleGroups::SignUp:0x007fe910f18168

And when we check value of
self.url_options
it gives

result = Hash (1 element)
host => www.example.com

So as you said, I think, the value is being set by either capybara or may be Rspec. Any thoughts?

That'll be the value from the Rails helpers we mix in, you need to check
your Rails configuration.

Hey @JonRowe
I checked and found that issue is exactly where @beydogan is suggesting in the first comment.
In the line 19 of feature_example_group.rb
default_url_options[:host]
is always nil, no matter where I set the default_url_options.
And thus in the same line default host is set to  www.example.com
As of now in my application I have set the default host at all possible places.
config/environments/test.rb
  Rails.application.default_url_options = {:host => Figaro.env.domain_name }
  Rails.application.routes.default_url_options = {:host => Figaro.env.domain_name }

spec/support/capybara.rb
Capybara.app_host = 'http://localhost'
Capybara.always_include_port = true

Capybara.configure do |config|
  config.default_host = Figaro.env.domain_name
end

Any further comments?

Sample app here: https://github.com/samphippen/demo_app_for_1275.git
Worth noting: this explicitly is not supposed to work in controller specs according to someone from rails core.
So request specs work, and feature specs don't work here.

For future reference: I tried all sorts of variations (e.g config.action_mailer.default_url_options = { host: 'www.example.com' }, Capybara's host etc), nothing worked. I then added Rails.application.routes.default_url_options[:host] = 'www.example.com' after the end (end of file, outside the config block) in config/environments/tests.rb and it worked.

I tried everything described in this issue too and my tests still broken.
I'm using apartment with custom domains and it's necessary setup default_url_options with custom domain.

anything found and tried, always end up with an error. visit("http://custom_domain") for now; but that quite feels weird. Hope there'd be a clear explanation

FWIW, I just ran into this issue, and found that if I call the url helper before making any requests in my request spec, I get the expected hostname:
+expected_url = foo_bars_url(foo)

 get url_for(foo)

 expect(json).to include(
   "links" => a_hash_including(
-    "bars" => foo_bars_url(foo)
+    "bars" => expected_url
   )
 )

I'm seeing the exact same situation as @rvsingh. Any attempt to configure default_url_options is effectively ignored.
I have been able to work around the issue by acquiescing, and re-configuring default_url_options to use the host "www.example.com". Thanks to @kurko for the suggestion.
This is incredibly frustrating because rspec-rails is effectively forcing you to use "www.example.com" as your host. If you have any other desire, you're left with options that feel wrong.

I'm sorry you're frustrated, but we just set a default value if one isn't present, it's up to Rails how it uses that value, I suspect its being cached in a way making it difficult to override.

For controller tests inside the Rails.application.configure seemed to work for me:
  config.action_controller.default_url_options = {
    host: ENV['HOST']
  }

Same issue. Alternate resolution.
I noticed that a random feature test was failing inconsistently in both dev machine and CI environments. After reproducing with rspec --seed and getting consistent failures tried many of the approaches here. Unfortunately, not of them quite worked for me. The route helpers would still resolve incorrectly. i.e. my_page_url = www.example.com/my_page.
The interesting thing was that only the first feature test would fail. For all the subsequent feature tests in any feature testing file, the URL helpers would still resolve incorrectly. However, the visit would be successful. In other words, visiting www.example.com/my_page would render my page correctly and run the necessary assertions as intended.
Simplest hack possible for me was just visiting one page before running the real tests:
  # HACK: https://github.com/rspec/rspec-rails/issues/1275
  config.include Warden::Test::Helpers
    visit(user_home_path)
  end

Added this to the RSpec configure block in my rails helper and haven't had any problems since.
ruby 2.3.4p301
rails 5.1.1
rspec 3.6.0
capybara 2.14.0

These options are ignored on system tests

I think this is just a Rails issue. There are many places to set default_url_options, but they either work on console but not web, or the other way around:
In Rails 5.1.4, I have tested the following scenarios on web and console (but not in Rspec):
    # in development.rb
    config.action_controller.default_url_options({:protocol => 'https'})
    config.action_controller.default_url_options(:protocol => 'https')
    # Does not work

    # in development.rb, outside config block
    Rails.application.routes.default_url_options[:protocol] = 'https'
    # Does not work, but works under console

    # in routes.rb
    Rails.application.routes.draw do
      default_url_options protocol: :https
    # Does not work, but works under console

    # in ApplicationController
    def default_url_options
      { protocol: :https }
    end
    # Works in browser, but does not work under console

    # in development.rb
    config.action_controller.default_url_options= {:protocol => 'https'}
    # Works in browser, but does not work under console

Regardless of the last comments. I think we can close this issue. Feel free to comment if we think we should still look at it.

Any fixes for this problem ?

I faced with the same issue. I found out that RAILS_ENV == development, so RAILS_ENV=test rspec  helped me.

If you set config.action_controller.default_url_options in config/environments/test.rb, you can reuse it in the feature specs by setting self.default_url_options = ... in a before block as below:
# File spec/rails_helper.rb
RSpec.configure do |config|
  config.before(type: :feature) do
    self.default_url_options = ApplicationController.default_url_options
  end
end

This fixes the issue originally described.

And now how do we achieve the same for view specs? 😖

I'm having facing the same problem unfortunatelly i didn't find any other solution that using the host option in the test it self, some one have some idea how to perform the override of default_url_options?

There is a Capybara.default_host option that will be set to 'http://www.example.com'. Under certain circumstances, feature specs will use this host.
One approach that may help some is to override this, and Capybara.server_host in your Capybara config with the following:
Capybara.server_host = 'localhost'
Capybara.default_host = "http://#{Capybara.server_host}"

You do not have to use 'localhost', that's just what I'm using.


I want to speed up the tresnet_m go a step further by modifying the structure

I want to speed up the tresnet_m go a step further, if I modify the bottlebneck strcture"[3,4,11,3]" to "[3,4,8,3]"，the network can work  too. Do you compare the modified "[3,4,8,3]" or "[3,4,6,3]" to standard resnet50"[3,4,6,3]" about accurancy and speed? Thank you a lot

i tried a model called TResNet-S (S for small) with [3,4,7,3].  didn't put it in the paper
i don't fully remember what's its accuracy was, but it was both faster and more accurate than resnet50.
In the end, just changing the number of blocks in the 3rd stage will move you on the Pareto curve - a faster model, with lower accuracy. it won't bring significant improvement to the speed-accuracy tradeoff.

Thank you very much!


undefined method `data' for #Hash:0x007fabf6664078

I've got myself a bit stuck and tried approaching the issue from a couple directions, but still can't seem to solve it. When I get the response from transloadit and run transloadit_save(data) I get a "undefined method `data' for #Hash:0x007fabf6664078" error occurring.
I'm using the approach in the go rails tutorial that uploads the file to cache via jquery uploader. Then submitting the key for that file. transloadit appears to get the file and transcode it fine, even firing off the web hook correctly. But the returned data from the web hook is causing an issue. Have I missed a setup step?

@rmaspero Could you include the full stack trace of the exception?

Is this what you are looking for?
/gems/shrine-2.8.0/lib/shrine.rb:694 in convert_to_data
/gems/shrine-2.8.0/lib/shrine.rb:683 in _set
/gems/shrine-2.8.0/lib/shrine.rb:672 in update
/gems/shrine-2.8.0/lib/shrine/plugins/activerecord.rb:133 in update
/gems/shrine-2.8.0/lib/shrine.rb:576 in swap
/gems/shrine-2.8.0/lib/shrine/plugins/backgrounding.rb:263 in swap
/gems/shrine-transloadit-0.4.3/lib/shrine/plugins/transloadit.rb:110 in transloadit_save
/gems/shrine-transloadit-0.4.3/lib/shrine/plugins/transloadit.rb:52 in transloadit_save
app/controllers/jobs_controller.rb:60 in video
/gems/actionpack-5.1.1/lib/action_controller/metal/basic_implicit_render.rb:4 in send_action
/gems/actionpack-5.1.1/lib/abstract_controller/base.rb:186 in process_action
/gems/actionpack-5.1.1/lib/action_controller/metal/rendering.rb:30 in process_action
/gems/actionpack-5.1.1/lib/abstract_controller/callbacks.rb:20 in block in process_action
/gems/activesupport-5.1.1/lib/active_support/callbacks.rb:131 in run_callbacks
/gems/actionpack-5.1.1/lib/abstract_controller/callbacks.rb:19 in process_action
/gems/actionpack-5.1.1/lib/action_controller/metal/rescue.rb:20 in process_action
/gems/actionpack-5.1.1/lib/action_controller/metal/instrumentation.rb:32 in block in process_action
/gems/activesupport-5.1.1/lib/active_support/notifications.rb:166 in block in instrument
/gems/activesupport-5.1.1/lib/active_support/notifications/instrumenter.rb:21 in instrument
/gems/activesupport-5.1.1/lib/active_support/notifications.rb:166 in instrument
/gems/actionpack-5.1.1/lib/action_controller/metal/instrumentation.rb:30 in process_action
/gems/actionpack-5.1.1/lib/action_controller/metal/params_wrapper.rb:252 in process_action
/gems/activerecord-5.1.1/lib/active_record/railties/controller_runtime.rb:22 in process_action
/gems/actionpack-5.1.1/lib/abstract_controller/base.rb:124 in process
/gems/actionview-5.1.1/lib/action_view/rendering.rb:30 in process
/gems/actionpack-5.1.1/lib/action_controller/metal.rb:189 in dispatch
/gems/actionpack-5.1.1/lib/action_controller/metal.rb:253 in dispatch
/gems/actionpack-5.1.1/lib/action_dispatch/routing/route_set.rb:49 in dispatch
/gems/actionpack-5.1.1/lib/action_dispatch/routing/route_set.rb:31 in serve
/gems/actionpack-5.1.1/lib/action_dispatch/journey/router.rb:46 in block in serve
/gems/actionpack-5.1.1/lib/action_dispatch/journey/router.rb:33 in each
/gems/actionpack-5.1.1/lib/action_dispatch/journey/router.rb:33 in serve
/gems/actionpack-5.1.1/lib/action_dispatch/routing/route_set.rb:832 in call
/gems/warden-1.2.7/lib/warden/manager.rb:36 in block in call
/gems/warden-1.2.7/lib/warden/manager.rb:35 in catch
/gems/warden-1.2.7/lib/warden/manager.rb:35 in call
/gems/rack-2.0.3/lib/rack/etag.rb:25 in call
/gems/rack-2.0.3/lib/rack/conditional_get.rb:38 in call
/gems/rack-2.0.3/lib/rack/head.rb:12 in call
/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:232 in context
/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:226 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/cookies.rb:613 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/callbacks.rb:26 in block in call
/gems/activesupport-5.1.1/lib/active_support/callbacks.rb:97 in run_callbacks
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/callbacks.rb:24 in call
/gems/airbrake-6.2.1/lib/airbrake/rack/middleware.rb:52 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/debug_exceptions.rb:59 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/show_exceptions.rb:31 in call
/gems/railties-5.1.1/lib/rails/rack/logger.rb:36 in call_app
/gems/railties-5.1.1/lib/rails/rack/logger.rb:24 in block in call
/gems/activesupport-5.1.1/lib/active_support/tagged_logging.rb:69 in block in tagged
/gems/activesupport-5.1.1/lib/active_support/tagged_logging.rb:26 in tagged
/gems/activesupport-5.1.1/lib/active_support/tagged_logging.rb:69 in tagged
/gems/railties-5.1.1/lib/rails/rack/logger.rb:24 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/remote_ip.rb:79 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/request_id.rb:25 in call
/gems/rack-2.0.3/lib/rack/method_override.rb:22 in call
/gems/rack-2.0.3/lib/rack/runtime.rb:22 in call
/gems/activesupport-5.1.1/lib/active_support/cache/strategy/local_cache_middleware.rb:27 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/executor.rb:12 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/static.rb:125 in call
/gems/rack-2.0.3/lib/rack/sendfile.rb:111 in call
/gems/actionpack-5.1.1/lib/action_dispatch/middleware/ssl.rb:66 in call
/gems/skylight-1.3.1/lib/skylight/middleware.rb:61 in call
/gems/railties-5.1.1/lib/rails/engine.rb:522 in call
/gems/puma-3.8.2/lib/puma/configuration.rb:224 in call
/gems/puma-3.8.2/lib/puma/server.rb:600 in handle_request
/gems/puma-3.8.2/lib/puma/server.rb:435 in process_client
/gems/puma-3.8.2/lib/puma/server.rb:299 in block in run
/gems/puma-3.8.2/lib/puma/thread_pool.rb:120 in block in spawn_thread

@rmaspero Oh, you probably forgot to load the versions plugin, see the "Versions" section for an example.

@janko-m Thank you. Now I feel like a complete noob 🤦♂

@rmaspero No worries, I think the problem is more in the exception Shrine raises, it doesn't say what the problem is, I added it to my TODO list to see whether it could be improved.


[6.x] Fix model date fields serialization

Closes #28047
When a model date field contains an invalid value like an empty string, Carbon throws an exception and the serialization (after calling toArray()) fails.
With this pull request, the value is verified if it is an empty value, and if it is, we skip it, avoiding then the error described in the related issue.

I've my doubts that the PR in this form is a good idea.
Why would a date value like false and '' produce that very same value?
IMHO it's correct and good that those value produce an error and not return itself or a date nevertheless => they are simply not valid dates.
Otherwise the assumption of the application would simply 'splode at a later point.
Basically what was commented in https://github.com/laravel/framework/issues/22107#issuecomment-444000672

Isn't this a wrong usage? How can an empty string be a date?!

You seem to have a specific use-case with a custom date format and also found a workaround ( https://github.com/laravel/framework/issues/22385#issuecomment-350768520 ).
I don't see why any of the current behavior should be changed, especially with such semantics touching erroneous dates.


 Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
wget
1 upgraded, 0 newly installed, 0 to remove and 444 not upgraded.
Need to get 270 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://security.ubuntu.com/ubuntu/ trusty-security/main wget amd64 1.15-1ubuntu<IP_ADDRESS> [270 kB]
Fetched 270 kB in 1s (174 kB/s)
(Reading database ... 172284 files and directories currently installed.)
Preparing to unpack .../wget_1.15-1ubuntu<IP_ADDRESS>_amd64.deb ...
Unpacking wget (1.15-1ubuntu<IP_ADDRESS>) over (1.15-1ubuntu<IP_ADDRESS>) ...
Processing triggers for install-info (5.2.0.dfsg.1-2) ...
Processing triggers for man-db (<IP_ADDRESS>-1ubuntu1) ...
Setting up wget (1.15-1ubuntu<IP_ADDRESS>) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package mesa-utils is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Unable to locate package gsl-bin
E: Unable to locate package libgiftiio-dev
E: Unable to locate package libjpeg-progs
E: Package 'mesa-utils' has no installation candidate
E: Unable to locate package tcsh
E: Unable to locate package libmotif-dev
libxp is installed via apt for Ubuntu 14.04
[ Fri Nov  9 08:38:10 UTC 2018 ] apt-get failed to install packages: cmake git graphviz graphviz-dev gsl-bin libexpat1-dev libgiftiio-dev libglib2.0-dev libglu1-mesa-dev libjpeg-progs libxml2-dev libxext-dev libxft-dev libxi-dev libxmu-headers libxmu-dev libxpm-dev libxslt1-dev mesa-common-dev mesa-utils netpbm build-essential xvfb libgl1-mesa-dri tcsh zlib1g-dev m4 libmotif-dev libxp-dev libgsl0-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 444 not upgraded.
[ Fri Nov  9 08:38:10 UTC 2018 ] : C-PAC system dependencies not fully installed.
Python dependencies cannot be installed unless system-level dependencies are installed first.
Have your system administrator install system-level dependencies as root.
Exiting now...

My ubuntu is 14.05 . When I try to install cpac_install.sh, it pop out above errors. Can you help me to figure it out?


Add option to create horizontal droplet generator

Currently, 3DuF only has the option to create a vertical droplet generator. A horizontal option, similar to the transposer, would be great.

Fixed as of Commit - 0609771abbf278c3f9817ea312f407683b04b11d

Also @maniwu feedback on rotation vs horizontal/vertical would be appreciated.


Entity not available: camera.map

Valeudo lastest dev 2021.2+, lovelace-valetudo-map-card latest release.
lovelace-valetudo-map-card - installed by hacs. all entities is on the places.

If enable homeassistant hack i have white text picture. In node-red, valetudo node convert mqtt sucsessfuly.

where i can make a mistake?

The home assistant map hack is necessary for the card to work. The card directly reads the data embedded in the PNG file, so you don't need node red. What is exactly going wrong when you use the home assistant map hack?

is apperad after toggle hass hack in options and chnging any  digits in setting off card, crop or rotate

So, sounds like you got it working then? I'll close this issue then. Please respond if I misunderstood you

yes, it`s working now. thank you


The various 'row' and 'column' components have the wrong icon in the insert menu

See here: all right now use the 'component' icon.

[ ] They should use the correct icon from the annotations
[ ] If that's already the case, the component annotations should be amended to use the right icons

They aren't set, so I'll update them

Done


[PR] Adding proxy contract for open source algoworld swapper

Description

Adds a proxy account that serves as a reference point for obtaining swap configurations for users of swapper.algoworld.io. The proxy contract accepts 2 pay transactions, one covering the fee for the consecutive transaction that is issued on behalf of proxy. The second transaction is always a 0 amount pay transaction who's note field contains the link to ipfs url that contains the swapper configuration file (here is a reference on the function that stores configs in ipfs in swapper). @cusma let me know if you have any questions. As usual if you see that i merged the PR already just leave the comments on it regardless (if you have any) - and i will address in timely manner.
Adds workflow step that pushed the package to pypi

Checklist

Please, make sure to comply with the checklist below before expecting review

[x] Code compiles correctly
[x] Created tests which fail without the change (if possible)
[x] All tests passing
[x] Extended the README / documentation, if necessary

@cusma hey - thanks for review, i addressed most of the comments but for your suggestion to decouple funding transaction of 110_000 algos, ill address it in separate pr https://github.com/AlgoWorldNFT/algoworld-contracts/issues/48


Feature request: choose component/render the column itself

I'm MUI as my UI system, and would like to be able to have the column be a MUI container (a Box or Paper component) that I can choose/pass contextual props to based on column id. These components get rendered as a div element, so it would still work fine with the underlying dnd library. It would be very useful for me as I have a light/dark theming engine and custom background for my paper components, as well as making it easy to add effects like elevation that are consistent with the rest of my UI.
It looks like here is where it would be added? Basically just using something component that extends from the div props, or using a div directly, and having a method for injecting more props during render (based on board state).
wdyt? I could potentially add this feature if you don't want to/don't have time. Are you accepting PRs?

Definitely open to PRs.
This is mainly just a 1:1 swap of the old one, it would be interesting to provide more flexibility in the custom render. If you haven't already, check out the example as it's using MUI as well. If that doesn't suit your needs, definitely open to PRs and I will take a look.

@christopher-caldwell I added a patch (using patch-package) that allows me to supply a custom component for the column, and it works well! It's pretty hackish though, gotta clean it up a lot before I upstream it.

@christopher-caldwell  thinking about this a bit more, rendering the column is really powerful and can potentially supplant (or act as an alternative pattern to) rendering column header and column adder. Those are pretty prescriptive patterns-- what if I want to have a FAB at the bottom-right of my column  for adding a card? Or I want to have a few different items at the top of the column?
Something generic that allows for rendering the column (that takes as an argument the cards for that column and renders them as a section within the column) would give a lot of flexibility.

Definitely a shift from the original implementation. Although, I am a big fan of getting the pieces and allowing me to arrange them however I want. In spirit with a headless UI library like tanstack's react table.
I don't think there will be any issue adding a custom render for the column.

Yeah, the original design is definitely more opinionated. I'm personally a fan of opinionated defaults + having a flexible escape hatch for rich customization.

After taking a look, I think this will possible, but will be a good amount of work to make sure everything checks out. I'll be working on this, it just might be awhile.

I got it working locally with patch-package. It's quite hackish though, did it as a proof of concept. I create a Context object in my code that uses your library, and I add some stuff to the context-- a custom component for the column, custom props for that component, and custom adder and header components (since neither were working/exposed via the controlled component interface).
Then (here's where it gets hackish..) I attach that context object globally to the window, and I useContext based on that window property in my patch in your library. I pull the various components and props from the context, and use them when rendering the column.
It works quite well! When I get my project a bit more polished I can show you a demo so you can see it in action.
Here's my<EMAIL_ADDRESS>file:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index b0f46f0..f1bb42c 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -1,22 +1,30 @@
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
-import { forwardRef } from 'react';
 import { Draggable } from '@hello-pangea/dnd';
+import { forwardRef, useMemo, useContext } from 'react';
 import { Card } from '../card';
 import { withDroppable } from '../with-droppable';
-import { CardAdder } from '../card-adder';
 import { pickPropOut } from '../../services/utils';
 const ColumnEmptyPlaceholder = forwardRef((props, ref) => (_jsx("div", Object.assign({ ref: ref, style: { minHeight: 'inherit', height: 'inherit' } }, props), void 0)));
 const DroppableColumn = withDroppable(ColumnEmptyPlaceholder);
 export const Column = function ({ children: column, index: columnIndex, renderCard, renderColumnHeader, disableColumnDrag, disableCardDrag, onCardNew, allowAddCard, }) {
-    return (_jsx(Draggable, Object.assign({ draggableId: `column-draggable-${column.id}`, index: columnIndex, isDragDisabled: disableColumnDrag }, { children: (columnProvided) => {
-            const draggablePropsWithoutStyle = pickPropOut(columnProvided.draggableProps, 'style');
-            return (_jsxs("div", Object.assign({ ref: columnProvided.innerRef }, draggablePropsWithoutStyle, { style: {
-                    height: '100%',
-                    minHeight: '28px',
-                    display: 'inline-block',
-                    verticalAlign: 'top',
-                    ...columnProvided.draggableProps.style,
-                }, className: 'react-kanban-column', "data-testid": `column-${column.id}` }, { children: [_jsx("div", Object.assign({}, columnProvided.dragHandleProps, { children: renderColumnHeader(column) }), void 0), allowAddCard && _jsx(CardAdder, { column: column, onConfirm: onCardNew }, void 0), _jsx(DroppableColumn, Object.assign({ droppableId: String(column.id) }, { children: column.cards.length ? (column.cards.map((card, index) => (_jsx(Card, Object.assign({ index: index, renderCard: (dragging) => renderCard(column, card, dragging), disableCardDrag: disableCardDrag }, { children: card }), card.id)))) : (_jsx("div", { className: 'react-kanban-card-skeleton' }, void 0)) }), void 0)] }), void 0));
-        } }), void 0));
+        // hacky method to inject custom components here w/o changing the whole library
+        const kanbanContext = useMemo(() => window.kanbanContext, []);
+        const { CustomRenderCardAdder, KanbanColumnComponent, customRenderColumnHeader, kanbanColumnComponentProps, } = useContext(kanbanContext);
+        // renderColumnHeader(column)
+        // <CardAdder<TCard> column={column} onConfirm={onCardNew} />
+        return (_jsx(Draggable, Object.assign({ draggableId: `column-draggable-${column.id}`, index: columnIndex, isDragDisabled: disableColumnDrag }, {
+                children: (columnProvided) => {
+                        const draggablePropsWithoutStyle = pickPropOut(columnProvided.draggableProps, 'style');
+                        return (_jsxs(KanbanColumnComponent, Object.assign({ ref: columnProvided.innerRef }, draggablePropsWithoutStyle, {
+                                style: {
+                                        height: '100%',
+                                        minHeight: '28px',
+                                        display: 'inline-block',
+                                        verticalAlign: 'top',
+                                        ...columnProvided.draggableProps.style,
+                                }, className: 'react-kanban-column'
+                        }, kanbanColumnComponentProps, { children: [_jsx("div", Object.assign({}, columnProvided.dragHandleProps, { children: customRenderColumnHeader(column) }), void 0), allowAddCard && _jsx(CustomRenderCardAdder, { column: column, onConfirm: onCardNew }, void 0), _jsx(DroppableColumn, Object.assign({ droppableId: String(column.id) }, { children: column.cards.length ? (column.cards.map((card, index) => (_jsx(Card, Object.assign({ index: index, renderCard: (dragging) => renderCard(column, card, dragging), disableCardDrag: disableCardDrag }, { children: card }), card.id)))) : (_jsx("div", { className: 'react-kanban-card-skeleton' }, void 0)) }), void 0)] }), void 0));
+                }
+        }), void 0));
 };
 export * from './components';

Again, this is just a quick hack/POC. Having render methods passed down via the root components is probably the correct pattern. It may make sense to use context internally though, just to prevent prop drilling.


Support multiple configurations per project

Enhancement Suggestion
Support multiple configurations (Romefile) per project and allow specifying which configuration it uses for each run.
Steps which explain the enhancement or reproduce the bug
N/A
Current behavior
Rome currently only support one configuration per project, which it takes from the Romefile in the project root directory.
Suggested behavior
Other than the current default setting, which Rome reads config from a Romefile file in the project root directory, Rome should allow specifying arbitrary Romefile for each run.
Examples
Romefile
[Cache]
  S3-Bucket = ios-dev-bucket

[RepositoryMap]
  Alamofire = Alamofire

Romefile.xcode10
[Cache]
  S3-Bucket = ios-dev-bucket

[RepositoryMap]
  Alamofire = static/Alamofire

rome download # read cache config from Romefile and download caches.

rome download --config Romefile.xcode10 # read cache config from Romefile.xcode10 and download caches.

Why would the enhancement be useful to most users
Some projects may have to support multiple version of Xcode or multiple version of Carthage at the same time. Dynamically frameworks are built and placed in Carthage/iOS/Build directory, while frameworks built with overrided MACH_O_TYPE = staticlib build setting are built and placed into Carthage/iOS/Build/Static directory. With the first Romefile, Rome won't see frameworks that were built into the Carthage/Build/iOS/Static directory. With the second Romefile.xcode10, Rome won't see frameworks that were built into the Carthage/Build/iOS directory.
Rome version:
v<IP_ADDRESS>
OS and version:
macOS 10.13.6 (17G65)

Sounds good.

@blender Looks like it works without any issue. Can you publish this version to CocoaPods?

@thii sure, I just want to:

[ ] add integration tests
[ ] update readme

and then it's ready to go.
Check back in 1 hour or so.

@thii  it's all out there.

@blender https://github.com/OpenShelter/fastlane-plugin-rome/pull/7


Tests in created gradle project fail with java.lang.SecurityException

I created a gradle project using the Create Java Project command from the command palette
When executing a gradle build, the test task failed.
The following inner exception was thrown: Caused by: java.lang.SecurityException: Prohibited package name: java.gradle
This was caused by the package name (java.gradle) that was used for the generated classes App and AppTest
When changing the package name for both classes, the gradle build executes without errors
Visual Studio Code Version: 1.68.1 (user setup)
Extensions:
Project Manager for Java v0.20.0 (from Extension Pack for Java v0.23.0)
Gradle for Java v3.12.1
JDK (preset from Extension Pack Setup):
openjdk version "17.0.3" 2022-04-19
OpenJDK Runtime Environment Temurin-17.0.3+7 (build 17.0.3+7)
OpenJDK 64-Bit Server VM Temurin-17.0.3+7 (build 17.0.3+7, mixed mode, sharing)

You should not use java as a segment of a package name. Changing to another name would solve this issue.

I know that I should not use java as part of a package name.
Maybe I didn't make it clear enough that this package name was generated by the "Create Java Project" (with gradle) command from the command palette. As far as I could determine, this command is part of your  VS-Code plugin "Project Manager for Java"

Actually the project creation behavior is delegated to Gradle for Java extension. It will not check your package name since Gradle itself won't do such thing. you can verify it via CLI command gradle init to create a new project.

@kriber82 if you have more questions about creating Gradle projects, feel free to file issues at https://github.com/microsoft/vscode-gradle/issues.
Thanks.


Use the desired button size for new image, fixes #31

If the image needs resizing, use the button size so that thebutton can draw.
Fixes #31

Thanks!

Thanks!


DBZ-1255

Supersedes https://github.com/debezium/debezium/pull/992

Hey @ivanobulo, so I've added one commit to this PR which changes an existing test, demonstrating that the value overflow issue still is present (this went unnoticed in your original PR, as there was no integration test that would test the actual value as sent to Kafka). I.e. the conversion to epoch nanos still is part of the code flow somewhere. Would you like to take a look into that one?

Essentially, the thing to look for is the invocations of Conversions#toEpochNanos(), which should be avoided. All the time related code is a bit convoluted, sorry for that. On the test btw., the change to OutboxEventRouterIT was just a quick reproducer for the issue; eventually, there should be a test for large temporal values in AbstractRecordsProducerTest (look for "time_table").

Thanks for adding those extra tests.
Could you please merge the changes from my branch with your changes?
I got all the tests pass in my branch right now:
https://github.com/ivanobulo/debezium/tree/dbz-1205b

@gunnarmorling I've finally made your test pass! Please merge with my branch. It already includes your changes too so there should be no merge conflicts.

@gunnarmorling Have you had a chance to merge with the changes I've made?

Hey @ivanobulo, yes, I'm on it; I took this as the opportunity to do a larger clean-up around these temporal times, PR based on your original change will come in a bit.

@ivanobulo, ok, I've rebased this PR to the current master and pushed my work. Can you take a look and give it a test in your environment? I've done some more clean-up -- see the updated PR description for the overall approach. I aimed at avoiding the usage of longs internally for representing temporal values, only at the system boundary the values will be converted to longs, representing millis or micros in MicroTime etc.
@Naros, if you could check this out, too, that'd be great, changes to the temporal stuff are always a bit sensitive. I feel it's in a much better shape now than before, though, due to the avoidance of using long for internal time/date mappings.
Thanks for any feedback!

Hi @gunnarmorling and @ivanobulo, this is definitely great work!
The test failure related to heartbeat was fixed in PR #999.  Once that gets merged and this branch rebased, all tests should be great; otherwise it LGTM.

Ok, so there are still some failures on CI, but they seem intermittent and caused by timing issues in assertions. Will merge and we'll see how the master job likes it.

@ivanobulo, would still be very much interested in your feedback, if you have a chance for testing this. Thanks!


[flutter_tools] reduce mocking in error handling io

Part of #71511.

I'm really running out of steam on these, so close though...

remove_all_mocks_for_real_this_time!


Since last update Suspense with RouterView acting weird

Vue version
3.3.10
Link to minimal reproduction
https://codesandbox.io/p/devbox/upbeat-ully-64czlg?file=%2Fsrc%2FApp.vue%3A10%2C35
Steps to reproduce
Navigate between ViewA and ViewB.
What is expected?
HTML elements suppose to keep same order (Navigation, RouterView, Footer) after navigating between views.
What is actually happening?
HTML elements being rendered in wrong order (Navigation, Footer, RouterView) after navigating between sync (ViewA) and async (ViewB) views.
System Info
No response
Any additional comments?
Ran into an issue after updating Vue to 3.3.10. Looks like it's related related to latest (3.3.10) release changes (https://github.com/vuejs/core/issues/8105) and is most likely not related to Vue Router itself, but rather to async components.
— Issue persists even if I toggling between components programatically, without RouterView.
— Removing timeout property from Suspense gives weird delay but footer stays in place.
— Wrapping Suspense in to div makes Footer to stay in correct order.

Most likely related to https://github.com/vuejs/core/pull/9309
/cc @edison1105


Fix PREFIX value for mempool app API

I'm trying to use the API of my running node, but I think there's a problem with the configuration file of the mempool app:
(the address is not mine)
curl -s http://umbrel.local:3006/api/address/bc1qh9c7xfz0eu3kvqtz6lgm0v0nqvcg5nkrwn3k6m/txs/mempool
<!DOCTYPE html>

<meta charset="utf-8">
<title>Error</title>

Cannot GET /api/v1/address/bc1qh9c7xfz0eu3kvqtz6lgm0v0nqvcg5nkrwn3k6m/txs/mempool

But syntax is ok and works fine with mempool.space site:
curl -s https://mempool.space/api/address/bc1qh9c7xfz0eu3kvqtz6lgm0v0nqvcg5nkrwn3k6m/txs/mempool
[]

Have you noticed the v1 added in the url on my node?

Update:
It seems related to the requested endpoint, as this command works fine:
curl -s http://umbrel.local:3006/api/address/bc1qh9c7xfz0eu3kvqtz6lgm0v0nqvcg5nkrwn3k6m/txs

Closing due to inactivity, let us know on https://community.getumbrel.com if the API is still giving you trouble.


Custom Pet Images

Allow uploading of custom individual pet images for a pet. Only those who can edit inventories can set these images.
Adds in a custom "pet page" that can be used to also give a pet a custom bio or keep track of info, both admins and users can edit these.
The creation of the "pet page" was mostly to avoid the confusion of having to get admins to sift through pets to give images to them, for example on my site some people have maybe 50+ pets, so having a direct link that admins can set images from is very useful.
I might end up doing more with the custom page in the future, since I know people want ways to "grow" pets up/etc.
php artisan migrate php artisan optimize

hi! went thru this pr and found some things that needed fixing up with Uri, we've merged your changes and added your credits thru the commit, it was just easier at the time to work directly on the branch since we're making some pet drop changes
this is an awesome change, for future try to squash commits and make functions descriptive (i.e. don't do $Service->desc to update an image description
looking forward to reviewing evolving / levelling!


Unable to create multiple tables within a single database

When attempting to create a second table within a single database, nothing happens; the table isn't created and the promise or callback is not fired on any call to setItem, for example.
I'm experiencing this issue with Google Chrome (35.0.1916.153) and IndexedDB.
An example of the issue can be viewed here: http://jsfiddle.net/kriswillis/uK3Qz/ - After loading the fiddle, "table1" is created under the "myApp" database, when changing the page variable to 2 and re-running, "table2" is not created.

A year later I have this problem too - hoping to have 3-4 tables in my app.

I want to do the same. This looks to work:

"var items = localforage.createInstance({ name: "mydatabasename" , storeName: "items" });
var config = localforage.createInstance({ name: "mydatabasename" , storeName: "config" });
items.setItem( "foo", {"id":123 , "name":"bar" } );
config.setItem( "user" , "dilbert" );"
Doesn't work for me.
It creates only "items" ObjectStore

any updates?

No updates from me, but if someone could find the reason for the bug and patch it I could certainly review it quickly.
I have less time to hunt down bugs right now so I can't give a date on this, though I understand it's a frustrating issue.

for current implementation it seems like the only workaround to create new ObjectStore inside current database is to increase db version.
var items = localforage.createInstance({ name: "testdatabase" , storeName: "items" });
items.setItem( "foo", {"id":123 , "name":"bar" } );
var config = localforage.createInstance({ name: "testdatabase" , storeName: "config", version: 2});
config.setItem( "user" , "dilbert" );
But I'm not sure that it is a good solution.

@mbalyaba Your workaround shouldn't be necessary because this issue (similar to #342) has been fixed by https://github.com/mozilla/localForage/pull/452 and released in 1.3.0 (and 1.3.1 for Ember).
Which version do you use? Do you have any error in the console?

Oh, sorry, my version is 1.2.2. In this version I have an error about non exist ObjectStore(for second instance).
Anyway if issue is fixed then it is a very very good news!
I will update.
Thank you!

@tofumatt I think we should close this issue, since it's related to #342 which has been fixed.

Ah okay, sounds good.

tofumatt (Sent from mobile)

On 7 Jan 2016, at 10:45, Sébastien Tisserant<EMAIL_ADDRESS>wrote:
@tofumatt I think we should close this issue, since it's related to #342 which has been fixed.
—
Reply to this email directly or view it on GitHub.

@mbalyaba You may now experience the following issue with Chrome on first startup:
Failed to execute 'transaction' on 'IDBDatabase': The database connection is closing.

If so, please refer to #492 in which it has been recently reported.

I want to do the same. This looks to work:
var items = localforage.createInstance({ name: "mydatabasename" , storeName: "items" });
var config = localforage.createInstance({ name: "mydatabasename" , storeName: "config" });
items.setItem( "foo", {"id":123 , "name":"bar" } );
config.setItem( "user" , "dilbert" );

Why isn't this included in the documentation @tofumatt & @sebweaver ? I was very close to switching to another library until I finally found this issue.
I've read everything, did I miss something? It would be nice and clear to have a section like "Create multiple tables in one DB instance".
Thanks a lot!

@owenfar There is documentation about multiple instances on the main API docs page, linked in the repo: https://localforage.github.io/localForage/#multiple-instances
Is there something missing from there for you? For what it's worth, I'm in the process of redoing the docs and the website, but for now I think the docs there cover multiple instances.

@tofumatt That section about multiple-instances is very clear, but multiple instances act as different "databases". It is not shown or is very clear to me that in an instance we can create different stores. From the docs I thought that I could only created different DBs, and not different storeNames (tables).
I think that for newcomers it would be very beneficial to have another section called "Create multiple stores in the same instance" and show a clear example of that, same as I quoted in the previous comment, or something like:
`const dbName = 'databaseName';
// Create table 1 in databaseName
_os_db.states = localforage.createInstance({
driver      : localforage.INDEXEDDB,
name        : dbName,
storeName   : 'tableOne',
description : '...'
});
// Create table 2 in databaseName
_os_db.states = localforage.createInstance({
driver      : localforage.INDEXEDDB,
name        : dbName,
storeName   : 'tableTwo',
description : '...'
});`
Do you think this would be better?

That looks great! Would you mind submitting a PR with those changes? 😄

@tofumatt Awesome. Sure, I'll do that now :)

@tofumatt That section about multiple-instances is very clear, but multiple instances act as different "databases". It is not shown or is very clear to me that in an instance we can create different stores. From the docs I thought that I could only create different DBs, and not different storeNames (tables).
I think that for newcomers it would be very beneficial to have another section called "Create multiple stores in the same instance" and show a clear example of that, same as I quoted in the previous comment, or something like:
const dbName = 'databaseName';

// Create table 1 in databaseName
var tableOne = localforage.createInstance({
      driver      : localforage.INDEXEDDB,
      name        : dbName,
      storeName   : 'tableOne',
      description : '...'
});

// Create table 2 in databaseName
var tableTwo = localforage.createInstance({
      driver      : localforage.INDEXEDDB,
      name        : dbName,
      storeName   : 'tableTwo',
      description : '...'
});

Do you think this would be better?

By the way does this works? Have you tested? I can not make it work... Used the example above... It only created 1 storeName inside the DB.

@MiguelQueiroz Yes it should work, perhaps something else is going wrong. Can you share what you did so that we can better help you?

@MiguelQueiroz Yes it should work, perhaps something else is going wrong. Can you share what you did so that we can better help you?

yes, try this.
So the databases are only generated, when they are followed or called by a setItem, meanwhile they are not created. Which is very confusing, because the docs don't say that.
https://jsfiddle.net/fvx9kao3/

Is it a problem for you that the DB is not created until an item exists? Not sure if this is the normal behaviour, but if the code works when an item is added, there's not much I can do for you. Perhaps you can open another issue as it's not related to this one. Best, Owen


fix: remove ++ in throwError in favor of {""}

This correctly interpolates the error messages
in the cases' tactic.
Reported at:
https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/uninterpolated.20error.20message.3A.20unecessary.20generalizing/near/400018518

Let's add some tests to test/cases.lean
/-- error: unnecessary 'generalizing' argument, variable 'a' is generalized automatically -/
#guard_msgs in
example (n : ℕ) (a : Fin n) : True := by
  induction' n generalizing a

/--
error: variable cannot be generalized because target depends on it
  m
-/
#guard_msgs in
example (m : ℕ) : True := by
  induction' m generalizing m

(I didn't test the tests -- you'll probably have to update the docstrings.)

bors r+


Update depcheck to latest

There were a great deal of fixes and new features lately

@rumpl  is someone going create a new release for this?

I have no idea and no write permissions on this repo 😅
@dylang ?

There is a couple of PR for updating dependencies, I would stick to one, like https://github.com/dylang/npm-check/pull/368 and try to get it merged.

Why isn't this merged yet? @dylang Please update dependencies to resolve security issues :)

When will be merged it?

fixed in #368


Signals shorter than 0.5 seconds return -inf using global loudness function

How can we get a value from a signal that is too short?

If your signal duration is less than 500 ms and you are using a 75 % overlapping between blocks, you are only measuring one 400 ms gating block (the first one). If the block loudness is under the threshold (-70 LUFS in EBU R128), the integrated loudness over the signal is actually -∞ LUFS. See https://www.itu.int/dms_pubrec/itu-r/rec/bs/R-REC-BS.1770-4-201510-I!!PDF-E.pdf for details.
Not sure what you're trying to achieve, but you could use the Momentary measure to get information on short segments. Notice that a Momentary measurement on a silent 400 ms segment will also produce a -∞ LUFS result.

Excuse me, is there any way to get the loudness information of WAV files with a shorter length, such as less than 0.4s. I found that such files as reaper or youlean loudness meter 2 can be retrieved, but I haven't found a way yet. Please give me some advice. Thank you very much!!

I want to get a value other than - 70 and negative infinity. Loudness measurement software can do it. But I didn't find a way


Feature Request: Option to disable setext headers in markdown mode

I know that setext headers are part of the commonmark spec, but our users find them unexpected and confusing (particularly when only a single character is used), in part because we style cm-header-2 to match the font size it will be rendered at

Would it be possible to add an option to disable setext headers to the markdown modeConfig in the same way other markdown features can be enabled/disabled like strikethrough
Alternatively, the spec says

If a line containing a single - can be interpreted as an empty list items, it should be interpreted this way and not as a setext heading underline.

which if implemented would largely solve our issue as well.
Thanks very much 👍

Thanks as always @marijnh for being such a responsive maintainer 👍


[stacked_firebase_auth] Return firebase user, exposed firebaseAuth for easier access, bumped versions for Google, Apple and Facebook plugins

Related to #267 discussion
Changed FirebaseAuthenticationResult to return Firebase User object instead of only uid and userToken.
Made firebaseAuth public for easier access from FirebaseAuthenticationService.
Bumped versions to latest for Google, Apple and Facebook plugins.
This was needed for fixing a version solving failed problem with the latest firebase_core and current flutter_facebook_auth.
Because flutter_facebook_auth >=2.0.0-web.8 <3.0.0-nullsafety.0 depends on flutter_facebook_auth_platform_interface ^1.0.1 which depends on plugin_platform_interface ^1.0.1, flutter_facebook_auth >=2.0.0-web.8 <3.0.0-nullsafety.0 requires plugin_platform_interf0-nullsafety.0 requires plugin_platform_interface ^1.0.1.
And because firebase_core >=1.0.0 depends on firebase_core_platform_interface ^4.0.0 which depends on plugin_platform_interface ^2.0.0, flutter_facebook_auth >=2.0.0-web.8 <3.0.0-nullsafety.0 is incompatible with firebase_core >=1.0.0.rebase_core >=1.0.0.
So, because stacked_firebase_auth depends on both firebase_core ^1.0.1 and flutter_facebook_auth ^2.0.2+1, version solving failed.

Maybe we can add
export 'package:firebase_core/firebase_core.dart';
to stacked_firebase_auth.dart for easier access to Firebase.initializeApp()?
This will enable autocomplete for Firebase Core everywhere stacked_firebase_auth is imported and there will be no need to manually import firebase_core.


Add LUFA boards to Tools>Board menu

I've been using LUFA a lot in various arduino projects, but am still using non-LUFA code as well, and switching was a bit tedious sometimes so I made it so that enabling/disabling LUFA is as easy as selecting the correct board type in the arduino IDE.
I've tested it on windows as well as ubuntu (I've also checked that activate/deactivate still work as intended).

Alright, looks good to me!
I think we can pretty much remove most boards except for those that use an Atmega32u4 or other MCU with its own USB-interface. See https://en.wikipedia.org/wiki/List_of_Arduino_boards_and_compatible_systems
I had a look in the boards.txt, and it seems the only boards compatible are:

Yún
Yún Mini
Leonardo
Leonardo ETH
Micro
Esplora
LilyPadUSB
Robot Control
Robot Motor
Adafruit Circuit Playground 32u4 w/Caterina Configuration
Industrial 101 (Chiwawa)
Linino One

The simplest is probably to search for .build.mcu=atmega32u4 in the boards block, and remove the board if it doesn't contain that.

ok I followed your suggestion and am now commenting out all boards which don't hve atmega32u4. Changed the readme to reflect this as well.
btw in the mean time I also researched info on how to add these directly to the board manager so that we don't even have to use a python script at all.
with external boards URL
We need to create a "release" from the repo so that there's a zipfile with the boards files prepackaged, and create a json with some headers to point to that github hosted zip.
Then we can instruct the user to add the URL to the json in the "additional custom boards URL" list, and from there they should be able to see LUFA boards in the manager and install from there.
directly in the main boards
Then we can create a PR on the arduino repo to add these boards to the existing manager, but for it I think we should also have the library added as a lib in the library manager. Which will require to add a couple new definition files, but also requires us not to use submodules, so we'd have to break the link to the LUFA repo and put their files directly on this repo.
I think having a "install lufa from library manager, then install lufa boards from board manager" would be awesome.

@Palatis, this can be merged now! Code quality is great and everything works as expected!
@CrazyRedMachine Thank you once more for this contribution, awesome stuff! I think there's some potential in looking at the board+library manager further, would you like to open a new issue for that? I'll gladly help with research and testing.


Removed Unused Dependencies & old e2e

Description

Removed old e2e and its associated package.json commands
Removes unused packages from package.json's
Updates useAPIRequest.test.ts to play better with hook testing

How to test

Test everything including Unit Tests, Cypress, and Storybook

@bnussman we also have tests for components via selenium that are the files ending in .spec.js in each component directory that can be removed. @ndukatz @bnussman have you thought about testing components with storybook via cypress at all?

I'm so sorry 😢 @patthiel. I'm not dead set on merging this PR, just wanted to put it up as a proof of concept for cleaning up the repo. I think we have the ability to test storybook via cypress, but we just don't right now.


Rviz plugin tier4_localization_rviz_plugin/InitialPoseButtonPanel does not exists

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
I just pulled latest Autoware and am testing it. When I start autoware, rviz reports the following error:
[rviz2-74] [ERROR<PHONE_NUMBER>.618417957] [rviz2]: PluginlibFactory: The plugin for class 'tier4_localization_rviz_plugin/InitialPoseButtonPanel' failed to load. Error: According to the loaded plugin descriptions the class tier4_localization_rviz_plugin/InitialPoseButtonPanel with base class type rviz_common::Panel does not exist. Declared types are  AutowareDateTimePanel AutowareScreenCapturePanel rviz_plugins/ManualController rviz_plugins::AutowareAutomaticGoalPanel rviz_plugins::AutowareStatePanel rviz_plugins::BagTimeManagerPanel rviz_plugins::RTCManagerPanel rviz_plugins::SimulatedClockPanel rviz_plugins::TrafficLightPublishPanel rviz_plugins::VelocitySteeringFactorsPanel tier4_adapi_rviz_plugins::RoutePanel tier4_calibration_rviz_plugin/AccelBrakeMapCalibratorButtonPanel (operator()() at ./src/main.cpp:68)

So apparently, tier4_localization_rviz_plugin/InitialPoseButtonPanel plugin is missing on my machine. But I can't find it anywhere:
$ rg -l InitialPoseButtonPanel src
src/universe/autoware.universe/planning/obstacle_avoidance_planner/rviz/obstacle_avoidance_planner.rviz
src/universe/autoware.universe/planning/static_centerline_optimizer/rviz/static_centerline_optimizer.rviz
src/universe/autoware.universe/vehicle/accel_brake_map_calibrator/accel_brake_map_calibrator/rviz/occupancy.rviz
src/universe/autoware.universe/perception/lidar_centerpoint/launch/centerpoint_vs_centerpoint-tiny/rviz/centerpoint.rviz
src/universe/autoware.universe/perception/lidar_centerpoint/launch/centerpoint_vs_centerpoint-tiny/rviz/centerpoint_tiny.rviz
src/launcher/autoware_launch/autoware_launch/rviz/autoware.rviz

Where is this plugin supposed to be built?
Expected behavior
No error on startup
Actual behavior
error message on startup
Steps to reproduce
Launch autoware?
Versions
No response
Possible causes
No response
Additional context
No response

@VRichardJP Hi.
That package was recently removed. https://github.com/autowarefoundation/autoware.universe/pull/4519

In that case, the .rviz config files should be updated accordingly, right?

@VRichardJP Yes! you are right.
Sorry, I forgot to remove it from the .rviz config files.


Add Jira to Scrum tools

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Duplicate pull request.
Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


mongoapi:save of a map fails with function_clause

First of all, many thanks for your effort.
In the mongoapi:save the oid is prepended to the document being saved:
https://github.com/SergejJurecko/erlmongo/blob/master/src/mongoapi.erl#L37
This works fine for proplists, but if I save a map, then bson:encode fails, because all elements are expected to be {Name, Value} tuples.
I believe that if L is a map, you should do L#{<<"_id">> => {oid, OID}} instead.

Thank you very much for reporting the issue.


Release Termdash v0.16.0.

v0.16.0 - 03-Apr-2021
Added

The Text widget has a new option MaxTextCells which can be used to limit
the maximum number of cells the widget keeps in memory.

Changed

Bump github.com/mattn/go-runewidth from 0.0.10 to 0.0.12.

Pull Request Test Coverage Report for Build 2246

60 of 62 (96.77%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 91.313%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

widgets/text/options.go
6
8
75.0%

Totals

Change from base Build 2198:
0.03%

Covered Lines:
8441

Relevant Lines:
9244

💛  - Coveralls

Pull Request Test Coverage Report for Build 2246

60 of 62 (96.77%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 91.313%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

widgets/text/options.go
6
8
75.0%

Totals

Change from base Build 2198:
0.03%

Covered Lines:
8441

Relevant Lines:
9244

💛  - Coveralls


feat(calendar): toggle responsiveness and pass custom break point function

Checklist

[x] If committing a change of production code, I have tested it in different browsers (Chrome, Firefox, Safari).
[ ] If committing a new feature, I have first submitted an issue (Please note: you are free to open PRs for non-issued features, but opening an issue increases your chance of a successful PR).
[ ] If committing a new feature, I have also written the appropriate tests for it.
[X] I have tried to build the feature in a way, that it does not cause any breaking changes for others (unless
agreed upon in an issue).

This PR solves the following problem**.
adds ability to toggle responsiveness of calendar (resizing on change of viewport width) and the option to pass a custom break point function that even this break point.
reference our chat on Discord
authors:  @struvelig & @malteamlimit

Thanks again for adding this.
Will be included in the next release :)


Mnist script

Added Mnist utils in order to process it with DataLoader. Also includes some tests.

Pushed again into that branch. There was an issue with GPU compatibility. It should be fixed now.


Feature/support local update

This feature is helpfull when dealing with huge projects with lots of dependencies, when update-deps becomes more expensive.

Hi there! This is great stuff. It would be easier for me to review if you separated out the different additions:

dealing with raw (thought I had merged fixes for that already on master?)
update local
SHA instead of tag
keep first (I thought we were already preserving order in a reasonable way?)
safer way to run commands.

And then make sure everything is rebased on master as you go.
Lastly, if there's any way to add some test coverage for some of these additions... that would be super awesome. There's the start of some test fixtures in the code now.

Hi, I formed pullrequest in one commit as you suggested, sorry for not doing it in the original pullrequest, i was wondering whether you were interested in this functionality at all)
Update fun is rather trivial from my point of view, but if you think it's important to add test for this I will write them a little bit later.

I'll merge this now. Seems to do what you've describe for me as well :)
I think we might want to emphasize in the docs (and maybe consider a different subcommand name) that what we are doing is updating the versions in deps to make it conform to what is in the lock file. The bisect use case makes a ton of sense and I see how this could be a real time saver.
Another enhancement that would be nice is to only print a message if the SHA of the dep is actually being updated. Right now, it seems to say "updating" for everything even when those pinnings aren't changing.

Great, thank you)


Remove any .idlHeader descendents in extractRespecIdl

Adapting to https://github.com/w3c/respec/pull/2663.
Fixes https://github.com/tidoust/reffy/issues/205.

@tidoust I can't quite figure out the testing setup for this repo. Both jasmine and mocha are dependencies and I see some tests in spec/*. npx jasmine does find and try to run these, but there are failures.
I see https://github.com/tidoust/reffy/issues/165 but what should I do with a change like this?

@foolip There will be another markup change in ReSpec WebIDL blocks (https://github.com/w3c/respec/pull/2701).
It won't break reffy, but letting you know as you asked :slightly_smiling_face:

Thanks @sidvishnoi! Happily I didn't select for the element type, so you're right this shouldn't affect Reffy.


error with starting

i seem to get this error when ever i start up the bot
SyntaxError: invalid syntax
Restarting Bot..
File "bot.py", line 80
async def on_ready():
im running the bot on a google windows cloud server any help would be awesome

I believe you need to run the bot with python3 instead of python since only version 3.0 and up have async, or something like that. It worked for me to literally just use "python3" instead of the command "python" but I can't promise that'll work.

I'll need to update this issue unfortunately, I have python 3.6 installed (in local, I will host it later on a python  3.7 or 3.8). And the bot sends me this everytime I launch it
Logged in as
WyvernBeta
632651106413182976
------
Ignoring exception in on_ready
Traceback (most recent call last):
  File "C:\Users\EnderKiller06\AppData\Local\Programs\Python\Python36\lib\site-packages\discord\client.py", line 242, in _run_event
    await coro(*args, **kwargs)
  File "C:\Data\Devellopement\BotDiscord\Discord-Werewolf-master\bot.py", line 91, in on_ready
    for role in client.get_server(WEREWOLF_SERVER).role_hierarchy:
AttributeError: 'Client' object has no attribute 'get_server'

This requires Python3.6 and Discord.py 0.16.x (I use 0.16.12)
You can install 0.16.12 via this command "pip install discorc.py==0.16.12"


How to add a backup key?

Can you add a section explaining how one would add a second yubikey as a backup device?

Wondering this as well. I'm taking a look at the options available under boot.initrd.luks.devices.*.yubikey and it really just seems like only a single yubikey is supported, unfortunately.

Can you advise how to add at least a backup passphrase, for when your yubikey is lost?

Yeah, sorry, I think I can probably come up with something.

Be sure to delete luks.key afterwards
KEY_LENGTH=512
ITERATIONS=1000000
read -s k_user
challenge=$(head -n1 /boot/crypt-storage/default | tr -d '\n' | openssl dgst -binary -sha512 | rbtohex)
response="$(ykchalresp -2 -x $challenge 2>/dev/null)"
echo -n $k_user | pbkdf2-sha512 $(($KEY_LENGTH / 8)) $ITERATIONS $response > luks.key
Now, you can pass the luks.key to any cryptsetup command. For instance,
if you want to add another key to your setup.
cryptsetup luksAddKey /dev/nvme0n1p2 luks.key
rm luks.key

@Deep-Six That's awesome! Feel free to add that to the README somewhere


add log and continue when step parsing fails for completion #2632

Thanks!
I saw many adjacent places where errors are beiing swallowed in this parsing code (in ways that would cause crashes on nil) so I began to assume I was missing something.

Yeah, i suppose that is a bad idea. I will give it another go when I find a bit more time, but at the least I'd say we should log it