Deployment fails with stemcell ubuntu-trusty version 3363.9

Our latest deployment in Softlayer tried using the newest ubuntu-trusty stemcell version 3363.9 and failed with the error
CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID '5285bda5-41d6-44d6-bb5c-db06ae7aff4d': Updating VM's agent env: Updating Agent Env timeout. : Upload to "/var/vcap/bosh/user_data.json" failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain' in 'create_vm' CPI method

Do we have to change something in the Cloud Config with this new stemcell version?
Help is appreciated. Thanks,
Peter
Full deployment log here:
Deploying
---------

Director task 6860
  Started preparing deployment > Preparing deployment. Done (00:00:01)

  Started preparing package compilation > Finding packages to compile. Done (00:00:00)

  Started compiling packages
  Started compiling packages > nginx/1c8867c98ccd77c9f8d5509ec8e6993681125bf3
  Started compiling packages > bits-common/31323f35fea0d06665c3ffdd9019605655cdcb99
  Started compiling packages > ruby-2.3/af291eea8a7bf463720143128a1f25a7b6e9f56c
  Started compiling packages > yajl/0508cba03499f6efc467759285a1ef8b34838450
  Started compiling packages > python/484075d81d41ce3985fa299004a82d96c9a24aa7
   Failed compiling packages > ruby-2.3/af291eea8a7bf463720143128a1f25a7b6e9f56c: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID '5285bda5-41d6-44d6-bb5c-db06ae7aff4d': Updating VM's agent env: Updating Agent Env timeout. : Upload to "/var/vcap/bosh/user_data.json" failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain' in 'create_vm' CPI method (00:11:36)
   Failed compiling packages > nginx/1c8867c98ccd77c9f8d5509ec8e6993681125bf3: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID '1cdc9ebb-a866-448d-bde6-d45b035d3296': Updating VM's agent env: Updating Agent Env timeout. : Upload to "/var/vcap/bosh/user_data.json" failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain' in 'create_vm' CPI method (00:11:43)
   Failed compiling packages > yajl/0508cba03499f6efc467759285a1ef8b34838450: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID '041d1de8-87fb-48b4-8a3e-7e15eec40c2f': Updating VM's agent env: Updating Agent Env timeout. : Upload to "/var/vcap/bosh/user_data.json" failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain' in 'create_vm' CPI method (00:11:47)
   Failed compiling packages > python/484075d81d41ce3985fa299004a82d96c9a24aa7: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID '71e9a0a5-4e7a-4608-b980-cea1f005a8ca': Updating VM's agent env: Updating Agent Env timeout. : Upload to "/var/vcap/bosh/user_data.json" failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain' in 'create_vm' CPI method (00:11:48)
   Failed compiling packages > bits-common/31323f35fea0d06665c3ffdd9019605655cdcb99: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID '1d6be408-c678-48f4-b480-1193073d1b25': Updating VM's agent env: Updating Agent Env timeout. : Upload to "/var/vcap/bosh/user_data.json" failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain' in 'create_vm' CPI method (00:13:37)

Error 100: CPI error 'Bosh::Clouds::CloudError' with message 'Creating Virtual_Guest with agent ID '5285bda5-41d6-44d6-bb5c-db06ae7aff4d': Updating VM's agent env: Updating Agent Env timeout. : Upload to "/var/vcap/bosh/user_data.json" failed: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain' in 'create_vm' CPI method

Task 6860 error

For a more detailed error report, run: bosh task 6860 --debug
command 'bosh -n --color -t https://<IP_ADDRESS> -d /tmp/bosh_manifest20170315-6-oswicm deploy --no-redact' failed!

/cc @suhlig @smoser-ibm

Is #131 related to this issue?

@gu-bin have we tested stemcell version 3363.9 with our pipeline? Did not see this.
/cc @mattcui @zhanggbj

Yes, It's a known problem with the stemcell 3363.9, but since the sha1 can't be overridden on bosh.io once it's already uploaded, we can't upload the good stemcell there. In addition, we are still working on the new pipeline for building the stemcell for catching up the community. In the meantime, you could try with the stemcell below, please let us know if you meet any problem. Thanks.
https://s3.amazonaws.com/bosh-softlayer-stemcells-candidate-container/light-bosh-stemcell-3363.12-softlayer-xen-ubuntu-trusty-go_agent.tgz

In the meantime, you could try with the stemcell below, please let us know if you meet any problem. Thanks.
https://s3.amazonaws.com/bosh-softlayer-stemcells-candidate-container/light-bosh-stemcell-3363.12-softlayer-xen-ubuntu-trusty-go_agent.tgz

@mattcui That's not really a viable option, because we're using concourse's stemcell resource. For the time being we're using the old stemcell version.
Can you add information to the broken stemcell version on bosh.io to make it obvious that there is an issue? It took me several hours to find out that it's the stemcell and not something else.

@petergtz  I totally agree, and sorry for wasting your time. @jianqiu tomorrow it's your last day working in Pivotal, possible to talk to the pair chair (or some senior guy there) to see if it's possible to fix this issue, or if it's possible to add some warning messages there at least? Thanks.
/cc @maximilien

@petergtz We have a new stemcell 3363.12.1 published on bosh.io. Please note that there requires to to add keep_root_password property under resouce_pool due to a change in bosh-agent, you could reference the sample docs/sl-bosh.yml

@mattcui How do I specify keep_root_password: true in v2 manifests? Is the property under instance_groups? Thanks.

@valeriap Yes, I think so.

@valeriap Maybe I'm missing something, but aren't you confusing the deployment manifest with a bosh director manifest? docs/sl-bosh.yml is a sample manifest to deploy a bosh director. Hence, there's no Cloud Config to update.
@mattcui Thanks for the update. We'll this one as soon as possible.

@petergtz Since the property is used by the bosh agent I supposed the change to be needed on each deployment, not specifically on the bosh director deployment. Am I wrong?

@valeriap No idea. @mattcui?

@mattcui Would it make sense to update the cloud_config.yml template to make it clear then?
Also, you wrote you "think" it has to be defined there. Does that mean it is unclear at this point?

@petergtz I am working on this these days, just submitted PR 55, you or @valeriap could reference cpi.yml and cloud-config.yml in  softlayer. The property keep_root_password has to be defined under instance_groups, reference -> concourse_sample_v2_schema.yml


test: add empty test for client/server rpc implementation

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 48.68%. Comparing base (d392733) to head (652efa7).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #190   +/-   ##
=======================================
  Coverage   48.68%   48.68%
=======================================
  Files          23       23
  Lines         910      910
  Branches      910      910
=======================================
  Hits          443      443
  Misses        446      446
  Partials       21       21

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Create Spanish (Spain)

Added Spanish from Spain for version 3.0.0.
I make this PR to development-v3 as discussed on #113

Thanks! I renamed the file to have the .txt extension and then I created a Python script to package translations. Installing a translation package should be as simple as copying the contents of the zip archive into the skin's folder.

Ups, sorry about that :sweat_smile: Perfect! Thanks you!!


【ERROR】Unable to pub upgrade flutter tool. Retrying in five seconds...

ubuntu 17.04

环境搭建遇到错误
git clone -b alpha https://github.com/flutter/flutter.git

evanyan@ps:~$ flutter doctor
Building flutter tool...
The setter 'readEventsEnabled=' was called on null.
 Please run

    pub --trace upgrade --verbosity=error --no-packages-dir

and include the logs in an issue on https://github.com/dart-lang/pub/issues/new
Error: Unable to pub upgrade flutter tool. Retrying in five seconds...

Presumably this is an access error to pub.dartlang.org which is causing a cascading failure?  Which means there are several things wrong.  @mit-mit

i have a problem,please help!
junludeMBP:~ Javen$ flutter doctor
Building flutter tool...
Got socket error trying to find package coverage at https://pub.dartlang.org.
Error: Unable to pub upgrade flutter tool. Retrying in five seconds...
Connection failed (OS Error: No route to host, errno = 65), address = storage.googleapis.com, port = 443
Error: Unable to pub upgrade flutter tool. Retrying in five seconds...
@eseidelGoogle
thank you very much

If you're in China, please try https://github.com/flutter/flutter/wiki/Using-Flutter-in-China and let us know if that doesn't work.

Thanks! it works! @eseidelGoogle

still get the error when i
export PUB_HOSTED_URL=https://pub.flutter-io.cn
export FLUTTER_STORAGE_BASE_URL=https://storage.flutter-io.cn
then i run the example of hello_world
Running "flutter packages get" in hello_world...

ERR : Connection failed (OS Error: No route to host, errno = 65), address = storage.googleapis.com, port = 443
that will make me give up .......

@linguowu Can you run the default app created by flutter create?

@InMatrix
when i run "flutter create myapp"
it shows below:

Running "flutter packages get" in myapp...
Got socket error trying to find package cupertino_icons at https://pub.dartlang.org.

@linguowu It looks like the environmental variables were not working. Can you provide the following information for diagnostic purposes:

output of echo $PUB_HOSTED_URL
output of echo $FLUTTER_STORAGE_BASE_URL
output of ls ~/.pub-cache/hosted
output of flutter doctor -v

Also, did you use the mirror to install Flutter?
Thank you for your patience.

@InMatrix
how to get the mirror to install Flutter?
below is the output for diagnostic:
`country5deMacBook-Pro-2:~ country5$ echo $PUB_HOSTED_URL
country5deMacBook-Pro-2:~ country5$ echo $FLUTTER_STORAGE_BASE_URL
country5deMacBook-Pro-2:~ country5$ ls ~/.pub-cache/hosted
pub.dartlang.org pub.flutter-io.cn
country5deMacBook-Pro-2:~ country5$ flutter doctor -v
[  +14 ms] [/Users/country5/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +28 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/alpha
[        ] [/Users/country5/flutter/] git rev-parse --abbrev-ref HEAD
[   +8 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] alpha
[        ] [/Users/country5/flutter/] git ls-remote --get-url origin
[   +8 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[        ] [/Users/country5/flutter/] git log -n 1 --pretty=format:%H
[   +6 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] 2e449f06f0a3be076e336ad6b30b0e9ec99dbdfe
[        ] [/Users/country5/flutter/] git log -n 1 --pretty=format:%ar
[   +6 ms] Exit code 0 from: git log -n 1 --pretty=format:%ar
[        ] 9 days ago
[        ] [/Users/country5/flutter/] git describe --match v*.. --first-parent --long --tags
[   +7 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[        ] v0.0.21-0-g2e449f0
[ +135 ms] /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info CFBundleShortVersionString
[  +61 ms] Exit code 0 from: /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info CFBundleShortVersionString
[        ] 3.0
[ +129 ms] [✓] Flutter (on Mac OS X 10.12 16A323, locale zh-Hans-CN, channel alpha)
[        ]     • Flutter version 0.0.21 at /Users/country5/flutter
[        ]     • Framework revision 2e449f06f0 (9 days ago), 2018-01-29 14:26:51 -0800
[        ]     • Engine revision 6921873c71
[        ]     • Tools Dart version 2.0.0-dev.16.0
[        ]     • Engine Dart version 2.0.0-edge.da1f52592ef73fe3afa485385cb995b9aec0181a
[   +6 ms] /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info CFBundleShortVersionString
[  +59 ms] Exit code 0 from: /usr/bin/defaults read /Applications/Android Studio.app/Contents/Info CFBundleShortVersionString
[        ] 3.0
[  +64 ms] java -version
[  +63 ms] [✓] Android toolchain - develop for Android devices (Android SDK 26.0.2)
[        ]     • Android SDK at /Users/country5/Development/android-sdk-macosx
[        ]     • Android NDK at /Users/country5/Development/android-sdk-macosx/ndk-bundle
[        ]     • Platform android-26, build-tools 26.0.2
[        ]     • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
[        ]     • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)
[  +99 ms] DevToolsSecurity -status
[  +31 ms] Developer mode is currently enabled.
[        ] python -c import six
[  +35 ms] idevice_id -h
[   +6 ms] idevice_id -h
[   +4 ms] idevice_id -l
[  +14 ms] ideviceinstaller -h
[   +6 ms] ios-deploy --version
[  +11 ms] ios-deploy --version
[   +9 ms] 1.9.2
[        ] ios-deploy --version
[   +8 ms] ios-deploy --version
[  +10 ms] 1.9.2
[   +1 ms] pod --version
[ +276 ms] pod --version
[ +276 ms] 1.3.1
[   +1 ms] pod --version
[ +267 ms] 1.3.1
[        ] [-] iOS toolchain - develop for iOS devices (Xcode 8.0)
[        ]     • Xcode at /Applications/Xcode.app/Contents/Developer
[        ]     • Xcode 8.0, Build version 8A218a
[        ]     ✗ Flutter requires a minimum Xcode version of 9.0.0.
Download the latest version or update via the Mac App Store.
[        ]     • ios-deploy 1.9.2
[        ]     • CocoaPods version 1.3.1
[   +1 ms] [✓] Android Studio (version 3.0)
[        ]     • Android Studio at /Applications/Android Studio.app/Contents
[        ]     • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)
[  +21 ms] /Users/country5/Development/android-sdk-macosx/platform-tools/adb devices -l
[  +13 ms] Exit code 0 from: /Users/country5/Development/android-sdk-macosx/platform-tools/adb devices -l
[        ] List of devices attached
ENU7N15A30000390       device usb:337641472X product:angler model:Nexus_6P device:angler transport_id:2
[   +7 ms] idevice_id -h
[  +18 ms] /Users/country5/Development/android-sdk-macosx/platform-tools/adb -s ENU7N15A30000390 shell getprop
[  +64 ms] ro.hardware = angler
[        ] ro.build.characteristics = nosdcard
[   +2 ms] [✓] Connected devices
[        ]     • Nexus 6P • ENU7N15A30000390 • android-arm • Android 8.1.0 (API 27)
[  +14 ms] "flutter doctor" took 1,664ms.
[ +100 ms] ensureAnalyticsSent: 98ms
[   +2 ms] exiting with code 0`

@linguowu given the output of the ECHO commands you have is empty it looks like those variable were not correctly exported/set. You need to make sure they are set before running the flutter command. See https://github.com/flutter/flutter/wiki/Using-Flutter-in-China for details.

@linguowu In addition to what @mit-mit said, you can persist these environment variables by adding these export commands to $HOME/.bash_profile and then source $HOME/.bash_profile.

checkout fluter by this way : https://github.com/flutter/flutter/wiki/Using-Flutter-in-China
2 .then try to excute : C:\flutterdev\flutter\bin\flutter.bat
i sovled my problem

hi
go to the bios and change vm (Virtual machine) from disable to enable. you want to run emulator so its Necessary.


Page with business cases

As a requirement of the website,  we need to add a long description of possible use cases

added use cases to the project website
/cc @iFetch-chatbot/farfetch-ifetch-team


Porch: ssh auth support

Describe your problem
When using Porch, I can register a repository with basic auth or workload identity. The basic auth can be used with GitHub personal access tokens. However, those tokens are highly priviliged - so much so that for my testing I created a new, separate GitHub user.
Instead, if we can support ssh auth, then I should be able to use a deploy key, which is scoped to an individual repository.
Not a blocker at this time but will be needed as we move towards something that folks could use in prod.

We do have a broader issue about supporting additional auth schemes for working with git providers: https://github.com/GoogleContainerTools/kpt/issues/3232

Duplicate


Glimpse shouldn't scan all assemblies for types on startup

Currently, Glimpse contributes about 10s to the warmup time of my app.
This is because the Glimpse module's Init function goes and inspects all types of all assemblies, probably even multiple times.
This has already been discussed years ago in a now closed issue.
The issue was closed because it was anticipated that a version 2 of Glimpse could afford a breaking change in the type location convention.
The workaround suggested by nikmd23 at the time - implementing a custom ServiceLocator - has become more difficult as apparently the types in question are no longer default-contructible as claimed.
I noticed when I tried doing just that.
This issue is years old, there's still no version 2.
I think 10s warmup for Glimpse alone is very problematic, especially when it's unexpected.
Also, when Glimpse is turned off (defaultRuntimePolicy="off"), it still searches the assemblies.

In v1, setting defaultRuntimePolicy="off" will still execute the logic on startup. It does this because its looking through other providers that can we at play to see what it should do. Have you tried setting the discoveryLocation to narrow things down?

Put any DLL's that contain Glimpse extensions (like Glimpse.Mvc* or Glimpse.Ef*) in a separate directory inside of bin. Then point the  attribute in web.config at the directory. This will reduce the reflection that Glimpse is doing to just the assemblies that actually contain Glimpse extensions.

Well, yes, but this isn't really a help-desk-type post. I just wanted to remind the relevant people that there's a genuine issue.
So far I'm happy with commenting out Glimpse in development until I need it and never deploy it on production.

At the moment in a case like yours I agree with your decision. At the moment 100% of our energy is being put into v2, which will in time hopefully address the specific problem you have. If you would like to submit a PR to fix this issue we can see about pulling it in. If you where interested in this, I would probably look at allowing you to manually specify the types that you want loaded in the web.config the same way that you can specify which types to ignore.


The documentation's description of TEMPLATE_CONTEXT_PROCESSORS is out-of-date for Django >= 1.8

In the documentation settings section, the usage of TEMPLATE_CONTEXT_PROCESSORS is no longer current as of Django 1.8 (1.7, 1.9, upgrade guide) and the location of the context_processors module has moved. It would be nice to clarify to users the appropriate method for their version.

Hi. Would this PR clarify the situation?
https://github.com/rossp/django-helpdesk/compare/master...mrkiwi-nz:patch-2#diff-f47f8ca652dac550c8bc9d449ca0d253

I'd think so, thanks!

@mrkiwi-nz Your PR shows no differences, however https://github.com/django-helpdesk/django-helpdesk/blob/0d8e81d7f0cb706b59715fc502b37173b9935aaa/docs/settings.rst still shows the deprecated use of TEMPLATE_CONTEXT_PROCESSORS. Could you open a PR with the proper branch please?


Explanation not sufficient, missing steps

Hi there,
I'm trying to create a canvas app where I can upload an image or take a photo and it's using my custom vision model to classify it.
I was pointed to the Power Fx documentation by a colleague, but I just wanted to give feedback, that it is not possible to implement it with the documentation. (I'm working as a CSA, so kind of stepping in the shoes of a customer here)
It's great that you put an animation in the end of exactly the use case that I am looking into, but instead of showing just the solution it would be great to see the steps necessary to implement it. This shouldn't be a marketing slide, but a documentation of how to properly use the functionality.
This is not useful for our customers!
Thanks,
Nadja
[Enter feedback here]

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

ID: cc82aee7-7245-42a3-41e9-a8d2aa3eed19
Version Independent ID: cc82aee7-7245-42a3-41e9-a8d2aa3eed19
Content: Use image classification model by Lobe in Power Apps (preview) - AI Builder
Content Source: ai-builder-docs/image-classification-component-in-powerapps.md
Service: aibuilder
GitHub Login: @mbeissinger
Microsoft Alias: mabeis

@nadjaklein - Thanks for your feedback. We will soon look into this issue regarding https://docs.microsoft.com/en-us/ai-builder/image-classification-component-in-powerapps.

@nadjaklein - Thanks for your feedback. This feature is planned to be updated in June. We will update the documentation at that time. Closing this issue.


add environment type as a parameter on apply. Seems more meanifull th…

…an duplicating it into the env.properties. Currently the /env.properties gets resolved but we always run with default env.type

Last week I added ability to pass extra parameters via -Dapply.params="environment.type=custom foo=bar" via a new sagenvInit2. I don't like it much but I really needed it. I'd like to have ability to pass-through any params like this
ant up -Denvironment.type=foo -Dbar=baz

What is the semantic difference between env and Environment type?
I was thinking that both are referencing the section under environment: in the yaml, so that what I give in
dev/
env.properties
will get resolved in
environment:
dev:
foo: ${}

additionally create a dev env folder and property file and the putting environment.type=dev inside and the trigger all with -Denv=dev looks a bit too much.


adding the .offset() and the .position() functions

Hi @jgermade ,
is it possible to add the adding the .offset() and the .position() functions to jqlite?
Thanks in advance!

Ok, looks good. I'll work on this soon

awesome @jgermade !
can't wait!

Hi @RongBranovate , I'm still working on this, I want to ensure cross-browser compatibility

Ok, awesome, let me know as soon as it's ready :+1:

Hi @RongBranovate jqlite v0.2.7 includes offset and position functions!
thanks a lot for your feedback!!

Thanks! awesome!


Add pruned RNN-T for aishell.

Using aidatatang_200zh as extra training data.

Cool.  So --avg 5 was the optimum?  Seems lower than normal.  It's OK that the WER is a tiny fraction worse, we could do better by having more epochs, probably, but let's get in the habit of not doing that, to save time.  What is context-length?

Cool. So --avg 5 was the optimum?

Yes.
The model was first trained for 30 epochs and then it was resumed and was trained for another 10 epochs.
You see that it improves only a bit, so I choose epoch 29 avg 5
(py38) kuangfangjun:modified_beam_search$ grep -r -n --color "best for test" log-* | sort -n -k2 | head -n10
log-decode-epoch-35-avg-5-modified_beam_search-beam-size-4-use-averaged-model-2022-06-20-16-31-42:19:beam_size_4        5.03    best for test
log-decode-epoch-29-avg-5-modified_beam_search-beam-size-4-use-averaged-model-2022-06-19-12-31-39:19:beam_size_4        5.05    best for test
log-decode-epoch-35-avg-6-modified_beam_search-beam-size-4-use-averaged-model-2022-06-20-16-49-49:19:beam_size_4        5.05    best for test
log-decode-epoch-38-avg-3-modified_beam_search-beam-size-4-use-averaged-model-2022-06-20-11-06-48:19:beam_size_4        5.05    best for test
log-decode-epoch-35-avg-4-modified_beam_search-beam-size-4-use-averaged-model-2022-06-20-16-15-29:19:beam_size_4        5.06    best for test
log-decode-epoch-35-avg-7-modified_beam_search-beam-size-4-use-averaged-model-2022-06-20-17-08-39:19:beam_size_4        5.06    best for test
log-decode-epoch-38-avg-4-modified_beam_search-beam-size-4-use-averaged-model-2022-06-20-11-21-57:19:beam_size_4        5.06    best for test
log-decode-epoch-39-avg-4-modified_beam_search-beam-size-4-use-averaged-model-2022-06-20-07-57-35:19:beam_size_4        5.06    best for test
log-decode-epoch-29-avg-4-modified_beam_search-beam-size-4-use-averaged-model-2022-06-19-12-13-36:19:beam_size_4        5.07    best for test
log-decode-epoch-29-avg-6-modified_beam_search-beam-size-4-use-averaged-model-2022-06-19-12-49-41:19:beam_size_4        5.1     best for test

Cool.
For new experiment directories, can we use that change that Zengwei tested, where the linear layers in the RandomCombine module are removed?

I anticipate the difference will be smaller for larger-data setups.

Yes, I believe so. The wenetspeech recipe is using context size 2, I think.

I anticipate the difference will be smaller for larger-data setups.

Sure.


Bug : 1251066 - link updated.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Web-Apps-Server-loc/configure-office-web-apps-for-sharepoint-2013.md
:white_check_mark:Succeeded

Web-Apps-Server-loc/content-roadmap-for-office-web-apps-server.md
:white_check_mark:Succeeded

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

Closing PR without merging as issue has been fixed


combo content detaches when scrolling the window via mousewheel

create so much ui that you get a scrollable window
create a zui.combo element
click the combo to open it
scroll via mousewheel
the combo scrolls up correctly, but it's content stays in place where it was opened

It looks like nowadays window scroll is blocked while combo is opened, so perhaps this is no longer an issue.

With Zui.alwaysRedraw = true; it still won't work. But i need that flag enabled to update counter displays and such.

Aha yes, I see it now, thanks for info!

fixed in af2371a733da3dc788374f18b9c8b3fd4f81d0cc


Firecert 2525

 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.7 out of 9 committers have signed the CLA.:white_check_mark: PreethiMaai:white_check_mark: anjalimukundan:white_check_mark: Abhishk123:white_check_mark: Nandana-NNR:white_check_mark: bpvstaty366:white_check_mark: ksentak:white_check_mark: Roebot926:x: jbigel:x: semantic-release-botjbigel 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.

b'## Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/firebolt-certification-suite/270/rdkcentral/firebolt-certification-suite

Commit: 2965d2d5d9d7f26855ff628c6d05ed8fb1b884c3

Report detail: gist'


[URGENT] Auto-check for secret keys!

Create tool to automatically scan repo for secret keys etc (make it generalized to all types, like GitHub ones, api keys, etc.). And have it be something I can run at command line and also something I can run during merging any branch for GitHub actions. It will throw an error that emails me every time something is found (if ran by github actions, not for command line). Test it with fake api keys. Have it search every single file I have. Maybe it could even prevent merges if it’s found in github actions?
Check to see if this already exists before making it custom! GitHib may do this by default? Or have an API I can call from actions? https://docs.github.com/en/code-security/secret-scanning/about-secret-scanning
Enabling it in settings? May not need a tool actually: https://docs.github.com/en/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories

Turns out this is already enabled in this repo in the security settings to notify me and block merged with keys


Issue 408: ARMA and ARIMA models

This draft PR closes #408 and starts towards adding submodels everywhere. To close this out I need to:

[ ] Remove all standard deviation priors from latent models
[ ] Use HierarchicalNormal as the default residual process
[ ] Decide if we need helper constructors for our current models (i.e do we want AR(std_prior)) to work)
[ ] Write arma and arima helper functions. Deciding how much flexibility to expose (plan is to restrict to just p,q,r priors and the standard deviation prior of the residuals).
[ ] Review and improve tests

Hey do you need any help with this one?

no its okay I just need to get off primarycensoreddist and then can get this unstuck

Seeing updates 👍

ha yes this PR has got really out of hand - just doing some lsthm admin stuff then back on this

I see the new define_ syntax being used for the arma and arima constructors. Noting we want to keep the same approach as used elsewhere (i.e. https://github.com/CDCgov/Rt-without-renewal/blob/ae73647df65fb9970e8a8a08e0783a30f7f57863/EpiAware/src/EpiLatentModels/manipulators/broadcast/helpers.jl#L13 so we don't introduce to many interface ideas.

Based on the benchmarks this looks like its quite a lot slower for all low-level models (and dependent benchmarks) in all cases except where compiled reverse diff is used. I think that is probably just the cost of dispatching through the multiple new submodel calls vs specifying the iid process directly and so somewhat unavoidable if we want this functionality (which I think we do)

Note that I can't run the notebooks locally for some reason (they just hang forever) so debugging those has been fun.

Note that I can't run the notebooks locally for some reason (they just hang forever) so debugging those has been fun.

I'll have a peek

Note that I can't run the notebooks locally for some reason (they just hang forever) so debugging those has been fun.

The new AR process changed the order of parameters which put the fixed "initial guess" for the more complicated example in Chatzilena replication in a very bad place causing NaNs to get passed. I've pushed a fix that works locally.

Ah great nice fix. Yes that isn't ideal at all

I put in some control code and reduced the broadcasting in HierarchicalNormal which seems to have marginally helped the performance regressions

@SamuelBrand1 any chance you can get to this today?

Based on the benchmarks this looks like its quite a lot slower for all low-level models (and dependent benchmarks) in all cases except where compiled reverse diff is used. I think that is probably just the cost of dispatching through the multiple new submodel calls vs specifying the iid process directly and so somewhat unavoidable if we want this functionality (which I think we do)

This seems possible. I've spotted some places we could have tried a parameteric dispatch e.g. have a method where the $\epsilon_t$ field of IID being a concrete Normal type dispatches to using MvNormal

**My only blocker to merging is that I'm not sure that https://github.com/CDCgov/Rt-without-renewal/issues/440 is addressed, which was part of the plan (cf https://github.com/CDCgov/Rt-without-renewal/pull/441). I don't think thats a major lift (it might already be addressed but I'm not sure). Otherwise, just some comments that look like future issues.
**

So my understanding was that this PR blocked #441 but wasn't trying to address #440 (hence not doing so). If you agree I think we should widen the scope of #440 to all parameters of this kind ot make sure they are in the order people might expect.

**My only blocker to merging is that I'm not sure that #440 is addressed, which was part of the plan (cf #441). I don't think thats a major lift (it might already be addressed but I'm not sure). Otherwise, just some comments that look like future issues.
**

So my understanding was that this PR blocked #441 but wasn't trying to address #440 (hence not doing so). If you agree I think we should widen the scope of #440 to all parameters of this kind ot make sure they are in the order people might expect.

I'm happy with this sequence.


Vim9: cannot use "system()" without "{input}" optional argument

Describe the bug
In Vim9 script, we cannot use system() to start an external process, without the optional argument {input}.
To Reproduce
Run this shell command:
vim -Nu NONE +'vim9 system(":")'

E1224 is given:
E1224: String or List required for argument 2

Expected behavior
No error is given, because we didn't pass the 2nd optional argument.
Environment

Vim version: 8.2 Included patches: 1-3229
OS: Ubuntu 20.04.2 LTS
Terminal: XTerm(353)

Additional context
Regression introduced in 8.2.3229.

Same issue with systemlist():
vim9script
systemlist(':')

E1224: String or List required for argument 2

cc @yegappan via https://github.com/vim/vim/pull/8646

Hi,
On Tue, Jul 27, 2021 at 1:24 PM lacygoill @.***> wrote:

Describe the bug
In Vim9 script, we cannot use system() to start an external process,
without the optional argument {input}.
To Reproduce
Run this shell command:
vim -Nu NONE +'vim9 system(":")'
E1224 is given:
E1224: String or List required for argument 2
Expected behavior
No error is given, because we didn't pass the 2nd optional argument.
Environment

Vim version: 8.2 Included patches: 1-3229
OS: Ubuntu 20.04.2 LTS
Terminal: XTerm(353)

Additional context
Regression introduced in 8.2.3229.
Same issue with systemlist():
vim9scriptsystemlist(':')
E1224: String or List required for argument 2

cc @yegappan https://github.com/yegappan via #8646
https://github.com/vim/vim/pull/8646

Thanks for reporting the issue. I have created PR #8651 with
a fix for this. Let me know if you see any other issues with other
functions.

Yegappan


react-scripts@5 BROWSER in .env file is not working

Describe the bug
With react-scripts@5 BROWSER is not working when placed in an .env file (I'm using .env.local in this case)
i.e. BROWSER=msedge used to work with react-scripts@4, with v5 this is ignored and the default browser opens
Did you try recovering your dependencies?

Node version: 16.13.2
NPM version: 8.3.1
Which terms did you search for in User Guide?

Following guide here: https://create-react-app.dev/docs/advanced-configuration/
Environment

Environment Info:
current version of create-react-app: 5.0.0
running from C:\Users[username]\scoop\persist\nodejs-lts\cache_npx\c67e74de0542c87c\node_modules\create-react-app
System:
OS: Windows 10 10.0.19044
CPU: (12) x64 Intel(R) Xeon(R) E-2176M  CPU @ 2.70GHz
Binaries:
Node: 16.13.2 - ~\scoop\apps\nodejs-lts\current\node.EXE
Yarn: Not Found
npm: 8.3.1 - ~\scoop\apps\nodejs-lts\current\bin\npm.CMD
Browsers:
Chrome: 97.0.4692.71
Edge: Spartan (44.19041.1266.0), Chromium (97.0.1072.62)
Internet Explorer: Not Found
npmPackages:
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
react-scripts: 5.0.0 => 5.0.0
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce

set BROWSER in .env.local file
npm start

Expected behavior

Specified browser opens
Actual behavior

System default browser opens, not as specified above

same thing happened to me.

Same Issue on "react-scripts": "4.0.3"

Still!!!

Same..

on windows, the only value that works is BROWSER=none. all others open default system browser due to invalid usage of open library after breaking changes in v8
this PR https://github.com/facebook/create-react-app/pull/11878 would fix it, not sure why it's still not merged.


Autocomplete list not displayed on component click

Upon clicking the component to select an entity, the view is not displayed correctly
Steps to reproduce the behavior:

Go to 'https://function-adminportal-test.shesha.dev/dynamic/shesha/forms'
Click on 'Create New' button
Click on 'Module'
See the way the component renders the view
Actual Results: The component does not display the list view as expected

Expected behavior
Upon clicking the component to select an entity, the view should be displayed correctly to allow users to select an entity
03a7cebf-bf53-4616-9987-585a3061092b.webm

Possible PR that affected the list UI: https://github.com/shesha-io/shesha-framework/pull/1926

Hi @hlayisanimazuze. It's fixed, please check


it changes the table view frame

I can not scroll to the  bottom to see the last cell after it ends

@Liqiankun Hello! Thanks for your report. Can you give me a more details about your issue?

@SerjOxo I will let u know!


Adding an update command to be able to check for new OCI images

Add a command to update all existing commands:
cpm update
This command checks if there are new image tags for all existing command. If there is a new tag, the command would update the reference and pull the new image.
Be able to check for updates on specific commands:
cpm update <command>
This command checks if there is a new image tag for the given command. If there is a new tag, the command would update the reference and pull the new image.

Implemented by #20


add support for using request header values

This PR allows rules to have access to request headers.

@jkotalik / @Tratcher could you guys review?

@jkotalik @Tratcher i should have some time to look at this tomorrow. thanks

Thanks @davidpeden3 for the PR. Closing this as there's no recent activity.
Please file a bug if you'd like to bring this back in.


licence conflict

Hi falkx,
Licence of DPF/dgl/src/resources/blender_icons.svg (inside the file itself) mention that :"This content is under CC Attribution-NonCommercial ShareAlike licence 3.0 as long as it's used for Blender 3D GUI. Any other uses are not allowed." but the file "LICENSE-blender_icons.svg.txt" says it's GPL2.
Certainly a boring licensing stuff but I thought you might want to know about this.

I think that's fine.
GPL doesn't really apply to artwork so a CC license is inside the svg file.
The text file references the license for usage in code.
That's how I understand it anyway.

Thanks for your answer.
Anyway, before you answered, I've been making a package after removing this file and the .png one as well. It doesn't look to affect anything on the GUI.
I've been testing the stand alone version:

The LADSPA and the LV2 version in Ardour (4.4):

And the LADSPA, VST, DSSI and LV2 version in qtractor:

Everything looks fine and working as expected.
I'm closing the issue then.

the png is already converted to binary.
even if you delete the file, the code for it is still going to be embedded in the final build.
this file includes the declaration of the png: https://github.com/DISTRHO/DPF/blob/master/dgl/src/Resources.hpp
and the cpp version of that includes the actual png data.

Thanks @falkTX, after a few months without looking into this, I does work perfeclty with your help (and a careful removal inside a few different files).

FYI the GPL related files are no longer included.
My plan with DPF is to make it as free as possible, the GPL stuff is a bit much.
So now DPF is full MIT/ISC licensed again.
(dejavu font is pre-included, but that has a very liberal license too)


How NOT dismiss dialog when .onPositive(...) called?

Subject.
I have material dialog with custom view.
I have edtitext field in it.
When user press "OK", i need to check, if inpul value is wright or wrong.
And if it's wrong - dialog must not be closed.
Thanks!

Sorry, my bad.
.autoDismiss(false)


standaloneSass error

Laravel Mix Version: 1.6.0
Node Version (node -v):  v8.9.0
NPM Version (npm -v): 5.5.1
OS:

Description:
Sass Compilation Failed!

/Users/project/node_modules/node-sass/bin/node-sass:235
      if (watch.indexOf(file) === -1) {
                ^

TypeError: watch.indexOf is not a function
    at /Users/project/node_modules/node-sass/bin/node-sass:235:17
    at Array.forEach (<anonymous>)
    at handler (/Users/project/node_modules/node-sass/bin/node-sass:233:17)
    at Gaze.<anonymous> (/Users/project/node_modules/node-sass/bin/node-sass:258:5)
    at emitOne (events.js:116:13)
    at Gaze.emit (events.js:211:7)
    at Gaze.emit (/Users/project/node_modules/gaze/lib/gaze.js:128:32)
    at /Users/project/node_modules/gaze/lib/gaze.js:437:16
    at StatWatcher._pollers.(anonymous function) (/Users/project/node_modules/gaze/lib/gaze.js:345:7)
    at emitTwo (events.js:126:13)

undefined:1
/Users/project/node_modules/node-sass/bin/node-sass:235
^

SyntaxError: Unexpected token / in JSON at position 0
    at JSON.parse (<anonymous>)
    at StandaloneSass.onFail (/Users/project/node_modules/laravel-mix/src/StandaloneSass.js:149:31)
    at whenOutputIsAvailable (/Users/project/node_modules/laravel-mix/src/StandaloneSass.js:48:41)
    at Socket.command.stderr.on.output (/Users/project/node_modules/laravel-mix/src/StandaloneSass.js:108:13)
    at emitOne (events.js:116:13)
    at Socket.emit (events.js:211:7)
    at addChunk (_stream_readable.js:263:12)
    at readableAddChunk (_stream_readable.js:250:11)
    at Socket.Readable.push (_stream_readable.js:208:10)
    at Pipe.onread (net.js:594:20)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ watch: `NODE_ENV=development webpack --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      /Users/zack/.npm/_logs/2017-11-06T20_11_15_872Z-debug.log

Steps To Reproduce:
Update to latest Laravel Mix
Run npm run watch
After it compiles and loads the browser, re-save a file to trigger the error This is super important

Looks like an issue with the latest node-sass release.
https://github.com/sass/node-sass/issues/2139
I've hardcoded a safe version and have tagged 1.6.1. Try upgrading to that version, and I think it should be fixed.

@JeffreyWay That did it. Thanks!


Move API and Browser project

Move API and Browser project

@uthra22,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@uthra22,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot


Improve the usage documentation for maintainers

So some issues that I encountered when I was trying to check for spec compliance locally, that I think should be addressed to help other maintainers with their implementations.

There aren't very clear instructions on how to run everything without docker. Usually when I am testing this I am just trying to get it to run with a local instance so that I can verify the fixes that go into caliban, so I don't really want to have to deploy and run docker. There are scripts for running the user and inventory graphs, but the script for running the gateway doesn't point to a real directory (also I had to change the paths of the subgraphs because they point to dist folders that don't get built).
The testing schemas appear inconsistent, the required one is this but the one in the reference for graphql-yoga is this
There should probably be a step to have the implementation generate the schema, at the moment it is just sitting alongside the implementation but the two could be completely different.

Great feedback @paulpdaniels, thanks! We'll be working on this shortly.

Hello 👋
I've added docs on how to run local instances without docker in https://github.com/apollographql/apollo-federation-subgraph-compatibility/pull/168

The testing schemas appear inconsistent, the required one is this but the one in the reference for graphql-yoga is this

With the recent changes to the test schemas we are now run better checks to ensure that subgraph schemas are correct.

There should probably be a step to have the implementation generate the schema, at the moment it is just sitting alongside the implementation but the two could be completely different.

We compare the schemas returned form the _service { sdl } query which is used by federation. Functionality is verified by running queries testing specific features against expected data set.

We are always looking for feedback to make this repo better. Feel free to open new issue/s to better track outstanding problems. Contributions are always welcome!


[LSP]VS Code automatically prompt parameter types

After I executed the flutter upgrade yesterday, VS Code added a function to automatically prompt parameter types (yellow blocks on the figure). How can I turn this function off? This seems to be related to LSP? I really don't need this hint.Someone help me please.

flutter doctor -v:
[✓] Flutter (Channel master, 3.4.0-19.0.pre.273, on macOS 12.5 21G72 darwin-x64, locale zh-Hans-CN)
• Flutter version 3.4.0-19.0.pre.273 on channel master at /Users/hanshow/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 05e0dc2e44 (19 hours ago), 2022-09-15 03:42:24 -0400
• Engine revision 8134f565c7
• Dart version 2.19.0 (build 2.19.0-201.0.dev)
• DevTools version 2.17.0
• Pub download mirror https://pub.flutter-io.cn
• Flutter download mirror https://storage.flutter-io.cn
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/hanshow/Library/Android/sdk
• Platform android-31, build-tools 30.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 14.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Build 14A309
• CocoaPods version 1.11.2
[✓] Android Studio (version 4.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
[✓] VS Code (version 1.71.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.48.0
[✓] Connected device (1 available)
• iPhone 14 Pro Max (mobile) • E9F5DD14-1AB4-4B97-9CBA-0B234CF9D7CC • ios • com.apple.CoreSimulator.SimRuntime.iOS-16-0 (simulator)
[✓] HTTP Host Availability
• All required HTTP hosts are available

Hi @git2321231, this is a feature of vscode which was enabled by the dart SDK. You can disable this by going to your settings in vscode and disabling inlay hints.
I'll be closing this as it is not a flutter issue.
Thank you

@danagbemava-nc Thank you!

Sorry for the bother. I hadn't noticed VS Code defaulted to always showing these. I had set mine to "offUnlessPressed" (which means they only show up while Ctrl+Option is held down) while testing and assumed it was opt-in.
I'm going to override the default for Dart in the next extension update.

I've pushed a patch release of the Dart extension (v3.48.4 and pre-release v3.49.20220916) that overrides this default. Please let me know if you still see this showing up by default after installing one of those and reloading.
With the new default, they'll only show up while Ctrl+Option(Alt?) are held down.

@DanTup Yes, it works! Thanks for repairing so quickly!

Great, thanks for confirming!


For #308 : Fix error undefined stdin

IO.popen bind input and output to same object (pipe). Thus, change output to pipe for IO.popen.
=> Referenced issue: #308

I tried this, but I get an infinite loop instead. Maybe the STDERR prompting has changed in git-svn? I have searched through the git release notes without finding any obvious change to git-svn, but I might have missed something.


Extended SentimentPrediction for easier display

Extended SentimentPrediction for easier display of results
Internal Review URL
Related code sample: https://github.com/dotnet/samples/pull/832

@luisquintanilla - I believe I've addressed your changes.

Thanks, @luisquintanilla and @natke for the thoughtful feedback and time spent. Much appreciated!


List of some improvements

nav-walker.php
For accessibility purposes:
$atts['aria-current'] = $item->current ? 'page' : '';
For security:
 //$atts['rel']    = ! empty( $item->xfn ) ? $item->xfn : '';
      if ( '_blank' === $item->target && empty( $item->xfn ) ) {
				$atts['rel'] = 'noopener noreferrer';
			} else {
				$atts['rel'] = $item->xfn;
			}

Gutenberg
Missing blocks
      'core/button', //need this to add buttons inline
      'core/group',
      'core/media-text',
      'core/block',
      'core/template',

Deprecated blocks
//'core/subhead', https://developer.wordpress.org/block-editor/how-to-guides/backward-compatibility/deprecations/#3-9-0
//'core/textColumns', https://developer.wordpress.org/block-editor/how-to-guides/backward-compatibility/deprecations/#3-5-0

Lastly, missing styles for alignwide and alignfull https://www.billerickson.net/full-and-wide-alignment-in-gutenberg/

While you at code level you might as well send a PR for us to review?

Quick notes: alignwide and alignfull were there last I checked 🤔
As for the allowed_blocks. We don't want to allow them all on purpose in the starter. People who build their themes based on Air can just choose which blocks to add. The deprecated blocks need to be removed naturally soon enough.
Aria-current is excellent catch. I've often added that myself but for some reason didn't add it to the theme yet. It seems it have been added to the original component that menu is based as well. We should maybe look on the updates it has been having over the years.

Just tested out and everything working from 7.0.3 to 7.1.7. Are you sure you are running the new enough version? There has been various Gutenberg fixes from 7.0.3 like this here.
The latest is 7.1.7 released 6 minutes ago. 🙂
I'm going to rename this issue considering the nav-walker as it's the only one yet to be done.

Just tested a bit the original nav walker our nav is based on, it contains aria-labelledby and other features we could implement the same time we do this aria-current update.
PRs still accepted.

Thanks @ronilaukkarinen been very busy but will have a look when I get some time!


Fixing doc-strings

Autogenerated documentation is incomplete. Missing:

mmv_ops
sparse
center_selection
gsc_losses are no good

Related to #1

Closed with a7af37e5ea63b1dea90957f6fd20c0eef50fc6d7


Discord link in readme not working

@ajcastro Fixed! Thanks for reporting this. I created a new one that does not expired 🙃


Fixed Major level code smells from frontend, and one appointment-frontend remnant (CS19)

Removed empty code blocks, updated duplicate methods/CSS, fixed variable scope clarity, fixed logic errors, removed extraneous variables, expanded nested ternary expressions for clarity, deleted obsolete JS file, removed commented out code

closed as they were included in 707


AVS don't use Alsa system config, need it to use DMIX.

Briefly summarize your issue:
Hello, I have problem with skill, eg (if I want to alexa say something during playing music, even if the player is on background).
So I m trying to use this file https://github.com/shivasiddharth/Assistants-Pi/blob/master/audio-drivers/USB-DAC/scripts/asound.conf without changes on alexa.
Just to test I have set "hw0,0", my speaker is "hw1,0".

I have tried editing /etc/asound.conf and ~/.asoundrc
I have tried too "aplay -D default sound.wav" it don't work too, in fact alexa is the only app that still working on all the OS (I have too error message on the GUI) ...
What is the expected behavior?
Will be nice if alexa players/renderers use system config file. there is a special audio configuration file somewhere ? It's not the first time I have this kind of incomprehensible sound bug, last time, the only way we have found was a fresh install. Except the previous time, was alexa don't working, and all the OS working.
What version of the AVS Device SDK are you using?
  <1.8.0>

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:

For information I have
 {
    "gstreamerMediaPlayer":{
        "audioSink":"alsasink"
    },

So I have tried too
gst-launch-1.0 -m audiotestsrc ! alsasink
And It don't work, still normal, but why AVS is still working ? Even Gstreamer use system config file.

Hi @Smanar,
The SDK uses the alsa configuration files (.asoundrc and asound.conf). Please check this troubleshooting (Raspberry Pi section) for more information.

Yeah, I know, I had similar bug somes weeks ago. But this time it's not a troubleshooting, if all was normal AVS need to bug too.
I intentionnaly set bad config to make a test, and all is HS atm, aplay/gstreaming/vlc except AVS.
How can you explain it can still working with bad configuration ?
I can send you all the logs, results from command you want, but to resume I can put all I want in theses 2 files, AVS don't take care about them.
All is bugging ATM with this bad config, except AVS.

Some examples
pi@raspberrypi:~/sounds $ aplay -D default med_ui_endpointing_touch.wav
ALSA lib pcm_dmix.c:1109:(snd_pcm_dmix_open) unable to open slave
aplay: main:788: erreur à l'ouverture audio: Argument invalide

pi@raspberrypi:~/sounds $ play med_ui_wakesound.wav
ALSA lib pcm_dmix.c:1109:(snd_pcm_dmix_open) unable to open slave
play FAIL formats: can't open output file `default': snd_pcm_open error: Invalid argument

But a full working AVS sesssion, with shell command "play" during listening (exactling the same command than the previous), and believe me, all sounds have worked.
https://pastebin.com/A9WQArhR

Lol, and just for fun, I wanted to use the bcm2835 because I have read somewhere it had 8 channel.
And now AVS is locked on usb card. I can change everything I want in the config, impossible to use the jack output.
I have on the same raspberry 3/4 media players, the google assistant, all are using jack output, ...... except AVS ^^.

Hi @Smanar, since we use "sudo bash startupsample.sh" to run the SampleApp, the SampleApp is actually using the .asoundrc in the /root directory, so maybe you can try this:
sudo su -
nano /root/.asoundrc

And modify it based on your system.  Hope this helps!

I am closing this issue due to inactivity, please reopen if you need more assistance regarding this.


Fixes some ATC warnings

removing some smoke, so we can focus on the more important ATC warnings:
following changes were made

replace APPEND with INSERT for sorted tables (ATC: CL_CI_TEST_APPEND_TO_SORTED)
added some PRAGMAs (##MG_MISSING and ##NO_TEXT) to remove other ATC warnings, where I believe the solution is already good.

I can't see how to link this PR to issue 113, but here is my PR. I also added a few pragmas to the solution

Thanks

Hi, no problem, my pleasure.
A little detail i just noticed on my customer system (7.50). The pragma ##NO_TEXT doesn't exist on 7.50- its newer HANA?). The correct pragma for an older ABAP system would be #EC NOTEXT. Should I submit a new PR to change ##NO_TEXT into #EC NOTEXT? On older ABAP systems this shows up as PRAGMA NO_TEXT is unknown.
Thanks
Martin


Authentication problem with tsiclient samples

I cannot log in to any of the samples that include authentication.  I have been able to do so in the past.  I have tried several different accounts of different types and even browsers and machines.  Am I doing something daft or has it been broken during recent updates?

That is really strange!  Are you using an account associated with Azure Active Directory?  Microsoft accounts (like your personal outlook.com account, for example) will not work with third party apps on top of Time Series Insights.  Unfortunately I can't reproduce this issue, is there a specific error you are seeing?

closing this issue since it is now stale


Fix checks for hidden file/folders
Fix slashes in the paths of multiple tests
Separate tests for relative paths with extra_arguments... We may want to normalize these paths in the future for teams that use both Windows and *nix.

If I can get all the tests stable on both Windows and *nix, I'll merge this in, and set up a Windows CI so we don't have these regressions in the future.

OK, as far as I can tell, all the tests now pass on both Windows and *nix. I'm going to merge. I'll add Windows CI in the next day or two.


No simp_chinese can be chose for Stellaris

FYI

In fact I'm not sure that this function even work now ^^'
It's an old function and simp_chinese wasn't supported at the time. I put that as enhancement.

I found out that will overwrite my language selection. Every time I apply a new mod config, the game language will change into English, but Game Launcher still using Chinese.
In the directory "C:\Users\UserName\Documents\Paradox Interactive\Stellaris"
I found out that "settings.txt" still include "language="l_simp_chinese"
But "pdx_settings.txt" will become below, and I have to change it manually

"System"={
"language"={
version=0
value="l_english"

Hope this reply will help, thanks for your great work :)

Should be available in Indev release now

I've tried and working just fine, cool


gvisor: 20221102.1 -> 20231113.0

Description of changes

Unbreak on go >= 1.21
ZHF: #265948
Hydra

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Oh, there was a draft PR #261980 that I didn't see. Please feel free to close this PR if that PR should be merged instead.
Also added passthru.tests to the existing nixos gvisor test.

Oh, there was a draft PR #261980 that I didn't see. Please feel free to close this PR if that PR should be merged instead.
Also added passthru.tests to the existing nixos gvisor test.

you can ping author of https://github.com/NixOS/nixpkgs/pull/261980 to update to latest version, depending on timing of response, either proceed  with this PR, or just reduce it to adding passthru.tests

It seems like the hello world test is flaky. I removed it for now.

I'd avoid formatting changes in general.


i think it is similar than rmsprop

loss moving graph in paper, it looks like rmsprop
how about your opinion? it is better than rmsprop, and why?

Thanks for the interest in Sophia! Sophia is different from RMSprop because (1) Sophia has the second-order estimator in the denominator, while RMSprop uses the square root of exponential moving average of squared gradients. (2) RMSprop does not have the moving average in the numerator of the update rule.  To further help address your question, which loss moving graph are you referring to?


Enable control text internationalization and add zh-CN localization

Enable control text internationalization;
add zh-CN localization.
#37 @lyonelf You can provide French support in a similar way.

Thanks for the contribution! I don't speak Chinese, but ChatGPT said that the text are fine :-)
The text shows up as Chinese in a English IDE, but when running it seems fine so I will merge this


How to import dart:html in dart without flutter

This tracker is for issues related to:

Dart core libraries ("dart:async", "dart:io", etc.)

The source code of file: main.dart
import "dart:html";

When I try to run it: dart lib/main.dart
The compilation output error:
lib/main.dart:1:8: Error: Not found: 'dart:html'
import 'dart:html';
So what's the reason? thanks!

You can only use dart:html when you are targeting the web through dart2js or dartdevc compilers. You can't use it on the native VM. If you want to develop a Web application with Dart see https://dart.dev/web
In the future I also would recommend to use other channels for questions (e.g. StackOverflow, Discord or Gitter). This is issue tracker for problems with Dart SDK not questions.

got it, sorry for the troubles, thanks!


"main" missing from bower.json in 0.10.3

https://github.com/adchsm/Slidebars/blob/master/bower.json


Avoids autofill for small fields

Reviewer:
Asana: https://app.asana.com/0/0/1204037710374985/f
Description
Skips email and password autofill for small fields. Note that this is just a starting point. We can give it more thought and have a set of fields that are not supposed to be small (or viceversa).
For example, these are frequently rather small:

cvv for credit cards
anything date-related like birthdays and expiration of credit cards

Steps to test
Please add tests.

Closing. This problem is now solved. I think we should still separate some of the utils out of the current matching file, but now this would be too hard to conflict-solve.


helloObj.d(59): Error: class uvm.base.uvm_root.uvm_root_entity(T) if (is(T : uvm_root)) is used as a type

[babu@chennai vpi]$ make all
gcc -I/home/babu/Vlang/vlang/vlang/src/esdl/intf  -c -fpic hello.c -o hello.o
dmd -I/home/babu/Vlang/vlang/vlang/src -I/home/babu/Vlang/vlang/vlang-uvm/src -version=UVM_NO_WAIT_FOR_NBA -version=COSIM_VERILOG -fPIC -w -O  -shared -m64 -ofhelloObj.vpi -L-ldl -L-l
vpi -L-lphobos2 -L-R/opt/dmd/linux/lib32 helloObj.d hello.o /home/babu/Vlang/vlang/vlang/src/esdl/base/comm.d /home/babu/Vlang/vlang/vlang/src/esdl/base/core.d /home/babu/Vlang/vlang/
vlang/src/esdl/data/time.d /home/babu/Vlang/vlang/vlang/src/esdl/intf/vpi.d /home/babu/Vlang/vlang/vlang/src/esdl/data/bvec.d /home/babu/Vlang/vlang/vlang/src/esdl/data/cstx.d /home/b
abu/Vlang/vlang/vlang/src/esdl/data/rand.d /home/babu/Vlang/vlang/vlang/src/esdl/data/obdd.d /home/babu/Vlang/vlang/vlang/src/esdl/data/queue.d /home/babu/Vlang/vlang/vlang/src/esdl/d
ata/sync.d /home/babu/Vlang/vlang/vlang/src/esdl/data/packer.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/meta/mailbox.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/meta/mcd.d /home/babu/V
lang/vlang/vlang-uvm/src/uvm/meta/meta.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/meta/misc.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/package.d /home/babu/Vlang/vlang/vlang-uvm/
src/uvm/base/uvm_array.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_barrier.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_bottomup_phase.d /home/babu/Vlang/vlang/vlang-uv
m/src/uvm/base/uvm_callback.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_cmdline_processor.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_common_phases.d /home/babu/Vlang/
vlang/vlang-uvm/src/uvm/base/uvm_comparer.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_component.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_config_db.d /home/babu/Vlan
g/vlang/vlang-uvm/src/uvm/base/uvm_coreservice.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_domain.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_event_callback.d /home/ba
bu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_event.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_factory.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_global_defines.d /home/
babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_globals.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_heartbeat.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_links.d /home/bab
u/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_message_defines.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_misc.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_object.d /home/ba
bu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_object_defines.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_object_globals.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_objecti
on.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_packer.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_phase.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_pool.d /hom
e/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_port_base.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_printer.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_queue.d /home/b
abu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_recorder.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_registry.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_report_catcher.d /
home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_report_handler.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_report_message.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_
report_object.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_report_server.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_resource.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm
/base/uvm_resource_db.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_resource_specializations.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_root.d /home/babu/Vlang/vlang/vl
ang-uvm/src/uvm/base/uvm_runtime_phases.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_spell_chkr.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_task_phase.d /home/babu/Vlan
g/vlang/vlang-uvm/src/uvm/base/uvm_topdown_phase.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_transaction.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_traversal.d /home/
babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_tr_database.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_tr_stream.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/base/uvm_version.d /ho
me/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/package.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_agent.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_algorithmic_compara
tor.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_driver.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_env.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_in_order_
comparator.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_monitor.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_pair.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_
policies.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_push_driver.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_random_stimulus.d /home/babu/Vlang/vlang/vlang-uvm/src/u
vm/comps/uvm_scoreboard.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_subscriber.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/comps/uvm_test.d /home/babu/Vlang/vlang/vlang-uvm/sr
c/uvm/tlm1/package.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/tlm1/uvm_analysis_port.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/tlm1/uvm_exports.d /home/babu/Vlang/vlang/vlang-uvm/src
/uvm/tlm1/uvm_imps.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/tlm1/uvm_ports.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/tlm1/uvm_sqr_connections.d /home/babu/Vlang/vlang/vlang-uvm/src
/uvm/tlm1/uvm_sqr_ifs.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/tlm1/uvm_tlm_defines.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/tlm1/uvm_tlm_fifo_base.d /home/babu/Vlang/vlang/vlang-
uvm/src/uvm/tlm1/uvm_tlm_fifos.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/tlm1/uvm_tlm_gen_rsp.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/tlm1/uvm_tlm_ifs.d /home/babu/Vlang/vlang/vla
ng-uvm/src/uvm/tlm1/uvm_tlm_req_rsp.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/seq/package.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/seq/uvm_push_sequencer.d /home/babu/Vlang/vlang/v
lang-uvm/src/uvm/seq/uvm_sequence_base.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/seq/uvm_sequence.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/seq/uvm_sequence_item.d /home/babu/Vlang/
vlang/vlang-uvm/src/uvm/seq/uvm_sequencer_analysis_fifo.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/seq/uvm_sequencer_base.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/seq/uvm_sequencer.
d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/seq/uvm_sequencer_param_base.d /home/babu/Vlang/vlang/vlang-uvm/src/uvm/vpi/uvm_svcmd_vpi.d
helloObj.d(59): Error: class uvm.base.uvm_root.uvm_root_entity(T) if (is(T : uvm_root)) is used as a type
helloObj.d(77): Error: function helloObj.EsdlRoot.doConfig does not override any function
please help me how to solve this issue
Thanks,
Suresh

Suresh
We are in the middle of making a new release of Vlang. We plan to make the release in the next two weeks. There are some API changes which break the examples. I will request you to wait for about 10 days and then give it a try.
Regards

Puneet

Hi Puneet,
Thanks for your response.
Thanks,Suresh
On Monday, May 30, 2016 12:24 PM, puneet<EMAIL_ADDRESS>wrote:

SureshWe are in the middle of making a new release of Vlang. We plan to make the release in the next two weeks. There are some API changes which break the examples. I will request you to wait for about 10 days and then give it a try.Regards

Puneet
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Puneet,
you have any update please ?
Thanks,Suresh
On Monday, May 30, 2016 12:24 PM, puneet<EMAIL_ADDRESS>wrote:

SureshWe are in the middle of making a new release of Vlang. We plan to make the release in the next two weeks. There are some API changes which break the examples. I will request you to wait for about 10 days and then give it a try.Regards

Puneet
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

We plan to make the release this Wednesday. Will inform you once it is done.

Just created a alpha0 source release for vlang and vlang-uvm. We are currently porting UVM test cases and on completion of that exercise, we will create a beta release.
I will make a binary package for AMD 64 platform tomorrow.

Hi Puneet, you have any update please ?
Thanks, Suresh
On Thursday, June 16, 2016 3:34 AM, Coverify<EMAIL_ADDRESS>wrote:

Just created a alpha0 source release for vlang and vlang-uvm. We are currently porting UVM test cases and on completion of that exercise, we will create a beta release.I will make a binary package for AMD 64 platform tomorrow.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hello Suresh
Sorry for the delay. Like most opensource projects we got into some issues that we wanted to resolve before making a formal release.
We hope to make a release this Saturday.
I would like to know what Linux distribution you would like to run Vlang on. We have a binary release that we are currently using internally at Coverify. It works on Ubuntu 14.04 and later releases. We have also tested it on CentOs 7. If that works for you, I will give you the path to download the binaries right away. If you use an earlier version, you will have to wait for a couple of days for us to get there.
Vlang release will not require root permissions to install. But in case you want to use vlang along with Icarus verilog, you will have to install Icarus yourself. Unfortunately Icarus binaries are not portable.
Since we are going to do a public release of vlang, we would like to first take it to some limited audience and make sure that we fix the teething problems before making public release. If you do not mind, we would like to hear from you regarding any issues that you face in installation or while running some examples.
You can write to me on my email address puneet at coverify (dot com).
Regards

Puneet


\str_lowercase:f removed in lualatex-dev

Description
In the developer's preview versions lualatex-dev, \str_lowercase:f seems to be removed. According to the l3deprecation.dtx the new command needs two underscores: \str_lower_case:f. Changing fontspec-luatex.sty to this variant works in both the normal as well as the developer variant.
Check/indicate

[ ] Relevant for XeTeX
[X] Relevant for LuaTeX
[X] Links to <tex.stackexchange.com> discussion if appropriate
There seems to be a similar issue, however, my l3kernel is both from Februar this year and mpm is not complaining about a required reinstallation (though I tested this, to be sure).
[X] Issue tracker has been searched for similar issues?

Minimal example demonstrating the issue
\documentclass{article}
\usepackage{unicode-math}
\setmainfont{texgyrepagella}[
  Extension = .otf ,
  UprightFont = *-regular.otf ,
  ItalicFont  = *-italic.otf  ,
]
\begin{document}
hello \emph{hello}
\end{document}

Ignore my commit above, it has been rolled back. I wasn't paying enough attention.
\str_lower_case:f is the OLD command — \str_lowercase:f is the new one.
I think an update to all l3.. and latex2e packages in your distribution should fix the issue.

Sorry for the wrong report. This seems to be a MikTeX development build issue, as all my l3 packages are up-to-date (even after the update today, it is still present), and also the date of the luatex-dev format is from February 1st (rebuild right now didn't help).

Great to hear!


Questions of huge interest in Loki Operator

Hello all,
Let me express great appreciation and hope for this Loki Operator initiative!
We've been searching for Loki Operator since OKD 4.0 release but with no luck. It's great pleasure to see RedHat's attempts in this direction to bring ELK alternatives to OpenShift 4.x.
Would you mind to give us some timelines when we can expect GA or preview release of Loki Operator? If that will be helpful for you, guys, we're ready to be early testers and adopters of this.
Also I would like to ask (if this is OK for you) if this Loki Operator will be available in free OKD (unlike current Logging Operator)? Are there any plans of integration of Loki into Cluster Console UI? I think it will be natural and very useful addition to Prometheus integrations there.
While trying to implement Loki ourselves, we've faced with lack of secure connections between Loki's components. Do you have any plans to make it available out the box (like all other OpenShift's components and Prometheus particularly)?
Thank you very much for any answers on these subjects!

First of all, thanks for stating your interest on the loki operator project. Really appreciate to hear from early adopters!
Let me try to answer you questions at the best of my ability:

We don't have any GA or preview release dates neither for OKD nor for OCP right now. This project aims to provide a kubernetes operator for Loki with out-of-the-box support for OpenShift but w/o requiring the later. The OpenShift integration is part of the OpenShift Cluster Logging stack but an optional thing here. You can follow up the details on this enhancement document: https://github.com/openshift/enhancements/blob/master/enhancements/cluster-logging/loki-storage.md
The OpenShift Cluster Logging team is looking into some native integration for logs into the Web Console atm, but this is unrelated to Loki or the current Elasticsearch store. AFAIK the integration is meant to be agnostic of the store, but I don't know much about the details TBH.
The path forward for the Loki Operator is to provide in addition to Loki a thin proxy layer to enable integration with user's tenancy and UI desires (e.g. OCP's tenancy model is namespace-driven). Moving forward we look for supporting folks to point their Grafana instance to the operator managed Loki as well as the OpenShift web console.

Last but not least, what are you referring as secure connections between Loki Components? Can you elaborate on the issues you faced on?
Thanks again for dropping by! If you are interested in testing the operator as is right now, I would be glad to provide assistance.

Also I would like to ask (if this is OK for you) if this Loki Operator will be available in free OKD (unlike current Logging Operator)?

This statement is incorrect.  Both the RH cluster-logging-operator and elasticsearch-operator are available to be deployed to OKD.    It may not be as simple as with OCP, but there are no restrictions otherwise.  Any feedback you can provide is welcome.  Please open an issue on the cluster-logging-operator

Also I would like to ask (if this is OK for you) if this Loki Operator will be available in free OKD (unlike current Logging Operator)?

This statement is incorrect. Both the RH cluster-logging-operator and elasticsearch-operator are available to be deployed to OKD. It may not be as simple as with OCP, but there are no restrictions otherwise. Any feedback you can provide is welcome. Please open an issue on the cluster-logging-operator

Thanks, @jcantrill, for pointing our attention to this. Official logging stack installation guide (https://docs.openshift.com/container-platform/4.7/logging/cluster-logging-deploying.html) is mentioning operators ("OpenShift Elasticsearch Operator" and "Red Hat OpenShift Logging") which are not present in Operator Hub in OKD:

This makes us think there is no cluster logging available for OKD. It's a great news if it is! Can you please point us to some guide how to deploy it on OKD (which I'm unable to find)?

First of all, thanks for stating your interest on the loki operator project. Really appreciate to hear from early adopters!
Let me try to answer you questions at the best of my ability:

We don't have any GA or preview release dates neither for OKD nor for OCP right now. This project aims to provide a kubernetes operator for Loki with out-of-the-box support for OpenShift but w/o requiring the later. The OpenShift integration is part of the OpenShift Cluster Logging stack but an optional thing here. You can follow up the details on this enhancement document: https://github.com/openshift/enhancements/blob/master/enhancements/cluster-logging/loki-storage.md
The OpenShift Cluster Logging team is looking into some native integration for logs into the Web Console atm, but this is unrelated to Loki or the current Elasticsearch store. AFAIK the integration is meant to be agnostic of the store, but I don't know much about the details TBH.
The path forward for the Loki Operator is to provide in addition to Loki a thin proxy layer to enable integration with user's tenancy and UI desires (e.g. OCP's tenancy model is namespace-driven). Moving forward we look for supporting folks to point their Grafana instance to the operator managed Loki as well as the OpenShift web console.

Last but not least, what are you referring as secure connections between Loki Components? Can you elaborate on the issues you faced on?
Thanks again for dropping by! If you are interested in testing the operator as is right now, I would be glad to provide assistance.

Thanks, @periklis, for this information! This is very useful and may change our direction of further work.

what are you referring as secure connections between Loki Components?
I mean there is no TLS between Promtail and Loki and there is no TLS between Loki and Grafana by default. Also there is no auth between these components. Official Loki docs says "Loki does not come with any included authentication layer.  So we're wondering how will you deal with this insecurity of Loki.

Thanks, @periklis, for this information! This is very useful and may change our direction of further work.

what are you referring as secure connections between Loki Components?

I mean there is no TLS between Promtail and Loki and there is no TLS between Loki and Grafana by default. Also there is no auth between these components. Official Loki docs says "Loki does not come with any included authentication layer.  So we're wondering how will you deal with this insecurity of Loki.

We will probably deal with a thin reverse proxy layer as we do on our internal hosted Loki instances, e.g. https://github.com/observatorium/api/


Investigation: try React-Redux v7 / v8 with React 18 alpha

React 18 is now available as preview alpha releases (per https://reactjs.org/blog/2021/06/08/the-plan-for-react-18.html ).
The React team has put together a Working Group discussion forum to describe the changes in React 18 in more detail: https://github.com/reactwg/react-18/discussions
Looking at that forum, there's several issues that may be relevant to React-Redux in some way:

Overviews:

Introducing React 18
Upgrading to React 18 on the Client
Installing React 18 Alpha

Behavior changes:

Automatic batching
Adding Strict Effects to StrictMode
How to support Strict Effects
Testing with Strict Effects
How to support Strict Effects

I'd like to have some folks start trying out React-Redux v7 with React 18 alpha, and report any interesting findings.  We could potentially use some of the example apps from the Redux tutorials, and any of the example CodeSandboxes linked in our docs.
You would need to:

Switch the React version to one of the React 18 alphas, and update the app to use React.createRoot() per instructions
Try out the app
Hand-inspect the behavior to see if anything seems unexpected

We're interested in seeing examples and comparisons with both connect and useSelector.
It would also be worth cloning the React-Redux repo, and updating our React devDep to run our tests against the alphas.
The React team has reported that a brief test of a couple Redux-based apps combined with createRoot + StrictMode did not appear to be working correctly - in particular, no re-rendering happening despite actions being dispatched.
It's very possible that Strict Effects running effects callbacks more than once is causing problems with subscriptions.
We'd appreciate any feedback reports!
Please provide this info:

Details on the example app used
Link to updated source code / CodeSandbox if possible
Description of observed behavior, good or bad ("works okay", "clicking button X doesn't update the UI", etc)

Note to folks trying — if you have StrictMode on, please test both with StrictMode and without it. This is to see if some issues only occur in StrictMode.

We actually have tests for StrictMode in our suite already, so it should be good to test at least the basics here.

Okay.  First issue here is that there's this new "Strict Effects" thing which is enabled if you're using createRoot() + <StrictMode>, which double-runs the effects in the same way that <StrictMode> has traditionally double-run renders.  I could easily see that messing up subscriptions.
So, we'd need to figure out how to do a React 18 upgrade for our tests, which I assume would mean something with React Testing Library since that's doing the rendering?

If you're asking about Testing Library compatibility, you may want to subscribe to https://github.com/testing-library/react-testing-library/pull/925.

I have a side project that used to React-Redux v7.2.4, I'd like to try it if React 18 alpha working on CRA v4.0.3.

Comment from the React team on plans for helping the community do updates:
https://github.com/reactwg/react-18/discussions/56#discussioncomment-865019

The first step is to explain what work we see needs to be done at a high level, so we're working on a workgroup post that will be a "Concurrent rendering for library maintainers" guide, and documentation for new APIs libraries will use to support concurrent features. Those docs will be a "kick off" for starting library support. After they're published, we'll do a Q&A / support session, and use the working group to document questions, use cases, patterns, design, etc.
I know we're all really excited to start with the work of adding support to libraries, so I'm sorry it's taking so long. We've spent the last couple weeks kicking off the release (which focused on the gradual adoption strategy), and now we're transitioning to working with libraries to support the new concurrent features.
We expect this work to take months, not weeks, similar to how the hooks release went.

Mobx has a PR going that's tracking some similar status checks for React 18. Worth keeping an eye on that:
https://github.com/mobxjs/mobx/pull/3005

Hi @markerikson! I have something interesting for you)
I have a repository with react 18 + SSR + redux for UI state. There is an interactive demo — http://<IP_ADDRESS>:5000/
As you can see, there is a button "Patch query string". If you'll click this button, the UI state in a redux-store will be updated with new Date().toString() There is a source code. Top part of the page has a component, that has a subscription to the redux-store vis useSelector.
So, if you will open the demo with a query param strict=true, the whole app will be wrapped with  component. If there is no strict query param — without it. Click to the button, that changes the query string works perfectly in strict mode and without it. But, it works in production build only.
If you will clone the repository, exec npm i && make dev and open http://localhost:4000?strict=true, you will see, that the. UI won't be changed after the button click.
Actually, I can not understand, what is the difference between develop and production build in case of redux/react-redux. May be it is because of react?

Example of StrictMode + createRoot breaking it, per request from https://github.com/reactwg/react-18/discussions/19#discussioncomment-1320450: https://codesandbox.io/s/serverless-wood-uouyy?file=/src/index.js

And copying over some excellent detective work from @andarist :

The problem is not that dispatching doesn't work (although you probably didn't mean exactly that) and it's not even because components are not subscribed - because they are. The problem is that the hooked up listener is a "proxy" listener:
https://github.com/reduxjs/react-redux/blob/d859c236168ddf53a97a032ac3d098ee670b8a40/src/utils/Subscription.ts#L111-L115
which actually forwards notifications to another one that is put as a property on the subscription object. And that property gets "nullified" in the cleanup of the Provider:
https://github.com/reduxjs/react-redux/blob/d859c236168ddf53a97a032ac3d098ee670b8a40/src/components/Provider.tsx#L43
while not being re-instantiated in the setup because it's only assigned within useMemo here:
https://github.com/reduxjs/react-redux/blob/d859c236168ddf53a97a032ac3d098ee670b8a40/src/components/Provider.tsx#L25
So what happens is that Provider gets notified about a store change - it should notify nested subscriptions but it doesn't because of the mentioned issue. And useSelector (and probably any other inner subscribers like connect etc) are never notified about this because they are subscribed to that parent subscription that lives in the Provider here.
TLDR; lack of symmetry between setup/cleanup of an effect in the Provider led to the notification chain being broken.

https://etg.dek.im works okay after updating to react-redux 8.0.0-beta.3 & react 18.0

React-Redux v8 is out, so I think we can call this done :)


deploymentmanager - clean up duplicate parameters outside of method

Modelerfour in T2 will combine the parameters outside of method and inside the method. Hence it causes duplicate parameter of subscriptionId, when it is defined twice.
This change likely not going to affect T1 SDKs.
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

From python PR https://github.com/AzureSDKAutomation/azure-sdk-for-python/pull/5157/files there is no change to operations.

/azp run


BaseRecalibratorDataflowIntegrationTest on SparkPipelineRunner

This gets BaseRecalibratorDataflowIntegrationTest running on Spark.
I noticed that the test with "-knownSites" from BaseRecalibratorIntegrationTest (i.e. the non-dataflow version) fails with both the Direct and Spark runners. I had a look at the file output and there are a few discrepancies (see diff below). Any thoughts on how to fix this? I've commented out the test in this PR.
diff /var/folders/d1/8f5_j4hx04z72w6wgqxkb2l40000gn/T/walktest.tmp_param.02172067147450353519.tmp src/test/resources/org/broadinstitute/hellbender/tools/BQSR/expected.NA12878.chr17_69k_70k.2inputs.txt
60c60
<           34   3051              34
---
>           34   3050              34
71c71
<           45  46942              45
---
>           45  46940              45
124,126c124,126
< 809R9ABXX101220.5  D                   45.0000             45.0000         23471    0.00
< 809R9ABXX101220.5  I                   45.0000             45.0000         23471    0.00
< 809R9ABXX101220.5  M                   27.0000             27.0494         23471   49.13
---
> 809R9ABXX101220.5  D                   45.0000             45.0000         23470    0.00
> 809R9ABXX101220.5  I                   45.0000             45.0000         23470    0.00
> 809R9ABXX101220.5  M                   27.0000             27.0493         23470   49.13
155c155
< 809R9ABXX101220.5            34  M                   34.0000          3051    2.96
---
> 809R9ABXX101220.5            34  M                   34.0000          3050    2.96
161,162c161,162
< 809R9ABXX101220.5            45  D                   45.0000         23471    0.00
< 809R9ABXX101220.5            45  I                   45.0000         23471    0.00
---
> 809R9ABXX101220.5            45  D                   45.0000         23470    0.00
> 809R9ABXX101220.5            45  I                   45.0000         23470    0.00
2714c2714
< 809R9ABXX101220.5            34  29              Cycle          M                   34.0000            20    0.00
---
> 809R9ABXX101220.5            34  29              Cycle          M                   34.0000            19    0.00
2773c2773
< 809R9ABXX101220.5            34  CA              Context        M                   34.0000           506    0.00
---
> 809R9ABXX101220.5            34  CA              Context        M                   34.0000           505    0.00
3464,3465c3464,3465
< 809R9ABXX101220.5            45  29              Cycle          D                   45.0000           180    0.00
< 809R9ABXX101220.5            45  29              Cycle          I                   45.0000           180    0.00
---
> 809R9ABXX101220.5            45  29              Cycle          D                   45.0000           179    0.00
> 809R9ABXX101220.5            45  29              Cycle          I                   45.0000           179    0.00
3634,3635c3634,3635
< 809R9ABXX101220.5            45  GCA             Context        D                   45.0000           278    0.00
< 809R9ABXX101220.5            45  GCA             Context        I                   45.0000           278    0.00
---
> 809R9ABXX101220.5            45  GCA             Context        D                   45.0000           277    0.00
> 809R9ABXX101220.5            45  GCA             Context        I                   45.0000           277    0.00

@droazen or @lbergelson - would you be able to take a look at this one please?

Sorry for the wait tom.  We're a bit behind on pull requests.  We will get to this as soon as possible.

Thanks @lbergelson. I've rebased on master to fix conflicts with the patch you did to remove secret keys. In doing so I changed back your change to BaseRecalibratorDataflowIntegrationTest which added the API key in one place since one of its tests now runs locally again, and there is no API key in that case.

@tomwhite, the local BaseRecalibratorDataflow needs the API key because, even though it's running locally, it fetches reference bases from the Google Genomics API.
That is also why I put it in the "cloud" group: my understanding is that this is the group of tests that will fail if you don't have valid credentials for the Google cloud.

@jean-philippe-martin, this change changes testBQSRLocal to be truly local, so that it reads the reference from the local filesystem (which was added in https://github.com/broadinstitute/hellbender/pull/827). So, for that test no API key is needed.
The testBQSRRefCloud test still loads the reference from the cloud, so we're still testing that case too.

@tomwhite ah ok, then that's fine.

I should have added this test in #827, but I missed that all the tests were running in the cloud.

Hmn, commented directly on one of the commits, sorry about that.

@tomwhite Back to you.  Feel free to squash and merge once it's no longer outputting the api key into the logs.

@lbergelson can you take this? you know better than i what to do

This is still leaking api keys into the public logs.  See https://storage.googleapis.com/hellbender/test/build_reports/2311.1/tests/classes/org.broadinstitute.hellbender.tools.dataflow.pipelines.BaseRecalibratorDataflowIntegrationTest.html

@lbergelson should we migrate this to hellbender-dataflow?

The non-test changes from this one were committed via https://github.com/broadinstitute/hellbender/pull/924, so the only thing needed is  the test to use a local reference file.

Closing this since it's no longer relevant.  Pushed the branch to gatk-dataflow


Fix TestStrictMTLS test to work in istiodremote topology

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@frankbu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
d0513f6bfcd3b539e1fc0fd026679918868fcccd
link
true
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-security-istiodremote-tests_istio

@frankbu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
d0513f6bfcd3b539e1fc0fd026679918868fcccd
link
true
/test release-notes_istio

unit-tests_istio
d0513f6bfcd3b539e1fc0fd026679918868fcccd
link
true
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest