New trace capturing with decycling

Just wanted to report that there currently seems to be a bug that causes the following... errm, stack trace :D
/bluebird/js/main/captured_trace.js:27
        var stack = nodes[i].stack;
                            ^
TypeError: Cannot read property 'stack' of undefined
    at CapturedTrace.uncycle (/bluebird/js/main/captured_trace.js:27:29)
    at CapturedTrace.attachExtraTrace (/js/main/captured_trace.js:73:10)
    at Promise._attachExtraTrace (/bluebird/js/main/promise.js:679:21)
    at Promise._settlePromiseFromHandler (/bluebird/js/main/promise.js:598:40)
    at Promise._settlePromiseAt (/bluebird/js/main/promise.js:733:18)
    at Promise._settlePromises (/bluebird/js/main/promise.js:850:14)
    at Async._drainQueue (/bluebird/js/main/async.js:78:16)
    at Async._drainQueues (/bluebird/js/main/async.js:88:10)
    at Async.drainQueues (/bluebird/js/main/async.js:13:14)
    at process._tickCallback (node.js:442:13)

edit: this might be caused by interaction with BB 1.0, checking nope its not 1.0

Can you create a reproducing case?
On Fri, Jan 16, 2015 at 8:21 AM, Gorgi Kosev<EMAIL_ADDRESS>wrote:

Just wanted to report that there currently seems to be a bug that causes
the following... errm, stack trace :D
/bluebird/js/main/captured_trace.js:27
var stack = nodes[i].stack;
^
TypeError: Cannot read property 'stack' of undefined
at CapturedTrace.uncycle (/bluebird/js/main/captured_trace.js:27:29)
at CapturedTrace.attachExtraTrace (/js/main/captured_trace.js:73:10)
at Promise._attachExtraTrace (/bluebird/js/main/promise.js:679:21)
at Promise._settlePromiseFromHandler (/bluebird/js/main/promise.js:598:40)
at Promise._settlePromiseAt (/bluebird/js/main/promise.js:733:18)
at Promise._settlePromises (/bluebird/js/main/promise.js:850:14)
at Async._drainQueue (/bluebird/js/main/async.js:78:16)
at Async._drainQueues (/bluebird/js/main/async.js:88:10)
at Async.drainQueues (/bluebird/js/main/async.js:13:14)
at process._tickCallback (node.js:442:13)
—
Reply to this email directly or view it on GitHub
https://github.com/petkaantonov/bluebird/issues/448.

@benjamingr not yet, will try.

I can't make a reproducing case, but this is the result of printing nodes in the few calls of uncycle before the crash with the stacktrace I pasted above
[ { [Error]
_parent: { [Error] _parent: [Object], _length: 11 },
_length: 12 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 10 },
_length: 11 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 9 },
_length: 10 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 8 },
_length: 9 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 7 },
_length: 8 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 6 },
_length: 7 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 5 },
_length: 6 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 4 },
_length: 5 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 3 },
_length: 4 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 2 },
_length: 3 },
{ [Error]
_parent: { [Error] _parent: undefined, _length: 1 },
_length: 2 },
{ [Error] _parent: undefined, _length: 1 } ]
[ { [Error]
_parent: { [Error] _parent: [Object], _length: 5 },
_length: 6 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 4 },
_length: 5 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 3 },
_length: 4 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 2 },
_length: 3 },
{ [Error]
_parent: { [Error] _parent: undefined, _length: 1 },
_length: 2 },
{ [Error] _parent: undefined, _length: 1 } ]
[ { [Error]
_parent: { [Error] _parent: [Object], _length: 8 },
_length: 12 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 7 },
_length: 8 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 6 },
_length: 7 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 5 },
_length: 6 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 4 },
_length: 5 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 3 },
_length: 4 },
{ [Error]
_parent: { [Error] _parent: [Object], _length: 2 },
_length: 3 },
{ [Error]
_parent: { [Error] _parent: undefined, _length: 1 },
_length: 2 },
{ [Error] _parent: undefined, _length: 1 },
,
,
]
Seems like some of the nodes in the list are removed without updating the length counts

I fixed it in #449 but I wasn't able to make a test case :(


Provide autofix in vscode?

Currently there is no autofix in vscode:

I have found this problem but can't reproduce it yet.

I've been unable to reproduce the problem in 0.0.12, I'm guessing it's been resolved. But please let me know if you still face this problem.


Bug: fetchGuestToken function is not called after internet is disconnected and error is encountered during embedded report access

Bug description
When a user's internet connection is interrupted while accessing an embedded dashboard user encountered the network errors but after that the fetchGuestToken function fails to execute for guest token refresh when the internet connection is restored. As a result, the guest token is not refreshed, and the user continues to receive errors related to guest token not valid when attempting to access the embedded report. This issue persists until the user manually refreshes the page. (which evenually rerender the iframe)
How to reproduce the bug

Embed a report in the dashboard that utilizes the fetchGuestToken function for authentication and guest token refresh.
Disconnect the internet connection.
Attempt to access the embedded report while the internet is disconnected.
Observe that a network error is thrown.
Reconnect the internet connection.
Attempt to access the embedded report again without refreshing the page.

Screenshots/recordings

Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

@dosu is there any alternate way without change in SDK package ?


selecting a button in one month and then changing the month to a month where that same button becomes a special date without an explicit border automatically gives it the selected border style

In code, make Jan 1 2017 a special date
In the app, navigate to December
Tap/select Nov 27
Navigate to January
Jan 1 will be highlighted as a special date and as though it were selected

I'm going to come back and take a look at this soon.

Thanks, it could be a race condition. I will release a new version (1.0.6) at the end of this week would you check this again with that version.
I could not reproduce this, but I already changed some code, so I do not know if this problem was solve by that.

It seems to only happen when the SpecialDate doesn't specify an explicit border color. In the example app this would be the SpecialDate set 3 days after today. I'm guessing when the month is changed the button just keeps the border color the same as it was when it was in the previous month because the incoming SpecialDate doesn't specify anything to set it to. It looks like the analogous problem happens for SelectedFontSize.
At first blush I might suggest setting all buttons to normal when the month changes before going back and layering special & selected stylings on top. That might mean setting a few colors and things twice (maybe inefficient) but it would make it easier to maintain the "default" styling.

Looking closer, the suggestion I made might work, but it looks like you already have some code for handling selected buttons that does the sort of handling of default styles we would need for SpecialDates:
				button.BackgroundColor = SelectedBackgroundColor.HasValue ? SelectedBackgroundColor.Value : (special != null && special.BackgroundColor.HasValue ? special.BackgroundColor.Value : defaultBackgroundColor);
				button.TextColor = SelectedTextColor.HasValue ? SelectedTextColor.Value : (special != null && special.TextColor.HasValue ? special.TextColor.Value : defaultTextColor);

I guess one of the approaches would need to be chosen but I'm not sure of the full consequences of the each yet.

I hoop this is resolved in 1.0.8, if not please reopen this issue.


Text state carries between separate calls to ansi_to_html after upgrading to v6.0.0

Hey there!
We use this library for rendering deploy logs at Netlify. When upgrading to 6.0.0, I've noticed that if one call to ansi_to_html detects an ansi value that should bold the text, that bold state carries over to subsequent calls to ansi_to_html.
I've created a CodeSandbox comparing 5.2.1 and 6.0.0 behavior. The first bold ansi value appears around the Netlify Build line. In 6.0.0, it bolds all subsequent lines while this doesn't happen in v5.
A workaround is to create a new instance of AnsiUp for every call.

I had been observing the same statefulness in v5.2.1 as well, thought it to be working as intended. For example a unclosed color opening sequence carried over to subsequent ansi_to_html calls.

@cmparsons - hi. thanks, I found the issue.
Getting a fix together now.


Reference another assertion from c2pa.assertion.metadata

Per 2.0 of the spec we can have c2pa.assertion.metadata assertions that provide metadata about other assertions.
The content model for this calls for a reference property with a hashed-uri-map that needs the JUMBF URL of the other assertion as well as the hash of the assertion.
Can this be supported? I saw from issue 133 that I could add an instanceId to my manifest JSON to get the ingredient assertion hash. Is there a similar way to refer to other assertions?
BTW: I noticed that each time I generate a manifest the hash for the metadata assertions changes even if the assertion JSON hasn't changed. Is that because the c2patool is generating a new salt for the assertion JUMBF box? If so, is there a way to specify what the salt should be when generating a manifest so the hash will be the same each time?

We have not yet implemented 2.0 spec changes. We need to add a way to map a reference to an assertion. I'm not exactly sure how to do that yet, but we will come up with something.
You are right about the salt changing the hash. That is by design to prevent redacted assertions being identified by the hash in the claim. Allowing you to set the salt would remove that safety. Why do you want that?

Thanks @gpeacock !
To create an assertion hash, I initially tried generating a manifest so I could get all the hashes from the claim and then use those values to create the c2pa.assertion.metadata with the right JUMBF URL and assertion hash. But then I noticed the hashes changed.
I thought if I could use the same salt each time I generated the manifest, then the hashes would be stable and I'd be able to populate the c2pa.assertion.metadata with all the right values.


请问，如何提高async_handshake时间

请问，如何提高https证书校验的时间

Google translates this as: "Excuse me, how to increase the time of https certificate verification"
At the moment, the question is ambiguous.
Does it mean:

How do I increase the validity period of an SSL certficate? In this case, the answer is that you cannot. You will need to issue a new certificate.

How do I increase the timeout while a client is verifying the certificate? This is difficult to answer here as if depends on the verification mechanism you are using.


Does current Symbiflow support generating SDF file for post place-and-route timing simulation?

I can't find SDF file in the build folder of a counter_16bit design.

I was able to generate the SDF file by using the -dump option; -dump post_verilog


no such file to load -- refinerycms/inquiries (LoadError)

First off, i've seen this resolved at https://github.com/resolve/refinerycms/issues/1113 , but i am facing the same issue today, while trying to "script/rails server" from a freshly generated refinerycms app
Andras-Szerdahelyis-MacBook-Pro:inquiries-test andras$ script/rails server
/Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:74:in require': no such file to load -- refinerycms/inquiries (LoadError) 	from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:74:in rescue in block in require'
from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:62:in block in require' 	from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:55:in each'
from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/bundler-1.1.rc.7/lib/bundler/runtime.rb:55:in require' 	from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/bundler-1.1.rc.7/lib/bundler.rb:118:in require'
from /Users/andras/CCWorkspace/inquiries-test/config/application.rb:13:in <top (required)>' 	from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/railties-3.1.3/lib/rails/commands.rb:52:in require'
from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/railties-3.1.3/lib/rails/commands.rb:52:in block in <top (required)>' 	from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/railties-3.1.3/lib/rails/commands.rb:49:in tap'
from /Users/andras/.rvm/gems/ruby-1.9.2-p180@egc/gems/railties-3.1.3/lib/rails/commands.rb:49:in <top (required)>' 	from script/rails:6:in require'
from script/rails:6:in `'
Here's how i can reproduce this

created a blank gem set in rvm
clone resolve/refinerycms.git, build and install all gems from there
refinerycms inquiries-test
edit gemfile, add refinerycms and refinerycms-inquiries master : https://gist.github.com/1578679
bundle install
my installed gems at this time : https://gist.github.com/1578679
trying to start up server gets me the error above

( I am -regrettably- not familiar with bundler internals; i've no idea where to go from here, sorry )
thanks!
Andras

ps: added trace to https://gist.github.com/gists/1578679

You need to point to rails-3-1 branch for refinerycms-inquiries gem.

that helped, thanks!


Kubernetes scale up on <IP_ADDRESS>

Hello,
Have a good day team !
I created a Kubernetes cluster with two control nodes and one worker. Then I tried to manually scale up by adding three more workers, but an error message appeared on the dashboard saying "Scaling failed for Kubernetes cluster: K8S-Dev, unable to update network rules." I checked the management log and found details about the error.
2023-05-09 18:13:38,304 DEBUG [c.c.u.d.T.Transaction] (API-Job-Executor-105:ctx-567d2785 job-2167 ctx-c4f4e780) (logid:2277cf45) Rolling back the transaction: Time = 29 Name =  API-Job-Executor-105; called by -TransactionLegacy.rollback:888-TransactionLegacy.removeUpTo:831-TransactionLegacy.close:655-Transaction.execute:38-FirewallManagerImpl.createFirewallRule:242-FirewallManagerImpl.createIngressFirewallRule:194-GeneratedMethodAccessor846.invoke:-1-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:566-AopUtils.invokeJoinpointUsingReflection:344-ReflectiveMethodInvocation.invokeJoinpoint:198-ReflectiveMethodInvocation.proceed:163
2023-05-09 18:13:38,321 ERROR [c.c.k.c.a.KubernetesClusterActionWorker] (API-Job-Executor-105:ctx-567d2785 job-2167 ctx-c4f4e780) (logid:2277cf45) Scaling failed for Kubernetes cluster : K8S-Dev, unable to update network rules
com.cloud.exception.NetworkRuleConflictException: The range specified, 2222-2227, conflicts with rule 216 which has 2222-2224
        at com.cloud.network.firewall.FirewallManagerImpl.detectRulesConflict(FirewallManagerImpl.java:470)
        at com.cloud.network.firewall.FirewallManagerImpl$1.doInTransaction(FirewallManagerImpl.java:255)
        at com.cloud.network.firewall.FirewallManagerImpl$1.doInTransaction(FirewallManagerImpl.java:242)
        at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
        at com.cloud.network.firewall.FirewallManagerImpl.createFirewallRule(FirewallManagerImpl.java:242)
        at com.cloud.network.firewall.FirewallManagerImpl.createIngressFirewallRule(FirewallManagerImpl.java:194)
        at jdk.internal.reflect.GeneratedMethodAccessor846.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
        at org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
        at com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:52)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
        at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:97)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
        at com.sun.proxy.$Proxy276.createIngressFirewallRule(Unknown Source)
        at com.cloud.kubernetes.cluster.actionworkers.KubernetesClusterResourceModifierActionWorker.provisionFirewallRules(KubernetesClusterResourceModifierActionWorker.java:446)
        at com.cloud.kubernetes.cluster.actionworkers.KubernetesClusterScaleWorker.scaleKubernetesClusterNetworkRules(KubernetesClusterScaleWorker.java:148)
        at com.cloud.kubernetes.cluster.actionworkers.KubernetesClusterScaleWorker.scaleUpKubernetesClusterSize(KubernetesClusterScaleWorker.java:369)
        at com.cloud.kubernetes.cluster.actionworkers.KubernetesClusterScaleWorker.scaleKubernetesClusterSize(KubernetesClusterScaleWorker.java:405)
        at com.cloud.kubernetes.cluster.actionworkers.KubernetesClusterScaleWorker.scaleCluster(KubernetesClusterScaleWorker.java:439)
        at com.cloud.kubernetes.cluster.KubernetesClusterManagerImpl.scaleKubernetesCluster(KubernetesClusterManagerImpl.java:1315)
        at org.apache.cloudstack.api.command.user.kubernetes.cluster.ScaleKubernetesClusterCmd.execute(ScaleKubernetesClusterCmd.java:162)
        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:163)
        at com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:106)
        at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
        at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
        at org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
        at org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
        at org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
2023-05-09 18:13:38,333 INFO  [c.c.k.c.a.KubernetesClusterActionWorker] (API-Job-Executor-105:ctx-567d2785 job-2167 ctx-c4f4e780) (logid:2277cf45) Revoking launch permission for systemVM template
2023-05-09 18:13:38,343 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl] (API-Job-Executor-105:ctx-567d2785 job-2167) (logid:2277cf45) Complete async job-2167, jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Scaling failed for Kubernetes cluster : CFOX-Dev, unable to update network rules"}

I see the message "The range specified, 2222-2227, conflicts with rule 216 which has 2222-2224".
Does CloudStack have a function to replace conflicting rules? If not, how can we manually or auto-scale?
My cluster has changed to Alert status, and I cannot do anything now except stop or delete the cluster.
Additionally, how can I put my cluster back to Health status? I have checked, and all pods in the cluster are still working fine.
Thanks !

@tuanhoangth1603 During scaling CloudStack tries to redo the firewall and portforwarding rules depending on the new cluster size. From your logs, it appears that it was not able to delete the old firewall rule and encountered an error while creating a new one. You may need to check how many node VMs the cluster is having right now and does listKubernetesClusters API returns the same size. If it is 6 (new size) then you may delete the firewall rule 2222-2224, add a new firewall rule 2222-2227 and verify if the portforwarding rules are correctly set. Thereafter KubernetesClusterStatusScanner should reconcile the cluster state.

@tuanhoangth1603 also, is this(issue while scaling) happening for all clusters in your env or just with this particular cluster?

Hi @shwstppr,
I tried scaling on a new cluster and didn't encounter a similar error. Perhaps the issue is only on the current cluster. I have created an additional instance that shares a network with this current cluster and added a firewall rule for that instance. Will doing so affect the automatic redo of the firewall rule when k8s scales?
Thanks !

@shwstppr
Here is output of listKubernetesClusters API and screenshots of the instances list, firewall rules, and portwarding rules.
(I have changed some information for security reasons but it does not affect the information that you need.)
CFOX-Dev is the alerting cluster which I want to fix the state.
Thanks for your help !
https://gist.github.com/tuanhoangth1603/dc4c6484e8dc8a83a020871108d0f1ec

@tuanhoangth1603 it seems your last 3 nodes never joined the k8s cluster due to error. In this case, I need to check but the only way to restore would be removing the extra node VMs alongwith the firewall and portforwarding rules. I'll check the code and may give you steps to proceed  tomorrow.

this seems to be because there are 2 cks clusters deployed on same isolated network.

It looks the first (pf port 2224) and last (pf port 2228)worker nodes worked well
the other 3 (pf port 2225/2226/2227) did not .
it would be good to upload some logs in the control nodes and the 3 worker nodes with issues.

scale up and scale down worked fine with CKS 1.26.6 ISO on my <IP_ADDRESS>-snapshot environment

@tuanhoangth1603 , as it seems to work on current environement, I am closing this issue. Please reopen or open a new one if you feel there is still a problem.


Merge main into release/6.0

Merge the following PRs into release/6.0:

https://github.com/apple/sourcekit-lsp/pull/1340
https://github.com/apple/sourcekit-lsp/pull/1344
https://github.com/apple/sourcekit-lsp/pull/1345
https://github.com/apple/sourcekit-lsp/pull/1346
https://github.com/apple/sourcekit-lsp/pull/1335
https://github.com/apple/sourcekit-lsp/pull/1347
https://github.com/apple/sourcekit-lsp/pull/1343
https://github.com/apple/sourcekit-lsp/pull/1352
https://github.com/apple/sourcekit-lsp/pull/1357
https://github.com/apple/sourcekit-lsp/pull/1359
https://github.com/apple/sourcekit-lsp/pull/1356
https://github.com/apple/sourcekit-lsp/pull/1354
https://github.com/apple/sourcekit-lsp/pull/1355
https://github.com/apple/sourcekit-lsp/pull/1350
https://github.com/apple/sourcekit-lsp/pull/1363

@swift-ci Please test


Does immer product not work with class instance object?

🙋♂ Question
Not expected case:

Expected case:

immer version: 6.0.3

https://immerjs.github.io/immer/docs/complex-objects

https://immerjs.github.io/immer/docs/complex-objects
On Thu, Apr 16, 2020 at 10:42 AM tingyuan<EMAIL_ADDRESS>wrote:

🙋♂ Question Not expected case:
[image: image]
https://user-images.githubusercontent.com/7310471/79440879-1d213d00-8009-11ea-9058-440e32f3e952.png
Expected case:
[image: image]
https://user-images.githubusercontent.com/7310471/79441015-493cbe00-8009-11ea-92e3-57f67a44a0a3.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/immerjs/immer/issues/578, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBCNXCXJ2N3DPOF5PVLRM3HGVANCNFSM4MJN4KXA
.

oh, I see, thanks a lot.


Removed signal import on win32

Description
Issue: The current code does not run on Windows due to the absence of the signal module functionalities for setting SIGPIPE.
Solution: Added a conditional import and setting of signal only if the operating system is not Windows.
Changes

Added a check to determine the operating system.
Imported and set signal only for non-Windows systems.

Code

if sys.platform != 'win32':
    from signal import signal, SIGPIPE, SIG_DFL
    signal(SIGPIPE, SIG_DFL)

Testing
Verified that the code runs without errors on Windows.
Ensured that the signal handling works correctly on non-Windows systems.

Please merge


Include Non Exported CardDefs and FieldDefs to LHS (in this file) panel

This PR supports non-exports of card and field definitions. Previously when you clicked on a card defined locally, the inheritance panel will not pop up -- now it should
https://github.com/cardstack/boxel/assets/8165111/b7491a1a-7b76-4156-8175-b97a90524006
Here are a few good files in the drafts-realm to look at:

in-this-file.gts

vendor.gts

payment-method.gts

asset.gts

contact-card.gts

Based on our pairing today, are you blocked on this pending a discussion around how we want to proceed regarding module mutations and loader sandboxing?

Based on our pairing today, are you blocked on this pending a discussion around how we want to proceed regarding module mutations and loader sandboxing?

I would consider our discussion of "sandboxing" outside scope of this pr

Pointed out some minor typos. Looks much better organized after refactoring and renaming. Looks good to me but is it possible to include a test for this?

There is a test already here which should model all schenarios


Extra new line added

Test:
var YAML = require('js-yaml');

data = "test1\ntest2"
console.log(data);
console.log('===============================================================');
data = YAML.safeDump(data);
console.log(data);
console.log('===============================================================');
data = YAML.safeLoad(data);
console.log(data);
console.log('===============================================================');

Output:
$ node test.js
test1
test2
===============================================================
|-
test1
test2

===============================================================
test1
test2

===============================================================

So extra new line added in the end of string.

Dupe?

@puzrin If you ask about #222, then no. It's about trailing new line and not related to 80 symbols.

Probably, that's because of #125 workaround (the same exists in Ruby's parser).

Both this and #222 actually caused by combination of two different bugs: one in the loader, and another in the dumper.
Loader bug:

It doesn't throw an error on block scalar without indentation. Block scalars cannot have 0-level indentation.

Dumper bug:

It doesn't add indentation for top-level block scalar.

Dumper part if fixed by #274.
I've created separate issue for the loader bug: https://github.com/nodeca/js-yaml/issues/280


drivers: timer: Set user RTC channel count conditionally

The RTC user channel count is increased contitionally to 2 when
nrf_802154 radio driver is enabled.
Signed-off-by: Rafał Kuźnia<EMAIL_ADDRESS>

@anangl @carlescufi Could this be merged?


update packages

:white_check_mark: Build TheIdServer 2.1.1-maintain-1-0-01-0045 completed (commit https://github.com/Aguafrommars/TheIdServer/commit/498b196eed by @)


How to pass current card info to controller

i am new to angularJS, and i am wonder if i can get the current selected card info in my controller, here is my scripts:

and in templates/deckgrid-card.html file, i want to pass the current clicked card's info to my controller,

and in my controller, i have the function showBookDetail defined:
	alert(title)
};```

and i can not get the value of card.title, but always the string of 'card.title'.

Thanks.

Sorry, i have figured it out, i need to use:

close it.


Kong 0.13 errors when requesting services and routes simultaneously

Summary
In my angularjs code, I am making simultaneous requests to fetch services and routes. Here is the code snippet:
(function() {
  angular.module('app').config(['$routeProvider', router]);

  function router($routeProvider) {
    $routeProvider.when('/plugins/add', {
        templateUrl: 'html/plugins/form.html',
        controller: 'PluginController',
        resolve: {
          // Fetching routes
          routes: ['Kong', function(Kong) {
            return Kong.get('/routes');
          }],
          // Fetching services
          services: ['Kong', function(Kong) {
            return Kong.get('/services');
          }]
        }
        // .... More code
  });
}

One of the calls (either routes or services) is failing randomly.
Below are the logs:
2018/05/08 05:55:33 [error] 34#0: *75038 lua coroutine: runtime error: /usr/local/share/lua/5.1/pgmoon/init.lua:294: bad request
stack traceback:
coroutine 0:
	[C]: in function 'post'
	/usr/local/share/lua/5.1/pgmoon/init.lua:294: in function 'query'
	.../share/lua/5.1/kong/db/strategies/postgres/connector.lua:180: in function 'execute'
	...local/share/lua/5.1/kong/db/strategies/postgres/init.lua:565: in function 'page'
	/usr/local/share/lua/5.1/kong/db/dao/init.lua:217: in function 'page'
	/usr/local/share/lua/5.1/kong/api/endpoints.lua:51: in function </usr/local/share/lua/5.1/kong/api/endpoints.lua:50>
coroutine 1:
	[C]: in function 'resume'
	/usr/local/share/lua/5.1/lapis/application.lua:393: in function 'handler'
	/usr/local/share/lua/5.1/lapis/application.lua:130: in function 'resolve'
	/usr/local/share/lua/5.1/lapis/application.lua:161: in function </usr/local/share/lua/5.1/lapis/application.lua:159>
	[C]: in function 'xpcall'
	/usr/local/share/lua/5.1/lapis/application.lua:159: in function 'dispatch'
	/usr/local/share/lua/5.1/lapis/nginx.lua:215: in function 'serve_admin_api'
	content_by_lua(nginx-kong.conf:141):2: in function <content_by_lua(nginx-kong.conf:141):1>, client: <IP_ADDRESS>, server: kong_admin, request: "GET /services HTTP/1.1", host: "kong:8001"
2018/05/08 05:55:33 [error] 34#0: *75038 [lua] init.lua:133: handle_error(): /usr/local/share/lua/5.1/lapis/application.lua:397: /usr/local/share/lua/5.1/pgmoon/init.lua:294: bad request
stack traceback:
	[C]: in function 'post'
	/usr/local/share/lua/5.1/pgmoon/init.lua:294: in function 'query'
	.../share/lua/5.1/kong/db/strategies/postgres/connector.lua:180: in function 'execute'
	...local/share/lua/5.1/kong/db/strategies/postgres/init.lua:565: in function 'page'
	/usr/local/share/lua/5.1/kong/db/dao/init.lua:217: in function 'page'
	/usr/local/share/lua/5.1/kong/api/endpoints.lua:51: in function </usr/local/share/lua/5.1/kong/api/endpoints.lua:50>

stack traceback:
	[C]: in function 'error'
	/usr/local/share/lua/5.1/lapis/application.lua:397: in function 'handler'
	/usr/local/share/lua/5.1/lapis/application.lua:130: in function 'resolve'
	/usr/local/share/lua/5.1/lapis/application.lua:161: in function </usr/local/share/lua/5.1/lapis/application.lua:159>
	[C]: in function 'xpcall'
	/usr/local/share/lua/5.1/lapis/application.lua:159: in function 'dispatch'
	/usr/local/share/lua/5.1/lapis/nginx.lua:215: in function 'serve_admin_api'
	content_by_lua(nginx-kong.conf:141):2: in function <content_by_lua(nginx-kong.conf:141):1>, client: <IP_ADDRESS>, server: kong_admin, request: "GET /services HTTP/1.1", host: "kong:8001"

Please let me know if you need any more information. I am using docker compose to setup the kong and postgres.

Hi,
Thanks for the report. This should be resolved by https://github.com/Kong/kong/pull/3423, which will be included in our next release (likely 0.13.2) very soon. In the meantime, you could apply this patch yourself, or temporarily execute those requests sequentially, if the added latency is acceptable for you.

@thibaultcha
Would be happy to know the approximate time when 0.13.2 is released ? Could you provide the updates
Thanks in advance

@kapralVV As you can see from the CHANGELOG, 0.13.2 was skipped in favor of 0.14.0. You will notice in the Core fixes for this version that this fix is included:

Ensure the PostgreSQL connector of the new DAO (used by Services, Routes, Consumers, and SSL certs/SNIs) is now fully re-entrant and properly behaves in busy workloads (e.g. scripting requests to the Admin API). #3423


SW-5749 package updates

Fixes failing dependabot pr updates
https://github.com/ministryofjustice/opg-sirius-supervision-workflow/pull/168
https://github.com/ministryofjustice/opg-sirius-supervision-workflow/pull/170
https://github.com/ministryofjustice/opg-sirius-supervision-workflow/pull/182
https://github.com/ministryofjustice/opg-sirius-supervision-workflow/pull/184
Also upgrades pact-ruby-standalone (v1.88.6 => 1.89.02-rc1)

Codecov Report

Merging #186 (a695811) into main (5696cf9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #186   +/-   ##
=======================================
  Coverage   49.51%   49.51%
=======================================
  Files          14       14
  Lines         519      519
=======================================
  Hits          257      257
  Misses        211      211
  Partials       51       51

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 5696cf9...a695811. Read the comment docs.


Query string breaks deep linking hash.

When adding a query string i.e. for tracking an exception is thrown in foundation.js:
Line 64: Uncaught SyntaxError: Failed to execute 'querySelectorAll' on 'Document': '#community?utm_source=email&utm_medium=events&utm_campaign=email' is not a valid selector.

Whilst I'm working on a fix I wondered if there was an existing workaround that I may of missed?

Same issue here... if you found a solution to that issue please share it :)

Hey (and sorry for my poor english),
I had some time to look at this issue a bit more.
It works fine if the order is url?query#hash.
it fails if the order is url#hash?query because location.hash returns EVERYTHING after the # (both # and ? are fragments identifiers so location.hash behavior seems unexpected).

Apologies for not replying sooner and thanks for the update.
I still haven't had time to resolve the issue but your findings seem to explain it, although as you say the behaviour seems unexpected.
I'll try swapping them around in my code and see how that goes.

This issue is stale, so I'm closing it, sorry for the lengthy delay in response.
In this case, however, there's only so much we can do to make it easy for you, I'm hoping the reversal of order worked well.


Add server option for MaxConnectionIdle

Seeing log lines of the form "rpc error: code = Unavailable desc = transport is closing" and it looks like this might fix it:
https://stackoverflow.com/questions/52993259/problem-with-grpc-setup-getting-an-intermittent-rpc-unavailable-error/54703234#54703234

The gRPC connection for containerd is via a UNIX domain socket, which does not have an equivalent to the TCP lifetime nor any intermediate proxies that might have stateful connection tracking.
Are the errors you're seeing in the client or server? If the client, is it possibly triggered by the containerd process restarting and thus interrupting the gRPC session?

@choo-stripe can you open an issue related to the problem you are seeing. As @jmillikin-stripe mentioned, there might be another root cause and we want to make sure the solution fixes the original issue.


VS Code support for private preview resource types

I would love the ability to consume resource types that are in private preview. This would help test this experience before types move to public preview.

It would be really nice to support this in an easy-to-use manner.
For now, here's a manual way to get this working using the current infrastructure:

Clone your private copy of the specs repo with your testing branch to a local folder.
Clone this repo.
Follow the instructions under https://github.com/Azure/bicep-types-az#running-generation-locally, pointing the --specs-dir parameter to the path you have cloned the specs repo to, and using the --single-path option where the path specified is the relative path to the README.md you're trying to generate types for. E.g. for the compute readme at specification/compute/resource-manager/readme.md, this value would simply be compute.
In your local copy of the Bicep repo, replace the following 2 references to use ProjectReference instead of PackageReference: https://github.com/Azure/bicep/blob/ec0c24b90d4358020131ab9b9faa234bf5502359/src/Bicep.Core/Bicep.Core.csproj#L28-L29.<ProjectReference Include="{path_to_bicep_types_repo}/src/Bicep.Types/Bicep.Types.csproj" />
<ProjectReference Include="{path_to_bicep_types_repo}/src/Bicep.Types.Az/Bicep.Types.Az.csproj" />

Run through https://github.com/Azure/bicep/blob/main/CONTRIBUTING.md#running-the-bicep-vscode-extension or https://github.com/Azure/bicep/blob/main/CONTRIBUTING.md#running-the-bicep-cli to build and run a local copy of the Bicep compiler, with your custom types added.


Add Peers and Nodes

Using websockets, add handling of peers and nodes. More information will be added later.

Netcode found in network.py and node.py

Currently working on HTTPNode because I suck at async and sockets

Blocks can now be transmitted via HTTPNode. An example of usage can be found in simplegui.py. A new method/route is needed to broadcast new blocks/transactions after a client has synced.
A synced message would help denote peers that are ready to receive new blocks/transactions.


Support of implicit flow in msal4j to acquire tokens

Hello msal4j team,
I need to acquire tokens using "implicit" grant flow. i don't see any sample example in github for "implicit" grant flow.
com.nimbusds.oauth2.sdk.id.Identifier.GrantType does have GrantType IMPLICIT.
Also, "com.microsoft.aad.msal4j.AcquireTokenByAuthorizationGrantSupplier class" doesnt implement implicit grant flow.
Could anyone let me know the references to the above problem statement?
I have a doubt that in this case, shall I use - ClientApplicationBase.acquireTokenCommon () to acquire token?
Thanks,
Mukul

@mukulb82 implicit flow is only implemented for single page applications, not web apps with a backend (which is what msal4j does, between other things).
You need to use msal.js
See Scenarios and supported platforms and languages
cc: @navyasric

Hi @jmprieur  thanks for quick response, i do understand you and i went through below documentation as well for implicit flow (https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/overview/ad-fs-openid-connect-oauth-flows-scenarios#implicit-grant-flow) - which now i think may not serve our requirement.
So basically i do have requirement to implement a solution to integrate with ADFS from a Java based web application to acquire tokens (mainly access_token and id_token) and not refreshToken (preferably and if possible).
I'm currently trying to implement typically a auth-filter (in a springBoot application) which requests for acquiring tokens after validating the presence of exisitng tokens. thereafter if the required tokens are present and are valid and not-expired then the actual resource (which can be a REST URL) have to be called.
so, in this case do you prefer that I use : authoriization-code flow(https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/overview/ad-fs-openid-connect-oauth-flows-scenarios#authorization-code-grant-flow) and not a implicit flow?
kindly suggest.
Thanks,
Mukul

@mukulb82
you are right. you want to use the authorization code flow.

okay great thanks @jmprieur .
i have one more related question to ask in case of authorization code flow.
question: How does the resource (could be any REST URL or web page or web-api) requested remains intact in the response from ADFS as the "redirect_uri" could be different from this originally requested resource by an end-user (usually through a web-browser)?
this means that as a developer how do i have a handle to the orginally requested resource so that the end-user is re-directed to this resource when the authentication is successful?
Thanks,
Mukul

@mukulb82 : I'm not sure I entierely understand your question. The app can register several redirect URI s. The audience for the token is the AppIdURI of the Web API => it's related to the logical app, and therefore is the same even if you deployed the app at several places.
Usually in a Web app you will navigate to the resource (Web app), which will delegate to Azure AD the user authenticaiton, consent etc ... and then will redirect to the URL of chosen (and proposed by the app).
See https://docs.microsoft.com/en-us/azure/active-directory/develop/scenario-web-app-sign-user-app-registration?tabs=aspnetcore and the following pages

Hi @jmprieur
I think i am trying to get what you mentioned. Let me also give you an example:

Lets say my web application with host-name: http://myapp.example.com has several REST end-point implemented (may be using SpringBoot framework lets say)
REST-end point could be from CRUD operations - /admin, /add, /delete, /view
Now, lets say i have registered my application with  ONLY with "http://myapp.example.com/admin" redirect-uri and now an end-user visits URL: http://myapp.example.com/view, so as per flow he would be redirected to a ADFS authorise end-point lets say http://myadfs.com/adfs/authorize?redirect_uri=http://myapp.example.com/admin because i registered with "http://myapp.example.com/admin" and then also some /token as a second step after receiving auth code.

So, now how the original requested URL which is - "http://myapp.example.com/view" be the user redirected??

Below are my questions -

a) How does the original requested URL "http://myapp.example.com/view"  (which is different fro what is registered) be called and will be available in the response ?
b) Do we need to register all the required URLs as part of client set up in ADFS management console?
Let me know if am able to make you clear here? Also i read about a resource parameter as part /authorize end-point ? is it helpful?

@mukulb82 You can register multiple redirect-uris. When you make the call to authorize, you pass the redirect-uri to which you would like the user to be redirected after they authorize. These will probably vary depending on your application logic/ what the user is trying to get access to.
Following your example, if you would the user to be redirect back http://myapp.example.com/view after they are done authenticating, you would also register http://myapp.example.com/view and then pass it in as the query parameter to the authrozation code URL call. The user would then be redirected back to that page.


./cleos get currency balance eosio.token exchange1 EOS

could someone explain how to convert get balance into REST API Call?
http://<IP_ADDRESS>:8888/v1/chain/get_currency_balance
post request with {"contract":"eosio", "account": "exchange", "symbol":"EOS"}
I am getting following error message
{
"code": 500,
"message": "Internal Service Error",
"error": {
"code": 3060002,
"name": "account_query_exception",
"what": "Account Query Exception",
"details": [
{
"message": "Fail to retrieve account for ",
"file": "chain_plugin.cpp",
"line_number": 462,
"method": "get_abi"
}
]
}
}

@thinkSharp your request should look like
{"account":"exchange","code":"eosio.token","symbol":"EOS"}

In the future release cleos will support --print-request, so you will be able to see what request is it doing ( #3849)
I am closing the ticket. Feel free to reopen if you still have the problem.


Persistent thinking dots when issue with parsing code

Expected behavior: Floating dots (the dots UI that indicated that the application is "thinking" / "processing") do not display indefinitely.
Observed behavior: There are cases when the floating dots display indefinitely after "Reset Code" is pressed.
Steps to reproduce: Simple example is return ss in the first common char question. Could not get application to reproduce floating dots persisting across code executions and page refresh, but I did see it.
High Priority: * This may be impacting user study results! *

Looking at this, but having difficulty reproducing (Chrome on Mac). Do you mean just opening up the application and submitting return "ss"?
If you can reproduce locally, are there any console errors?

Return an undefined variable, not a string:
return ss

I confirm this bug. Working on it.

Thanks seanlip!

Fixed in #310


Apply edge to edge into contributors page

Issue

close #458

Overview (Required)

I applied edge to edge into the contributors page.
Pass the innerPadding as contentPadding in LazyColumn.

Links

https://developer.android.com/develop/ui/views/layout/edge-to-edge

Screenshot

Description
Before
After

3-buttons case(portrait)

gesture navigation case(portrait)

3-buttons case(landscape)

gesture navigation case(landscape)

👀


aziot_esp32 fails with Arduino Espressif ESP32 2.0.0-rc2

Upgrading the Arduino ESP32 board resources to the latest breaks the MQTT communication with the Azure hub.

Sample code compiles & runs with ESP32 board 1.0.6.
Update via Arduino boards manager to 2.0.0-rc2.
The code compiles ok, but crashes after "MQTT client started"
static int establishConnection()
{
  connectToWiFi();
  initializeTime();
  initializeIoTHubClient();
  (void)initializeMqttClient();
}

Setup (please complete the following information):

OS: Win10
IDE: Arduino 1.8.13
Azure/azure-sdk-for-c 1.1.0

Hey @RLmonitor, pre-release versions like this one are normally less stable and more prone to random errors than the latest stable version which is the 1.0.6. They're also not recommended for production scenarios, which is why we test - and you confirmed - version 1.0.6 works fine with the ESP32 and Azure IoT. This is the reason why we don't support release-candidate versions, until they become a stable release.

Thanks for your comments. I'll look forward to the release version. I was testing RC2 as it has a fix for a hang when the UART is initialised and there is incoming data.


Reject bdist uploads containing inconsistent metadata

What's the problem this feature will solve?
See https://pypi.org/project/triton/0.4.0/#files, which has 0.4.1 wheel names but (as the URL indicates), the wheels are actually for a 0.4.0 version.
This happened due to an incorrectly manipulated package by the author of the package (see https://github.com/openai/triton/issues/122) which resulted in an inconsistent version number being presented between the simple index and the project page.
Describe the solution you'd like

Such uploads should be blocked.
Additional context

None? I tried to look for duplicates and couldn't find any. Apologies if I missed something relevant!

Thanks for filing! Doing a bit of triage:
It's odd that PyPI accepted this at all, since the upload endpoint does check for consistency between the version in the wheel name and in the metadata:
https://github.com/pypi/warehouse/blob/7c93a28780ea728ac07b51d03a1c6b7db45899d9/warehouse/forklift/legacy.py#L1026-L1031

Oh hmm, trition==0.4.0 was uploaded in May 2021, and that check was added just a few weeks ago with https://github.com/pypi/warehouse/pull/15795, fixing https://github.com/pypi/warehouse/issues/15749.
So I think this is already fixed 🙂

Yeah, this is fixed.


Update artifact name for flaky tests

Flaky tests failed as their generated artifacts had the same names for runs with Fast DDS v2 and Fast DDS v3.

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

Project coverage is 26.34%. Comparing base (57421e1) to head (417c409).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #162      +/-   ##
==========================================
+ Coverage   25.17%   26.34%   +1.16%
==========================================
  Files          75       56      -19
  Lines        5842     3671    -2171
  Branches     2999     1811    -1188
==========================================
- Hits         1471      967     -504
+ Misses       3408     2030    -1378
+ Partials      963      674     -289

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


Plans to support compilation via Yul IR (--via-ir option)?

Hi folks.
It looks like Ethereum Team is moving to more adaptation for Yul support, since it allows for better optimizations and helps with common EVM compilation issues, such as stack-too-deep errors (error that I faced when trying to compile for TVM).
Are there plans to add Yul IR compilation option to TVM compiler? Failed to search for any information regarding Yul for TVM.

It seems they don't support --vir-ir flag yet.
I am looking.

The next version will support

@cfengliu https://github.com/tronsuper/bare-box/blob/master/tronbox.js#L58 The configuration is here


Pre-Release <IP_ADDRESS> - Sunday, 13 September 2020, 23:09:05

Testing new pre-release
--> Loading game with Harmony, Core, HugsLib, Rimthreaded
--> Running Rimworld 1.2.2753
--> New Colony, Tribe
--> Random pawns
--> Random starting location
Game throws massive error logs the moment pawns start interacting with items; e.g. eating food.
The following log was thrown within 4 seconds of gameplay.
Test aborted, unstable.
System information and error log attached.
System-Info.zip
Player.log
Player-prev.log
Edit: verified findings, added addition log.
Player - verified.log

bad preview version was released


Help! After updating VSCode, I can no longer connect to NixOS though the WSL remote

You may have noticed that with the latest update to the WSL remote extension (0.77.0), connecting to NixOS fails.
This is because Micrsoft removed the option for setting the remote connection method. Where before you could get it to connect by setting the option to something other than wslExeProxy, that is the only option available now.
There are two issues tracking possible solutions:

microsoft/vscode-remote-release#8305 asking them to patch the alternate connection methods back in
#222 here for patching NixOS on WSL to support wslExeProxy

EDIT: As @purepani pointed out over at the Microsoft repo, for the time being, you can try to get it to work by downgrading the WSL Remote extension to the latest working version (0.76.0) either through the GUI or by running the following command:
code --install-extension<EMAIL_ADDRESS>
and making sure that you have the following setting configured in VSCode
  "remote.WSL2.connectionMethod": "wsl2VMAddress",

Or if downgrading isn't desired, msteen's VSCode Server is also an option. Just my two cents here :)

For me, just type code in my WSL shell, waiting for it to download vscode-server is enough.
After vscode-server is downloaded, everything is the same as before. Just use nixos-vscode-server or manually replace node under ~/.vscode-server with a symlink.

While debugging why my WSL setup broke I discovered that it only wants to run uname
wsl.extraBin = with pkgs; [
  { src = "${coreutils}/bin/uname"; }
];

but the node is then unpatched. Probably patchelfing it could fix things.


🚪 Add feature to export dashboard configuration to a json file

Problem
When migrating a suricate instance to another cluster,
Suggestion
Add a feature to export dashboard to backup, share or migrate configuration

@yodamad
There's an endpoint that exports (and imports) the whole configuration of an instance: https://github.com/michelin/suricate/blob/master/src/main/java/com/michelin/suricate/controller/ImportExportController.java#L76
Does this issue intend to export the configuration of a single dashboard?

@loicgreffier
Yes I'd need to export just a single dashboard to be able to provide a catalog of predefined dashboards in my company


Added "Terms and Conditions" and "Privacy Policy" Pages

Hey @Its-Aman-Yadav and @Kalivarapubindusree
issue closes #879
Below are the Changes I Implemented -

I Created two separate HTML pages for "Terms and Conditions" and "Privacy Policy" .
I added a NEW COLUMN as name "Legal" to add Legal Pages related to the website (also linked both the pages in it).
I tried my very best to style the two pages similar to the website's color theme so that visually it will look good to see.
I have included a footer at the end and the navbar at the top to both pages for better experience.
Additionally, I have linked these pages "Home" Section of navbar to home page.

Please take look to the video below -
https://github.com/Its-Aman-Yadav/Community-Site/assets/131389695/1a611929-8579-4bec-9aed-2b1b3f2aee65
@Its-Aman-Yadav Please review the changes and let me know if any adjustments are needed.
Thank you!
I look forward to contribute more to your project.

Great work @aslams2020


docs: updated the faq.md file

@vplasencia , added difference between the Bandada and Semaphore  in the faq.md file

Hey @od-hunter! Thank you very much for the PR. I will review it this week.

@vplasencia , so sorry will send a more accurate pr

Hey @od-hunter no worries. Thank you very much and let me know if you need help.

Hey folks - any progress on this?
@vplasencia perhaps worth just merging this then making the updates you see fit?

Hey @od-hunter! This is a high priority task now, so I will work on it to finish it asap.
Then I will need to close your PR, sorry about it, but feel free to ask for any other good first issue here: https://github.com/bandada-infra/bandada/issues?q=is%3Aopen+is%3Aissue+label%3A"good+first+issue"
Thank you! 🙏
I added the same comment in the issue: https://github.com/bandada-infra/bandada/issues/438#issuecomment-2338492944


Remove StubGitHub in favor of our existing mock

Summary
This removes the manually-maintained StubGitHub in favor us using
the auto-generated one.
Change Type
Mark the type of change your PR introduces:

[ ] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[x] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 47.713% (+0.01%) from 47.701%
when pulling 20222582e0ce01b0306821b0ff23b1aee7cc22c9 on rm-stub
into bc7c7c968ade457782cda56f6f962b38f29304cb on main.


Turning on bluetooth after installing WinUSB

Hi,
I installed the WINUSB driver for my Intel Wireless Bluetooth 7260 bluetooth hardware. However, I'm not able to enable or disable bluetooth with the WINUSB driver. The default apps to enable bluetooth do not work anymore. Running a bluetooth code using this just hangs
set BLUETOOTH_HCI_SOCKET_USB_VID=0x050d
set BLUETOOTH_HCI_SOCKET_USB_PID=0x065a

node <file>.js

I'm running on Windows 8.1

With WinUSB you won't be able to enable or disable Bluetooth using the Windows UI as the driver is unloaded.
See https://github.com/sandeepmistry/node-bluetooth-hci-socket#windows to see how to revert the driver.


Property 'setState' error rectified.

Property 'setState' does not exist on type 'InnerMe' error in TestMe.tsx rectified.

can you please rebase to master? looks like something may have also gotten force pushed so expect merge conflicts...?

can you please rebase to master? looks like something may have also gotten force pushed so expect merge conflicts...?

Everything seems to be up to date and I think there are no merge conflicts.

InnerMe extends React.Component, which means that setState and props will automatically be available. The only reason I can think of that setState and props wouldn't be available is if you didn't run npm install before npm start.

Closed this PR since I don't think it's the right fix. Feel free to open an issue and tag me if you'd like help debugging what's going wrong.


RFC-3197: Config

Close https://github.com/apache/incubator-opendal/issues/3151
Close https://github.com/apache/incubator-opendal/issues/3152

Just a thought, what about add a interface in trait Builder
fn config(&self) -> Box<dyn Config>

And let Config itself be
trait Config: Serialize + Deserialize + ....

trait Config: Serialize + Deserialize + ....

Providinh a trait that allows Serialize + Deserialize is different from providing structs/enums that supports Serialize + Deserialize. The structs/enums allows users to work directly with detailed configuration.
Users can implement TryFrom/TryInto according to their own needs.
This is crucial for production applications as they do not want to be impacted by OpenDAL's breaking changes.

Hi, @oowl, please don't force push my branches. Thanks.

For dealing with secrets, there is secrecy

For dealing with secrets, there is secrecy

Thank you for the advice. However, as stated in the proposal, this does not include anything related to secrets.

cc @suyanhanx @Ji-Xinyou @ClSlaid would you like to review again?

Hi, @suyanhanx, do you have any review comments to address?


Match Postgres for stddev and variance on less than 3 values

Describe the bug
The behavior of the stddev and variance aggregation differs from Postgres for less than three values.  DataFusion crashes in these cases, whereas Postgres computes a variance for an array with two values and returns NULL for an array of one value.
In DataFusion CLI:
❯  select stddev(sq.column1) from (values (1.0), (2.0), (3.0)) as sq;
+--------------------+
| STDDEV(sq.column1) |
+--------------------+
| 1                  |
+--------------------+

❯  select stddev(sq.column1) from (values (1.0), (2.0)) as sq;
ArrowError(ExternalError(Internal("At least two values are needed to calculate variance")))

❯  select stddev(sq.column1) from (values (1.0)) as sq;
ArrowError(ExternalError(Internal("At least two values are needed to calculate variance")))

In Postgres
❯  select stddev(sq.column1) from (values (1.0), (2.0), (3.0)) as sq;
1

❯ select stddev(sq.column1) from (values (1.0), (2.0)) as sq;
0.7071067811865475244

❯ select stddev(sq.column1) from (values (1.0)) as sq;
NULL

I would like to suggest DataFusion match the behavior of Postgres. Otherwise every usage of the variance function risks raising an error (depending on the distribution of the groupby column).
Additional context
Variance was first added by @realno in https://github.com/apache/arrow-datafusion/pull/1525.

We should definitely calculate something for the two-sample case -- erroring simply doesn't make sense in that case. The second example has various behaviors going around, see the discussion in Snowflake docs. I agree with your sentiment that we should align with Postgres.


Closes: #1 Usernames should always start with letters

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #1

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!
-------- Original message --------From: "google-cla[bot]" @.> Date: 10/07/2021  6:01 pm  (GMT+05:30) To: google/it-cert-automation-practice @.> Cc: Ram Khavanewadkar @.>, Author @.> Subject: Re: [google/it-cert-automation-practice] Closes: #1 Usernames should
always start with letters (#15457)
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers
It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.
ℹ Googlers: Go here for more info.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Change Paper - content updates

Collection of changes to support missing content in the Change Papers.
Testing
I've tried to include some automated tests to verify the HTML/DITA output, but manual testing is slow and laborious...

Publish mdm-plugin-nhs-data-dictionary to Maven local and run in mdm-application-build
Run the Orchestrator and sign in
Click on the "Changes" nav link
Select an in-flight branch, then click "Run". This will give a preview of the change paper content.
Next click on "Branches" nav link.
Select a in-flight branch, click "Publish", then one of the generate buttons to produce DITA
Wait...
Download the zip file result, extract to a local folder
Use OxygenXML on the DITA content to produce a PDF

Publication Date Format
Fixes #66
Fixed the publication date to use "dd MMMM yyyy" format, as requested in NHSDigital/DataDictionaryPublication#498

Missing descriptions for "Updated descriptions"
Fixes #72
This didn't seem to work on TEST but does on my machine (I don't understand why...), so considering this resolved apart from styling, which is NHSE responsibility:

Include "Change attributes" list for Classes
Fixes #75
Classes did not appear in the list of changes because only descriptions were checked. I've updated this to perform a check on attributes within a class that might have been added/removed:

Include missing tables for Attributes
Fixes #74
Attributes had certain information missing, which I have now added.
Aliases table:

National codes table:

Include "Format / Length" for Data Elements

"Summary of Changes" incorrect
Resolves #71
I think this is down to the data ingested and being modified on the server. Also, some of the supposed changes were down to missing content (above), so I think this issue is actually a red herring.
Data Set definition changes
Resolves #76
When including data set definitions:

Refer to the definitions as "Changed Data Set" instead of "Unchanged Items", like the original Borland Together change papers.
Don't include Data Elements and Attributes related to data sets multiple times - if a Data Element or Attribute was changed, it does not need to be added a second time, since this breaks the unique topic keys of the DITA output.

Exclude diffs containing HTML tables
Fixes #77
There is an issue with DaisyDiffHelper when comparing HTML content containing tables, the added/removed tags/markup that it adds will intermingle with the table markup, causing a table structure that is not accurate. This is especially troublesome when converting the HTML into DITA because that is much stricter on the XML schema. Temporary solution is to not perform a diff on such content - just show the current content with a message to explain.
Include data set specifications
Resolves #73
Added the missing data set specification tables to the change paper (preview and PDF):

To answer some of your questions...
The dictionary branch should have a "Work Item" profile at the versioned folder level which details the change paper reference e.g. "CR1883". The reason why "CRXXX" is used is because we haven't overwritten that profile in our local environments. Same with the background page text, this would be included with the work item profile to produce correct page output.
I think your comments are worth noting but I'm happy to merge this now and release it for testing.


Allow saveMany() to accept Collections as first parameter

Currently, when using saveMany() in a seeding/model factory context, you have to use create() and then call all() on the returned Collection. This PR makes it to where you can just call create():
$people->each(function ($person, $key) {
    $person->contacts()->saveMany(factory(Contact::class, 5)->create());
});

Please send to 5.2. Changing the method signature is breaking.


i2c: move nordic IPs to sda-gpios, scl-gpios

Nordic pinmuxing for I2C SDA and SCL pins is done with sda-pin and scl-pin DTS properties. Move these to a more idiomatic sda-gpios and scl-gpios style instead.
A prototypical example for how the devicetree should be updated is:
 &i2c1 {
 	compatible = "nordic,nrf-twim";
 	status = "okay";
-	sda-pin = <41>;
-	scl-pin = <11>;
+	sda-gpios = <&gpio1 9 0>;
+	scl-gpios = <&gpio0 11 0>;
 };

The old properties continue to be supported, but are now deprecated. Move in-tree boards and sample overlays to the new style.

@pabigot @anangl this is picking up where we left off in https://github.com/zephyrproject-rtos/zephyr/pull/30769.
I'm only doing TWI and TWIM for now to keep this relatively small since it's the first one.
I've discsussed with @carlescufi and I can commit to updating all of the following properties for Zephyr 2.6 in this and follow-up PRs:

nordic,nrf-i2s: sck-pin, lrck-pin, sdout-pin, sdin-pin, mck-pin
nordic,nrf-pdm: clk-pin, din-pin
nordic,nrf-pwm: ch0-pin, ch1-pin, ch2-pin, ch3-pin
nordic,nrf-qdec: a-pin, b-pin, led-pin, enable-pin
nordic,nrf-qspi: sck-pin, csn-pins, io-pins
nordic,nrf-spi: sck-pin, mosi-pin, miso-pin
nordic,nrf-spim: sck-pin, mosi-pin, miso-pin
nordic,nrf-spis: csn-pin, sck-pin, mosi-pin, miso-pin
nordic,nrf-twi: sda-pin, scl-pin
nordic,nrf-twim: sda-pin, scl-pin
nordic,nrf-twis: sda-pin, scl-pin
nordic,nrf-uart: tx-pin, rx-pin, rts-pin, cts-pin
nordic,nrf-uarte: tx-pin, rx-pin, rts-pin, cts-pin

Rebased onto https://github.com/zephyrproject-rtos/zephyr/pull/32001.

Seeing if temporarily increasing the buildkite parallelism will avoid CI timesouts. DNM since that patch should not be merged.

Added a missing include to the TWI driver and rebased.

Remaining CI failures are due to https://github.com/zephyrproject-rtos/zephyr/issues/32619 as far as I can tell.

All of the remaining CI failures contain the same message and look like timing nondeterminism to me:
    Assertion failed at WEST_TOPDIR/zephyr/tests/net/socket/select/src/main.c:101: test_select: (tstamp <= FUZZ is false)

I'm going to consider this green CI and will work with @carlescufi to get this merged tomorrow after removing the DNM patch increasing the bitkeeper parallelism.
Hopefully this is it, thanks to everyone who reviewed.

The PR has been merged, so following is just for the record. I believe the implementation presented in this PR does not follow Linux device tree specification.
The -gpios properties are meant to be used for pins controlled by the GPIO module only. This is documented in "Specifying GPIO information for devices".
Pins controlled by other hardware modules, i2c, uart, spi, etc. should use pinctrl-bindings. Unfortunately, it doesn't seem to be a good match for requirements imposed by the Nordic HAL so the now deprecated -pin properties might have been a better choice.
In general it's important to be able to distinguish if the pin is controlled by the the hardware module, e.g. i2c, spi or the GPIO module since there exist configurations when the same pin e.g. SS pin of the SPI bus is switched at runtime between SPI and GPIO hardware module. DT node describing such configuration would contain both: pinctrl- and -gpios properties.

@mnkp I'm working through all of our bindings during this release to move them to foo-gpios, so I would like to know more about what a better way might be. Note that @anangl is also following this approach in https://github.com/zephyrproject-rtos/zephyr/pull/34251. I think we need to converge on the right approach quickly if possible.
However, I think it's important to be able to specify a GPIO controller phandle, pin, and flags.
For some additional relevant background, I tried to get a build system target merged which produced a report of which pins were used by which peripherals in https://github.com/zephyrproject-rtos/zephyr/pull/24132. That used the existing foo-pin properties, but it was rejected as insufficiently generic to go upstream, and I was under the impression that we would have to do something like this PR to get this feature merged on top of it.
I think a real phandle is also important so the I2C -> GPIO device dependency is tracked in things like DT_REQUIRES_DEP_ORDS().
A pin number is important for obvious reasons.
As for flags, I was planning on replacing things like our miso-pull-up property with the relevant GPIO flags.

Unfortunately, it doesn't seem to be a good match for requirements imposed by the Nordic HAL

These are not simply HAL requirements. Each peripheral has registers which are programmed with the port and pin to use which were the actual foo-pin values, so a SPI peripheral has a PSEL.MOSI register, and so forth.
This PR's approach of converting a phandle and pin to the value that goes into these registers is more readable. I am trying to avoid past support problems with people who didn't get how to encode and decode the foo-pin properties, which after all are exposing raw register values.
Beyond these PSEL.MOSI style registers, the pins themselves are configured using the GPIO registers.
I can rename these properties to something that's more appropriate than scl-gpios, etc. if you can suggest an alternative, but given the above I think the general approach is sound. However I haven't followed the pinctrl discussion and I may have missed something; I'll read through your reference and see what I can come up with.

At first short introduction to the Linux pinctrl DT bindings. The Linux description of pin controller node in DT was developed around the notion that the SoC has a dedicated pin controller block, most SoCs do, that has its own register address and its main purpose is to route signals between pins and different SoC peripherals. It quickly become clear that the actual hardware design of pin muxing in SoCs put on the market by different vendors differs so much that it's not feasible to have one way to describe pin controller nodes in DT. That's why Linux pinctrl bindings make recommendations, show how to describe typical hardware but officially leave the actual implementation in the hands of the developer.
That is, it's OK to have vendor specific implementation.
About the only requirement that Linux DT imposes is that pin configuration on the client side, e.g. I2C module, will be defined using pinctrl-n properties. From the binding document
Required properties:
pinctrl-0:	List of phandles, each pointing at a pin configuration
		node. These referenced pin configuration nodes must be child
		nodes of the pin controller that they configure.

It would be nice to have it done this way also for Nordic but it's not that easy and probably it's not worth it.
For me it's fine if those families, like Nordic or SiLabs, that don't actually have pin controller hardware module use a vendor specific approach. The drawback here is that they will never have support for the official Zephyr pinctrl API. But surely they could have a vendor specific one.
That said, the -gpios properties are used in DT exclusively to describe pins connected to / owned by the GPIO driver, so whatever way we come up with we should not use those to connect pins with other peripherals.

However, I think it's important to be able to specify a GPIO controller phandle, pin, and flags.

Yes, sounds good. I believe we should use whatever is easiest, most natural for the user.

For some additional relevant background, I tried to get a build system target merged which produced a report of which pins were used by which peripherals in #24132. That used the existing foo-pin properties, but it was rejected as insufficiently generic to go upstream, and I was under the impression that we would have to do something like this PR to get this feature merged on top of it.

That looks good, it would be great to have it supported on all the platforms. However, a general solution won't be easy. Likely, the implementation would always need to be family specific.

The drawback here is that they will never have support for the official Zephyr pinctrl API. But surely they could have a vendor specific one.

Tagging @carlescufi and @anangl on this feedback from @mnkp about the scl-gpios, sda-gpios approach I have taken for TWIM etc. and we are taking on I2S and other peripherals.
I think this is a rather serious drawback and we need to rethink our approach.

About the only requirement that Linux DT imposes is that pin configuration on the client side, e.g. I2C module, will be defined using pinctrl-n properties.  [...] It would be nice to have it done this way also for Nordic but it's not that easy and probably it's not worth it.

@mnkp Just throwing an idea out here to check my understanding. What's wrong with something like this?
i2c0: i2c@40003000 {
	compatible = "nordic,nrf-twi";
	/* ... */

	pinctrl-0 = <&i2c0_pinctrl>;
	i2c0_pinctrl: pinctrl {
		sda-gpios = <&gpio0 26 0x0>;
		scl-gpios = <&gpio0 27 0x0>;
	};
};


the time suffix hits the web_version_by_plugin.json cache

web_version_by_plugin.json use "t=${performance.now()}" as suffix.
When there is a high number of visiting users and the website utilizes a CDN, it can result in the file being cached and frequently prompting the need to refresh the page. Is it possible to change the file's suffix to a timestamp?

good question


How to Save & Application Stop Unexpectedly ?

Sorry, for Disturbing you Again. Actually I have two issues

How to Save the Edited Hex File I tried to figure it out, but sample doesn't contain any such example.

Whenever I select Fill selection with Byte, it gets stuck and stops.. I have attached a video in zip which will show you how to reproduce the issue.

Thanks Again! Your Work is really Worth
attach.zip

You can save with SubmitChange() for crash o will check this soon :)

Put your build in Debug and send me a screenshot where the code crash please.

Hi @KaustubhPatange the bug are fixed !
Take the lastest code to update. :)


configure.sh: make pkg-config and ar used for host configurable

Hi, thanks for this PR, can you confirm that Solo5 works for NixOS? I will be able to cut a minor release if you want.

No, still some obstacles, these are just some low hanging fruits / non-invasive changes that I've found useful. If you want to follow the progress, you can look at https://github.com/NixOS/nixpkgs/pull/153204.

Thanks, if you want any help on our side, don't hesitate to call us 👍 ! On our side, I think we will move forward and release the rest of the MirageOS toolchain - we desperately want to cut a release before February. I'm currently working on the CI of Solo5 too and we will start to figure out how to integrate NixOS as a platform and how to test it systematically (as Debian, FreeBSD and OpenBSD) to finally help any of us.

4 years after, I was able to launch CI on your PR. I will try to see why we have an error on OpenBSD 7.2 and FreeBSD 14 (something is probably missing in these systems).

Ok, the CI looks good now, the PR seems ok and I like the idea to be able to define HOST_AR and HOST_PKG_CONFIG :+1:. Let's merge and sorry for the long delay.


Transport components

paul's transport component idea. added base component so we can get started

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Can't open folders in Explorer view

Issue Type: Bug
All of a sudden most of the folders I try to open in VS Code simply won't open.
Reproduction:

Create a new, empty, repo in Gitlab
Frrom a terminal:  Clone the repo
cd new-repo
code .

Expected results
The folder is opened in the Exporer view
Actual results
The Explorer view says, ”You have not yet opened a folder”. Using the Open Folder button doesn't help, neither Open from the File menu.
Similar symptoms as with #91002, afaict.
Some folders do work.
It works in Insiders June: 1.47.0-insider. However I am not sure that means it is fixed. Rather it could be that some state I have in my regular Code install is not there for my Insiders install. At least I can't find any PR addressing this.
VS Code version: Code 1.46.1 (cd9ea6488829f560dc949a8b2fb789f3cdc05f5d, 2020-06-17T21:17:14.222Z)
OS version: Darwin x64 19.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
32.00GB (0.97GB free)

Process Argv
.

Screen Reader
no

VM
0%

Extensions (26)

Extension
Author (truncated)
Version

calva
bet
2.0.106

emojisense
bie
0.7.0

clj-kondo
bor
2020.6.21

better-toml
bun
0.3.2

gitlens
eam
10.2.2

terraform
has
2.0.2

vscode-mocha-test-adapter
hbe
2.6.0

vscode-test-explorer
hbe
2.19.1

chat
kar
0.35.0

restructuredtext
lex
128.0.0

vscode-scss
mrm
0.9.0

vscode-docker
ms-
1.3.1

vsliveshare
ms-
1.0.2377

vsliveshare-audio
ms-
0.1.85

vsliveshare-pack
ms-
0.4.0

debugger-for-chrome
msj
4.12.8

vscode-react-native
msj
0.16.0

typescript-hero
rbb
3.0.0

vscode-xml
red
0.12.0

vscode-yaml
red
0.8.0

terraform-doc-snippets
run
0.4.0

code-settings-sync
Sha
3.4.3

vscode-scss-formatter
sib
2.0.1

code-spell-checker
str
1.9.0

shellcheck
tim
0.9.0

org-mode
too
0.5.0

Does the problem also happen if you launch with all extensions disabled?

Hi PEZ, this issue is because of the problem of the extensions for the VS code which is present suffering everyone. So, I would suggest either to reset the settings or re-install the file related extensions or GIT related extensions.

Also. After having done an extension-less launch seems to have fixed whatever caused the problem. Now I can run with extensions enabled and folders open as they should.

So it seems to be caused by an extension. Please find which extension caused it and file an issue against that extension. Thanks


Enable tabs

References:

https://develop.spacemacs.org/layers/+emacs/tabs/README.html

I tried this, it was annoying.


Localizing images destroys tables

Hi
I like this plugin a lot but there is a downside. It destroys tables if the images are in tables. You can test it with the page below yoursel. Copy and paste the page then run localize attahcments
https://github.com/nerdyrodent/AVeryComfyNerd
thanks

What do you mean by Localize Attachments? This plugin doesn't have such command

Fixed in https://github.com/dy-sh/obsidian-consistent-attachments-and-links/releases/tag/2.0.0


Template Payload extraction + cleanup

Extract timer template payload
Created extension for NotificationContent class to retrieve template payload keys
Support for Dark Mode
Unit test for TemplatePayload

Closing this PR because https://github.com/adobe/aepsdk-notificationcontent-ios/pull/15 contains the same code


AD-173 - db refactor: improve how dashboard configuration is stored for teams

Description

add a new table Configuration composed by Jira config and Bug SLOs config
support custom team jira queries
support custom metric for the Jira Bugs affecting CI for each team

Issue ticket number and link
AD-173
AD-172

/lgtm

/retest
outage in production: https://issues.redhat.com/browse/SRVKP-5770

/lgtm


[REFACTOR] Move the setup.py to pyproject.toml.

Yes it should, python-publish action uses build that recognizes pyproject.toml file.


Merge provided dev option with default

Operating System: macOS 10.13.3
Node Version: 8.9.4
NPM Version: 5.7.1
webpack Version: 4.0.1
webpack-serve Version: 0.1.5

This issue is for a:

[ ] bug
[ ] feature request
[x] modification request

Code
CLI Command
  $ webpack-serve

webpack.config.js
{
  serve: {
    dev: {logLevel: 'warn'},
  },
}

Expected Behavior
Currently, the dev option defaults to {publicPath: '/'}. I was expecting that if I provided my own dev config object, it would be merged with the default one. In other words, if I only provide logLevel, I expected publicPath to still be /.
Would you consider making this behavioral change? I would be happy to PR it.
Actual Behavior
The provided object is not merged with the default one, so changing the log level of the dev server removes the default publicPath config.
New Feature Use Case
Shown above -- tweaking an unrelated setting without affecting the defaults.
(P.S. thanks for this library! ❤)

Thanks for the PR 🍺  You'll see a fix commit pop up in this thread any second now. Feel free to put together PRs in the future, we love those! (I just happened to be cranking away on this when you made that issue)


Detect EOF while reading in libssl (master)

If we hit an EOF while reading in libssl then we will report an error
back to the application (SSL_ERROR_SYSCALL) but errno will be 0. We add
an error to the stack (which means we instead return SSL_ERROR_SSL) and
therefore give a hint as to what went wrong.
Contains a partial fix for #10880
This is the master version of #10882. I've left #10882 in WIP for now, but this one is ready for review.
I have a feeling that we are likely to see a number of reports as a result of this change going in. It turns out to be rather easy to hit the new "unexpected eof while reading" error that this change introduces.
For example if you start s_server:
$ openssl s_server

And then start s_client:
$ openssl s_client

Simply pressing ctrl-C on the s_server side results in this error on the s_client side:
40:C2:55:46:1B:7F:00:00:error:SSL routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:306:

Previously we got this rather enigmatic and unhelpful message:
read:errno=0

Similarly doing it the other way around (pressing ctrl-c on the s_client side) we see the same "unexpected eof while reading" displayed by s_server. Previously it just said "ERROR" with no additional information.
I think this is an improvement and more accurately helps people to diagnose the problem. However I suspect that lots of people encounter this at the moment and it is logged one way in their logs - and this change will give a different error message - which may be a surprise to lots of people.
With all of that in mind we should consider whether we want to backport this to 1.1.1, or whether this bug fix is a step too far there.

Ping

Pushed. Thanks.

So I now get the new error even without pressing Ctrl-C in openssl s_client.  That is, a normal s_client request that should end normally now fails with the error when previously with 1.1.1 it didn't report an error:
OpenSSL 1.1.1d-freebsd  10 Sep 2019:
# openssl s_client -host oe1 -port 443 -msg -tls1_2
CONNECTED(00000003)
...
---
GET /
>>> ??? [length 0005]
    17 03 03 00 1e
<<< ??? [length 0005]
    17 03 03 13 b5
HTTP/1.0 200 ok
Content-type: text/html

...
   0 callback cache hits
   0 cache full overflows (128 allowed)
---
no client certificate available

read:errno=0
>>> ??? [length 0005]
    15 03 03 00 1a
>>> TLS 1.2, Alert [length 0002], warning close_notify
    01 00

This is what I get with 'master' after this commit:
# openssl s_client -host oe1 -port 443 -msg -tls1_2
CONNECTED(00000003)
...
---
GET /
>>> ??? [length 0005]
    17 03 03 00 1e
<<< ??? [length 0005]
    17 03 03 13 b5
HTTP/1.0 200 ok
Content-type: text/html

...
   0 callback cache hits
   0 cache full overflows (128 allowed)
---
no client certificate available

00:10:B7:00:08:00:00:00:error:SSL routines::unexpected eof while reading:../ssl/record/rec_layer_s3.c:307:

I'm getting the same new error on 1.1.1e since this commit was merged there.


Tf validate debug

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

Comparison is base (60e6ffb) 98.47% compared to head (5577cf5) 98.48%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4171      +/-   ##
==========================================
+ Coverage   98.47%   98.48%   +0.01%
==========================================
  Files          43       43
  Lines        4068     4095      +27
==========================================
+ Hits         4006     4033      +27
  Misses         62       62

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


Binary collation: transparently handle int64, uint64 and float64.

Values in int64, uint64 and float64 should be comparable as if they belong to the same type -Number. Like suggested elsewhere, sorting is a human perception.
Also while converting Binary-collate back to Value, or CBOR, or JSON make sure that precision and accuracy is not lost.
Finally, add test cases to validate them same.

All of them - int64, uint64, float64 are handled as floating point, without loss of precision or accuracy (other than what float64 already suffers).