Crash on Production app with IllegalStateException

@KaustubhPatange
I am getting this crash on Live App, could you please take a look at this issue Thanks.
Exception java.lang.IllegalStateException: Restarter must be created only during owner's initialization stage
at androidx.savedstate.SavedStateRegistryController.performAttach (SavedStateRegistryController.kt:45)
at androidx.savedstate.SavedStateRegistryController.performRestore (SavedStateRegistryController.kt:63)
at com.lengo.uni.navigation.navigator_compose.LifecycleController.performRestore$app_allLangRelease (LifecycleController.java:206)
at com.lengo.uni.navigation.navigator_compose.ComposeNavigator$Setup$1$1$1.invoke (ComposeNavigator.kt:1316)
at com.lengo.uni.navigation.navigator_compose.ComposeNavigator$Setup$1$1$1.invoke (ComposeNavigator.kt:1310)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt:116)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt:34)
at com.lengo.uni.navigation.navigator_compose.ComposeNavigator$CommonEffect$1$1$1.invoke (ComposeNavigator.kt:1401)
at com.lengo.uni.navigation.navigator_compose.ComposeNavigator$CommonEffect$1$1$1.invoke (ComposeNavigator.kt:1390)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt:116)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt:34)
at androidx.compose.foundation.layout.BoxWithConstraintsKt$BoxWithConstraints$1$1$measurables$1.invoke (BoxWithConstraints.kt:69)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt:107)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt:34)
at androidx.compose.ui.layout.LayoutNodeSubcompositionsState$subcompose$2$1$1.invoke (SubcomposeLayout.kt:770)
at androidx.compose.ui.layout.LayoutNodeSubcompositionsState$subcompose$2$1$1.invoke (SubcomposeLayout.kt:448)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt:107)
at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke (ComposableLambda.jvm.kt:34)
at androidx.compose.runtime.ActualJvm_jvmKt.invokeComposable (ActualJvm_jvmKt.java:74)
at androidx.compose.runtime.ComposerImpl$doCompose$2$5.invoke (Composer.kt:3193)
at androidx.compose.runtime.ComposerImpl$doCompose$2$5.invoke (Composer.kt:3183)
at androidx.compose.runtime.SnapshotStateKt__DerivedStateKt.observeDerivedStateRecalculations (SnapshotStateKt__DerivedStateKt.java:252)
at androidx.compose.runtime.SnapshotStateKt.observeDerivedStateRecalculations (SnapshotStateKt.java:1)
at androidx.compose.runtime.ComposerImpl.doCompose (Composer.kt:3183)
at androidx.compose.runtime.ComposerImpl.composeContent$runtime_release (ComposerImpl.java:3119)
at androidx.compose.runtime.CompositionImpl.composeContent (Composition.kt:584)
at androidx.compose.runtime.Recomposer.composeInitial$runtime_release (Recomposer.kt:811)
at androidx.compose.runtime.ComposerImpl$CompositionContextImpl.composeInitial$runtime_release (Composer.kt:3712)
at androidx.compose.runtime.ComposerImpl$CompositionContextImpl.composeInitial$runtime_release (Composer.kt:3712)
at androidx.compose.runtime.CompositionImpl.setContent (Composition.kt:519)
at androidx.compose.ui.layout.LayoutNodeSubcompositionsState.subcomposeInto (SubcomposeLayout.kt:468)
at androidx.compose.ui.layout.LayoutNodeSubcompositionsState.subcompose (SubcomposeLayout.kt:441)
at androidx.compose.ui.layout.LayoutNodeSubcompositionsState.subcompose (SubcomposeLayout.kt:432)
at androidx.compose.ui.layout.LayoutNodeSubcompositionsState.subcompose (LayoutNodeSubcompositionsState.java:421)
at androidx.compose.ui.layout.LayoutNodeSubcompositionsState$Scope.subcompose (SubcomposeLayout.kt:732)
at androidx.compose.foundation.layout.BoxWithConstraintsKt$BoxWithConstraints$1$1.invoke-0kLqBqw (BoxWithConstraints.kt:69)
at androidx.compose.foundation.layout.BoxWithConstraintsKt$BoxWithConstraints$1$1.invoke (BoxWithConstraints.kt:67)
at androidx.compose.ui.layout.LayoutNodeSubcompositionsState$createMeasurePolicy$1.measure-3p2s80s (SubcomposeLayout.kt:590)
at androidx.compose.ui.node.InnerPlaceable.measure-BRTryo0 (InnerPlaceable.kt:44)
at androidx.compose.ui.node.LayoutNode$performMeasure$1.invoke (LayoutNode.kt:1428)
at androidx.compose.ui.node.LayoutNode$performMeasure$1.invoke (LayoutNode.kt:1427)
at androidx.compose.runtime.snapshots.Snapshot$Companion.observe (Snapshot.kt:2116)
at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads (SnapshotStateObserver.kt:110)
at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui_release (OwnerSnapshotObserver.kt:78)
at androidx.compose.ui.node.OwnerSnapshotObserver.observeMeasureSnapshotReads$ui_release (OwnerSnapshotObserver.java:66)
at androidx.compose.ui.node.LayoutNode.performMeasure-BRTryo0$ui_release (LayoutNode.java:1427)
at androidx.compose.ui.node.OuterMeasurablePlaceable.remeasure-BRTryo0 (OuterMeasurablePlaceable.kt:94)
at androidx.compose.ui.node.OuterMeasurablePlaceable.measure-BRTryo0 (OuterMeasurablePlaceable.kt:75)
at androidx.compose.ui.node.LayoutNode.measure-BRTryo0 (LayoutNode.kt:1366)
at androidx.compose.foundation.layout.BoxKt$boxMeasurePolicy$1.measure-3p2s80s (Box.kt:137)
at androidx.compose.ui.node.InnerPlaceable.measure-BRTryo0 (InnerPlaceable.kt:44)
at androidx.compose.ui.node.LayoutNode$performMeasure$1.invoke (LayoutNode.kt:1428)
at androidx.compose.ui.node.LayoutNode$performMeasure$1.invoke (LayoutNode.kt:1427)
at androidx.compose.runtime.snapshots.Snapshot$Companion.observe (Snapshot.kt:2116)
at androidx.compose.runtime.snapshots.SnapshotStateObserver.observeReads (SnapshotStateObserver.kt:110)
at androidx.compose.ui.node.OwnerSnapshotObserver.observeReads$ui_release (OwnerSnapshotObserver.kt:78)
at androidx.compose.ui.node.OwnerSnapshotObserver.observeMeasureSnapshotReads$ui_release (OwnerSnapshotObserver.java:66)
at androidx.compose.ui.node.LayoutNode.performMeasure-BRTryo0$ui_release (LayoutNode.java:1427)
at androidx.compose.ui.node.OuterMeasurablePlaceable.remeasure-BRTryo0 (OuterMeasurablePlaceable.kt:94)
at androidx.compose.ui.node.LayoutNode.remeasure-_Sx5XlM$ui_release (LayoutNode.java:1381)
at androidx.compose.ui.node.LayoutNode.remeasure-_Sx5XlM$ui_release$default (LayoutNode.java:1372)
at androidx.compose.ui.node.MeasureAndLayoutDelegate.doRemeasure-sdFAvZA (MeasureAndLayoutDelegate.kt:187)
at androidx.compose.ui.node.MeasureAndLayoutDelegate.remeasureAndRelayoutIfNeeded (MeasureAndLayoutDelegate.kt:274)
at androidx.compose.ui.node.MeasureAndLayoutDelegate.access$remeasureAndRelayoutIfNeeded (MeasureAndLayoutDelegate.kt:38)
at androidx.compose.ui.node.MeasureAndLayoutDelegate.measureAndLayout (MeasureAndLayoutDelegate.kt:208)
at androidx.compose.ui.platform.AndroidComposeView.measureAndLayout (AndroidComposeView.android.kt:757)
at androidx.compose.ui.node.Owner.measureAndLayout$default (Owner.java:196)
at androidx.compose.ui.platform.AndroidComposeView.dispatchDraw (AndroidComposeView.android.kt:954)
at android.view.View.draw (View.java:23190)

Use the latest 0.1-alpha36 release of Compose Navigator that will the fix the issue.

@KaustubhPatange I tried updating to 0.1-alpha36 but for some reason still getting the same crash on live play store build.

@KaustubhPatange Actually, i was not able to reproduced it, but there many user who are getting this error

Maybe this could be the reason because i'm using SaveState 1.2.0
https://developer.android.com/jetpack/androidx/releases/savedstate#version_120_3

@KaustubhPatange  I added this check before calling performRestore i think it might resolve this issue
if (!lifecycleController.isRestored() && lifecycleController.lifecycle.currentState == Lifecycle.State.INITIALIZED) {
lifecycleController.performRestore(null)
This code is from Androidx  SavedStateRegistryController class
@MainThread
fun performAttach() {
val lifecycle = owner.lifecycle
check(lifecycle.currentState == Lifecycle.State.INITIALIZED) {
("Restarter must be created only during owner's initialization stage")
}
lifecycle.addObserver(Recreator(owner))
savedStateRegistry.performAttach(lifecycle)
attached = true
}

This is a hack, the main question is why your old destination's lifecycle is not destroyed even though the @Composable's onDispose {} is called, so navigator-compose is trying to reuse the same which is why crash!
Are you adding any lifecycle observers to route (mentioned in this doc)?

@KaustubhPatange  No i'm not using lifecycle observers also not using popupTo as well.

Are you changing the navigation destination within a coroutine scope somewhere?


Design interface for generator of values and factory of this generator

The generators of (random) values should have common interface which has to be designed. Also some factory of generators should be designed.

The interfaces was created.


Linux Support

This looks like a really neat module and I was excited to try it out, but I ran into a few issues on Linux; I'm guessing this wasn't written with Linux support in mind.
Is your feature request related to a problem? Please describe.
Installing on Linux via Install-Module -Name Invoke-Terraform -Repository PSGallery -Scope CurrentUser works, but commands within the module (i.e. Get-ConfigurationPath) return the system configuration path instead of the config path within the user's home directory. The system configuration path requires root privileges to write to. I've attempted to go down the rabbit hole with this a little bit and get it working properly on Linux, but without intimately knowing exactly how this module is supposed to work, progress is slow and difficult.
Describe the solution you'd like
Proper support for Linux
Describe alternatives you've considered
Additional context
Below is what happens when attempting to set the terraform version on Linux.
$ set-TerraformVersion -TFVersion 1.4.6
WARNING: The Enterprise path /etc/xdg/xdg-cinnamon/powershell cannot be found
New-Item: Access to the path '/etc/xdg/xdg-cinnamon' is denied.
New-Item: Access to the path '/etc/xdg/xdg-cinnamon' is denied.

Performing the operation "Setting TFVesion configuration version to 1.4.6" on target "/etc/xdg/xdg-cinnamon/powershell/Christian
Pearce/Invoke-Terraform".
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "Y"): y
WARNING: The Enterprise path /etc/xdg/xdg-cinnamon/powershell cannot be found
New-Item: Access to the path '/etc/xdg/xdg-cinnamon' is denied.
New-Item: Access to the path '/etc/xdg/xdg-cinnamon' is denied.
WARNING: The Enterprise path /etc/xdg/xdg-cinnamon/powershell cannot be found
New-Item: Access to the path '/etc/xdg/xdg-cinnamon' is denied.
New-Item: Access to the path '/etc/xdg/xdg-cinnamon' is denied.
Set-Content: Could not find a part of the path '/etc/xdg/xdg-cinnamon/powershell/Christian Pearce/Invoke-Terraform/Configuration.psd1'.

HI I have tests that install on MacOS, Windows and Linux.  I have personally used this in pipelines that run on Linux.  I just installed it on Linux via Azure Cloud Shell.

What distribution are you running?
What is in your $PSGetPath ?

Similar issue? https://github.com/Jaykul/PowerLine/issues/39

Sorry for the delayed reply, and thank you for taking the time to respond.

I have personally used this in pipelines that run on Linux. I just installed it on Linux via Azure Cloud Shell.

I'm glad that my (apparently poor) guess of this not having Linux support was wrong! :smile:

What distribution are you running?

Short answer: Linux Mint.
Long Answer:
/home/user> cat /etc/os-release
NAME="Linux Mint"
VERSION="21.1 (Vera)"
ID=linuxmint
ID_LIKE="ubuntu debian"
PRETTY_NAME="Linux Mint 21.1"
VERSION_ID="21.1"
HOME_URL="https://www.linuxmint.com/"
SUPPORT_URL="https://forums.linuxmint.com/"
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/en/latest/"
PRIVACY_POLICY_URL="https://www.linuxmint.com/"
VERSION_CODENAME=vera
UBUNTU_CODENAME=jammy

What is in your $PSGetPath ?

/home/user> $PSGetPath

AllUsersModules    : /usr/local/share/powershell/Modules
AllUsersScripts    : /usr/local/share/powershell/Scripts
CurrentUserModules : /home/user/.local/share/powershell/Modules
CurrentUserScripts : /home/user/.local/share/powershell/Scripts

Similar issue? https://github.com/Jaykul/PowerLine/issues/39

Hmm that is interesting; I think so! On my system, it appears that $Env:XDG_CONFIG_HOME is equal to $null. I'm not sure if this is specific to my distro of choice. (Curious: was it populated in AZ Cloud Shell?) The spec referenced in the issue you linked seems to indicate that it shouldn't matter if it is $null, since whatever relies on it should fall back to $HOME/.config/. However, I don't see XDG_CONFIG_HOME anywhere in your module so I don't think this is the problem, unless I'm mistaken.


Fixes #276

Python Program to Find Factorial of Number Using Recursion.

UPDATED !!
https://github.com/Algo-Phantoms/Algo-Tree/pull/2005


:bug: Fix(core): Fix bytecode not being passed into contract actions

Description
Fixed bug with forgetting to pass the bytecode into the individual actions
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #682   👈

This stack of pull requests is managed by Graphite.


Complete health probe failure not correct

In the last part of the document it states:
"If health probes fail for every backend in a backend pool, then Front Door considers all backends healthy and routes traffic in a round robin distribution across all of them."
That is not correct. If health probes fail for every backend in a backend pool, Front Door DOESN'T consider backends healthy and, thus, won't route traffic. Only when the health probes are showing healthy again is when Front Door will start routing traffic again.

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

ID: f35a0b39-ab2f-ba8a-0907-e0f3a6b69135
Version Independent ID: 0e6c8267-a911-9c6b-0522-3ec96753b3ef
Content: Azure Front Door Service - backend health monitoring
Content Source: articles/frontdoor/front-door-health-probes.md
Service: frontdoor
GitHub Login: @sharad4u
Microsoft Alias: sharadag

@ositobio , Thank you for your feedback. We will investigate and get back to you shortly.

@ositobio , I tested it myself with having a web app behind the Frontdoor and configured the probes to a directory that doesn't exist. When I browsed the AFD URL , I am still able to get the page loaded.
The statement in the doc is correct. Let me know if you have any further questions.

@ositobio , Do you have any update for me?

@ositobio , Please tag me if you have any further questions.

Semantics. I think @ositobio may be right as this seems to be a grammar issue. Would it be better worded to say "Frontdoor considers all the healthy backends and routes traffic in a round robin distribution across all of them" ?


ci: Upgrade to PNPM 8 and Node 18

PNPM:

There are some minor problems with peer dependencies with PNPM 7, which are resolved by upgrading to PNPM 8
8 is the default version if you install pnpm
PNPM 8 also has roughly 2x the number of downloads vs v7, and 7x the number of downloads as v6, so it's safe to say it's the most common version.
PNPM versions: https://www.npmjs.com/package/pnpm?activeTab=versions

NodeJS:

Node 16 is in maintainance mode
Node 18 is current official LTS version for Docker: https://hub.docker.com/_/node/
With PNPM 9, NodeJS 16 will likely be deprecated
@types/node v20 is most popular, with v18 2nd popular
Node 16 will not be supported in September 2023: https://github.com/nodejs/Release#release-schedule

Generally, targeting TypeScript 5.x usually prefers Node.js v18 or v20, unless we want to target minimal compatible versions in which case TypeScript 5 with Node.js v16 and PNPM 7 is fine for now.
Think it would be good to keep note of supported versions in README.md

I support upgrading pnpm. It's very verbose when it wants an update, so I expect most devs already have it. I've been using it successfully these past few months with sapphire-paratime. Are some other components having a problem?
It's good to support the Node LTSes until they've exited maintenance mode. 16-18 are all pretty compatible. 20 has fetch which is going to break fetchRuntimePublicKey, but even a light breeze breaks that function, so whatever...

As per #183 and #177 we've upgraded to PNPM 8 and Node v18


Minor update for cdh.md

Hi @astroshim :D
The most of the original contents was awesome, so I just updated some minor parts(e.g. table of contents, Cloudera link and removing #apache-zeppelin-on-cdh anchor header in dropdown menu and index.md). Could you please check this change?

@AhyoungRyu Really appreciate for your help!! :+1:


Fixes for breaking changes from OpenSearch#7468

Description
Fixes for breaking changes from OpenSearch#7468
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks for this fix, I think these are handled by #743

solved by #743


[Legal] Missing license

I wanted to use this starter project but it seems like it's missing a license.
I don't know if I can distribute projects made with this React template.

@AleksandarDev can you add the license please. Thanks.


feat: reusable namespaces

This PR adds support for reusing a namespace for more than 1 Makefile essentially allowing you do to the following
type Terraform sg.Namespace

func (Terraform) Plan(ctx context.Context) error {
	// do terraform plan here
}

func main() {
	sg.GenerateMakefiles(
		sg.Makefile{
			Path:          sg.FromGitRoot("Makefile"),
			DefaultTarget: All,
		},
		sg.Makefile{
			Path:          sg.FromGitRoot("project1/Makefile"),
			Namespace:     Terraform{},
		},
		sg.Makefile{
			Path:          sg.FromGitRoot("project2/Makefile"),
			Namespace:     Terraform{},
		},
	)
}

Which would then generate a Makefile in folder project1 and project2 with the targets in the Terraform namespace
The main change here is that rather than 1 single init function in the generated sage binary, we now generate 1 function for each Makefile and use the hash of the defined Makefile path as a prefix to know which Makefile is calling the sage binary.
Together with this work I refactored the generation code and broke it out into a few isolated functions to try and make that code, which was getting difficult to work with, a little easier to understand.
There is one major user facing change and a minor one.
The major one is that the targets generated in the root Makefile for calling other Makefiles is now the path of the Makefile file directory rather than the namespace name. So before, for the example above, you would have make terraform as a target in the root Makefile and now you have make project1 and make project2 instead (which I think it makes sense from a point of view of make.
The minor one is that the sage binary call inside the make target would be slight more readable and now will contain the hashed prefix. So in the example above you would have
.PHONY: terraform-plan
terraform-plan: $(sagefile)
	@$(sagefile) Terraform:Plan

and now will look something like this
.PHONY: terraform-plan
terraform-plan: $(sagefile)
	@$(sagefile) "Target1692162558:Terraform:Plan"

@alethenorio should we keep the branch?

@alethenorio should we keep the branch?

I think we can always bring it back it we need to so no reason to keep it


Swift 5 support and New Menu from Top option added

Hi @deejeay143, thank you for contributing to SideMenu. Unfortunately, I've had a very large rewrite of this repo in the works when you made this contribution, and so your changes are now incompatible with the latest version.
The good news is there is now a SideMenuPresentationStyle class that allows you to create your own custom presentation styles. This may make it easier for you to create the desired effect. Take a look at the Advanced section of the README for more information.

Sure I will look into the possibilities.


⚠ Bofrost.lu has degraded performance

In 5bace4b, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1145 ms

Resolved: Bofrost.lu performance has improved in b13dbdc after 6 minutes.


Describe release cadence, version numbering, etc

This is a Feature Request

What would you like to be added
A page that tells readers about the following, or helps them find other authoritative pages about:

Which versions of Kubernetes are supported, and what “supported” means
How often major versions are released
How often minor versions are released
What versions are compatible with what other versions

What the Kubernetes project does about releases to address security shortcomings, etc

Why is this needed
Someone asked about this on Slack, and when I was looking for a page to answer their question I realized that there wasn't one.

Potentially relevant to #12322, #12323, #12324, #12233, and #14307

/kind feature
/priority backlog

/remove-priority backlog
/priority important-longterm

/lifecycle frozen

/sig release

We now have https://kubernetes.io/releases/ from PR #27929
/close


Action fails for "merge_group" events

The action fails when triggered by the merge queue event "merge_group".
> Run wearerequired/lint-action@v2
Error: lint-action does not support "merge_group" GitHub events

I can create a PR for this, given this is something @wearerequired are looking to do. Please let me know @wearerequired.


v1.1.0

v1.1.0 release + update example to STAC 1.0.0
it is a a minor version because we add functionality in a backwards compatible manner

nodata table row fixed
nodata cannot be a string, always a number. All language have infinity and NaN as a number representation but not JSON
merged

@emmanuelmathot @m-mohr where are we on this?

I requested the review by @m-mohr but I think he is off.
I addressed all his points of his review so I think we are good to go.

Yes, seems good. I'm just too busy right now.


Deprecate get_or_spawn

Objective
After merging retained rendering world #15320, we now have a good way of creating a link between worlds (HIYAA intensifies). This means that get_or_spawn is no longer necessary for that function. Entity should be opaque as the warning above get_or_spawn says. This is also part of #15459.
I'm deprecating get_or_spawn_batch in a different PR in order to keep the PR small in size.
Solution
Deprecate get_or_spawn and replace it with get_entity in most contexts. If it's possible to query &RenderEntity, then the entity is synced and render_entity.id() is initialized in the render world.
Migration Guide
If you are given an Entity and you want to do something with it, use Commands.entity(...) or World.entity(...). If instead you want to spawn something use Commands.spawn(...) or World.spawn(...). If you are not sure if an entity exists, you can always use get_entity and match on the Option<...> that is returned.

Does removing this affect networking crates at all? My assumption would be that they might desire to pass entities over the wire and sync them one-to-one using something like get_or_spawn. Or do they typically just use a map to correlate entities (e.g. EntityMapper)?

Or do they typically just use a map to correlate entities (e.g. EntityMapper)?

This is the recommended pattern. Per @maniwani, since we don't have entity ID range reservation, relying on specific entity IDs is very fragile and ill-advised, because things like UI spawning will generating new entity IDs and clash with the networked entities.

Changes look fine to me, a bit odd that the transform hierarchy and prepare_cluster ones don't have expect and all the other ones do, but not really blocking imo.

Those, I believe, don't use any of the sync machinery so I don't know what I would write in the expect clause.

Or do they typically just use a map to correlate entities (e.g. EntityMapper)

That's what we do in bevy_replicon, so we won't be affected.

Or do they typically just use a map to correlate entities (e.g. EntityMapper)

That's what we do in bevy_replicon, so we won't be affected.

Can also confirm that's how bevy_ggrs works!


Add clipbar extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for your contribution 🔥
This is already possible in this extension - could you use that?

Thanks for the recommendation, it's not exactly what I want but I think it's good enough!


FF_dissolve_glitch_simplified.py window really small/squashed

I'm trying to use FF_dissolve_glitch_simplified.py on Ubuntu 22.04 with python 3.10 and the window size is really small

It can't be resized either (no resize handles appear and the resize option is greyed out).

@hellocatfood Ok, I finally built the llinux version in Ubuntu this time, check the linux folder inside python version. Now it can find ffmpeg automatically, (It was not working in the earlier version because I just forgot to add the 'shell=True' command),

I have tested it and it is working properly.

I just tried this again and getting the same result. I did some digging and it seems the script window sizing is reacting the window scaling.
I have a HiDPI screen (3840x2400) and have scaling set to 200%

At this setting it is the only window where all of the UI elements appear squashed

Hi @hellocatfood,
I just changed the whole UI of ff-dissolve glitch to a modern look. Now it looks like this:

Hope you will like this :)


Higher priority for replica set primary than secondaries?

cc: @krallin
(This is a question, not a prescription.) Right now, we use the same priority (1) for all members of a replica set. This means that, given a cluster with primary mongo-1 and secondaries mongo-2 and mongo-3, and the scenario:

mongo-1 crashes.
mongo-2 is elected new primary.
mongo-1 is restored.

mongo-2 will remain primary. We can, however, coerce mongo-1 into reclaiming primary status whenever it's online by using priority 1 for primaries and 0.5 for secondaries.
A pro of this configuration is that the database container reported as primary in our system is much more likely to actually be the primary (assuming it's up and running). Are there cons?

Summarizing our Slack conversation about this here for the record:

The UI does not actually suggest the first node is the primary. It just says other nodes are in the same cluster (this is intentional: for replication, it does say that the first node is the master). We can of course always reword to make this even clearer if needed :smile:.
There is a real downside to doing this since it'll trigger cluster re-elections than are not actually needed (which, among other things, will cause the master to close all open connections — which Mongo's doc refer to as a "maintenance window"). It might even cause multiple elections to get the node with the highest priority to become the master (according to the MongoDB docs).
MongoDB clients actually discover the master on their own, so they don't need to be deliberately pointed at the primary. However, this only happens if you instruct them that they're connecting to a replica set, either by specifying multiple node names, or by specifying the replica set name. In practice, if you don't do that, then the client will behave just as if you were connecting to a standalone. When we make MongoDB clustering self-service, we should add a notice instructing users to properly configure their client.
Customers that do care about having priorities can actually set them on their own.

So, the bottom line is, this doesn't seem like something we should be doing.
Let me know if I missed anything, @fancyremarker!
Cheers,


get list

Rename BaseResource's build_filter and list as get_filters and get_list respectively (the latter being now a method instead of a property). get_list now accepts optional filters (get_filters is used if none provided).

Codecov Report

Merging #30 into master will decrease coverage by 0.01%.
The diff coverage is 95.65%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
- Coverage   93.79%   93.77%   -0.02%
==========================================
  Files          28       28
  Lines        1096     1093       -3
==========================================
- Hits         1028     1025       -3
  Misses         68       68

Impacted Files
Coverage Δ

connect/resource/usage_automation.py
93.85% <100%> (ø)
:arrow_up:

connect/resource/automation.py
92.3% <100%> (-0.8%)
:arrow_down:

connect/resource/base.py
92.3% <100%> (ø)
:arrow_up:

connect/resource/fulfillment_automation.py
52.83% <100%> (ø)
:arrow_up:

connect/resource/template.py
60% <66.66%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #30 into master will decrease coverage by 0.01%.
The diff coverage is 95.65%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
- Coverage   93.79%   93.77%   -0.02%
==========================================
  Files          28       28
  Lines        1096     1093       -3
==========================================
- Hits         1028     1025       -3
  Misses         68       68

Impacted Files
Coverage Δ

connect/resource/usage_automation.py
93.85% <100%> (ø)
:arrow_up:

connect/resource/automation.py
92.3% <100%> (-0.8%)
:arrow_down:

connect/resource/base.py
92.3% <100%> (ø)
:arrow_up:

connect/resource/fulfillment_automation.py
52.83% <100%> (ø)
:arrow_up:

connect/resource/template.py
60% <66.66%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


GatewayDiscoveryClientAutoConfiguration.ReactiveDiscoveryClientRouteDefinitionLocatorConfiguration#discoveryClientRouteDefinitionLocator:       Did not match:          - @ConditionalOnProperty (spring.cloud.gateway.discovery.locator.enabled) did not find property 'spring.cloud.gateway.discovery.locator.enabled' (OnPropertyCondition)

Describe the bug
Hey guys, there is the problem. I was setting spring.profiles.includes=dynamicproperty in application.yml to including a specified profile named 'dynamic(file name:application-dynamic-eureka.yml)', which enabled DiscoveryClient Route Definition Locator. But it doesn't seem to work. I saw initialize log in the console:
GatewayDiscoveryClientAutoConfiguration.ReactiveDiscoveryClientRouteDefinitionLocatorConfiguration#discoveryClientRouteDefinitionLocator:
      Did not match:
         - @ConditionalOnProperty (spring.cloud.gateway.discovery.locator.enabled) did not find property 'spring.cloud.gateway.discovery.locator.enabled' (OnPropertyCondition)

Also, I couldn't find any routes definition by URL 'http://localhost:9201/actuator/gateway/routes' after the gateway was started.
I'm sure the value of property spring.cloud.gateway.discovery.locator.enabled is true in the profile.
This is the link to my code.
By the way, if I'm not using the spring.profiles.include to include profiles, and put all the properties in application-dynamic-eureka.yml into the application.yml, The application will work perfectly.
Is that a stupid problem with my usage of spring.profiles.include? or it's a bug or something ? plz help me find out the key problem and resolve it, thanks!
(Plz forgive me if there are some pragmatic fault )
How to reproduce
Three modules:  api-gateway, eureka-server, and user-service. Just start those applications and check the response of http://localhost:9201/actuator/gateway/routes or log in console.

I don't think this has anything specific to gateway. You have spring.profiles.includes=dynamic but the name of the file is application-dynamic-eureka.yml. At this point I'm guessing boot is using the profile to load the file and application-dynamic.yml doesn't exist.

Hey @spencergibb, thank you for the reply.
I changed the file name to application-dynamic.yml as your suggestion and rerun application. it works now.
There is some problem that may need your help. Is spring boot load profiles with class which named org.springframework.boot.context.config.ConfigFileApplicationListener? If so, when and where this class is used? (Maybe some book list will be helpful)
Thank you kindly.😆

I'm not sure what you're asking for. That is all Spring Boot functionality.


add feature to enable streaming image with torch on

Description
*I added a new feature to enable torch while streaming the image since there is no torch feature inside.

@googlebot I signed it!
On Mon, Aug 24, 2020, 9:53 PM googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it! and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fflutter%2Fplugins%2Fpull%2F2957
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/plugins/pull/2957#issuecomment-679174928, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3N2OK4TCVWAH7YVVDEVMTSCJ5GDANCNFSM4QJSZUCA
.

This feature is implemented in #3367, closing this PR

This feature is implemented in #3367, closing this PR


What is the difference between centernet.py and centernet_back.py

Hi! Thanks for opensourcing the great work. I wonder What is the difference between centernet.py and centernet_back.py?

Thank you for catching this! This is an intermediate version during the code cleanup, that is very hard to read. I should have removed this ...

Thanks for your reply.! I got it.


Fix global_step variable definition

Pull Request Test Coverage Report for Build 82

1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.934%

Totals

Change from base Build 79:
0.0%

Covered Lines:
820

Relevant Lines:
1324

💛  - Coveralls

This was implemented in https://github.com/tensorflow/lucid/pull/59.
Sorry we couldn't merge this PR for that—the global_step tensor also needed initialization.

Apologies for not documenting the motivation for this PR, but I don't think #59 fixes the issue that this PR was trying to tackle: global_step is not available in the T function passed to the objectives functions.
Thus, even after #59, the following custom decay objective fails:
@objectives.wrap_objective
def decay(n_steps):
  def inner(T):
    return 1 - (T('global_step') / n_steps)
  return inner

with the following error:
KeyError: "The name 'import/global_step:0' refers to a Tensor which does not exist. The operation, 'import/global_step', does not exist in the graph."

As discussed in person with @arvind:

Current workaround is to directly use tf.train.get_or_create_global_step(). Objective functions get evaluated within a scope that has the default session and graph available.
We should rethink T in general, especially the special cases such as input. I think its plausible we don't need T at all, but should probably discuss with everyone first. :-)


Annotation driven dependency declaration for Kotlin kernel

Using magic commands are common in a jupyter context, but illicit according to kotlin (and I guess java) language spec. So exporting e.g. kts scripts from a notebook, could strip all magics, which will loose all dependencies declarations. Or it could keep them, but the result would be non-compilable.
An annotation-driven configuration would be beneficial, because it's compatible with the kotlin language specs.
// To use a custom maven repository you can declare it with
@file:MavenRepository("imagej-releases","http://maven.imagej.net/content/repositories/releases" )

@file:DependsOnMaven("net.clearvolume:cleargl:2.0.1")

For example details see https://github.com/holgerbrandl/kscript#annotation-driven-script-configuration
Such an approach is implemented in the other kotlin kernel
https://github.com/ligee/kotlin-jupyter
and for scripting in
https://github.com/holgerbrandl/kscript
Clearly, having different annotations to declare dependencies across different types of scripting tooling won't give any benefits to the user, but there's a KEEP https://github.com/Kotlin/KEEP/issues/75 trying to unify these annotations. Maybe beakerx could implement the proposal once it's ready? (fyi @ligee)

Thank you for your suggestion, Holger.  I don't know much about Kotlin, so your feedback is especially useful.  Please forgive me however if some extra explanation is required for me understand it, however.
If Kotlin standardizes a scripting version then I would be happy to use it.
Currently we are using the embeddable compiler (https://github.com/twosigma/beakerx/blob/56653e6012a97914a7ad88416e610b0df06fb6ec/kernel/kotlin/build.gradle#L43) but it doesn't have APIs for things like autocomplete, so it's not ideal.
However I am not sure I understand the annotation system and how it relates to the magics.
If the Kotlin script system implements these annotations then wouldn't they "just work" in BeakerX, similar to how Groovy's Grape works (http://nbviewer.jupyter.org/github/twosigma/beakerx/blob/master/doc/groovy/ClasspathMagicCommands.ipynb)?

You would not use any magics but simply evaluate a code cell that contains an special annotation that is declaring a dependency. Indeed the @Grab looks very similar here.
And it could work the same way with java I guess.
I have no opinion nor experience with the compiler internals, but I guess the Kotlin Slack forum is a good place to ask. Or @ligee might now?

What is the current suggested way of handling dependencies? I can't seem to find a documentation about it =\ I see %import in the cheatsheet, but how do I point it to jar/repository/etc?

Ah, there is %classpath as well


Added SeasonType to teamPlayerDashboard

Coverage remained the same at 79.554% when pulling f88fbc74fc08257f0df2f0634aa08003974e8857 on briancbarrow:master into df305a338e5fea304f2793a6a096cf35b11da7c3 on nickb1080:master.

Lots of issues ive noticrd with bench and their fam*lys


Added serde derives + a test

This should work unless I missed something.
referencing #32

Looks good. Thanks!


Service image tag update (CI->CD)

Describe the solution you'd like
When I first evaluated kam, I was expecting to see a binding between CI and CD.
Instead, I found a static nginx deployment.
Would it make sense, in the default bootstrapping to :

Create a new Task that would edit the GitOPS repo  (environments/dev/apps/app-my-app/services/my-app/overlays/kustomization.yaml) and set the images: value using kustomize edit set image (last build, tag based on commit SHA)
Add this Task to the App Pipeline, to run after the Buildah task

It seems to me this is a standard way of doing things. Don't you think?

@pbriet  thanks for your suggestion.  It seems to make sense.


Remove the default WorkspaceReader from the build process.

The default reader prefers packaged or even installed versions of the project under construction.

Successfully replace ReactorReader with ProjectWorkspaceReader


🥾 b00t emoji characters don't render in PREVIEW THUMBNAIL (but work fine in asciinema)

I have no idea who to report this to (not sure who is responsible for the github markdown), but Emoji doesn't preview correctly on the github previews of the asciicast.
The actual RENDER video on asciinema works fine, just the thumbnail preview shows UTF8 escape sequences for non-western characters (though it seems to show chinese pinyin fine)?
preview:
http://github.com/elasticdotventures/b00t
I will try to debug more on my own, but would appreciate any advice in the proper direction to get this resolved.  Thanks!

Look at the screwball character codes in the video below, then watch the video.

Hi! Thanks for your report.
I believe you want to file a bug about thumbnails generated by https://asciinema.org.
This repository (asciicast-tools) is a third-party project and does not contain any code used in https://asciinema.org.
You're probably looking for the https://github.com/asciinema/asciinema-server project.
Please feel free to reopen this bug if you think it has been closed in error.


Can I support raspberry pie net core?

Can I support raspberry pie net core?

hi @peterfoot ,
Now can I use raspberry pie net core?

hi @peterfoot , Now can I use raspberry pie net core?

Not yet, c# there are few cross platform Bluetooth.

Closing this as Linux support is covered by issue #37


...and if I do not want to appear in a channel's contacts list?

For ex.:
Mister X  is a nazi-fascist, and I'm not, I blocked him, but
he try to add me  and I appear in the connections list of Mister X ( in this list there are 10 nazi-fascists + ME :-O ).
We need to find a solution for this problem, lately we have had these problems.

We now mark unidirectional connections with an no entry sign.
Reopen if you think this is not sufficient.


Options for Creating Packages

It's currently a surprising hassle to upload a new package.  It is particularly difficult when using the JFrog CLI with Appveyor or Travis when the session is scripted.
In both cases, the user must do one of two undesirable things:

Query and Create

Call package-show to determine if a package using that name exists in the repo already
Parse the response, verify that the repo doesn't exist, and then call package-create

Try Create

The user can call the package-create and know that it will fail if package exists already
Ignore the 409 Conflict exception if that's what is returned from Bintray

The way it should work is the way the Conan client implements it today (with bintray).  It's idempotent with regard to the package and version.  This means that if the package doesn't exist, it's created.  If it does exist, it's used.  The same logic applies to a version.
The client could implement this any number of ways, but first it needs to get reported as a feature request.

FYI, Conan client apparently does not upload via the Bintray standard API, so the way it automatically creates packages and versions as needed is implemented differently.

Here is the kind of problem we have on Appveyor, it fails the whole build if the package already exists:
jfrog bt pc %BT_SUBJECT%/%BT_REPO_MSI%/%MYAPP% --vcs-url=%VCS_URL% && exit 0
[Info] Creating package...
[Error] Bintray response: 409 Conflict
{
"message": "Package go-msi exists for repository '*****/public-msi'"
}
Command exited with code 1
A "solve just this issue" approach could be to add a flag to "--ignore-errors" so that the CLI returns 0.  I don't like that approach, but it would solve this appveyor problem.  I would prefer that non-existent packages were created automatically.


ImageCache always returns false when using removeImageWithIdentifier method.

I am trying to remove the image from image cache using removeImageForRequest method of ImageCache. Although it performs the necessary work and delete the image from cache but it always returns false.
I think the issue is with dispatch_async_barrier block. Because the piece of code in it runs asynchronously hence it always return false.
Please fix this issue as it doesn't return true value when it has removed the image.

Thanks for reporting @asifbilal786. It was definitely wrong. I've pushed a fix in 6be1da8b which is part of #154. I've also added tests to verify the return value now works as expected.
I'm going to close this issue out. Please redirect all further comments to #154.

Thanks for quick fix. As i have implemented Pods, so did you also update the Cocoa Pods for this?

The changes are still in review. Once we get it merged, we're going to release AF 4.0.0-beta.1 and AFI 3.0.0-beta.1. If you need to pull the changes in before, you can always point directly to the beta6 branch in #154.


Linux build fails

@isuruf: CircleCI seems to be lacking permissions?

@conda-forge-admin, please update circle

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I updated the circle-ci deploy key and followed the project.


bosh upload release is broken

Using 1.3115
Generated /var/folders/tp/mfydkfq136l964tfdb6fgh5c0000gn/T/d20151027-37913-p1lmaw/d20151027-37913-1a6nsjg/release.tgz
Release size: 2.2G
Cannot find file `/var/folders/tp/mfydkfq136l964tfdb6fgh5c0000gn/T/d20151027-37913-p1lmaw/d20151027-37913-18m9whn/release.MF'

If I look at the $TMPDIR, it should be/var/folders/tp/mfydkfq136l964tfdb6fgh5c0000gn/T/d20151027-37913-p1lmaw/release.MF
If I drop to 1.3100, it all works.

Hello
We can't seem to recreate the issue, tried to create and upload a release on both mac and linux without issues. Can you maybe give us more details about your environment and maybe a debug log?
Thanks

I am more than happy to give you a debug log. Where is it on my local machine?

can you run: bosh task {the_failed_task_number} --debug

There is no task since it didn't get that far.

is it possible to share the release tarball you were trying to upload? and are you running on mac?

It was the develop branch of cf-release with updated loggregator code.
I am on a Mac. I was using 3115 but dropped to 3100 to get things working.

We still can't seem to recreate the problem. Did you create the tarball using create release? We have seen cases where this error happens when the tarball is created manually.  Can you send the listing for tar -tvf against the tarball you are using?

I can no longer recreate the issue.

I located the source of the problem.
https://github.com/cloudfoundry/bosh/blob/master/bosh_cli/lib/cli/release_tarball.rb#L47
On my machine, I have gnu tar installed and --fast-read is a mac specific option which fails.

@fraenkel please try 3148. we believe https://github.com/cloudfoundry/bosh/commit/dddb47433d75f3087d650d71d9ff47030b562980 fixes this problem. reopen if problem persists.

@cppforlife I have using 3215 and run into the exact problem. I am using the default BSD tar that shipped with mac.

@simonleung8 this issue has been closed for a long time. please open a different issue and include necessary info like cli and director version, error stacktrace, etc.


Fixing the jmap/geopackage integration

absolute tile coordinate (jmap viewer) to crs coordinate (geopackage)

Fixed with commit 4e084a7d04c02b0a41a9d6a3ac97f931c794defd


Extending Jackson2JsonMessageConverter

I want to register a new module into the object mapper present in Jackson2JsonMessageConverter, but the documentation suggests two ways of doing it:

One is to configure the ObjectMapper and inject into Jackson2JsonMessageConverter. The documentation in the setJsonObjectMapper suggest an alternative which is to extend the class and override the method initializeJsonObjectMapper

The issue with extending the Jackson2JsonMessageConverter is the lack of access to the ObjectMapper in the parent class, ending up like this:

public class JacksonMessageConverter extends Jackson2JsonMessageConverter {
    @Override
    protected void initializeJsonObjectMapper() {
        ObjectMapper objectMapper = new ObjectMapper();
        objectMapper.registerModule(new GuavaModule());
        objectMapper.configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false);
        this.setJsonObjectMapper(objectMapper);
    }
}

So we still have to inject the ObjectMapper, besides overriding the method, it doesn't really look like an alternative.
Changing the ObjectMapper visibility to protected (or a getter) would give us the alternative.

Yes, it looks like an oversight; there should either be a getter or the mapper should be passed in as an argument to the method.


TypeError: meshgrid() got an unexpected keyword argument 'indexing'

Loaded pretrained resnet:
Traceback (most recent call last):
File "tools/run.py", line 82, in
run()
File "tools/run.py", line 71, in run
torch.multiprocessing.spawn(
File "/root/anaconda3/envs/cwhpy38/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 230, in spawn
return start_processes(fn, args, nprocs, join, daemon, start_method='spawn')
File "/root/anaconda3/envs/cwhpy38/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 188, in start_processes
while not context.join():
File "/root/anaconda3/envs/cwhpy38/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 150, in join
raise ProcessRaisedException(msg, error_index, failed_process.pid)
torch.multiprocessing.spawn.ProcessRaisedException:
-- Process 2 terminated with the following error:
Traceback (most recent call last):
File "/root/anaconda3/envs/cwhpy38/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 59, in _wrap
fn(i, *args)
File "/nvmelv/cwh8szh/BoxeR/tools/run.py", line 40, in distributed_main
main(configuration, init_distributed=True)
File "/nvmelv/cwh8szh/BoxeR/tools/run.py", line 29, in main
trainer.load()
File "/nvmelv/cwh8szh/BoxeR/e2edet/trainer/base_trainer.py", line 57, in load
self.load_model_and_optimizer()
File "/nvmelv/cwh8szh/BoxeR/e2edet/trainer/base_trainer.py", line 103, in load_model_and_optimizer
self.model = build_model(self.config, num_classes)
File "/nvmelv/cwh8szh/BoxeR/e2edet/model/init.py", line 22, in build_model
model.build()
File "/nvmelv/cwh8szh/BoxeR/e2edet/model/base_model.py", line 46, in build
self._build()
File "/nvmelv/cwh8szh/BoxeR/e2edet/model/boxer2d.py", line 54, in _build
self.transformer = build_transformer(self.config.transformer)
File "/nvmelv/cwh8szh/BoxeR/e2edet/module/transformer.py", line 392, in build_transformer
return BoxTransformer(
File "/nvmelv/cwh8szh/BoxeR/e2edet/module/box_transformer.py", line 33, in init
encoder_layer = BoxTransformerEncoderLayer(
File "/nvmelv/cwh8szh/BoxeR/e2edet/module/box_transformer.py", line 312, in init
self.self_attn = BoxAttention(d_model, nlevel, nhead)
File "/nvmelv/cwh8szh/BoxeR/e2edet/module/box_attention.py", line 168, in init
self._create_kernel_indices(kernel_size, "kernel_indices")
File "/nvmelv/cwh8szh/BoxeR/e2edet/module/box_attention.py", line 182, in _create_kernel_indices
i, j = torch.meshgrid(indices, indices, indexing="ij")
TypeError: meshgrid() got an unexpected keyword argument 'indexing'

Thanks for solving the this problem

Hi,
This means you are using the old pytorch version. In this codebase, we recommend to use pytorch >= 1.10


Light id is fix after it connected  to the hue ? can i set it ?

anyone  who knows? thank you!

The bridge determines the light id, you can't change it.

The bridge determines the light id, you can't change it.

when I search for new lights again or turn off the light, can  the light id change  automatic？

The light id does not change.

ok, thank you!


Bucket does not exist

I have successfully built the template and every thing is in buckets. While creating cloud formation its failing to complete and following is the error.
Error occurred while GetObject. S3 Error Code: NoSuchBucket. S3 Error Message: The specified bucket does not exist (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: e0f2ea38-5209-11e9-b390-a7dbaaa5a497)

Hi there,
If I understand correctly you have gone through the deployment process and pushed the zipped source code to an s3 bucket but the template is failing to launch. The above error message suggests that CloudFormation can't access the source code, specifically it can' find the bucket.
Can you:

check the template source code mapping has been updated with your bucket and the path to the zip files.
check the bucket is in the same region as the region you are deploying the template to.
check the bucket has the -region extension in the name.

Example for deploying the solution to us-east-1:

Create a bucket called 'my-bucket-us-east-1'

Run the build script:
./build-s3-dist.sh mybucket v1.0

Copy the zip files with public read permissions to the s3://my-bucket-us-east-1/serverless-image-handler/v1.0/

Before running the template please check the mapping section has been updated (lines 135/136):

S3Bucket: my-bucket
S3Key: serverless-image-handler/v1.0/serverless-image-handler.zip
** note ** the -us-east-1 is added later in the template as part of the lambda resource.
If you not making any hanges to the code you can also launch our public version which can be found here: https://aws.amazon.com/solutions/serverless-image-handler/?trk=sl_card

Resolving. Please re-open this if you are still having an issue.


HNC: Clean up kubectl plugin hierarchy modification functions

(Filed as a part of #93; may supplant #108)
We currently have three commands to change the structure of the hierarchy: set-parent, unset-parent and subnamespace. These commands don't work consistently and aren't grouped well.
As a result, I think we should have a single set <ns> command with multiple flags:

--parent <parent>: sets the parent
--root: unsets the parent (i.e., turns this into a root namespace)
--requiredChild <child>: specifies that <child> is a required child
--unrequiredChild <child>: FUTURE removes the currently unrequired child

I think this is more clear. For example, let's say we have a namespace called middle and we wanted to set its parent top and its required child bottom. Today, this would be expressed as:
kubectl hnc set-parent mid top
kubectl hnc subnamespace mid bottom

It's not clear, in this setting, what's the meaning of the first or second parameters without looking at the documentation. Instead, the new format will be:
kubectl hnc set mid --parent top
kubectl hnc set mid --requiredChild bottom

This makes it more clear (I think) which namespace is being acted on and what the resulting relationship will look like.
Finally, where there's a set, there should probably be a get as well. Let's change kubectl hnc show to kubectl hnc get instead.

/good-first-issue

/assign vjdhama

@vjdhama looks like you're not a member of kubernetes-sigs yet, can you please add yourself as per https://github.com/kubernetes-sigs/multi-tenancy#join-this-repo? tashimi and I can sponsor you, and it's ok not to have contributions yet, just say you'll be working on HNC and reference this issue.

Thanks. I raised membership request. 🤞


fix: do not apply approved label if change requested

An outstanding CHANGES_REQUESTED state prevents a PR from being merged even if another reviewer approves the PR. This change makes it so that the approved label cannot be added until all change requested states have been resolved.
This prevents a scenario where tide will repeatedly try to merge a PR and be rejected by GitHub due to the changes requested state.
Fixes: https://github.com/kubernetes-sigs/prow/issues/269

/ok-to-test

/hold

An outstanding CHANGES_REQUESTED state prevents a PR from being merged even if another reviewer approves the PR.

I may be wrong (will have to look at GH docs) but I don't think the above is universally true, IIRC this was a branch protection configuration option.
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#require-pull-request-reviews-before-merging
Says:

If a person with admin permissions chooses the Request changes option in a review, then that person must approve the pull request before the pull request can be merged. If a reviewer who requests changes on a pull request isn't available, anyone with write permissions for the repository can dismiss the blocking review.

I'm not convinced the PR is the right fix. When reviewActsAsApprove is not enabled, I don't think approve should take it into account at all. If the repo is configured via BP to require reviews for merging (leading Tide to loop merge attempts) then it is basically misconfigured and Tide should surface this problem better (I believe we had an issue for this class of problems - it was not just request changes, but other cases where BP prevents PRs from merging but Tide does not know about it).

I may be wrong (will have to look at GH docs) but I don't think the above is universally true, IIRC this was a branch protection configuration option.

I think you're right, I see also the wording of the BP setting:

When enabled, pull requests targeting a matching branch require a number of approvals and no changes requested before they can be merged.

Is there a doc/guide anywhere on how to properly set up GitHub, and branch protection in particular, for Prow/Tide?

If the repo is configured via BP to require reviews for merging (leading Tide to loop merge attempts) then it is basically misconfigured and Tide should surface this problem better (I believe we had an issue for this class of problems - it was not just request changes, but other cases where BP prevents PRs from merging but Tide does not know about it).

Yeah this is really my main gripe, the behavior came as a bit of a surprise and it took some digging for us to understand what was going wrong. I see it as more of an implementation detail how it's addressed, but would like for the error to be more transparent. Do you have any suggestions?

Is there a doc/guide anywhere on how to properly set up GitHub, and branch protection in particular, for Prow/Tide?

Unfortunately I'm not aware of any. Many advanced branch protection features enforcing PR merge eligibility are younger than Tide and the big Prow orgs (kube, openshift) are mostly not using them. Generally Tide expects a PR to be mergeable once it passes Tide's criteria (query match + required jobs pass) and considers inability to merge to be "user errors".
I think that in today's world this does not stand. I'd prefer the solution to be

Tide to properly surface any occurrences when it thinks it may merge but is disallowed to do so
Tide to check as many mergeability properties as possible in its isAllowedToMerge method to avoid thinking it may merge a PR when GH would disallow it

It is not entirely straightforward. 1) is a problem because the status context (which right now is the only PR-facing Tide user interface, maybe with the exception of Tide PR dashboard which people don't really use that much) is controlled by a separate controller than the one that actually tries to merge. 2) is also not easy because checking mergeability for BP would require Tide asking about more properties of the PR (and possibly the repo, to check BP requirements).

I think that in today's world this does not stand. I'd prefer the solution to be

Tide to properly surface any occurrences when it thinks it may merge but is disallowed to do so
Tide to check as many mergeability properties as possible in its isAllowedToMerge method to avoid thinking it may merge a PR when GH would disallow it

Ack - closing this PR as the solution should take a different approach


Master to Live

Docs Build status updates of commit 89dfe2e:
:clock10: Full build: the average full build time is 13 min(s) 30 sec(s), this is based on the last 514 build(s) for this repository.

Docs Build status updates of commit 89dfe2e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/client-access/Set-CASMailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/devices/Set-DeviceConditionalAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Set-MailboxFolderPermission.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-audit/Search-UnifiedAuditLog.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance/New-ActivityAlert.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance/Set-ActivityAlert.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/role-based-access-control/Remove-ManagementRoleEntry.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/Get-CsAdditionalInternalDomain.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Get-CsTeamsAppPermissionPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Grant-CsTeamsAppPermissionPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsAutoAttendant.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsAppPermissionPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsTeamsAppPermissionPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

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

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


Sometimes the time text goes under the icon

fix in
https://github.com/opensquare-network/statescan/commit/ff80518719af59812b7a1eb3790f3802e86f69a7


Update to use new pydoc-markdown options

The pydoc-markdown package used to render the API docs has been significantly upgraded since I first did the docs for this package and now includes integration with mkdocs. I think this should significantly simply the docs build process.

Alternatively, just move to Read the Docs...


Unable to understand how to use the code

Sir i am very new to xcode and i am making an app where i must select the colour and get RGB values i am just able to add radial colour pallet and nothing more can you please brief me how to use

Hi Sanju. It is expected that you have some basic understanding of programing, Swift and XCode to use this library. That said, please refer to readme for fastest and easiest way how to add FlexColorPicker to your app.
Also, when reporting issues, please be specific about the problem and add code samples or screenshots.

Also you can have a look on code in this directory for examples on how you can use FlexColorPicker.


update extension location, use psr18 discovery

Codecov Report

Merging #8 (032c7d9) into main (cf9b68a) will not change coverage.
The diff coverage is 0.00%.

:exclamation: Current head 032c7d9 differs from pull request most recent head 61366aa. Consider uploading reports for the commit 61366aa to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

@@            Coverage Diff            @@
##               main       #8   +/-   ##
=========================================
  Coverage     71.47%   71.47%
  Complexity      366      366
=========================================
  Files            38       38
  Lines          1143     1143
=========================================
  Hits            817      817
  Misses          326      326

Flag
Coverage Δ

7.4
71.45% <0.00%> (ø)

8.0
71.45% <0.00%> (ø)

8.1
71.45% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

src/Console/Command/Release/PeclCommand.php
0.00% <0.00%> (ø)

Continue to review full report in Codecov by Sentry.

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


[Doc bug] resource tag for a web app is inconsistent in the docs

In the following docs page, the guidance on how to tag app service resources for deployment is inconsistent.
https://docs.microsoft.com/en-us/azure/developer/azure-developer-cli/make-azd-compatible?pivots=azd-create#add-bicep-files
This section states to replace the value web with the name of the actual resources.

This example shows to use the actual value web, which I believe is correct.

I think the problem is there are two different and valid interpretations of "replacing web with the name of your service".  I think it's possible to interpret that as "the name of the azure resource (like an app service service) that runs your compute" (and I think that's what Chris had done here) vs "the name of a key in the services object in azure.yaml" (which is the intended reading).
Later in the linked documentation, we do say this:

Which tries to say the same thing in a different way.  It's interesting to note that that section is the first time we really talk about a "service" in the way azd thinks about services.
Maybe we need to rework the prose to something like this:

Add the following code, to add a tag named azd-service-name with the value of web to your Azure resource.  azd uses this tag to determine what resource to deploy your application to.  The value should match the name of your service as defined in azure.yaml (and then perhaps this is a link to the anchor'd section later in the prose)?

The above is probably still not great (I'm not a technical writer!), but I think being more explicit about what "service" means in this context (and linking to the stuff about services in the the azure.yaml file) is helpful. It also explains more of "why" this is done.

Updated: https://docs.microsoft.com/en-us/azure/developer/azure-developer-cli/make-azd-compatible?pivots=azd-create.


Deployment commit for prod-stable

Merged prod-beta branch to prod-stable.
Use latest commit to update namespace ref in app-interface repo. Don't use merge commit, SHAs must be unique when images are created for each branch.

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

Project coverage is 65.80%. Comparing base (dd0a9b6) to head (19a5e35).
Report is 1599 commits behind head on prod-stable.

Additional details and impacted files
@@               Coverage Diff               @@
##           prod-stable    #3815      +/-   ##
===============================================
+ Coverage        65.12%   65.80%   +0.67%
===============================================
  Files              507      514       +7
  Lines             9764     9933     +169
  Branches          2242     2171      -71
===============================================
+ Hits              6359     6536     +177
+ Misses            3402     3394       -8
  Partials             3        3

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


Access Control Origin

I am able to post messages through your repo but I continue to get the below message on both my local and staging environments
XMLHttpRequest cannot load https://hooks.slack.com/services/randomtext/randomtext.
A wildcard '*' cannot be used in the 'Access-Control-Allow-Origin' header when the credentials flag is true.
Origin 'https://localhost:3000' is therefore not allowed access.

I have a similar issue, [Error] Fetch API cannot load https://hooks.slack.com/services/XXXXXXXXXXXXXXX. Request header field Content-Type is not allowed by Access-Control-Allow-Headers.


Bump esbuild version

This version bump fixes https://github.com/evanw/esbuild/issues/3219 which we are seeing when trying to build and deploy our Remix site via SST + seed.run

Relevant Discord thread https://discord.com/channels/983865673656705025/1129464581945835610/1130998543314862191


edit log format

This PR intends to update changes made to the API endpoint, in order to attempt to pass the test for challenge 5.

Passes 6/7 of the ch5 test. One more to go!


Hi,everyone,my S1750*2,the linux will panic when i concurrent startup

host：CentOS6
kernel: 4.18.20
server: Dell R740
hardwa: S7150*2
QEMU:2.3.0 and 2.12.0
this is my system kdump
vmcore-dmesg.txt

host：CentOS6
kernel: 4.18.20
server: Dell R740
hardwa: S7150*2
QEMU:2.3.0 and 2.12.0
this is my system kdump
vmcore-dmesg.txt

Hello, I've had specific crashes. Have you solved it now?

Hi
Can you tell me your company name ? maybe we can setup cooperate project
发件人: Zzoujiwei<EMAIL_ADDRESS>发送时间: 2020年9月23日 9:58
收件人: GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization<EMAIL_ADDRESS>抄送: Subscribed<EMAIL_ADDRESS>主题: Re: [GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization] Hi,everyone,my S1750*2,the linux will panic when i concurrent startup (#34)
host：CentOS6
kernel: 4.18.20
server: Dell R740
hardwa: S7150*2
QEMU:2.3.0 and 2.12.0
this is my system kdump
vmcore-dmesg.txthttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGPUOpen-LibrariesAndSDKs%2FMxGPU-Virtualization%2Ffiles%2F5072347%2Fvmcore-dmesg.txt&data=02|01|monk.liu%40amd.com|0f2406a6069547a0727b08d85f640d68|3dd8961fe4884e608e11a82d994e183d|0|0|637364230626185983&sdata=%2BRW0VhaZIsv%2B%2BpJYmNAZYhwsJLNUw72Fp6l0Vx%2FglmA%3D&reserved=0
Hello, I've had specific crashes. Have you solved it now?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGPUOpen-LibrariesAndSDKs%2FMxGPU-Virtualization%2Fissues%2F34%23issuecomment-697075636&data=02|01|monk.liu%40amd.com|0f2406a6069547a0727b08d85f640d68|3dd8961fe4884e608e11a82d994e183d|0|0|637364230626185983&sdata=7sBE4jRxybkdES87TZoD0wwwnslt2TDX67rF8dNA%2BR8%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG4GO4KXVNP2KBRGEWX3BM3SHFIZHANCNFSM4P7BFNBA&data=02|01|monk.liu%40amd.com|0f2406a6069547a0727b08d85f640d68|3dd8961fe4884e608e11a82d994e183d|0|0|637364230626195976&sdata=wFYiKOQ7N3ocf5oCwG3ferARpYiRvQJ2S8JTPGwzMSk%3D&reserved=0.

Hello, have you not solved this problem? Is there an error when loading GIM?
------------------ 原始邮件 ------------------
发件人:                                                                                "GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization"<EMAIL_ADDRESS>发送时间: 2020年9月24日(星期四) 晚上11:46
收件人<EMAIL_ADDRESS>抄送: "今日头条"<1678316310<EMAIL_ADDRESS>主题: Re: [GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization] Hi,everyone,my S1750*2,the linux will panic when i concurrent startup (#34)
Hi
Can you tell me your company name ? maybe we can setup cooperate project
发件人: Zzoujiwei<EMAIL_ADDRESS>发送时间: 2020年9月23日 9:58
收件人: GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization<EMAIL_ADDRESS>抄送: Subscribed<EMAIL_ADDRESS>主题: Re: [GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization] Hi,everyone,my S1750*2,the linux will panic when i concurrent startup (#34)
host：CentOS6
kernel: 4.18.20
server: Dell R740
hardwa: S7150*2
QEMU:2.3.0 and 2.12.0
this is my system kdump
vmcore-dmesg.txt<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGPUOpen-LibrariesAndSDKs%2FMxGPU-Virtualization%2Ffiles%2F5072347%2Fvmcore-dmesg.txt&data=02%7C01%7Cmonk.liu%40amd.com%7C0f2406a6069547a0727b08d85f640d68%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637364230626185983&sdata=%2BRW0VhaZIsv%2B%2BpJYmNAZYhwsJLNUw72Fp6l0Vx%2FglmA%3D&reserved=0>
Hello, I've had specific crashes. Have you solved it now?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGPUOpen-LibrariesAndSDKs%2FMxGPU-Virtualization%2Fissues%2F34%23issuecomment-697075636&data=02%7C01%7Cmonk.liu%40amd.com%7C0f2406a6069547a0727b08d85f640d68%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637364230626185983&sdata=7sBE4jRxybkdES87TZoD0wwwnslt2TDX67rF8dNA%2BR8%3D&reserved=0>, or unsubscribe<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG4GO4KXVNP2KBRGEWX3BM3SHFIZHANCNFSM4P7BFNBA&data=02%7C01%7Cmonk.liu%40amd.com%7C0f2406a6069547a0727b08d85f640d68%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637364230626195976&sdata=wFYiKOQ7N3ocf5oCwG3ferARpYiRvQJ2S8JTPGwzMSk%3D&reserved=0>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[AMD Official Use Only - Internal Distribution Only]
Please tell me your company name and we can setup formal procedure, we cannot help you without the formal procedure
No one can help you only depends on those shatters of information, and even we by coincidence figure out what’s going wrong there we still not allowed to extent our technique support
To an anonymous customer
Thanks

Monk Liu|GPU Virtualization Team |AMD
<EMAIL_ADDRESS>From: Zzoujiwei<EMAIL_ADDRESS>Sent: Monday, September 28, 2020 9:20 AM
To: GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization<EMAIL_ADDRESS>Cc: Liu, Monk<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization] Hi,everyone,my S1750*2,the linux will panic when i concurrent startup (#34)
Hello, have you not solved this problem? Is there an error when loading GIM?
------------------ 原始邮件 ------------------
发件人: "GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization"<EMAIL_ADDRESS>发送时间: 2020年9月24日(星期四) 晚上11:46
收件人<EMAIL_ADDRESS>抄送: "今日头条"<1678316310<EMAIL_ADDRESS>主题: Re: [GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization] Hi,everyone,my S1750*2,the linux will panic when i concurrent startup (#34)
Hi
Can you tell me your company name ? maybe we can setup cooperate project
发件人: Zzoujiwei<EMAIL_ADDRESS>发送时间: 2020年9月23日 9:58
收件人: GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization<EMAIL_ADDRESS>抄送: Subscribed<EMAIL_ADDRESS>主题: Re: [GPUOpen-LibrariesAndSDKs/MxGPU-Virtualization] Hi,everyone,my S1750*2,the linux will panic when i concurrent startup (#34)
host：CentOS6
kernel: 4.18.20
server: Dell R740
hardwa: S7150*2
QEMU:2.3.0 and 2.12.0
this is my system kdump
vmcore-dmesg.txt<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGPUOpen-LibrariesAndSDKs%2FMxGPU-Virtualization%2Ffiles%2F5072347%2Fvmcore-dmesg.txt&data=02%7C01%7Cmonk.liu%40amd.com%7C0f2406a6069547a0727b08d85f640d68%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637364230626185983&sdata=%2BRW0VhaZIsv%2B%2BpJYmNAZYhwsJLNUw72Fp6l0Vx%2FglmA%3D&reserved=0>
Hello, I've had specific crashes. Have you solved it now?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGPUOpen-LibrariesAndSDKs%2FMxGPU-Virtualization%2Fissues%2F34%23issuecomment-697075636&data=02%7C01%7Cmonk.liu%40amd.com%7C0f2406a6069547a0727b08d85f640d68%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637364230626185983&sdata=7sBE4jRxybkdES87TZoD0wwwnslt2TDX67rF8dNA%2BR8%3D&reserved=0>, or unsubscribe<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG4GO4KXVNP2KBRGEWX3BM3SHFIZHANCNFSM4P7BFNBA&data=02%7C01%7Cmonk.liu%40amd.com%7C0f2406a6069547a0727b08d85f640d68%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637364230626195976&sdata=wFYiKOQ7N3ocf5oCwG3ferARpYiRvQJ2S8JTPGwzMSk%3D&reserved=0>.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FGPUOpen-LibrariesAndSDKs%2FMxGPU-Virtualization%2Fissues%2F34%23issuecomment-699720427&data=02|01|monk.liu%40amd.com|8b5b880b2c5847787db108d8634cac8a|3dd8961fe4884e608e11a82d994e183d|0|0|637368528251052173&sdata=mfHnBs8EuUlUISaHx7oUvhDxSY0PHKiKZrYxQS2lkDE%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAG4GO4OXJRNRZBP6K47BMKLSH7QFPANCNFSM4P7BFNBA&data=02|01|monk.liu%40amd.com|8b5b880b2c5847787db108d8634cac8a|3dd8961fe4884e608e11a82d994e183d|0|0|637368528251062169&sdata=3ZlAdBei7jJ4clrYfmmTgyadz74sNDBdlYrm6VPd%2BGc%3D&reserved=0.


Can't resolve link for index.md and README.md

I really like this plugin and your approach and Auto-expand Link Feature.
I found that it can't handle the link for index.md or README.md properly.
As you might can see in this link, mkdocs has a page called index page for each directory. A Index page literally work as index page of the path, so has different logic for it's path.
If docs/  has bellow documents,
- 'index.md'
- 'a.md'
- folder
    - 'README.md`
    - `b.md`

then for each document gets following link by mkdocs

index.md - /
a.md - /a
floder/README.md - /folder
floder/b.md - /folder/b

Can you please resolve this issue?

Thanks for the reported issue. I'll try to look into it during the weekend.

I actually found out that my algorithm works not exactly as it's supposed to (not as I wanted).
It doesn't take into account the partial path provided and instead relies only on the file name. Need to rewrite it.


Setting up StoreKit environment with configuration file in Xcode 12

Is your feature request related to a problem? Please describe.
Testing IAP flow is impossible with current Detox. Another issue we face is we may not receive the IAP product prices during the test which causes flakiness.
Describe the solution you'd like
Apple introduced StoreKit Testing on the latest iOS 14 and Xcode 12. By adding a Configuration.storekit file and selecting it on the Run section of the scheme, we can provide the IAP list. Although using StoreKit configuration fixes the not connecting to AppStore on the Xcode run, it does not affect detox test run.
I don't know if providing complex StoreKit scenarios is possible at all but allowing passing a StoreKit Configuration file to tests is a huge improvement to the current situation.

After digging in StoreKit configuration, I found a workaround to provide StoreKit configuration during the test but it works only on second launch.
function findId(systemPath: string) {
  return new Promise<string>((resolve, reject) => {
    glob(
      path.join(systemPath, "/**/Documents/Persistence/storeSystem.db"),
      (err, files) => {
        if (err || !files || files.length === 0) {
          return reject(err);
        }
        const ff = files[0].replace(systemPath, "");
        const regex = /\/?([a-zA-Z0-9-]+)\//;
        resolve(regex.exec(ff)[1]);
      }
    );
  });
}

export async function setupStoreKitConfiguration(
  configFile: string,
  bundleId: string
) {
  const systemPath = path.join(
    os.homedir(),
    "Library/Developer/CoreSimulator/Devices/",
    device.id,
    "data/Containers/Data/System"
  );
  const systemId = await findId(systemPath);
  const dataPath = path.join(
    systemPath,
    systemId,
    "Documents/Persistence/Octane/",
    bundleId
  );
  fs.mkdirSync(dataPath, { recursive: true });
  fs.copyFileSync(configFile, path.join(dataPath, "Configuration.storekit"));
}

// USAGE
await setupStoreKitConfiguration("path/to/Configuration.storekit", "com.example.app");
await device.launchApp({});

Hello,
I am not familiar with how StoreKit Testing works in Xcode 12. If you are able to create a native (no RN) skeleton demo project, with a Configuration.storekit file, I can take a look. It is most likely either an environment variable or a launch argument that Xcode provides when launching the app from a scheme with that file linked.

@LeoNatan The sample app that Apple provided for iOS 14 has Configuration.storekit file and in README it explains how to use it:
https://developer.apple.com/documentation/app_clips/fruta_building_a_feature-rich_app_with_swiftui

Grits is one of the buggiest Apple examples, causing consistent SwiftUI crashes. 😂

@sercand solution worked fine for me but now I can't confirm the purchase since it's a system dialog, any workarounds ?

Unfortunately we won’t be able to offer system alert support until we have an XCUITest support, which is upcoming but will take time.

Interesting, I don't see a launch argument or environment variable for the app process.

The database modification can probably be added to https://github.com/wix/AppleSimulatorUtils
https://github.com/wix/AppleSimulatorUtils/issues/72
Closing this issue in Detox, as it's out of scope. AppleSimUtils is a better place for configuration injection into simulators, while Detox will eventually get the ability to tap on the "Confirm" button using XCUIElement actions. This will take some time.


Doesn't respect instances with strict rules on bots

My home instance is icosahedron.website, which has the rule that bots cannot interact with users without their explicit consent (see https://icosahedron.website/@halcy/332608). Since the follower bots have started appearing, the admin has been blocking them.
There is no technical way to determine if an instance has a rule like this, but I think it would be useful to keep a list of instances where follow bots are not welcome, and don't send requests to them. This list could be built up over time through pull requests.
Thanks

As you said, there's no way to magically know if the instance has rules or not for that or not.
That said, a blacklist has been implemented for that specific need and I respond to anyone asking to be added to that blacklist ( the bot won't follow the specific user, or the specific instance once its coded ).
I have not received a request from the owner of your instance though but you can also do a pull request, and I'll be glad to accept it :)

May be you should just not use spam bot at all.

@DavidLibeau I think you misunderstood the goal of this bot and how Mastodon works.
Removing your comment as it's not constructive and the issue was already solved.

To populate the federated timeline you just need to folow one account
for each instance. Follow one admin found in /about/more and don't spam
regulaer users. I'm already spammed with your bots.
Le 08/04/2017 à 23:50, Tristan Mahé a écrit :

@DavidLibeau https://github.com/DavidLibeau I think you
misunderstood the goal of this bot and how Mastodon works.
Removing your comment as it's not constructive and the issue was
already solved.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gled-rs/mastodon-autofollow/issues/2#issuecomment-292748116,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALCetr7TUOY13Y7dzfuBg1WKkiaNhWiuks5ruAEfgaJpZM4M3NiO.

@DavidLibeau actually no.
if you only follow the admin of each instance, you'll only have that admin toots on your federated timeline, not so much for a diverse view.
I'll gladly accept your username in the blacklist though, so that future bots based on this code won't try to follow you.

I don't want to be on any list.
If, for now, Mastodon don't handle correctly the federate timeline, it must be improved. Hacking it with any system is just bandage... Wait or contribute to Mastodon is a better and only way to solve the issue, in my view.


state properties for the delegation model

We will be writing property tests for our executable haskell model of the ledger with delegation.  The first step is to think of all the properties that we can test.  Add these to the LaTeX (or lhs) document.

We have an Epic  for this (I added this issue to it), so I wonder whether this issue should remain open.


Removed comment from migration topic

Removed comment from migration topic
This is a template comment that should have been deleted from the migration issue. It has already been removed in the topic in the Microsoft/dotnet repo.

also not related to this change, but the includes seem to use different table styles: see the table on the following section and the next:
https://review.docs.microsoft.com/en-us/dotnet/framework/migration-guide/retargeting/4.0-4.7.1?branch=pr-en-us-5016#the-default-hash-algorithm-for-wpf-packagedigitalsignaturemanager-is-now-sha256


Debugger: Step to a wrong line while debugging

Environment data
dotnet --info output:
VS Code version: 1.10.1
C# Extension version: \scratch2\scratch\janraj\vsdbg3\csharp-1.8.0-beta1.vsix
.NET Core SDK: 1.0.0-preview2-1-003177
OS: linuxmint17
Steps to reproduce

Open attached folder.
hwapp.zip
Set the "StopAtEntry: true" on launch.json.
Set bp at the line of 16 in Program.cs
Press F5 to start debugging.(Cursor hit the line of 9 in Program.cs)
F10
F11
F5(Continue).(Cursor hit the bp at the line of 16 in Program.cs)
F5

Expected  behavior
Stop debugging
Actual behavior
Cursor hit the bp at the line of 9 in Program.cs or others line.
Investigation

This issue is unstable.
Attached log file.
log.txt
This issue also occur on opensuse13.2.
The log file only 2 lines when I collected log with adding" "args":["--engineLogging=/home/Claire/log.txt"] " on package.json.
I tried to this operation on different Linux OS, and many OS only can collected 2 lines log file.  Could you please help to confirm it?

@WardenGnaw should this be resolved?

I could not reproduce the issue of stepping to the wrong line. However, I am noticing --engineLogging="" is only writing two lines.

@WardenGnaw lets open a new bug for the log file issue

I took a look at the log. What happened was that somehow the CLR ran the same code on two threads --
<- (E) {"seq":24,"type":"event","event":"stopped","body":{"reason":"step","threadId":14539,"allThreadsStopped":true,"source":{"name":"Program.cs","path":"/home/claire/Documents/hwapp/Program.cs"},"line":9,"column":9}}
And
<- (E) {"seq":24,"type":"event","event":"stopped","body":{"reason":"step","threadId":14542,"allThreadsStopped":true,"source":{"name":"Program.cs","path":"/home/claire/Documents/hwapp/Program.cs"},"line":9,"column":9}}

Actually, it isn't just that which is duplicated -- almost all the commands are duplicated. So we are actually debugging two different apps. Not sure if that means that this is a VS Code bug, or a bug in vsdbg-ui that somehow we are duplicating requests. @WardenGnaw did you try OpenSUSE 13.2?

I have not tried it on OpenSUSE.
For engine logging. I'm only getting these two lines:

@ClaireKang can you still repro this with the 'beta2' drop? If so, is there some way we can connect to your box? If so, please email us a link.

I still can repro this with the 'beta2' drop.

When I done the repro steps, the debug console have already display the .dll has exited, but actually the process still running.

I tried to collect log file, but it still only got 2 lines, do you need me to file a new bug?
I reproduce this issue on physic machine via Hyper-v, I'm sorry that I have no ideal to share it.

I have made a fix to the engine logging issue. We will release a new vsix with the fix. Can you show me the engine logging with the new vsix?

It can correctly collect log with latest extension(v1.8.0).

Removing from 1.8 since we aren't able to repro the issue from our side, so this will need to be fixed in some later release.


Add APK expansion support

The change is transparent to the user, Gdx.files.internal() can be used to access assets inside expansion files.
The application must call ((AndroidFiles)Gdx.files).setAPKExpansion() first, to open the expansion file(s). The function returns true if it was opened successfully.

test this

test this please

Looks OK to me. @Tom-Ski should merge if he agrees.

It seems that if there are lots of entries in the obb file, exists() is rather slow. For directories I have no better idea, but for files I think it can be optimized to this:
return isDirectory() ? expansionFile.getEntriesAt(getPath()).length != 0 : read() != null;
Can I somehow make this patch without a new pull request?


Search country by country code

I am trying to get country by country code. When I do:
ISO3166::Country.find_all_by('country_code', "1")
I get array of 25, while i am expecting it to return only united states?
Problem I am trying to solve is that I have country code which is country_code in this gem, and I want to get that country's  International Call Prefix. Which is international_prefix in this gem.
I know this might be expected behaviour. If any one can guide me about this, that will be great. Thank-you.

I think you are hitting the North American Numbering plan that share the 1 digit prefix.   https://en.wikipedia.org/wiki/North_American_Numbering_Plan
This is regretfully the "correct" response.

Thank-you for the response @rposborne
I expected that this is correct behaviour. But if you(or anyone) can guide me in solving the problem that will be great?
Should i save country name instead of country code in my DB, so i can get use find_country_by_name and than extract country code and international code easily from that. Though, this approach will cause me to extract country code every-time i need it.


Question about generic type Snapshotting<Value, Format>

Hello,
I love swift snapshot testing. And now I have a problem write some helper methods.
I wrote a helper method to verify a UIViewController as image with a specific snapshotDirectory:
    func verify(matching value: UIViewController,
                file: StaticString = #file,
                testName: String = #function,
                line: UInt = #line) {

        let failure = verifySnapshot(matching: value,
                                     as: .image,
                                     snapshotDirectory: snapshotDirectory(file: file),
                                     file: file, testName: testName, line: line)

        XCTAssertNil(failure, file: file, line: line)
    }

and later I created a similar method for UIView:
    func verify(matching value: UIView,
                file: StaticString = #file,
                testName: String = #function,
                line: UInt = #line) {

        let failure = verifySnapshot(matching: value,
                                     as: .image,
                                     snapshotDirectory: snapshotDirectory(file: file),
                                     file: file, testName: testName, line: line)

        XCTAssertNil(failure, file: file, line: line)
    }

They are doing exactly the same thing so I want to make it generic:
    func verify<T>(matching value: T,
                file: StaticString = #file,
                testName: String = #function,
                line: UInt = #line) {

        let failure = verifySnapshot(matching: value,
                                     as: Snapshotting<T, UIImage>.image,
                                     snapshotDirectory: snapshotDirectory(file: file),
                                     file: file, testName: testName, line: line)

        XCTAssertNil(failure, file: file, line: line)
    }

And now compiler gives error for:
Ambiguous reference to member 'image'

since there are a list of implementation for Snapshotting.image methods. I tried seveal ways e.g. casting but not work. Is there any solutions to achieve this? Thanks!

Hi @billypchan! Sorry for the delay. I don't think the compiler has enough information to resolve the code you have above since image is defined on specific extensions of Snapshotting and not on generic Snapshotting<T, UIImage>. The overloads should be just fine, though!
Gonna close this as an issue since we're doing some spring cleaning, but feel free to follow up here if you have any questions!


Add resume() method to ByteBuf that restores prior write position.

A situation we're running into is:
let mut input = ByteBuf::mut_with_capacity(8192);
read(&mut input);
let mut so_far = input.flip();
let done = parse_wire_thingie(so_far.bytes());
if !done {
    // we need more..
    input = so_far.resume();
    read(&mut input);
}

.. essentially, if we don't hit a whole "thingie", or find the sentinel, or whatever, we want to go back to appending more input on the end of the buffer.
This resume() method lets you do that; it's like flip(), but it puts you back to the end of the written section.

This looks good to me.

Awesome!

ty sir


Clarification

Just to clarify, when you say:
"If the user isn't authenticated, the user is redirected to the underlying authentication system, which is usually ASP.NET Core Identity."
Is this the part when I would log in to a Google/Facebook/etc account (if i'm not logged in)?

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

ID: f34f7534-347a-5752-3127-fd774abea530
Version Independent ID: af2c6c8a-d398-0202-4c28-cd5e15ce5219
Content: Secure ASP.NET Core Blazor WebAssembly
Content Source: aspnetcore/security/blazor/webassembly/index.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @bencalnan ... Yes when one of those 3rd party providers is used. That's why it says "usually" there ... if you don't configure anything else, then it would be ASP.NET Core Identity.

Thanks that's helpful


[SPARK-25356][SQL]Add Parquet block size  option to SparkSQL configuration

What changes were proposed in this pull request?
I think we should configure the Parquet buffer size when using Parquet format.
Because for HDFS, dfs.block.size is configurable, sometimes we hope the block size of parquet to be consistent with it.
And  whether this parameter spark.sql.files.maxPartitionBytes is best consistent with the Parquet  block size when using Parquet format?
Also we may want to shrink Parquet block size in some tests.
How was this patch tested?
N/A

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/testing-k8s-prb-make-spark-distribution-unified/2898/
Test PASSed.

Test build #95752 has started for PR 22350 at commit 3485b52.

Test build #95752 has finished for PR 22350 at commit 3485b52.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95752/
Test FAILed.

Sorry its not clear what is the setting - how do we adjust this setting, I wish to adjust parquet block size.

@AnirudhVyas, set parquet.block.size Hadoop configuration at Spark context or set it as an option e.g., option("parquet.block.size", "...")


Share configuration among our libraries

🎯 Goal: - Currently we have 5 libraries and likely to have more. Each lib now has its own eslint + jest config - It could increase the maintainability to have 'inherit' default configuration but also allow overrides
🤔 Things to consider:

is there a strong standard for this?
Jest has the notion of preset - This encourages to create of a pseudo-package (library) that holds shared config
Consider other custom configuration of unknown tools that libraries share (e.g. mutation, codecov, snyk, etc)

@rluvaton @DanielGluskin @elektronik2k5 Is there a strong standard here?

Not one which I'm aware of. It is very fragmented:

Some tools support declarative configuration inheritance (like eslint and TS).
Others don't support it out of the box, but as long as they can be configured via JS, it can be done. Jest and webpack are examples of that.
Some tools just don't have this feature at all (editorconfig).


Add function to get body literals.

test_asp.py became too long 1050/1000 lines
I added "# pylint: disable=too-many-lines"
We also can split it in two.
Let me know what do you prefer.

test_asp.py became too long 1050/1000 lines
I added "# pylint: disable=too-many-lines"
We also can split it in two.
Let me know what do you prefer.

I don't mind so much if a module is a bit longer. I also don't see a good way to cut it here. We can simply increase the limit in the global .pylintrc to say 2000.
Currently, the function would also collect elements in other statements than rules, for example, #show statements.
The function get_positive_body should be added to __ALL__. Maybe make the PositiveBodyVisitor private. The case for the rule could be removed and we could simply call visit(stm.body) assuming stm is the AST argument of get_positive_body.
We can also make the function more general and maybe not call it get_positive_body (which is questionable with antimonotone aggregates for example). What about the following:
get_body(stm: AST,
         exclude_aggregates: bool = False,
         exclude_theory_atoms: bool = False,
         exclude_signs: Tuple[Sign] = ())

I also like exclude better than discard.

It makes sense. I made the changes you suggested.
I also include the option to exclude conditional literals and use a Container instead of a Tuple for exclude_signs.

It makes sense. I made the changes you suggested.
I also include the option to exclude conditional literals and use a Container instead of a Tuple for exclude_signs.

Cool, I have a look at this one next. But now its weekend!!! :smile:

I did a couple of things:

removed the visitor because there was no recursive visiting happening,
adjusted docstrings,
removed remaining occurrences of "positive body",
update the pylintrc to work with the latest pylint version.

The PR is fine from my side.

I just updated the docstring.
It seems that pylint complains about an unrelated function "evaluate_binary()".

I just updated the docstring.
On my computer pylint complains about "evaluate_binary()" and "evaluate_unary()":
clingox/theory.py:132:4: R0201: Method could be a function (no-self-use) clingox/theory.py:171:4: R0201: Method could be a function (no-self-use)

This seems to be checked by an extension: https://pylint.pycqa.org/en/latest/user_guide/messages/refactor/no-self-use.html. I don't know why it is enabled on your computer.


Adds XA support to Helidon's UCP integration

Signed-off-by: Laird Nelson<EMAIL_ADDRESS>

See also #4292