Cannot get train-kubernetes installed in a Docker image based on chef/inspec:4.41.2

I have this Dockerfile:
FROM chef/inspec:4.41.2
RUN apt-get update && apt-get install -y make gcc g++
RUN ln -s /bin/mkdir /usr/bin/mkdir  # gem wants this for inexplicable reasons
RUN gem install inspec-bin -v 4.41.2 --no-document --quiet
RUN gem install train-kubernetes

WORKDIR /
RUN git clone https://github.com/GoogleCloudPlatform/inspec-gke-cis-benchmark.git
RUN cd inspec-gke-cis-benchmark && bundle install
RUN apt-get update && apt-get install -y jq curl python3
RUN curl https://sdk.cloud.google.com | bash
RUN ln -s /root/google-cloud-sdk/bin/gcloud /usr/bin/gcloud
ENV CHEF_LICENSE=accept
RUN gem uninstall excon -v 0.96.0
RUN inspec plugin install train-kubernetes
ENTRYPOINT []

Attempt 1
I build it with docker build -t chef-gke -f Dockerfile . in a directory with no other files. Every layer builds fine until I get to the inspec plugin install train-kubernetes. That fails with this error:
 => ERROR [12/13] RUN inspec plugin install train-kubernetes                                                                                43.3s
------
 > [12/13] RUN inspec plugin install train-kubernetes:
#15 14.64 +---------------------------------------------+
#15 14.64 ✔ 1 product license accepted.
#15 14.64 +---------------------------------------------+
#15 43.17 Unknown error occured - installation failed.
#15 43.17
------
executor failed running [/bin/sh -c inspec plugin install train-kubernetes]: exit code: 1

Attempt 2
I also tried with gem uninstall excon -v 0.85.0, which is the other version which is present. With that change to the Dockerfile, I get this error instead:
 => ERROR [12/13] RUN inspec plugin install train-kubernetes                                                                                1.5s
------
 > [12/13] RUN inspec plugin install train-kubernetes:
#15 1.429 /opt/inspec/embedded/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'excon' (= 0.85.0) - did find: [excon-0.96.0] (Gem::MissingSpecVersionError)
#15 1.430 Checked in 'GEM_PATH=/root/.gem/ruby/2.7.0:/opt/inspec/embedded/lib/ruby/gems/2.7.0', execute `gem env` for more information
#15 1.430 	from /opt/inspec/embedded/lib/ruby/2.7.0/rubygems/dependency.rb:323:in `to_spec'
#15 1.430 	from /opt/inspec/embedded/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:62:in `gem'
#15 1.430 	from /opt/inspec/bin/inspec:107:in `<main>'
------

Attempt 3
I also tried building without gem uninstall excon at all:
FROM chef/inspec:4.41.2
RUN apt-get update && apt-get install -y make gcc g++
RUN ln -s /bin/mkdir /usr/bin/mkdir  # gem wants this for inexplicable reasons
RUN gem install inspec-bin -v 4.41.2 --no-document --quiet
RUN gem install train-kubernetes

WORKDIR /
RUN git clone https://github.com/GoogleCloudPlatform/inspec-gke-cis-benchmark.git
RUN cd inspec-gke-cis-benchmark && bundle install
RUN apt-get update && apt-get install -y jq curl python3
RUN curl https://sdk.cloud.google.com | bash
RUN ln -s /root/google-cloud-sdk/bin/gcloud /usr/bin/gcloud
ENV CHEF_LICENSE=accept
RUN inspec plugin install train-kubernetes
ENTRYPOINT []

This also fails with
 => ERROR [12/13] RUN inspec plugin install train-kubernetes                                                                                43.3s
------
 > [12/13] RUN inspec plugin install train-kubernetes:
#15 14.64 +---------------------------------------------+
#15 14.64 ✔ 1 product license accepted.
#15 14.64 +---------------------------------------------+
#15 43.17 Unknown error occured - installation failed.
#15 43.17
------
executor failed running [/bin/sh -c inspec plugin install train-kubernetes]: exit code: 1

Attempt 4
And one last try with as little extra noise as possible:
FROM chef/inspec:4.41.2
RUN apt-get update && apt-get install -y make gcc g++
RUN ln -s /bin/mkdir /usr/bin/mkdir  # gem wants this for inexplicable reasons
ENV CHEF_LICENSE=accept
RUN gem install train-kubernetes
RUN inspec plugin install train-kubernetes
ENTRYPOINT []

Same error:
 => ERROR [5/5] RUN inspec plugin install train-kubernetes                                                                                35.6s
------
 > [5/5] RUN inspec plugin install train-kubernetes:
#8 13.43 +---------------------------------------------+
#8 13.43 ✔ 1 product license accepted.
#8 13.43 +---------------------------------------------+
#8 35.43 Unknown error occured - installation failed.
#8 35.43
------
executor failed running [/bin/sh -c inspec plugin install train-kubernetes]: exit code: 1

Ah, I also tried to install k8s-ruby, but version 0.10.4 doesn't appear to be in the ruby gems repo?
...
RUN gem install k8s-ruby -v 0.10.4

 => ERROR [4/6] RUN gem install k8s-ruby -v 0.10.4                                                                                23.9s
------
 > [4/6] RUN gem install k8s-ruby -v 0.10.4:
#7 2.338 ERROR:  Could not find a valid gem 'k8s-ruby' (= 0.10.4) in any repository
#7 23.87 ERROR:  Possible alternatives: k8s-ruby
------
executor failed running [/bin/sh -c gem install k8s-ruby -v 0.10.4]: exit code: 2


Android 6.0 Unity : Timeout while trying to pause the Unity Engine.

On android 6.0 our game freezes when we request the runtime permissions for fine and course location.
Could this be the reason?:
https://forum.unity.com/threads/crash-on-immediate-restart-timeout-while-trying-to-pause-the-unity-engine-before-win-death.313408/

This log message appears in normal circumstances, as well. Does the app freeze indefinitely? Are you using the latest version of the plugin?

Does the app freeze indefinitely?
yes, until i get an ANR. higher api versions than Android 6 work fine, btw.
Are you using the latest version of the plugin?
Ralph Kunz: yes 1.1
Am 31.10.2019 18:01:32 schrieb Süleyman Yasir KULA<EMAIL_ADDRESS>This log message appears in normal circumstances, as well. Does the app freeze indefinitely? Are you using the latest version of the plugin?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [https://github.com/yasirkula/UnityAndroidRuntimePermissions/issues/3?email_source=notifications&email_token=ADRB4K3UQY27VLBOWVDXHATQRMFOXA5CNFSM4JHNSRJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYQOFA#issuecomment-548472596], or unsubscribe [https://github.com/notifications/unsubscribe-auth/ADRB4K42XDOGQJZV4MSVY4LQRMFOXANCNFSM4JHNSRJA].

To be honest, I don't even know where to look. Are there any other error messages? In the worst case, you can uncomment the asynchronous permission functions and try using them: https://github.com/yasirkula/UnityAndroidRuntimePermissions/blob/4719de5ebb576d03719e194657c1f4590bf6b5ed/Plugins/AndroidRuntimePermissions/AndroidRuntimePermissions.cs#L130-L155

Thanks a lot. I'll give the asynchronous functions a try!
Am 31.10.2019 18:12:13 schrieb Süleyman Yasir KULA<EMAIL_ADDRESS>To be honest, I don't even know where to look. Are there any other error messages? In the worst case, you can uncomment the asynchronous permission functions and try using them: https://github.com/yasirkula/UnityAndroidRuntimePermissions/blob/4719de5ebb576d03719e194657c1f4590bf6b5ed/Plugins/AndroidRuntimePermissions/AndroidRuntimePermissions.cs#L130-L155 [https://github.com/yasirkula/UnityAndroidRuntimePermissions/blob/4719de5ebb576d03719e194657c1f4590bf6b5ed/Plugins/AndroidRuntimePermissions/AndroidRuntimePermissions.cs#L130-L155]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [https://github.com/yasirkula/UnityAndroidRuntimePermissions/issues/3?email_source=notifications&email_token=ADRB4K2RBQS6UGFQI3VCBN3QRMGWVA5CNFSM4JHNSRJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECYRTLA#issuecomment-548477356], or unsubscribe [https://github.com/notifications/unsubscribe-auth/ADRB4K7XN2GXB3IW227Q7ADQRMGWVANCNFSM4JHNSRJA].

I had the same issue when attempting to get permissions on Android 12 (using Unity 2020.3.26).  Using the Async method fixed the issue for me.

That's worrying. Thanks for sharing your findings and the details.

@BenF-GD Does the permission popup show up at all or does it freeze without presenting the popup?

@yasirkula No permission popup at all!  Not that it should make any difference at all, but for completeness, I am requesting android.permission.BLUETOOTH_CONNECT.  My unity app app targets SDK 31, with a min SDK of 26.
As I say, making the equivalent async method public (and then calling that) works well.  Have tested that across multiple devices, running android 10-12 (though its only devices running 12 that actually needs this particular permission).
I should also thank you!  This little plugin saved me a day, and as its free, I appreciate your work.


registerWebPlugin throws error

When attempting to register the web plugin, as per the instructions, I get this error:
Argument of type 'FacebookLoginWeb' is not assignable to parameter of type 'WebPlugin'.   Types have separate declarations of a private property 'addWindowListener'.
The plugin was working until recently, so this could be due to a capacitor update.
Thanks!

This is capacitor version Issue. I fixed by<EMAIL_ADDRESS>Please update.

I just faced the same error again after upgrading to capacitor 1.2.0.
It seems that even with @capacitor/core: "latest" npm does not recognize that the latest version is already installed in node_modules/@capacitor/core and installs it again into node_modules/@rdlabo/capacitor-facebook-login/node_modules/@capacitor/core which results in the "separate declarations error".
My first solution was to just delete the @capacitor/core directory within your plugin but that only works until you use npm install again.
The second solution was to remove your plugin and my package-lock.json. This will probably work until I update Capacitor again.
Any idea on how fix this permanently? I have the same issue with my own plugin and just don't know how to teach npm to not install a separate version of @capacitor/core after an upgrade other than upgrading my plugin with every capacitor upgrade to use the exact capacitor version numbers. (Just moving my capacitor core dependency to peerDependencies in package.json did not work either)

I'm using version 1.0.9.


Can I change a variable value?

Hello! I'm callmekohei!
Problems summary
So I want to change a valiable value daynamically.
Repro step
sample9$ cat foo.cs
using System;
namespace HelloWorld
{
    class Hello
    {
        static void Main()
        {
            string s = "Hello World!";
            Console.WriteLine(s);

        }
    }
}

sample9$ mcs -debug foo.cs

sample9$ sdb 'run foo.exe'
Welcome to the Mono soft debugger (sdb 1.5.6548.37600)
Type 'help' for a list of commands or 'quit' to exit

Inferior process '4040' ('foo.exe') started
Hello World!
Inferior process '4040' ('foo.exe') exited with code '0'

(sdb) bp add at foo.cs 8
Breakpoint '0' added at '/Users/callmekohei/tmp/sample9/foo.cs:8'

(sdb) r
Inferior process '4041' ('foo.exe') started
Hit breakpoint at '/Users/callmekohei/tmp/sample9/foo.cs:8'
#0 [0x00000001] HelloWorld.Hello.Main at /Users/callmekohei/tmp/sample9/foo.cs:8
            string s = "Hello World!";

(sdb) env set s abc

(sdb) env
's' = 'abc'

(sdb) s
Inferior process '4041' ('foo.exe') resumed
Inferior process '4041' ('foo.exe') suspended
#0 [0x00000007] HelloWorld.Hello.Main at /Users/callmekohei/tmp/sample9/foo.cs:9
            Console.WriteLine(s);

(sdb) p s
string it = "Hello World!"

(sdb) env set s abc
(sdb) env
's' = 'abc'

(sdb) p s
string it = "abc"

Actual
(sdb) p s
string it = "Hello World!"

(sdb) env set s abc
(sdb) env
's' = 'abc'

(sdb) p s
string it = "abc"

It's a bit unintuitive, but basically what you need to do is p s = "abc" instead of env set s abc. env is only for manipulating environment variables for the debuggee.

Thank you !!! (^_^)v
I can do it.
I close this issue.


Define relative position of components [syntax help / feature]

Hello,
mermaid is so great, I am really happy I found it - l especially love that its syntax is so compact!
I use it embedded in markdown, through typora. While trying to make some more defined graphs, I encountered the problem that I cannot put textboxes at defined positions. Google was no good friend this time.
graph TB
	idf["I want this left of all"]
	idy["Top of all"]
    subgraph one
    b1-->x
    end
    subgraph two
    b1-->b2
    end
	id4["Between subgraphs 1 and 2"]
    subgraph three
    c1-->c2
    end
  	idss["I want this below all"]

Without subgraphs, it can be put left or right (or top/bottom in LR layout).
graph TB
     id2("It goes left")
     A == 70% ==> B
     A --25%--> C
     A -. 5% .-> D
     id1("It goes right")

If there is a solution, it would be great to include it in the manual.
It seems related to #270 .
I am also not sure, should this question rather be asked on stack overflow? Do you guys follow it?

Flowchart layout is powered by https://github.com/dagrejs/dagre-d3. We can add this feature easily if upstream project supports it.


Race condition when executing continual tests with upgrade framework

Expected Behavior
Tests executed via the upgrade framework in https://github.com/knative/pkg/tree/master/test/upgrade properly run the "continual" tests which run in background during an upgrade.
Actual Behavior
The test framework occasionally detects a race condition when tests are executed with -race flag. The example error can be seen here: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-knative_serverless-operator/804/pull-ci-openshift-knative-serverless-operator-main-4.6-upgrade-tests-aws-ocp-46/1361689216857149440
The stacktrace looks like this:
2021-02-16T15:47:08.236Z	INFO	upgrade/steps.go:57	3) 🔄 Starting continual tests. 3 tests are registered.
2021-02-16T15:47:08.236Z	INFO	upgrade/steps.go:60	3.1) Starting continual tests of "ProbeTest".
    testing.go:954: race detected during execution of test
2021-02-16T15:47:20.489Z	ERROR	upgrade/functions.go:41	💣🤬💔 Upgrade suite have failed!
knative.dev/pkg/test/upgrade.(*Suite).Execute
	/go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/functions.go:41
github.com/openshift-knative/serverless-operator/test/upgrade.TestServerlessUpgrade
	/go/src/github.com/openshift-knative/serverless-operator/test/upgrade/upgrade_test.go:50
testing.tRunner
	/usr/local/go/src/testing/testing.go:1039

Steps to Reproduce the Problem

Define multiple continual tests as defined below
Execute tests with -race flag

suite := pkgupgrade.Suite{
	Tests: pkgupgrade.Tests{
		PreUpgrade:    preUpgradeTests(),
		PostUpgrade:   postUpgradeTests(),
		Continual:     []pkgupgrade.BackgroundOperation{
			servingupgrade.ProbeTest(),
			servingupgrade.AutoscaleSustainingTest(),
			eventingupgrade.ContinualTest(),
		},
	},
  ...
}

Additional Info

More details about the root cause from verbose logs:
=== RUN   TestServerlessUpgrade/ContinualTests/SetupProbeTest
    service.go:98: Creating a new Service service upgrade-probe
    crd.go:36:  resource {<nil> <nil> <*>{&TypeMeta{Kind:,APIVersion:,} &ObjectMeta{Name:upgrade-probe,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[]OwnerReference{},Finalizers:[],ClusterName:,ManagedFields:[]ManagedFieldsEntry{},} {{&ObjectMeta{Name:,GenerateName:,Namespace:,SelfLink:,UID:,ResourceVersion:,Generation:0,CreationTimestamp:0001-01-01 00:00:00 +0000 UTC,DeletionTimestamp:<nil>,DeletionGracePeriodSeconds:nil,Labels:map[string]string{},Annotations:map[string]string{},OwnerReferences:[]OwnerReference{},Finalizers:[],ClusterName:,ManagedFields:[]ManagedFieldsEntry{},}} {<nil>}} {{0 <nil> <nil>} { } {<nil> <nil> <nil>}}} <nil>}
    service.go:116: Waiting for Service to transition to Ready. service upgrade-probe
    service.go:121: Checking to ensure Service Status is populated for Ready service
    service.go:127: Getting latest objects Created by Service
    service.go:130: Successfully created Service upgrade-probe
    spoof.go:103: Spoofing upgrade-probe-serving-tests.apps.ci-op-k6xfg5sw-113e4.origin-ci-int-aws.dev.rhcloud.com -> upgrade-probe-serving-tests.apps.ci-op-k6xfg5sw-113e4.origin-ci-int-aws.dev.rhcloud.com
    prober.go:123: Starting Route prober for http://upgrade-probe-serving-tests.apps.ci-op-k6xfg5sw-113e4.origin-ci-int-aws.dev.rhcloud.com.
==================
WARNING: DATA RACE
Read at 0x00c000edc3a3 by goroutine 97:
  testing.(*common).logDepth()
      /usr/local/go/src/testing/testing.go:710 +0xa7
  testing.(*common).log()
      /usr/local/go/src/testing/testing.go:703 +0x8f
  testing.(*common).Logf()
      /usr/local/go/src/testing/testing.go:749 +0x21
  testing.(*common).Logf-fm()
      /usr/local/go/src/testing/testing.go:749 +0x73
  knative.dev/pkg/test/spoof.New()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/spoof/spoof.go:103 +0x206
  knative.dev/pkg/test.NewSpoofingClient()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/clients.go:47 +0x1df
  knative.dev/serving/test.(*manager).Spawn.func1()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/serving/test/prober.go:142 +0x21b
  golang.org/x/sync/errgroup.(*Group).Go.func1()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/golang.org/x/sync/errgroup/errgroup.go:57 +0x85
Previous write at 0x00c000edc3a3 by goroutine 115:
  testing.tRunner.func1()
      /usr/local/go/src/testing/testing.go:1025 +0x467
  testing.tRunner()
      /usr/local/go/src/testing/testing.go:1043 +0x20d
  knative.dev/pkg/test/upgrade.(*suiteExecution).startContinualTests.func1.1()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/steps.go:67 +0x4f
  testing.tRunner()
      /usr/local/go/src/testing/testing.go:1039 +0x1eb
Goroutine 97 (running) created at:
  golang.org/x/sync/errgroup.(*Group).Go()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/golang.org/x/sync/errgroup/errgroup.go:54 +0x73
  knative.dev/serving/test.(*manager).Spawn()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/serving/test/prober.go:141 +0x69f
  knative.dev/serving/test.RunRouteProber()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/serving/test/prober.go:228 +0x198
  knative.dev/serving/test/upgrade.ProbeTest.func1()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/serving/test/upgrade/probe.go:54 +0x71e
  knative.dev/serving/test/v1.CreateServiceReady()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/serving/test/v1/service.go:99 +0x256
  knative.dev/serving/test/upgrade.ProbeTest.func1()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/serving/test/upgrade/probe.go:45 +0x267
  knative.dev/pkg/test/upgrade.(*suiteExecution).startContinualTests.func1.1()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/steps.go:67 +0x4f
  testing.tRunner()
      /usr/local/go/src/testing/testing.go:1039 +0x1eb
Goroutine 115 (running) created at:
  testing.(*T).Run()
      /usr/local/go/src/testing/testing.go:1090 +0x700
  knative.dev/pkg/test/upgrade.(*suiteExecution).startContinualTests.func1()
      /go/src/github.com/openshift-knative/serverless-operator/vendor/knative.dev/pkg/test/upgrade/steps.go:66 +0x547
  testing.tRunner()
      /usr/local/go/src/testing/testing.go:1039 +0x1eb


ngAnimate not work

I have this container

I use ui-route to change state / route.
In this ui-view I attach this

The section is dynamic based on page content. The problem is that the animation fadeInUp is binded to "div wrapper" and not in "div content-wrapper" where I want it. Any solution??

I think we need some  more information about this issue before we can help you. For instance the CSS that defines the animation. Best of all, if you could provide a working demonstration of the problem you would be more likely to get a solution.

The css works fine, but is attached to a parent div, I cannot make demostration...

In that case we are not able to help.

http://plnkr.co/edit/VxnHAeuZ9JmmallbLVsx
This is plunkr @petebacondarwin

OK I will take a look this week

Thank you, I need your help before as you can :)

So what I see in that plunker is that you have attached the animations to the nested view by using the [ui-view] selector in the CSS and then using data-ui-view on the wrapper view placeholder to prevent it being animated. Right?
I think that the problem is that ui-router is loading the nested view into the wrapper view before the wrapper view is added to the DOM and so the ngAnimate code is not picking up the enter correctly.
I am not sure if this is a problem with ngAnimate or with ui-router.
@matsko, @nateabele or @christopherthielen do you have a view on this?

I also note that this plunker is using angular 1.2.x - have you tried updating to 1.4?

@petebacondarwin  Yes it's right :)
I'm trying with 1.4.x(2-3) but also not work.
Have you a stable fix for this or I should waiting?

I found the issue. You're using data-ui-view in your HTML code, but your CSS selectors are only matching [ui-view]. Make sure that the two are the same:
http://plnkr.co/edit/2VSZtYsjQ2p7lXgVbFlw?p=preview

Isn't correct. I need to make animation in "view-app" and not to div that contain it ("view-layout")
@matsko

@petebacondarwin Our animation code is a little hard to follow because our Angular support goes back a few versions, but this is basically what we do:

https://github.com/angular-ui/ui-router/blob/master/src/viewDirective.js#L219-L223
https://github.com/angular-ui/ui-router/blob/master/src/viewDirective.js#L270-L271

If we need to change up the priority on something, let us know.

I wait other comments, maybe somebody know solutions...
If you see http://themicon.co/theme/angle/v2.6.1/backend-angular/#/app/dashboard I see that the change nesteded state works fine, but in my plunkr not... I take a look a few days I their example but I don't find difference... Maybe is lazyload library?? @petebacondarwin @nateabele @matsko

Nobody?

I need help!

Sorry for the delay. Would you mind testing against these files:
http://www.angular-dev.com/raf-fix/angular.js
http://www.angular-dev.com/raf-fix/angular-animate.js
If not then we can pair tomorrow on the issue via hangouts.

@matsko still not working,
see http://plnkr.co/edit/HbOueeaqRZF6IjNK8PPR?p=preview
Thanks for reply I need fix as soon as possible, thanks!

OK I'll have a look at this tomorrow.

Thank you very much! @matsko

@furyscript
I've updated animate.css from your latest plunk:
http://plnkr.co/edit/EbZVmWugk9UmlENKTfBA?p=preview
Its more like a workaround. Would that do?

Uhm I've a large CSS with all animations adpted see https://daneden.github.io/animate.css/
It's probably impossible or it isn't good updated all css D: @savras
I prefer a really update in code..

And is it possible with this example? http://plnkr.co/edit/m2Cil3QHONx06egtW2Ou?p=preview

HELP!

No solutions? D:

Hi all !!
I'm really happy I've found solution :D
check this plunker: http://plnkr.co/edit/2b2QvcbekC79HnwnbTRB?p=preview
@petebacondarwin @matsko @savras @nateabele

@furyscript Glad that you found a solution. I think this behavior can be attributed more to ui-view than to angular-animate. since it's fixable by changing the API (and if it was a bug with ng-animate I'd expect it to have popped up more often).

@Narretz The DOM implementation for ui-view is a copy of ng-view, so, not likely, unless it's also an ng-view problem.


Is there any way to give the Audio input in the form of a URL?

Hello!
Nope - amen works strictly on local files.
We've got plans to make a web endpoint like the old Echo Nest Remix track/upload, but they're mostly plans for now:  https://github.com/algorithmic-music-exploration/amen-server


Clarify "Cache dependencies" example

I'm trying to understand the Cache dependencies example, but some of it is eluding me.
First off, please clarify what is meant by "parent" and "child".  I'm confused as to which expires upon the expiry of which other.
CancellationTokenSource allows evicting multiple cache entries as a group.  But what's the point of the using block in the example?  I downloaded the sample project and replaced the using block with the following:
_cache.Set( CacheKeys.Parent, DateTime.Now, new CancellationChangeToken( cts.Token ) );
_cache.Set( CacheKeys.Child, DateTime.Now, new CancellationChangeToken( cts.Token ) );

While my two lines are simpler, they seem to have the same effect as the using block.  The doc says:

With the using pattern in the code above, cache entries created inside the using block will inherit triggers and expiration settings.

What does "triggers and expiration settings" refer to here?
I must add dependent cache entries in my application, but they must be added at separate times.  Therefore I can't take the approach shown in the example's using block since it requires both entries be added at the same time, right?  What functionality am I missing out on by instead taking the approach shown above in my two lines of code?
Finally, shouldn't Dispose be called on CancellationTokenSource after the Cancel call?  The sample doesn't do that.

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

ID: 13f5f8f9-18dd-9c12-9ed1-fcc6b44ba7fd
Version Independent ID: 640b4f36-5886-7b69-1c95-cfc8574a02fd
Content: Cache in-memory in ASP.NET Core
Content Source: aspnetcore/performance/caching/memory.md
Product: aspnet-core
Technology: aspnetcore-performance
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

First off, please clarify what is meant by "parent" and "child".
It's the normal computer science parent child.

public IActionResult CreateDependentEntries()
{
    var cts = new CancellationTokenSource();
    _cache.Set(CacheKeys.DependentCTS, cts);

    using (var entry = _cache.CreateEntry(CacheKeys.Parent))
    {
        // expire this entry if the dependant entry expires.
        entry.Value = DateTime.Now;
        entry.RegisterPostEvictionCallback(DependentEvictionCallback, this);

        _cache.Set(CacheKeys.Child,
            DateTime.Now,
            new CancellationChangeToken(cts.Token));
    }

    return RedirectToAction("GetDependentEntries");
}
``

> I'm confused as to which expires upon the expiry of which other.

Per the doc,

When Cancel is called on the CancellationTokenSource, both cache entries are evicted.

> What does "triggers and expiration settings" refer to here?

Per the doc:

Any activity on the cache (Get, Set, Remove) can trigger a background scan for expired items. A timer on the CancellationTokenSource (CancelAfter) also removes the entry and trigger a scan for expired items.

When Cancel is called on the CancellationTokenSource, both cache entries are evicted.

How is this "the normal computer science parent child"?  If they're mutually dependent then they're siblings rather than parent/child.  Better to avoid confusion by calling it what it is.

Any activity on the cache (Get, Set, Remove) can trigger a background scan for expired items.

You copy and pasted that from a different section of the doc.  It doesn't flow from the section we're discussing and I don't see how it fits together.  What code in the example of the same section does "triggers and expiration settings" refer to?  If there isn't any then please add some to demonstrate.
Please kindly answer my last two questions:

I must add dependent cache entries in my application, but they must be added at separate times. Therefore I can't take the approach shown in the example's using block since it requires both entries be added at the same time, right? What functionality am I missing out on by instead taking the approach shown above in my two lines of code?
Finally, shouldn't Dispose be called on CancellationTokenSource after the Cancel call? The sample doesn't do that.

Please consider improving the doc instead of simply closing this issue.


[enhancement] add release workfolow for daily release and tag event.

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage
/sig storage

/kind documentation
What this PR does / why we need it:
Add a release workflow for updating images daily and updating images when a new tag is created.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

/assign @Congrool
Does this PR introduce a user-facing change?

other Note

Seems some problems here: If we are not at the tag, the image-tag should be the tag, otherwise it should be latest. However, make rule will tag the image as GIT_VERSION which is based on the IMAGE_TAG and not be exposed to outside. Thus, what we set in IMAGE_TAG will not work. Maybe we have to revise the makefile to make it work.

@rambohe-ch Thanks for your feedback. and I have exposed IMAGE_TAG as global env, so end user can set this env in the github action.

Thanks for your feedback. and I have exposed IMAGE_TAG as global env, so end user can set this env in the github action.

Well, I mean GIT_VERSION is not exposed to the outside, it is the tag what images will actually use. You can find it here:
https://github.com/openyurtio/openyurt/blob/master/Makefile#L99
The arguments of -t option is ${IMAGE_REPO}/yurthub:${GIT_VERSION}, not the ${IMAGE_TAG}. So, I think it may need to be revised.

Thanks for your feedback. and I have exposed IMAGE_TAG as global env, so end user can set this env in the github action.

Well, I mean GIT_VERSION is not exposed to the outside, it is the tag what images will actually use. You can find it here: https://github.com/openyurtio/openyurt/blob/master/Makefile#L99
The argument of -t option is ${IMAGE_REPO}/yurthub:${GIT_VERSION}, not the ${IMAGE_TAG}. So, I think it may need to be revised.

@Congrool fixed it.

/lgtm
It looks good to release image daily. But these logic in makefile will make it a little bit complicated and difficult to use. It's better the move them into a script. Maybe we can do it in further work.

/lgtm


require('psi'): Error connecting to http://localhost:$PORT/insights (ECONNREFUSED)

As soon as I add psi as a required dependency I start getting ✗ Error connecting to http://localhost:50780/insights (ECONNREFUSED) (the port number randomly changes, of course).
Here's the reference solution.js:
'use strict';

var fs = require('fs');
var path = require('path');
var express = require('express');
var psi = require('psi');

var app = express();
var port = process.env.PORT || 7777;

app.get('/', home);
app.get('/insights', insights);
app.listen(port, listening);

function listening () {
  console.log('Listening on port', port);
}

function home (req, res) {
  var file = path.join(__dirname, 'index.html');
  var index = fs.readFileSync(file, 'utf8');
  res.send(index);
}

function insights (req, res) {
  res.end('Not very insightful!');
}

As soon as I comment the PSI line I get
perfschool run solution.js                                                     [0:14:12]

# /insights produces valuable information about page weight
✓ Returns a 200 OK status code
✗ Returns a JSON object
✗ Response has a "resources" property
✗ Response has a "resources.js" property
✗ Response has a "resources.css" property
✗ Response has a "resources.total" property
✗ Response has a "resources.hosts" property

As soon as uncomment — the reported error.

Also the PSI response format has changed, here's the recent one:
{
numberResources: 18,
numberHosts: 6,
totalRequestBytes: "1986",
numberStaticResources: 14,
htmlResponseBytes: "2959",
cssResponseBytes: "175745",
imageResponseBytes: "1342803",
javascriptResponseBytes: "230129",
otherResponseBytes: "755",
numberJsResources: 3,
numberCssResources: 3
}

(I got it by manually running the proper solution.js with node and copying the result from the browser.)

Could you create a PR fixing this issue?

Unfortunately I'm not sure how to fix it, the format change doesn't look like the main source of the problem, see the 1st message

Hi! I also faced with this problem (ECONNREFUSED).
After examining the code a bit, I came to the conclusion that solution server doesn't have time to run.
Timeout for calling test method I'm found in workshopper-wat module. I just increase this value and the problem was solved.
Maybe it's because I'm set up tunnel globally, not in test method, and it takes some time.

Cool. We should improve that method to wait on something listening on that port and time out after something like 10s

The timeout issue should be resolved now.


Re-enable interop with MLS++ on CI

We had previously disabled it due to a bug in CMake. See the PR description of #1555 for more info.

This is enabled again.


Refactor petitio to got

Summary
Due to the unsupported node 16+ version on petition (https://github.com/helperdiscord/petitio/issues/40) which causes all one link deployments (railway and etc...) to not work. Closes #35
Test Plan
Unfortunately due to lacking existing test suite mostly doing manual tests for this, would love to get some help to spot potential errors. We have also deployed this to our own self-hosted version and working with this for the last couple of days with no issues.
Related Issues
Closes #35

@tedspare refactored petitio for got due to lack of petition node support and quite small community traction for npm downloads and general github activity.
This PR created quite a lot of changes due to prettier which I'm sorry for, but it would require me too much work to separate prettier away :( Would suggest to add this as a dependency in another PR later anyway. Hope this is ok 🙏

Initially was thinking it's because of a missing prettier rc which i now see that it exists. Prettier package is not installed on the repo which might caused prettier not working at all if it's not installed globally. Maybe that's the case?

@tedspare done most of those tests manually in the last days, hard for me to guarantee all functionality and edges cases work tho. I hope I will be able to add a basic test suite infrastructure because testing everything manually each time is quite a lot of time :(

@tedspare done most of those tests manually in the last days, hard for me to guarantee all functionality and edges cases work tho. I hope I will be able to add a basic test suite infrastructure because testing everything manually each time is quite a lot of time :(

Makes sense and thanks for working through this! The project is still young.

Done @tedspare 🚀


Darkviperau

Added Disingenuous dense motherfucker and low polygon motherfucker by DarkViperAU

If you can fix the build, I'll merge.

ok it was a typo, a singular "u" was missing x)
Travis is still running checks but the npm test returned no errors for me so I guess it should be good when travis is done

Coverage remained the same at 100.0% when pulling 4e154cf7d0187177873cef02b0f1d3aba1464ab7 on Khoding:darkviperau into 100b7587349a9b3064804a2e4a4dd72589637349 on tomdionysus:master.


lxd/images: Cleanup any leftovers on startup

As LXD may have been downloading or publishing an image as it got
restarted or crashed, it's not that unusual for there to be leftovers in
the images directory.
This adds a function which compares the content of the images directory
with what's expected to be there according to the database and deletes
any file that shouldn't be there.
Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

jenkins: test this please

Wasn't sure if I could merge since Jenkins was all red but it seemed somewhat unrelated.


Clarification about description

Dear Developer(s),
Thank you for an awesome product!
I have used the addon once or twice but both times had a hard time understanding the descriptive lines:
"Set the number of days to keep history items in the options page. Setting it to 0 will disable history deletion"
Does Setting it to 0 will disable the history deletion add-on or will it retain the history forever (bloating the places.sqlite file) until manually deleted?
You might want to change these lines correspondingly at all the places to put it more clearly.
Thanks and keep up the good work!
Sincerely,
Inderjeet

Hello,
Sorry about the confusion. Setting it to 0 only prevents this extension from deleting history. Having the setting default to 0 (disabled) means the extension won't delete anything until the user sets their preferred number of days.
This extension can't (and won't) prevent you from deleting history through other means.
Hope this helps!


feat(fmt): Add support for comments

Opening a draft to get some feedback on comments. Essentially the way comments are handled is by splitting them into two categories, prefixes and postfixes and types line and block comments
/* this is a prefix block comment */
let var = 1; // this is a postfix line comment

and trying to appropriately insert them where necessary, where prefixes need to start on a new line and line comments can't have anything follow them. As comments aren't in the parse tree the challenge is to try to figure out when to insert them appropriately and how to deal with the whitespace that they may or may not create.
This is essentially done by the adding a Comments context to the formatter and popping off comments as chunks get written via the write_chunk function and sometimes manually where more control is needed.
What I start doing here as well is to use the IndentWriter more by allowing the writing of multiple lines at a time as chunks can now be multiline given they contain line or prefix comments, and foregoing some of the assumptions of item size / line count before
The next steps are probably

[ ] Replace all write! functions where necessary with write_chunk!
[ ] Replace all write_items_separated with write_chunks_separated
[ ] Lots and lots of tests
[ ] Cleanup / refactor to find more patterns like write_chunks_separated (this will most likely be important when starting to really implement expressions and handling nesting / operator grouping)

Could you rebase/cherry-pick the last few commits on latest master?

@rkrasiuk wanna take a stab at the above?

closing for #1833


Avoid matching <x:Envelope> tags inside comments

I have a specific case where I fail to use node-soap because the wsdl service is sending me an xml with a comment that includes an example of an Envelope node:
<RealNode>
...
<!--
  Use this format for something:
    <ins:Envelope>
       Bla Bla Bla
    </ins:Envelope>...
-->
</RealNode>

The current code picks this piece of the comment and tries to work with <ins:Envelope> Bla Bla Bla </ins:Envelope> as the body of the request.
This PR solves this by matching on the body after removing comments.

Coverage remained the same at 92.715% when pulling 6c7635069857dca3bfe5e96417a404a822189933 on ranhalprin:master into 19e6ca93792e6594e6df02a74af6eed0767b500a on vpulim:master.

thanks a lot @ranhalprin - could you please add tests as outlined in our Guidelines on Submitting a Pull Request so that we can asure, that your code does not get overridden/ripped out accidentially? :+1:

Thanks @herom, added a test that fails without my change.

Coverage remained the same at 92.715% when pulling b7d6582e7cc01ce5a3ec494e9bfbbbb7e24d7db5 on ranhalprin:master into 19e6ca93792e6594e6df02a74af6eed0767b500a on vpulim:master.

Coverage remained the same at 92.715% when pulling b7d6582e7cc01ce5a3ec494e9bfbbbb7e24d7db5 on ranhalprin:master into 19e6ca93792e6594e6df02a74af6eed0767b500a on vpulim:master.

Coverage remained the same at 92.715% when pulling b7d6582e7cc01ce5a3ec494e9bfbbbb7e24d7db5 on ranhalprin:master into 19e6ca93792e6594e6df02a74af6eed0767b500a on vpulim:master.

Awesome! Thanks a ton :dancers:

Hello,
I have a content with "" inside my soap response, and with the
var match =       body.replace(/<!--[\s\S]*?-->/, "").match(/(?:<\?[^?]*\?>[\s]*)?<([^:]*):Envelope([\S\s]*)<\/\1:Envelope>/i);     if (match) {       body = match[0];
insctruction, the first comment is deleted, beceause the body is valid for the second regular expression.
Is it normal to remove any first "" in the response even if it doesn't contain  code ?
In order to not remove my necessary comment, I surchage the handleResponse, but I'm not sure that's the good way, and I prefer to let you know this behavior.
And the other way, thank you for all your work, soap library is very usefull !!!

hey @cedricrey,
thanks a lot for your kind words 😺
it would be awesome if you could show us what you'd expect our library to output if it hits your case with a PR 👍

Hello @herom,
I'm sorry I've never post on github, I don't know how to do :-)
I don't know what is a PR.
My case is : I create a soap client, and when I request with it, the response has HTML content in it, something like that :
<Envelope><data><content><source><[!CDATA[<!--some necessary comment --><html>....</html>]]></source></content></data></Envelope>
And when I get the response from the client, the first html comment (<!--some necessary comment -->) was deleted from the content.
After investigation, I found that was comming from the HttpClient.prototype.handleResponse, particulary the .replace(/<!--[\s\S]*?-->/, ""). I found that code were added for this pull request.
Is this delete expected ? I may be wrong and have forgot something in the use of the library.


FPGA: Minor changes to qrd/qri/cholesky/cholesky_inversion

Existing Sample Changes
Description
This change makes multiple small updates to the QRD/QRI/Cholesky/Cholesky_inversion code samples:

QRI: updated tar location
QRD: remove unneeded RAM from copying R to the FPGA DDR
QRD/QRI: remove 1,2….7 prints
QRD: remove unneeded shannonization
QRD/QRI: cmake will no longer fail when an unknown board is given but will instead use the A10 default parameters
QRD/QRI/Cholesky/Cholesky_inversion: make the design parameters configurable from the cmake command rather than environment variables

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

[x] Command Line

Hey @jimmytwei, could you have a look at this PR? It has been internally reviewed and validated, thanks!


Add render threshold

Fixes https://github.com/CartoDB/carto-vl/issues/336

I'm not very happy with this threshold adjustment. What is the real reason for the issue? Retina, the color space?

Try the same: configuring your color space to Display P3 or Color LCD to SD 170M-A


Be able to declare pre-hooks and post-hooks

If no one has anything against it, I would like to work with that 💃


added patch scripts for debian 10 and linux vanilla

L515 working on Debian 10
zip@aware:~/librealsense$ uname -a
Linux aware 5.0.21-rt16 #1 SMP PREEMPT Fri Jun 19 14:05:53 MDT 2020 x86_64 GNU/Linux
zip@aware:~/librealsense$ lsusb
Bus 002 Device 005: ID 8086:0b64 Intel Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2104:0124
Bus 001 Device 003: ID 1bcf:2b97 Sunplus Innovation Technology Inc.
Bus 001 Device 002: ID 187c:0550 Alienware Corporation
Bus 001 Device 006: ID 8087:0025 Intel Corp.
Bus 001 Device 005: ID 0d62:e90c Darfon Electronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
zip@aware:~/librealsense$ modinfo uvcvideo | grep "version:"
version:        1.1.1
srcversion:     D52EDAEED04C3FC3C88AFD1

[ 1013.429278] usb 2-6: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd
[ 1013.450507] usb 2-6: New USB device found, idVendor=8086, idProduct=0b64, bcdDevice=10.41
[ 1013.450515] usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1013.450519] usb 2-6: Product: Intel(R) RealSense(TM) 515
[ 1013.450521] usb 2-6: Manufacturer: Intel(R) RealSense(TM) Camera
[ 1013.450524] usb 2-6: SerialNumber: 00000000F0171941
[ 1013.458786] uvcvideo: Found UVC 1.50 device Intel(R) RealSense(TM) 515 (8086:0b64)

This attempts on any kernel version you specify using all of the patches in your repo.
The only kernel you have specified in the patches is 4.8, this works with 5.0.21 as specified in the comments.
Thank You,
Andrew Hodel

On Jun 22, 2020, at 4:47 AM, ev-mp<EMAIL_ADDRESS>wrote:

@ev-mp commented on this pull request.
In scripts/patch-debian-10.sh:

+# use -c to continue existing downloads
+wget -c https://mirrors.edge.kernel.org/pub/linux/kernel/v5.x/linux-${KV1}.${KV2}.${KV3}.tar.xz
+wget -c https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/${KV1}.${KV2}/patch-${KV1}.${KV2}.${KV3}-rt${RT}.patch.xz

+# use -k, keep the input files so they don't have to be redownloaded if you restart the script
+# use -f, overwrite existing in the case of restart
+unxz -kf linux-${KV1}.${KV2}.${KV3}.tar.xz
+unxz -kf patch-${KV1}.${KV2}.${KV3}-rt${RT}.patch.xz
+
+tar xf linux-${KV1}.${KV2}.${KV3}.tar
+cd linux-${KV1}.${KV2}.${KV3}
+
+patch -p1 < ../patch-${KV1}.${KV2}.${KV3}-rt${RT}.patch
+
+# this will apply all patches
+patch -p1 < ../*.patch
@andrewhodel , you need to specify and provide the exact patches to be built into the kernel.
Though I don't see how this is going be implemented - Librealsense patches are different from kernel to kernel so you can't have a single version/ fit all approach.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@andrewhodel hello, as I've explained in #6650 this approach is not viable.

This attempts on any kernel version you specify using all of the patches in your repo.

The patches are managed and specified per specific kernel version. There is no solution that fits all kernel.

The only kernel you have specified in the patches is 4.8, this works with 5.0.21 as specified in the comments.

It is not clear which patch you reviewed to reach this conclusion. The official patches cover all  Ubuntu LTS kernels in the range of 4.4 .... 5.3 (Xenial+Bionic).
In case you're not sure about which patches should be selected you can invoke/review the script from the [installation guide]:(https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md#prerequisites)
./scripts/patch-realsense-ubuntu-lts.sh
The script doesn't evaluate the selected patches, so how can one verify that (a) proper patches are selected and (b) the patches were applied correctly ?
What librealsense-specific tests do you run to validate that the compiled kernel was patched properly ?

Please review #6650 again, as this in its current form this PR cannot lead to merge.

You can just apply all patches using a wildcard and the ones for the
correct kernel code will apply properly.
It's a fundamental of patch and diff routines.
Andrew
On Tue, Jun 23, 2020 at 12:58 AM ev-mp<EMAIL_ADDRESS>wrote:

@andrewhodel https://github.com/andrewhodel hello, as I've explained in
#6650 https://github.com/IntelRealSense/librealsense/issues/6650 this
approach is not viable.
This attempts on any kernel version you specify using all of the patches
in your repo.
The patches are managed and specified per specific kernel version. There
is no solution that fits all kernel.
The only kernel you have specified in the patches is 4.8, this works with
5.0.21 as specified in the comments.

It is not clear which patch you reviewed to reach this conclusion.
The official patches cover all Ubuntu LTS kernels in the range of 4.4 ....
5.3 (Xenial+Bionic).
In case you're not sure about which patches should be selected you can
invoke/review the script from the [installation guide]:(
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md#prerequisites
)
./scripts/patch-realsense-ubuntu-lts.sh
The script doesn't evaluate the selected patches, so how can one
verify that (a) proper patches are selected and (b) the patches were
applied correctly ?
What librealsense-specific tests do you run to validate that the
compiled kernel was patched properly ?

Please review #6650
https://github.com/IntelRealSense/librealsense/issues/6650 again, as
this in its current form this PR cannot lead to merge.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/pull/6653#issuecomment-647949212,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVCSOWYSTCNBUFXXCBW2DRYBHCNANCNFSM4ODBNKRA
.

That's why a diff is byte by byte, by design only the patch files that can
be applied will be applied and if you are only creating files for each
kernel version then you will get the right one with patch -p1 < *.patch or
you created 2 patch files that are identical for different versions which
will still work in this case.
On Tue, Jun 23, 2020 at 9:24 AM Andrew Hodel<EMAIL_ADDRESS>wrote:

You can just apply all patches using a wildcard and the ones for the
correct kernel code will apply properly.
It's a fundamental of patch and diff routines.
Andrew
On Tue, Jun 23, 2020 at 12:58 AM ev-mp<EMAIL_ADDRESS>wrote:

@andrewhodel https://github.com/andrewhodel hello, as I've explained
in #6650 https://github.com/IntelRealSense/librealsense/issues/6650
this approach is not viable.
This attempts on any kernel version you specify using all of the patches
in your repo.
The patches are managed and specified per specific kernel version. There
is no solution that fits all kernel.
The only kernel you have specified in the patches is 4.8, this works with
5.0.21 as specified in the comments.

It is not clear which patch you reviewed to reach this conclusion.
The official patches cover all Ubuntu LTS kernels in the range of 4.4 ....
5.3 (Xenial+Bionic).
In case you're not sure about which patches should be selected you
can invoke/review the script from the [installation guide]:(
https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md#prerequisites
)
./scripts/patch-realsense-ubuntu-lts.sh
The script doesn't evaluate the selected patches, so how can one
verify that (a) proper patches are selected and (b) the patches were
applied correctly ?
What librealsense-specific tests do you run to validate that the
compiled kernel was patched properly ?

Please review #6650
https://github.com/IntelRealSense/librealsense/issues/6650 again, as
this in its current form this PR cannot lead to merge.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/pull/6653#issuecomment-647949212,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVCSOWYSTCNBUFXXCBW2DRYBHCNANCNFSM4ODBNKRA
.

@andrewhodel hello,
In order to proceed with the PR we'll need your cooperation to address the comments.

This question was already raised but I need to reiterate it - what method did you use to ensure that the patches were properly applied?
As already stated Realsense Depth cameras are UVC-compliant devices that run with vanilla kernels. Hence the lsusb's cannot be used to assert that the correctness of the patches. See #6837 for alternative methods.
Recompiling the whole kernel is not a method we recommend, and the script need to be refactored such that instead of recompiling and replacing the kernel only the affected loadable modules will be rebuilt as in Ubuntu's case.

Patches, and the patch code originally developed for old unix systems and
still in use 40+ years later will only apply a patch file if the code
blocks being modified are 100% the same.
Your concern about rebuilding the kernel is just when speaking about 1
distribution, Ubuntu and DKMS specifically. It is not true with the other
hundreds of distributions.
Andrew
On Tue, Jul 21, 2020 at 2:10 PM ev-mp<EMAIL_ADDRESS>wrote:

@andrewhodel https://github.com/andrewhodel hello,
In order to proceed with the PR we'll need your cooperation to address the
comments.

This question was already raised but I need to reiterate it - what
method did you use to ensure that the patches were properly applied?
As already stated Realsense Depth cameras are UVC-compliant devices
that run with vanilla kernels. Hence the lsusb's cannot be used to
assert that the correctness of the patches. See #6837
https://github.com/IntelRealSense/librealsense/issues/6837 for
alternative methods.
Recompiling the whole kernel is not a method we recommend, and the
script need to be refactored such that instead of recompiling and replacing
the kernel only the affected loadable modules will be rebuilt as in
Ubuntu's case.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IntelRealSense/librealsense/pull/6653#issuecomment-662080823,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVCSMMBFSKZZGO762H3ATR4XY3FANCNFSM4ODBNKRA
.


add aliases, remove register function, allow flexible args in !ag

This adds various aliases for commands.
It also removes the !register command and will now silently register users in the DB if they are not already.
Also adds flexible arguments when adding gains, and will automagically figure out which arg is the name of the exercise and which is the number of reps performed.


Update patternfly & angular-patternfly dependencies to 3.5.1

Updated patternfly & angular-patternfly to 3.5.1, minor updates to some dependencies..
Removed old bower overrides, and unused moment.js.

[x] check changes in patternfly 2.3.0 -> 3.5.1
[x] check changes in angular-patternfly 2.3.2  -> 3.5.1
separate PR:

update angular-bootstrap to 1.* (angular-patternfy forces 0.13)
same for lodash

[x] check list-view item styling changes .. good enough :)
[x] check select default item behaviour changes (schedule service retirement)
[x] 3.5.1 -> 3.6.0

@dclarizio should be ready for review.. :)


Update active-directory-deploying-ws-ad-guidelines.md

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@tobunka-git : Thanks for your contribution to the Azure documentation! The author, @femila, has been notified to review your proposed change.

#sign-off


Duplicated CSSStyleDeclaration

Since #74 linkedom depends on cssom which implements CSSStyleDeclaration class.
Because of this, the implementation of the same class located in interface/css-style-declaration.js is redundant, and actually brings also bug, having it a very poor implementation of the CSS Object Model, compared to that of cssom.
All the imports to interface/css-style-declaration.js should be redirected to cssom
I'd make a PR, if I haven't one opened already.

is redundant, and actually brings also bug, having it a very poor implementation of the CSS Object Model, compared to that of cssom.

but it's fast, right?

Surely, but it hasn't many function, like setProperty, which instead cssom has.
Or we implement other functionality trying to keep it as fast as it is now or we switch to cssom

I need to see if that class is on the critical path for rendering. If it's not, I am OK switching to a better class instead of reinvent the wheel, since the dependency is already in, but if that's the case, maybe we can think about some lazy-upgrade as dealing with CSS as if it was a browser is out of this module scope, there's JSDOM for that, here there's no goal to be 1:1 with all the Web standards.
I hope this makes sense.

Thank you.
Reading your last message and the fact this is another issue I'm encountering with this library make me think that probably I should flag JSDOM to riot/ssr (a library that I use that depends on linkedom)...

So ... reason I am using my class is that it's hooked with MutationObservers and Custom Elements observed attributes.
If I use any foreign class I need to be sure changes in there are reflected, otherwise nothing works.
Is there anything in particular that is not working, or why is the fact two modules have same CSSStyleDeclaration an issue?

The only real problem, beyond the absence of some functionality, could be an expression where a style declaration object is compared with instanceof with the class and it won't work because it is an instance of the class of the other library. I think that this is a rare edge-case, so we can live along with that.
I found this because I tried using setProperty function, which isn't implement, so the main issue is the lack of functionality.

I could bring in the class and extend it: instanceof would work, but I need to check the rest of the methods.

Turns out, rollup found that cssom CSSStyleDeclaration has some circular dependency, causing issues even on  build ... I don't think I should use that directly, but if that was your concern, I think there's a cssom issue to solve first.


Dumping ttir and ttnn into json files

This PR addresses issue #149 by adding functionality to reportify for formatting and storing MLIR input (ttir) and MLIR output (ttnn) in a JSON file. With this update, running any module will save MLIR information within the path testify/ll-sw/%MODULE_NAME%/mlir_reports as ttir.mlir and ttnn.mlir.
Fix #149

@vkovinicTT minor comment, can we open the following issues with the tech dept label: Visualizing stored MLIR IR in Visualizer (e.g. reportify).
There is no need to work on it as a next task, but let's keep it as something to take a look in the future :))


[core] make browser-implementation of getEnv() return only defaults, getEnvWithoutDefaults() an empty object

Description

[!IMPORTANT]
Only actionable for next branch. Any PRs opened for this MUST be based on and targeted at the next branch.

The @opentelemetry/core package contains a browser implementation of getEnv() that attempts to get the configuration from the _globalThis (similar to getting env vars from process.env in Node.js). This behvaior

duplicates ways to configure components that have to be set up via code anyway
increases bundle size
significantly increases test-complexity
significantly increases code-complexity
confuses users who are looking for the "right" way to do things

Since removing getEnv() completely would be quite an undertaking and would result in a large, difficult to review PR, this issue focuses on:

disabling the functionality of getEnv() and getEnvWithoutDefaults() so that it does not extract config from _globalThis
removing any browser tests (run via the npm run test:browser script) that tested this behavior.

Since the behavior is then not present anymore when we release 2.0, removing getEnv() usage for browser code can be a non-breaking change and can be done in a feature-release. We can remove usages of getEnv() and getEnvWithoutDefaults() step-by-step throughout the code base as a clean-up in feature releases. This should yield bundle-size improvements and an eventual further reduction of code-complexity.
This issue is considered done when:

[ ] getEnv() has been changed returns a copy of DEFAULT_ENVIRONMENT for the browser implementation
[ ] getEnvWithoutDefaults() has been changed to return a new empty object for the browser implementation
[ ] any tests that rely on this behavior have been removed or adapted

note: please do not blindly remove all tests. some tests may be used both in Node.js and Browser (usually in common directories) - you may have to adapt some tests and move them to different directories so that the only run on Node.js

[ ] a follow-up issue to track removing getEnv() and getEnvWithoutDefaults() in a feature release has been created

Code location

https://github.com/open-telemetry/opentelemetry-js/blob/141b457b8513069b64a5f246165167832fc0d83a/packages/opentelemetry-core/src/platform/browser/environment.ts#L28-L37

duplicates ways to configure components that have to be set up via code anyway

@pichlermarc do you feel confident that all the configs currently settable via globalThis.OTLP_* variables have obvious programmatic equivalents? I ask because I looked into implementing this, but having to update some of the existing tests revealed that some of the migration (for users) can be less than straight-forward, if possible at all.
If you currently set one of the OTEL_* variables, you'd often have to look deeply into the implementation source code to see how they are being used to infer what the equivalent is. Sometimes it is used deep inside the construction of nested/related objects that you won't otherwise have to construct yourself today when using these variables, making the migration non-trivial, if possible at all.
Some variables have no obvious replacement (that I could find). For example, #4897 plan on using the OTEL_SEMCONV_STABILITY_OPT_IN in the migration plan, which you can't otherwise set.
So if we are going ahead with this, I think we'd have to:

Audit the existing variable, triage them into "not supported on the web", "have programmatic replacement API", "need new programatic API"
Write up a migration guide to document the replacement for each of the supported variables

That seems like a pretty significant lift to me, but perhaps it feels more tractable to someone with more context.
Alternatively, here is a counterproposal that would capture most of the same benefits, but less aggressive:

Introduce a new entrypoint @opentelemetry/core/browser-env, or somewhat equivalently, a new package @opentelemetry/browser-env
Export a setEnv({ ... }) function from @opentelemetry/core/browser-env as a direct replacement for setting the variables on globalThis
Ensure all the internal validation and parsing code (e.g. "true" -> true) are only required within @opentelemetry/core/browser-env
setEnv({ ... }) will validate and parse the variables, and privately set the parsed result as module state in core or something like globalThis._PRIVATE_OTEL_PARSED_ENV
getEnvWithoutDefaults() in core can simply return the parsed result, if set, and getEnv() is simply { ...DEFAULTS, ...PARSED_ENV }

Benefits:

Existing code that already uses those variables have a straightforward migration path, they can migrate the the programmatic APIs over time and won't be blocked from upgrading to 2.0 just because of this issue
We can start prioritizing documenting the programmatic APIs and make clear that those are the preferred way
In a bundler that supports tree-shaking, this should realize the same bundle size benefits for code that doesn't use the new entrypoint/package
If we do this as a separate package, the README for the package itself can document that the programmatic APIs are preferable, and can serve as the migration guide; we can deprecate the package itself when we feel confident about the coverage and that the community had enough time to absorb the changes

As far as reducing the test and code complexity, so far I am not sure that would be the case anyway. As you pointed out, most of the code consuming getEnv() are shared between both environments. So long as the node version is still required to support customizing the behavior based on those ENV variables (to maintain parity/consistency with other language SDKs), the getEnv() abstraction (even if it does ~nothing in the browser) seems to make it easier to share the code and test the customizations.
Part of the issue I ran into when implementing this is precisely that – the current tests are written to both 1. test that setting the ENV variable has the desired effect, and 2. test the functionality of said "desired effect". Since even under the original proposal, this should continue to work in Node, we still need the tests for (1) in Node, but it's hard to test that without actually test the functionality, so it ends up requiring the tests to be duplicated (plus a lot of adaptation to the existing test that resulted in more elaborate setup).

@chancancode thanks for the detailed write-up - yes you're right it's a pretty significant change with lots of moving parts, I think this needs some more thought so I'll apply the needs:refinement label and we can go back to the drawing board on this.
The long-term goal is to remove "automatic configuration" via environment variables (or env-var like config in the case of the web implementations) from the plain SDK packages @opentelemetry/sdk-trace*, @opentelemetry/sdk-metrics* (it's already gone there), @opentelemetry/sdk-logs (that's experimental and we may introduce breaking changes later, so it's out of scope for now) and move them to a package like @opentelemetry/sdk-node, since there's additional specification on the way that will provide an alternative way of configuring that will override env-var config - but I think that needs more discussion with the other maintainers before we can make a move on this.
I'll put this on ice right now since there are some other changes I'm thinking of (and that I did not write down yet) which may make this change here significantly easier.

I'll update the issue once we've come up with a more comprehensive plan.


escape character closing bracket bug

The opening bracket character \{ is correctly handled, but the closing bracket \} produces the sequence:
}\}

Thank you for reporting! I'm sorry this took a while to process but it should be fixed now.


chores: requesting information from Zuzalu

What do we need to know?

[ ] Assets to have refs for the design of the pages
[ ] All badges they want to emit
[ ] Will they want to assign managers during the event period themselves? ( the ones that can check-in users)
[ ] Will they want to have full control over the Resolver?
[ ] Will they want to create new badges during the event?
[ ] Will they want a vanity address for their contract? (max 12 decimals)

Hey, gm!
Heads up on it:

Assets to have refs for the design of the pages
All badges they want to emit:

changed my mind about X, phrasing has to be confirmed
disagreed with somebody on stage
create session on Zuzalu.city
check in proof of personhood
check out time elapsed
write on Zuzagora
voted on significant poll
early contributors
one for each week? With theme of week
volunteer during event
start a new club
host a discussion

The rest of the questions I'm waiting for a response.
Thanks Mr. Neves

Another very importante questions, who will do the checkout? the user or a manager of zuzalu?  Also important, will managers of Zulalu be allowed to force checkout users?

What are the comments we should use in this section?

What are the comments we should use in this section?

1) What is Trustful?
Trustful is a reputation aggregator system designed to match governance, participation, and efforts. Using the Ethereum Attestation Service (EAS) and a badge system, we can attest to specific participation and ensure that this on-chain information results in a scoring system. This system can be used for resource allocation, governance, and more.
2) How does Trustful work in ZuVillage?
In ZuVillage, your interactions and contributions will be attested to and stored on-chain. This promotes dialogue, avoids echo chambers, and encourages active participation. In the future, this aggregated reputation can be used to benefit participants, providing them with recognition.
3) What do you need to do now?

_Now that you have connected your wallet, you need to do the check-in.
Your check-in badge will be your first badge, unlocking the creation of other badges.
By interacting with the event, whether by disagreeing with someone, actively participating in talks, or creating sessions, you can create or attest to badges.
This process builds your reputation, tied to your wallet, based on your interactions._

More questions that may appear
What is the check out for?
The check out badge confirms that you are ending your stay at ZuVillage Georgia. It will be used to calculate how long you lived in our ZuVillage, which will contribute to your ZuVillager reputation score. It also helps us keep track of how many people are currently present. Thank you for joining us at ZuVillage Georgia!
What is the check out badge?
The check out badge is an advanced reputation aggregator built by Trustful. Trustful aims to foster real connections and deep dialogues, facilitating check-in processes and enabling attestations of the quality of interactions and the convergence of ideas. By integrating Trustful into ZuVillage Georgia, Trustful aims to create an environment where reputation is defined and recognized based on the community's unique values, ensuring that members' contributions and interactions are duly valued. This first OP version for ZuVillage Georgia will focus on creating new Statement Badges and it will allow organizers and attendants of a Zuzalu pop-up village event to give badges to each other in recognition of their contributions and knowledge. This mobile-first version aims to enable the community to create its first badges, which members will later use to generate Reputation Scores.


feat: add a safe-await helper

Added the safe await helper, ported to TypeScript.
Function has the signature:
function safeAwait<T>(promise: Promise<T>, finallyFn?: (() => void) | undefined): Promise<readonly [Error] | readonly [undefined, T]>

@kyranjamie in the util itself, can you comment an example that we could add to the docs once they're up and running?

The types could be improved here actually.
    const [error, data] = await safeAwait(deriveRootKeychainFromMnemonic(mnemonic, ''));

    if (error) {
      setError('Not a valid bip39 mnemonic');
      return;
    }

    data?.encryptedMnemonicHex;

In this case, we want the compiler to infer data is definitely defined, as we're checked error.


It does not work on non-English versions of steam

How to fix:

Click "Steam" on the top left of steam
Click "Settings"
In appeared window click "Interface"
In language selection menu select "English"
Reload steam
???
RROFIT

yeah, the way can fix most running problem
but can't close the print Windows
I tried renamed the "print" into other language,but it doesn't work. :(

but prog still works :)
it performs its main function. not so fast, but...
You can change name of this window in prog. at me it worked

maybe chinese is too difficult :)

Hello,
A little trick for users from other countries, if you want the script SteamBulkKeyActivator.ahk working
with another language change some words at several lines.
Ex: English(Original file) to French:
steam_activate_window(){ ;activate the steam activation window
WinWait, Product Activation, ;wait for the activation window to pop up
IfWinNotActive, Product Activation, , WinActivate, Product Activation, ;if not active make active
WinWaitActive, Product Activation, ;wait until active
steam_activate_window(){					;activate the steam activation window
WinWait, Activation de produit, ;wait for the activation window to pop up
IfWinNotActive, Activation de produit, , WinActivate, Activation de produit, ;if not active make active
WinWaitActive, Activation de produit, ;wait until active

is_print_window(){							;way to check if we have a new product or a duplicate
applog("waiting 5 seconds for the print window to pop up")
WinWait, Print,,5 ;wait 5 seconds.
...
IfWinNotActive, Print, WinActivate, Print,
WinWaitActive, Print,
WinKill,Print,
is_print_window(){							;way to check if we have a new product or a duplicate
applog("waiting 5 seconds for the print window to pop up")
WinWait, Imprimer,,5 ;wait 5 seconds.
...
IfWinNotActive, Imprimer, WinActivate, Imprimer,
WinWaitActive, Imprimer,
WinKill,Imprimer,
You must write the same words as displayed in the windows title of the Steam key windows and the print windows


gs1.1 peer exchange

Implements https://github.com/libp2p/specs/blob/master/pubsub/gossipsub/gossipsub-v1.1.md#prune-backoff-and-peer-exchange
Follows go-libp2p-pubsub implementation closely
Depends on https://github.com/libp2p/js-libp2p/pull/683
As noted in a comment there, we now require the libp2p repo as a full-fledged dependency, due to needing to openAndCertify the raw envelope.

Codecov Report

Merging #100 into gsv1.1 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           gsv1.1     #100   +/-   ##
=======================================
  Coverage   91.66%   91.66%
=======================================
  Files           2        2
  Lines          24       24
=======================================
  Hits           22       22
  Misses          2        2

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 b040dc8...3d2b194. Read the comment docs.

@vasco-santos  This is ready for re-review. Codecov is giving an :x: but we'll tackle the tests in another PR (in progress :smiley:)


Tracking issues of OpenDAL v0.50.1 Release

This issue is used to track tasks of the opendal v0.50.1 release.

Discussion: https://github.com/apache/opendal/discussions/5202

Tasks
Blockers

https://github.com/apache/opendal/pull/5204

Build Release
Release List

Name
Version
Next

core
0.50.0
0.50.1

integrations/cloud_filter
0.0.1
0.0.2

integrations/compat
-
1.0.0

integrations/dav-server
0.2.0
0.2.1

integrations/fuse3
0.0.7
0.0.8

integrations/object_store
0.48.0
0.48.1

integrations/parquet
0.2.0
0.2.1

integrations/spring
-
-

integrations/unftp-sbe
0.0.7
0.0.8

integrations/virtiofs
-
-

bin/oay
0.41.11
0.41.12

bin/ofs
0.0.12
0.0.13

bin/oli
0.41.11
0.41.12

bindings/c
0.44.13
0.45.0

bindings/cpp
0.45.11
0.45.12

bindings/dotnet
0.1.9
0.1.10

bindings/go
0.1.3
0.1.4

bindings/haskell
0.44.11
0.44.12

bindings/java
0.47.3
0.47.4

bindings/lua
0.1.9
0.1.10

bindings/nodejs
0.47.5
0.47.6

bindings/ocaml
-
-

bindings/php
0.1.9
0.1.10

bindings/python
0.45.10
0.45.11

bindings/ruby
0.1.9
0.1.10

bindings/swift
-
-

bindings/zig
-
-

GitHub Side

[ ] Bump version in project

[ ] rust
[ ] cpp
[ ] haskell
[ ] java
[ ] nodejs

[ ] Update docs
[ ] Generate dependencies list
[ ] Push release candidate tag to GitHub

ASF Side

[ ] Create an ASF Release
[ ] Upload artifacts to the SVN dist repo
[ ] Close the Nexus staging repo

Voting

[ ] Start VOTE at opendal community

Official Release

[ ] Push the release git tag
[ ] Publish artifacts to SVN RELEASE branch
[ ] Release Maven artifacts
[ ] Send the announcement

For details of each step, please refer to: https://opendal.apache.org/community/release/

Created: https://github.com/apache/opendal/pull/5209


fix: zh_hans & zh_hant matching

Fixes: 7937d4d10585 ("feat: support other languages (#4)")

ah, good catch


refactor: get the vendor style name in the style directive

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[x] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Do not have to get the div style every time

I think the names were better before. I'm not sure if directly caching the style object has any impact (ie: does the browser replace the reference of the element at some time?)
I thought Opera had webkit prefixes

@posva Thanks for your advice.
I removed Opera from vendorNames
good night. 🌝

@gebilaoxiong haha, I wasn't even sure about that!
I checked and it looks like the o prefix was necessary in older versions of opera

@posva
e.... what should I do now .... 😭

@posva  @yyx990803
thanks


Missing import statement in the Custom Power BI Visual tutorial

At Step 9 there is a new method added to populate formatting options:
public enumerateObjectInstances(options: EnumerateVisualObjectInstancesOptions): VisualObjectInstanceEnumeration {
    const settings: VisualSettings = this.visualSettings || <VisualSettings>VisualSettings.getDefault();
    return VisualSettings.enumerateObjectInstances(settings, options);
}

In order to make this step work, you need to add previously this import:
import VisualObjectInstanceEnumeration = powerbi.VisualObjectInstanceEnumeration;
And in fact I believe the below import needs to be added: this is added by default by pbviz, but at the previous tutorial page some people can have the impression that it is not needed and can remove (as I did for the first time) - so to be on the safe side I'd add here a comment to make sure this import is also there:
import EnumerateVisualObjectInstancesOptions = powerbi.EnumerateVisualObjectInstancesOptions;

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

ID: 4bc4f82a-1cec-444c-8561-c02aa38caa96
Version Independent ID: c05253d9-f12e-b2ee-763f-96e4a76fec54
Content: Adding formatting options to a Power BI custom visual - Power BI
Content Source: powerbi-docs/developer/visuals/custom-visual-develop-tutorial-format-options.md
Service: powerbi
Sub-service: powerbi-custom-visuals
GitHub Login: @KesemSharabi
Microsoft Alias: kesharab

Thanks @peterbud for your comment on the tutorial. I have passed your observation on to the author for review.
@KesemSharabi

Thanks for your observation @peterbud. I added the two imports to step 8 in the Adding custom formatting options section, in the Tutorial: Adding formatting options to a Power BI visual.


⚠ Bofrost.at has degraded performance

In f4b3e32, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1331 ms

Resolved: Bofrost.at performance has improved in 1e88b09.


Dismissing autoclosing notifications

Is there a particular reason why autoclosing notifications lack a dismiss button?
Is there a reason why a tiny button is used to close a notification?
I believe that all notifications should be dismissable. And they should be dismissed by clicking anywhere on the notification slate. A close button could display on hover over the slate.
If you agree, i can send a PR.

I'm not sure clicking on them anywhere to dismiss them is a good idea from a UX perspective, especially if you need to hover over them to view the x
I like the fact that there is an x for discoverability i.e. the user knows that they can be closed. Maybe we should design a larger touch surface though in the case that someone is viewing these on a mobile device. how about a section at the end of the "slate" became a close?
I agree that you should be able to dismiss the auto-closing notifications.

I have also seen users try and click the wrong x on error messages.

Not sure about the legitimacy of clicking anywhere on the message to dismiss. In some instances, these notifications could be interactive (link, button) or include information that may needed to be copied the in the case of a fatal error.
I'm happy to accept a PR that enables the currently implemented dismiss for ALL notifications, regardless of auto clear or not.

@griffind That's a good point. We should probably look for an alternative to represent an error message. Again, happy to accept a PR.


Enable logger on off

This PR enables to turn off the json logger by passing an omnetpp parameter (The default value is true)

This change is

you can use debugger to investigate the error.

build with debug symbol  make -C quisp MODE=debug run-unit-test
set the launch.json for code-lldb

{

    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "Launch",
            "program": "${workspaceFolder}/quisp/run_unit_test",
            "args": [],
            "cwd": "${workspaceFolder}/quisp"
        },
    ],
}

start debugger

@res6idue I fixed the segmentation faults. Could you check it?


Terminal doesn't appear to support interactivity.

My app makes extensive use of the Inquire crate. The initial output does come through, but none of the arrow keys etc. result in any response. Not really sure what the difficulty of adding support for this is like. Would be nice to have. I believe inquire uses crossterm under the hood.

Anyone know if this is possible? Output of inquire Select looks like this:
�[?25l�[?25l�[?25l�[38;5;10m?�[39m Select
�[38;5;14m>�[39m This
  That
�[38;5;14m[�[39m�[38;5;14m↑↓ to move, enter to select, type to filter�[39m�[38;5;14m]�[39m
�[4A�[10G�[?25h

@MichalGniadek Thanks for the reply. For me at least, this feature would make this crate incredibly powerful to me. Let me know if you ever happen to get around to it!


Сustom php binary path

On some virtual hosting platforms for correct deploy we need to specify php binary.
For instance:
/opt/php54/bin/php composer.phar install

I suggest to create new environment var, for example "php_bin" with default value "php"

Why not using alias php='/opt/php54/bin/php'?

Just "php" is busy with old version of php.
I've tried to create .bashrc with alias, but It's not working for me.

.bashrc is only taken into account for interactive shells.  You may check for .profile instead.

Then try env('php', '/path/php') and then use: run('{{ php }} ...').

@lbausch thanks! It's work!
@elfet I resolved my issue by overriding tasks deploy:vendors, deploy:assetic:dump, etc.
In generally yes, users can create alias and put in .profile, but True-way is put this variable in configuration

.bashrc does not work, .profile does not work, env('php', .. ) does not work. Exactly as @dmkuznetsov said, we need an environment variable to specify PHP version. Or a way to set the PATH variable and use it in all subsequent calls (better!)

Will be in Deployer v4. #586

There is {{bin/php}} env variable now.


Add Better Stack to monitoring services

Add Better Stack for uptime monitoring and logging for Docker containers and the apps that run inside them.

Hey @ayoisaiah,
can you please point us to the reference where docker is mentioned on the website? I could neither find a mention on the index  nor on the pricing page.

@mashb1t sorry!!!🙇♂🙇♂
I am on my phone and just saw it was in the paying services.
I think you are totally right
We should point to the docker part. I'll fix this asap.

Ping @ayoisaiah


support boringssl support

especially for the client side this is needed to emulate TLS using boringssl directly (for chromium profiles)

Hey Glen, I want to take a stab at this one, but I'm not really sure where to begin. I noticed we do have rustls client so I figured it may be similar to that but other than that, I'm not sure how to proceed.

I agree with you  and I appreciate the details you provided.


Fix Grpc.Core.Api assembly version

Fix assembly version, as mentioned https://github.com/grpc/grpc/pull/18485
No changes to Grpc.Refleciton

Another sanity test failure: Version.csproj.include is also generated from a template.
https://github.com/grpc/grpc/blob/master/templates/src/csharp/Grpc.Core/Version.csproj.include.template

@jtattermusch Could you push this one through to completion? There are a lot of moving parts in the build I'm not familiar with

@JamesNK  I'll do that (and I'll also try to simplify stuff while doing that)

Known failures: https://github.com/grpc/grpc/issues/18477


Mongo db integration

Implemented All APIs of Products
Introducing Java Docs

Let's maintain code hygiene, good and brief java doc (not just generate), good variable names and indentation through the project.
All the reusing constants should be kept at single file.


Python 3.13 support

It seems there's a simple explanation of the failing python 3.13 compilation. PyEval_CallObject which is used in med is removed in python 3.13
error: 'PyEval_CallObject' was not declared in this scope; did you mean 'PyObject_CallObject'?

(failing ci job https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1046350&view=logs&j=3a25022a-f08c-5c04-be7d-d279a7fc48ef&t=d05e68a4-849f-59a6-7be7-12aeebbc2dd2&l=2851)
Found reference in https://bugzilla.redhat.com/show_bug.cgi?id=2245814 which hints to a few simple solutions such as
According to https://docs.python.org/3.13/whatsnew/3.13.html:
Remove PyEval_CallObject(), PyEval_CallObjectWithKeywords(): use PyObject_CallNoArgs() or PyObject_Call() instead.
Warning: PyObject_Call() positional arguments must be a tuple and must not be NULL,
keyword arguments must be a dict or NULL, whereas removed functions checked arguments type and accepted NULL positional and keyword arguments.
To replace PyEval_CallObjectWithKeywords(func, NULL, kwargs) with PyObject_Call(),
pass an empty tuple as positional arguments using PyTuple_New(0).

So the fix seems simple enough. Just create a patch where we add ifdef macros for python >= 3.13 where we replace instances of  PyEval_CallObject  (and similar) with the equivalent ones.

closed with https://github.com/conda-forge/libmed-feedstock/pull/72


Is there a way to get VSCode to automatically use the closest Pipfile/pipenv?

E.g.
--/
--foo-package
--Pipfile (Pipfile-A)
--Pipfile.lock
--script.py (when this file is open, use Pipfile-A for module resolution)
--bar-package
--Pipfile (Pipfile-B)
--Pipfile.lock
--script.py (when this file is open, use Pipfile-B for module resolution)
Although the virtual environment can meet this requirement to some extent, we still hope to be able to coexist and be independent of each other like the above catalog (this makes the project clearer.)  Is this achievable?
Hopefully VS Code will consider supporting multiple Pipfiles at some point.
Thank you very much.

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

Thanks a lot!

This calls for multi-root workspaces. As of now we have a known issue that would probably impact what you're asking for, so I'm closing this issue in favour of https://github.com/microsoft/vscode-python/issues/5066.


Dart VM error when creating a FlutterEngine (Add-to-App)

Steps to Reproduce

Set up Android embedding project following Add Flutter to existing apps wiki
Instantiate a new FlutterEngine from the new embedding API
Launch an Activity that creates the engine and FlutterView

Logs
I have seen this error in previous versions of Flutter, but fixed it by generating the flutter_assets directory. After running flutter upgrade, it came back but seems to be coming from something else this time around.

Crash happens at line 38:

[✓] Flutter (Channel master, v1.8.5-pre.117, on Mac OS X 10.14.5 18F132, locale en-US)
    • Flutter version 1.8.5-pre.117 at /Users/.../Desktop/lcedev/flutter
    • Framework revision 83a8a575ee (2 days ago), 2019-08-10 12:38:20 -0700
    • Engine revision ff49ca1c6e
    • Dart version 2.5.0 (build 2.5.0-dev.1.0 f29f41f1a5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/.../Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.3, Build version 10G8
    • CocoaPods version 1.7.2

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 37.0.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.36.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.3.0

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 9 (API 28) (emulator)

• No issues found!

Re-building the flutter module made the error go away. The aar or other outputs could have been missing for all that I know. Could this still be a bug in the framework?

Made a new issue with a little more understanding of what's going on (#38319).


This repo is not maintained anymore!!!

Please use this one instead: https://github.com/goktugyil/EZSwiftExtensions

Another alternative is this https://github.com/ankurp/Cent


Adding a safety check inside tenant model save and delete for compatibilty

Hello!
This PR concerns two changes, that are minor and do not have direct impact on the project. I'll try to explain them both in detail.
The entire test suite is passing.
Safety check inside save/delete methods
Inside the TenantMixIn model, I've added a few safety checks. These safety checks prevent the direct usage of connection.schema_name, unless if it really exists.
The rationale behind this are two:

We have a project that needs to support both ways. With and without tenants. Everything is fine on our side, except that when we are working on a tenantless mode, the save method and delete method try to do direct usage of connection.schema_name and everything blows up on our face :smile:

We currently test a few of our applications with two different settings. PostgreSQL with tenants (which takes a long time, it's a big suite) and SQLite (without tenants, which is way faster). The same problem occurs.

We already have overriden the save and delete methods on our tenant and we don't have this problem in production or our project at all, but I thought it would be a "nice to have" if other people find the same requirements.
Changing the dts_test_project_settings

While trying to run the tests, we have encountered that it was not possible to customize a few of the settings we have. So instead of changing my own password so we could run these, I've added the option to customize the command with environment variables, the same way as the database can be customized.

Thanks looks good to me

Great. Thanks!


HttpTrigger Throttling Config

Add a host level configuration setting (and perhaps function level as well) that allows the user to set the maximum number of concurrent http requests that the host should handle at any given time.

the host level setting would apply to ALL functions (i.e. not function specific like our existing knobs like queue BatchSize)
when this threshold is exceeded, the host will return 429 "Too Many Requests" status along with a "Retry-After"
In addition to an integer max requests limit, we should also allow the "Retry-After" value to be configured. We'll have an intelligent default

Such a setting will allow clients like Logic Apps to gracefully handle busy host situations. In the Logic Apps case, it handles the 429 and will retry after some time.

Before we do this http specific feature, I want to give this more thought and try to generalize it in some way so that it can apply to other trigger types.

We need to look into applying different values to different VM (instance) sizes. Per Mathew comment, throttling is applicable for 'stream' type triggers like HTTP, where messaging types, like queue, IMHO,  don't really require specific throttling

The other "automatic" triggers like queues etc. have their own trigger specific throttle knobs (e.g. BatchSize). HttpTrigger doesn't currently so it is somewhat special.


admin: improve logs handler test coverage

Signed-off-by: Tianpeng Wang<EMAIL_ADDRESS>
Commit Message: admin: improve logs handler test coverage
Additional Description: This is a follow-up of #19868, in this PR which should increase coverage to  100%
Risk Level: Low
Testing: unit test
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A

/retest

/retest


Added Firefox Reality

Added on Daydream, Oculus Go and Vive port for Firefox Reality on browser's list

Added Firefox Reality on developer section

@cvan thanks for the suggestions!

thanks!


Line 100 - Doesn't work when "space" is included.

I'm having issues with trying to add a space between words for Line 100.

I do not have coding background so this is very complex to me.
Please help me out.
I've tried using &nbsp but it turned out like this

Having a "space" in between words will cause Line 100 to not work.
Line 100 will work fine without "space"
Example: CapitaLink Solutions will cause Line 100 to not work

CapitaLinkSolutions will work fine

I'm trying to have it look like "CapitaLink Solutions" in recipients' email inbox.

Please post the whole snippet.

Please post the whole snippet.

are these what you were looking for?

Try this simple script. Replace <some email>.
function main() {
  GmailApp.sendEmail('<some email>', 'Test', null, {
    htmlBody: '
HTML Body
',
    name: 'Testing Name with Space'
  });
}

@vinay-google, I replace which line with this code?


_cat/health in REST (cerebro)

I'am trying to run '_cat/health' (GET) via REST (cerebro 6.5) without success. I get the following error message

{
"error": {
"root_cause": [
{
"type": "index_not_found_exception",
"reason": "no such index",
"resource.type": "index_expression",
"resource.id": "",
"index_uuid": "na",
"index": ""
}
],
"type": "index_not_found_exception",
"reason": "no such index",
"resource.type": "index_expression",
"resource.id": "",
"index_uuid": "na",
"index": ""
},
"status": 404
}

In console everything is ok:

curl -XGET 'http://localhost:9200/_cat/health'
1480896067 01:01:07 elasticsearch yellow 1 1 5 5 0 0 5 0 - 50.0%

In the elasticsearch log files, I have the following error message

[2017-07-24T11:59:26,763][WARN ][o.e.d.r.RestController   ] Content type detection for rest requests is deprecated. Specify the content type using the [Content-Type] header.

The reason is explained in this blog post: https://www.elastic.co/blog/strict-content-type-checking-for-elasticsearch-rest-requests
Basically, starting with ES 5.3, ES will start requiring that the client send the Content-Type header along with all their requests. Until ES 6, it will be optional but as of ES 6, this will be mandatory and not modifiable.
So the data service should always add Content-Type: application/jsonto the requests sent to ES, or the REST tab should provide a way to either specify the content type or select from application/json or application/x-yaml

Hello,
I understood that it came from the Content-type, but the problem is that even if I specify in cerebro the Content-type (/_cat/health?format=json) this does not work.
It may be necessary to make modifications in cerebro?
Thank you for your answer.

@soume86 it is not something that you are doing wrong, but something that needs to be changed inside the Cerebro codebase. Sorry if that wasn't clear.

Would you know if the change is planned or not?
Thank again,

ping @lmenezes

hey. I will prepare a fix for this soon and create a new release.

Any news on the next release @lmenezes ?

This still doesn't seem to work on the latest 0.6.7 version.


Test version based on CircuitPython 4.1.2

Hej @Rodot and @Sorunome,
I created a test version based on CircuitPython 4.1.2 based on your work. You can find it here: https://github.com/BjoernSchilberg/circuitpython/releases/tag/Gamebuino
See commit: https://github.com/BjoernSchilberg/circuitpython/commit/5bb1e3cc553a52ff2a3ea9895a2e6aba435f039e
Snake from @iw4rr10r works for me:
https://gist.github.com/iw4rr10r/690f22fe8506ab7a2739dd6b40377b94
Also Pong from https://gamebuino.com/academy/workshop/discover-python-programming/program-a-pong
It would be great if you could test it. I am happy about every feedback. And feel free to fork it and maybe bring out your own new Gamebunio-Circuitpython release.
CircuitPython 4.1.X promises:
4.1.0’s biggest feature is speed! General execution of Python should be 2-5x faster and display refreshing will be faster as well.

It shouldn’t break any code compatible with previous 4.x releases.

https://blog.adafruit.com/2019/08/03/circuitpython-4-1-0-released/

That's awesome! Do you want to PR the changes?

I'd be happy to. Just give me 1 or 2 days. Busy week. I'll probably have to fiddle around a bit.

No problem, take your time, and thank you!

Ok here we go see #7 .


[Question] Is the event definition used when creating the mongo record?

Hello,
I have an event definition that looks like:
let eventDefinition = {
    correlationId: 'commandId',
    id: 'id',
    name: 'name',
    aggregateId: 'aggregate.id',
    aggregate: 'aggregate.name',
    payload: 'payload',
    revision: 'head.revision',
    meta: 'meta'
};

This event definition is then used when defining my domain:
function NoiseDomain(options) {
    this.logger = options.logger;
    this.domain = cqrsDomain({
        domainPath: __dirname + '/domain',
        eventStore: options.eventStoreConfig,
        aggregateLock: options.aggregateLockConfig,
        deduplicationConfig: options.deduplicationConfig
    });
    this.domain.defineCommand(commandDefinition);
    this.domain.defineEvent(eventDefinition);
    this.domain.extendValidator((validator)=> {
        validator.addFormat(require('tv4-formats'))
    });
}

I can clearly see it is using my event definition when in debugging mode:

But when my event is apply and persisted on my mongodb i can see the event as:

Does the mongo record should also comply to the event definition? Or the mongo has its own structure and a mapping is done before applying and raising it again?
I'm asking this because I'm currently trying to reload the events on my readmodel. for this I plug my readmodel straight to the event store (And the "propritary" format of the event on the event store.
When I try to reload the event coming straigh from the event store, well, they are not formatted as described by the event defintion...

Forget about it. I can answer my own question. The event itself is on the payload of the eventstore monog record :). My mistake.


Font color in ALSA widget

Hi me again, is there a way to set a font color in the ALSA widget? i have already tried foreground but to no effect, the font is always white.
Thanks again.

It's hardcoded at the moment. Easy enough to make it configurable.

Great thanks man


WIP: New Tenant v1alpha2 version

@prometherion this is the first commit for #286. Adds new v1alpha2 Tenant spec

I was thinking about it, but then I checked https://github.com/Azure/azure-service-operator as an example, and they are copying structs between versions, not using abstract ones. And I think this approach had an advantage, because we will be able to modify them in future without breaking v1alpha1 CRDs.