Pre triage aqatests with jdk17

Release Summary Report for openjdk17-pipeline
Report generated at: Tue, 28 Jun 2022 16:17:26 GMT
TRSS Build and TRSS Grid View
Jenkins Build URL https://ci.adoptopenjdk.net/job/build-scripts/job/openjdk17-pipeline/444/
Started by upstream project "build-scripts/weekly-openjdk17-pipeline" build number 77 at 6/26/2022, 8:05:10 AM

create_installer_mac ❌ undefined ❌
create_installer_windows ❌ undefined ❌
jdk17u-aix-ppc64-temurin ❌ FAILURE ❌
jdk17u-aix-ppc64-temurin_SmokeTests ❌ FAILURE ❌
jdk17u-alpine-linux-aarch64-temurin ❌ FAILURE ❌
jdk17u-alpine-linux-x64-temurin ❌ FAILURE ❌
jdk17u-linux-aarch64-temurin ❌ FAILURE ❌
jdk17u-linux-arm-temurin ❌ FAILURE ❌
jdk17u-linux-ppc64le-temurin ❌ FAILURE ❌
jdk17u-linux-s390x-temurin ❌ FAILURE ❌
jdk17u-linux-x64-temurin ❌ FAILURE ❌
jdk17u-mac-aarch64-temurin ❌ FAILURE ❌
jdk17u-mac-x64-temurin ❌ FAILURE ❌
jdk17u-windows-x64-temurin ❌ FAILURE ❌
jdk17u-windows-x86-32-temurin ❌ FAILURE ❌
sign_build ❌ undefined ❌
sign_installer ❌ undefined ❌
sign_temurin_gpg ❌ undefined ❌

Test_openjdk17_hs_extended.openjdk_aarch64_alpine-linux ❌ ABORTED ❌
Test_openjdk17_hs_extended.openjdk_aarch64_alpine-linux_testList_0 ❌ ABORTED ❌
jdk_security3_2 => deep history 0/1 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_aarch64_alpine-linux_testList_1 ❌ ABORTED ❌
jdk_security4_0 => deep history 0/1 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_aarch64_linux ❌ FAILURE ❌
java -version
openjdk version "17.0.4" 2022-07-19
OpenJDK Runtime Environment Temurin-17.0.4+7 (build 17.0.4+7)
OpenJDK 64-Bit Server VM Temurin-17.0.4+7 (build 17.0.4+7, mixed mode, sharing)

jdk_net_0 => deep history 3/4 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_arm_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_arm_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_custom_0 => deep history 0/1 passed | possible issues |
langtools_custom_0 => deep history 0/1 passed | possible issues |
jvm_native_sanity_0 => deep history 0/1 passed | possible issues |
runtime_nestmate_0 => deep history 0/1 passed | possible issues |
jdk_beans_0 => deep history 0/1 passed | possible issues |
jdk_other_0 => deep history 0/1 passed | possible issues |
jdk_net_0 => deep history 0/1 passed | possible issues |
jdk_security3_0 => deep history 0/1 passed | possible issues |
jdk_management_0 => deep history 0/1 passed | possible issues |
jdk_security4_0 => deep history 0/1 passed | possible issues |
jdk_rmi_0 => deep history 0/1 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_arm_linux_testList_1 ⚠ UNSTABLE ⚠
jvm_compiler_0 => deep history 0/2 passed | possible issues |
hotspot_custom_0 => deep history 0/1 passed | possible issues |
jdk_io_0 => deep history 0/2 passed | possible issues |
jdk_nio_2 => deep history 0/2 passed | possible issues |
jdk_text_0 => deep history 0/2 passed | possible issues |
jdk_tools_0 => deep history 0/2 passed | possible issues |
jdk_security_infra_0 => deep history 0/2 passed | possible issues |
jdk_build_0 => deep history 0/2 passed | possible issues |
jdk_instrument_0 => deep history 0/2 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_arm_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_nio_0 => deep history 0/5 passed | possible issues |
jdk_security1_0 => deep history 0/5 passed | possible issues |
jdk_security2_0 => deep history 0/5 passed | possible issues |
jdk_time_0 => deep history 0/5 passed | possible issues |
jdk_jmx_0 => deep history 0/5 passed | possible issues |
jdk_jfr_0 => deep history 0/5 passed | possible issues |
jdk_jdi_0 => deep history 0/5 passed | possible issues |
jdk_imageio_0 => deep history 0/5 passed | possible issues |
jdk_native_sanity_0 => deep history 0/5 passed | possible issues |
jdk_vector_0 => deep history 0/5 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_ppc64_aix ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_0 ⚠ UNSTABLE ⚠
jdk_net_0 => deep history 0/4 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_1 ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_ppc64_aix_testList_2 ⚠ UNSTABLE ⚠
jdk_nio_0 => deep history 0/3 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_ppc64le_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_other_1 => deep history 2/3 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_s390x_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_s390x_linux_testList_1 ⚠ UNSTABLE ⚠
jdk_security_infra_0 => deep history 1/4 passed | possible issues |
jdk_security_infra_1 => deep history 2/3 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_x86-32_windows ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_0 ⚠ UNSTABLE ⚠
jdk_custom_0 => deep history 0/1 passed | possible issues |
langtools_custom_0 => deep history 0/1 passed | possible issues |
jvm_native_sanity_0 => deep history 0/1 passed | possible issues |
jvm_compiler_2 => deep history 0/4 passed | possible issues |
runtime_nestmate_0 => deep history 0/1 passed | possible issues |
jdk_beans_0 => deep history 0/1 passed | possible issues |
jdk_other_0 => deep history 0/1 passed | possible issues |
jdk_net_0 => deep history 0/1 passed | possible issues |
jdk_security3_2 => deep history 0/3 passed | possible issues |
jdk_security3_0 => deep history 0/1 passed | possible issues |
jdk_security4_0 => deep history 0/1 passed | possible issues |
jdk_management_0 => deep history 0/1 passed | possible issues |
jdk_rmi_0 => deep history 0/1 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_1 ⚠ UNSTABLE ⚠
hotspot_custom_0 => deep history 0/1 passed | possible issues |
jvm_compiler_0 => deep history 0/2 passed | possible issues |
jdk_io_0 => deep history 0/2 passed | possible issues |
jdk_nio_2 => deep history 0/1 passed | possible issues |
jdk_text_0 => deep history 0/2 passed | possible issues |
jdk_tools_0 => deep history 0/2 passed | possible issues |
jdk_instrument_0 => deep history 0/2 passed | possible issues |
jdk_build_0 => deep history 0/2 passed | possible issues |
jdk_security_infra_0 => deep history 0/2 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_2 ❌ FAILURE ❌
Test_openjdk17_hs_extended.openjdk_x86-64_alpine-linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-64_alpine-linux_testList_1 ⚠ UNSTABLE ⚠
jdk_jdi_1 => deep history 0/4 passed | possible issues |
jdk_jdi_0 => deep history 0/3 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_x86-64_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_jfr_1 => deep history 2/3 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_x86-64_windows ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-64_windows_testList_0 ⚠ UNSTABLE ⚠
jdk_jfr_1 => deep history 2/3 passed | possible issues |
jdk_other_0 => deep history 0/4 passed | possible issues |
Test_openjdk17_hs_extended.perf_ppc64_aix ❌ FAILURE ❌
Test_openjdk17_hs_extended.system_arm_linux ⚠ UNSTABLE ⚠
java -version
openjdk version "17.0.4" 2022-07-19
OpenJDK Runtime Environment Temurin-17.0.4+7 (build 17.0.4+7)
OpenJDK Server VM Temurin-17.0.4+7 (build 17.0.4+7, mixed mode, sharing)

MiniMix_5m_0 => deep history 0/10 passed | possible issues |
ConcurrentLoadTest_5m_0 => deep history 0/10 passed | possible issues |
DBBLoadTest_5m_0 => deep history 0/10 passed | possible issues |
LangLoadTest_5m_0 => deep history 0/10 passed | possible issues |
LockingLoadTest_0 => deep history 0/10 passed | possible issues |
UtilLoadTest_5m_0 => deep history 0/10 passed | possible issues |
HCRLateAttachWorkload_previewEnabled_0 => deep history 0/10 passed | possible issues |
MathLoadTest_all_5m_0 => deep history 0/10 passed | possible issues |
Test_openjdk17_hs_extended.system_ppc64_aix ❌ FAILURE ❌
Test_openjdk17_hs_extended.system_x86-32_windows ⚠ UNSTABLE ⚠
java -version
openjdk version "17.0.4" 2022-07-19
OpenJDK Runtime Environment Temurin-17.0.4+7 (build 17.0.4+7)
OpenJDK Client VM Temurin-17.0.4+7 (build 17.0.4+7, mixed mode, emulated-client)

MathLoadTest_all_5m_0 => deep history 0/10 passed | possible issues |
MiniMix_5m_0 => deep history 0/10 passed | possible issues |
ConcurrentLoadTest_5m_0 => deep history 0/10 passed | possible issues |
DBBLoadTest_5m_0 => deep history 0/10 passed | possible issues |
LangLoadTest_5m_0 => deep history 0/10 passed | possible issues |
LockingLoadTest_0 => deep history 0/10 passed | possible issues |
UtilLoadTest_5m_0 => deep history 0/10 passed | possible issues |
HCRLateAttachWorkload_previewEnabled_0 => deep history 0/10 passed | possible issues |
Test_openjdk17_hs_sanity.functional_aarch64_alpine-linux ⚠ UNSTABLE ⚠
java -version
openjdk version "17.0.4" 2022-07-19
OpenJDK Runtime Environment Temurin-17.0.4+7 (build 17.0.4+7)
OpenJDK 64-Bit Server VM Temurin-17.0.4+7 (build 17.0.4+7, mixed mode, sharing)

cmdLineTester_libpathTestRtfChild_0 => deep history 0/9 passed | possible issues |
Test_openjdk17_hs_sanity.functional_x86-64_alpine-linux ⚠ UNSTABLE ⚠
java -version
openjdk version "17.0.4" 2022-07-19
OpenJDK Runtime Environment Temurin-17.0.4+7 (build 17.0.4+7)
OpenJDK 64-Bit Server VM Temurin-17.0.4+7 (build 17.0.4+7, mixed mode, sharing)

cmdLineTester_libpathTestRtfChild_0 => deep history 1/7 passed | possible issues |
Test_openjdk17_hs_sanity.openjdk_aarch64_alpine-linux ⚠ UNSTABLE ⚠
java -version
openjdk version "17.0.4" 2022-07-19
OpenJDK Runtime Environment Temurin-17.0.4+7 (build 17.0.4+7)
OpenJDK 64-Bit Server VM Temurin-17.0.4+7 (build 17.0.4+7, mixed mode, sharing)

jdk_lang_0 => deep history 0/9 passed | possible issues |
jdk_lang_1 => deep history 0/9 passed | possible issues |
jdk_lang_2 => deep history 0/9 passed | possible issues |
Test_openjdk17_hs_sanity.openjdk_aarch64_linux ❌ FAILURE ❌
java -version
Due to the maximum characters of comment separate the summary to two comments.

openjdk version "17.0.4" 2022-07-19
OpenJDK Runtime Environment Temurin-17.0.4+7 (build 17.0.4+7)
OpenJDK 64-Bit Server VM Temurin-17.0.4+7 (build 17.0.4+7, mixed mode, sharing)

Post Test => deep history 3/9 passed | possible issues
Test_openjdk17_hs_sanity.openjdk_arm_linux ❌ FAILURE ❌

aarch64_alpine- hang https://github.com/adoptium/aqa-tests/issues/3799

arm test targets naming with _0 are running mode150, should be corrected by https://github.com/adoptium/TKG/pull/333 .
Test_openjdk17_hs_extended.openjdk_arm_linux_testList_1 ⚠ UNSTABLE ⚠
jdk_nio_2 => deep history 0/2 passed | possible issues |

Test_openjdk17_hs_extended.openjdk_aarch64_linux ❌ FAILURE ❌
11:44:47  Cannot contact test-docker-ubuntu2204-armv8l-1: java.lang.InterruptedException
Cancelling nested steps due to timeout
18:29:52  Could not connect to test-docker-ubuntu2204-armv8l-1 to send interrupt signal to process
[Pipeline] sh
18:29:52  test-docker-ubuntu2204-armv8l-1 was marked offline: This agent is offline because Jenkins failed to launch the agent process on it.

Test_openjdk17_hs_extended.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_ppc64le_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_other_1 => deep history 2/3 passed | possible issues |

Test_openjdk17_hs_extended.openjdk_ppc64le_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_ppc64le_linux_testList_2 ⚠ UNSTABLE ⚠
jdk_other_1 => deep history 2/3 passed | possible issues |

Test_openjdk17_hs_extended.openjdk_s390x_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_s390x_linux_testList_1 ⚠ UNSTABLE ⚠
jdk_security_infra_0 => deep history 1/4 passed | possible issues |
jdk_security_infra_1 => deep history 2/3 passed | possible issues |

Test_openjdk17_hs_extended.openjdk_x86-64_linux ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-64_linux_testList_0 ⚠ UNSTABLE ⚠
jdk_jfr_1 => deep history 2/3 passed | possible issues |
Test_openjdk17_hs_extended.openjdk_x86-64_windows ⚠ UNSTABLE ⚠
Test_openjdk17_hs_extended.openjdk_x86-64_windows_testList_0 ⚠ UNSTABLE ⚠
jdk_jfr_1 => deep history 2/3 passed | possible issues |
jdk_other_0 => deep history 0/4 passed | possible issues |

TODO
Test_openjdk17_hs_sanity.functional_x86-64_alpine-linux ⚠ UNSTABLE ⚠
java -version
cmdLineTester_libpathTestRtfChild_0 => deep history 1/7 passed | possible issues |
Test_openjdk17_hs_sanity.openjdk_aarch64_linux ❌ FAILURE ❌
java -version
Post Test => deep history 3/9 passed | possible issues


chore(docs): Update build-preferences.md

Made changes to  description of hls and smoothstreaming track types.
Please advise.

I'm closing this PR as I requested some changes and haven't gotten any feedback.


x/tools/gopls: drop support for building at Go 1.12

As discovered in CL 380555, some of our dependencies no longer support building with Go 1.12. This is to be expected -- 1.12 was a long time ago.
#50825 outlines a long-term plan to remove support for building gopls at legacy Go versions, but in the meantime we need to to mark<EMAIL_ADDRESS>as the final release supporting being built by Go 1.12. Fortunately, this is consistent with our stated support for the four latest major Go versions.
Action items:

[x] check with the VS Code team to see if there's anything we can do to help users avoid breakage when upgrading gopls from VS Code (CC @hyangah @suzmue)
[x] document our new compatibility matrix.
[x] update the v0.7.5 release notes
[x] remove Kokoro 1.12 CI
[x] upgrade our dependencies, thus breaking the 1.12 build

using golang v1.12.17 with gopls v0.7.5 not working, reporting
../../../../pkg/mod/golang.org/x/tools@v0.1.9-0.20220114220130-fd7798718afd/go/analysis/passes/buildtag/buildtag.go:13:2: package go/build/constraint is not in GOROOT (/usr/local/go1.12.17/go/src/go/build/constraint)
../../../../pkg/mod/github.com/!burnt!sushi/toml@v0.4.1/decode_go116.go:6:2: package io/fs is not in GOROOT (/usr/local/go1.12.17/go/src/io/fs)

@Davidrjx did you use go get -u?
 Is there a reason you cannot use a supported version of Go?

@Davidrjx did you use go get -u?
 Is there a reason you cannot use a supported version of Go?

i was building calico v3.9.1 and project source contains a go.mod file


Allow missing IdP hint

This is the case then the OpenID client does not forward the kc_idp_hint which is provided by the magic button

[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.143 s - in de.intension.authentication.WhitelistAuthenticatorTest


How to disable devtools ?

Is there an option to disable this shiny new devtool ?

Perfect thanks !

Can you unregister vite-plugin-vue-devtools in plugin options of vite.config.{j,t}s?

Is there an option to disable this shiny new devtool ?

What is the reason to disable it and what are the conditions to either show it or not? I think you could provide more context about what is it what you expect, @Mikaleb...

Currently, DevTools will be forcibly enabled during development (vite dev) and will never be bundled in production (vite build). So, don't worry about that.

Currently, DevTools will be forcibly enabled during development (vite dev) and will never be bundled in production (vite build). So, don't worry about that.

maybe he want to disable the tool, when the envirment is develop.
just use shotcut to show tool's UI, but don't show the icon always.

You can disable this option to do this.

Is there an option to disable this shiny new devtool ?

What is the reason to disable it and what are the conditions to either show it or not? I think you could provide more context about what is it what you expect, @Mikaleb...

I think the corresponding habit settings can be saved in the project's .local, for example:

Scenario 1: Enter pinia, open the store / time by default.
Project members prefer the chrome extension version of vue dev. You can set whether to enable it in .local.

You can disable this option to do this.

How to open it again? Lmao... It disappeared and I don't get it how to open it back again.
First, I try to search HOW TO DISABLE IT, spend 10 minutes on it, find old solution, doesn't work
Find this, fine, toggle this thingy, it disappears completely
Are you serious?
I understand that devtools is a good and helpful thing, but UX is severely lacking on this one...

You can disable this option to do this.

How to open it again? Lmao... It disappeared and I don't get it how to open it back again.
First, I try to search HOW TO DISABLE IT, spend 10 minutes on it, find old solution, doesn't work Find this, fine, toggle this thingy, it disappears completely
Are you serious?
I understand that devtools is a good and helpful thing, but UX is severely lacking on this one...

Yeah, our shortcut descriptions are very lacking 😅. And sorry our contributors are currently very busy and not too active in solving this issue 🥲.
Anyway, this is a brief:
How to disable the devtools anchor?
You can disable the option called Always show the floating panel on the Settings page.
How to open it again?
By shortcut

cmd + shift + D in macOS
alt + shift + D in Windows

align with Nuxt devtools.

I love this tool! It's very handy.
Unfortunately, it's also breaking my Cypress tests in my local development environment. I need to be able to programmatically prevent the floating buttons from appearing within Cypress, preferably without removing them completely from my development environment.

@dash- Does that mean vue-devtools works for you in a cypress environment? As in: You could actually interact with them in a cypress-driven browser? Because that is what I am trying to achieve at the moment. (I guess I am having the opposite of your problem).

Currently, DevTools will be forcibly enabled during development (vite dev) and will never be bundled in production (vite build). So, don't worry about that.

(cc @alexzhang1030 ) I think this is worth mentioning in the main documentation, or in the FAQ.  It's not clear (at least to me, and probably other developers) that the plugin doesn't get included in vite build steps out-of-the-box without any user configuration.

Currently, DevTools will be forcibly enabled during development (vite dev) and will never be bundled in production (vite build). So, don't worry about that.

(cc @alexzhang1030 ) I think this is worth mentioning in the main documentation, or in the FAQ.  It's not clear (at least to me, and probably other developers) that the plugin doesn't get included in vite build steps out-of-the-box without any user configuration.

make sense, I will update it

Does anyone have a fix for removing this annoying floating panel thing?

I have the option turned off.. but the thing keeps reappearing?

Comment out import vueDevTools from 'vite-plugin-vue-devtools' in vite.config.js then comment out vueDevTools() from the plugins


R Visual Template

Added the basic R Custom Visual template
Updated the VisualBuilder to support watching and taking the content of
script.r file and place it's content inside the pbiviz capabilities

Hi @raananzvi, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Raanan Zvi). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


[GHSA-5jf7-8333-m22j] Authorization Bypass Through User-Controlled Key in...

Updates

Affected products
CVSS
Description
Severity
Source code location
Summary

Hi @p-w, unfortunately we are not accepting this contribution because it is about an affected product that cannot be found within our supported ecosystems.
Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!


Doug has hair

Please remove all references to Doug having hair in the project

No, he just needs more babaga

Doug being bald is now canon, it was closed as completed


Enhance provision fixtures to specify policy fixtures and align with the db service implementation

Duplicate of https://github.com/opentdf/platform/issues/786 which has been addressed and closed.


ERROR-extracting assets from Data/globalgamemanagers

Data.zip
this is assets resource of my app with Unity 5.5.4p4.
I want to  extract resources from this file, but get an System.IO.EndOfStreamException.
I have no knowledge of c#, can u fix it?

yes, fixed in 88304561ee0cb4b42357fa3bffc9f77cfa1adfa5

thx

now it export Shader only.

ohhh... try latest

thx for fixing this bug

The scenes of this app should have  loading , Paris, New York at least.
I'm trying to fix the bug of exporting only one scene.


[CBS] Could not find XML element title

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.06.06
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log
$ youtube-dl -v 'https://www.paramountplus.com/shows/survivor/video/Rcmd9CGvysrl13uSff93up_SnD5RzVfH/survivor-my-million-dollar-mistake/'
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--restrict-filenames', '-o', '%(title)s-%(id)s-%(uploader)s.%(ext)s', '-w', '-v', 'https://www.paramountplus.com/shows/survivor/video/Rcmd9CGvysrl13uSff93up_SnD5RzVfH/survivor-my-million-dollar-mistake/']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.06.06
[debug] Python version 3.9.6 (CPython) - Linux-5.10.52-with-glibc2.33
[debug] exe versions: ffmpeg 4.4, ffprobe 4.4
[debug] Proxy map: {}
[CBS] Rcmd9CGvysrl13uSff93up_SnD5RzVfH: Downloading XML
ERROR: Could not find XML element title; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/lib/python3.9/site-packages/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/usr/lib/python3.9/site-packages/youtube_dl/extractor/cbs.py", line 115, in _real_extract
    return self._extract_video_info(content_id)
  File "/usr/lib/python3.9/site-packages/youtube_dl/extractor/cbs.py", line 65, in _extract_video_info
    title = xpath_text(video_data, 'videoTitle', 'title', True)
  File "/usr/lib/python3.9/site-packages/youtube_dl/utils.py", line 1911, in xpath_text
    n = xpath_element(node, xpath, name, fatal=fatal, default=default)
  File "/usr/lib/python3.9/site-packages/youtube_dl/utils.py", line 1904, in xpath_element
    raise ExtractorError('Could not find XML element %s' % name)
youtube_dl.utils.ExtractorError: Could not find XML element title; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description
Worked fine in the past (and the first two episodes of this season still work), but the latest episode does not.

I get the same API result in UK but the target URL redirects to a "Paramount+ coming soon to your region" page so it's not possible to reproduce the item playing in the browser.
@2011, you checked the statement that the URL played in the browser for you. Can you confirm that? Was any special procedure needed (login, geo-bypass, etc)?

This issue is not specific to the one particular episode of Survivor but instead appears to be the majority of new content (but definitely not all) added to Paramount+ on or after 10/4/2021. Some more examples URLs that exhibit the same behavior (all episodes that aired on or after 10/4/2021:
https://www.paramountplus.com/shows/bull/video/TUT_4UVB87huHEOfPCjMkxOW_Xe1hNWw/bull-gone
https://www.paramountplus.com/shows/ncis/video/LzcJLBA2OGq_fE1bDD3NF7lx_zGEyt3L/ncis-road-to-nowhere
https://www.paramountplus.com/shows/csi-vegas/video/ct82smMrQDbogrBqISHZEJKj3IUOI1yo/csi-vegas-legac
https://www.paramountplus.com/shows/fbi-most-wanted/video/xKRZ7nMYi0i9WjKk5yUBwIPmmEVRrXvM/fbi-most-wanted-tough-love/

can confirm all 4 of your test URLs work with yt-dlp

Also see #29564.

Another example...
youtube-dl --verbose https://www.cbsnews.com/video/paul-mccartney-the-compromise-inside-the-epidemic/
[debug] System config: ['-o', '/path/to/youtube-dl/%(extractor)s/%(series)s/%(series)s-%(uploader)s-%(title)s.%(ext)s', '--write-sub', '--write-auto-sub', '--sub-lang', 'en,it']
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.cbsnews.com/video/paul-mccartney-the-compromise-inside-the-epidemic/']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.06.06
[debug] Python version 3.8.10 (CPython) - Linux-5.11.0-38-generic-x86_64-with-glibc2.29
[debug] exe versions: ffmpeg 4.2.4, ffprobe 4.2.4
[debug] Proxy map: {}
[cbsnews] paul-mccartney-the-compromise-inside-the-epidemic: Downloading webpage
[cbsnews] 81Vb59Y_YNG_XzqL_SV7AARydZLiXNQv: Downloading XML
ERROR: Could not find XML element title; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/3rdparty/youtube-dl/youtube-dl/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/usr/local/bin/3rdparty/youtube-dl/youtube-dl/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/3rdparty/youtube-dl/youtube-dl/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/3rdparty/youtube-dl/youtube-dl/youtube_dl/extractor/cbsnews.py", line 108, in _real_extract
    return self._extract_video_info(item['mpxRefId'], 'cbsnews')
  File "/usr/local/bin/3rdparty/youtube-dl/youtube-dl/youtube_dl/extractor/cbs.py", line 65, in _extract_video_info
    title = xpath_text(video_data, 'videoTitle', 'title', True)
  File "/usr/local/bin/3rdparty/youtube-dl/youtube-dl/youtube_dl/utils.py", line 1911, in xpath_text
    n = xpath_element(node, xpath, name, fatal=fatal, default=default)
  File "/usr/local/bin/3rdparty/youtube-dl/youtube-dl/youtube_dl/utils.py", line 1904, in xpath_element
    raise ExtractorError('Could not find XML element %s' % name)
youtube_dl.utils.ExtractorError: Could not find XML element title; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

https://github.com/ytdl-org/youtube-dl/issues/30197

Se also 30247

Ive been ignoring these as they require sign in, but if someone can provide credentials I can look into fixing it. If you want to, run the following command and reply back with the output:
echo USER:PASS | age -a -r age1zkz9g0kld97vs826j0r7p3ghvz3zcyd4tcqr2vrxpt0uux7mkycsl77hy6

https://github.com/FiloSottile/age

Maybe just look at the same code in YT-DLP and see what they did to fix it?

@jefft666 I am not going to implement a fix on something I cant even test.

Maybe just look at the same code in YT-DLP and see what they did to fix it?

Done it. Feel free to test PR #30085 as linked above.

https://github.com/ytdl-org/youtube-dl/issues/30417

https://github.com/ytdl-org/youtube-dl/issues/30491

The patch seems to work for all the videos on this page:
cbs.com/shows/survivor/video/EktRdacCXDsJo8Qqyw18Rg26tLwfzk4N/survivor-juggling-chainsaws
https://cbsios-vh.akamaihd.net/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/21/1951002179554/CBS_SURVIVOR_4102_PRORES_2997_846322_,503,4628,3128,2228,1628,848,000.mp4.csmil/master.m3u8?hdnea=acl=/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/21/1951002179554/CBS_SURVIVOR_4102_PRORES_2997_846322_*~exp=1646520979~hmac=598cbf18d8261a446978746b7b26197016dd1ae3b9e8827b7ed540f7461bcbaa
cbs.com/shows/survivor/video/Rcmd9CGvysrl13uSff93up_SnD5RzVfH/survivor-my-million-dollar-mistake
https://cbsios-vh.akamaihd.net/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/28/1953791555546/CBS_SURVIVOR_4103_PRORES_2997_873188_,503,4628,3128,2228,1628,848,000.mp4.csmil/master.m3u8?hdnea=acl=/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/28/1953791555546/CBS_SURVIVOR_4103_PRORES_2997_873188_*~exp=1646520980~hmac=506b72a271405ef1cf49414573f130f418015369d5e6842d0115aff0c8494aa9
paramountplus.com/shows/bull/video/TUT_4UVB87huHEOfPCjMkxOW_Xe1hNWw/bull-gone
https://cbsios-vh.akamaihd.net/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/29/1954671683728/CBS_BULL_601_PRORES_2398_881248_,503,4628,3128,2228,1628,848,000.mp4.csmil/master.m3u8?hdnea=acl=/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/29/1954671683728/CBS_BULL_601_PRORES_2398_881248_*~exp=1646520980~hmac=fac5513eab1a70c0eb3c74909b68dd10a8fb47843ded6ad6eaeb834f54729315
paramountplus.com/shows/csi-vegas/video/ct82smMrQDbogrBqISHZEJKj3IUOI1yo/csi-vegas-legac
https://cbsios-vh.akamaihd.net/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/29/1954245699947/CBS_CSI_VEGAS_101_UHD_FIX_R1_1122829_,503,4628,3128,2228,1628,848,000.mp4.csmil/master.m3u8?hdnea=acl=/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/29/1954245699947/CBS_CSI_VEGAS_101_UHD_FIX_R1_1122829_*~exp=1646520980~hmac=4596d6d806f49db22f6c11c350e293cd94b7ddb6000eddfa8a70b388d17b8b2a
paramountplus.com/shows/fbi-most-wanted/video/xKRZ7nMYi0i9WjKk5yUBwIPmmEVRrXvM/fbi-most-wanted-tough-love
https://cbsios-vh.akamaihd.net/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/28/1953787459869/CBS_FBI_MW_303_WB_2398_917161_,503,4628,3128,2228,1628,848,000.mp4.csmil/master.m3u8?hdnea=acl=/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/28/1953787459869/CBS_FBI_MW_303_WB_2398_917161_*~exp=1646520981~hmac=6660382837a910759b4b1ee631a40934cdc0e6dece605de4d45c6261c3ada771
paramountplus.com/shows/ncis/video/LzcJLBA2OGq_fE1bDD3NF7lx_zGEyt3L/ncis-road-to-nowhere
https://cbsios-vh.akamaihd.net/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/28/1953779779705/CBS_NCIS_421_2398_865739_,503,4628,3128,2228,1628,848,000.mp4.csmil/master.m3u8?hdnea=acl=/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/28/1953779779705/CBS_NCIS_421_2398_865739_*~exp=1646520981~hmac=36e0ed5be142a3edd34d9e0bb2e5a8d68c3535cca16e89b96de3212964d87752
paramountplus.com/shows/survivor/video/Rcmd9CGvysrl13uSff93up_SnD5RzVfH/survivor-my-million-dollar-mistake
https://cbsios-vh.akamaihd.net/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/28/1953791555546/CBS_SURVIVOR_4103_PRORES_2997_873188_,503,4628,3128,2228,1628,848,000.mp4.csmil/master.m3u8?hdnea=acl=/i/temp_hd_gallery_video/CBS_Production_Outlet_VMS/video_robot/CBS_Production_Entertainment/2021/09/28/1953791555546/CBS_SURVIVOR_4103_PRORES_2997_873188_*~exp=1646520981~hmac=e2af427ea1f948ab2708faaefe5d22c144eda52503f329f4a3630b53637a63a4
but it does fail with some others:
paramountplus.com/shows/the-harper-house/video/eyT_RYkqNuH_6ZYrepLtxkiPO1HA7dIU/the-harper-house-the-harper-house


[BUG] After annotating the documentation for entity-associated property, the dto language generates a class with incorrect documentation for the flat-associated property.

The entity definition is as follows:
interface Task {
    /**
     * 任务数据源
     */
    @OneToOne
    val connector: Connector
}

interface Connector {
    /**
     * 数据源id
     */
    @Id
    @GeneratedValue(generatorType = UUIDIdGenerator::class)
    val id: String

    /**
     * 连接器类型
     *
     * @see ConnectorType
     */
    val type: ConnectorType
}

The dto attribute is defined as follows:
input CreateTaskParam {
    flat(connector) {
        id? as connectorId
        type? as connectorType
    }
}

The generated classes are as follows:
open class CreateTaskParam(
    /**
     * 任务数据源
     */
    @get:NotNull(
        message = "数据源id不可为空"
    )
    public val connectorId: String? = null,
    /**
     * 任务数据源
     */
    @get:NotNull(
        message = "数据源类型不可为空"
    )
    public val connectorType: ConnectorType? = null
)

In flat(connector), the comments for id and type should not be the comments for the connector's document in Task, but should be the comments for them in Connector.

Try 0.8.134

Same...
DTO definition:

Generated dto class:

Entity interface definitions are the same as before.


Allow users to join an organization

Overview
Allows users to join and leave an organization. If a user attempts to join an organization before they are logged in, they are redirected to a modal asking them to sign up.

Add new API endpoint for joining organization
Connect frontend to backend
Add new redux module for organizationJoin
Add API endpoint for leaving organization
Show JoinOrganization modal for unauthenticated users when attempting to join an organization
Update AuthModalContent to support reuse as part of the OrganizationJoin workflow
Format and lint

Checklist

[x] Description of PR is in an appropriate section of CHANGELOG.md and grouped with similar changes, if possible

Demo
Before Join - logged in

After join - user in org

Before join - unauthenticated user

Before join - prompt to login

Notes

Per @tgilcrest 's comment on #226 , we are still waiting for updated copy to be used in AuthModalContent. Additionally, we will need to wire this up a bit more to support automatic joining of an organization after successful registration when clicking this button. My thinking is that this probably makes sense to tackle in a separate issue? Let me know your thoughts here.

Testing Instructions

./scripts/update
In your DB shell, create a new organization (e.g., slug: PHL)
Login on the frontend and navigate to http://localhost:3003/o/{SLUG}
Attempt to join the organization
Expect: Page refreshes, and updates to list 1 mapper and button text updates to indicate that the current user already belongs to this organization
Attempt to leave the organization by clicking the 'Leave Organization' button
Expect: Page refreshes, and updates to list 0 mappers

Closes #226

Auth modal should now be closed once a user has logged in.


[enhancement] Removed exception message Closes #46

Removed an exception and the test for the removed exception
Closes #46

I do not know why coveralls is decreasing with python2 yet staying the same with python3

With the coveralls only failing for python2? is it a good idea for me to drop python2 support for this module as my next task? As python2 is becoming obsolete now

You also have to update your tests to make sure the coverage does not decrease as mentioned in the issue.


0.71.0 has an upper bounds failure

I'm sending PRs to fix this upstream but we might want to work around this her in the meantime.
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps failed with message:
Failed while enforcing RequireUpperBoundDeps. The error(s) are [
Require upper bound dependencies error for com.google.auth:google-auth-library-oauth2-http:0.11.0 paths to dependency are:
+-com.google.cloud:upper-bounds-check:0.0.1-SNAPSHOT
  +-com.google.cloud:google-cloud-core:1.53.0
    +-com.google.api:gax:1.35.0
      +-com.google.auth:google-auth-library-oauth2-http:0.11.0
and
+-com.google.cloud:upper-bounds-check:0.0.1-SNAPSHOT
  +-com.google.cloud:google-cloud-storage:1.53.0
    +-com.google.cloud:google-cloud-core-http:1.53.0
      +-com.google.auth:google-auth-library-oauth2-http:0.12.0
and
+-com.google.cloud:upper-bounds-check:0.0.1-SNAPSHOT
  +-com.google.cloud:google-cloud-storage:1.53.0
    +-com.google.cloud:google-cloud-core-http:1.53.0
      +-com.google.api:gax-httpjson:0.52.0
        +-com.google.auth:google-auth-library-oauth2-http:0.11.0
]

What command were you running to find this? We should be able to catch this with CI.

This happened with the upper bounds checker for the cloud-oss-bom when I attempted to upgrade that to 0.71.0. 0.70.0 worked. I need to dig into this more deeply. It may depend on the order in which dependencies are declared.

I think that this repo is doing the right thing.  gax should update its com.google.auth:google-auth-library-oauth2-http.  renovate-bot will take care of that.  This specific issue is outdated now that auth was upgraded in gax: https://github.com/googleapis/gax-java/pull/701


Update bug-report.yaml for 1.6-exp1

A microsoft employee must use /azp run to validate using the pipelines below.
WARNING:
Comments made by azure-pipelines bot maybe inaccurate.
Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR
(https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary)
and run the build against your PR branch with the default parameters.

A microsoft employee must use /azp run to validate using the pipelines below.
WARNING: Comments made by azure-pipelines bot maybe inaccurate. Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR (https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary) and run the build against your PR branch with the default parameters.

I noticed that the version date of Windows App sdk 1.6 experimental 1 has been determined on May 30th, but it will be on June 4th (Beijing time,GMT+8). Windows App sdk 1.6 experimental 1 is still not released, is there any problem that leads to the delayed release?
我注意到 Windows App sdk 1.6 experimental 1 的版本日期已经确定在 5 月 30 日，然而时到 6 月 4 日（北京时间，GMT+8）， Windows App sdk 1.6 experimental 1 仍没有发布，是遇到了什么问题导致延迟发布了吗？

A microsoft employee must use /azp run to validate using the pipelines below.
WARNING: Comments made by azure-pipelines bot maybe inaccurate. Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR (https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary) and run the build against your PR branch with the default parameters.

I noticed that the version date of Windows App sdk 1.6 experimental 1 has been determined on May 30th, but it will be on June 4th (Beijing time,GMT+8). Windows App sdk 1.6 experimental 1 is still not released, is there any problem that leads to the delayed release?
我注意到 Windows App sdk 1.6 experimental 1 的版本日期已经确定在 5 月 30 日，然而时到 6 月 4 日（北京时间，GMT+8）， Windows App sdk 1.6 experimental 1 仍没有发布，是遇到了什么问题导致延迟发布了吗？

Please keep in mind that Redmond is on GMT-7. Which means there is a 15 hour time difference between Beijing and Microsoft.
This PR was made on Friday, then it's weekend which are non office hours.
They just finished their first day of the week.  I'm sure they'll release it soon :)

A microsoft employee must use /azp run to validate using the pipelines below.
WARNING: Comments made by azure-pipelines bot maybe inaccurate. Please see pipeline link to verify that the build is being ran.
For status checks on the main branch, please use TransportPackage-Foundation-PR (https://microsoft.visualstudio.com/ProjectReunion/_build?definitionId=81063&_a=summary) and run the build against your PR branch with the default parameters.

I noticed that the version date of Windows App sdk 1.6 experimental 1 has been determined on May 30th, but it will be on June 4th (Beijing time,GMT+8). Windows App sdk 1.6 experimental 1 is still not released, is there any problem that leads to the delayed release?
我注意到 Windows App sdk 1.6 experimental 1 的版本日期已经确定在 5 月 30 日，然而时到 6 月 4 日（北京时间，GMT+8）， Windows App sdk 1.6 experimental 1 仍没有发布，是遇到了什么问题导致延迟发布了吗？

Please keep in mind that Redmond is on GMT-7. Which means there is a 15 hour time difference between Beijing and Microsoft. This PR was made on Friday, then it's weekend which are non office hours. They just finished their first day of the week. I'm sure they'll release it soon :)

Thank you very much for your answer. Hope to see the new version released soon.

/azp run


document is error

document is error：
https://bucket4j.com/7.0.0/toc.html#using-bucket-as-scheduler
2.1.3. Using bucket as scheduler
bucket.asScheduler().consume(1);
interface SchedulingBucket is not existed method  consume(long numTokens)
https://bucket4j.com/7.0.0/toc.html#scheduling-bucket

Indeed, the documentation indicates that you should use: bucket.asScheduler().consume(1); (cf. screen capture or link to documentation).
But in the source, you only have this method available: CompletableFuture<Void> consume(long numTokens, ScheduledExecutorService scheduler); so I don't know how to migrate from 6 to 7. Thx

Hello guys,
The method asScheduler has been renamed in 7.0.0 to asBlocking

Thanks


theme color option

Sorry, I haven't resolved this before, but I haven't got time until now. I updated the package with a new version c03f993273ead946858c4f32c2c066e0424896cb (0.2.0) which has an external JSON config file. If you are interested, you can give it a look. Also, I see you have created your own repository, so it is probably irrelevant, but you should use a fork instead of copying the repository next time, so I will get a little crediting to my original repository.


Clear comments

Cleared commented out codes as requested.

Thanks @nimiakinleye 😄  if you can fix the merge conflicts this will be ready to merge.

Thanks @nimiakinleye 😄  if you can fix the merge conflicts this will be ready to merge.


Trinity.Storage.Composite refactoring

@thautwarm please ignore the data importer part. I'm migrating it to leverage Trinity.Storage.Composite instead of the old implementation of code building.
This PR updates Trinity.Storage.Composite:

namespace aligned to Trinity.Storage.Composite
references Trinity.TSL.CodeGen.exe, which will be available at runtime. thus we do not have to use a python collector script to collect the assemblies. just invoke "dotnet" and install the packages.
merge GraphEngine.DataImporter and its CoreCLR counterpart. Multi-targeting is achieved.
reduce accessibility levels for most classes in Trinity.Storage.Composite.
Simplify the setup of Trinity.Storage.Composite -- no more parameterized initial setup

we should compare the performance of the three:

pythonnet interop
our ffi interfaces
use ctype to load trinity.ffi


Consider supporting proxy references in Lifetime

Describe the Request
Consider support proxy references (OwnedProxy, RefProxy, RefMutProxy) with lifetimes. This idea may ultimately not make sense and we'd rather keep lifetimes and ownership separate, but I'm curious if we can unify them. Specifically, we could use lifetimes to ensure that borrows are valid as done by the Rust compiler.
Sample Code
No response

Closing this as "not planned" for now.
Right now we have three distinct mechanisms for managing target object lifetimes, and I think it'll be good to use those for a bit and see where the pain points are before adding new features.


rust-analyzer-unwrapped: 2023-04-17 -> 2023-04-24

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for rust-analyzer-unwrapped is: A modular compiler frontend for the Rust language
meta.homepage for rust-analyzer-unwrapped is: https://rust-analyzer.github.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2023-04-24 with grep in /nix/store/3yasypbpggzcj0mkvsx2vh6w4g6x5lzk-rust-analyzer-unwrapped-2023-04-24
found 2023-04-24 in filename of file in /nix/store/3yasypbpggzcj0mkvsx2vh6w4g6x5lzk-rust-analyzer-unwrapped-2023-04-24

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
rust-analyzer
rust-analyzer-unwrapped
vscode-extensions.rust-lang.rust-analyzer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/3yasypbpggzcj0mkvsx2vh6w4g6x5lzk-rust-analyzer-unwrapped-2023-04-24 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A rust-analyzer-unwrapped https://github.com/r-ryantm/nixpkgs/archive/08afd721843f5e8e606cf342b7132ab70d9f61e1.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3yasypbpggzcj0mkvsx2vh6w4g6x5lzk-rust-analyzer-unwrapped-2023-04-24
ls -la /nix/store/3yasypbpggzcj0mkvsx2vh6w4g6x5lzk-rust-analyzer-unwrapped-2023-04-24/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

rust-analyzer
rust-analyzer-unwrapped
vscode-extensions.rust-lang.rust-analyzer

Maintainer pings
cc @oxalica for testing.

@ofborg build rust-analyzer-unwrapped rust-analyzer-unwrapped.passthru.tests


OverflowError: Python int too large to convert to C long

Thanks for the hard work in this project.  It's really helpful.
I just have one problem to report, when I try and parse the Windows EVTX file 'CAPI2' I get the error below.  Is there a workaround please?  I am actually using the library to parse every EVTX file in a certain directory and this EVTX is the only one that throws up a problem!
  File "g:\Python Code\Events\Evtx2Time.py", line 121, in <module>
    main()
  File "g:\Python Code\Events\Evtx2Time.py", line 71, in main
    for xml, record in evtx_file_xml_view(fh):
  File "C:\Python27\lib\Evtx\Views.py", line 221, in evtx_file_xml_view
    record_str = _build_record_xml(record, cache=cache)
  File "C:\Python27\lib\Evtx\Views.py", line 172, in _build_record_xml
    xml = rec(record.root())
  File "C:\Python27\lib\Evtx\Views.py", line 163, in rec
    subs_strs.append(rec(sub))
  File "C:\Python27\lib\Evtx\Views.py", line 154, in rec
    f = _make_template_xml_view(root_node, cache=cache)
  File "C:\Python27\lib\Evtx\Views.py", line 120, in _make_template_xml_view
    template_instance = root_node.fast_template_instance()
  File "C:\Python27\lib\Evtx\Nodes.py", line 909, in fast_template_instance
    return TemplateInstanceNode(self._buf, ofs, self._chunk, self)
  File "C:\Python27\lib\Evtx\Nodes.py", line 716, in __init__
    self._data_length += new_template.length()
  File "C:\Python27\lib\Evtx\Nodes.py", line 211, in length
    return self.tag_length() + self.data_length()
  File "C:\Python27\lib\Evtx\BinaryParser.py", line 205, in no_length_handler
    return f(offset)
  File "C:\Python27\lib\Evtx\BinaryParser.py", line 356, in unpack_dword
    return struct.unpack_from("<I", self._buf, o)[0]
OverflowError: Python int too large to convert to C long

huh, i'm not sure whats happening here. the stack trace is useful, but i can't see why the overflow error would be thrown on struct.unpack_from.
is there any chance you can share the evtx file? i dont think i have a similar one on my system, and haven't been able to reproduce this error.

a workaround might be to use 64-bit python, if that's feasible.
the reported issue is still a bug, however.

Hi Willi,
Thanks for getting back to me.  Sorry my response took a few day.
I have attached the EVTX log file but please just delete it when you've done your testing.
Thanks,
Chris,
On Tuesday, 11 October 2016, 18:46, Willi Ballenthin<EMAIL_ADDRESS>wrote:

a workaround might be to use 64-bit python, if that's feasible.the reported issue is still a bug, however.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

would you email this to me directly at<EMAIL_ADDRESS>when you respond to a github notification email, github doesn't know what to do with attachments, so i didn't get it.
thanks!


Add color to status field of agents tab

When I open the agents tab, my attention is immediately drawn towards the process column, because it's blue and contains the information icon. For some reason my instinct immediately tells me something is wrong when I see the page, even when all agents are up. I think it would be good to colorize/iconize the status field, as such that it's immediately clear which agents are up and which agents are causing a problem.
The colors should be:

up == green
down == red
paused == yellow/warning

Hey team! Please add your planning poker estimate with ZenHub @andraskvr @Stijnkool


how to use connection.ping and when to use it?

@dougwilson ,
can I ask some help. How can I implement the connection.ping in my server.js ?
is this the right way
io.on('connection', function (socket) {

  socket.on('display_1', function (data) {
     pool.getConnection(function (err, connection) {
                    if (err) {
                        console.error('error connecting: ' + err.stack);

                    }
     connection.ping(function (err) {
      if (err) throw err;
      console.log('Server responded to ping');
    });
     connection.query({...});
         //some implementation here.

  });

 });

  socket.on('display_2', function (data) {
     pool.getConnection(function (err, connection) {
                    if (err) {
                        console.error('error connecting: ' + err.stack);

                    }
     connection.ping(function (err) {
      if (err) throw err;
      console.log('Server responded to ping');
    });
     connection.query({...});
         //some implementation here.

  });
 });

});

Thank you in advance.

You never need to call connection.ping(), especially because pool.getConnection() already calls ping on the connection before handing it to your code, so all you're doing above it calling ping a second time every time.

Thank you


qtbase do_install broken after update to recent oe-core

Updated my oe-core yesterday (was so happy my patched made it into warror..).
Now I get dozens of errors at qt install:
log)_do_install.txt
Have no idea what's going wrong except that pseudo was updated and maybe qtbase tries something that pseudo does't accept...

Is it reproducible in clean build (after removing tmp-glibc)?
I've updated oe-core yesterday as well and haven't seen this issue in my jenkins builds yet.

Yes I started build from scratch and cleansstate qtbase does not help - it looks 100% reproducible for me.
In my desperation, I have now updated build host (Fedora 29) and a new glibc was installed.

This is 100% reproducible for me as well. This is a recent change (in the last few days).

My builds are on Ubuntu 18.04 and e.g.
http://jenkins.nas-admin.org/job/LuneOS/view/unstable/job/luneos-unstable_qemux86/191/consoleFull
just finished with this oe-core revision from today:
http://git.openembedded.org/openembedded-core/commit/?id=7469c2a5595337fc4407fa7a2ad06b5bf2347545
and latest meta-qt5 revision a4bf2402c19742b866cf4b5e5e4665ae070500ff
On Fri, Apr 12, 2019 at 7:43 PM Andreas Müller<EMAIL_ADDRESS>wrote:

Yes I started build from scratch and cleansstate qtbase does not help - it
looks 100% reproducible for me.
In my desperation, I have now updated build host (Fedora 29) and a new
glibc was installed.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/meta-qt5/meta-qt5/issues/187#issuecomment-482662038,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLW0pjEXmAo167iSa93oTnsk4GWgXGkks5vgMWtgaJpZM4csfgW
.

meta-qt5: same a4bf2402c19742b866cf4b5e5e4665ae070500ff
oe-core now warrior master from today b5f493078335a77dea2f229d36629399d897a528
And the worst: After update and restart of host as mentioned and building from scratch I now get an error at do_compile!!
I'll come back with log later - am working on other issues currently (there are lots - not OE specific only)...

I'm bisecting the breakage in meta, I'll let you know when I have a commit.

We'll see - my glass ball says [1]
[1] https://git.openembedded.org/openembedded-core/commit/?id=0fb257121b68f38b40c078150db8f7d0979b7ea5

I suspect so, I have gotten this far. I don't think I'll get a chance to finish it today:

5958938313 (refs/bisect/bad) gobject-introspection: auto-enable/-disable gobject-introspection for meson (by Andreas Müller 8 days ago)
88188807a6 elfutils: remove Elfutils-Exception and include GPLv2 for shared libraries (by Mikko Rapeli 33 hours ago)
d70c77e4d5 python3: Fix ptest output parsing (by Richard Purdie 4 days ago)
2a48df02a2 python3: Avoid hanging tests (by Richard Purdie 5 days ago)
0fb257121b pseudo: Update to gain key bugfixes (by Richard Purdie 2 days ago)
a3923085d1 (refs/bisect/good-a3923085d1cad7de7e644ff57d05c4a8955b5b00) busybox: Use PTEST binary directory (by Mariano Lopez 4 days ago)

Yeah, pseudo: Update to gain key bugfixes is the first bad commit in meta.

Well, that's concerning.
/home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-mortsgna-linux-gnueabi/qtbase/5.12.2+gitAUTOINC+856fb1ab44-r0/recipe-sysroot-native/usr/bin/qmake -install qinstall -exe /home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-mortsgna-linux-gnueabi/qtbase/5.12.2+gitAUTOINC+856fb1ab44-r0/git/bin/syncqt.pl /home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-mortsgna-linux-gnueabi/qtbase/5.12.2+gitAUTOINC+856fb1ab44-r0/image/usr/bin/syncqt.pl
Error copying /home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-mortsgna-linux-gnueabi/qtbase/5.12.2+gitAUTOINC+856fb1ab44-r0/git/bin/syncqt.pl to /home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-mortsgna-linux-gnueabi/qtbase/5.12.2+gitAUTOINC+856fb1ab44-r0/image/usr/bin/syncqt.pl: Cannot create /home/superandy/tmp/oe-core-glibc/work/cortexa7t2hf-neon-vfpv4-mortsgna-linux-gnueabi/qtbase/5.12.2+gitAUTOINC+856fb1ab44-r0/image/usr/bin/syncqt.pl for output

This seems to be the root actual error.
The actual changes are (1) on systems that have renameat2 wrappers in glibc, block access to renameat2 through the wrapper, not just through the generic syscall wrapper, (2) handle blocking opens of pipes differently.
I'm guessing it isn't the pipe thing, so this could be a change with renameat2 handling. If that means that qmake actually needs renameat2, and hasn't got a way to fall back if renameat2 doesn't work, then we definitely have a serious problem, because renameat2 is surprisingly hard to implement in pseudo, which is why it's just being blocked right now.

I think with this background a solution might be simple: We have already a patch deciding to use renameat2 or not (LOL the author has lost his brain - can't remember) [1].
If I am not mistaken is just needs adjustment. Will play around a bit and get back then.
[1] https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/qtbase/0013-Check-glibc-version-for-renameat2-statx-on-non-boots.patch

That would explain it, yeah! Sorry about this -- the underlying problem is that it turns out pseudo's IPC and database code doesn't have a good way to handle atomic exchange renames, and while I could in theory just ENOSYS on those, I thought it would be safer if the renameat2 code just errored out unconditionally, because that's more likely to result in code concluding that it's unsupported.
I might try to actually implement the support some day, but it's a much larger thing, and it'll probably still stay broken for the syscall wrapper case -- syscall parameters are more magic than I'm comfortable trying to handle on code that might need to run on multiple architectures.

I start to remember [1]: Since then renameat2 got mandatory to avoid direct syscalls by coreutils (and that's why I did the patch for - I guess).
Wonder what qmake does when disabling renamat2 these days...
Ahh and - I think people not seeing breakages have glibc < 2.28 and elder coreutils - right?
[1] http://lists.openembedded.org/pipermail/openembedded-core/2018-March/267587.html

Yup, the glibc wrapper got added in glibc 2.28. We already did ENOSYS for direct syscalls using the RENAMEAT2 syscall, because it's hard to translate safely.
It's a lovely system call, it just violates assumptions I made designing pseudo's original protocol.

Looked through meta-qt5 git log:

@shr-project  introduced 539e4f09f749f024d6e157a49559e5ad7f51470a to fix build with glibc 2.28.
I followed with 2d1d8078156d050994a6cf46298d836b357df15c

Martin's patch is gone - so my first approach is to remove mine either. Build from scratch is running....

Nope - just remove  https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qt5/qtbase/0013-Check-glibc-version-for-renameat2-statx-on-non-boots.patch does not do the job - zzz

Can you just try unconditionally defining # define QT_FEATURE_renameat2 -1 ? I'm hoping that means it uses a fallback!

Yes that's the next step

After fixing all typos in commit message (hopefully) patch is ready for test [1].
@alistair23: Maybe you want to give it a try
[1] https://github.com/meta-qt5/meta-qt5/pull/189

Yep, that fixes the install failure for me.

There is probably a more advanced patch where you could catch ENOSYS as well as EINVAL and just fall through that function FWIW...

On Ubuntu 18.04 with:
ii  libc6:amd64                  2.27-3ubuntu1                     amd64
ii  coreutils                    8.28-1ubuntu1                     amd64
it's not reproducible (so 8.28 coreutils alone isn't the issue only in combination with glibc 2.28). Or depends on coreutils patches as mentioned by Peter in oe-core ML:
http://lists.openembedded.org/pipermail/openembedded-core/2019-April/281343.html
With Ubuntu 19.04 beta with:
ii  libc6:amd64                  2.29-0ubuntu2               amd64
ii  coreutils                    8.30-1ubuntu1               amd64
and Ubuntu 18.10 with:
ii  libc6:amd64                  2.28-0ubuntu1                     amd64
ii  coreutils                    8.28-1ubuntu2                     amd64
I was able to reproduce it, but only with qt 5.12 (not with 5.11 from meta-qt5/thud).
Now when I can reproduce, I'll test your PR on Ubuntu and if it fixes the issue there as well I'll merge it to warrior and master (probably together with 5.12.3 upgrade). Thanks

I'm going to merge these patches soon, but still something isn't right.
I was going to report on oe-core ML, that new pseudo finally really resolved the issue with host-user-contamination as often triggered in glibc-locale (one of my builders already finished 1700 rebuilds of glibc-locale without any host-user-contamination error).
But then when testing the PR for this issue (together with 5.12.3 upgrade on top of it) I already got few host-user-contamination issues there:
ERROR: qtwebengine-5.12.3+gitAUTOINC+c7b8d6d878_4c7ecce300-r0 do_package_qa: QA Issue: qtwebengine: /qtwebengine-qmlplugins/usr/lib/qml/QtWebEngine/Controls1Delegates/MenuItem.qml is owned by uid 1026, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
ERROR: qtquickcontrols-5.12.3+gitAUTOINC+3a5ac4885b-r0 do_package_qa: QA Issue: qtquickcontrols: /qtquickcontrols-qmlplugins/usr/lib/qml/QtQuick/Dialogs/qml/DefaultWindowDecoration.qml is owned by uid 1026, which is the same as the user running bitbake. This may be due to host contamination
So maybe the 0013-Check-glibc-version-for-renameat2-statx-on-non-boots.patch patch was still useful to prevent host-user-contamination with pseudo which I haven't seen with qt5* recipes for quite long time possibly since 5.9* where I'm still using host-user-contamination issues as well even with the latest revision from pseudo (3fa7c853e0bcd6fe23f7524c2a3c9e3af90901c3 ERROR: QA Issue: lib32-qtquickcontrols: /lib32-qtquickcontrols-qmlplugins/usr/lib/qml/QtQuick/Dialogs/DefaultColorDialog.qmlc is owned by uid 1101, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated])

I'm guessing that the addition of the glibc renameat2 patch is going to break some things that were previously working, although I'm not totally sure how. We may need to try to catch more cases, or possibly even implement some of them. (As noted elsewhere, actually handling renameat2 is going to be really ugly in pseudo, which is why it hasn't happened yet, but we might be able to handle some subset of cases reasonably.)
The obvious question would be: Can you find specific renameat2 calls, especially their flags, that are happening but failing, so I can develop a better plan for this?

Haven't had the time to look into pseudo sources yet but if I understood @seebs correctly, actual pseudo returns ENOSYS on renameeat2 for glibc wrapper or direct system call.

Old 0013-Check-glibc-version-for-renameat2-statx-on-non-boots.patch did check glibc version and in case of >= 2.28 it enabled renameat2 calls. This does not work any more with current pseudo and host glibc >= 2.28
New 0018-Avoid-renameeat2-for-native-sdk-builds.patch disables renameat2 independent of host glibc version and - to ensure there was nothing overseen - removes code using renameat2. The code below the area removed supplies a fallback.

Both host-contamination share that they are on installation of qml-files (and that they seem to occure unreproducible).
Don't know for 'qml-file' installation:

if the 2 cases are enough to create some rule out of it
is special - means using other tool than qmake for installation

I've added https://bugzilla.yoctoproject.org/show_bug.cgi?id=12434#c48 with a bit more information about this issue.


README: add link to the libnmstate python API

In addition, notify that the nmstatectl manual page is available.
Signed-off-by: Fernando Fernandez Mancera<EMAIL_ADDRESS>

Coverage decreased (-0.04%) to 66.135% when pulling 7231b190cee88787bd73b9ec4805b791336bddcf on ffmancera:api_readme into 9c1663c8154df823d54aa43244a392ab6f4929cb on nmstate:master.

Coverage decreased (-0.04%) to 66.135% when pulling 7231b190cee88787bd73b9ec4805b791336bddcf on ffmancera:api_readme into 9c1663c8154df823d54aa43244a392ab6f4929cb on nmstate:master.


Init Azure.ResourceManager.ElasticSan

/azp run prepare-pipelines

/azp run net - elasticsan - ci

API change check for Azure.ResourceManager.ElasticSan
API review is created for Azure.ResourceManager.ElasticSan. You can review APIs here.


Replace bindings by WBT blocks through Simulink function calls

Implements #5 and subsequent fixes (refer to https://github.com/dic-iit/matlab-whole-body-simulators/issues/5#issuecomment-771047600).
Default iCub simulation should work exactly as before (should render same robot behavior), except that it should run approximately 3 times faster.

Ping @GiulioRomualdi , @Giulero .

For the last commit, refer to https://github.com/dic-iit/matlab-whole-body-simulators/issues/5#issuecomment-772948255.

Hi @nunoguedelha ! Maybe I've something wrong in my configuration, but I've got this error
An error occurred in the block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System' during compile.
Caused by:
Simulink detected an error
 'Simulink encountered an error while allocating a handle object in MATLAB System block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System'. Create the handle object only once in the corresponding System object 'robotDynWC.step_block'.'.

 The error occurred for MATLAB System block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System'.

 To prevent this error, use one of the following:
 * Modify the System object to avoid code that does not support code generation.
 * Change 'Simulate using' parameter to 'Interpreted Execution'.

Hi @nunoguedelha ! Maybe I've something wrong in my configuration, but I've got this error
An error occurred in the block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System' during compile.
Caused by:
Simulink detected an error
 'Simulink encountered an error while allocating a handle object in MATLAB System block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System'. Create the handle object only once in the corresponding System object 'robotDynWC.step_block'.'.

 The error occurred for MATLAB System block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System'.

 To prevent this error, use one of the following:
 * Modify the System object to avoid code that does not support code generation.
 * Change 'Simulate using' parameter to 'Interpreted Execution'.

Also, when the simulink model stops the file manager moves to /lib/RobotDynamicsWithContacts.

Hi @Giulero , it stops in RobotDynamicsWithContacts everytime it stops due to an error, otherwise it stops in the original repo root folder matlab-whole-body-simulators. I would say this is a normal behavior.
I never saw this error before. Could you start MATLAB from scratch and try again?

Rework completed. @Giulero

@Giulero , @GiulioRomualdi , I've updated the README for reflecting the Config.USE_OSQP flag deprecation.

I tried starting Matlab from scratch and run test_matlab_system_19.
Same error :(

I tried starting Matlab from scratch and run test_matlab_system_19.
Same error :(

Hi @Giulero  I'm trying to reproduce it in my environment...

Let's see if @CarlottaSartore (MATLAB 2019b + Linux) and @VenusPasandi (MATLAB2020b + Linux) have the same issue.
I definitely can't reproduce it (MATLAB 2019b + MacOS).

My computer Configuration:

Ubuntu 18.04 LTS
matlab-whole-body-simulator

commit e14d45088f4f4ec1896f075311538739b35c70dc (HEAD -> feature/replace-bindings-by-wbt-blocks, origin/feature/replace-bindings-by-wbt-blocks)
Author: Nuno Guedelha<EMAIL_ADDRESS>Date:   Thu Feb 4 23:27:04 2021 +0100

    Update the README w.r.t. the deprecation of Config.USE_OSQP and temporary use of qpOASES

IDynTree v2.0.2
WBtoolbox

Merge: 9a3848b 44f3d8b
Author: Diego Ferigo<EMAIL_ADDRESS>Date:   Tue Nov 24 14:23:23 2020 +0100

   Merge pull request #194 from CarlottaSartore/feature/CreateCMMSimulinkBlock

   Created CMM Simulink Block

Able to run ~1 sec of simulation (then the robot falls) and get this error

An error occurred while running the simulation and the simulation was terminated
Caused by:
MATLAB System block 'test_matlab_system_19/Robot visualizer/MATLAB System' error occurred when invoking 'stepImpl' method of 'Visualizer'. The error was thrown from '
 '/home/csartore/iit_ws/robotology-superbuild/build/install/mex/+iDynTreeWrappers/updateVisualization.m' at line 21
 '/home/csartore/iit_ws/matlab-whole-body-simulators/src/robotVisualizer/Visualizer.m' at line 42'.
Invalid value for Matrix property

Let's see if @CarlottaSartore (MATLAB 2019b + Linux) and @VenusPasandi (MATLAB2020b + Linux) have the same issue.

@nunoguedelha , I got the same error as @Giulero said https://github.com/dic-iit/matlab-whole-body-simulators/pull/15#issuecomment-773385872 as following
An error occurred in the block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System' during compile.
Caused by:
Simulink detected an error
 'Simulink encountered an error while allocating a handle object in MATLAB System block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System'. Create the handle object only once in the corresponding System object 'robotDynWC.step_block'.'.

 The error occurred for MATLAB System block 'test_matlab_system_19/RobotDynWithContacts/MATLAB System'.

 To prevent this error, use one of the following:
 * Modify the System object to avoid code that does not support code generation.
 * Change 'Simulate using' parameter to 'Interpreted Execution'.

Just for clarifying for anyone else joining the discussion:

@CarlottaSartore : Able to run ~1 sec of simulation (then the robot falls) and get this error

This error is an old error in the visualizer that occurs only when the robot gets to that weird position..

@VenusPasandi : I got the same error as @Giulero said #15 (comment) as following

this is what we are analyzing.
@VenusPasandi , could you please specify your machine configuration?
Apart from MATLAB version (2020b), do you share the same configuration (superbuild, etc) as @CarlottaSartore ?

After discussing with @VenusPasandi and @CarlottaSartore , we confirm that both the configurations they used are identical except for the MATLAB version. I will upgrade my MATLAB version tomorrow and analyze the problem. Let's wait until Friday at least before we merge this PR.

With Ubuntu 20.04 and Matlab 2020a I had the same error as @CarlottaSartore in https://github.com/dic-iit/matlab-whole-body-simulators/pull/15#issuecomment-775911762.
The robot was kind of exploding. Not sure what is the expected behavior.

Btw, I suggest checking also at the terminal output in which you launched Matlab. In my case I had:
sdafarra@iiticublap104:~$ matlab
MATLAB is selecting SOFTWARE OPENGL rendering.
Gtk-Message: 16:10:16.586: Failed to load module "canberra-gtk-module"
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.
Internal qpOASES error. Trying to solve the problem with the remaining number of iterations.

that may explain why the robot was exploding.

Btw, I suggest checking also the terminal output in which you launched Matlab. In my case I had:

Yes absolutely. At that point the robot was already under the floor a priori. We were having a a similar error way before this PR. Regarding the pqOASES failure, we were planing to handle the error more properly, allowing a given number of consecutive failures while using the last valid QP result, and stopping the simulation if that max number is reached. I've just opened https://github.com/dic-iit/matlab-whole-body-simulators/issues/16 for this.
For clarifying, the robot falling and sinking in the ground is an expected behaviour. The controller used in the test model is a fake controller, we are sending 0 torques to the joints and letting the robot fall on the ground to check the contacts handling.

For the record, this is what I see
https://user-images.githubusercontent.com/18591940/107637932-2e5dc900-6c6f-11eb-9302-b159218dfc4a.mp4
I also noticed that in the Diagnostic Viewer I have the message

Warning: The new value for the Matrix property may cause rendering problems.
In iDynTreeWrappers.updateVisualization (line 21)
In Visualizer/stepImpl (line 42)

It is printed at every visualization update. I confirm that the qpOases errors appear only when the robot is down below the ground.

For the record, this is what I see

Unfortunately, lately I cannot see videos attached to Github or Gitlab from Linux (probably because of Linux 20?). But I guess it matches my previous description.
Regarding the Warning, I have seen this for a while but as it is not a priori critical nor related to recent developments, I never had time to pay much attention.

After installing MATLAB 2020b, I've reproduced the issue:

Analysis ongoing...

Issue analysis (in Matlab internal code)
Error message Create the handle object only once in the corresponding System object found in the xml error definition file /Applications/MATLAB_R2020b.app/resources/SystemBlock/en/MATLABSystem.xml, mapping the key HandleObjectPersistentUnsupported.
A search on this keyword led to the help page /Applications/MATLAB_R2020b.app/help/simulink/ug/memory-management-of-handle-objects-in-generated-code.html.

We ruled out an issue related to the mask of the library.
Considering the keyword and the use cases addressed in the help page, we could guess that the issue is related to the section "A Handle Object That a Persistent Variable Refers To Must Be a Singleton Object".
Some persistent variable might be pointing the object step_block, or there is some problem with the "tunable", "nonTunable" parameters of the Matlab System block. Further analysis ongoing...

@VenusPasandi @CarlottaSartore @Giulero @S-Dafarra I've edited the analysis https://github.com/dic-iit/matlab-whole-body-simulators/pull/15#issuecomment-778027931.
The fix is working. Pushing it in a few.

Fix pushed and tested. @Giulero, @GiulioRomualdi or @CarlottaSartore , can you please review the fix (very few changes) such that we merge and unblock the other depending PRs?
Additional info for the review

main functional hange is

Removed parent class "handle" from KinDynComputations class definition

because of this, the call to a class method changing the class object has to return the updated object (change in Robot.m).
This fix allowed to have the property robot_config of "step_block" as Nontunable again.
Added also robot_config to the library mask (minor change for coherence, no functional impact except that this parameter appears clearly as an input of the library, as it was already the case for contact_config and physics.config).

Hi @GiulioRomualdi , @Giulero , any news on the approval? Sorry to insist, it's just that this PR is critical for improving the simulator performance in another project depending on it, specially this week. CC @CarlottaSartore

Thx @Giulero ! Merging


Spamming Error: Missing target pids from mounts since v6.11.0 (AWS, ECS, Docker)

Output of the info page (if this is a bug)
agent.status.txt
Describe what happened:
Ever since version 6.11.0 getting a lot of spam in logs about:
Error: Missing target pids from mounts

Describe what you expected:
No spam?
Steps to reproduce the issue:
This is reproable by just running the check docker command on the amazon ecs ami we're running:
The output looks like this:
/opt/datadog-agent/bin/agent/agent check docker
Multiple check instances found, running each of them
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
Error: Missing target pids from mounts
=== Series ===
And then a bunch of json for the actual docker containers

Additional environment details (Operating System, Cloud provider, etc):
AWS
Amazon ECS AMI (latest or near latest)

I am seeing the same problem, and still have some v6.10 running without this error.  Just to add some error messages I am seeing continuously.
2019-04-24 06:18:58 UTC | PROCESS | ERROR | (pkg/util/containers/metrics/cgroup_detect.go:53 in cgroupFilePath) | Missing target pids from mounts
2019-04-24 06:19:00 UTC | CORE | ERROR | (pkg/util/containers/metrics/cgroup_detect.go:53 in cgroupFilePath) | Missing target pids from mounts

I'm also seeing this with 6.11.0
2019-05-03 08:45:50 UTC | CORE | ERROR | (pkg/util/containers/metrics/cgroup_detect.go:53 in cgroupFilePath) | Missing target pids from mounts

Hi @thisdougb 👋

2019-05-20 08:16:51 UTC | CORE | ERROR | (pkg/util/containers/metrics/cgroup_detect.go:53 in cgroupFilePath) | Missing target pids from mounts
2019-05-20 08:16:54 UTC | PROCESS | ERROR | (pkg/util/containers/metrics/cgroup_detect.go:53 in cgroupFilePath) | Missing target pids from mounts

Only seeing  these errors in agent logs

we are getting the same issue using de 6.11.3, we had to rollback to 6.10.2 to avoid the log spam. any updates on this issue???

@dagisus the fix seems to be coming in the 6.12 release: https://github.com/DataDog/datadog-agent/milestone/52?closed=1

we are getting the same issue using de 6.11.3, we had to rollback to 6.10.2 to avoid the log spam. any updates on this issue???

we solved the issue by updating the ECS AMI to the latest. it seems that in previous versions some cgroup data is not stored in the default /cgroup/ and the documented /sys/fs/cgroup/ is also empty, we moved the cluster AMI to the latest to this date for us-east-1 ami-0f812849f5bc97db5 which has docker version 18.06.1-ce and Amazon agent version 1.28.1 running Amazon Linux 2. hope this helps.

Going to close this out since the fix was released with 6.12.0


Add post processing handler to GCS source stage.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: rokarolla:x: andrey.erokhinandrey.erokhin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: rokarolla:x: andrey.erokhinandrey.erokhin seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Library: qiskit torch trainer

Summary
Qiskit trainer for parallel QPU utilization using Qiskit Runtime Sessions
Details and comments
Example of usage
from quantum_serverless.library.train import (
    QiskitScalingConfig,
    QiskitTorchTrainer,
    get_runtime_session,
)

def loop(config):
    dataset_shard = session.get_dataset_shard("train")

    runtime_sessions = get_runtime_sessions(config) # this will give you session with dedicated backend for current worker
    qnn = create_qnn(Sampler(session=runtime_sessions[0]))
    ...

scaling_config = QiskitScalingConfig(
    num_workers=3,
    resource_filtering={
        "qpu1": {"simulator": True}, # all filters that goes to `QiskitRuntimeServier.backends` method
        "qpu2": {"simulator": True},
    },
    allow_overbooking=True # allow same backend assigned to multiple workers
)
runtime_service = QiskitRuntimeService(...)

trainer = QiskitTorchTrainer(
    train_loop_per_worker=loop,
    qiskit_runtime_service_account=runtime_service.active_account(), # TODO: fix to accept QiskitRuntimeService object
    scaling_config=scaling_config,
    datasets={"train": train_dataset}
)
trainer.fit()

TODOs:

[x] multiple session per worker
[x] tests
[x] documentation
[x] move to library module

References:
Program example https://github.com/Qiskit-Extensions/quantum-serverless/blob/chore/qiskit-for-ray-train/docs/tutorials/source_files/train.py
Tutorial notebook to run above program: https://github.com/Qiskit-Extensions/quantum-serverless/blob/chore/qiskit-for-ray-train/docs/tutorials/08_distributed_qml.ipynb

@ElePT ⬆

@ElePT updated description + added example.
Program example https://github.com/Qiskit-Extensions/quantum-serverless/blob/chore/qiskit-for-ray-train/docs/tutorials/source_files/train.py
Tutorial notebook to run above program: https://github.com/Qiskit-Extensions/quantum-serverless/blob/chore/qiskit-for-ray-train/docs/tutorials/08_distributed_qml.ipynb
Let me know if I missed anything?

closing due to no activity


When playing TuneIn's podcast, sometimes the GUI does not come up even after 5 mins but audio plays.

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

When playing TuneIn's podcast, sometimes the GUI does not come up even after 5 mins but audio plays.
What is the expected behavior?

TuneIn's GUI should come up.
What behavior are you observing?

TuneIn's podcast is playing but GUI doesn't come up.
Provide the steps to reproduce the issue, if applicable:

Alexa, Play the Rachel maddow show from TuneIn. (Waiing podcast playing and GUI comes up)
Alexa, Skip 30 minutes. (Waiting podcast skips to 30 minutes)
Alexa, Stop
Press [ESC] to clear screen
Alexa, Play the Rachel maddow show from TuneIn.

Then, repeat 3) ~ 5).
The below is DEBUG9 log from beginning to latest podcast playing.
avs_1.19.1_sssdk_2.1_TuneIn_Podcast_noui_debug9.zip
Tell us about your environment:

What version of the AVS Device SDK are you using?
  <1.19.1>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[x] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[x] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Have you tried the same use case with AVS Device SDK SampleApp?

[ ] The issue is not applicable to the AVS Device SDK SampleApp.
[x] The issue is not reproducible on the AVS Device SDK SampleApp.

Hi @oscar1372, Can you confirm if I understand this sequence of events correctly

Alexa, Play
-> Audio plays and UI appears
Alexa, Skip 30 minutes.
-> Audio moves forwards
Alexa, Stop
-> Audio stops
Press [ESC] to clear screen
-> Screen clears
Alexa, Play
-> Audio plays, UI apppears
Alexa, Stop
-> Audio stops
Press [ESC] to clear screen
-> Screen clears
Alexa, Play
-> Audio plays, UI does not appear

Specifically during steps 1 and 5 the UI appears, but on the third play (step 8) it does not?
Also is this issue specific to TuneIn podcasts or are you able to reproduce it with other sources?

Hi @oscar1372, Can you confirm if I understand this sequence of events correctly

Alexa, Play
-> Audio plays and UI appears
Alexa, Skip 30 minutes.
-> Audio moves forwards
Alexa, Stop
-> Audio stops
Press [ESC] to clear screen
-> Screen clears
Alexa, Play
-> Audio plays, UI apppears
Alexa, Stop
-> Audio stops
Press [ESC] to clear screen
-> Screen clears
Alexa, Play
-> Audio plays, UI does not appear

Specifically during steps 1 and 5 the UI appears, but on the third play (step 8) it does not?
Also is this issue specific to TuneIn podcasts or are you able to reproduce it with other sources?

Hi @powj , Yes, the issue is step 8 which UI doesn't appear when TuneIn podcast playing. This issue can reproduce on other TuneIn podcast (I checked Fighting talk also can reproduce).
When issue happened, I notices SDK received RenderPlayerInfo directive indeed.
2021-01-08 12:46:18.060 [ 21] I DirectiveSequencer:onDirective:directive=namespace\:TemplateRuntime\,name\:RenderPlayerInfo\,messageId\:3b8efed3-3eab-45c7-b748-0721dcecb2a3\,dialogRequestId\:\,correlationToken\:\,eventCorrelationToken\:\,payloadVersion\:\,instance\:
But it doesn't trigger UI render event to render. It seem SDK think they already rendering as the below but UI is invisible in fact.
2021-01-08 12:46:18.064 [ 1b] 5 TemplateRuntime:handleRenderPlayerInfoDirectiveInExecutor 2021-01-08 12:46:18.064 [ 1b] 3 TemplateRuntime:handleRenderPlayerInfoDirectiveInExecutor:audioItemId=amzn1.as-ct.v1.Dee-Domain-Music#ACRI#url#ACRI#a76435d5-b59d-4815-9964-943f124ee2ed\:1:Matching audioItemId in execution. 2021-01-08 12:46:18.065 [ 1b] 9 TemplateRuntime:notRenderingPlayerInfo:reason=sameDirectiveMultipleTimes.

Hi @powj , Yes, the issue is step 8 which UI doesn't appear when TuneIn podcast playing. This issue can reproduce on other TuneIn podcast (I checked Fighting talk also can reproduce).
When issue happened, I notices SDK received RenderPlayerInfo directive indeed.
2021-01-08 12:46:18.060 [ 21] I DirectiveSequencer:onDirective:directive=namespace\:TemplateRuntime\,name\:RenderPlayerInfo\,messageId\:3b8efed3-3eab-45c7-b748-0721dcecb2a3\,dialogRequestId\:\,correlationToken\:\,eventCorrelationToken\:\,payloadVersion\:\,instance\:
But it doesn't trigger UI render event to render. It seem SDK think they already rendering as the below but UI is invisible in fact.
2021-01-08 12:46:18.064 [ 1b] 5 TemplateRuntime:handleRenderPlayerInfoDirectiveInExecutor 2021-01-08 12:46:18.064 [ 1b] 3 TemplateRuntime:handleRenderPlayerInfoDirectiveInExecutor:audioItemId=amzn1.as-ct.v1.Dee-Domain-Music#ACRI#url#ACRI#a76435d5-b59d-4815-9964-943f124ee2ed\:1:Matching audioItemId in execution. 2021-01-08 12:46:18.065 [ 1b] 9 TemplateRuntime:notRenderingPlayerInfo:reason=sameDirectiveMultipleTimes.

Hi @oscar1372,
There were a variety of fixes that have been made since version 2.2 of the Smart Screen SDK which address issues around how exit and back navigation are handled.
If possible I would recommend upgrading to a later version as functions such as forceExit have changed significantly to address issues such as these.

Hi @oscar1372,
There were a variety of fixes that have been made since version 2.2 of the Smart Screen SDK which address issues around how exit and back navigation are handled.
If possible I would recommend upgrading to a later version as functions such as forceExit have changed significantly to address issues such as these.

Hi @powj, I checked the smart screen sdk 2.4 and can also reproduce same problem in this sdk. But the poodcast "Rachel maddow show" is not stable to play, I suggest uses Fighting Talk to reproduce issue.
Here is the log from device sdk 1.21.0 + smart screen sdk 2.4
tunein_podcast_noui_debug9.log
When I checked the log, I can find the same log for issue.
2021-01-20 15:52:11.992 [ 18] 3 TemplateRuntime:handleRenderPlayerInfoDirectiveInExecutor:audioItemId=amzn1.as-ct.v1.Dee-Domain-Music#ACRI#url#ACRI#4402f1a3-0056-4101-aab1-5efad5981e36\:1:Matching audioItemId in execution. 2021-01-20 15:52:11.992 [ 18] 9 TemplateRuntime:notRenderingPlayerInfo:reason=sameDirectiveMultipleTimes.
And notice the problem may caused by TemplateRuntime.cpp#478
I am not sure why does it need to clear m_audioItems when TemplateRuntime found it in last playback. I found issue doesn't happen after I remove TemplateRuntime.cpp#478
It seem GUI would base on m_audioitems to display playerInfo. Or m_audioitems is not root cause but will impact to GUI?

Hi @powj, I checked the smart screen sdk 2.4 and can also reproduce same problem in this sdk. But the poodcast "Rachel maddow show" is not stable to play, I suggest uses Fighting Talk to reproduce issue.
Here is the log from device sdk 1.21.0 + smart screen sdk 2.4
tunein_podcast_noui_debug9.log
When I checked the log, I can find the same log for issue.
2021-01-20 15:52:11.992 [ 18] 3 TemplateRuntime:handleRenderPlayerInfoDirectiveInExecutor:audioItemId=amzn1.as-ct.v1.Dee-Domain-Music#ACRI#url#ACRI#4402f1a3-0056-4101-aab1-5efad5981e36\:1:Matching audioItemId in execution. 2021-01-20 15:52:11.992 [ 18] 9 TemplateRuntime:notRenderingPlayerInfo:reason=sameDirectiveMultipleTimes.
And notice the problem may caused by TemplateRuntime.cpp#478
I am not sure why does it need to clear m_audioItems when TemplateRuntime found it in last playback. I found issue doesn't happen after I remove TemplateRuntime.cpp#478
It seem GUI would base on m_audioitems to display playerInfo. Or m_audioitems is not root cause but will impact to GUI?

Hey @oscar1372,
I'm trying Fighting Talk podcast with the scenario @powj mentioned. I can see the UI in step 8. Are you trying this with the same steps?

Hi @zsubas ,
Yes. It is same steps. I try again it seem doesn't reproduce now. However, Alexa can not do step 2 also in my testing this time.
I will try again later to confirm GUI can come up every time.

Hey @oscar1372,
I was able to reproduce this issue a couple of hours ago in R2.4, but now I'm not, I can see the card in both conditions. When you say just "play", directive comes from AVS Cloud, but when you say "Play fighting talk from TuneIn" it's skill's responsibility to send the directives. My guess is skill is not sending correct directives all the time. If you are still able to reproduce the issue, can you please enable -DACSDK_EMIT_SENSITIVE_LOGS=ON from CMake flags, reproduce the issue again and share the logs with me?

Closing due to inactivity. Please reopen if needed.


Improve File Hashing by Including stats.blocks

I was thinking about the file hashing, and detecting file changes and I realised we should really be using stats.blocks(The number of blocks actually allocated for a file) in our hashing calculation... 🤔
As we don't hash the entire file for performance reasons, files downloaded in chunks can be missed by the app as changes, as their file size doesn't account for file sparseness! 🔥
A fix for this would be use stats.blocks which would be easy, but unfortunately this would break our current .vha2 files as hashes would change...
Unless we do something clever, by checking if stats.blocks * stats.blksize >= stats.size, and use stats.size in that case! 👍 That would preserve backwards compatibility! 🚀
https://nodejs.org/api/fs.html#fs_class_fs_stats

Since this change can be added, as you describe, without breaking backwards compatibility, it seems like we can add it whenever (and it doesn't need to be along with the version 3.0.0 release).
I'm so eager to get the new version out, I'd rather push off all features until later unless they need to be in 3.0.0
I'll keep the issue open. Do let me know if there's good reason to get it in with 3.0.0 rather than later.

🤔 I'm still unsure what the benefit is ... I'm not really eager to add this feature 😓
I'm thinking of closing this -- please let me know if there's some important benefit I'm not seeing 🤝

Without this change, if files are imported as they're being downloaded (say you download directly to your video hub folder), VHA will import it as is, and will generate incorrect thumbnails, if it even can.
With this change, a new scan of the hub will detect that the video has been updated again (since fully downloading), and should reimport the thumbnails as it has a new hash now! 🎉
stats.blocks is the number of actual file system blocks used to store the file, which increases as the file grows. For speed, most file systems only allocate the blocks when needed, so a 1GB file might actually only be 1MB on disk, if only 1MB has been written to the file. In this case, stats.blocks will be a much lower number than a truly 1GB file.
Including this into the hash calculation will allow these changes to be detected by VHA.

I feel like it would take a lot of careful edge-case detection to implement. At the moment, I'm preventing the app from re-scanning files that have already been added to the app (for example: https://github.com/whyboris/Video-Hub-App/blob/main/node/main-extract-async.ts#L253)
If we attempt to re-scan files that have already been added, we'll need to run a stat command across every file is the library (it's over 9000 :trollface: ) which seems wasteful for the potential that some user might have pointed their app at the download directory.
I personally feel like it's a mistake to point VHA at a downloads-in-progress folder 🤷  but I won't judge 😝
I'm reluctant to add this feature because of the re-scanning it will require. Please let me know if you think there's a way around this problem, or it's not a problem 🤔


status is-login does not work for iTerm2

changing is-login to is-interactive works for both iTerm2 and Terminal.
Background:
Installed pyenv using fisher.
fisher pyenv
Using Terminal, running python in a directory with 3.6.1 in .python-version, starts python 3.6.1. However, when I use iTerm2, same steps do not have same results. Typing python opens up the python 2.7.10 which is the default python shipped with Darwin.
Doing which python in both the pseudo terms result in different python executables too. In iTerm2
/usr/bin/python and in Terminal it goes to /Users/tdasgupt/.pyenv/shims/python.
Test:
With the above change, correct version of python is picked up from the .python-version files. env shows PATH contains PATH=/Users/tdasgupt/.pyenv/shims: in both iTerm2 and Terminal. which python goes to /Users/tdasgupt/.pyenv/shims/python for both.
Not tested:
Any scenarios that is dependent on status is-login check in pyenv/conf.d/pyenv.fish. Also any scenario that will double execute this script so as to add the shim path despite it being added. Not sure how to reproduce such a scenario. If such a case exists, probably need to change to check if path has pyenv/shim before adding.

You should configure iTerm2 to use login sessions for your shell. If not, it won't do certain actions that are part of 'login', like setting up your PATH. This is normally the case when you leave the Command option on Login Shell in iTerm2's preferences (General) and properly set the shell for your user by running a chsh -s /path/to/shell.

Crap, didn't meant to hit the Close button just yet, sorry about that.


how to authenticate with Docker hub in order to pull the private repo

Hi There,
I am wondering how to handle the Docker hub authentication in order to pull the private docker image? I don't see it in the document but only the authentication for the private registry. Thanks.
ymote

This will probably help you :)
https://github.com/apocas/dockerode/issues/120

Thanks. Might be a good idea to include it in the readme :-)

Wanna throw an example file in the examples folder with this? :)

I guess ...
the problem might be coming from docker-medom
https://github.com/apocas/docker-modem/blob/master/lib/modem.js#L112
https://docs.docker.com/reference/api/docker_remote_api/
docker registry need
> xx.toString("base64")
'eyJ1c2VybmFtZSI6ICJzdHJpbmciLCAicGFzc3dvcmQiOiAic3RyaW5nIiwgImVtYWlsIjogInN0cmluZyIsICJzZXJ2ZXJhZGRyZXNzIiA6ICJzdHJpbmciLCAiYXV0aCI6ICIifQ=='
> xx.toString()
'{"username": "string", "password": "string", "email": "string", "serveraddress" : "string", "auth": ""}'

If we send the object as options.authconfig ...
We will get ...
> yy = {"username": "string", "password": "string", "email": "string", "serveraddress" : "string", "auth": ""}
{ username: 'string',
  password: 'string',
  email: 'string',
  serveraddress: 'string',
  auth: '' }
> new Buffer(JSON.stringify(yy)).toString("base64")
'eyJ1c2VybmFtZSI6InN0cmluZyIsInBhc3N3b3JkIjoic3RyaW5nIiwiZW1haWwiOiJzdHJpbmciLCJzZXJ2ZXJhZGRyZXNzIjoic3RyaW5nIiwiYXV0aCI6IiJ9'
> JSON.stringify(yy)
'{"username":"string","password":"string","email":"string","serveraddress":"string","auth":""}'
>

What problem @c3h3 ? :)
Read https://github.com/apocas/dockerode/issues/120
It's a matter of auth object format and documentation lacking about this, I will put something on the readme.md about this later.

:+1:  would like to see this in the documentation.

https://github.com/apocas/dockerode#pull-from-private-repos