MTOUCH : error MT5211: Native linking failed, undefined Objective-C class: SDWebImageManagerDelegate. The symbol 'OBJC_CLASS$_SDWebImageManagerDelegate' could not be found in any of the libraries or frameworks linked with your application.

From @GeonetJP on August 7, 2018 8:19
My setup:

Visual Studio for Mac Community Version 7.5.4 (build 3)
Xamarin SDK updated to the latest
iOS SDK updated to the latest.

When I run my project it fails with the following:
clang : error : linker command failed with exit code 1 (use -v to see invocation)
MTOUCH : error MT5211: Native linking failed, undefined Objective-C class: SDWebImageManagerDelegate. The symbol '_OBJC_CLASS_$_SDWebImageManagerDelegate' could not be found in any of the libraries or frameworks linked with your application.
MTOUCH : error MT5211: Native linking failed, undefined Objective-C class: SDWebImagePrefetcherDelegate. The symbol '_OBJC_CLASS_$_SDWebImagePrefetcherDelegate' could not be found in any of the libraries or frameworks linked with your application.
MTOUCH : error MT5202: Native linking failed. Please review the build log.

It started right after the latest updated from both SDK (Xamarin and iOS)
I've read the previous posts with similar issue and I think it can be fixed from your side via an update on your Nuget Package: Xamarin.SDWebImage.
Can you please help with this issue?
Copied from original issue: xamarin/xamarin-macios#4585

@VincentDondain  We are in the final stages of releasing a new version of SDWebimage, so this should hopefully fix your problem.

Hi @newky2k,
I'm still waiting for your updates on the Xamarin.SDWebImage Component.
Do you have any timescale on this. The current version I'm running on my project is the latest available (version 4.0.0-beta1) but it's still not compiling. Just failing with the same stack trace.
Any details would be helpful.
Is there any patch applicable on my code to make it work?
Thanks.

Hi @VincentDondain, @newky2k,
Is it possible to know when a fixed version of the SDWebImage Component will be available.
I'm running the version 4.0.0-beta1 but it's still failing with the same issue:

clang : error : linker command failed with exit code 1 (use -v to see invocation)
MTOUCH : error MT5211: Native linking failed, undefined Objective-C class: SDWebImageManagerDelegate. The symbol 'OBJC_CLASS$_SDWebImageManagerDelegate' could not be found in any of the libraries or frameworks linked with your application.
MTOUCH : error MT5211: Native linking failed, undefined Objective-C class: SDWebImagePrefetcherDelegate. The symbol 'OBJC_CLASS$_SDWebImagePrefetcherDelegate' could not be found in any of the libraries or frameworks linked with your application.
MTOUCH : error MT5202: Native linking failed. Please review the build log.

I currently have a project to update and to deliver and I can't implement the new features just because this component it's not working at compilation phase.
Do you have any advice or tips e.g. for example to get the component and patch it myself so at least I could make it work locally till you push the official fix.
Any help/support would be great

We just pushed v4.4.0 to NuGet which works well in testing here.
Please give it a try!

FYI may be a few minutes for it to show up in NuGet.org's index, but here's the direct link:
https://www.nuget.org/packages/Xamarin.SDWebImage/4.4.0

Hi @Redth,
I just downloaded the latest version and I confirm that it works perfectly fine now.
Thanks for the fix.

Hi all, I'm getting the following error, does anyone know how to fix it?
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT0141: The interpreter is not supported in the simulator. Switching to REPL which provide the same extra features on the simulator.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACAbstractLog. The symbol 'OBJC_CLASS$_MSACAbstractLog' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACAppCenter. The symbol 'OBJC_CLASS$_MSACAppCenter' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACAppCenterUserDefaults. The symbol 'OBJC_CLASS$_MSACAppCenterUserDefaults' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACAppDelegateForwarder. The symbol 'OBJC_CLASS$_MSACAppDelegateForwarder' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACChannelUnitConfiguration. The symbol 'OBJC_CLASS$_MSACChannelUnitConfiguration' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACDependencyConfiguration. The symbol 'OBJC_CLASS$_MSACDependencyConfiguration' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACHttpClient. The symbol 'OBJC_CLASS$_MSACHttpClient' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACHttpIngestion. The symbol 'OBJC_CLASS$_MSACHttpIngestion' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACHttpUtil. The symbol 'OBJC_CLASS$_MSACHttpUtil' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACKeychainUtil. The symbol 'OBJC_CLASS$_MSACKeychainUtil' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACLogger. The symbol 'OBJC_CLASS$_MSACLogger' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACServiceAbstract. The symbol 'OBJC_CLASS$_MSACServiceAbstract' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACSessionContext. The symbol 'OBJC_CLASS$_MSACSessionContext' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSACUtility. The symbol 'OBJC_CLASS$_MSACUtility' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5211: Native linking failed, undefined Objective-C class: MSAC_Reachability. The symbol 'OBJC_CLASS$_MSAC_Reachability' could not be found in any of the libraries or frameworks linked with your application.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5210: Native linking failed, undefined symbol: OBJC_METACLASS$_MSACAbstractLog. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5210: Native linking failed, undefined symbol: OBJC_METACLASS$_MSACHttpIngestion. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5210: Native linking failed, undefined symbol: OBJC_METACLASS$_MSACServiceAbstract. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'System' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'ole32' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'System' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'System.Net.Security' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'System' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'System' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'crypt32' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'advapi32' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'kernel32' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): warning MT5215: References to 'ncrypt' might require additional -framework=XXX or -lXXX instructions to the native linker
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error MT5202: Native linking failed. Please review the build log.
1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(224,3): error : linker command failed with exit code 1 (use -v to see invocation)


I can't import my map

I can't import my map with /mvimport that displays "starting.... Failed" ! I have this error ! I have already upload in my server but I want it for a second use !
[Server thread/ERROR]: [Multiverse-Core] The world 'Thelab' could NOT be loaded because the server didn't like it!
[22:39:21] [Server thread/ERROR]: [Multiverse-Core] We don't really know why this is. Contact the developer of your server software!
[22:39:21] [Server thread/ERROR]: [Multiverse-Core] Server version info: git-Spigot-6016ac7-10c10b3 (MC: 1.10)
[22:39:21] [Server thread/ERROR]: [Multiverse-Core] Failed to Create/Load the world 'Thelab'
[22:39:21] [Server thread/INFO]: Clemdu63: Failed!
Sorry for my bad english I'm french

Please at least try to read the error message. It says

Contact the developer of your server software!

I have contacted him and he say "the problem is an internal error of the plugin"


Add an automatically generated API client

This PR is a first cut at adding a clientset for K6 objects that can be used programmatically in go (in the same way that vanilla k8s apis in v1/core, v1/batch, etc).
The PR is divided into 3 commits:

Add and bump some dependencies
Rename the api directory to apis.  This is driven by an (AFAICS undocumented) assumption in the kube-codegen codebase that all APIs will be located in a single package, and will be named according to PARENT-PKG/GROUP/VERSION.  So api/v1alpha doesn't work quite right in the codegen (this piece of code which does something surprising when a package name is exactly api doesn't help either....)
Add the makefile rule to generate the code, as well as the generated code files.

There are a few outstanding questions I have:

What is the minimum version of the go compiler and the k8s api libraries that you want to support?  I just built with go1.18 and bumped the deps as far as they would go, since this seemed like the easiest way to get it working.  If you have specific minimum version support requirements/goals, then I can dial the versions back to meet them
How (if at all) would you like the code generation to be integrated in the CI/build process?  So far, the target is in the makefile but nothing calls it (other than manually)
The integration with the kube-codegen library is a bit ad hoc.  The official docs want the integrator to call a bash script that's bundled into an upstream go package (:exploding_head:).  They also rely on having some libraries (such as kube-codegen) vendored into the integrating repo.  Given that go run exists and this repo doesn't vendor its deps, the upstream advice seemed to me like not the best way to integrate the upstream library...

PS If you are wondering, "what's this for," at $WORK we have an internal tool that does supervision of NFT tests in a k8s cluster.  So far we use vanilla k8s Jobs for this (that run k6 on the inside) but we want to migrate to the operator.  We need programmatic access to the K6 resources in the cluster in in our test supervisor (written in go) so we can do things like "wait until the test has passed and then [push a docker image/deploy the version to a test env/etc]"  I/we were able to get a certain distance with the generic REST interface, but at a certain point having properly typed API clients becomes very helpful....

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you for the PR @aecay! IMHO, this feature is valid, I'm even surprised it hasn't come up before. Just as a heads-up, I won't be able to properly review this PR for a couple of weeks. At first glance, it looks OK but it does change a lot of things around and generation seems intricate. It might also clash with #138 changes.
One request from my side now: please remove dependency updates (other than what is added by the client generation). Our policy is to do dependency updates in separate PRs and therefore, builds.
As for your questions:

currently, I'd say it's 1.17.
we only build docker images a the moment. I've been thinking of possibility to add manifests generation to the CI - and client-gen seems similar. But this is tied to the 3rd point too and can likely become very messy. Either way, changes to CI would be better put into a separate PR so no need to add anything here. Thanks for considering it.
:thinking: what steps did you run exactly? Looking at this doc, that shell script is not meant to be used outside of Kubernetes repo. And in sample-controller, it looks like, well, a sample, not a requirement... Do they claim differently in another place? This might require going into more detail than I have capacity now but general advice would be to rely on Makefile if needs be. I.e. adding another command with the steps you took, etc. would be fine, so long as there're brief comments on what it actually does.

Hi @yorugac .  Thanks for your feedback (and sorry it has taken me a while to get back to this -- I needed to chase approvals for the CLA internally at my employer -- which I'm happy to say is now sorted out).
First of all, I've redone the branch with no dependency updates needed.  :tada:  It turned out to be pretty simple (now that I know what I'm doing, more than I did when I started...)

gotcha
gotcha
I've added the command needed to generate the api client files to the Makefile.  I've added a comment explaining what that target does, and noting the fact that it's currently not hooked into any automation.

As far as the issue about vendoring of dependencies goes, as far as I can see the flags for client-gen to control the output file location are --output-base and --output-package.  I tried passing --output-base . --output-package apis/k6/v1alpha1/generated which in principle should write the generated files into the right place in this repo.  And it does -- but it generates the import paths between the generated modules like:
import (
	k6v1alpha1 "apis/k6/v1alpha1/generated/clientset/typed/k6/v1alpha1"
)

What we need that import path to be is actually github.com/k6-operator/apis/.....  That just means that I need to generate the files into a folder named github.com/k6-operator, copy them out of there and into the right place in the source tree, and then delete the github.com folder.  That's all handled in the makefile on my branch and it's not a big deal -- it just seemed like a strange usability quirk of the tool.  I was worried I was missing something -- but now I think that upstream k8s just has a vendoring-heavy workflow and so has not catered for this situation.  :shrug:

Hi @yorugac .  Just checking on this PR -- is there anything outstanding that I need to do from your POV?  Thanks :slightly_smiling_face:

Hi @aecay, I've finally had some time to dig into your PR; my apologies for the delay.
Code wise: the current branch seems fine to me but I intend to run some more tests with it -- will let you know if anything comes up. Ideally, I'd ask to include an example of how clientset is used if it's not too much trouble. Our README is becoming kind of overwhelmed though, so maybe a separate folder docs/examples would be good.
However, I've been trying to understand myself what's going on with different Kubernetes generators :joy: Partially due to issues you raised about the quirks of the tooling but also because in this PR, we get a new dependency: previously we used basically kubebuilder - now it's also code-generator. And it appears that there are differences in opinion regarding clientset in ecosystem! Namely, this article and the issue https://github.com/kubernetes-sigs/kubebuilder/issues/1152 are making it clear that kubebuilder approach is to go wtihout clientset.
Could you please share your opinion on this? I don't think we got this request about clientset from anyone before and I'd like to have a more clear view on 'why' we add this prior to merging :slightly_smiling_face: E.g. you mentioned hitting some limits at which you started needing a dedicated clientset: are there some specific requirements that couldn't be resolved with the default client or is it too much boilerplate, etc.?

@yorugac Thanks for this info.  I was previously not familiar with this way of writing clients -- I had previously only used the approach with specific clientset per API.  I am going to make an attempt at implementing our code with the kubebuilder method instead -- I think that will give us what we need!  If it turns out that there are any issues encountered with kubebuilder, I may reopen this.  But based on what I have seen so far, it should work out for us :slightly_smiling_face:
Thanks again :slightly_smiling_face:

Thanks for the update and clarifying the situation, @aecay! I hope the operator works for your use case. And certainly feel free to re-open if needs be :slightly_smiling_face:


Sort index headers

Suggestion for https://github.com/reason-association/rescript-lang.org/issues/69

Thanks. I like the detail with t as the first element.

Thanks. I like the detail with t as the first element.


Fix typo

You might also want to cleanup/refactor calculateRowOrder to use sortable's toArray-method.


Android Teams app: App Permissions missing

Hi.
The menu for App Permissions is missing on thecurrent Teams-app on Android.
App-version: 1416/<IP_ADDRESS>1063702/0602
Android-version:  10
#3305 looks like the same exact problem , but for iOS in that case.
Following the docs on requesting permissions for apps on Request device permissions for your Microsoft Teams app.

Any attempts to request camera using selectMedia throws Error Code 1000 PERMISSION_DENIED.
There are no user prompts displayed.
The app manifest contains "devicePermissions": ["media"].

The docs display the settings like this:

No App Permissions present on this version:

Hi @oyvindam - Thanks for bringing up this issue. I am able to reproduce the issue. We will raise a bug and will inform you.

@oyvindam - I have created a bug for this issue and concerned engineering team is working on this.

An update on this from my end:
Requesting camera using selectMedia/captureImage now works fine on version 1416/<IP_ADDRESS>1074803/0613.
User is prompted to give permissions and the in-app camera works as expected.
The app permissions menu is still missing, but that may have been removed by design afaik.

@oyvindam  - The concerned engineering team is working on this. We will update you if the issue gets resolved. Currently we don’t have any ETA to share.

This is working now. The app permissions menu has reappeared on both iOS and Android and the camera functionality works as expected.


Rename README.md to README.md Js. Benefits Trgull

Update

Checklist

[x] documentation is added or updated
[x] tests are added or updated

Please update to other accounts

This is completely wrong. No.


Vifedo/apim quotas self hosted gateways

Fixed wrong quota contract. Test added.

fixes issue - https://github.com/Azure/azure-sdk-for-net/issues/11734

@vfedonkin can you update the major version here, since this is a breaking change from the SDK perspective, even though the older version never worked.

@solankisamir , version changed

Please add a link to the openapi spec review PR here.
Thanks

This is a link to rest spec PR: https://github.com/Azure/azure-rest-api-specs/pull/9642

@isra-fel , I added link to PR and removed files


error on deploying

ive been getting an unknown error in deploying my app. And the code seem to be fine and works properly while hosting on my own server i dont y it isnt working on koyeb

as u see in screen shot i cant view logs nor i dont know y app is ded

hey after refreshing page multiple time i can see logs. btw my logs are fine so as the code but y is it showing as error on deployal.
It would be nice if logs are more specific like other hosting platforms like (heroku.com). and tqs for koyeb u did a great job guys. i like koyeb's ui verymuch tqs

my logs here

Hi @TAMILVIP007!
Thanks for the bug report. I quickly took a look and it looks like there have been some intermittent errors while fetching logs our engineering team is currently looking at.
I will close this issue as it is not related to Koyeb CLI.
If you need further support, please click on the chat widget in the bottom right on app.koyeb.com.


riscv: smarter FPU context switching

Instead of saving/restoring FPU content on every exception and task
switch, this replaces FPU sharing support with a "lazy" (on-demand)
context switching algorithm similar to the one used on ARM64.
Every thread starts with FPU access disabled. On the first access the
FPU trap is invoked to:

flush the FPU content to the previous thread's memory storage;

restore the current thread's FPU content from memory.

When a thread loads its data in the FPU, it becomes the FPU owner.
FPU content is preserved across task switching, however FPU access is
either allowed if the new thread is the FPU owner, or denied otherwise.
A thread may claim FPU ownership only through the FPU trap. This way,
threads that don't use the FPU won't force an FPU context switch.
If only one running thread uses the FPU, there will be no FPU context
switching to do at all.

Compliance checks cannot pass as new typedefs are needed to work with
GEN_OFFSET_SYM(). What's the way out here?

Someone with merge superpowers would need to merge the PR after approvals.

@cfriedt wrote:

I think it would be nice to include a benchmark before and after this
change. Is there one that already exists for Aarch64?

No. Aarch64 was done "right" from the start.
However the gain should be obvious. With one thread using FP instructions,
the actual task switching cost is reduced from the whole FPU save-restore
to simply flipping FPU access on or off. Same thing for every interrupt
and syscall entry/exit (no more FPU save-restore is done).
If two threads are both actively using the FPU then there will be some
overhead as the ownership is transferred via an access trap. But interrupt
handlers and syscalls shouldn't normally be fighting for the FPU (this
implementation allows for it even if Zephyr doesn't officially support it)
and the gain here is real in all cases.
Plus stack usage is far less. The FPU content is saved in the thread object
only once and no longer on the exception stack frame at every exception
entry (including recursive IRQs).

Just one suggestion - turn FPU_DEBUG into a Kconfig option - maybe
CONFIG_RISCV_FPU_DEBUG.

 There are no user-serviceable parts there. This debugging facility
is for real mechanics willing to get their hands dirty.  ;-)

@cfriedt wrote:

I think it would be nice to include a benchmark before and after this
change. Is there one that already exists for Aarch64?

No. Aarch64 was done "right" from the start.
However the gain should be obvious.

Of course it is - it's just nice to be able to quantify improvements 😉 It's useful for your own records but also for people who need to advocate for changes here and there, for marketing purposes, etc. This change will have a pretty significant impact for a lot of people.

Just one suggestion - turn FPU_DEBUG into a Kconfig option - maybe
CONFIG_RISCV_FPU_DEBUG.

 There are no user-serviceable parts there. This debugging facility
is for real mechanics willing to get their hands dirty.  ;-)

Just a suggestion.

Of course it is - it's just nice to be able to quantify improvements 😉

I'll try to come up with a good FPU switching benchmark test in a
separate PR. But that might take some time.

OK... The trap overhead I mentioned earlier is now gone.
With the patch I just pushed on top, things are now optimal
in all cases

Hey @npitre,
Just to say, I applied your patches on top of our SMP patch set with some minor tweaks so the patches would apply and ran the fpu_sharing_generic test. It built and ran successfully on our mpfs_icicle platform. I will attach the output. are these the kinda figures you are expecting?
here are some KCONFIG options that I set:
CONFIG_SMP=y
CONFIG_MP_MAX_NUM_CPUS=4
CONFIG_MAIN_STACK_SIZE=4096
CONFIG_ISR_STACK_SIZE=4096
CONFIG_IDLE_STACK_SIZE=4096
CONFIG_TEST_EXTRA_STACK_SIZE=4096
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096
Also as a note, I always have to bump up the stack sizes for our platform, but I guess that is a topic for another day.
Cheers!
fpu_sharing_generic_output.log

Hey @npitre, Just to say, I applied your patches on top of our SMP patch set with some minor tweaks so the patches would apply and ran the fpu_sharing_generic test. It built and ran successfully on our mpfs_icicle platform. I will attach the output. are these the kinda figures you are expecting?
here are some KCONFIG options that I set: CONFIG_SMP=y CONFIG_MP_MAX_NUM_CPUS=4 CONFIG_MAIN_STACK_SIZE=4096 CONFIG_ISR_STACK_SIZE=4096 CONFIG_IDLE_STACK_SIZE=4096 CONFIG_TEST_EXTRA_STACK_SIZE=4096 CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096
Also as a note, I always have to bump up the stack sizes for our platform, but I guess that is a topic for another day.
Cheers! fpu_sharing_generic_output.log

@con-pax - Could you please run the same benchmark without @npitre 's commit? That will help us to get an idea of the speedup.

Hey @cfriedt, I can!
here is the test using the same same set up, except with none of the commits from this PR. We can see the improvement in the test_load_store. I think approx 9%
fpu_sharing_generic_output_no_npitre_commits.log

hi,
just merged  `upstream/main'  into my tree and see that this change results in a regression for my test-case:
Find the test in my tree here
looking into it the changes I found that:
static bool fpu_access_allowed(unsigned int exc_update_level)
{
	__ASSERT((csr_read(mstatus) & MSTATUS_IEN) == 0,
		 "must be called with IRQs disabled");
	if (_current->arch.exception_depth == exc_update_level) {
		/* We're about to execute non-exception code */
		if (_current_cpu->arch.fpu_owner == _current) {
			/* everything is already in place */
			return true;
		}
		if (_current->arch.fpu_recently_used) {
[...]
			z_riscv_fpu_load();
			_current_cpu->arch.fpu_state = MSTATUS_FS_CLEAN;
			return true;
		}
		return false;
	}

In my setup neither of the two condition potentially resulting in returning true result in taking the path to return true. As a consequence FPU regs seem to never be saved.
I'm using configs like this:
	select CPU_HAS_FPU_DOUBLE_PRECISION
	select REQUIRES_FULL_LIBCPP
	select THREAD_NAME
	select FPU_SHARING

and many more you find here: https://github.com/pottendo/zephyr-pottendo/blob/main/boards/riscv/orangecart/orangecart_fpu_defconfig
Anything I've missed to activate?
My code used a construct like this when starting a thread:
#if defined(__ZEPHYR__) && defined(CONFIG_FPU)
	// make sure FPU regs are saved during context switch
	int r;
	if ((r = k_float_enable(k_current_get(), 0)) != 0)
	{
	    log_msg("%s: k_float_enable() failed: %d.\n", __FUNCTION__, r);
	}
#endif

with that the FPU was working as expecting in this multithreaded application.
Any ideas?
pottendo

@pottendo - you will need to file a bug, as we're past feature freeze in the release process for v3.3.
Thanks for reporting it.

For the record, I created a test to exercise all FPU context switching
decisions and found (and fixed) 2 bugs with it already.
I started looking at the issue reported by @pottendo and found another
bug, namely the frm instruction isn't trapped and cause an illegal
instruction exception (at least on QEMU). I'm not sure yet how to
reconscile that with the reported issue yet though.

For the record, I created a test to exercise all FPU context switching decisions and found (and fixed) 2 bugs with it already. I started looking at the issue reported by @pottendo and found another bug, namely the frm instruction isn't trapped and cause an illegal instruction exception (at least on QEMU). I'm not sure yet how to reconscile that with the reported issue yet though.

@npitre if there is anything you would like me to test on our platform, let me know.

I just created PR #54207 (with corresponding issue #54208) that includes
several fixes and a comprehensive test for this.


Revert "Revert "[ALLUXIO-1749] Make thrift largest frame size adjustable""

Reverts Alluxio/alluxio#2830
We are able to reproduce the problem of complaining frame size smaller than the default limit. As a result, we increase the frame size and add the support of customizing this value.

@apc999 Do we want to mark this experimental?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9748/
Test PASSed.

@calvinjia experimental marked

@calvinjia @jsimsa  thanks for the suggestion. I fixed your comments

LGTM

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9752/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9753/
Test PASSed.


feat: update actions progress

Codecov Report
Attention: Patch coverage is 88.63636% with 5 lines in your changes missing coverage. Please review.

Project coverage is 91.06%. Comparing base (58d6d72) to head (1a0bb3c).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

.../update-plan/update-actions-progress/controller.ts
87.50%
2 Missing :warning:

...eys/update-plan/update-actions-progress/schemas.ts
86.66%
2 Missing :warning:

server/routes/csip-records/controller.ts
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #259      +/-   ##
==========================================
- Coverage   91.13%   91.06%   -0.08%
==========================================
  Files         285      288       +3
  Lines        4265     4309      +44
  Branches      657      664       +7
==========================================
+ Hits         3887     3924      +37
- Misses        376      383       +7
  Partials        2        2

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


json: remove enable_shared_from_this

I was looking at https://github.com/envoyproxy/envoy/issues/1684
and noticed this. I doubt it's related but we should remove it if
not used.
Signed-off-by: Matt Klein<EMAIL_ADDRESS>

@danielhochman


Fix SRAM size for 45,46,56 devices

Closes #81
Please see the screenshots on the issue for details.

Thank you, @bbrown1867, looks good to me!


Pipelinerun status will not be set to PipelineRunStopping if pipeline contains finally tasks

Expected Behavior
The pipelinerun status should be set to PipelineRunStopping when any of taskrun fails and other taskruns are still running (though pipeline contains finally tasks)
Actual Behavior
The pipelinerun status is not set to PipelineRunStopping when any of taskrun fails and other taskrus are still running when pipeline contains finally tasks
Steps to Reproduce the Problem

Create a pipeline with 2 tasks and 1 finally task
Make sure that one of the tasks fails before the other one
Start the pipeline and observe the state of pipelinerun when one of the taskrun fails

Additional Info

Kubernetes version:
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.0+b3b92b2", GitCommit:"b3b92b2", GitTreeState:"clean", BuildDate:"2020-07-15T09:27:21Z", GoVersion:"go1.14.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"18+", GitVersion:"v1.18.3+002a51f", GitCommit:"002a51f", GitTreeState:"clean", BuildDate:"2020-08-10T05:10:21Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"linux/amd64"}

Tekton Pipeline version:

Client version: 0.11.0
Pipeline version: v0.14.3
Triggers version: v0.6.1

Command execution logs:
[varadhya@localhost testing]$ tkn tr ls
No TaskRuns found
[varadhya@localhost testing]$
[varadhya@localhost testing]$ tkn pr ls
No PipelineRuns found
[varadhya@localhost testing]$
[varadhya@localhost testing]$ tkn p start pipeline-test-timeout
? Value for param `first-param` of type `string`? check
PipelineRun started: pipeline-test-timeout-run-jndt9

In order to track the PipelineRun progress run:
tkn pipelinerun logs pipeline-test-timeout-run-jndt9 -f -n veeresh-testing
[varadhya@localhost testing]$
[varadhya@localhost testing]$ tkn pr ls
NAME                              STARTED         DURATION   STATUS
pipeline-test-timeout-run-jndt9   9 seconds ago   ---        Running
[varadhya@localhost testing]$
[varadhya@localhost testing]$
[varadhya@localhost testing]$ tkn tr ls
NAME                                                 STARTED          DURATION   STATUS
pipeline-test-timeout-run-jndt9-run-script-1-glh5t   18 seconds ago   ---        Running
pipeline-test-timeout-run-jndt9-run-script-2-jb2jw   18 seconds ago   ---        Running
[varadhya@localhost testing]$
[varadhya@localhost testing]$ tkn tr ls
NAME                                                 STARTED          DURATION   STATUS
pipeline-test-timeout-run-jndt9-run-script-1-glh5t   34 seconds ago   ---        Running
pipeline-test-timeout-run-jndt9-run-script-2-jb2jw   34 seconds ago   ---        Running
[varadhya@localhost testing]$
[varadhya@localhost testing]$
[varadhya@localhost testing]$ tkn tr ls
NAME                                                 STARTED        DURATION   STATUS
pipeline-test-timeout-run-jndt9-run-script-1-glh5t   1 minute ago   ---        Running
pipeline-test-timeout-run-jndt9-run-script-2-jb2jw   1 minute ago   1 minute   Failed
[varadhya@localhost testing]$
[varadhya@localhost testing]$ tkn pr ls
NAME                              STARTED        DURATION   STATUS
pipeline-test-timeout-run-jndt9   1 minute ago   ---        Running
[varadhya@localhost testing]$
[varadhya@localhost testing]$ kubectl get pr
NAME                              SUCCEEDED   REASON    STARTTIME   COMPLETIONTIME
pipeline-test-timeout-run-jndt9   Unknown     Running   92s
[varadhya@localhost testing]$ kubectl get pr
NAME                              SUCCEEDED   REASON    STARTTIME   COMPLETIONTIME
pipeline-test-timeout-run-jndt9   Unknown     Running   4m37s

/cc @pritidesai

yes this is by design. stopping mode with finally does not make sense because once a task fails, finally tasks are scheduled right after that first failure. For pipeline without finally, once a task fails, pipeline waits for other running tasks to complete and does not schedule any new task i.e. pipeline goes in stopping state.

The above link does not mention about the state PipelineRunStopping of pipelinerun, it only talks about the final state of the pipelinerun. I think it needs to be updated.
When I was going through the newly added features of v0.14.0, I found A new reason "PipelineRunStopping" indicate that the pipeline run has found a failure and is waiting for task runs to complete. and thought of testing that and I found that it does not work with finally so I filed this issue.
What is the expected state transition of the pipelinerun when there are multiple finally tasks running and one of it fails (since finally tasks are running, there will not be any new tasks to be scheduled), Is it Started -> Running -> Failed or Started -> Running -> PipelineRunStopping -> Failed?

Hi @VeereshAradhya PR #2774 introduced PipelineRunStopping for DAG tasks which was part of 0.14.0.

What is the expected state transition of the pipelinerun when there are multiple finally tasks running and one of it fails (since finally tasks are running, there will not be any new tasks to be scheduled), Is it Started -> Running -> Failed or Started -> Running -> PipelineRunStopping -> Failed?

The expected state transition in this case is  Started -> Running -> Failed like its documented here. Finally task failure does not transition into stopping state since expectation is rest of the final tasks have to be executed and pipeline keeps running until it finishes executing all finally tasks or it hits timeout.


Specifying which KMS key to be used for etcd data volume encryption

This feature request is derived from https://github.com/coreos/kube-aws/issues/383#issuecomment-284662241
Can we just reuse the key specified with kmsKeyArn for data volume encryption, too?

@swestcott I've created an another issue for your feature request

@mumoshu I've had a go at implementing this (https://github.com/swestcott/kube-aws/commit/394b1f0d634a7dde963d3c249d6ef993b0088e22), does this look like a sensible approach? If so, I'll add a test and sort out a PR.

Note to self (or whoever picks this up), attempting to reattach an encrypted volume errors with,
aws ec2 attach-volume --volume-id vol-xxx --instance-id i-yyy --device /dev/xvdf
An error occurred (CustomerKeyHasBeenRevoked) when calling the AttachVolume operation: Volume vol-xxx cannot be attached. The encrypted volume was unable to access the KMS master key.

Widening https://github.com/coreos/kube-aws/blob/master/core/controlplane/config/templates/stack-template.json#L275 ti kms:* works, but clearly overly permissive.

@swestcott Added a comment to your commit.

Thanks for your efforts there!
If I understand correctly, on top of your commit, just configuring cluster.yaml:
etcd:
  kmsKeyArn: <your key for volume encryption>

and adding the following policy:
{
  "Action" : "kms:Decrypt",
  "Effect" : "Allow",
  "Resource" : "{{$.Etcd.KMSKeyARN}}"
}

to our etcd IAM role would do the job without making it overly permissive?

@mumoshu During my testing I found kms:decrypt isn't sufficient to re-attach an encrypted volume on a new EC2 instance (see above CustomerKeyHasBeenRevoked error). I pinged AWS support last week and they've come back with the following suggestion which I'll try,
            "Action": [
                "kms:CreateGrant",
                "kms:Decrypt",
                "kms:Describe*",
                "kms:Encrypt",
                "kms:GenerateDataKey*",
                "kms:ReEncrypt*"
            ],

@swestcott Any news on this? 😈

The patch is done, just needs an end-to-end before I raise the PR. Having difficultly starting my cluster currently at the moment as etcd bootstrap is failing, both with and without my changes...


Cannot prepare the release because you have local modifications

Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) on project systemds: Cannot prepare the release because you have local modifications

Keep the repo clean without any uncommitted work.


Keysight 344xx: DIG option is always enabled with 3.0 firmware, also add MEM option

For two types of multimeters (34465A and 34470A) from this driver the digitizer option (aka DIG) has been enabled with firmware version 3.0.
This PR proposes a request that the digitizer is enabled when it is detecting the firmware version to be higher or equal to version 3.0. 3.0 is the correct firmware version to check against for all the 4 models because the previous version is 2.17, as stated in this release notes document.
Also add support for the 'MEM' option that changes the number of allowed pretrigger samples.
More documentation on the instruments can be found here:
https://www.keysight.com/en/pdx-2891457-pn-34465A/digital-multimeter-6-digit-truevolt-dmm
See page 26 of user manual:

Note that the firmware check will not mistakenly add DIG-enabled driver features to models 34460A and 34461A because the output of the _license() call for them will not contain 'DIG' ever.

We have learned from keysight that *OPT? which returns options is a better way to check for options as that will always work (as opposed to the license command) I suggest that we add a private function similar to _licenses() that does this? and use that in the has_dig and has_mem checks. That will be much more future proof


Handle empty responses in json

Responses with status 204 and 205 don't contain a body which causes response.json() to blow up (unlike response.text() et al).
I think the correct way to handle this is to return null.

This would need to apply to d3.text and probably every other fetch helper too, but I haven’t thought through yet whether this is the right approach.

@mbostock I've checked and none of the other Response methods throw an exception but returns an empty object of the respective type.
👉 https://beta.observablehq.com/@herrstucki/204

The spec seems clear that throwing is the desired behavior here, which would make it your responsibility to handle this condition. Related: whatwg/fetch#113 github/fetch#123 bitinn/node-fetch#165
The downside is that you’d have to handle it at the Fetch layer rather than at the d3-fetch layer, since presumably you’d want to check the response status code rather than catching any SyntaxError. So that might be an argument to return undefined rather than throwing… (I think undefined is more appropriate than null here.)

Yeah, that was my thinking too … and since d3-fetch already is an abstraction (and checks for response.ok), I think this would be the right place to handle it.


Incorrect environment name parameter in hooks script

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm install -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v14.18.2
Amplify CLI Version
7.6.4
What operating system are you using?
Ubuntu
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
In documentation, parameter structure in hooks scripts is following:
{
  "amplify": {
    "version": String,
    "environment": String,
    "command": String,
    "subCommand": String,
    "argv": [ String ]
  }
}

But, actually amplify.envionment is Object not String, and amplify.envionment.envName is actually the environment name.
Expected behavior
To access amplify.environment as String.
Reproduction steps

Create amplify/hooks/pre-status.js with the following contents.const fs = require('fs');
const parameters = JSON.parse(fs.readFileSync(0, { encoding: 'utf8' }));
console.log(parameters.data, parameters.error)

Run amplify status
The following content is output to the terminal----- 🪝 pre-status execution start -----
   {
     amplify: {
       environment: {
         projectPath: '/workspaces',
         defaultEditor: 'vscode',
         envName: 'dev'
       },
       command: 'status',
       argv: [
         '/usr/local/bin/node',
         '/usr/local/share/npm-global/bin/amplify',
         'status'
       ],
       version: '7.6.4'
     }
   } undefined
----- 🪝 pre-status execution end -----

GraphQL schema(s)
No response
Log output
No response
Additional information
No response

It looks like this was fixed by https://github.com/aws-amplify/amplify-cli/pull/9347, so I'll close this out.

Oops. #9347 was closed without merging, so I'll reopen this.


Question

Does the service survive a reboot, or will I need to start it every time?
Great work by the way :)

Thanks! 😁
The services is set to Automatic, so I'll start after a reboot automatically.


Login attempts should be limited

After ten incorrect attempts, a user account will be locked and
the user will be sent an email to enable them to unlock their
account. Alternately, their account will re-activate after 24
hours.
Closes #344

Coverage decreased (-0.03%) to 87.745% when pulling ec956d0f342e91b01b62288457dd40fbca743a42 on feature/lockable into 7d24e7b488537b0a29815da85cf32c06433ae980 on master.


'log writing failed' message while deploying microBOSH to AWS

I deploy microBOSH to AWS using light-bosh-stemcell-2776-aws-xen-hvm-ubuntu-trusty-go_agent stemcell. bosh micro deploy command writes error message while writing logs at the end.
Here is stdout output and supplementary information about deployment.

$ bosh micro deploy light-bosh-stemcell-2776-aws-xen-hvm-ubuntu-trusty-go_agent.tgz

No `bosh-deployments.yml` file found in current directory.

Conventionally, `bosh-deployments.yml` should be saved in /Users/lexsys/code.
Is /Users/lexsys/code/mkbosh a directory where you can save state? (type 'yes' to continue): yes
Deploying new micro BOSH instance `manifest.yml' to `Unknown Director' (type 'yes' to continue): yes

Verifying stemcell...
File exists and readable                                     OK
Verifying tarball...
Read tarball                                                 OK
Manifest exists                                              OK
Stemcell image file                                          OK
Stemcell properties                                          OK

Stemcell info
-------------
Name:    bosh-aws-xen-hvm-ubuntu-trusty-go_agent
Version: 2776

  Started deploy micro bosh
  Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)
  Started deploy micro bosh > Uploading stemcell. Done (00:00:06)
  Started deploy micro bosh > Creating VM from ami-96d141fe light. Done (00:00:41)
  Started deploy micro bosh > Waiting for the agent. Done (00:01:47)
  Started deploy micro bosh > Updating persistent disk
  Started deploy micro bosh > Create disk. Done (00:00:04)
  Started deploy micro bosh > Mount disk. Done (00:00:10)
     Done deploy micro bosh > Updating persistent disk (00:00:23)
  Started deploy micro bosh > Stopping agent services. Done (00:00:04)
  Started deploy micro bosh > Applying micro BOSH spec. Done (00:00:40)
  Started deploy micro bosh > Starting agent services. Done (00:00:02)
  Started deploy micro bosh > Waiting for the director. Done (00:00:05)
     Done deploy micro bosh (00:03:48)log writing failed. can't be called from trap context

Deployed `manifest.yml' to `Unknown Director', took 00:03:48 to complete
/Users/lexsys/.rvm/gems/ruby-2.0.0-p481/gems/net-ssh-2.9.1/lib/net/ssh/ruby_compat.rb:30:in `select': Bad file descriptor (Errno::EBADF)
  from /Users/lexsys/.rvm/gems/ruby-2.0.0-p481/gems/net-ssh-2.9.1/lib/net/ssh/ruby_compat.rb:30:in `io_select'
  from /Users/lexsys/.rvm/gems/ruby-2.0.0-p481/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:209:in `process'
  from /Users/lexsys/.rvm/gems/ruby-2.0.0-p481/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in `block in loop'
  from /Users/lexsys/.rvm/gems/ruby-2.0.0-p481/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in `loop'
  from /Users/lexsys/.rvm/gems/ruby-2.0.0-p481/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in `loop'
  from /Users/lexsys/.rvm/gems/ruby-2.0.0-p481/gems/bosh_cli_plugin_micro-1.2768.0/lib/bosh/deployer/remote_tunnel.rb:43:in `block in monitor_session'

manifest.yml
name: mkbosh

network:
  type: manual
  vip: <IP_ADDRESS>
  ip: <IP_ADDRESS>
  dns: [<IP_ADDRESS>]
  cloud_properties:
    subnet: subnet-f949d6c3

resources:
  persistent_disk: 20000
  cloud_properties:
    instance_type: t2.small
    availability_zone: us-east-1e

cloud:
  plugin: aws
  properties:
    aws:
      access_key_id: XXX
      secret_access_key: XXX
      default_key_name: bosh_lx
      default_security_groups: ["bosh_lx"]
      region: us-east-1
      ec2_private_key: ~/.ssh/bosh_lx.pem # Path relative to the manifest file

apply_spec:
  agent:
    blobstore: {address: <IP_ADDRESS>}
    nats: {address: <IP_ADDRESS>}
  properties:
    registry: {address: <IP_ADDRESS>}

$ gem list bosh
*** LOCAL GEMS ***

bosh-bootstrap (0.14.4)
bosh-director-core (1.2768.0)
bosh-registry (1.2768.0)
bosh-stemcell (1.2768.0)
bosh-template (1.2768.0)
bosh_aws_cpi (1.2768.0)
bosh_cli (1.2768.0)
bosh_cli_plugin_micro (1.2768.0)
bosh_common (1.2768.0)
bosh_cpi (1.2768.0)
bosh_openstack_cpi (1.2768.0)
bosh_vcloud_cpi (0.7.1)
bosh_vsphere_cpi (1.2768.0)

$ bosh status
Config
             /Users/lexsys/.bosh_config

Director
  Name       mkbosh
  URL        https://<IP_ADDRESS>:25555
  Version    1.2776.0 (00000000)
  User       admin
  UUID       5f0b4717-622b-42ed-b38f-f4bf87566015
  CPI        aws
  dns        enabled (domain_name: microbosh)
  compiled_package_cache disabled
  snapshots  disabled

Deployment
  not set

stemcell version(s) you are using
light-bosh-stemcell-2776-aws-xen-hvm-ubuntu-trusty-go_agent.tgz

Happened on my laptop too. Just in case you need a repro environment.

+1
Just occurred on my MacBook, OSX 10.10.5
ruby 2.1.3p242 (2014-09-19 revision 47630) [x86_64-darwin14.0]

Verifying stemcell...
File exists and readable                                     OK
Verifying tarball...
Read tarball                                                 OK
Manifest exists                                              OK
Stemcell image file                                          OK
Stemcell properties                                          OK

Stemcell info
-------------
Name:    bosh-aws-xen-hvm-ubuntu-trusty-go_agent
Version: 3063

  Started deploy micro bosh
  Started deploy micro bosh > Unpacking stemcell. Done (00:00:00)
  Started deploy micro bosh > Uploading stemcell. Done (00:00:25)
  Started deploy micro bosh > Creating VM from ami-e1577396 light. Done (00:00:34)
  Started deploy micro bosh > Waiting for the agent. Done (00:02:34)
  Started deploy micro bosh > Updating persistent disk
  Started deploy micro bosh > Create disk. Done (00:00:07)
  Started deploy micro bosh > Mount disk. Done (00:00:08)
     Done deploy micro bosh > Updating persistent disk
  Started deploy micro bosh > Stopping agent services. Done (00:00:02)
  Started deploy micro bosh > Applying micro BOSH spec. Done (00:00:39)
  Started deploy micro bosh > Starting agent services. Done (00:00:01)
  Started deploy micro bosh > Waiting for the director. Done (00:00:08)log writing failed. can't be called from trap context

Deployed `deployment.yml' to `https://<IP_ADDRESS>:25555', took 00:04:45 to complete
/Users/deejay/.gem/ruby/2.1.3/gems/net-ssh-2.10.0.beta1/lib/net/ssh/ruby_compat.rb:25:in `select': Bad file descriptor (Errno::EBADF)
	from /Users/deejay/.gem/ruby/2.1.3/gems/net-ssh-2.10.0.beta1/lib/net/ssh/ruby_compat.rb:25:in `io_select'
	from /Users/deejay/.gem/ruby/2.1.3/gems/net-ssh-2.10.0.beta1/lib/net/ssh/connection/session.rb:210:in `process'
	from /Users/deejay/.gem/ruby/2.1.3/gems/net-ssh-2.10.0.beta1/lib/net/ssh/connection/session.rb:170:in `block in loop'
	from /Users/deejay/.gem/ruby/2.1.3/gems/net-ssh-2.10.0.beta1/lib/net/ssh/connection/session.rb:170:in `loop'
	from /Users/deejay/.gem/ruby/2.1.3/gems/net-ssh-2.10.0.beta1/lib/net/ssh/connection/session.rb:170:in `loop'
	from /Users/deejay/.gem/ruby/2.1.3/gems/bosh_cli_plugin_micro-1.3063.0/lib/bosh/deployer/remote_tunnel.rb:43:in `block in monitor_session'

Now I use bosh-init to create bosh env and it works fine. See: https://github.com/cloudfoundry/bosh-init


SearchAttribute from DescribeWorkflowExecution return wrong type for Integer

Expected Behavior
Return the integer type
Actual Behavior
Return the float64 type
Steps to Reproduce the Problem
see https://github.com/temporalio/samples-go/pull/228
Specifications

Version:  go.temporal.io/sdk v1.17.0
Platform: MacOS

This is because you are choosing to use interface{} and converter.GetDefaultDataConverter().FromPayload which uses default Go JSON semantics which never returns an int. From https://pkg.go.dev/encoding/json#Unmarshal:

float64, for JSON numbers

If this is an issue, you can either: 1) pass in the type you want JSON to unmarshal to, or 2) you can create your own converter that leverages https://pkg.go.dev/encoding/json#Decoder.UseNumber and changes to int if needed.

interesting...
But it will be tedious to pass in the type because my code have to know it in advance.
I think Temporal should have all the information to convert it correctly, isn't it? If so I would still consider it as a bug in Temporal.

But it will be tedious to pass in the type because my code have to know it in advance.

Not necessarily. You can either have a custom converter or confirm that float64 will work for your needs.

I think Temporal should have all the information to convert it correctly, isn't it? If so I would still consider it as a bug in Temporal.

It could if we treated search attributes as different than any other integer in the system, but we do not. Same thing with memo. If you call converter.GetDefaultDataConverter().FromPayload(value, &object) like your example, and payload is a numeric value, you will be subject to default conversion rules. This goes for all of our payloads and is not unique to search attributes.

Correct, closing.


Resume issue with empty playlist

Hi,
thanks for the great plugin and continuation of the work, I just switched in one  of my installations from sonospollytts to here.
** Issue **
When my playlist is empty, somehow the TTS track played (ownfile and normal) gets added to the playlist, or is at least set as the last song played in sonos. So I get some weird echo effect, when playing a second time, or it repeats the original message, when playing a new message right after the first one.
With one song in the playlist this behavior is gone.
Is it possible to handle this "empty playlist" issue, with removing all items from sonos, before playing, e.g. the next tts?
I'm still on sonos version 1. Wether this is causing the issue I can not verify.

Hi
It’s very strange, because sonos shouldn’t add the tts to the playlist.
if the playlist is empty, tts-ultimate will skip resuming it.
I’m on sonos v2.
Leave me some time to get my old v1 and to test it.

Ok, i'm able to reproduce the issue.
I'm working on that.
A Fix should be out in about 2 hours.
I'll keep you advised...

Hi,
<EMAIL_ADDRESS>is out with that fix.
Please try it as soon as you see it in the palette and remember to star my node if you find it useful.
Thanks

Thanks for the quick fix, tested and works now as expected.

Thank you!


Development

I got false impression that PR were merged into main. I will try to rebase this changes now

Rebased. I'm testing it and will merge after


unable to download files with space in file name

Some files with space in their name can not be downloaded. I have tried using Url Encoding but that does not helps. I can download these file using Firefox or Chrome on PC.

can you give me the url address and the version of the file-downloader, i test "http://<IP_ADDRESS>/ftp/image/shop/product/Kids Addition & Subtraction 1.0.apk" that with space goes right in version 0.3.2.

version 0.3.2 has been solved


[BUG] Biotea is unusable due to breaking changes in the packaging package

Describe the bug
All commands crash due to LegacyVersion being removed in the packaging package. Biotea version 1.0.3.
To Reproduce
Steps to reproduce the behavior:

Install biotea
Run any command

Limiting the package's version fixed the issue. However, I'm keeping this open as a reminder to migrate away from LegacyVersion.


Update Set-CsEnhancedEmergencyServiceDisclaimer.md

Resolves MicrosoftDocs/office-docs-powershell#9422

Docs Build status updates of commit ebd1c59:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsEnhancedEmergencyServiceDisclaimer.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8f1a7e6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsEnhancedEmergencyServiceDisclaimer.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 687a344:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsEnhancedEmergencyServiceDisclaimer.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@dariomws @tseward @get-itips

@tiburd Please merge this PR. Thanks

Docs Build status updates of commit 98ffbdb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Set-CsEnhancedEmergencyServiceDisclaimer.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Json object improvements.

Reviewers: @scottschurr @nbougalis
If this code looks familiar, it's because it's most of https://github.com/ripple/rippled/pull/832 and has already been reviewed and approved as sch!
Unfortunately, that branch includes a transaction change so it sits around.  I'm extracting the non-breaking changes into a separate change so I can get 'em out...

I don't see any way to do that while still preserving the forward declaration...?

(I did move the two big functions into the .cpp.  The remaining ones will almost certainly want to be inlined anyway as they are near trivial...)

Tom, since you seem to spend some time in the *ToJson stuff, what would you think of turning the LEDGER_JSON_* #defines in Ledger.h into an enum?  Not necessary for this pull request.  Just a tidy thing to do at some point.  Thanks.

LEDGER_JSON_ - wince, this was on my list.  OK, on it right now (in another window!)

(i.e., I didn't write that but I knew it was there... :-))

Interesting.  Line 176 of JsonObject.h may be the first case I've ever seen of protected inheritance.  Does the fact that Array uses private inheritance (line 235) suggest that Array should be marked final?

Done, in https://github.com/ripple/rippled/pull/891.

Looks good to me.
:+1:

Fixed the spelling mistake and the include guards too.

The protected inheritance was a suggestion of Howard's, since I never used the base class.  I don't see any particular reason to prevent inheritance, barring any negative consequence from it.   But perhaps we should be marking classes as final by default and changing them if needs be?
Anyway, I didn't change that.  :-)

Regarding final, my inclination has been to mark anything that wasn't specifically intended to be inherited from as final.  And my usual test for whether the class was designed for inheritance is if inheritance actually happens.  That's a luxury we can take since we're not developing library code.  I think the advantage of this conservative approach is, if someone does choose to inherit from a class, they'll know right away that there might be some work to do.  But it's not a big deal.  It's just an inclination I have.

@HowardHinnant Which standard library classes are marked final?

I just did a search in the latest C++17 draft.  I'm counting zero.

I didn't notice I was tagged as a reviewer on this - will get on it right now.
On the topic of final: I personally tend to think of it as nothing more than window dressing; it's unclear to me that it provides any real, tangible benefit, unlike, e.g. override. I'm not going to complain if we add it judiciously when encountering cases during work on business logic, but at the same time, I don't want us to go out of our way to do so.

final is like making sure the deck chairs are lined up on the Titanic

Ping!
Do remember that this already got approved as part of https://github.com/ripple/rippled/pull/832...

Needs to be squashed down

The first three changes are essentially separate.  Unfortunately, patching the last change back would involve major surgery due to the move that happened...

(Next time I'll do the move first...)

What's wrong with squashing them all down into one commit with this message?
Refactor treament of JSON:
* Better integration between JsonObject and Json::Value
* Move streaming Json objects to ripple/json
* Replace Json::JsonException with std::logic_error
* Move functions to Object.cpp; fix include guards.

Fixed the vcxproj!
I don't want to squash the huge move - which doesn't change behavior - with the change before it or the change after it.  I did squash away one change in there... :-)

@rec Fine.
:+1:


Add Couchbase to database services

Adds Couchbase to the list of database services. Confirmed Couchbase server is running locally and compiling of takeout CLI worked.

Thanks @therobfonz!!


Parameters within the object can be modified

When the parent page passes Object parameters to the child page，the parameters within the object can be modified on the child page

Hi @xiaojieonly,
Thanks for filing the issue could you please provide a minimal reproducible code with the exact steps with expected vs actual results along with the output of flutter doctor -v. This will help to better address the issue.
Thank you.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


Add link to cdwv/awesome-helm

Please consider linking to the awesome-helm repository, where we're maintaining a list of great Helm resources

CLA signed.


Crash on Startup after Copy Files

Description
I just tried to copy (not mving) two files from one folder to another.
The app didnt made any copy but stated the the process is done. I tried it several times, but nothing happened.
Then the tool crashed and now i cannot open it again, because it crashes everytime on launch
Steps To Reproduce
No response
Expected behavior
it should copy the files to the other location
Files Version
<IP_ADDRESS>
Windows Version
Windows: Windows 10 PRO
Version: 21H1
Relevant Assets
here is the logfile:
 2021-11-09 18:10:46.7170|INFO|OnLaunched|App launched. Prelaunch: False 2021-11-09 18:10:47.2430|INFO|GetDrivesAsync|Drive added: C:\, Fixed 2021-11-09 18:10:47.2820|INFO|GetDrivesAsync|Drive added: D:\, Fixed 2021-11-09 18:10:47.3210|INFO|GetDrivesAsync|Drive added: E:\, Fixed 2021-11-09 18:10:47.3531|INFO|GetDrivesAsync|Drive added: F:\, Fixed 2021-11-09 18:10:47.3856|INFO|GetDrivesAsync|Drive added: G:\, Fixed 2021-11-09 18:10:47.4311|INFO|GetDrivesAsync|Drive added: H:\, CDRom 2021-11-09 18:10:47.4597|INFO|GetDrivesAsync|Drive added: I:\, Fixed 2021-11-09 18:10:47.4957|INFO|GetDrivesAsync|Drive added: W:\, Network 2021-11-09 18:10:47.5257|INFO|GetDrivesAsync|Drive added: X:\, Network 2021-11-09 18:10:47.5577|INFO|GetDrivesAsync|Drive added: Y:\, Network 2021-11-09 18:10:47.5893|INFO|GetDrivesAsync|Drive added: Z:\, Network 2021-11-09 18:10:48.0006|INFO|EnumerateDrivesAsync|Adding cloud provider "Dropbox" mapped to E:\Dropbox 2021-11-09 18:10:48.0742|INFO|EnumerateDrivesAsync|Adding cloud provider "OneDrive" mapped to E:\OneDrive 2021-11-09 18:12:09.5225|INFO|IsRunningOnArm|Running on ARM: False 2021-11-09 18:13:19.4175|INFO|IgnoreExceptions|Object reference not set to an instance of an object. 	System.NullReferenceException: Object reference not set to an instance of an object.    at Files.Views.LayoutModes.GridViewBrowser.GridViewBrowser_obj27_Bindings.Update_LoadFileIcon(Boolean, Int32) + 0x43    at Files.Views.LayoutModes.GridViewBrowser.GridViewBrowser_obj27_Bindings.GridViewBrowser_obj27_BindingsTracking.PropertyChanged_(Object, PropertyChangedEventArgs) + 0x3fa    at System.Action2.InvokeMulticastThunk(T1, T2) + 0x4e
at System.EventHandler`1.Invoke(Object, TEventArgs) + 0x2e
at Microsoft.Toolkit.Mvvm.ComponentModel.ObservableObject.SetProperty[T](T&, T, String) + 0x9c
at Files.Filesystem.ListedItem.<Img_ImageOpened>b__80_0() + 0x1e
at System.Action.Invoke() + 0x25
at Files.Common.Extensions.IgnoreExceptions(Action, Logger) + 0x22
2021-11-09 19:20:21.4180|WARN|SendMessageForResponseAsync|Error sending request on pipe.
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xad
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
at Files.Helpers.NamedPipeAsAppServiceConnection.d__12.MoveNext() + 0x24d
2021-11-10 17:05:12.6562|WARN|SendMessageForResponseAsync|Error sending request on pipe.
System.Threading.Tasks.TaskCanceledException: A task was canceled.
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0xad
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
at Files.Helpers.NamedPipeAsAppServiceConnection.d__12.MoveNext() + 0x24d
2021-11-10 17:27:32.2181|INFO|OnActivated|App activated by CommandLineLaunch
2021-11-10 17:27:59.2483|INFO|OnLaunched|App launched. Prelaunch: False
2021-11-10 17:28:03.9983|INFO|OnActivated|App activated by CommandLineLaunch
2021-11-10 17:28:07.7826|INFO|OnActivated|App activated by CommandLineLaunch
2021-11-10 17:28:20.5270|INFO|OnActivated|App activated by CommandLineLaunch
2021-11-10 17:29:47.0637|INFO|OnLaunched|App launched. Prelaunch: False
2021-11-10 19:39:33.9908|INFO|OnLaunched|App launched. Prelaunch: False
2021-11-10 19:40:00.2638|INFO|OnLaunched|App launched. Prelaunch: False
2021-11-11 07:46:32.1374|INFO|OnLaunched|App launched. Prelaunch: False
2021-11-13 13:12:26.6783|INFO|OnLaunched|App launched. Prelaunch: False`

@Rockatweb is this still an issue in the preview version? http://files.community/download/preview


[RFC] Create AzureIngressManagedListener CRD

Create a new Kubernetes custom resource definition (CRD) AzureIngressManagedListener, which will define a top level parent of the resources our Ingress Controller is allowed to mutate.
The AzureIngressManagedListener objects will be created by the AKS administrator.
A sample YAML creating new instances of this resource would have the following shape:
apiVersion: "appgw.ingress.k8s.io/v1"
kind: AzureIngressManagedListener
metadata:
  name: ingress1-managed-listener
spec:
  host: "www.contoso.com"
  port: 80
  path: "/bar/*

AKS administrator would make multiple AzureIngressManagedListener objects in order to control multiple ports/hosts/URLs.

See: https://github.com/Azure/application-gateway-kubernetes-ingress/pull/267


Correct management domain bind to IP <IP_ADDRESS>

Current document mention domain contosointernalvnet.management.azure-api.net bind to IP <IP_ADDRESS> is not correct. The correct IP for contosointernalvnet.management.azure-api.net should be <IP_ADDRESS> where can access port 3443.

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

ID: c0666302-7986-481e-97a0-2515d5c60210
Version Independent ID: 2d45104c-c3ec-4432-ea6f-117ca53ed8cb
Content: Connect to an internal virtual network using Azure API Management
Content Source: articles/api-management/api-management-using-with-internal-vnet.md
Service: api-management
GitHub Login: @dlepow
Microsoft Alias: danlep

@dlepow
Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@thohng - Thanks for submitting this PR. In the documentation we provide the IP address <IP_ADDRESS> just as an example, and as documented the private IP address is expected to be the same for all of the API Management instance's endpoints: gateway, management, developer portal, etc. This PR would result in a different address <IP_ADDRESS> specifically for the management endpoint. Is this what you intend?

Hi @dlepow, yub I understand that the private IP <IP_ADDRESS> is just an example. During exploration, we found that in the Internal VNet integration mode the management endpoint at n.n.n.4 is different IP with the rest, the gateway, developer portal, scm, etc will be the same IP at n.n.n.5. We actually did not use the direct management endpoint but this is the result when we validating. We also notice that the private IP <IP_ADDRESS> will be the outbound IP.
Unlike Public IP or External VNet mode, where all components gateway, management, developer portal, scm, etc could be same public IP Address.
For example, if we setup Internal VNet to the subnet <IP_ADDRESS>/26 (for example), then they will be:
<IP_ADDRESS> apim-dev.azure-api.net
<IP_ADDRESS> apim-dev.portal.azure-api.net
<IP_ADDRESS> apim-dev.developer.azure-api.net
<IP_ADDRESS> apim-dev.management.azure-api.net
<IP_ADDRESS> apim-dev.scm.azure-api.net

Thanks for providing the detail @thohng! I will consult with the engineering team to see what changes we should make to the documentation.

@solankisamir @ferantoMSFT  - In internal VNet mode is it expected that the management IP address is different from the IP address for other API Management endpoints (gateway etc.)? Thanks


Running time Algorithm solution in JAVA

Solved issue #525
In Language- JAVA

[x] Updated README Link
[x] Added code with comments

Thanks for contributing!

There's only one program here

updated


[READY] Implement Sortable where possible

As proposed in #8, I'm implementing a Sortable system.
Agenda:

Rename CachedStore in CachingDecorator ✔
Create a SortableStore interface for sortable stores ✔
Create a SortableDecorator with a sort() method that use an array for an in-memory sort for others ✔
Implement sort() for native sortable stores WIP

I'm currently wondering if I should create a Decorator namespace and a Decorator interface (as with this PR and the PR about countable, we will have 3 decorators). What do you think?

Thanks for working on this @tgalopin! Looks good :) Sure, you can add a Decorator namespace if you like.

I think I'll stay like that after all. Decorators are just specific stores (they implement the same API) so it's not that incoherent.

I think it's ready as I'm going to fix the Scrunitizer problems in another PR (#11). What do you think @webmozart ?

Could you rebase, squash, push -f and fix the StyleCI issues please?

I'm not sure of my squash, is it fine for you?

-> IRC

Could you add tests for the SortableDecorator please?

We still have the @return void problem in Scrunitizer but other than that, it seems fine :) .

Thanks @tgalopin! :)


SkyscanReconImport Batch Mode log file order

Describe the bug
SkyscanReconImport Batch Mode shows log files out of order, making it difficult to use.
To Reproduce
Steps to reproduce the behavior:

Go to SkyscanReconImport and select batch mode
Select a directory with multiple scans
Push Find Log files button

Expected behavior
Log files should be shown in a logical order (preferably alphabetical)
Desktop (please complete the following information):

OS: Linux

Additional context
It might be helpful to give the user multiple options of how to sort them (e.g., alphabetical, most recent, A to Z, Z to A)

what is the situation of this @oothomas.

#360 complete with tutorial update.


Redefine window dimensions calculation

What does this PR?

Previously we were calculating window dimensions in a utility method "getWindowDimensions" and inside our theme file. Problem with this approach was on certain devices like android tablets when orientation is set to landcsape and ececny is opened it miscalculate the dimensions because due to our orientation locking mechanism it lcoks the orientation to portrait but dimensions calculated at start doesn't change causing distorted and broken layout.
In this PR, we are using useWindowDimension hook in our main application container and storing the dimensions in redux. And after that using these dimensions from redux into stateful components. I this way whenever orientation changes, useWindowDimensions get aware of dimension changes and it updates redux and redux updates the UI according to new dimensions
Issue number
fixes #2449
Screenshots/Video
Screen record after changes. These changes are only done in header/tabbar and feedscreen.
https://user-images.githubusercontent.com/48380998/194387128-29e27b14-3e33-47f6-9bf4-02eee6f210a0.mp4

@noumantahir this is the video before. When ecency is launched in landscape locked, UI got messed up. And this is because is is taking the landscape dimensions but UI is locked in portrait and UI is not updating because dimensions are not inside stateful component and hence not able to update UI if dimensions get updated
https://user-images.githubusercontent.com/48380998/194388548-be4846c4-811f-4e09-a25e-4f70f5f29dc5.mp4

@aliseyalvi this has some conflicts

@feruzm don't merge this. Maybe we can discard this. This was created to fix renering issue on chromebook and android tablet but that is fixed in separate PR with some other trick.


Casting to google nest groups fails (sort off)

What version of Music Assistant has the issue?
2.0.0b63
The problem
When playing streaming radio via MA and then tts.cloud a message to 1 single speaker, all is OK

Music plays
music stops
message is played (without the ' ding'  announcement sound)
music continues.

When doing the same thing, but then cast the message to a google speaker group (3 google devices, containing also the speaker above)) the message is played multiple times

Music plays
music stops
message is played (without the 'ding' announcement sound)
message is played again...
message is played again.....
music continues.

How to reproduce
Play music via the radio browser to one single speaker.

Play the message to the same (one) speaker:

All is good.
Play the message to a google speaker group (speaker group made in the google home app and contains 3 speakers):

The message is played 3 times...
Relevant log output
Music Assistant BETA
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/music.py", line 331, in get_item
return await self.mass.get_provider("url").parse_item(item_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/url/init.py", line 106, in parse_item
item_id, url, media_info = await self._get_media_info(item_id_or_url, force_refresh)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/url/init.py", line 174, in _get_media_info
media_info = await parse_tags(url)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/helpers/tags.py", line 357, in parse_tags
raise InvalidDataError(f"Unable to retrieve info for {file_path}: {str(err)}") from err
music_assistant.common.models.errors.InvalidDataError: Unable to retrieve info for https://my.ha.com:8123/api/tts_proxy/48a030bc7d17da7efaf3beb706a2fe9c2aaa4d1d_nl-nl_e09b5a0968_cloud.audiooutput.mp3: Server returned 404 Not Found
2023-08-02 20:26:30.149 ERROR (MainThread) [music_assistant.webserver] [140661638189904] Error handling message: CommandMessage(message_id=2, command='music/albums/get_album', args={'item_id': '4', 'provider_instance_id_or_domain': 'library'})
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/webserver.py", line 372, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/media/albums.py", line 71, in get
album = await super().get(
^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/media/base.py", line 165, in get
library_item = await self.get_library_item_by_prov_id(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/media/base.py", line 303, in get_library_item_by_prov_id
return await self.get_library_item(item_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/media/base.py", line 292, in get_library_item
raise MediaNotFoundError(f"{self.media_type.value} not found in library: {db_id}")
music_assistant.common.models.errors.MediaNotFoundError: album not found in library: 4
2023-08-02 20:26:31.226 ERROR (MainThread) [music_assistant.webserver] [140661638189904] Error handling message: CommandMessage(message_id=7, command='music/recently_played_items', args={'limit': 10, 'media_types': ['track', 'radio']})
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/helpers/tags.py", line 346, in parse_tags
raise InvalidDataError(error["string"])
music_assistant.common.models.errors.InvalidDataError: Server returned 404 Not Found
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/webserver.py", line 372, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/music.py", line 301, in recently_played
item = await self.get_item(media_type, db_row["item_id"], db_row["provider"])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/music.py", line 331, in get_item
return await self.mass.get_provider("url").parse_item(item_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/url/init.py", line 106, in parse_item
item_id, url, media_info = await self._get_media_info(item_id_or_url, force_refresh)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/url/init.py", line 174, in _get_media_info
media_info = await parse_tags(url)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/helpers/tags.py", line 357, in parse_tags
raise InvalidDataError(f"Unable to retrieve info for {file_path}: {str(err)}") from err
music_assistant.common.models.errors.InvalidDataError: Unable to retrieve info for https://my.ha.com:8123/api/tts_proxy/48a030bc7d17da7efaf3beb706a2fe9c2aaa4d1d_nl-nl_e09b5a0968_cloud.audiooutput.mp3: Server returned 404 Not Found
2023-08-02 20:26:40.979 INFO (ThreadPoolExecutor-0_3) [pychromecast.controllers] Receiver:Launching app CC1AD845
2023-08-02 20:34:14.554 INFO (ThreadPoolExecutor-0_0) [pychromecast.controllers] Receiver:Launching app CC1AD845
2023-08-02 20:42:25.130 INFO (ThreadPoolExecutor-0_1) [pychromecast.controllers] Receiver:Launching app CC1AD845
2023-08-02 20:42:41.740 INFO (ThreadPoolExecutor-0_3) [pychromecast] Quitting current app
2023-08-02 20:42:41.741 INFO (ThreadPoolExecutor-0_3) [pychromecast.controllers] Receiver:Stopping current app 'CC1AD845'
2023-08-02 20:42:43.971 INFO (ThreadPoolExecutor-0_8) [pychromecast.controllers] Receiver:Launching app CC1AD845
2023-08-02 20:47:16.792 ERROR (MainThread) [music_assistant.webserver] [140661993153104] Error handling message: CommandMessage(message_id='515508a1d8b54cd9aaed04354ef94f15', command='players/queue/play_media', args={'queue_id': 'e42f75a7-2a3d-4d00-84b6-de770cb5353e', 'media': 'https://my.ha.com:8123/api/tts_proxy/a6cb4243dd9b6d56c4188f1da57377d5073ac296_en-gb_e09b5a0968_cloud.audiooutput.mp3', 'option': 'play', 'radio_mode': False})
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/webserver.py", line 372, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/player_queues.py", line 280, in play_media
await self.play_index(queue_id, cur_index)
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/player_queues.py", line 519, in play_index
raise FileNotFoundError(f"Unknown index/id: {index}")
FileNotFoundError: Unknown index/id: 1
2023-08-02 20:48:18.103 ERROR (MainThread) [music_assistant.webserver] [140661595018256] Error handling message: CommandMessage(message_id=10, command='music/recently_played_items', args={'limit': 10, 'media_types': ['track', 'radio']})
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/helpers/tags.py", line 346, in parse_tags
raise InvalidDataError(error["string"])
music_assistant.common.models.errors.InvalidDataError: Server returned 404 Not Found
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/webserver.py", line 372, in _run_handler
result = await result
^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/music.py", line 301, in recently_played
item = await self.get_item(media_type, db_row["item_id"], db_row["provider"])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/controllers/music.py", line 331, in get_item
return await self.mass.get_provider("url").parse_item(item_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/url/init.py", line 106, in parse_item
item_id, url, media_info = await self._get_media_info(item_id_or_url, force_refresh)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/providers/url/init.py", line 174, in _get_media_info
media_info = await parse_tags(url)
^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/music_assistant/server/helpers/tags.py", line 357, in parse_tags
raise InvalidDataError(f"Unable to retrieve info for {file_path}: {str(err)}") from err
music_assistant.common.models.errors.InvalidDataError: Unable to retrieve info for https://my.ha.com:8123/api/tts_proxy/48a030bc7d17da7efaf3beb706a2fe9c2aaa4d1d_nl-nl_e09b5a0968_cloud.audiooutput.mp3: Server returned 404 Not Found
Additional information
No response
What version of Home Assistant Core are your running
2023.07.03 and 2023.08.01
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

I have tried re-producing the same thing several times, sometimes I succeed, but just now I tried and then it plays the test message in the test-window one time, and then I previous (different) test message I used earlier, another 3 times and then continues playing radio.
Sometimes the radio does not continue after playing the test-message.
I am getting very unpredictable behaviour.

Thanks for the extra testing. We will get to this in due course.

Just an update. This will be fixed when the TTS implementation is finished. It is on the roadmap but ETA still unknown. Thanks for your patience

Great, thx!

Any updates on TTS? I see it as in progress on the projects but i dont see any branch or anything associated with the feature. Would really love this to get implemented so i can switch over from LMS.

It is being worked on. There is a desire to have this done by the end of the month but it depends on workload.

This one has been implemented. Please test with beta124 (and beta125 even has a few follow up fixes for TTS/announcements)


Passing current /

Ask your Question
So I'm probably missing something fundamental; but is there an example of passing the currently active page to a child?
I'm doing something very similar to the Basic example, but I would like to pass the current active page to a child. Unfortunately setting a state variable using the selectPageCallback re-renders the parent, and the animated view goes back to the initialPage={0} basically just flickers back.
This happens as soon as you set any kind of state variable.
Would love any pointers or ideas! (quite a react novice so I'm probably just doing something very bad :) )
Some of my sample code:
 const setPage = useCallback(
    (page) =>
      pagerRef.current?.setPage(page),
    []
  );

  const data = [
    {
      key: 0,
      title: 'A good child,
      view: <ChildView nextPage={setPage}></ChildView >,
      ...
    },

<AnimatedPagerView
        style={{ flex: 1 }}
        initialPage={0}
        ref={pagerRef}
        scrollEnabled={true}
        draggable={true}
        onPageScroll={onPageScroll}
        onPageSelected={onPageSelected}
      >
        {useMemo(() => {
          return data.map(({ key, title, view }) => (
            <View key={key}>
              {view}
            </View>
          ));
        }, [data])}
      </AnimatedPagerView>
      ```

Now in my world I would do something like this:

const onPageSelected = useCallback(({ nativeEvent }) => {
setActivePage(nativeEvent.position);
}, []);

facing the same issue 🥲

You could set your initialPage to the activePage initialPage={activePage}
I think that would solve the flicker.

Please use usePagerView hook.


Create new Provider for self-testing / admin

We shouldn't rely on luminus as a sole provider. We can't even create a dev team admin account or mock student / staff accounts as a result.

Done in b13fd9880acccfc0e64eaaef2554231103b50b8f.


t Subscribe

Thank you for bringing this to my attention
when I merged updates from the main theme, part of the localization was lost, now I fixed everything I could find


Unified swagger.json across multiple versions?

Dear all,
for my dotNetCore project, I need to implement a second API version and would love to use this nugget package.
It looks very promising and I like how swagger can display multiple versions.
However, one customer of my API uses the openapi-generator-cli  to automatically generate a client for the api.
They have asked whether it would be possible to provide them with a unified swagger.json including all paths of all versions so that they can control which version they use per method.
I have been playing with the startup.cs and tried some things but did not succeed.
My plan was to use an environment variable to set whether one unified swagger.json or multiple should be created.
That way I could set this value to generate the swagger.json for them and normally run it in my environment to have the beautiful multi environment swagger documentation and the unified one showing all paths of the application with among all versions.
Thank you for your help,
Philipp

This isn't really possible. Open API (Swagger) documents have no concept of versioning or even grouping within a document. Every defined path in the document must be unique, which is impractical for most forms of versioning. Finally, even if you could combine everything into a single document, how would the generator understand how to separate things out? I'm not aware of any client code generator that supports parallel version generation or method overloads in a single client. Clients are typically bound a specific version so code generating for a specific version is the most appropriate behavior.
The only possible way I know that you could make this work is if you version by URL segment. The works because the version in the path produces distinct paths. I highly discourage that because it's not RESTful (it violates the Uniform Interface constraint). Should you attempt to take this path, I still suspect that client code generation would be strange or would not work at all. I'm not super familiar with how it would disambiguate things, but it has historically been a problem for code-generated proxies.
My recommendation for the cleanest, simplest solution is to use one document per version and generate one client per version. I suspect most clients will not be bound to more than one version at time. I can't imagine a single scenario where it would more than two, but perhaps some scenario exists.

Thank you for this fast and very detailed response!
I will go with own clients per version!


!add-season does not set --end-date correctly

End date is never set with !add-season and must be edited manually.

Nvm I once again forgot that the parameter name is --end-date-exclusive instead of --end-date.


Kebab: Mediasoup-client and small patches

Check out the new example (mediasoup-audio) for audio usage. Also, there is no Node support yet, but it will be added soon.

anyone wanna review this or do you just trust my code


fix trailing , explicitly check for string type, dump object type

This PR does 3 things:

with these changes numerical values (int, float, etc..) would now be using the fallback output style using var_dump instead of the nl2br() output that applied before. This is a slight change in behaviour which you might not want in a "hotfix" - let me know and I will restore the previous behaviour for numericals
fixed: objects that didn't resolve to true for is_array in the data.phtml view no longer throw warnings for attempting to echo them using nl2br. This is achieved by defaulting to a var_dump instead, which results in a behaviour change described in 1)
fixed: without xdebug loaded, the output of arrays in array.phtml allowed html to be rendered unescaped, which broke the toolbar (think writing cms content into the cache). This was solved by starting a buffer and applying htmlentities. The behaviour for the new var_dump fallback also requires this.

Thanks for the PR!


Switch from golang builder image to ubi8

What this PR does / why we need it:
Switch from golang builder image to ubi8
this pr changes golang builder image to ubi8 minimal, due to
dockerhub rate limits.
Special notes for your reviewer:
Release note:
NONE

Signed-off-by: Karel Šimon<EMAIL_ADDRESS>

@ksimon1 I think you are missing wait-for-vmi-status Dockerfile

/lgtm


Do square brackets index into maps? Docs unclear.

On page: https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-workflow-definition-language
This table appears:

operator
task

'
To use a string literal as input or in expressions and functions, wrap the string only with single quotation marks, for example, '<myString>'. Do not use double quotation marks (""), which conflict with the JSON formatting around an entire expression. For example:Yes: length('Hello')No: length("Hello")When you pass arrays or numbers, you don't need wrapping punctuation. For example:Yes: length([1, 2, 3])No: length("[1, 2, 3]")

[]
To reference a value at a specific position (index) in an array, use square brackets. For example, to get the second item in an array:myArray[1]

.
To reference a property in an object, use the dot operator. For example, to get the name property for a customer JSON object:"@parameters('customer').name"

?
To reference null properties in an object without a runtime error, use the question mark operator. For example, to handle null outputs from a trigger, you can use this expression:@coalesce(trigger().outputs?.body?.<someProperty>, '<property-default-value>')

I am almost certain that square brackets also let you access values in maps.
From examples, e.g. the set/add/remove property functions all have example text that include something very much look like that's what's happening:

setProperty(<object>, '<parent-property>', addProperty(<object>['<parent-property>'], '<child-property>', <value>)
                                                                ^here

And partially from some logic apps we have at our company that use it like a map indexing operator, e.g.:

lastIndexOf(triggerBody()?['subject'],'some string');
                           ^here

but this use doesn't actually appear to have documented semantics anywhere in the language definition.
Am I missing something?

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

ID: d03bfc0e-6636-8847-8a22-1bf280d26b6e
Version Independent ID: ea462c47-798f-981b-85fd-3771a4a1f5a4
Content: Workflow Definition Language schema reference - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-workflow-definition-language.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@SRNissen
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@SRNissen, a doc update was published, thank you!

Yes I saw, very happy to see you're being this responsive to your users :D


conda-store extension poll ways too often

Currently conda-store jupyterlab extension is polling as fast as possible. Need to change to polling every 5 seconds or so.

Should be fixed in last PR.
This was due to me not setting a timer or an interval for the React useEffect hook.