sap adapter tech ref updates

@MandiOhlinger,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-sap/metadata-node-ids4.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/configure-the-soap-action-for-oracle-database.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/develop-your-oracle-database-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/glossary3.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/metadata-node-ids3.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/use-the-servicemodel-metadata-utility-with-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/develop-your-oracle-e-business-suite-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/TOC.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/basic-sap-data-types.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-a-port-using-the-wcf-custom-adapter-and-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-a-port-using-the-wcf-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-the-soap-action-for-the-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/create-the-sap-system-connection-uri.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/creating-an-rfc-destination-in-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/creating-an-rfc-in-an-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/develop-your-sap-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-exec-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-execquery-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-select-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/get-started-with-the-biztalk-adapter-for-mysap-business-suite.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/glossary7.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/grammar-examples-for-statements-supported-with-the-data-provider-for-sap.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/message-schemas-for-idoc-operations.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/messages-and-message-schemas-for-biztalk-adapter-for-mysap-business-suite.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/microsoft-biztalk-adapter-for-mysap-business-suite-documentation.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/microsoft-biztalk-adapter-for-sap-developer-reference.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/origTOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/performing-tasks-using-the-sap-gui-for-specific-sap-adapter-scenarios.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/receive-inbound-rfc-calls-from-sap-using-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/receive-inbound-rfc-calls-in-sap-using-the-wcf-service-model.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/sending-idocs-from-an-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/sending-rfc-calls-from-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/technical-reference-for-the-sap-adapter.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/translate-sap-query-parameters-into-execquery-command.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/troubleshoot-operational-issues-with-the-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/use-the-servicemodel-metadata-utility-with-the-sap-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/viewing-details-about-the-idocs-sent-and-received-in-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/viewing-transaction-ids-in-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/metadata-node-ids4.md

Line 39: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sap/[IDOC_CIMTYPE]).
Line 40: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sap/[IDOC_CIMTYPE]).

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

:warning: Validation status: warnings

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-sap/metadata-node-ids4.md
:warning:Warning
View
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/configure-the-soap-action-for-oracle-database.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/develop-your-oracle-database-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/glossary3.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/metadata-node-ids3.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/use-the-servicemodel-metadata-utility-with-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/develop-your-oracle-e-business-suite-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/TOC.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/basic-sap-data-types.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-a-port-using-the-wcf-custom-adapter-and-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-a-port-using-the-wcf-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-the-soap-action-for-the-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/create-the-sap-system-connection-uri.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/creating-an-rfc-destination-in-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/creating-an-rfc-in-an-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/develop-your-sap-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-exec-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-execquery-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-select-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/get-started-with-the-biztalk-adapter-for-mysap-business-suite.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/glossary7.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/grammar-examples-for-statements-supported-with-the-data-provider-for-sap.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/message-schemas-for-idoc-operations.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/messages-and-message-schemas-for-biztalk-adapter-for-mysap-business-suite.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/microsoft-biztalk-adapter-for-mysap-business-suite-documentation.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/microsoft-biztalk-adapter-for-sap-developer-reference.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/origTOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/performing-tasks-using-the-sap-gui-for-specific-sap-adapter-scenarios.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/receive-inbound-rfc-calls-from-sap-using-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/receive-inbound-rfc-calls-in-sap-using-the-wcf-service-model.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/sending-idocs-from-an-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/sending-rfc-calls-from-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/technical-reference-for-the-sap-adapter.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/translate-sap-query-parameters-into-execquery-command.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/troubleshoot-operational-issues-with-the-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/use-the-servicemodel-metadata-utility-with-the-sap-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/viewing-details-about-the-idocs-sent-and-received-in-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/viewing-transaction-ids-in-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/metadata-node-ids4.md

Line 39: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sap/[IDOC_CIMTYPE]).
Line 40: [Warning] Invalid file link:(~/adapters-and-accelerators/adapter-sap/[IDOC_CIMTYPE]).

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/configure-the-soap-action-for-oracle-database.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/develop-your-oracle-database-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/glossary3.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/metadata-node-ids3.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-database/use-the-servicemodel-metadata-utility-with-the-oracle-db-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-oracle-ebs/develop-your-oracle-e-business-suite-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/TOC.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/basic-sap-data-types.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-a-port-using-the-wcf-custom-adapter-and-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-a-port-using-the-wcf-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/configure-the-soap-action-for-the-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/create-the-sap-system-connection-uri.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/creating-an-rfc-destination-in-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/creating-an-rfc-in-an-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/develop-your-sap-applications.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-exec-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-execquery-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/examples-for-select-statement.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/get-started-with-the-biztalk-adapter-for-mysap-business-suite.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/glossary7.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/grammar-examples-for-statements-supported-with-the-data-provider-for-sap.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/message-schemas-for-idoc-operations.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/messages-and-message-schemas-for-biztalk-adapter-for-mysap-business-suite.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/metadata-node-ids4.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/microsoft-biztalk-adapter-for-mysap-business-suite-documentation.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/microsoft-biztalk-adapter-for-sap-developer-reference.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/origTOC.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/performing-tasks-using-the-sap-gui-for-specific-sap-adapter-scenarios.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/receive-inbound-rfc-calls-from-sap-using-biztalk-server.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/receive-inbound-rfc-calls-in-sap-using-the-wcf-service-model.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/sending-idocs-from-an-sap-system.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/sending-rfc-calls-from-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/technical-reference-for-the-sap-adapter.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/translate-sap-query-parameters-into-execquery-command.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/troubleshoot-operational-issues-with-the-sap-adapter.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/use-the-servicemodel-metadata-utility-with-the-sap-adapter-in-biztalk.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/viewing-details-about-the-idocs-sent-and-received-in-an-sap-system.md
:white_check_mark:Succeeded

biztalk/adapters-and-accelerators/adapter-sap/viewing-transaction-ids-in-an-sap-system.md
:white_check_mark:Succeeded

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


Gentoo GNU/Linux Portage: random permission denied issue

Your Windows build number:  10.0.18362.418

What you're doing and what's happening:

Get any Gentoo current stage4 tarball here: http://distfiles.gentoo.org/releases/amd64/autobuilds/. I used systemd one.
Unpack tar from tar.xz to c:\
cmd
wsl --import gentoo c:\gentoo stage4-amd64-systemd-yyyymmdd.tar
wsl -d gentoo

Add/replace to/in /etc/portage/make.conf:
COMMON_FLAGS="-march=native -O2 -pipe"
MAKEOPTS="-j2"
FEATURES="-ipc-sandbox -pid-sandbox -mount-sandbox -network-sandbox"

emerge-webrsync
emaint sync -a
emerge -ev @world

What's wrong / what should be happening instead:
Error occured:

>>> Emerging (1 of 272) virtual/libintl-0-r2::gentoo
 * Fetching files in the background.
 * To view fetch progress, run in another terminal:
 * tail -f /var/log/emerge-fetch.log
>>> Unpacking source...
>>> Source unpacked in /tmp/portage/virtual/libintl-0-r2/work
>>> Preparing source in /tmp/portage/virtual/libintl-0-r2/work ...
>>> Source prepared.
Traceback (most recent call last):
  File "/var/tmp/portage/._portage_reinstall_.6o2a_lwh/lib/portage/locks.py", line 181, in _lockfile_iteration
    myfd = os.open(lockfilename, os.O_CREAT|os.O_RDWR, 0o660)
  File "/var/tmp/portage/._portage_reinstall_.6o2a_lwh/lib/portage/__init__.py", line 246, in __call__
    rval = self._func(*wrapped_args, **wrapped_kwargs)
PermissionError: [Errno 13] Permission denied: b'/tmp/portage/virtual/libintl-0-r2/.ipc_lock'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/var/tmp/portage/._portage_reinstall_.6o2a_lwh/bin/ebuild-ipc.py", line 277, in <module>
    sys.exit(ebuild_ipc_main(sys.argv[1:]))
  File "/var/tmp/portage/._portage_reinstall_.6o2a_lwh/bin/ebuild-ipc.py", line 273, in ebuild_ipc_main
    return ebuild_ipc.communicate(args)
  File "/var/tmp/portage/._portage_reinstall_.6o2a_lwh/bin/ebuild-ipc.py", line 130, in communicate
    lock_obj = portage.locks.lockfile(self.ipc_lock_file, unlinkfile=True)
  File "/var/tmp/portage/._portage_reinstall_.6o2a_lwh/lib/portage/locks.py", line 113, in lockfile
    unlinkfile=unlinkfile, waiting_msg=waiting_msg, flags=flags)
  File "/var/tmp/portage/._portage_reinstall_.6o2a_lwh/lib/portage/locks.py", line 187, in _lockfile_iteration
    _raise_exc(e)
  File "/var/tmp/portage/._portage_reinstall_.6o2a_lwh/lib/portage/util/install_mask.py", line 157, in _raise_exc           raise wrapper
portage.exception.PermissionDenied: [Errno 13] Permission denied: b'/tmp/portage/virtual/libintl-0-r2/.ipc_lock'         * The ebuild phase 'prepare' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.

>>> Failed to emerge virtual/libintl-0-r2, Log file:

This error may occur for any package, but it always about PermissionError: [Errno 13] Permission denied: and  b'/tmp/portage/.../.ipc_lock'
It may occur for any single emerges, but it always occurs for me trying emerge -ev @world.
It also reported 2 years ago at reddit: https://www.reddit.com/r/bashonubuntuonwindows/comments/66mzgk/gentoo_userland_on_wsl/
Emerging some single packages works fine almost always.
I never hit such error on my Gentoo amd64 box for 10+ years.

Strace of the failing command, if applicable:  Sadly, I cann't reproduce this under strace. Looks like some race condition specific to WSL.

Also: I don't have any antivirus sofware except Windows Defender. c:\gentoo added to Defender exclusion list. I also tryed to disable real time protection without success.

10.0.18362.418
[...]
I used systemd one.
[...]
FEATURES="-ipc-sandbox -pid-sandbox -mount-sandbox -network-sandbox"

Scenario won't fly on WSL1 for a plethora of duplicate reasons. This could be filed under a different cover on WSL2 if someone was motivated to do so, however n.b. CLI repro steps. I almost did one but effort. Starts with something like (under powershell):
PS> cd $home
PS> curl.exe --output gentoo.tar.xz http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage4-amd64-minimal/stage4-amd64-minimal-20191030T214502Z.tar.xz
PS> curl --output xz.zip https://tukaani.org/xz/xz-5.2.4-windows.zip
PS> Expand-Archive xz.zip
PS> .\xz\bin_x86-64\xz.exe -d gentoo.tar.xz
PS> wsl.exe --import gentoo $home\gentoo $home\gentoo.tar
[... all the things]

Too swamped this afternoon to fill it out.


How to do a multipart form post?

It's not covered in the docs but is there any way I can send some kind of mapping of keys and values for a multipart form post body to httpotion without writing the whole post body out as a string?

Looks like ibrowse itself doesn't have this functionality, we'll have to implement it here...

So I've been thinking about this and I realized that it should be a separate library. We don't have any special support for JSON and other formats here – why should multipart/form-data be an exception?


Resolve or ignore issues in codacy coverage report

The ocean.py codacy coverage report PR check fails. Despite it being a non-required check, it's probably a good idea to either resolve or ignore the issues it identified.
Codacy Issues List: https://app.codacy.com/gh/oceanprotocol/ocean.py/issues

Ref codacy static analysis: I did some ignoring cleanup and asked Maria to integrate the issues with the non-assigned variables from test_config (as part of her branch to improve testing). Once that is done, can you let me know @mariacarmina? I'll re-check to see if any Codacy Static Analysis issues re-appear.
Ref codacy code coverage, there are two tickets about this in provider and aquarius (i.e "only allow merges if code coverage is ratcheting up". I'll reformulate this one to say the same thing, after we re-fix the Static Analysis part.

We no longer send coverage reports to Codacy. :) Issues are moved to CodeClimate.


build: update travis config file to install latest CocoaPods - travis…

… build was failing with error 'The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods installation'

Codecov Report

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

@@           Coverage Diff           @@
##           master      #68   +/-   ##
=======================================
  Coverage   90.97%   90.97%
=======================================
  Files          25       25
  Lines        1308     1308
=======================================
  Hits         1190     1190
  Misses        118      118

Continue to review full report at Codecov.

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


Convert between vector types on FPGA

Allow copying from one length vector to another length vector in FPGA codes in order to do memory buffering with gearboxing in device code.

@tbennun This actually seems to work on the device side, but on the CPU side I cannot instantiate a dace::vec<dace::vec<float, 4>, 4>, because it seems all the vector types are hardcoded.


fix component selectors + css prop usage

This PR reverts the change to remove foldedComponentIds and reintroduces some v4 behavior to not inject styles into the static component classes.
Without these changes components targeted via component selector that have been wrapped in any way (css prop, styled() hoc, etc.) will not be found for style application which is a regression from v4.
In order to reintroduce foldedComponentIds we need to go back to the previous behavior in v4 of not injecting styles into the component stable ssr className so that it remains available for placeholder / targeting usage only.

blah incomplete fix, need to test some more -_-

@kitten ok this is good to go, tested in my SSR setup with component selectors etc and it's working as expected

Going to rebase to clean up the tree

Available for test at 5.0.0-beta.6-ej2

@kitten tried it and looks good 👍

@kitten rebased and dropped the last commit. Doesn't materially affect bundle size and I'd rather be safe than sorry on hashing stuff

Hello,
I still encounter HASH confusions on beta8.
Components rendered only on the client side, after a click for example, have a hash collisions to other components on the page, rendered on SSR.

@Burdigalien please open a new issue with a reproduction, thanks!


Redirecting back to the modal, doesn't refresh data

This might be me, but when I redirect from a controller function back to the modal (because some piece of data has updated), it doesn't refresh.
For example:
    public function install(Request $request, $id)
    {
        ...
        $model->services[] = $service;
        $model->save()
        ...

        return redirect()->route('modals.service.show', $id)->with('success', 'Service installed');
    }

When I then check the modal after the redirect, it "should" have the new data and update the UI accordingly (like model.services.include('whatever')) but it doesn't do that. I do see the new value coming back in the props after the redirect, but the UI doesn't seem to pick this up.
Am I missing something obvious?
EDIT: It might be worth noting, that it seems this worked yesterday with 0.6. I will run a quick test with that.
EDIT 2: Yes, can confirm, it worked before! Forcing version: "@inertiaui/modal-vue": "0.5.4", solves the issue, seems the 0.6.* version changed behavior? Probably inside here is what caused it: https://github.com/inertiaui/modal/pull/33/commits/d3c00f641e4f196f24bf5d09f9b0e5d54782e0c1

Fixed in v0.6.2


404 for Linux download from button at https://hyper.is/ even though website/index.html is correct

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name:
Hyper.app version:
Link of a Gist with the contents of your .hyper.js:
Relevant information from devtools (CMD+ALT+I on Mac OS, CTRL+SHIFT+I elsewhere):
The issue is reproducible in vanilla Hyper.app:

Issue

None of the above is relevant to this issue because I haven't installed it yet. That's the issue. Your download link for Linux is still wrong on the actual website. It goes to https://github.com/zeit/hyper/releases/download/1.2.0/hyper-1.3.1-x86_64-linux.AppImage which is a 404 error. If I copy and paste the download location from line 605 of website/index.html that you updated 2 days ago, the download works perfectly. Nobody will do that though, of course. The purpose of the link is so that people knowing nothing about github can download the package from your static website.

Here's the currently working link until the website/index.html is amended:
https://github.com/zeit/hyper/releases/download/1.3.1/hyper-1.3.1-x86_64-linux.AppImage

This is currently broken.
The current link at hyper.is is https://github.com/zeit/hyper/releases/download/1.3.1/hyper-1.3.0-x86_64-linux.AppImage. but it should have been https://github.com/zeit/hyper/releases/download/1.3.1/hyper-1.3.1-x86_64-linux.AppImage (notice the mismatched version in the filename).

Fix here: https://github.com/zeit/hyper/pull/1690
Go to https://hyper-latest.now.sh to see

@albinekb the fix has been merged but the hyper website (https://hyper.is/#installation) still doesn't have the updated link for the AppImage

Aha thanks @erhathaway, @matheuss can you deploy? 🙏


ideal to always be very first middleware?

Thanks for a fantastically useful project!
Wouldn't it be ideal in almost all use cases for this to be the very first middleware, so that other middleware don't do useless computation? So then the recommendation would be:
config.middleware.insert(0, Rack::ReverseProxy)

What do you think about having a recommended way to insert the middleware via a helper method? Something like: Rack::ReverseProxy::Rails.configure ?
Also, what about pure Rack application? Would it be possible to have a similar functionality?

You mean make a method which somehow automagically takes care of the insertion?
I don't think there will be a way to do this reliably. Different parts of an app might be "fighting" for middelware ordering, so it needs to be done by the developer as explicitly and simply as possible.

backing up a bit: i'm wondering why the readme suggests insert_before(Rack::Lock/Rack::Runtime, and what you think of suggesting to the user that it always be the very first middleware in most cases?

see #12 and #27 for reasons why it should be the very first middleware. those problems would have been avoided if it wasn't being run through deflater.

I don't think there will be a way to do this reliably. Different parts of an app might be "fighting" for middelware ordering, so it needs to be done by the developer as explicitly and simply as possible.

Agree


View Git Info in File Explorer bottom bar

Description of the new feature / enhancement
This feature would add the git repository info to the bottom bar in Windows File Explorer. Please view the attached screenshot below for a visual example.

Scenario when this would be used?
As somebody working with Git, this would give the user instant feedback whether or not they are in a Git repository folder as well as which branch, outgoing/incoming commits, etc. The information displayed would be configurable.

Supporting information

### Tasks

/dup https://github.com/microsoft/devhome/issues/679


dealing with missing tortoize output

When tortoize crashed, Iris crashes as well. I am proposing these changes to deal better with a tortioize crash. Please check and test it.

Tested, runs OK.


fix eval of featureGraphic, add dev email+website

Finally got rid of that rarely working loop and now reliably obtaining featureGraphic (plus adding developerEmail and developerWebsite). As the loop was dropped, this also gives a nice performance boost :smile:
Ready to go, @BaseMax – just take a look if you wish and merge if you agree :smiley:

    while ( empty($proto) && $limit > 0 ) { // sometimes protobuf is missing, but present again on subsequent call

Are you sure we not need the while/loop anymore?

PS: Do you think with this merged, another release should be made? If so, what version would you suggest? I'd go with v1.2.0 if you agree. Last release was almost a year ago, and there were quite some fixes/improvements applied since.

v1.2.0 is fine.

Before going to release, README, Documentation and wiki need to be updated.

Are you sure we not need the while/loop anymore?

I'm running without that for about a week now, so: yes, pretty sure. You might have noticed those data are now taken from a different ds (DataSet). Either they were "shuffled around" (which I assume, as while featureGraphic worked in the past it entirely stopped working months ago) – or we were looking at the wrong spot all the time. So TL;DR: that loop just went to its max count for nothing since then.

Before going to release, README, Documentation and wiki need to be updated.

I already had updating the wiki with those two new fields on my todo for once this MR got merged. Will do that now; would you take care for the other spots (or at least point out what specifically should be added/changed/updated)?

Urgs. Looks like reviews are broken now, ds:7 only has empty values. (looking around) haha, they've moved to ds:8. Which confirms my above suspicion that Google moves things around there. Let me see if changing to ds:8 solves that issue. If so, expect another MR before the release.

OK, fixed – and the wiki page on AppDetails updated. Give me a ping when I shall tag and release, I'll then write up the release notes as well.

OK, maybe I was a little impatient – but I hope I got all the places that needed a little updating. Release is tagged and pushed now.

PS: Would you mind changing the merge strategy default to "rebase & merge" (instead of "merge commit") for a cleaner history, @BaseMax? That would avoid the extra merge commit. I can't do that myself as I cannot access the project's settings.


 A deck that's loaded from the db should always have colored_symbols even if it is None because of SELECT ... cache.colored_symbols ... in deck.load_decks.
The only other place we construct a Deck object is in decklist.vivify which isn't called when loading "decks containing card X".
I wonder how your db got out of whack. You could try repriming the deck cache with decksite.data.deck.reprime_cache(d) and see if it persists?

Closing this as a one-off/dev env issue but feel free to reopen if you see it again.


Server_hostname missing, iterative insertion of peers in MySQL

When the server_hostname is not present, each time the database refreshes a new row for each peer is inserted in the database.
This fix avoids this to prevent the database from growing without even noticing and the UI to get freeze from loading too much registries.
A simple fix in the SQL query.

Hi @walmon , Can you please submit a patch in gerrit ?  Please follow http://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html guide.
http://gerrit.hyperledger.org/


Docs need more detail on how to resolve uport DIDs

We're working on a php library to match this functionality and it would help a lot to have a bit more information about how to retrieve the full document for a given DID

The gist is that the document is not retrieved from somewhere, it is constructed based on information gathered from the registry smart contract.
More specifically, the document is built based on the result of the identityOwner(identity) method call, and from the list of events emitted by the registry contract concerning that identity.
Each event contains a previousChange field you can use to build the complete list of events for an identity.
Then, each event in that history can contain information needed to build the publicKey, authentication , or service arrays in the resulting DID Document.
Is there something specific in the documentation that is confusing?

@alexander-morris  If this is of any help, here is a working example of did-ethr used by uport

@mirceanis thanks for your support. Mainly what is confusing is that everything that is well documented is outdated, or at least there is not a global set of diagrams explaining the flow correctly for noobs, like myself.
For example, the basic functionality for building anything that is verifiable is the ability to check signatures. In order to check signatures, it is needed a public key. According to the specs, this is the flow to get the key:
(From https://github.com/uport-project/specs/blob/develop/pki/index.md)

From the documentation of this library and your comment, it seems this is no longer true, but rather the did doc is constructed from events queried to the registry.
Funny enough, the only noob solution working is from @vasa-develop , which I truly appreiciate. However, after getting the did doc STILL i'm not able to get a public key, getting this DDO:
Ethr DID Document
{
'@context': 'https://w3id.org/did/v1',
id: 'did:ethr:0xe4e73272b77cab09b65b651836cd8ec4ada08715',
publicKey: [
{
id: 'did:ethr:0xe4e73272b77cab09b65b651836cd8ec4ada08715#owner',
type: 'Secp256k1VerificationKey2018',
owner: 'did:ethr:0xe4e73272b77cab09b65b651836cd8ec4ada08715',
ethereumAddress: '0xe4e73272b77cab09b65b651836cd8ec4ada08715'
}
],
authentication: [
{
type: 'Secp256k1SignatureAuthentication2018',
publicKey: 'did:ethr:0xe4e73272b77cab09b65b651836cd8ec4ada08715#owner'
}
]
}
Maybe I'm wrong and there is no need of a "public key" as I understand it, so I checked online if it was possible to get a public key from an ethereum address. Apparently, it is possible via this method

only if there has been a transaction from that account.
Again, sorry if I'm mistaken but the documentation is confusing. We need a simple way of obtaining a public key, or otherwise, a clear example of how to do it. Ty

@Namenox getting a public key from an ethereum address should be impossible since the address is part of the hash of the public key.
What happens during verification is that the public key is recovered from the data+signature using a method usually called ecRecover and then an ethereumAddress is derived from that. If the address matches the ethereumAddress of one DID document then it is considered a match.
Note that for this to work directly, a "recovery byte" is needed as part of the signature (making the signature 65 bytes long instead of 64).
In case that byte is not present, one would have to check both possible values (either 0 or 1), and match the DID Document against 2 possible ethereumAddresses.
Also note that many libraries that provide an ecRecover method may expect the recovery byte values to be 27 & 28 instead of 0 & 1

@mirceanis thank you very much, this answer was great for understanding.
This may not be the right place to ask this, so please fell free to move it somewhere:
-How is uPort solution dealing with privacy? Are the users expected to create a new DID for every service they interact with? (Or will it be added as a feature in the future?) Please note that i'm not stating that this should be the way to go, but I think I read it somewhere on uPort's medium and I would like to make use of this oportunity to clarify things.

What's uPort business model?

In the existing solution (the uPort mobile app), a single root-DID is used for receiving and sharing verifiable credentials (off-chain).
The off-chain verifiable credential data is only available to the user's device and to the parties the user decides to share with (during a selective disclosure).
It's technically possible to use different DIDs for off-chain interactions but because of the relatively small privacy attack surface it is not enabled in the app.
That being said, for ETH transactions the situation is different since on-chain interactions are public. The app also has support for eth signatures (interaction with dapps). App-specific addresses are used in this situation to protect privacy and to avoid accidental linking of off-chain credentials with the immutable on-chain activity.
For more details and/or extra questions, please refer to our support channel: https://uport.zendesk.com


You cannot define an index on fields with native type @db.VarChar(Max) of SQL Server

Bug description
model User {
  id @default(autoincrement())
  notes @db.VarChar(Max)

 @@index([Notes], map:"nci_wi_User_099fasfa")

}

How to reproduce
Just paste the below schema in the prisma.schema
Expected behavior
No response
Prisma information
model Ula {
  id Int  @id( ) @default(autoincrement())
  Notes String @db.VarChar(Max)
  Name String @db.VarChar(255)

 @@index([Notes,Name], map:"nci_wi_Ula_009AFCDDFASDFAF")

}

Environment & setup

OS: Windows
Database: MS SQL Server
Node.js version: 14.17.3

Prisma Version
4.0.0

Oh wow, I was not even aware that @db.VarChar(Max) is a thing. We support nice things 😆
I can confirm the validation error:
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "sqlserver"
  url      = env("DATABASE_URL")
}

model Ula {
  id    Int    @id() @default(autoincrement())
  Notes String @db.VarChar(Max)
  Name  String @db.VarChar(255)

  @@index([Notes, Name], map: "nci_wi_Ula_009AFCDDFASDFAF")
}

PS C:\Users\Jan\Documents\throwaway\foo> npx prisma validate
Environment variables loaded from .env
Prisma schema loaded from prisma\schema.prisma
Error: Get DMMF: Schema parsing - Error while interacting with query-engine-node-api library
Error code: P1012
error: You cannot define an index on fields with native type `VarChar(Max)` of SQL Server.
  -->  schema.prisma:15
   |
14 |
15 |   @@index([Notes, Name], map: "nci_wi_Ula_009AFCDDFASDFAF")
   |

Validation Error Count: 1

Prisma CLI Version : 4.0.0

I guess on SQL Server side there is no reason why this column should not be able to be used in an index?

@janpio also I get this error for @db.NVarChar(Max)

@jkomyno hey guys any update on this ?

The reported scenario is confirmed to happen as described.
It is unclear if you should be able to create an index on a field of @db.VarChar(Max) though, as it seems that this is an explicit validation we added.

And indeed:
https://www.linkedin.com/pulse/sql-server-nvarchar-max-index-compliant-workaround-guillaume-diamant/
https://learn.microsoft.com/en-us/sql/t-sql/statements/create-index-transact-sql?view=sql-server-ver15#column

Columns that are of the large object (LOB) data types ntext, text, varchar(max), nvarchar(max), varbinary(max), xml, or image can't be specified as key columns for an index.

So this is unfortunately a limitation of SQL Server that Prisma has correctly implemented. Sorry.


uploads: Ask user about deleting uploaded files when removed from edited message

Complete the unfinished work from https://github.com/zulip/zulip/pull/25764 in May 2023. When a user edits a message, attachments can be removed or changed. When the user hits 'save', if any attachments are removed, a modal will pop up asking the user to delete them.

merge #25764, resolve conflict, fix bugs.
add test cases.

Fixes: https://github.com/zulip/zulip/issues/25525

Screenshots and screen captures:

Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

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

Completed manual review and testing of the following:

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

I have fixed the commit comments, and the PR is ready for review. Thanks!

The "Manage uploaded files" link feels out of place to me. Let's try moving it below the list of files, and see if that helps.

@alya I have removed the 'edit history' link and added an error state screenshot and screenshots with 'manage uploaded files' at the bottom. (see updated PR). Let me know which option you like more. Thanks.

Thanks! I reopened the PR and posted a question on CZO for broader feedback.

Is there a reason you've been closing your PRs?

Is there a reason you've been closing and reopening your PRs?
@alya This PR frequently gets merge conflict because it changes a volatile file changelog.md. It will create an additional commit if I opt to "resolve" the merge conflict.  The side effect is that Github automatically closes PR when I reset my branch to main. Therefore, I have to reopen it.
I'm still learning Git, and I apologize for the multiple close/open actions, which can be confusing for a reviewer. I will research Git to handle situations like this better. Thank you.

Yeah, that sounds like a more complicated workflow than you need. In any case, you can always use rebase -i to squash any extra commits.

https://zulip.readthedocs.io/en/latest/git/index.html might help, or asking in #git-help on CZO.

@alya I have made the code changes and uploaded the latest screenshots. It's ready for review.

Thanks, the screenshots look good to me! @timabbott do you wan to take a look next?

Hey @alya, this PR could be marked as close as it has been completed in #31161.

Thanks for that ping @Joelute. And @wandrew0, thanks for working on this issue!


Cannot get styling to work inside markdown editor

I'm pretty sure this is my mistake but I don't know what I'm doing.  I'm trying to style various markdown editor elements so that color coding makes more sense while editing.
I've tried all the following in userchrome.css to make H1 light blue, but nothing works.  Any suggestions?
.CodeMirror.CodeMirror span.cm-header-1 {
    color: #0095ff!important;
}
.cm-header-1, .cm-header-2, .cm-header-3, .cm-header-4, .cm-header-5, .cm-header-6 {
    line-height: 1.5em;
    color: #0095ff!important;
}

span.cm-header.cm-header-1 {
    color: #0095ff!important;
}

Your first example works for me
.CodeMirror.CodeMirror span.cm-header-1 {
    color: #0095ff!important;
}

Are you restarting Joplin after making changes to userchrome.css? That's the most common cause of styles not applying. Make sure to use File->Quit, you might have the close to tray icon enabled which means pressing the X button doesn't actually close Joplin.

Yes I am.  For some reason, I can add a CSS definition in the browser and it works.  But if I copy/paste into the file, then restart, it doesn't work.  This is not true of every single style, just a few of them.  I'm still doing more testing.  I found that disabling the MacOS theme/plugin, the blank startup failure issue I've been having with the new version of Joplin seems to have gone away.


Encrypted Search shouldn't show up

encryptcontent:
title_prefix: ''
password_file: 'pwd.yml'
password_button: true
password_button_text: continue
hljs: False
arithmatex: False
mermaid2: False
search_index: 'dynamically'

see here:
The default is 'encrypted', which means all encrypted pages are removed from the search index. So just remove search_index or set it to the default.

But shouldn't the encrypted pages not show up in the search if you're not logged in, and decrypt when logged in so you can search them? It sounds hard to do so basically all encrypted pages are not searchable?

On-the-fly search decryption in 'dynamically' mode works out of the box with the mkdocs theme and some others.
The material theme does include its own search plugin which cannot easily be controlled/modified by this plugin. There are some hacks which require to modify the source code of mkdocs-material and recompiling.

I was thinking of making the search only kick in after 3 characters, which filters out the encryption pretty good. Just a simple fix.

Next time, please be more specific when describing the issue.
Yes, it is bad that the encrypted texts are showing up as search topics. We could modify the normal search plugin (as we are already replacing it) to not show encrypted entries. But as stated, our influence on the materials search plugin is limited. You'd have to check the documentation if there is a way to require a minimum amount of characters before results are listed.
But maybe we should keep search entries of encrypted pages in a separate file (besides search/search_index.json) and mix the entries in only after decryption... Let's keep this issue open as a reminder or to discuss this idea.


[Training] incorporate new materials - misc videos and ancillary files for TBD video

sub-task of https://github.com/NASA-PDS/PDS.nasa.gov-UX/issues/80

New materials:

The videos for File Area, Display Settings, and Array 2D image are now public. Here are the links to each video on YouTube:

File Area:  https://youtu.be/TF1ubd8_fiA
Display Settings:  https://youtu.be/WZDr1QL3OnU
Array 2D:  https://youtu.be/DhIKfBvgzsA

We are working on a video for a label example walkthrough for Collection Inventory label files. I’m thinking the link for this should go directly under Collection Product Label Structure. It has several files related to it that need to be included (attached to this email):

Collection_document_1.9.csv
Collection_document_1.9.xml
Collection_document_1.9_empty.xml
Mission.insight_2.0.xml

The walkthrough is in two parts because of the length. I will send you the Youtube links to the videos once they are approved and made public.

To Do:

[x] update links within page
[x] update links within documents
[x] edit document for Collection Product Label Structure with link to video and ancillary files
[x] update Filling Out the File Area document (sent in another email)
[x] use links instead of radio buttons
[x] use chevron instead of +/- for expansion
[x] add section for author attributions

@c-suh as a note, when creating sub-tasks for an Epic, there should be a Epics selection capability along the right sidebar, where you can actually select the Epic this should be associated with.

@jordanpadams ah, ok, I see it! The Epic option is available through ZenHub, but not through GitHub. I'll keep this in mind; thank you!

@c-suh you should also be able to see this if you in Github, as long as you have the zenhub extension installed

Changes have been approved for this iteration.


Bump ini from 1.3.5 to 1.3.7

Bumps ini from 1.3.5 to 1.3.7.

Release notes
Commits

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

Closed in favor of #10


standard compliance (arguable)

[http://www.w3.org/TR/cors/#access-control-allow-origin-response-header] sais:

In practice the origin-list-or-null production is more constrained. Rather than allowing a space-separated list of origins, it is either a single origin or the string "null".

Your code sais:

| Origins OriginSet
-- ^ Allow cross-origin requests from these origins.

I am not sure how to interpret the w3c document, but my bet is that it wants you to use a single origin here, not 0 or more.  What is yours?  (-:
Thanks for writing this!

I'm afraid I'm only providing basic maintenance for this library now, and I honestly can't comment on the intention. However, it at least seems to be doing the right thing! If anyone has any troubles with this and can investigate further, I will accept PRs that clear up the situation.


libicui18n.so: Firefox tends to break when quarterly packages are updated in base system

After updating the system in Q1/2022, a Firefox app bundle built in Q4/2021 will no longer run because we now have libicui18n.so.70.1 rather than libicui18n.so.69 in the base system.
Apparently libicui18n.so changes its version number in the filename all the time, even within the same FreeBSD release, in incompatible ways.
XPCOMGlueLoad error for file /usr/home/user/Applications/Firefox 93.0.app/Resources/usr/local/lib/firefox/libxul.so:
Shared object "libicui18n.so.69" not found, required by "libxul.so"
Couldn't load XPCOM.

What is the right thing to do?

FreeBSD% patchelf --print-needed "/usr/home/user/Applications/Firefox 93.0.app/Resources/usr/local/lib/firefox/libxul.so" | grep libicui
libicui18n.so.69

FreeBSD% patchelf --remove-needed "libicui18n.so.69" "/usr/home/user/Applications/Firefox 93.0.app/Resources/usr/local/lib/firefox/libxul.so"

FreeBSD% patchelf --add-needed "libicui18n.so" "/usr/home/user/Applications/Firefox 93.0.app/Resources/usr/local/lib/firefox/libxul.so"

FreeBSD% patchelf --print-needed "/usr/home/user/Applications/Firefox 93.0.app/Resources/usr/local/lib/firefox/libxul.so" | grep libicuuc
libicuuc.so.69

FreeBSD% patchelf --remove-needed "libicuuc.so.69" "/usr/home/user/Applications/Firefox 93.0.app/Resources/usr/local/lib/firefox/libxul.so"

FreeBSD% patchelf --add-needed "libicuuc.so" "/usr/home/user/Applications/Firefox 93.0.app/Resources/usr/local/lib/firefox/libxul.so"

Works...


Rename MatrixStatsAggregation.php to MaxAggregation.php

Cherry pick of #313 for Elasticsearch 6 and Symfony 5

@84m Would you please cut a new release 6.2.x release?

Codecov Report

Merging #339 into 6.2 will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                6.2     #339   +/-   ##
=========================================
  Coverage     78.53%   78.53%
  Complexity      713      713
=========================================
  Files           123      123
  Lines          1887     1887
=========================================
  Hits           1482     1482
  Misses          405      405

Impacted Files
Coverage Δ
Complexity Δ

src/Aggregation/Matrix/MaxAggregation.php
0.00% <ø> (ø)
10.00 <0.00> (?)

Continue to review full report at Codecov.

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


ARROW-9695: [Rust] Improve comments on LogicalPlan enum variants

While reviewing the DataFusion code more (thanks again for this great piece of work) I have some small suggestions on improving the documentation that I would have personally appreciated while reading the code. I wanted to contribute them back

LGTM also. Thanks a lot!


Lens on Windows 10 unable to use kubectl from WSL system

Describe the bug
When Lens is installed on a Win 10 and kubectl is installed in the WSL ubuntu linux subsystem, with configuration pointing the binary folder to where kubectl resides seems to not work.
In my example, the WSL kubectl had the oidc-login plugin installed and configured, the kubectl oidc-login get-token works when executed manually, but the Lens UI shows error:
error: unknown command "oidc-login" for "kubectl"

E0802 18:32:37.205765 10604 proxy_server.go:147] Error while proxying request: getting credentials: exec: executable kubectl failed with exit code 1

To Reproduce
Steps to reproduce the behavior:

Install Lens on Win 10
Setup kubectl with oidc-login on WSL linux subsystem, confirm it works there
Configure Lens to use WSL paths (see screenshots below)
Try to connect to any cluster requiring oidc-login

Expected behavior
Lens should use the actual kubectl binary path from the configuration
Screenshots

Confirmation that oidc-login works in WSL ubuntu:

Preferences/Kube:

Preferences/Terminal:

The error in Lens:

Environment (please complete the following information):

Lens Version: 2023.5.310801-latest
OS: Windows 10
OS2: Ubuntu 22.04 @ WSL2
Installation method: executable

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:

complete application log from startup, to error, to shutdown
info: [LENS-EXTENSIONS]: LOADING ...
info: [LENS-EXTENSIONS]: LOADED from C:\Users\radon\AppData\Roaming\Lens\lens-extensions.json
info: Starting v2023.5.310801-latest of Lens...
debug: Set kubectl version 1.23.3 for cluster version 1.23.3 using version map
info: 🔌 Starting LensProxy
info: [LENS-PROXY]: Proxy server has started at <IP_ADDRESS>:55493
info: 🔎 Testing LensProxy connection ...
info: [LENS-USER-STORE]: LOADING ...
debug: [USER-PREFERENCES]: fromStore() {"preferences":{"downloadBinariesPath":"\\\\wsl.localhost\\Ubuntu-22.04\\usr\\local\\bin","downloadKubectlBinaries":false,"editorConfiguration":{"fontFamily":"RobotoMono","fontSize":12,"lineNumbers":"on","minimap":{"enabled":true,"side":"right"},"tabSize":2},"kubectlBinariesPath":"\\\\wsl.localhost\\Ubuntu-22.04\\usr\\local\\bin","shell":"wsl.exe","syncKubeconfigEntries":[{"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube"}],"terminalConfig":{"fontFamily":"RobotoMono","fontSize":12},"updateChannel":"latest"}}
info: [LENS-USER-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\lens-user-store.json
info: [LENS-CLUSTER-STORE]: LOADING ...
info: [LENS-CLUSTER-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\lens-cluster-store.json
info: ⚡ LensProxy connection OK
info: 📟 Setting protocol client for lens://
info: 📟 Protocol client register succeeded ✅
debug: [APP-MAIN] initializing ipc main handlers
info: [CREATE-ELECTRON-WINDOW]: Loading content for window "splash" from file: C:\Users\radon\AppData\Local\Programs\Lens\resources\app.asar\static\splash.html...
info: [LENS-FILESYSTEM-PROVISIONER-STORE]: LOADING ...
info: [LENS-FILESYSTEM-PROVISIONER-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\lens-filesystem-provisioner-store.json
info: 🐚 Syncing shell environment
info: [LENS-WEBLINK-STORE]: LOADING ...
info: [LENS-WEBLINK-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\lens-weblink-store.json
debug: [SHELL-SYNC]: nothing to do, env not special in shells
info: [LENS-HOTBAR-STORE]: LOADING ...
info: [LENS-HOTBAR-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\lens-hotbar-store.json
info: 🧩 Initializing extensions
info: [EXTENSIONS-LOADER]: auto initializing extensions
info: [CLOUD-PROVIDER-SYNC-EXTENSION] activated
info: [LENS-DESKTOP-KUBE] onActivate
info: [LDK-STORE]: LOADING ...
info: [LDK-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\lens-desktop-kube-lens-extension\ldk-store.json
info: [SECURITY-PREFERENCES-STORE]: LOADING ...
info: [SECURITY-PREFERENCES-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\oci-image-lens-extension\security-preferences-store.json
debug: [IPC-RENDERER]: adding extension handler {"channel":"logs:export","extension":{"name":"@lensapp/support-lens-extension","version":"0.12.0"}}
info: [SUPPORT-EXTENSION] activated
info: [PREFERENCES-STORE]: LOADING ...
info: [PREFERENCES-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\survey-lens-extension\preferences-store.json
info: [TOUR-EXTENSION] activated
info: [TIP-STORE]: LOADING ...
info: [TIP-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\tour-lens-extension\tip-store.json
debug: [IPC-RENDERER]: adding extension handler {"channel":"clustersecurity:settings:open","extension":{"name":"@lensapp/tour-lens-extension","version":"1.7.1"}}
debug: [CLOUD-PROVIDER-SYNC-EXTENSION] has cloud provider clis:
info: [PREFERENCES-STORE]: LOADING ...
info: [PREFERENCES-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\telemetry-lens-extension\preferences-store.json
info: [LOCAL-METADATA-STORE]: LOADING ...
info: [LOCAL-METADATA-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\lenscloud-lens-extension\local-metadata-store.json
info: [RELEASE-NOTES-STORE]: LOADING ...
info: [RELEASE-NOTES-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\lenscloud-lens-extension\release-notes-store.json
info: [END-OF-TRIAL-STORE]: LOADING ...
info: [END-OF-TRIAL-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\lenscloud-lens-extension\end-of-trial-store.json
info: [GRACE-PERIOD-STORE]: LOADING ...
info: [GRACE-PERIOD-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\lenscloud-lens-extension\grace-period-store.json
info: [SPACES-SETTINGS-STORE]: LOADING ...
info: [SPACES-SETTINGS-STORE]: LOADED from C:\Users\radon\AppData\Roaming\Lens\extension-store\lenscloud-lens-extension\spaces-settings-store.json
info: [LENS-SPACES-EXTENSION]: 02/08/2023, 18:44:41 Broadcasted spaces change to SpacesListener on renderer
warn: [LENS-SPACES-EXTENSION]: 02/08/2023, 18:44:41 No spaces in SpaceSyncer disposeSpacesReaction, not changing selected space.
debug: [IPC-RENDERER]: adding extension listener {"channel":"disconnectClusterEvent","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension listener {"channel":"deleteOneSpace","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"forceRefreshToken","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"disconnectProxiedClustersEvent","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"resetSpaceSyncerEvent","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"stopTokenRefresherEvent","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"getSpaceSyncerSpaces","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension listener {"channel":"loadRemoteSpacesClusters","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension listener {"channel":"createOneSpace","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension listener {"channel":"leaveOneSpace","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: adding extension listener {"channel":"selectSpace","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
info: [LENS-SPACES-EXTENSION]: 02/08/2023, 18:44:41 Lens Spaces Extension activated
debug: [IPC-RENDERER]: adding extension handler {"channel":"vulnerabilities:db:import","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vulnerabilities:settings:open","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"clustersecurity:settings:open","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vulnerabilities:db:export","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"csv:export","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vulnerabilities:db:info","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vulnerabilities:clear","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vulnerabilities:scan:image","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vulnerabilities:scan:storage","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vulnerabilities:scan:enabled","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"image:manifest","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"image:tag","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"image:manifest-list","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"image:history","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"image:vulnerabilities","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
info: [LENS-SECURITY] activated
info: [CREATE-ELECTRON-WINDOW]: Window "splash" loaded
warn: [LENS-SPACES-EXTENSION]: (from:onRefreshTokenError) 02/08/2023, 18:44:41 InvalidGrantError error, reset Lens state and set connected=false... Offline user session not found {"stack":"Error: Offline user session not found\n    at t.refreshTokens (C:\\Users\\radon\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\@lensapp\\lenscloud-lens-extension\\dist\\main.js:2:31016)\n    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)\n    at async AuthTokenStore.refresh (C:\\Users\\radon\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\@lensapp\\lenscloud-lens-extension\\dist\\main.js:2:45593)"}
info: [LENS-SPACES-EXTENSION]: (from:resetSpaceSyncer) Clearing spaces/k8sClusters...
error: [LENS-SPACES-EXTENSION]: 02/08/2023, 18:44:41 Error: Offline user session not found
warn: [LENS-SPACES-EXTENSION]: 02/08/2023, 18:44:41 Couldn't refresh tokens, starting token refresher later.
info: [LENS-SPACES-EXTENSION]: 02/08/2023, 18:44:41 isLensCloudStatusOk on initialization returns true
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:enabled","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:start","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:stop","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:reset","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:delete","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:installDockerContext","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:uninstallDockerContext","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:download:pause","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:download:resume","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:download:cancel","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:create","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:update","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:profiles:get","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:getDockerInstallStatus","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"k0s:versions:get","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"extension:enable","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:cluster:active","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:cluster:isLdkClusterPath","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:cluster:getId","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: adding extension handler {"channel":"vm:os:compatibility","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
warn: [LENS-DESKTOP-KUBE] not a valid lens subscription, stopping ...
info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION]: enabled<EMAIL_ADDRESS>info: [EXTENSION-DISCOVERY] loading extensions from C:\Users\radon\AppData\Roaming\Lens
debug: [EXTENSION-DISCOVERY]: 0 extensions loaded {"extensions":[],"folderPath":"C:\\Users\\radon\\.k8slens\\extensions"}
info: [EXTENSION-DISCOVERY] watching extension add/remove in C:\Users\radon\.k8slens\extensions
info: [CREATE-ELECTRON-WINDOW]: Loading content for window "first-application-window" from url: https://lens.app:55493...
info: [CLI] inspecting registry
info: [KUBECONFIG-SYNC]: starting requested syncs
info: [KUBECONFIG-SYNC]: starting sync of file/folder {"filePath":"C:\\Users\\radon\\AppData\\Roaming\\Lens\\kubeconfigs"}
debug: [KUBECONFIG-SYNC]: 1 files/folders watched {"files":["C:\\Users\\radon\\AppData\\Roaming\\Lens\\kubeconfigs"]}
info: [KUBECONFIG-SYNC]: starting sync of file/folder {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube"}
debug: [KUBECONFIG-SYNC]: 2 files/folders watched {"files":["C:\\Users\\radon\\AppData\\Roaming\\Lens\\kubeconfigs","\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube"]}
debug: [KUBECONFIG-SYNC]: file changed {"filePath":"C:\\Users\\radon\\AppData\\Roaming\\Lens\\kubeconfigs\\c4007f91-3198-497b-873f-99c62ef067fc"}
error: [KUBECONFIG-SYNC]: watching file/folder failed: Error: EISDIR: illegal operation on a directory, watch '//wsl.localhost/Ubuntu-22.04/home/radon/.kube' {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube"}
error: [KUBECONFIG-SYNC]: watching file/folder failed: Error: EISDIR: illegal operation on a directory, watch '\\wsl.localhost\Ubuntu-22.04\home\radon\.kube\kubectx' {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube"}
debug: [KUBECONFIG-SYNC]: file changed {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\kubectx"}
error: [KUBECONFIG-SYNC]: watching file/folder failed: Error: EISDIR: illegal operation on a directory, watch '\\wsl.localhost\Ubuntu-22.04\home\radon\.kube\config' {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube"}
debug: [KUBECONFIG-SYNC]: file changed {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\config"}
debug: [KUBECONFIG-SYNC]: File now has 0 entries {"filePath":"C:\\Users\\radon\\AppData\\Roaming\\Lens\\kubeconfigs\\c4007f91-3198-497b-873f-99c62ef067fc"}
debug: [KUBECONFIG-SYNC]: Finished computing diff {"filePath":"C:\\Users\\radon\\AppData\\Roaming\\Lens\\kubeconfigs\\c4007f91-3198-497b-873f-99c62ef067fc"}
warn: [KUBECONFIG-SYNC]: encountered errors while loading config: "value" must be of type object {"details":[{"context":{"label":"value","type":"object","value":"prod-staff@prod-app.myapp"},"message":"\"value\" must be of type object","path":[],"type":"object.base"}],"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\kubectx"}
debug: [KUBECONFIG-SYNC]: File now has 0 entries {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\kubectx"}
debug: [KUBECONFIG-SYNC]: Finished computing diff {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\kubectx"}
debug: [KUBECONFIG-SYNC]: File now has 2 entries {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\config"}
debug: [KUBECONFIG-SYNC]: Added new cluster from sync {"contextName":"dev-staff@dev-app.myapp","filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\config"}
debug: [KUBECONFIG-SYNC]: Added new cluster from sync {"contextName":"prod-staff@prod-app.myapp","filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\config"}
debug: [KUBECONFIG-SYNC]: Finished computing diff {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube\\config"}
info: [CREATE-ELECTRON-WINDOW]: Window "first-application-window" loaded
info: [CLUSTER]: activate {"accessible":false,"disconnected":true,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}
info: [CLUSTER]: bind events {"accessible":false,"disconnected":true,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}
info: Starting connection ... {"meta":{"accessible":false,"disconnected":true,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}}
info: [CLUSTER]: reconnect {"accessible":false,"disconnected":true,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}
info: Authentication proxy started {"meta":{"accessible":false,"disconnected":true,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}}
info: [KUBE-AUTH-PROXY]: found port=55572
debug: [CLUSTER-MANAGER]: updating catalog from cluster store
info: Refreshing connection status ... {"meta":{"accessible":false,"disconnected":false,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}}
error: error: unknown command "oidc-login" for "kubectl"
 {"meta":{"accessible":false,"disconnected":false,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}}
error: E0802 18:44:50.162301   41548 proxy_server.go:147] Error while proxying request: getting credentials: exec: executable kubectl failed with exit code 1
 {"meta":{"accessible":false,"disconnected":false,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}}
error: [CLUSTER]: Failed to connect to<EMAIL_ADDRESS>Error: Failed to get /version for clusterId=3eec37498ca23e245b77ddf126cbf918: Internal Server Error
error: Failed to get /version for clusterId=3eec37498ca23e245b77ddf126cbf918: Internal Server Error {"meta":{"accessible":false,"disconnected":false,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}}
debug: [CLUSTER]: already disconnected {"id":"acedf1886811f2a3b20bc8d1e61e5e99"}
debug: [CLUSTER]: already disconnected {"id":"ba08b0439431ff5324bf28fc3f140804"}
info: [CLUSTER]: disconnecting {"id":"3eec37498ca23e245b77ddf126cbf918"}
debug: [KUBE-AUTH]: stopping local proxy {"accessible":false,"disconnected":false,"id":"3eec37498ca23e245b77ddf126cbf918","name":"dev-staff@dev-app.myapp","online":false,"ready":false}
info: [CLUSTER]: disconnected {"id":"3eec37498ca23e245b77ddf126cbf918"}
debug: [CLUSTER-MANAGER]: updating catalog from cluster store
debug: [CLUSTER]: already disconnected {"id":"942312d567440821efc149205de29b45"}
info: [LENS-PROXY]: Closing server
info: Quitting application ...
info: [SHELL-SESSIONS]: Killing all remaining shell sessions
info: [KUBECONFIG-SYNC]: stopping requested syncs
info: [KUBECONFIG-SYNC]: stopping sync of file/folder {"filePath":"C:\\Users\\radon\\AppData\\Roaming\\Lens\\kubeconfigs"}
debug: [KUBECONFIG-SYNC]: 1 files/folders watched {"files":["\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube"]}
info: [KUBECONFIG-SYNC]: stopping sync of file/folder {"filePath":"\\\\wsl.localhost\\Ubuntu-22.04\\home\\radon\\.kube"}
debug: [KUBECONFIG-SYNC]: 0 files/folders watched {"files":[]}
info: [EXTENSION-DISCOVERY] stopping the watch for extensions
info: [EXTENSION]: disabled<EMAIL_ADDRESS>info: [LENS-DESKTOP-KUBE] deactivated
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:enabled","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:start","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:stop","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:reset","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:delete","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:installDockerContext","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:uninstallDockerContext","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:download:pause","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:download:resume","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:download:cancel","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:create","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:update","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:profiles:get","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:getDockerInstallStatus","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"k0s:versions:get","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"extension:enable","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:cluster:active","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:cluster:isLdkClusterPath","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:cluster:getId","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vm:os:compatibility","extension":{"name":"@lensapp/lens-desktop-kube-lens-extension","version":"0.28.1"}}
info: [EXTENSION]: disabled<EMAIL_ADDRESS>info: [EXTENSION]: disabled<EMAIL_ADDRESS>info: [LENS-SPACES-EXTENSION]: 02/08/2023, 18:44:58 Lens Spaces Extension deactivated
debug: [IPC-RENDERER]: removing extension listener {"channel":"disconnectClusterEvent","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension listener {"channel":"deleteOneSpace","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"forceRefreshToken","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"disconnectProxiedClustersEvent","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"resetSpaceSyncerEvent","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"stopTokenRefresherEvent","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"getSpaceSyncerSpaces","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension listener {"channel":"loadRemoteSpacesClusters","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension listener {"channel":"createOneSpace","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension listener {"channel":"leaveOneSpace","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
debug: [IPC-RENDERER]: removing extension listener {"channel":"selectSpace","extension":{"name":"@lensapp/lenscloud-lens-extension","version":"1.32.2"}}
info: [EXTENSION]: disabled<EMAIL_ADDRESS>info: [LENS-SECURITY] deactivated
debug: [IPC-RENDERER]: removing extension handler {"channel":"vulnerabilities:db:import","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vulnerabilities:settings:open","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"clustersecurity:settings:open","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vulnerabilities:db:export","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"csv:export","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vulnerabilities:db:info","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vulnerabilities:clear","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vulnerabilities:scan:image","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vulnerabilities:scan:storage","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"vulnerabilities:scan:enabled","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"image:manifest","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"image:tag","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"image:manifest-list","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"image:history","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
debug: [IPC-RENDERER]: removing extension handler {"channel":"image:vulnerabilities","extension":{"name":"@lensapp/oci-image-lens-extension","version":"0.29.2"}}
info: [EXTENSION]: disabled<EMAIL_ADDRESS>debug: [IPC-RENDERER]: removing extension handler {"channel":"logs:export","extension":{"name":"@lensapp/support-lens-extension","version":"0.12.0"}}
info: [EXTENSION]: disabled<EMAIL_ADDRESS>info: [EXTENSION]: disabled<EMAIL_ADDRESS>info: [EXTENSION]: disabled<EMAIL_ADDRESS>debug: [IPC-RENDERER]: removing extension handler {"channel":"clustersecurity:settings:open","extension":{"name":"@lensapp/tour-lens-extension","version":"1.7.1"}}
info: [EXTENSION]: disabled<EMAIL_ADDRESS>

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.
apiVersion: v1
clusters:
- cluster:
    certificate-authority-data: ****SECRET****
    server: https://****SECRET****
  name: dev-app.myapp
- cluster:
    certificate-authority-data: ****SECRET****
    server: ****SECRET****
  name: prod-app.myapp
contexts:
- context:
    cluster: dev-app.myapp
    user: dev-staff
  name<EMAIL_ADDRESS>- context:
    cluster: prod-app.myapp
    user: prod-staff
  name<EMAIL_ADDRESS>current-context<EMAIL_ADDRESS>kind: Config
preferences: {}
users:
- name: dev-staff
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - oidc-login
      - get-token
      - --oidc-issuer-url=****SECRET****
      - --oidc-client-id=****SECRET****
      - --oidc-client-secret=****SECRET****
      command: kubectl
      env: null
      interactiveMode: IfAvailable
      provideClusterInfo: false
- name: prod-staff
  user:
    exec:
      apiVersion: client.authentication.k8s.io/v1beta1
      args:
      - oidc-login
      - get-token
      - --oidc-issuer-url=****SECRET****
      - --oidc-client-id=****SECRET****
      - --oidc-client-secret=****SECRET****
      command: kubectl
      env: null
      interactiveMode: IfAvailable
      provideClusterInfo: false

Additional context
Add any other context about the problem here.

I'd also like to be able to use the native windows Lens installation to access clusters requiring a binary executed within WSL and residing on the WSL filesystem.
Although I do understand that the settings configured in this issue do not relate to the execution environment of kubectl, it would be nice to have a seamless integration.
As a side note, the current "workaround" or "solution" is to run Lens inside of WSL.

I had the same problem... The config in WSL does not work when passed to Lens in Windows. Here it worked when I setup kubectl on Windows directly, without using WSL. This is an annoying bug


[GHSA-9mg4-v392-8j68] erlang-jose (aka JOSE for Erlang and Elixir) through 1.11...

Updates

Affected products
CVSS
Severity
Summary

Comments
Add affected package & versions as well as CVSS

Hi @maennchen, https://github.com/potatosalad/erlang-jose/commit/718d213f07b08056737923f8063d5df56dcb66ae says the vulnerability is fixed in 1.11.7.  Is that wrong?

@JonathanLEvans Oh, you’re right. There was 3 releases (.7 - .9) in rapid succession.
Can I edit this PR normally since it was done via the form?

No problem, I will take care of it on my end.  I just wanted to make sure I was not missing anything.


Bootstrap jenkins jobs

Create an initial seed job to run other jobdsl files to create jobs. These are downloaded by the entrypoint.sh script ready for jenkins to process

LGTM 👍


Card stuck on swipe

Sometimes, cards are stuck when swipe. How do I make it to be easily swiped out.

Can you provide some code or screenshot?


fixes bug 1264400 - Delay setup for Faye subscription

Coverage remained the same at 84.787% when pulling 280e86ff557d1582cf8cf57bc50207080b9da47d on peterbe:bug-1264400-delay-setup-for-faye-subscription into 2df922f160ec30899e4a8d2cf7df610c48d792c7 on mozilla:master.


RadioGroupButton: VR motion implementation

Summary
VR RadioGroupButton motion implementation WITHOUT other VR specific styles.
What changed?
BEFORE

AFTER

Links

Jira
Figma

Checklist

[ ] Added unit tests
[ ] Added documentation + accessibility tests
[x] Verified accessibility: keyboard & screen reader interaction
[x] Checked dark mode, responsiveness, and right-to-left support
[x] Checked stakeholder feedback (e.g. Gestalt designers, relevant feature teams)

i assume we don't need to listen to useReducedMotion here... can you confirm that?


docker-machine env places double quotes around path for DOCKER_CERT_PATH, but around the certificate

To reproduce:
$(docker-machine env dev)
$ docker ps
FATA[0000] Couldn't read ca cert "/Users/booyaa/.docker/machine/machines/dev"/ca.pem: open "/Users/booyaa/.docker/machine/machines/dev"/ca.pem: no such file or directory

presumably for this to work, the file path to ca.pem should be: "/Users/booyaa/.docker/machine/machines/dev/ca.pem"
this behaviour appears to be have been introduced in v0.2.0.
version I'm using: docker-machine version 0.2.0 (45f08d9)
os: OSX Yosemite 10.10.2

It's eval $(docker-machine env machine) to load the settings into the env now.

cheers!


Fix BroadcastServiceTest.FastTestBackendProducer member variable runnable to be volatile

to avoid hang in testSlowClient.

Closing because Marie's PR https://github.com/kaazing/gateway/pull/335 is the one that should be merged. This was just experimental.


⚠ Digital Ocean - https://status.digitalocean.com/ has degraded performance

In 260d443, Digital Ocean - https://status.digitalocean.com/ (https://status.digitalocean.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 184 ms

Resolved: Digital Ocean - https://status.digitalocean.com/ performance has improved in d0dbb91.


Remove SimpleMap, Add Flatten into Block Enumeration

@prachigauriar @macdrevx Please Review…

[x] End the life of TWTSimpleMap
[x] Implementation of flatten for arrays and dictionaries
[x] Create better randomized tests
[x] Documentation

:+1:


standardizing method names

proposal:

rename function enableUnits() --> enable_units()
rename function disableUnits() --> disable_units()
create functions enable_signomials() and disable_signomials(), to replace current practice of modifying the module-level boolean variable gpkit.enable_signomials.

Sounds good to me.

Implemented in #228. Forgot to build the docs, resulting in #231, but that's now fixed.


Request to check Build Android

We try to build Android with your building guide, but we meet the build error.
This is my environment and version of tools.
export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
export ANDROID_HOME=~/Android/Sdk
export ANDROID_NDK_HOME=~/Android/Sdk/ndk/21.3.6528147
After downloading codes on master branch, I follow your guide until 'make -f Makefile-Android'
Could you check to build Android??
We began to check this building issue because of android-studio build error
.../connectedhomeip/src/android/CHIPTool/app/src/main/java/com/google/chip/chiptool/setuppayloadscanner/BarcodeFragment.kt: (119, 27): Unresolved reference: SetupPayloadParser
For getting .so files, we thought it needs to build ndk.
And we tried to do 'build Android'.
If you have the best solution for android-studio build error, share with us, plz.

@vidhis88 ?

The steps to build Android are listed in the README here: https://github.com/project-chip/connectedhomeip/tree/master/src/android/CHIPTool
Please let me know if this still doesn't help build the Android demo app.

I believe this issue is obsolete: we moved the build system to GN and there are build instructions.
The error seems to be caused by a failure to load so (either themselves or libstdc++). This should be resolved if following the readme since it contains some not as obvious steps.


Accessing REST api outside local computer

Background
I'm trying to perform commands via the REST api on my local network.  I receive an immediate "connection refused" when I try to access the REST api from a different computer on the same network.
Your environment

version of lnd: 0.4.2
which operating system (uname -a on *Nix): 4.14.34-v7+ (ARM debian)
version of btcd, bitcoind, or other backend: 0.16.0
any other relevant environment details: I'm on a Raspberry PI

Steps to reproduce
The relevant line of lnd.conf:
restlisten=<IP_ADDRESS>:8080
I then performed the following curl request from a computer on my network:
curl --insecure --header "Grpc-Metadata-macaroon: [mymacarroon]" https://[myip]:8080/v1/getinfo
Expected behaviour
I was expected to get info about the node.  When I run the same command above on the Raspberry PI (with localhost substituted for [myip]) I get a response with the node info.  I can also successfully access the RPC endpoint from outside my local computer.
Actual behaviour
I immediately receive the following error:
curl: (7) Failed to connect to [myip] port 8080: Connection refused

Ensure that your NAT situation is figured out. You'll need to ensure that the ports are being forwarded properly.
If you're trying to access via LAN, then you'll need to use the local IP, not your external IP.

I'm only on my local LAN and I'm using my local (192.168.x.xxx) IP address.  Again, this is working for gRPC, just not for REST.

Check to ensure (using a tool like netstat or lsof) that lnd is actually listening on the proper port.

I had the restlisten line in the wrong location in lnd.conf...I now get a response from lnd.  However, I now get a certificate error.  The answer in issue 684 is to regenerate the certificates with additional IP addresses...however after some googling I couldn't figure out how to generate certificates in such a way as to include specific IP addresses.  Any guidance would be appreciated!

I had the restlisten line in the wrong location in lnd.conf...I now get a response from lnd. However, I now get a certificate error. The answer in issue 684 is to regenerate the certificates with additional IP addresses...however after some googling I couldn't figure out how to generate certificates in such a way as to include specific IP addresses. Any guidance would be appreciated!

Hi were you able to figure out how to regenerate the certificates?


JSON data in trained model return not found.

Hi, I am getting this when I try one trained model.

Hi,
By just looking at the error, it's seems that it's not finding your Rasa Core/Nlu. Just a few questions as check mark before going deep into the problem.
Yours Rasa NLU and Core are proper running ?
Did you registered them correclty into Rasa UI ?
Are you able to call them outside RasaUI, through command line?

Hi,
Yes, NLU and Core are proper running in port 5000 and 5005 respectively, I go to localhost:5000 and localhost:5005 and a messages like Hello from Rasa NLU  appears.
What do you mean with registered into Rasa UI?  I have NLU, CORE and Postgres running in dockers and I deploy all througt docker-compose up call from console.

@ProgramadorDeValor  I really appreciate if you can guide me step by step I been searching for information about this but I don't know how to solve this. I don't understand English well and I think I am misunderstanding the README.md. Thank you so much.


Allow pinning the gateway to a specific version of the schema

The idea here is to force the gateway to keep using the same version of the schema. It's obviously not safe and error-prone :)
The "forcing" part can be either on our side (Hive) or on the gateway level (code).
If it's on our side, we will have to keep track of the "pinned" version and keep it on the CDN storage as latest.
If it's controllable by the gateway, it means we have to start storing artifacts of every version in the CDN storage (we use R2 so it's fine).
I prefer the gateway approach as it reduces the complexity on our side.

We got that question during one of the meetings. I personally would avoid this pattern but if we can make it possible without headaches on our side, I'm okay with it.