Company Cards - Bank UI

Details
Company Cards - Bank UI flow
Fixed Issues
$ https://github.com/Expensify/App/issues/50448
PROPOSAL:
We will use here "example url" - https://secure.chase.com/web/auth/#/logon/logon/chaseOnline?redirect_url=
User should have company cards available
Tests
WEB, Desktop, mWeb:
For WEB - to open a new tab in modal overlay - browser should not be in full screen mode

Choose any bank account (not Other) -> Next (For Brex point 2 is skipped)
Choose Direct feed or Business Card (for Amex)
Verify that user sees a new screen with image, text and link button to open a new tab
Verify that new tab was opened in default browser with "example url"
Close a new tab and move back to app screen
Click on link to open a new tab -> Verify that new tab is opened
Move back to the app -> click Go back button -> Verify that opened tab with "example url" is closed as well (not working for Desktop - based on global rule set here)
Verify that go back land user to Select Feed or Card Type for Amex or Select Bank for Brex

Native App:

Choose any bank account (not Other) -> Next (For Brex point 2 is skipped)
Choose Direct feed or Business Card (for Amex)
Verify that user sees "example url" opened in WebView
Click Go back button -> Verify that go back land user to Select Feed or Card Type for Amex or Select Bank for Brex

[x] Verify that no errors appear in the JS console

Offline tests
Same rules as was defined to the whole feature
QA Steps
WEB, Desktop, mWeb:
For WEB - to open a new tab in modal overlay - browser should not be in full screen mode

Choose any bank account (not Other) -> Next (For Brex point 2 is skipped)
Choose Direct feed or Business Card (for Amex)
Verify that user sees a new screen with image, text and link button to open a new tab
Verify that new tab was opened in default browser with "example url"
Close a new tab and move back to app screen
Click on link to open a new tab -> Verify that new tab is opened
Move back to the app -> click Go back button -> Verify that opened tab with "example url" is closed as well (not working for Desktop - based on global rule set here)
Verify that go back land user to Select Feed or Card Type for Amex or Select Bank for Brex

Native App:

Choose any bank account (not Other) -> Next (For Brex point 2 is skipped)
Choose Direct feed or Business Card (for Amex)
Verify that user sees "example url" opened in WebView
Click Go back button -> Verify that go back land user to Select Feed or Card Type for Amex or Select Bank for Brex

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/7f516403-a225-4ba7-9871-62859a2323a8

Android: mWeb Chrome
https://github.com/user-attachments/assets/a370aa62-3ae5-4889-b8da-625a1bf224f2
https://github.com/user-attachments/assets/43575244-44c5-4a4b-8fc7-8c2ee1f3f69c

iOS: Native
https://github.com/user-attachments/assets/9d952ae3-7d4f-43e5-a484-ff880baa3eb4

iOS: mWeb Safari
https://github.com/user-attachments/assets/d49c230c-e0aa-4dc3-b163-1aab29e0af8d

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/3f0ba70b-0caf-4537-bc53-e0169e3771e4
https://github.com/user-attachments/assets/0d0e2435-3f64-4b07-b6b4-02279beac04c

MacOS: Desktop
https://github.com/user-attachments/assets/b0c00f7f-2894-4a1c-8011-7ff3afa0a12d

The videos look pretty good to me. The only thing that caught my eye was that when you manually press the link here:
...can we make that open up the Chase/bank login window the same way it previously opened (small window centered on top) rather than a new tab? Or maybe we're doing a new tab on purpose?

@shawnborton i think it was just an example video from @allgandalf to show that when we click back button - tab is closed. Technically when browser is not in a full mode and user clicks on the link - we will open new browser in a modal:
https://github.com/user-attachments/assets/40f2af7e-2b40-4d5e-8347-86394c348ff7

Okay great, thanks for confirming!

Reassure Performance Tests / perf-tests (pull_request) Failing after 17m

Processing measurement 1: [ReportScreen] should render ReportScreen
Error: Render count difference exceeded the allowed deviation of 0. Current difference: 1

There is nothing in this PR that could influence the ReportScreen rendering so I will go ahead and merge it @OlimpiaZurek any  chance this could be related to the change from last week

This is not an emergency, seems like the Reassure test is broken at the moment so I proceeded with merging


chore(release): 2.29.0

Version bump in package.json and package-lock.json for release 2.29.0

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove some files from the repo root

Fixes #51444
The only potentially scary thing here is the docker change; it requires buildkit, but that should work so long as all of our images are Linux-based (which they are).
This removes 5 files from the repo root.

@typescript-bot user test this slower

@typescript-bot user test this slower

The long user task appears to be broken, but that seems to be unrelated to this PR. I can confirm from the logs that the docker stuff works as expected: https://typescript.visualstudio.com/TypeScript/_build/results?buildId=139770&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b&t=7cc137c2-61f2-5d65-b5f8-0e03d1af3170&l=1057
#2 [internal] load .dockerignore
#2 sha256:4a4ed123b7937fef327b6f12d7babeb7c7a07d5a8af63a162e6f811bf52948b2
#2 transferring context: 2B done
#2 DONE 0.0s

#1 [internal] load build definition from Dockerfile
#1 sha256:e6e25f4c61172b287941e50a438f9a94a99c43b98323adec666262af669c5696
#1 transferring dockerfile: 932B 0.0s done
#1 DONE 0.1s

#4 [auth] library/node:pull token for registry-1.docker.io
#4 sha256:9d889029f2fe9cc4ecee8c32e4b6949103b3aa1f0c32d07372b8410ce7579e3e
#4 DONE 0.0s

#3 [internal] load metadata for docker.io/library/node:current
#3 sha256:a8f9e90e756db67758be7de595ae6d22761b7409621f0db40bca2c65d7f7f599
#3 DONE 0.3s

This is buildkit output, and it's finding the new paths for the dockerignore and Dockerfile correctly, so this change looks to be safe.


Map canonical links to their models

Signed-off-by: Ashton Larkin<EMAIL_ADDRESS>🎉 New feature
Closes #706
Follow-up to #685 and #678
Summary
When calling UpdateSim in the physics system, we have to update a model's pose if the model's canonical link changed. We are currently handling this by iterating through all models in the ECM because:

The ECM implicitly gives us a topological ordering of models, which allows us to handle nested model updates correctly since nested model poses are stored with respect to their parent model's pose.
For each changed canonical link, we have no way of knowing which models view this link as its canonical link (unless we recurse upward via parent models, checking canonical links along the way - this is inefficient to do for every canonical link in each simulation update, and is also difficult code to maintain/understand), so we result to getting each model and seeing if its canonical link has changed.

This PR should resolve both of these issues, and also removes the need for looping through the ECM to check for model updates, which should result in a performance improvement for worlds with a lot of non-static models that do not change often.
Test it

Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge

Note to self: The component I am working on in this PR can be used when canonical links are created in the SDFEntityCreator: https://github.com/ignitionrobotics/ign-gazebo/blob/ignition-gazebo5_5.0.0/src/SdfEntityCreator.cc#L211-L430
Then, in the physics system, instead of looping through all of the models in UpdateSim, I can loop through all of the changed links, see if a link has this new component (it will if it's a canonical link), and if so, then I can update all of the models that are in this component.
I may need to change ChangedLinks to return a std::map instead of std::unordered_map to ensure that the links are also being iterated through in topological order... I'll need to think about this some more (I can imagine that this may be an issue with nested models if a parent and nested model change pose on a given iteration, but the nested model's canonical link is checked first before the parent model. This would mean that the nested model is updated before the parent model, which would be incorrect since the nested model needs to be updated with respect to the most recent update of its parent model).


When do we expect to get codes, and pre-trained models?

Hi,
I have been waiting on the codes or pre-trained models of your approach for more than two months, when do we expect to have the code?

We have just completed the release of the FMA-Net code, including training, testing, and pretrained model.
Thank you for your interest in FMA-Net.


Linux Web Framework tests is failing with RangeError (index): Invalid value

This is blocking recipes repo and also Fuchsia roll. Failed builds:
Recipe cq failed build
Fuchsia roll failed build
Seems it has been failing in the try builder: https://ci.chromium.org/p/flutter/builders/try/Linux Web Framework tests
Detailed log:
[  +10 ms] /b/s/w/ir/cache/builder/src/out/host_debug_unopt/dart-sdk/bin/dart --disable-dart-dev /b/s/w/ir/cache/builder/src/out/host_debug_unopt/gen/frontend_server.dart.snapshot --sdk-root /b/s/w/ir/cache/builder/src/out/host_debug_unopt/flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=false -DFLUTTER_WEB_USE_SKIA=false --output-dill /b/s/w/ir/tmp/t/flutter_tools.PAQZGR/flutter_test.ELAMIN/out --libraries-spec file:///b/s/w/ir/cache/builder/src/out/host_debug_unopt/flutter_web_sdk/libraries.json --packages /b/s/w/ir/k/flutter/packages/flutter/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-root /b/s/w/ir/k/flutter/packages/flutter/test --filesystem-root /b/s/w/ir/tmp/t/flutter_tools.PAQZGR/flutter_test.ELAMIN/ --filesystem-scheme org-dartlang-app --initialize-from-dill build/e1ffba66f615b3b54e08e2104bac7ab8.cache.dill.track.dill --platform file:///b/s/w/ir/cache/builder/src/out/host_debug_unopt/flutter_web_sdk/kernel/flutter_ddc_sdk_sound.dill --sound-null-safety
[  +12 ms] <- compile org-dartlang-app:///main.dart
[ +141 ms] Unhandled exception:
[   +1 ms] RangeError (index): Invalid value: Not in inclusive range 0..3: 1117348
[        ] #0      List.[] (dart:core-patch/array.dart:268:52)
[        ] #1      BinaryBuilder._readComponentIndex (package:kernel/binary/ast_from_binary.dart:731:48)
[        ] #2      BinaryBuilder._readOneComponent (package:kernel/binary/ast_from_binary.dart:801:29)
[        ] #3      BinaryBuilder.readComponent.<anonymous closure> (package:kernel/binary/ast_from_binary.dart:633:34)
[        ] #4      Timeline.timeSync (dart:developer/timeline.dart:163:22)

/cc @yjbanov

The Dart roll has been failing since https://dart.googlesource.com/sdk.git/+log/4832aa2f161a..b0289f3d4835

@yjbanov couldn't reproduce this locally. @godofredoc is attempting to investigate in infra. I'm going to apply the issue tag, and assign to @godofredoc to report back on the infra investigation.

This is the task running with led:
https://chromium-swarm.appspot.com/task?id=52752ae34a411010

Failing with the same issue, is there a good known engine isolate that I can use?

Same failure when using an isolated built by one of the prod builders: https://chromium-swarm.appspot.com/task?id=5275375359199510

This is a task with the same properties but running with the prod service account in the prod pool: https://chromium-swarm.appspot.com/task?id=52756f70ed867d10

@godofredoc If this is reproducing in prod, why is the engine tree not red?

@yjbanov suggested in chat that we could disable Linux Web Framework on the try bots to unblock engine PRs. If the prod bots are still working correctly, then any failures will be caught there. I think we should do that while we debug the try bots, but that only makes sense if the tree is really supposed to be green right now.

I believe the try jobs are sending the correct signal as they are failing 100% of the time for my manual runs in both try and prod. I'm checking the configs to see why it is not failing in prod.

This should be addressed by https://flutter-review.googlesource.com/c/recipes/+/11420. We can close this when web_tests turns green again on the engine tree.

This is the second CL: https://flutter-review.googlesource.com/c/recipes/+/11461


Change cliff direction marker to dark grey to match the line

Cliffs had their colour changed in 5f9bea67d, but the directional
arrow remained green.

Fixes #6918

Looks good, but can you target the 2.15 branch so we can fast track releasing it?  thanks!

Rebased and retargeted; thanks taking a look so quickly.

@huonw Thanks for the fix!


[ADH-4305] Refactor SmartConf and related classes

Moved SSM hosts files (agents and servers files) parsing logic to the SsmHostsFileReader class
Removed checking if path is covered from WhitelistHelper. Now, PathChecker is used to determine whether to process or ignore file

@arenadata/java


Fix CI badge

The badge was broken...

I'd like to fix the coverage badge as well, but I don't know why the covarage report for master is not showing up on codecov.


Good work

Hey good work on this.
Tried to find any contact info would like to talk to you i have some questions.
Add me on discord : rocco#0252 If you want.

Hmm, ok.


qlen should be uint64_t type for ZMQ_HWM option

I found setopt for ZMQ_HWN failed in my error log, checking the api doc the value type should be uint64t.
http://api.zeromq.org/2-1:zmq-setsockopt

That is correct for 0MQ < 3.0 (which we haven't been using/testing for a while), but newer versions require an "int" for this parameter. The type should probably be a "zmq_hwm_t" defined in "ngx_http_log_zmq.h" together with the other compatibility definitions that are already there.

@carlosefr
I define the new type zmq_hwm_t :)


python3.pkgs.jinja2: don't build offline documentation by default

Description of changes
E.g. systemd fails like this:
    last 25 log lines:
    > Checking for function "blkid_probe_set_hint" with dependency blkid: YES
    > Run-time dependency libkmod found: YES 30
    > Run-time dependency xencontrol found: NO (tried pkgconfig and cmake)
    > Run-time dependency libmicrohttpd found: NO (tried pkgconfig and cmake)
    > Checking for function "crypt_activate_by_token_pin" : NO
    > Run-time dependency libiptc found: NO (tried pkgconfig and cmake)
    > Run-time dependency libqrencode found: NO (tried pkgconfig and cmake)
    > Run-time dependency gnutls found: NO (tried pkgconfig and cmake)
    > Run-time dependency openssl found: NO (tried pkgconfig, system and cmake)
    > Run-time dependency p11-kit-1 found: NO (tried pkgconfig and cmake)
    > Run-time dependency tss2-esys tss2-rc tss2-mu found: NO (tried pkgconfig and cmake)
    > Run-time dependency libdw found: NO (tried pkgconfig and cmake)
    > Run-time dependency zlib found: NO (tried pkgconfig, cmake and system)
    > Library bz2 found: NO
    > Run-time dependency liblzma found: NO (tried pkgconfig and cmake)
    > Run-time dependency libzstd found: NO (tried pkgconfig and cmake)
    > Run-time dependency xkbcommon found: NO (tried pkgconfig and cmake)
    > Run-time dependency libpcre2-8 found: NO (tried pkgconfig and cmake)
    > Run-time dependency dbus-1 found: NO (tried pkgconfig and cmake)
    > Message: default-dnssec cannot be set to yes or allow-downgrade openssl and gcrypt are disabled. Setting default-dnssec to no.
    > Program python3 (jinja2) found: NO
    >
    > meson.build:1949:15: ERROR: python3 is missing modules: jinja2

Upon trying more packages I realized that this is not the only one (it
appears to be related to python3.withPackages in some cases).
For now, flip the default to unbreak a lot of stuff and remove the
enableDocumentation = false; hacks from a bunch of other packages.
cc @KAction

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Im wondering if this causes breakage with other things needing jinja2.
Maybe enableDocumentation = true; for jinja2 shouldn't be the default?

Agreed with that last one, until we know for sure why having documentation caused breakage, it might be good to make the default false and enable for certain package where we know everything works.

Yeah, while trying out other packages I realized that even more is broken. Will change the PR accordingly.

@flokli @happysalada done! :)

Thanks again for taking care of the fix !

Sorry for inconvenience. I'll try to find better way to build jinja2 docs.

Content of jinja2.out with enableDocumentation is almost empty:
> tree ./result/
./result/
├── lib
│   └── python3.10
│       └── site-packages
└── nix-support
    └── propagated-build-inputs

4 directories, 1 file

That is embarrassing that I missed it, but at least narrows search area. Rebuilding jinja2 is pain, though.


fix: ensure that ContinuousArchiving is set as failed in case of errors

Closes #2624

/test limit=local

@mnencia we should back port to 1.18 too if you agree

/test depth=push test_level=4 feature_type=backup-restore,recovery,storage,replication


Remove dead code from miqSetButtons.

Purpose or Intent
Remove dead code from miqSetButtons.
Simplify miqSetButtons call by moving a test inside.
@himdel, @skateman: review?

Also noticed that https://github.com/martinpovolny/manageiq/blob/001e71c0b077839432e8a341c03b078e5e2e1311/app/assets/javascripts/miq_application.js#L1084-L1088 should probably be dead as well.. (center_buttons_div)

@himdel : fixed the bug. Other dead code can be removed in a separate PR.

@himdel : removed the dead code you pointed out. Please check and merge!

Works like a charm :) will merge when green..


Add linux/arm to build-base target platform.

Changes
gcr.io/distroless/static:nonroot does support this platform. We need
to build our base image for it too, otherwise the arm version of
pipeline is broken as it cannot run creds-init and git-init images.
Fixes #3647
Long term, we might need to specify by hand the platform we support when we release as we may run into this next time distroless supports a new platform.
Signed-off-by: Vincent Demeester<EMAIL_ADDRESS>/cc @afrittoli @bobcatfish @barthy1
/kind bug
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Build `git-init` and `creds-init` image for linux/arm too

/hold
 => ERROR [linux/arm/v7 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk u  3.2s
 => CANCELED [linux/arm64 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk  3.1s
------
 > [linux/arm/v7 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade:
#10 0.241 fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/armv7/APKINDEX.tar.gz
#10 0.697 fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/community/armv7/APKINDEX.tar.gz
#10 1.359 (1/13) Installing ca-certificates (20191127-r2)
#10 1.397 (2/13) Installing nghttp2-libs (1.40.0-r1)
#10 1.405 (3/13) Installing libcurl (7.67.0-r3)
#10 1.419 (4/13) Installing libgcc (9.3.0-r0)
#10 1.425 (5/13) Installing expat (2.2.9-r1)
#10 1.432 (6/13) Installing pcre2 (10.34-r1)
#10 1.448 (7/13) Installing git (2.24.3-r0)
#10 1.774 (8/13) Installing git-lfs (2.9.2-r1)
#10 2.870 Executing git-lfs-2.9.2-r1.post-install
#10 2.873 ERROR: git-lfs-2.9.2-r1.post-install: script exited with error 1
#10 2.873 (9/13) Installing openssh-keygen (8.1_p1-r0)
#10 2.886 (10/13) Installing ncurses-terminfo-base (6.1_p20200118-r4)
#10 2.898 (11/13) Installing ncurses-libs (6.1_p20200118-r4)
#10 2.912 (12/13) Installing libedit (20191211.3.1-r0)
#10 2.919 (13/13) Installing openssh-client (8.1_p1-r0)
#10 3.005 Executing busybox-1.31.1-r9.trigger
#10 3.007 ERROR: busybox-1.31.1-r9.trigger: script exited with error 1
#10 3.008 Executing ca-certificates-20191127-r2.trigger
#10 3.010 ERROR: ca-certificates-20191127-r2.trigger: script exited with error 1
#10 3.017 1 error; 30 MiB in 27 packages
------
Error: failed to solve: rpc error: code = Unknown desc = executor failed running [/dev/.buildkit_qemu_emulator /bin/sh -c apk add --update git git-lfs openssh-client     && apk update     && apk upgrade]: exit code: 1

/hold
 => ERROR [linux/arm/v7 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk u  3.2s
 => CANCELED [linux/arm64 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk  3.1s
------
 > [linux/arm/v7 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade:
#10 0.241 fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/main/armv7/APKINDEX.tar.gz
#10 0.697 fetch http://dl-cdn.alpinelinux.org/alpine/v3.11/community/armv7/APKINDEX.tar.gz
#10 1.359 (1/13) Installing ca-certificates (20191127-r2)
#10 1.397 (2/13) Installing nghttp2-libs (1.40.0-r1)
#10 1.405 (3/13) Installing libcurl (7.67.0-r3)
#10 1.419 (4/13) Installing libgcc (9.3.0-r0)
#10 1.425 (5/13) Installing expat (2.2.9-r1)
#10 1.432 (6/13) Installing pcre2 (10.34-r1)
#10 1.448 (7/13) Installing git (2.24.3-r0)
#10 1.774 (8/13) Installing git-lfs (2.9.2-r1)
#10 2.870 Executing git-lfs-2.9.2-r1.post-install
#10 2.873 ERROR: git-lfs-2.9.2-r1.post-install: script exited with error 1
#10 2.873 (9/13) Installing openssh-keygen (8.1_p1-r0)
#10 2.886 (10/13) Installing ncurses-terminfo-base (6.1_p20200118-r4)
#10 2.898 (11/13) Installing ncurses-libs (6.1_p20200118-r4)
#10 2.912 (12/13) Installing libedit (20191211.3.1-r0)
#10 2.919 (13/13) Installing openssh-client (8.1_p1-r0)
#10 3.005 Executing busybox-1.31.1-r9.trigger
#10 3.007 ERROR: busybox-1.31.1-r9.trigger: script exited with error 1
#10 3.008 Executing ca-certificates-20191127-r2.trigger
#10 3.010 ERROR: ca-certificates-20191127-r2.trigger: script exited with error 1
#10 3.017 1 error; 30 MiB in 27 packages
------
Error: failed to solve: rpc error: code = Unknown desc = executor failed running [/dev/.buildkit_qemu_emulator /bin/sh -c apk add --update git git-lfs openssh-client     && apk update     && apk upgrade]: exit code: 1

The other option is to remove linux/arm from the release published platform 🙃

The other option is to remove linux/arm from the release published platform 🙃

@vdemeester how did you get the error?
I have to say I've got strange results with my local attempts.
With existing setup (can be broken because of active usage and tests though) I've got the same result as you listed.
However on new clean amd64 vm the image build was successful for existing archs + arm:
# docker buildx build --platform linux/amd64,linux/s390x,linux/ppc64le,linux/arm64,linux/arm --no-cache .
WARN[0000] No output specified for docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
[+] Building 10.8s (17/17) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 146B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [linux/arm/v7 internal] load metadata for docker.io/library/alpine:3.11                                                                                2.7s
 => [linux/s390x internal] load metadata for docker.io/library/alpine:3.11                                                                                2.7s
 => [linux/amd64 internal] load metadata for docker.io/library/alpine:3.11                                                                                2.5s
 => [linux/ppc64le internal] load metadata for docker.io/library/alpine:3.11                                                                                2.6s
 => [linux/arm64 internal] load metadata for docker.io/library/alpine:3.11                                                                                2.6s
 => [linux/s390x 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.4s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:ae4c90d25da4580c1cd02a35a672d9113b17e063183b4148c463df4d33079192 2.58MB / 2.58MB                                                                                0.2s
 => => extracting sha256:ae4c90d25da4580c1cd02a35a672d9113b17e063183b4148c463df4d33079192                                                                                0.2s
 => [linux/arm/v7 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.3s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:71728559ce1f58d5e0ef30be5b1d7628ff967d4038f9202818dd3d8c76feb8ab 2.42MB / 2.42MB                                                                                0.2s
 => => extracting sha256:71728559ce1f58d5e0ef30be5b1d7628ff967d4038f9202818dd3d8c76feb8ab                                                                                0.1s
 => [linux/arm64 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.5s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:20d8a246443a66e74e17f2a0e81a51fe774876ca0c2676691c37ee1b0e4d3cd5 2.73MB / 2.73MB                                                                                0.3s
 => => extracting sha256:20d8a246443a66e74e17f2a0e81a51fe774876ca0c2676691c37ee1b0e4d3cd5                                                                                0.2s
 => [linux/amd64 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.7s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:0a6724ff3fcd51338afdfdc2b1d4ffd04569818e31efad957213d67c29b45101 2.81MB / 2.81MB                                                                                0.6s
 => => extracting sha256:0a6724ff3fcd51338afdfdc2b1d4ffd04569818e31efad957213d67c29b45101                                                                                0.1s
 => [linux/ppc64le 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.5s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:2c090b1a59445fb94c5fb14edf51af12a8f8bc2259535b08191f26ea84a7bb05 2.82MB / 2.82MB                                                                                0.3s
 => => extracting sha256:2c090b1a59445fb94c5fb14edf51af12a8f8bc2259535b08191f26ea84a7bb05                                                                                0.2s
 => [linux/arm/v7 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade                                                                                6.5s
 => [linux/s390x 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade                                                                                7.3s
 => [linux/arm64 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade                                                                                6.3s
 => [linux/ppc64le 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade                                                                                6.9s
 => [linux/amd64 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade

@vdemeester how did you get the error?
I have to say I've got strange results with my local attempts.
With existing setup (can be broken because of active usage and tests though) I've got the same result as you listed.
However on new clean amd64 vm the image build was successful for existing archs + arm:
# docker buildx build --platform linux/amd64,linux/s390x,linux/ppc64le,linux/arm64,linux/arm --no-cache .
WARN[0000] No output specified for docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
[+] Building 10.8s (17/17) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 146B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [linux/arm/v7 internal] load metadata for docker.io/library/alpine:3.11                                                                                2.7s
 => [linux/s390x internal] load metadata for docker.io/library/alpine:3.11                                                                                2.7s
 => [linux/amd64 internal] load metadata for docker.io/library/alpine:3.11                                                                                2.5s
 => [linux/ppc64le internal] load metadata for docker.io/library/alpine:3.11                                                                                2.6s
 => [linux/arm64 internal] load metadata for docker.io/library/alpine:3.11                                                                                2.6s
 => [linux/s390x 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.4s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:ae4c90d25da4580c1cd02a35a672d9113b17e063183b4148c463df4d33079192 2.58MB / 2.58MB                                                                                0.2s
 => => extracting sha256:ae4c90d25da4580c1cd02a35a672d9113b17e063183b4148c463df4d33079192                                                                                0.2s
 => [linux/arm/v7 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.3s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:71728559ce1f58d5e0ef30be5b1d7628ff967d4038f9202818dd3d8c76feb8ab 2.42MB / 2.42MB                                                                                0.2s
 => => extracting sha256:71728559ce1f58d5e0ef30be5b1d7628ff967d4038f9202818dd3d8c76feb8ab                                                                                0.1s
 => [linux/arm64 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.5s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:20d8a246443a66e74e17f2a0e81a51fe774876ca0c2676691c37ee1b0e4d3cd5 2.73MB / 2.73MB                                                                                0.3s
 => => extracting sha256:20d8a246443a66e74e17f2a0e81a51fe774876ca0c2676691c37ee1b0e4d3cd5                                                                                0.2s
 => [linux/amd64 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.7s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:0a6724ff3fcd51338afdfdc2b1d4ffd04569818e31efad957213d67c29b45101 2.81MB / 2.81MB                                                                                0.6s
 => => extracting sha256:0a6724ff3fcd51338afdfdc2b1d4ffd04569818e31efad957213d67c29b45101                                                                                0.1s
 => [linux/ppc64le 1/2] FROM docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.5s
 => => resolve docker.io/library/alpine:3.11@sha256:0bd0e9e03a022c3b0226667621da84fc9bf562a9056130424b5bfbd8bcb0397f                                                                                0.0s
 => => sha256:2c090b1a59445fb94c5fb14edf51af12a8f8bc2259535b08191f26ea84a7bb05 2.82MB / 2.82MB                                                                                0.3s
 => => extracting sha256:2c090b1a59445fb94c5fb14edf51af12a8f8bc2259535b08191f26ea84a7bb05                                                                                0.2s
 => [linux/arm/v7 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade                                                                                6.5s
 => [linux/s390x 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade                                                                                7.3s
 => [linux/arm64 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade                                                                                6.3s
 => [linux/ppc64le 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade                                                                                6.9s
 => [linux/amd64 2/2] RUN apk add --update git git-lfs openssh-client     && apk update     && apk upgrade

/test check-pr-has-kind-label

/test check-pr-has-kind-label

Closing in favor of #3717
/close

Closing in favor of #3717
/close


Fix incorrect textView frame.

When the height of text (content size) is less then the scrollView height the textView height should equal to the scrollView height otherwise the rest of the area will not response to the press event.

#12725

Looks like a fix is in master.


hyper::client::ResponseFuture to String or Bytes

Hello I've had some problems and I want to get a response to the text
let client = Client::new();
let req = Request::builder()
        .method("POST")
        .uri("http://<IP_ADDRESS>:9999/echo")
        .body(Body::from("Hallo!"))
        .expect("request builder");
let future = client.request(req);

How to convert future:hyper::client::ResponseFuture  to String or Bytes
Thank u.

You need to await the future to get a response, and from there, you can stream the body. The getting started guide may help some.
You'd be looking for code like:
let resp = client.request(req).await?;
let bytes = hyper::body::to_bytes(resp).await?;

Since this isn't a bug, I'm going to close this issue.


Plugin needs org.springframework.security.core.userdetails.User but org.springframework.security.core.userdetails.UserDetails would be sufficient

Hey,
I wanted to use your plugin to add shiro permission checking to my application that uses spring security. Unfortunately I don't retrieve the User information via the default spring security core GORM mechanisms, but via a custom AuthenticationProvider. This provider does not use the preimplemented User class from Spring but implements its own UserDetails class. On the spring security core side this works pretty well. But when adding your plugin I had a problem, as, in the SpringSecurityRealm, you cast the principal of the authentication to User, but UserDetails would be better as it is an interface implemented by User and seems to be sufficient for the stuff you do afterwards.
I changed the appropriate plugin code, but was not able to compile the plugin successfully as I currently have not enough knowledge of the grails plugin development (and not enough time to fix this) and how to use own plugins.
A workaround for my personal code is to extend the User class, but I hope that this won't be needed anymore in the long term.
I'll send you a pull request with the changes.
Greetings,
Lukas

PR applied, will be in 1.0-RC2


Body::Readable#each returns enumerator without a block

This PR adds a feature for Body::Readable#each. This method will return Enumerator if called without a block.
This is the "real" code I'd be using this feature with (I currently use each and manually increment index):
require "async"
require "async/http/internet"

Async do |task|
  internet = Async::HTTP::Internet.new

  response = internet.get(url)
  response.body.each.with_index(1) do |chunk, index|
    # Don't saturate the CPU
    Async::Task.current.yield if index.modulo(10).zero?

    cpu_heavy_operation(chunk)
  end
end

Types of Changes

[ ] Bug fix.
[x] New feature.
[ ] Performance improvement.

Testing

[x] I added new tests for my changes.
[x] I ran all the tests locally.

Please let me know if you think we need more tests for this.

Unfortunately I don't believe this will work correctly as enumerators have issues when used like this with blocking I/O, which will hopefully be resolved with Ruby 3.0.

Thanks for the quick response.
I'm running things on ruby 3.0.0preview1. I haven't had any issues running this code (monkey patched). I'll report any errors if they occur.
I understand async will need to support ruby 2.x for a long time, so I'm ok with closing this PR.

I'll revisit this because it makes sense at least to consider how we handle this.

Can you please rebase this on main?

Done!

This is now merged.


Hostname is not resolvable if created by template in swarm compose

Given the following working swarm compose yml results in not resolvable hostnames on the overlay network using the swarm DNS service discovery as usual.
version: "3"

services:

  app:
    hostname: "{{.Service.Name}}-{{.Task.Slot}}"
    depends_on:
      - redis
      - minio
    networks:
      - net
    image: registry:latest
    volumes:
      - /home/mario/reg/registry-conf/config.yml:/etc/docker/registry/config.yml
    deploy:
      restart_policy:
        condition: any
      mode: replicated
      replicas: 3
      update_config:
        delay: 2s

  redis:
    networks:
      - net
    image: redis
    command: redis-server --appendonly yes
    volumes:
      - /home/mario/reg/redis-data:/data
    deploy:
      restart_policy:
        condition: any
      mode: replicated
      replicas: 1
      update_config:
        delay: 2s

  minio:
    ports:
            - 9000:9000
    image: minio/minio
    command: server /export
    networks:
      - net
    volumes:
      - /home/mario/reg/minio-data:/export
      - /home/mario/reg/minio-conf:/root/.minio
    environment:
      - MINIO_ACCESS_KEY=B2E0E27AAAAAAAAJATWZ
      - MINIO_SECRET_KEY=6f1yeVsuf4c9aaaaaaaaxgf3QBar8hrsKHj2ryRE
    deploy:
      restart_policy:
        condition: any
      mode: replicated
      replicas: 1
      update_config:
        delay: 2s

networks:
  net:
    external:
      name: registry_net

Here is the evidence:

[09:26 mario@ ~/reg]$ docker stack deploy -c registry-swarm.yml registry
Creating service registry_app
Creating service registry_redis
Creating service registry_minio
[09:26 mario@ ~/reg]$ docker exec registry_app.1.pf1ia54eyankjqo0y0egs43wh hostname
9483c153494b
[09:27 mario@ ~/reg]$ docker exec registry_app.2.t7lmvfgfyz9mtoinesawvnsad hostname
1c3b1054d421
[09:27 mario@ ~/reg]$ docker exec registry_app.1.pf1ia54eyankjqo0y0egs43wh ping 1c3b1054d421
PING 1c3b1054d421 (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=64 time=0.157 ms
64 bytes from <IP_ADDRESS>: seq=1 ttl=64 time=0.137 ms
^C

changed the swarm compose to use hostname: "{{.Service.Name}}-{{.Task.Slot}}" for hostname:
hostname: "{{.Service.Name}}-{{.Task.Slot}}"

[09:27 mario@ ~/reg]$ docker stack deploy -c registry-swarm.yml registry
Updating service registry_app (id: js6hzq1zvtjzlgf01rnqc5u45)
Updating service registry_redis (id: luha9payd14qotjnk3r2eqbxv)
Updating service registry_minio (id: x15ubn9ctxjuo64j0qapfmyoh)
[09:27 mario@ ~/reg]$ docker exec registry_app.1.oc3eudiz86attr7kktjk0jjdl hostname
registry_app-1
[09:28 mario@ ~/reg]$ docker exec registry_app.2.w4mjpo46ikov2xkero552r6if hostname
registry_app-2
[09:28 mario@ ~/reg]$ docker exec registry_app.1.oc3eudiz86attr7kktjk0jjdl ping registry_app-2
ping: bad address 'registry_app-2'

Expected result:
The hostnames of the containers should be registered correctly in the swarm DNS service discovery during startup. It does also not work if I recreate the stack (rm, deploy)
Importance:
I guess that this is important because the correct behavior is needed for cluster services like Redis/Minio/etc which should be deployed through stack but which are depending to use stable DNS resolvable hostnames during the cluster configuration. IP-address are subject of change during redeployment's and these IP-addresses are not predictable beforehand - therefore ip-addresses are not usable in these scenarios (cluster configuration).
 No error, but no new alias. But I can ping the given one from any container.
    networks:
      net:
        aliases:
          - "{{.Service.Name}}-{{.Task.Slot}}"

            "Networks": {
                "registry_net": {
                    "IPAMConfig": {
                        "IPv4Address": "<IP_ADDRESS>"
                    },
                    "Links": null,
                    "Aliases": [
                        "c7d5b7a82724"
                    ],
                    "NetworkID": "uoufdo1bwnepruvuk594jmiun",
                    "EndpointID": "bfd860f6a532b5ee78d352edb280f4c049cf8464cd742122bdcf31e471376c40",
                    "Gateway": "",
                    "IPAddress": "<IP_ADDRESS>",
                    "IPPrefixLen": 24,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": "02:42:0a:00:01:05"
                }

[10:09 mario@ ~/reg]$ docker exec registry_app.2.6lhya7ftxoq6lna7c672gx5ta ping c7d5b7a82724
PING c7d5b7a82724 (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: seq=0 ttl=64 time=0.173 ms

Feature Request opened at moby/moby#34239

@kleinsasserm since this issue is being tracked and discussed elsewhere, can we close this one?

@nishanttotla As this issue is covered as closes due commit docker/libnetwork@61f3d913, this one would be closed automatically if the PR is merged. My PR there is quite simple (two 2 liner) but very useful and it would be nice if you could support (+1) the merge there to get this done. This would be very helpful.
I've opened this issue here, because at first I thought that this is a swarm issue. Sometimes later I researched, that the source of this behavior is technically in libnetwork. I guess that others would also try to search here then elsewhere. Another thing is, that the default search view on Github covers only issues with status open. Therefore it is sometimes hard to see if something is merged or solved or wip for inexperienced users if issues are closed.
But if you think so you can close this one :)

@kleinsasserm thank you for the detailed explanation and context. Since issues are searchable even when closed, let's close this one, and track any follow-up discussion in libnetwork.

Linking https://github.com/docker/swarmkit/issues/1242, which is where the global design for a DNS schema is being discussed


train ReID logs

Hi @NirAharon ，
I am training ReID model on MOT20, but the training results is abnormal. As shown in the figure below，loss_cls is instability and lr  remains the same after 2000 iters. Do you have the same problem when you train this model.

Hi @EnzoLiang,
It is likely because of the CosineAnnealingLR scheduler.
I don't recall any problem when I trained this network, but it was a long time ago. I will try to find the training log.
If you still have trouble, maybe you be able to find more information at the FastReID repo or try and change the LR scheduler.

Hi @NirAharon,
The results are  unchanged when I change the LR scheduler to MultiStepLR.  It is normal to train on Market1501 datasets using the same yaml config. Is it related to the generated MOT20 dataset?

Hi @EnzoLiang, It is likely because of the CosineAnnealingLR scheduler. I don't recall any problem when I trained this network, but it was a long time ago. I will try to find the training log. If you still have trouble, maybe you be able to find more information at the FastReID repo or try and change the LR scheduler.

@EnzoLiang Hi, have you solved the issue? What is the reason of that?


Public cloud UI mvp account coding redesign

new design for accounting code component applied for create page and product page

Is this PR still relevant being that there is another PR for account coding fixes?


[Sprint 11/PI - 154] Akushon Unit Test

Jira Link:
https://ichiro-its.atlassian.net/browse/PI-154
Description
create unit test for node initialization, interpolator, and action creation
Type of Change

[ ] Bugfix
[ ] Enhancement
[ ] New feature
[ ] Breaking change (fix or feature that would cause the existing functionality to not work as expected)

How Has This Been Tested?

[x] New unit tests added.
[ ] Manual tested.

Checklist:

[X] Using Branch Name Convention

feature/JIRA-ID-SHORT-DESCRIPTION if has a JIRA ticket
enhancement/SHORT-DESCRIPTION if has/has no JIRA ticket and contain enhancement
hotfix/SHORT-DESCRIPTION if the change doesn't need to be tested (urgent)

[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have made the documentation for the corresponding changes.

My guess was the interpolator test has its loop until the action used for testing finished. You can expect_near or assert_equal the result of nth loop with the difference value of current pose target position against initial position multiply by its speed and nth loop. Exactly, you have to calculate the current joint values on nth loop that you want to assert.
But I think this is okay, the code was manually tested. Good for your beginning on making this code.

Maybe mas @threeal, any suggestion or comment?

btw pls resolve the warnings @Alffaza


Template check

Changed template check to take environment into consideration (development -> HTTP, production -> $templateCache).

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
http://guh.guru:8080/job/guh-webinterface-pull-request/26/
Test PASSed.


Create Timeout Settings for Automated Logout Page

This is a follow-up to #7211
Can you add a new section to the Automated Logout Dashboard page that starts with a checkbox (disabled by default)
[ ] Automatically log out users who are inactive for [ ] seconds or more.
And then implement this? I would imagine this is probably just a public facing setter for the session cookie lifetime, right?

Users can modify the cookie lifetime on the client side, the only thing we want to make sure is that the session is invalidated server side too


Crash when using Realm in Swift playground

Hi,
I realise this is probably full of sharp edges, but I thought I'd try to use Realm in a playground (git HEAD, commit 2990f07576c1847ce38dde5ea735044daeb9ca63). I'm on Xcode 6.0.1 GM (6A317).
I followed the instructions for getting started with Swift, and Realm is visible to my Swift application.
I can also import it into my playground, and the code completion works :sunglasses:
This is the code in the playground:
import Realm
class Dog : RLMObject {
}
let d = Dog()

But the final let statement crashes, clicking the inspect button shows this call stack :scream:
* thread #1: tid = 0x4216c, 0x0000000109003e57 libswiftCore.dylib`swift_ClassMirror_count + 23, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x10)
  * frame #0: 0x0000000109003e57 libswiftCore.dylib`swift_ClassMirror_count + 23
    frame #1: 0x0000000107174269 PlaygroundLogger`PlaygroundLogger.PlaygroundObjectWriter.encodeStructured (PlaygroundLogger.PlaygroundObjectWriter)(Swift.MirrorType, Swift.UInt64, PlaygroundLogger.LoggerCappingPolicy) -> () + 121
    frame #2: 0x0000000107174ee0 PlaygroundLogger`PlaygroundLogger.PlaygroundObjectWriter.encodeStructured (PlaygroundLogger.PlaygroundObjectWriter)(Swift.MirrorType, Swift.UInt64) -> () + 656
    frame #3: 0x000000010717ad80 PlaygroundLogger`PlaygroundLogger.PlaygroundObjectWriter.encode (PlaygroundLogger.PlaygroundObjectWriter)(Swift.MirrorType, Swift.UInt64) -> () + 7728
    frame #4: 0x000000010717b4c0 PlaygroundLogger`PlaygroundLogger.PlaygroundObjectWriter.encodeObject (PlaygroundLogger.PlaygroundObjectWriter)<A>(A, Swift.String) -> () + 1296
    frame #5: 0x000000010714efde PlaygroundLogger`playground_log + 350
    frame #6: 0x0000000113013638 $__lldb_expr414`top_level_code + 168 at playground414.swift:8
    frame #7: 0x00000001130139dd $__lldb_expr414`main + 61 at <EXPR>:0
    frame #8: 0x00000001070aa510 HouseFinder`get_field_types__XCPAppDelegate + 160
    frame #9: 0x00000001070ab081 HouseFinder`reabstraction thunk helper from @callee_owned () -> (@unowned ()) to @callee_owned (@in ()) -> (@out ()) + 17
    frame #10: 0x00000001070a9cf1 HouseFinder`partial apply forwarder for reabstraction thunk helper from @callee_owned () -> (@unowned ()) to @callee_owned (@in ()) -> (@out ()) + 81
    frame #11: 0x00000001070ab0b0 HouseFinder`reabstraction thunk helper from @callee_owned (@in ()) -> (@out ()) to @callee_owned () -> (@unowned ()) + 32
    frame #12: 0x00000001070ab0e7 HouseFinder`reabstraction thunk helper from @callee_owned () -> (@unowned ()) to @callee_unowned @objc_block () -> (@unowned ()) + 39
    frame #13: 0x00000001076f2abc CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
    frame #14: 0x00000001076e8805 CoreFoundation`__CFRunLoopDoBlocks + 341
    frame #15: 0x00000001076e7fc3 CoreFoundation`__CFRunLoopRun + 851
    frame #16: 0x00000001076e7a06 CoreFoundation`CFRunLoopRunSpecific + 470
    frame #17: 0x00000001077942c1 CoreFoundation`CFRunLoopRun + 97
    frame #18: 0x00000001070a7dcd HouseFinder`top_level_code + 3629
    frame #19: 0x00000001070aa53a HouseFinder`main + 42
    frame #20: 0x000000010a3c5145 libdyld.dylib`start + 1

It is unclear whether it's a bug in Swift, the playground infrastructure, or something Realm does. Regardless, it would be pretty sweet to have playground support for rapid prototyping, so I just thought I'd put this up here.
Leon

For me Realm works in a playground, building 691ef1ebb14e4bf1ec7c867f22eb17180af112cb from source.  A few notes: My playground is an iOS Playground, and my schema is NOT defined directly in my playground as @bitserf tried, rather it is defined as a framework that I made, which I then import into the playground.
However, I have the caveat that I can only load a Realm database in read only mode.  If I set readOnly to false, I get the error:
*** Terminating app due to uncaught exception 'RLMException', reason: 'open() failed: Operation not permitted'
*** First throw call stack:
(
	0   CoreFoundation                      0x0000000102f0df35 __exceptionPreprocess + 165
	1   libobjc.A.dylib                     0x0000000104a2bbb7 objc_exception_throw + 45
	2   RealmDatabase                       0x000000010e989d28 _Z18RLMSetErrorOrThrowP7NSErrorPU15__autoreleasingS0_ + 264
	3   RealmDatabase                       0x000000010e96dc51 -[RLMRealm initWithPath:key:readOnly:inMemory:dynamic:error:] + 5201
	4   RealmDatabase                       0x000000010e96f80a +[RLMRealm realmWithPath:key:readOnly:inMemory:dynamic:schema:error:] + 2890
	5   RealmDatabase                       0x000000010e96e978 +[RLMRealm realmWithPath:readOnly:error:] + 152
	6   ???                                 0x000000010ef3740e 0x0 +<PHONE_NUMBER>
)
libc++abi.dylib: terminating with uncaught exception of type NSException

Note that RealmDatabase is my own framework that I build that I mentioned above.
I am loading the Realm file from the Playground's resource directory.  I'm not sure how much not being able to write to the Realm is an issue with Realm, or a restriction with Playgrounds.

Update: I changed reading from the Playground resources to:
let path : String = (NSSearchPathForDirectoriesInDomains(NSSearchPathDirectory.DocumentDirectory, NSSearchPathDomainMask.AllDomainsMask, true)[0] as String).stringByAppendingPathComponent("realm.realm")

and now I can open the Realm file in writable mode.

How did you guys to it to import, mine is failing on import Realm or import RealmSwift
Playground execution failed: <module-includes>:1:9: note: in file included from <module-includes>:1:
#import "/Users/kylefang/Library/Developer/Xcode/DerivedData/Pomotodo2-gqvmkihjmtjsntanzzshgbrsykbc/Build/Products/Debug-iphonesimulator/Realm.framework/Headers/Realm.h"
        ^
/Users/kylefang/Library/Developer/Xcode/DerivedData/Pomotodo2-gqvmkihjmtjsntanzzshgbrsykbc/Build/Products/Debug-iphonesimulator/Realm.framework/Headers/Realm.h:21:9: error: 'Realm/RLMArray.h' file not found
#import <Realm/RLMArray.h>
        ^
could not build Objective-C module 'Realm'<module-includes>:2:9: note: in file included from <module-includes>:2:
#import "Headers/RealmSwift-Swift.h"
        ^

I'm on Xcode7 right now...

I found I could CRUD Realm databases by building 17972cb0 from source, placing the project file into a workspace, adding a playground and creating the realm in the 'Shared Playground Data' folder.
However, I then placed the realm database file and the required classes into a framework, #importd the framework, set to readOnly: true but ran into this error:
Error Domain=io.realm Code=1 "Operation not permitted" UserInfo={NSLocalizedDescription=Operation not permitted, Error Code=1}

Realm works fabulously for me in a Playground both in-memory and on disc with the default configuration. I just crated a workspace with a playground and included RealmSwift 0.98.3 via Cocoapods by doing pod playgrounds import RealmSwift and it worked straight away.

@icanzilb this works for me too. I haven't analysed the conditions for success and still get scary looking warnings in the console, but REPL-oriented development is definitely possible with Realm !

@DanielAsher do you get any particular error reported? I have just this in the console, which looks like nothing serious:

2016-03-05 08:44:13.591 RealmSwift[40751:650775] Failed to obtain sandbox extension for path=/var/folders/64/vmn77sp112xdn5np6mjtwxfw0000gn/T/com.apple.dt.Xcode.pg/containers/com.apple.dt.playground.stub.iOS_Simulator.RealmSwift-18C8513C-641D-4EF0-AA8D-570FDCB2DEC4/Library/Caches/com.apple.dt.playground.stub.iOS_Simulator.RealmSwift-18C8513C-641D-4EF0-AA8D-570FDCB2DEC4. Errno:1

@icanzilb - yes, this is (scary but harmless) error message I get. Realm REPL remains awesome.

ok it looks like there are subtle differences between running in a playground and in an app.
This code works in an app but crashes in a Playground:
let wife = Person()
let husband = Person()
husband.spouse = wife
wife.spouse = husband

try! realm.write {
    realm.add(husband)
}

While this code works in both an app and a Playground:
let wife = Person()
let husband = Person()
husband.spouse = wife

try! realm.write {
    realm.add(husband)
}

try! realm.write {
    wife.spouse = husband
}

I'm sure this will give a good hint if anyone's to fix this

At present there might be more issues than I initially hope for - trying to delete any objects also ends with SIGABRT. That's a pitty having realm in a playground could've been a real game changer

Ok - got help and turns out both above issues were my own fault. So far I have zero issues running in a playground

As best we can tell, Realm Swift is very usable in Xcode Playgrounds, and we're adding an example in #3370. We just forgot to update this issue whenever this was resolved, likely many months ago :scream:.


[SECURESIGN-1479] Trillian TLS: add external DB TLS CA certificate

This looks good, thanks! Is there a way we could extend the user_provided molecule scenario to test for this?

There seems to be an error in the molecule default scenario execution, can you please take a look?
  TASK [Setting tas_single_node_trillian_trusted_ca] *****************************
  fatal: [<IP_ADDRESS>]: FAILED! => {"msg": "The 'file' lookup had an issue accessing the file '/etc/mysql/ssl/ca-cert.pem'. file not found, use -vvvvv to see paths searched"}


metal-cpp_macOS14.2_iOS17.2.zip

From the latest zipfile on https://developer.apple.com/metal/cpp/

Hi there! Thanks for reminder, I downloaded the latest and then forgot about it...
I'm not accepting your PR because I keep versions in different branches, and merge would just plop it into previous version branch.
https://github.com/bkaradzic/metal-cpp

Thanks!


BenchmarkResults "out_stream" field setup fails on Windows

https://github.com/hendriknielaender/zBench/blob/f88d20b21748881240d8b34078684bfe3f2cc5b7/zbench.zig#L251
On Windows 10 / Zig 0.11, the type of stdout writer cannot be determined at compile-time
C:\Users\user\scoop\apps\zig\current\lib\std\os\windows.zig:1892:28: error: unable to evaluate comptime expression
                break :blk asm volatile (
                           ^~~
C:\Users\user\scoop\apps\zig\current\lib\std\os\windows.zig:1907:15: note: called from here
    return teb().ProcessEnvironmentBlock;
           ~~~^~
C:\Users\user\scoop\apps\zig\current\lib\std\io.zig:36:30: note: called from here
        return os.windows.peb().ProcessParameters.hStdOutput;
               ~~~~~~~~~~~~~~^~
C:\Users\user\scoop\apps\zig\current\lib\std\io.zig:50:34: note: called from here
        .handle = getStdOutHandle(),
                  ~~~~~~~~~~~~~~~^~
zbench.zig:253:125: note: called from here
    out_stream: std.io.BufferedWriter(1024, @TypeOf(std.io.getStdOut().writer())) = .{ .unbuffered_writer = std.io.getStdOut().writer() },

related: #40


Fixes links to docs

Per @themoonrat's suggestion in #3298, makes the type valuable click-able. Also, adds a bunch of docs that were missing from CONST.
Preview:
http://pixijs.download/fix-settings-docs/docs/PIXI.html
http://pixijs.download/fix-settings-docs/docs/PIXI.settings.html

I hate those things :( making names in jsdocs, brrrr


react-native-git-upgrade doesn't work with local user config

I don't have a global git config for user.email because I use different emails for different repos. Instead I set it in each repo. Even though git config -l confirms my user.email is set in my local repo, react-native-git-upgrade refuses to run because it believes it isn't set.
In order to run react-native-git-upgrade, I have to set user.email in my global .gitconfig. So I think whatever check it is doing is probably incorrect. It shouldn't care whether its set globally, only locally.
This has been around since react-native-git-upgrade was launched on up to 0.42.rc-2

Would you be interested in sending a PR to fix this?

So I dug into this a bit further and react-native-git-upgrade does a simple git commit -m "snapshot". The issues with global vs local config have been reported by many people in regard to many other projects that use git, but in the end I'd say its a problem with git itself.


Verify shared library files integrity

Summary
Change the shared library initializer to validate the files in the existing shared directory or write new files instead of relying on a sentinel file and keep the file handles open with read-only shared access. This allows .NET Monitor to confidently share libraries that will be loaded into target applications and know that they have not been tampered with between runs of .NET Monitor. If any file is different than expected, shared library initialization will fail and any feature that is dependent on it will not work.
Example console output:
16:58:51 info: Microsoft.Diagnostics.Tools.Monitor.Startup[60]
      Tell us about your experience with dotnet monitor: https://aka.ms/dotnet-monitor-survey
16:58:51 info: Microsoft.Diagnostics.Tools.Monitor.Startup[77]
      Connection mode: Listen at '\\.\pipe\diagport'
16:58:51 warn: Microsoft.Diagnostics.Tools.Monitor.Startup[13]
      WARNING: Authentication has been disabled. This can pose a security risk and is not intended for production environments.
16:58:52 info: Microsoft.Hosting.Lifetime[14]
      Now listening on: https://localhost:49260
16:58:52 info: Microsoft.Hosting.Lifetime[14]
      Now listening on: http://localhost:49261
16:58:52 fail: Microsoft.Diagnostics.Tools.Monitor.LibrarySharing.SharedLibraryService[73]
      Failed to initialize shared library storage. Some monitoring features may be unavailable.
      System.InvalidOperationException: The shared file 'C:\Users\jander\dnmshared\libs\8.0.0-dev.23363.1\any\net6.0\Microsoft.Diagnostics.Monitoring.StartupHook.dll' is different from source file 'C:\src\dotnet\dotnet-monitor\artifacts\bin\dotnet-monitor\Debug\net6.0\shared\any\net6.0\Microsoft.Diagnostics.Monitoring.StartupHook.dll'.
         at Microsoft.Diagnostics.Tools.Monitor.LibrarySharing.DefaultSharedLibraryInitializer.Initialize() in C:\src\dotnet\dotnet-monitor\src\Tools\dotnet-monitor\LibrarySharing\DefaultSharedLibraryInitializer.cs:line 123
         at Microsoft.Diagnostics.Tools.Monitor.LibrarySharing.SharedLibraryService.ExecuteAsync(CancellationToken stoppingToken) in C:\src\dotnet\dotnet-monitor\src\Tools\dotnet-monitor\LibrarySharing\SharedLibraryService.cs:line 47
16:58:52 info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.

Release Notes Entry

/azp run dotnet-monitor-ci


Add Feeditem class to replace the item array

This PR adds a new class FeedItem to replace the current item array generated by the bridges. It is intended to perform sanity checks during bridge execution rather than attempting to format arbitrary contents (i.e. detecting invalid URIs and broken timestamps early).

See lib/FeedItem.php for implementation details (documented in the source code)
See tests/FeedItemTest.php for test cases (in case code breaks in the future)
See any bridge for recommended changes (not required, because index.php still handles legacy arrays)

Remarks:

index.php currently supports FeedItem and legacy items. Updating bridges is not a requirement, but it is part of this PR right now.
This PR updates all bridges to make use of the $item->parameter syntax (i.e. $item->title instead of $item['title']).
FeedItem supports two methods for accessing parameters:

$item->setParameter(...), for example $item->setTitle($title) and
$item->parameter = ..., for example $item->title = $title, at the cost of performance according to https://stackoverflow.com/a/3330859 (though I think it can be neglected because downloading and caching is the real bottleneck)

This PR might break some bridges which have send invalid data in the first place (for example because the item URI ($item['uri']) is relative instead of absolute (which it should be).

Let me know if there is any problem with this approach.
Are there any arguments against updating all bridges?

The only things I see are disadvantages:

any invalid title, timestamp etc will produce broken feed
cost of performance

at the cost of performance according to https://stackoverflow.com/a/3330859 (though I think it can be neglected because downloading and caching is the real bottleneck)

Thanks for the feedback!

any invalid title, timestamp etc will produce broken feed

Those bridges currently fail as well, but silently over long periods of time until a user realizes something is missing (i.e. missing titles, no timestamps, etc...). It should be possible to detect such cases early on, in order to keep bridges as functional as possible.
I do agree that forcefully breaking bridges is not a good solution, especially because it breaks user experience (which I hadn't considered tbh). Debug messages are a better approach to this, as they are disabled in production mode. I'll work on that.

cost of performance

That only applies to the $item->parameter syntax (which is simpler to use). As mentioned before, this is probably no issue for RSS-Bridge, because downloading contents takes much more performance. I haven't seen any differences in performance on my machine.
Anyway, I'll revert the last commit (changing all bridges) for now, this can be managed more efficiently in index.php using the more efficient setter functions. Performance isn't an issue then and we can still upgrade bridges later.

The only things I see are disadvantages

Here are a few advantages:

Predictability
Parameters are specified explicitly and not implicitly like before. This makes things more predictable and (hopefully) helps new developers in implementing their own bridges with better feedback on what had gone wrong (no more empty output). Invalid parameters are properly reported and no longer ignored (i.e. relative URIs, empty titles, etc...). Currently those invalid parameters are only noticed by looking at the output, which may degrade over time.

Simplicity
Formats can be simplified because they don't need to validate parameters (i.e. Enclosures and Categories are guaranteed to be arrays, Title will be text, etc...). Those problems are sometimes hard to detect and should not result in a broken formats, as they indicate degrading or broken bridges.

Standardization
Bridges don't need to check if parameters are set.
Code like if(!isset($item['enclosures'])) { $item['enclosures'] = array(); } is no longer necessary.

Extensibility
FeedItem could handle common operations (to be fair, these are not implemented yet). Those common operations will benefit all bridges, without the need to touch any of them. Here are a few examples:

If timestamp is a string, try strtotime
Do intelligent parsing if a parameter is an instance of simple_html_dom. For example, if URI is such an object, try $uri->href.
Remove script tags and forms from content
Strip tags from titles, but keep it readable (i.e. put spaces where necessary)
Take care of entity decoding (especially for content)

Forgot to mention: caching doesn't work yet.


onDidTerminateDebugSession maybe shouldn't fire when debug session doesn't start successfully

Testing #29490
If a call to createDebugSession fails, e.g. for passing invalid arguments, onDidTerminateDebugSession is still fired. It seems like maybe it shouldn't fire in that case. I don't know whether there are other events in the extension API that follow a similar pattern that we can follow.

This makes sense to me. @weinand ?

yep, that makes sense. So I suggest that "onDidTerminateDebugSession" is only fired if the corresponding "debugService.createProcess" returns a process. See https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/api/electron-browser/mainThreadDebugService.ts#L38


Version 0.81.0 build fails due to missing dependency io/fs in golang 1.15

What version of Hugo are you using (hugo version)?

0.81.0

Here is what happens if I try to build with go 1.15.8:

$ go install --tags extended
go: downloading github.com/gobwas/glob v0.2.3
. . .
tpl/internal/go_templates/texttemplate/helper.go:11:2: package io/fs is not in GOROOT (/usr/local/go/src/io/fs)

I think this is related to https://github.com/golang-migrate/migrate/issues/480
To reproduce:

clone https://github.com/Bronek/build-hugo - prerequisites are: make and (docker or podman), on Linux
bump version number near the top of Makefile
issue make build - this will download docker image golang:1.15.8-buster and then run the build inside the container

Hugo 0.81.0 need Go >= 1.16 to build. That is unfortunate, but not something that I can fix.

In that case, you need to update the Dockerfile:
0.81.0 has: FROM golang:1.15-alpine AS build


HDDS-9050. Added exploratory logging to gather further information.

What changes were proposed in this pull request?
Please see the JIRA description and comments for more information on the failure being addressed here.
We do not know the reason of the failure, and could not reproduce the issue after finding it a few times.
This change adds some logging around the place where we add extensions to certificates, as this is where we have seen the NPE. I believe knowing what is in the CSR, and what we have in the supported extensions map should be sufficient to further deduct things about the failure, and I do not see more places where we can add anything useful to further debug the problem, but I am open to any ideas.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9050
How was this patch tested?
No additional testing was done.

cc: @devmadhuu

@fapifta the patch looks good, but I think PR title should be updated to reflect the code change, not the problem that triggered this change

@adoroszlai I have changed the title, this way it should be sufficient.


Shortcuts with R functions

First of all, thanks for this VS Code extension. I came from Tinn-R, the big advantage from this is to define  shortcuts for R-code like nrow(selection) or length(selection). I know how to run Selection by "ctrl + Enter". But is it currently possible to define Shortcuts with 'R-Code' and automatically send it to the console ?
I think it´s possible to adapt or copy the function 'runSelection' from the extension.ts. Therefore two thinks have to be changed in my opinion. First of all runSelection needs a input variable (simple function name like 'nrow'). Secondly the rTerm.sendText(line) has to be change:
async function runSelection(RfunctionName) {
var first = true
for (const line of selection.selectedTextArray) {
 if (checkForComment(line)) { continue; }
 await delay(8); // Increase delay if RTerm can't handle speed.
 if (first) {rTerm.sendText(RfunctionName + '('}
 if (last) {')'}
 rTerm.sendText(line);
}
I`m not familiar with Typescript but i think this could be the way to define R-Shortcuts within this Extension.

Due to a missing reaction i adapt the 'extension.js' and 'package.json' to use R-Commands in Visual Studio Code. Now i would like to explain my solution for the example 'nrow'. First of all in the package.json the "commands" and "keybindings" has to be changed. Sencondly the function 'runSelection' and 'context.subscriptions' has to be changed:
package.json
commands:
{"title": "Show number of rows for selected object", "category": "R", "command": "r.nrow"}
keybindings:
{"command": "r.nrow", "key": "Ctrl+1","mac": "cmd+1","when": "editorTextFocus && editorLangId == 'r'"},
extension.js
runSelection
async function runSelection(rFunctionName) {
    const selection = selection_1.getSelection();
    if (!rTerminal_1.rTerm) {
        const success = rTerminal_1.createRTerm(true);
        if (!success) {
            return;
        }
        await util_1.delay(200); // Let RTerm warm up
    }
    if (selection.linesDownToMoveCursor > 0) {
        vscode_1.commands.executeCommand("cursorMove", { to: "down", value: selection.linesDownToMoveCursor });
        vscode_1.commands.executeCommand("cursorMove", { to: "wrappedLineEnd" });
    }

    for (let line of selection.selectedTextArray) {
        if (selection_1.checkForComment(line)) {
            continue;
        }
        await util_1.delay(8); // Increase delay if RTerm can't handle speed.

        if (rFunctionName) {
            let rFunctionCall = ""
            for (const feature of rFunctionName) {
                rFunctionCall += feature + "("
            }
            line = rFunctionCall + line.trim() + ")".repeat(rFunctionName.length);
        }
        rTerminal_1.rTerm.sendText(line);
    }
    setFocus();
}

context.subscriptions
context.subscriptions.push(vscode_1.commands.registerCommand("r.nrow", () => runSelection(["nrow"])))
If somebody is interersted in this solution feel free to use it. If you are interested i would send you the adapted files with some new keybindings like: nrow, length, head, transposed head, names. runSelection accepts empty input (standard runSelection like before), single input or an array of R-functions like transposed head = t(head(selected)). Every line give separated output. If two variables in two lines are selected, the function give for every line the nrow or something else.
This adaption now allows us to use VS Code like Tinn-R with shortcuts.

@MaTo04 Thank you for your suggestion, It's a great job!
If you will submit pull request I'll merge this (I'll put your name on changelog).
But if you would not, I want to just copy your code.
Which do you want to do?

Thanks, i will submit pull request today.

Fixed by #101, thank you @MaTo04


Move @fs/configurations webpack config into cra.

@redbugz I think this is ready.

@joeycozza what do you think?


Cover corner case for fresh install without CRD

Cover the concern case for fresh installation when CommonService CRD does not exist.
When it is a fresh installation, RETRY_CONFIG_CSCR will never set to 1. And configure_cs_kind function will not raise error if RETRY_CONFIG_CSCR is not 1.
We need to set RETRY_CONFIG_CSCR to 1 when configure_cs_kind is called AFTER installing cs-operator, it will abort the scripts when number of remaining retires is 0.

/lgtm


chore(main): release 0.3.8

:robot: I have created a release beep boop
0.3.8 (2024-04-02)
Bug Fixes

Revert "fix: Try to handle otel headers" (677042d)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/philipcristiano/et/releases/tag/v0.3.8 :sunflower:


PEAR-2077: Fix for Consequences table missing text in "Showing X - Y of Z"

Description

Refactored Pagination section of VerticalTable

Checklist

[ ] Added proper unit tests
[ ] Left proper TODO messages for any remaining tasks
[ ] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

Screenshots/Screen Recordings (if Appropriate)

Verified the consequences table has the item name at the bottom. 👍
While testing this, noticed some item names are ultra-pluralised: https://gdc-ctds.atlassian.net/browse/PEAR-2084

Verified the consequences table has the item name at the bottom. 👍
While testing this, noticed some item names are ultra-pluralised: https://gdc-ctds.atlassian.net/browse/PEAR-2084

I feel like it's much better to put a fix in this PR itself.
cc. @craigrbarnes

looks good 👍


ks diff outputs a wrong diff

/kind bug
What happened:
ks diff outputs a diff as if the remote doesn't contain any object.
What you expected to happen:
ks diff should show only the differences between local and remote
How to reproduce it (as minimally and precisely as possible):
Given a fresh minikube instance and the following component
{
  "apiVersion":"v1",
  "kind":"Service",
  "metadata":{"name":"kube-dns-aws","namespace":"kube-system"},
  "spec":{
    "ports":[{"name":"dns-tcp-aws","port":53,"protocol":"TCP"}],
    "selector":{"k8s-app":"kube-dns"}
  }
}

trying to apply and diff results in
$ ks show default
---
apiVersion: v1
kind: Service
metadata:
  name: kube-dns-aws
  namespace: kube-system
spec:
  ports:
  - name: dns-tcp-aws
    port: 53
    protocol: TCP
  selector:
    k8s-app: kube-dns

$ ks apply default
INFO Updating services kube-system.kube-dns-aws

$ ks diff default
@@ -1 +1,17 @@
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: kube-dns-aws
+  namespace: kube-system
+spec:
+  ports:
+  - name: dns-tcp-aws
+    port: 53
+    protocol: TCP
+  selector:
+    k8s-app: kube-dns

$ kubectl --context minikube -n kube-system get service kube-dns-aws -o yaml
apiVersion: v1
kind: Service
metadata:
  annotations:
    ksonnet.io/managed: '{"pristine":"H4sIAAAAAAAA/3zOMWvDMBAF4L0/483yUEqhaG1/gKFJlpDhIt0gbEuHTnYIRv89KASTLFnv8b17K0jCgbOGFGGxfMJgCNHD4p/zEhzDYOJCngrBrog0MSyG+cydj9rRRWHuVxVyW6RXLTyhGqiwa1BSLgp73CqaLk4eDS2G/f4ykJxKcmmExe63RzUvYvZvxf6vRz0ZKI/sSsrt8/CjHYk8rUat9eMGAAD//wEAAP//+bSNpPsAAAA="}'
  creationTimestamp: 2018-06-01T12:26:02Z
  labels:
    app.kubernetes.io/deploy-manager: ksonnet
  name: kube-dns-aws
  namespace: kube-system
  resourceVersion: "463"
  selfLink: /api/v1/namespaces/kube-system/services/kube-dns-aws
  uid: f298ed9a-6596-11e8-b028-080027638f74
spec:
  clusterIP: <IP_ADDRESS>
  ports:
  - name: dns-tcp-aws
    port: 53
    protocol: TCP
    targetPort: 53
  selector:
    k8s-app: kube-dns
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

Environment:
$ ks version
ksonnet version: 0.11.0
jsonnet version: v0.10.0
client-go version:

Duplicate of #814


Feature request: standalone python connectivity example

It would be good to see a standalone python example for connecting to Message Hub.

For an example, see here http://stackoverflow.com/a/40325181/1033422

Hi @snowch,
Thanks for the suggestion. We will likely add a Python sample in the future. In the meantime, we can confirm several clients work out of the box. We've successfully  tested:

https://github.com/confluentinc/confluent-kafka-python
https://github.com/dpkp/kafka-python

We've now added a Python sample: https://github.com/ibm-messaging/message-hub-samples/tree/master/kafka-python-console-sample
Closing this issue


IE has multiple severe errors in the console log file

When I view a particular epub in IE, I see a number of errors that I don't see when I view the same document in Chrome and Firefox.  I have protractor tests that, at the end of each test, check the console.log to see if any severe errors were output.  If severe errors occurred, then the test is failed.
So, these severe errors are preventing my protractor tests from passing in IE.

These messages occur very often.  It seems to me that these are not really errors; as far as I can tell, the application continues to work correctly.  If these are not really errors, please lower the severity.

!iframe.baseURI => http://localhost:17105/library/testlibrary/EPubRead/doofvr9
algorithm incorrect: downshiftedEntry.orderingByLastUseTimestampIdx: 6, i: 6 -- /ops/images/pub.jpg

I get this when moving back and forth between two chapters in a particular epub.  I have not traced through the code to determine where it is occurring.  It might be something in my implementation, rather than in Readium; so no need to take action until I get further info for you.

[object Error]{description: "Access is d...", message: "Access is d...", name: "Error", number: -2147024891, stack: "Error: Acce..."}

I get this often as well; but I think that this is my implementation, rather than a readium issue.  Again, no need to take action until I get further info.

MEDIA12899: AUDIO/VIDEO: Unknown MIME type.

UPDATE: #3 is an issue caused by the inclusion of a file in the epub, where the mimetype of the file is not one that is recognized by readium.

@kimtuck THanks for reporting this.  Do you see 1 and 2 on all books or just some specific ones?

#1 -- first message occurs a lot; there is a console.error line that outputs this.  I don't consider this an error; and the console.error statement could be removed.
#1 -- second message occurs often; and I have no idea what it means or why it occurs.
#2 I don't know yet.  I've been working on other things for a while and so I haven't had time to investigate further.
#3 is not a readium issue per se; the publisher included a file with a mimetype that is not recognized by the browser; and thus the browser issues this error.  The file in question is a css file; and is included by the xhtml file; but the manifest says it is of some other mimetype, not text/css.

I have observed #1 as well. However, just the iframe.baseURI part.
I can add that I observe (consequently, I presume) IE making requests for the referenced content of the document from the stated (incorrect in our case at least, our application is hosted from a different domain than the content) base URI, which 404, and then again from the desired base URI.

The iframes that host EPUB content documents (HTML files) are actually fed with BlobURIs in the cloud reader (rather than a regular URL), or via document.write() in the IE case. So the baseURI is important to resolve relative / linked resources. The reason why it's a console.error() log message, not a lower-priority console.warn() is to be debated (we need to figure-out / test what happens when the iframe baseURI is missing)
https://github.com/readium/readium-js/blob/develop/js/epub-fetch/iframe_zip_loader.js#L36
            if (!iframe.baseURI) {

                if (isIE && iframe.ownerDocument.defaultView.frameElement) {

                    //console.debug(iframe.ownerDocument.defaultView.location);
                    iframe.baseURI = iframe.ownerDocument.defaultView.frameElement.getAttribute("data-loadUri");

                    console.log("EPUB doc iframe src (BEFORE):");
                    console.log(src);
                    src = new URI(src).absoluteTo(iframe.baseURI).search('').hash('').toString();
                }
                else if (typeof location !== 'undefined') {
                    iframe.baseURI = location.href + "";
                }

                console.error("!iframe.baseURI => " + iframe.baseURI);
            }


Error link on youtube video on Campaign

Which area(s) of Podkrepi.bg are affected?
Campaigns
Describe the Bug

Not working YouTube link.
To Reproduce

Open https://podkrepi.bg/campaigns/scouts-jamboree-korea
Click on link "YouTube канала на Организация на българските скаути"
Open wrong Youtube

Expected Behavior
Fix or remove YouTube link.
Which browser are you using? (if relevant)
Vivaldi

Which area(s) of Podkrepi.bg are affected?
Campaigns
Describe the Bug
 Not working YouTube link.
To Reproduce

Open https://podkrepi.bg/campaigns/scouts-jamboree-korea
Click on link "YouTube канала на Организация на българските скаути"
Open wrong Youtube

Expected Behavior
Fix or remove YouTube link.
Which browser are you using? (if relevant)
Vivaldi

Fixed


Rename SCSS files to include .module before file extension

Issue Description
Tools like webpacker and create-react-app v2 enable CSS modules automatically for stylesheet files that include .module before the extension name. file.module.css, another-file.module.scss
This would allow terra components to be used more easily with these tools with less config needed to enable CSS modules.
Issue Type

[ ] New Feature
[x] Enhancement
[ ] Bug
[ ] Other

Expected Behavior
Files that end in .scss are renamed to end in .module.scss

This file rename will be non-passive, while consumers are not recommended to use this files directly and instead, interface with the components as the component API, some users may be interfacing with these files directly. Renaming them could break usage in this case but does not break out intended use case of using the files via the react components.
With that, I'd recommend we do this update only when we have another major version bump we need to do so we can group the MVBs on this.

Tech Design

Rename all SCSS files to *.module.scss
Keep scss mixins and variable files named as is, without .module.scss
Update imports in JSX files to import new *.module.scss files


Bug: secureheaders does not work with cache

PHP Version
8.1
CodeIgniter4 Version
4.2.1
CodeIgniter4 Installation Method
Manual (zip or tar.gz)
Which operating systems have you tested for this bug?
macOS, Linux
Which server did you use?
apache
Database
No response
What happened?
Http headers of "secureheaders" are not present when cache is active
Steps to Reproduce

Active "secureheaders" in "app/Filters.php"

Add "$this->cachePage(200);" in your Controller

Expected Output
The following lines should appear in the http header :
x-content-type-options: nosniff
x-download-options: noopen
x-frame-options: SAMEORIGIN
x-permitted-cross-domain-policies: none
Anything else?
No response

Thanks for the report.
4Team: The gatherOutput() method, in which the page caching function is called, is called before the filters (after) have been processed. Therefore, headers set in filters do not get into the cache.
The gatherOutput() method also calls the displayPerformanceMetrics() method on which the debug toolbar filter depends. This will not allow the gatherOutput() method to be called after the filters. Although it would be logical.
So the only way out is to extract the caching from the gatherOutput() method.
https://github.com/codeigniter4/CodeIgniter4/blob/62048964f20f6561cb1e05e6fa58978a114d1026/system/CodeIgniter.php#L476-L485

@iRedds Thanks for your analysis.
I sent a PR #6282

I'm not sure if this is safe to consider a "bug". After filters can do any number of things, including content not safe for caching. For example I have a number of libraries that use after filters to apply content changes specific to a logged-in user. I chose to go with after filters as opposed to View Decorators in part due to the caching differences.
If this change is needed to make advertised features work as expected then it needs to be handled as a breaking change with larger potential impact.

I understand your concern, but there is no documentation that shows after filtering not cached.
It seems difficult that we say the Secure Headers will be gone when you cache the page.
And if a dev changes contents in before filters or in a controllers for a logged-in user,
what's the difference between them and in after filters?
The feature that changes in after filters are not cached seems difficult to justify and is unpredictable.

Understood. Please be sure to highlight in the changelog and I will update my package docs as needed.
FWIW I almost never use page caching; I frequently have a nav bar with the user's name in it, and almost any page can have flashdata alerts displayed. It might be handy in the future to have an explicit way of caching pages before filters and view decorators, then run the cached content through those components before displaying.

Yes, the current Web Page Caching cannot be used for personalized pages.
It seems it is better to have Page Cache service and a dev can control when Response is cached.


Update Singularity guide for RStudio Server 1.4

Here's a go at updating the Singulatiy guide for RStudio 1.4.x. I've tried to throw in a few additional seemingly-good practices as well.

Pin rocker/rstudio tag, due to periodic breaking changes in RStudio releases.
By default, RStudio 1.4.x creates an SQLite database in /var/lib/rstudio-server.
The contents of the revocation-list file has been moved to this database.
Credit: fasrc/fas-on-demand-rstudio
Update docs to mention Remote Image Builder for extending rocker rstudio images (using Singularity definition files)
Set R_LIBS_USER to rocker-specific directory via environment variable (defined in rsession) instead of writing to ~/.Renviron to avoid mixing personal libraries from rocker images & any R environment on the host (e.g., loaded via environment module)
Securely create temporary directory for files/directories that will be bind-mounted in the container
Use singularity exec --cleanenv to prevent environment variables set on the host---and there can be quite a few st in an HPC cluster environment environment---from interferring with environment variables in the container. Prefix environment variables that should be passed through with SINGULARITYENV_

Thanks @nathanweeks , this looks excellent!  Really appreciate the contribution.

Looks like the website hasn't been rebuilt to reflect these changes (https://www.rocker-project.org/use/singularity/). Could that be done when convenient? Thanks!