Lots of pendingchannels with limbo balance

Background
Describe your issue here.
Closed channels are not getting swept and the balance remains in limbo. I disabled height_hint cache (problem last time), didn't manage to fix.
Your environment

version of lnd 10.1-beta
which operating system (uname -a on *Nix)-  Ubuntu 18.04
version of btcd, bitcoind, or other backend - bitcoind 0.20
any other relevant environment details

Steps to reproduce
lncli pendingchannels
{
"channel": {
"remote_node_pub": "0274a984d028819cf0207965b4872aa4efa7fbd611d414d90f78c184154f099317",
"channel_point": "a3c5ded9e26441e6d956925c38353f59686660aa8ff43d38446062b5bb0d90c4:0",
"capacity": "5547214",
"local_balance": "5546723",
"remote_balance": "0",
"local_chan_reserve_sat": "0",
"remote_chan_reserve_sat": "0",
"initiator": "INITIATOR_LOCAL",
"commitment_type": "LEGACY"
},
"closing_txid": "c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc",
"limbo_balance": "5546723",
"maturity_height": 609267,
"blocks_til_maturity": -26497,
"recovered_balance": "0",
"pending_htlcs": [],
"anchor": "LIMBO"
}
Closing TXID is not found on the blockchain.
After restarting LND logs show:
May 19 21:29:34 ln lnd[882]: 2020-05-19 21:29:34.113 [ERR] CNCT: *contractcourt.commitSweepResolver(a3c5ded9e26441e6d956925c38353f59686660aa8ff43d38446062b5bb0d90c4:0): unable to sweep input: sweep failed after max attempts
May 19 21:29:34 ln lnd[882]: 2020-05-19 21:29:34.113 [ERR] CNCT: ChannelArbitrator(a3c5ded9e26441e6d956925c38353f59686660aa8ff43d38446062b5bb0d90c4:0): unable to progress *contractcourt.commitSweepResolver: sweep failed after max attempts
Expected behaviour
Channel closes
Actual behaviour
43 channels in "wait close"
7 channels in "pending force close"
30m sats! :eyes: in limbo

LND was down for about a week while I was travelling and not checking it regularly. When it restarted, a bunch of channels were inactive. They never closed properly.

If you do lncli getinfo does it show as being "synced to chain"? Also does the height reported there match the height of your backend? It might be the case that some re-scans are still on-going if it was down for a while.

sweep failed after max attempts

Any logs related to this showing why the broadcasts are failing?

version of btcd, bitcoind, or other backend - bitcoind 0.20

So 0.10.1 doesn't support bitcoind, but master, and the current v0.10.2-beta.rc2 do.

Got it, let me change versions, see if that fixes it
Thanks

Still showing limbo balance, even for a channel that supposedly closed 6
months ago. This is just one of 7 pending in limbo:
{
"channel": {
"remote_node_pub":
"0274a984d028819cf0207965b4872aa4efa7fbd611d414d90f78c184154f099317",
"channel_point":
"a3c5ded9e26441e6d956925c38353f59686660aa8ff43d38446062b5bb0d90c4:0",
"capacity": "5547214",
"local_balance": "5546723",
"remote_balance": "0",
"local_chan_reserve_sat": "0",
"remote_chan_reserve_sat": "0",
"initiator": "INITIATOR_LOCAL",
"commitment_type": "LEGACY"
},
"closing_txid":
"c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc",
"limbo_balance": "5546723",
"maturity_height": 609267,
"blocks_til_maturity": -26504,
"recovered_balance": "0",
"pending_htlcs": [],
"anchor": "LIMBO"
}
https://blockstream.info/tx/c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc
Status
26506 Confirmations
Included in Block
0000000000000000000c16bd299bd7eae7702b0ad1450306d780f01c2b6999a0
https://blockstream.info/block/0000000000000000000c16bd299bd7eae7702b0ad1450306d780f01c2b6999a0
Block height
609 267
Block timestamp
2019-12-22 03:58:21 GMT-5
I don't understand why that would be showing as in "limbo".

If you do lncli getinfo does it show as being "synced to chain"? Also does the height reported there match the height of your backend? It might be the case that some re-scans are still on-going if it was down for a while.

It is synced to chain, height 635773, which is currently the same on bitcoind and blockstream.info, so it looks good.

So what happened is that in 0.20, bitcoind changed the error message returned when you try to broadcast a transaction that's already in the chain. 0.10.1 didn't account for this change, so it thinks it's just unable to broadcast, when in fact the transaction has already been confirmed on chain.

By _running 0.10.2, lnd should now recognize that those transactions have actually confirmed (we register for confirmation after) the broadcast), and mark those channels are being fully resolved on-chain (as they are, even the outputs created have been swept somewhere).

After 12 hours, still pending. However, I see that it is trying to sweep the channel closing TXs, such as c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc which was the example channel from December.
Jun 22 00:42:55 ln lnd[12151]: 2020-06-22 00:42:55.952 [INF] SWPR: Creating sweep transaction c500a9d583d8a1913cfdadd5609f3bbb3bf83905e4237b833c59afd7739d21b0 for 5 inputs (c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0 (CommitmentNoDelay), 809a5c03859570d576ae471e2eb0f353eddd1e0b862c14a7a226014bd1260552:1 (CommitmentNoDelay), 1d922ffea7ba6534fbb62c543ee5ec9a6d7d027ceb43790d66a2bc742108b422:0 (CommitmentNoDelay), 816cb9c49ff159bff9b0932da782d7b408698a1a82241834444bbbcf19f5af47:1 (CommitmentNoDelay), 8dbb43215961988064311246f34ce3a2d1c8e7acc3c0039e84dafebf46a6cc85:0 (CommitmentNoDelay)) using 5276 sat/kw, tx_fee=0.00008077 BTC
Jun 22 00:42:55 ln lnd[12151]:    PreviousOutPoint: (wire.OutPoint) c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0,
Jun 22 01:45:01 ln lnd[12151]: 2020-06-22 01:45:01.942 [INF] SWPR: Creating sweep transaction e13c89cd013643d2fbb80ab122c812db89c180c09ee7fc83cc7c1707eeb6145c for 2 inputs (c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0 (CommitmentNoDelay), 809a5c03859570d576ae471e2eb0f353eddd1e0b862c14a7a226014bd1260552:1 (CommitmentNoDelay)) using 5276 sat/kw, tx_fee=0.00003756 BTC
Jun 22 01:45:01 ln lnd[12151]:    PreviousOutPoint: (wire.OutPoint) c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0,
Jun 22 02:07:49 ln lnd[12151]: 2020-06-22 02:07:49.665 [INF] SWPR: Creating sweep transaction 914d944d1e276de320f5db41219693e2be2aa09aed7e752a6e64c7287c5f9ba4 for 1 inputs (c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0 (CommitmentNoDelay)) using 5276 sat/kw, tx_fee=0.00002316 BTC
Jun 22 02:07:49 ln lnd[12151]:    PreviousOutPoint: (wire.OutPoint) c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0,
Jun 22 02:24:14 ln lnd[12151]: 2020-06-22 02:24:14.853 [INF] SWPR: Creating sweep transaction e8b61bb00a321bd0d62dec24059be189c29e5d53f18daad8a892463618337528 for 2 inputs (c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0 (CommitmentNoDelay), 6f9b60342937a0eb93fd1e91be9d52e90fa69db097a3b75df0fdead7706f288c:0 (CommitmentNoDelayTweakless)) using 5276 sat/kw, tx_fee=0.00003756 BTC
Jun 22 02:24:14 ln lnd[12151]:    PreviousOutPoint: (wire.OutPoint) c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0,
Jun 22 07:35:35 ln lnd[12151]: 2020-06-22 07:35:35.192 [INF] SWPR: Creating sweep transaction 95768a0aabc77ac3e8201af5f4a930773c7c534d5e792f9afbfebf415f37894e for 1 inputs (c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0 (CommitmentNoDelay)) using 4552 sat/kw, tx_fee=0.00001998 BTC
Jun 22 07:35:35 ln lnd[12151]:    PreviousOutPoint: (wire.OutPoint) c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0,
Perhaps it is having difficulty in the high-fee environment. But at least something is happening with those channels.
Should I close the issue or should I wait until it has swept it successfully?

Perhaps it is having difficulty in the high-fee environment. But at least something is happening with those channels.
Should I close the issue or should I wait until it has swept it successfully?

The outputs being swept have already been spent, which is why broadcasts keep failing. The issue seems to be lnd not recognizing the spend of the outputs being swept. Disabling the height hint cache in this case wouldn't help, but if it was already enabled and the spend wasn't detected, then that would point to an issue there.
What do your NTFN and CNCT logs show for c037a0c2c641f5c124c2483b4f9fe8da276f0d296d497c2c94047b530fc1fcbc:0?

I will restart with detailed logging on NTFN and CNCT and we'll see. Thanks

If you restart, don't forget to set --debuglevel=NTFN=debug,CNCT=debug :)

Yes exactly, it's now restarting with those two set to debug and all the rest set to info.

 Do you have any debug NTFN logs prior to the ones included in your latest comment?

I think I removed the height hint cache when running 0.10.1 which was
incompatible with bitcoind 0.20. When I upgraded lnd, I reverted the height
hint cache issue.
I will add it back in, maybe with a config option patch...
I don't have older logs. I don't keep them long.

After about 15 hours, 40 out of the 50 pending channels have cleared. Only 10 now on "pending force close"
Again, it was the height hint cache, combined with a long downtime cause by lack of maintenance and attention on my end.
I think there should be a config flag to disable height hint cache to help unstick stuck channels.
Can I get some feedback (here) on whether that's desirable so I can work on a PR to that effect?

Yeah, let's move forward with the flag.
Given that you've run into this issue twice already, would you mind keeping the debuglevel=CNCT=debug,NTFN=debug option on so that we have the logs required to debug this the next time around?

The PR adding the flag has been merged, and I think andreas reports no more pending channels running w/ the flag. Can we close this now?

Yes, this issue is resolved by the PR that disables the height hint cache
queries


Adding a tutorial about how to integrate the catalog with Wallet Connect

Look at: https://wagmi.sh/docs/hooks/useSwitchNetwork


[BUG] Filter widgets for list fields with one unique value do not allow filtering

On fiftyone==0.16.5, if a categorial field (eg "label") of a label list field (eg Classifications) has only one unique value, then the UI does not allow filtering by that value.
However, if the field is a "single" label field (eg Classification, not Classifications), then the UI does allow filtering by that single value, as expected.
The UI should always allow selecting a value, even if there is just one, because other samples may have null values (IE the filter could still return something interesting)
For example in the App below, there is no checkbox next to cat in the labels field:
import fiftyone as fo
import fiftyone.zoo as foz

dataset = foz.load_zoo_dataset("quickstart", max_samples=2)
dataset = dataset.select_fields().clone()

sample = dataset.first()
sample["label"] = fo.Classification(label="cat")
sample["labels"] = fo.Classifications(classifications=[fo.Classification(label="cat")])
sample.save()

session = fo.launch_app(dataset)

This has been resolved as of fiftyone==0.20!


Sermons button on Homepage routes you to the Events page

It is the button located in the Sermons card when scrolling down on the homepage.

fixed in dev


Eng 657 frontend allow users to view what tables

Show the base tables associated with the integration and preview (with the MUI data grid component!).

The code makes sense! Would you mind include a screen shot or recording in the PR description? It's a bit tricky to picture what things looks like

Also includes non-base tables because this backend change hasn't been merged yet: https://github.com/aqueducthq/aqueduct/pull/60
https://user-images.githubusercontent.com/30596854/173147121-6b8df795-f54d-4002-b687-1a9c0fbfcbf4.mov


Add #[no_std] support.

Would love to use this on Monotron.

Very old ticket. Haven't cleaned up that repo in a long while.
Anyway, no_std support should work. If anyone wants to give it a shot, please do.
We can reopen this issue in case we still run into issues or create a new one.
Pretty sure it's not on the roadmap for integration into Monotron (sadly), but if somebody
wants to try something similar I'd be delighted to hear about it.
Thanks for giving me the inspiration to work on this crate in the first place @thejpster. ⭐

Very old ticket. Haven't cleaned up that repo in a long while.
Anyway, no_std support should work. If anyone wants to give it a shot, please do.
We can reopen this issue in case we still run into issues or create a new one.
Pretty sure it's not on the roadmap for integration into Monotron (sadly), but if somebody
wants to try something similar I'd be delighted to hear about it.
Thanks for giving me the inspiration to work on this crate in the first place @thejpster. ⭐


Automate @polygon-nightfall/common-files release to npm

Currently, every change to common-files requires a manual deployment to npm. This thing should be automated as part of the pipeline. Helpful commands.
npm diff

npm publish

If you are still not part of the @polygon-nightfall npm org, please let me know, I am happy to add you!

@israelboudoux I may need your help on this oen as some point, probbaly early next week my friend ❣

@israelboudoux I may need your help on this oen as some point, probbaly early next week my friend heavy_heart_exclamation

I'm at your disposal! :D


LRA-478 art survey setup shibboleth to work on prod

Created TDX ticket for ITS to register Art Survey production URL to work with Shibboleth endpoint:
https://teamdynamix.umich.edu/TDClient/30/Portal/Requests/TicketRequests/TicketDet.aspx?TicketID=3825203

@britaumich - We need to wait for ITS to register production URL and then make an update in Hatchbox.


Release 3.7-Stable CR2

Close this one, and merge it manually due to the luarocks issue fixed on master.


Chain: Fix batch_size for queries

[Update] Queries weren't passing the batch_size to the underlying
adapter. Add and added test to test for this behavior.
[Update] Modified changelog in previous commit accidentally with
blanket eval_limit replaced with record_limit. Changing back
since that statement is not correct in the changelog.

Related Issue https://github.com/Dynamoid/Dynamoid/issues/85

Coverage increased (+0.005%) to 96.697% when pulling eaabe7a1fa99b3f71740d7ed129db03d1d2f9963 on richardhsu:richardhsu/batch-size-for-query into e3d233ca4367290a396b5e7be2a220794029b2d8 on Dynamoid:master.


Information on md2-select for angular 2.4.x versions

We are planning to use Angular 2.4.7 version and the application will be used in IE browser only .
I am looking for a select dropdown feature from a 3rd party resource . The IE select drop feature doesnot look good ,
So does your package work well on IE browser(ie 10 + ) ?
When displaying data in the select drop down can we pass data of any interface object type OR is there any standard way of dealing with it in this package ?
(Eg : I might have an object with many properties and, one of the property values would be used for the drop down values. and on select I could pass the whole object to the backend )

@AngularTx MD2 supports the most recent two versions of all major browsers: Chrome (including Android), Firefox, Safari (including iOS), and IE11 / Edge now we are targeting Latest browsers, so it is working in EDGE and IE11


Error on charset when using PostgreSQL

The ";charset=utf8" caused trouble on DSN when using pgsql, worked nice after removing it

ah makes me wonder if that's not valid for PostgreSQL.


Read-only file system: '/config/host_id.json' in anchore-engine-core on kubernetes 1.8 and 1.8 GKE

I've been trying to run anchore via it's 0.1.4 helm chart https://hub.kubeapps.com/charts/stable/anchore-engine/0.1.4 on GKE with kubernetes v1.8 and v1.9.
anchore-engine-worker and postgresql pods start fine but anchore-engine-core pod fails to be ready
My guess is it's related to https://github.com/kubernetes/kubernetes/pull/58720
In the logs I can see:
[service:catalog] 2018-03-21 23:51:48+0000 [-] [bootstrap] [ERROR] cannot load configuration: exception - [Errno 30] Read-only file system: '/config/host_id.json'
Traceback (most recent call last):
  File "/bin/twistd", line 11, in <module>
    load_entry_point('Twisted==17.5.0', 'console_scripts', 'twistd')()
  File "/usr/lib64/python2.7/site-packages/twisted/scripts/twistd.py", line 29, in run
    app.run(runApp, ServerOptions)
  File "/usr/lib64/python2.7/site-packages/twisted/application/app.py", line 662, in run
    runApp(config)
  File "/usr/lib64/python2.7/site-packages/twisted/scripts/twistd.py", line 25, in runApp
    _SomeApplicationRunner(config).run()
  File "/usr/lib64/python2.7/site-packages/twisted/application/app.py", line 380, in run
    self.application = self.createOrGetApplication()
  File "/usr/lib64/python2.7/site-packages/twisted/application/app.py", line 440, in createOrGetApplication
    ser = plg.makeService(self.config.subOptions)
  File "/usr/lib/python2.7/site-packages/twisted/plugins/anchore_catalog.py", line 76, in makeService
    r = anchore_engine.services.common.makeService(slist, options, bootstrap_db=True, bootstrap_users=True)
  File "/usr/lib/python2.7/site-packages/anchore_engine/services/common.py", line 315, in makeService
    raise err
IOError: [Errno 30] Read-only file system: '/config/host_id.json'
Traceback (most recent call last):
  File "/usr/bin/anchore-engine", line 128, in startup_service
    raise Exception("process exited: " + str(rc))
Exception: process exited: 1

Greeting @rawlingsj - really appreciate the reference to the recent k8s patch, I agree at first look that it is likely related, as anchore-engine does write some small files to the local configuration volume on first startup.  We'll investigate and follow up on this ticket!
Note that, if 'host_id' is explicitly set in the anchore-engine config.yaml, it will skip writing out to /config/host_id.json.  However there are some other files that will be copied over there as well, so while this could get past the first instance if the issue, there will be a few more after this point in the anchore-engine bootstrap.

Ok thanks for the fast response - I've got it building locally so can try to debug further configs, add them to the configmap and see if we can get further.  Will post my findings back.

Hi @rawlingsj , yes I see what you're saying and have reproduced the issue. The issue you referenced is indeed the cause, so it will only be seen on new k8s releases.
The core issue is the default files copied into that location. The chart statically sets the host_id in the configmap itself using an environment variable but it looks like that substitution is done after the config is loaded and host_id.json dropped to the FS during initial bootstrap script.
This will result in an anchore code update, but I'll see if I can find a helm/k8s workaround for now to get you unblocked without requiring a new release of the anchore container. Updates to follow.

OK sounds great @zhill!  FWIW I've got anchore-engine building locally as well as building the docker image so I can hack any code changes to test stuff out if that's easier.  I don't know python but with a bit of guidance or a fork to clone I can test out changes too.  No rush though, whatever is easiest for you.

Hi all,
Upon further investigation, we've determined that the existing anchore-engine chart can be run with a parameter that will set the 'service_dir' in config.yaml to a non-config volume location, which is the crux of the issue.  To do this, the command would be
helm install stable/anchore-engine --set globalConfig.configDir=/path/to/writable/directory
e.g.
helm install stable/anchore-engine --set globalConfig.configDir=/anchore_service_dir

anchore-engine will create and then use that directory, so it should be set to something that either exists and is empty (and writable), or doesn't exist but can be created (and written to).
Moving forward, we'll be changing the default setting for that parameter in the helm chart with something similiar to /anchore_service_dir, at which point it won't be necessary any longer to specify on helm install (though it would still work if one did!)
We'll keep this ticket open until the helm chart update is done, but the above should get things going against k8s 1.8/1.9/1.10!
Best
_Dan

That worked great! Many thanks @nurmi!

Update on this issue - the anchore-engine helm chart has been updated to set the service directory location by default (though the manual approach as defined here will also continue to work!).


Website/A11y - Skip links are not mentioned at https://clarity.design/documentation/app-layout

Skip links are not mentioned at https://clarity.design/documentation/app-layout
How to reproduce
Steps to reproduce the behavior:

Go to https://clarity.design/documentation/app-layout
Observe that there is no mention of the use of "skip links" to allow keyboard-only users the ability to move focus past groups of links or other controls such as those found in navigation.

Expected behavior
The layout documentation example should include skip links, and the purpose of skip links should be explained.
Versions
App

Angular: NA
Node: NA
Clarity: NA

Device:

Type: Any
OS: Any
Browser Any
Version

Additional notes
For more information please review these resources.
Success Criterion 2.4.1 Bypass Blocks
https://www.w3.org/TR/WCAG21/#bypass-blocks
Understanding Success Criterion 2.4.1: Bypass Blocks
https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks.html

I am unable to label this issue, if I could I would have applied the Website and Accessibility labels.

This is content that should go into an accessibility section. It's not something the Clarity devs should produce and maintain.

Clarity has a vision for including some accessibility content, but this is a specific detail that we don't need to track. Closing as something that is outside of Clarity's documentation or may be included as part of a generic accessibility guide.


Logic for 'Most Recent' material on homepage

Authoring/dynamic rules for 'Most Recent'.
'Most Recent' will highlight the 20 newest pieces of content published on M+ Stories using the following content type quotas:

up to 8 blogs
up to 5 journal articles
up to 1 journal issue
up to 5 videos
up to 1 exhibition/commission

Content ordering:

is there a way for us to shuffle content type but not chronology?

Notes:

pagination is for the author to set (as is currently the case)
the author can manually sort content after dynamic rules have been applied

CC: @dianewang @ellenoredsson

We've implemented this with the following logic:

The CMS grabs the latest 20 items using the criteria outlined above.
It returns these 20 items in a random order to mitigate accidental grouping of one type of content.
You can limit the number shown by default as with any other content list.

Let us know how/if we should tweak this to better suit how you imagined it. As mentioned before, we can't sort by dynamic and custom orders simultaneously, but could for example add the ability to always show the 4 (or some other number) most recent in order, and shuffle the remainder.

Hi @ellenoredsson @dianewang @laramplus -- let me know your thoughts on this... I think keeping the top three positions for the most recent would be good and support content that has a time-based prerogative. The quotas for content type and shuffle will keep the rest of the content from 'batching' up too much...

@rdunk -- let's implement as you suggest, but reserve the first three positions for 'most recent' regardless of content-type.
Question: is there any way to provide a manual override? This will be very handy, i.e. can we automatically generate a list that can then be ordered by the content author?

Okay great, I will implement that for you to test.
And regarding the question: Yes, this would be quite complicated but technically possible. There would need to be some kind of manual action required to 'refresh/replace' the current list and we would probably need to build some quite complex logic to make it foolproof. I would suggest we keep this issue open at a lower priority and return to it after resolving some of the other issues.

Will test further on Production Site when we're dealing with final content.

Re-opening this one to deal with the manual override issue as discussed above.


Add a Hackage badge to the README

Add a Hackage badge to the README so that visitors have a simple, one-click gateway to the Hackage page

This could (and should) go to main. Is there a way to retarget it?


Atom stalls when Julia is started

Hi,
I installed Atom and uber-juno package after installing Julia 0.6.0 on my machine, and Atom cannot process any Julia code. Julia is working through terminal and ipython notebook, but just not through Atom.
When I click Julia > Start Julia, a progress bar in the bottom left corner of Atom just keeps going until I manually hit Julia > Stop Julia again. Similarly, when I open up a new .jl file and type any command and hit Shift+Enter, same thing happens again.
Any help would be appreciated.

Hi, I experienced the same problem on windows10 with Julia version 0.6.2. When I'm invited to press Enter to start Julia in the console, Julia didn't start and the progress bar runs forever. I tried on a diffrent machine and had the same results. Also tried with Juno that comes with JuliaPro and again had the same problem. However I was able to make Julia run by disabling the Powershell Wrapper in Julia-Client.

Boot mode "cycler", console is REPL-based. Devtools report, WinPTY agent doesn't exist within julia-client package.

That sounds like a messed up installation -- can you try reinstalling? Also maybe disable your virus scanner temporarily and install julia client via apm install julia-client in a terminal.

Hi. Has there been found any resolutions for this problem? We've adopted Julia for our Algorithms and Datastructures course, and recommend Atom/Juno as IDE. But a lot of students with Windows computers have this problem.
Reinstalls doesn't fix it, nor does checking the path. They all have updated versions, including julia 1.0.0.

Ah. No, the main issue, with the REPL hanging on "Press Enter to start Julia."

I have never been able to repro that issue, so a couple of questions:
Does using Pkg; Pkg.add("Atom"); using Atom work in a REPL? If you open the devtools with Ctrl-Shift-I, are there any errors?

using Pkg; Pkg.add("Atom"); gave an error + stacktrace starting with
ERROR: The following package names could not be resolved:
* Atom (not found in project, manifest or registry)
Please specify by known `name=uuid`.

Another student proposed the following, which solved the problem for both of them.
rm(joinpath(homedir(), ".julia", "registries"); recursive=true)

using Pkg; Pkg.add("Atom"); using Atom

Ah, right, I think that's a Pkg bug that'll be fixed in Julia 1.0.1. Glad you figured it out! :)


Return x-ms-request-id from storage service query_entities

For diagnostics, in _convert_response_to_feeds, add something like this:
if 'x-ms-request-id' in name:
            setattr(feeds, 'x_ms_request_id', value)

Issue Migrated to https://github.com/Azure/azure-storage-python/issues/15


AuthenticationMiddleware must be installed to access request.user

Hello,
I try to setup a middleware to record all request parameters to a json doc.
I've success to do all things instead to get the request.user.username information coming from the Request because it requires to install AuthenticationMiddleware.
Please can you support me to setup that properly?
Code
@app.middleware("http")
async def http_tracking(request: Request, call_next):
    response = await call_next(request)
    trace = {
        "request": {
            "type": request['type'],
            "asgi": request['asgi'],
            "server": request['server'],
            "client": request['client'],
            "scheme": request['scheme'],
            "method": request['method'],
            "path": request['path'],
            "path_params": request['path_params'] if 'path_params' in request else {},
            "user": request.user.username
        },
        "response": {
            "headers": dict(response.headers)
        }
    }
    # Trace record fct

    return response

Error log
2021-04-05 00:21:07 - uvicorn.error - ERROR - Exception in ASGI application
Traceback (most recent call last):
  File "D:\documents\GitLab\bo-art-of-bonsai\venv\lib\site-packages\uvicorn\protocols\http\h11_impl.py", line 389, in run_asgi
    result = await app(self.scope, self.receive, self.send)
  File "D:\documents\GitLab\bo-art-of-bonsai\venv\lib\site-packages\uvicorn\middleware\proxy_headers.py", line 45, in __call__
    return await self.app(scope, receive, send)
  File "D:\documents\GitLab\bo-art-of-bonsai\venv\lib\site-packages\fastapi\applications.py", line 179, in __call__
    await super().__call__(scope, receive, send)
  File "D:\documents\GitLab\bo-art-of-bonsai\venv\lib\site-packages\starlette\applications.py", line 111, in __call__
    await self.middleware_stack(scope, receive, send)
  File "D:\documents\GitLab\bo-art-of-bonsai\venv\lib\site-packages\starlette\middleware\errors.py", line 181, in __call__
    raise exc from None
  File "D:\documents\GitLab\bo-art-of-bonsai\venv\lib\site-packages\starlette\middleware\errors.py", line 159, in __call__
    await self.app(scope, receive, _send)
  File "D:\documents\GitLab\bo-art-of-bonsai\venv\lib\site-packages\starlette\middleware\base.py", line 25, in __call__
    response = await self.dispatch_func(request, self.call_next)
  File "D:/documents/GitLab/bo-art-of-bonsai/blocker/app/main.py", line 57, in http_tracking
    print(request.user.username)
  File "D:\documents\GitLab\bo-art-of-bonsai\venv\lib\site-packages\starlette\requests.py", line 148, in user
    ), "AuthenticationMiddleware must be installed to access request.user"
AssertionError: AuthenticationMiddleware must be installed to access request.user

Thanks in advance, take care! and have a great day :D

Look like it wants this: https://www.starlette.io/authentication/ ?

In my case, I was using JWT Bearer authentication. So, I also couldn't call request.user where necessary. I did apply the Authentication middleware. Hope this will help.
Writing your own authentication backend

This class is written based on my application structure and needs. You may need this to fit for your application

# Authentication Backend Class
class BearerTokenAuthBackend(AuthenticationBackend):
    """
    This is a custom auth backend class that will allow you to authenticate your request and return auth and user as
    a tuple
    """
    async def authenticate(self, request):
        # This function is inherited from the base class and called by some other class
        if "Authorization" not in request.headers:
            return

        auth = request.headers["Authorization"]
        try:
            scheme, token = auth.split()
            if scheme.lower() != 'bearer':
                return
            decoded = jwt.decode(
                token,
                settings.JWT_SECRET,
                algorithms=[settings.JWT_ALGORITHM],
                options={"verify_aud": False},
            )
        except (ValueError, UnicodeDecodeError, JWTError) as exc:
            raise AuthenticationError('Invalid JWT Token.')

        username: str = decoded.get("sub")
        token_data = TokenData(username=username)
        # This is little hack rather making a generator function for get_db
        db = LocalSession()
        user = User.objects(db).filter(User.id == token_data.username).first()
        # We must close the connection
        db.close()
        if user is None:
            raise AuthenticationError('Invalid JWT Token.')
        return auth, user

Add the middleware on the main file (In my case it's main.py)

@app.on_event('startup')
async def startup():
    app.add_middleware(AuthenticationMiddleware, backend=BearerTokenAuthBackend())

@iashraful Hi I also apply starlette authentication middleware and it works properly. Anyway how did you get authorization header in swagger-ui?, Using Oauth2PasswordBearer parameter with starlette AuthenticationMiddleware decodes jwt twice. Do you know about any good methods?

Sorry didn't try it. I'll let you know if I get time for a try :)

@iashraful Sorry I misunderstand about Oauth2PasswordBearer . I debugged repeatedly with Oauth2PasswordBearer, it seems like only inspect about its authorization header type is bearer.


Port can be made optional for non-routable apps

We error out if a port is not set for non-routable apps, but there might be scenarios where you might want to run an app as job which might not require any port.
we should still continue to check for ports even for non-routable apps because they might be private apps just servicing within the cluster but shouldn't error out if not set.

Are you talking about the PORT requirement we enforce when people have private registry?

no...if an app is set as non-routable using deis routing then there should be no mandatory check for port, it might be using private registry or public.

non-routable still means we create a Service, which requires a port. How do you propose we handle that scenario if we make the port optional? default port and the service won't really point at the app properly unless people adjust?

Couldn't it just skip creation of the service, if no PORT is set?

yes...i was thinking to leave it with the default port and update when deploy updates it.

We create the service when we create the namespace so we would have to change a few things around - it's done that way so you can add domains and more before a deploy. It's an assumption models make atm that they will have the service available to them


Design issue on payment methods page

When MBO is installed, the recommanded modules on the payment methods page are not well displayed and images are not displayed

It's on the new prestashop version right ? this one seems to be a symfony controller ?

Yes, this is a preview of the Payment methods page, on the next PS release.


I know this issue has been closed but I still have the problem with the version 4.4.4 or 4.3.2

Hello,
defaultHour and defaultMinute don't work for me. Like in this other thread I linked.
Here is a JSFiddle: https://jsfiddle.net/9yc6auqL/2/
I know this issue has been closed but I still have the problem with the version 4.4.4 or 4.3.2
Originally posted by @aguidis in https://github.com/flatpickr/flatpickr/issues/1001#issuecomment-380477284

Hi @egolive,
Could you please do the following:

Update the title with what the issue is actually about
Add a description of the desired result and what doesn't work exactly
Create a JSFiddle showcasing the problem, using the latest flatpickr version

Sorry, I edit my post.

Okay, i removed maxDate but it's still not working :/
https://jsfiddle.net/f40g53yo/

Thank you, it worked :)


Add stratis fee policy to light wallet

Stratis fee is based on a fixed fee of 10,000/KB as per StratisX.
Unit tests to come in future commit.

Having a look as well.

So we agree this can go in?
Then a follow up change will come with the NBitocin changes.

Yeah that's fine for me :-) Thanks @mikedennis


Missing validation when retrieving file from S3 with SSECustomerKey

This is using boto3, but the errors happen within botocore. If I use an invalid key to upload a file to an S3 endpoint, I get:
botocore.exceptions.ClientError: An error occurred (InvalidArgument) when calling the PutObject operation: The secret key was invalid for the specified algorithm.

However, using the invalid key to fetch a file from S3 does not. With the specific cloud provider's S3 I was using, this caused botocore to try to redirect to an invalid AWS region.
I would expect to see a similar exception as above, but instead I get a connection error as botocore redirects to an invalid S3 endpoint. One workaround we will do is validate the encryption key ahead of time to make sure it's 32 bytes (256 bit for AES256) but I think this should be handled by botocore, seeing as the upload part does have validation in place.
Sample code
(Note: here I'm using boto3, but problem happens in botocore):
import os
import boto3

S3_ENDPOINT = os.getenv("S3_ENDPOINT")
S3_ACCESS_KEY_ID = os.getenv("S3_ACCESS_KEY_ID")
S3_SECRET_ACCESS_KEY = os.getenv("S3_SECRET_ACCESS_KEY")
S3_ENCRYPTION_KEY = os.getenv("S3_ENCRYPTION_KEY")
S3_BUCKET_NAME = os.getenv("S3_BUCKET_NAME")

client = boto3.client(
    "s3",
    endpoint_url=S3_ENDPOINT,
    aws_access_key_id=S3_ACCESS_KEY_ID,
    aws_secret_access_key=S3_SECRET_ACCESS_KEY,
)

def get_file(bucket_name, file_path, download_path, encryption_key):
    print(f"Fetching file s3://{bucket_name}/{file_path} to {download_path}")
    extra_args = None
    if encryption_key:
        print("Using encryption")
        extra_args = {
            "SSECustomerAlgorithm": "AES256",
            "SSECustomerKey": encryption_key,
        }
    client.download_file(
        Bucket=bucket_name, Key=file_path, Filename=download_path, ExtraArgs=extra_args
    )

    return download_path

def main():
    encryption_key = S3_ENCRYPTION_KEY
    print(f"Encryption key: {encryption_key}")

    downloaded_path = get_file(
        S3_BUCKET_NAME,
        "test.txt",
        "download.txt",
        encryption_key,
    )

if __name__ == "__main__":
    main()

Versions
Python 3.6.7
Botocore 1.12.104
Boto3 1.9.104
Seen on macOS 10.14.3 and on Ubuntu

However, using the invalid key to fetch a file from S3 does not. With the specific cloud provider's S3 I was using, this caused botocore to try to redirect to an invalid AWS region

Can you share the specific error you're getting?
Also, just want to clarify, this error message:
botocore.exceptions.ClientError: An error occurred (InvalidArgument) when calling the PutObject operation: The secret key was invalid for the specified algorithm.

doesn't actually come from botocore (the part about the secret key being invalid).  That's an error that's returned directly from S3 that we're surfacing back to the user.
What happens if you try to fetch an object from the real S3 with an invalid key?  I suspect S3 should return an error message back to you.  It would be helpful to compare the two responses.

The actual error we got from boto was:
EndpointConnectionError: Could not connect to the endpoint URL: "https://s3.de.amazonaws.com/<bucket>/<key>"

from botocore/httpsession.py in send at line 278. There was also the exception from the socket.py and urllib3 indicating a connection. We received these exceptions in Sentry, so we have a bit of context to work with.
That URL was strange because we use a different endpoint, not Amazon's AWS. Since that's not a valid AWS region, the request failed to resolve, but really it also hides the underlying cause. I can't tell what we got from the server with boto (would have to check using the HTTP(S) API).
About halfway through the call stack, I can see in botocore/client.py in _make_api_call (line 648) there's a request_context that is:
{
auth_type: [Filtered],
client_config: <botocore.config.Config object at 0x7fee376d0ac8>,
client_region: 's3-de-central',
has_streaming_input: False,
s3_redirected: True,
signing: {
bucket: '<bucket>',
endpoint: 'https://s3.de.amazonaws.com',
region: 'de'
},
timestamp: '20190228T141818Z'
}

Note that the client_region is set to a value recommended by the provider (although it seems like maybe their actual region ends up being de). I also found it a bit odd that there's no configuration exposed when creating the client to set the URL format to use when s3_redirected ends up being True.

Having queried the S3 endpoint with the same parameters, I got back a 400 Bad Request with:
<?xml version="1.0" encoding="UTF-8"?>
<Error>
    InvalidArgument
    <Message>The secret key was invalid for the specified algorithm.</Message>
    <RequestId>4d0912e0-10df-1996-a9e7-0cc47af2c4a0</RequestId>
    <HostId>H54TdLEE4c6zTao[...]</HostId>
</Error>

The code that sets the s3_redirected I mentioned in my previous comment seems to be in botocore/utils.py, in the redirect_from_error function at line 1087, where it does seem to do special handling for the 400 errors. In that function, it tries to redirect regardless of the actual error message, which is likely what's hiding the validation from us and instead causes a misleading redirect and error.
Potentially also worth noting is the Server in the response header is CloudianS3.

@jerr0328 - Following up on old issue. Are you still facing the issue ? If yes, can you please provide full debug logs ? I would be happy to help. You can enable log by adding boto3.set_stream_logger('') to your code.

@swetashre Thanks for the response! I'm not working on the codebase that had the issue, and we pretty much worked around the issue by adding our own validation to make sure the SSECustomerKey was the correct length before passing to boto3, so we don't get this behavior anymore.

I am closing this issue for now. Please reopen if you have any concerns.


Unable to Install

I've tried on multiple environments now and cannot for the life of me get this setup.
Mac El Capitan
Python 2.7.11
running pip install python-pptx
get the following error
Command "/usr/local/opt/python/bin/python2.7 -u -c "import setuptools, tokenize;__file__='/private/var/folders/z5/6_qdc1895cx53w50lw3md7rr0000gn/T/pip-build-0EWWkZ/lxml/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /var/folders/z5/6_qdc1895cx53w50lw3md7rr0000gn/T/pip-FoEwJX-record/install-record.txt --single-version-externally-managed --compile" failed with error code 1 in /private/var/folders/z5/6_qdc1895cx53w50lw3md7rr0000gn/T/pip-build-0EWWkZ/lxml/
Any idea?

and like that I figured it out...had to install x-code tools first:
xcode-select --install


CAS-332: rework the pool layer

In principle nothing changes, however the creation
of base_bdevs is implicitly done through bdev URI's
and lvols now Impl Share.
One new feature that has been added is that we can
can now set properties on lvols. This means that when
we create a lvol, and then share it, the fact that it
is shared is persisted on disk. On import the lvols are
automatically shared.

BTW this does not change the existing grpc pool interaction yet, thats can only be done after this PR.


Pod 0.9.4

Update J2ObjC cocoapods spec to 0.9.4.

Looks like we need 0.9.6 version. Why Google does not support cocoapods in official repo?


Create the service if it does not already exist

Only supports REPLICA service types and doesn't support any other options (i.e. Load Balancers)

Thanks @patrobinson! I just merged #26 but it looks like this now conflicts?

@toolmantim merged and tests pass

Thanks @patrobinson!


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.8",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=148c816f10fd11df27ca6a9b3238cdd42fa72cd3"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "148c816f10fd11df27ca6a9b3238cdd42fa72cd3",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "nfsd: fix use-after-free due to delegation race\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.8 by commit 148c816f10fd11df27ca6a9b3238cdd42fa72cd3. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002600


[Event Request] T77 "Report Selections" - procedure SaveReportAsHTML()

local procedure SaveReportAsHTML(ReportID: Integer; RecordVariant: Variant; LayoutCode: Code[20]; ReportUsage: Enum "Report Selection Usage") FilePath: Text[250]
var
    IsHandled: Boolean;
begin
    ReportLayoutSelection.SetTempLayoutSelected(LayoutCode);

    ----------------------- ADD EVENT ----------------------
    IsHandled := false;
    OnBeforeSaveAsHTML(ReportID, FilePath, RecordVariant, IsHandled)
    if not IsHandled then
       REPORT.SaveAsHtml(ReportID, FilePath, RecordVariant);
    ----------------------------------------------------------

    ReportLayoutSelection.SetTempLayoutSelected('');

....................
[IntegrationEvent(false, false)]
local procedure OnBeforeSaveAsHTML(var ReportID: Integer; var RecordVariant: Variant; var FilePath: Text[250]; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Possibility to enable inheritAttrs

I would like to know if it's possible to enable this feature because in my use case, I perform some validations on events when entering and exiting the field (focus/blur/click). Since attribute inheritance is disabled and there are no listener declarations in the component, I am unable to use this component.
Note: I am migrating the application from Vue 2 to Vue 3.

It is handled here: https://github.com/jonathanpmartins/v-money3/blob/ad029f9f838d7f8521daa772ac8a670adad22130/src/component.vue#L4
And here: https://github.com/jonathanpmartins/v-money3/blob/ad029f9f838d7f8521daa772ac8a670adad22130/src/component.vue#L202-L211
Everything that you put into the component should be pass down to the input element.
Your (focus/blus/click) events should work fine.
Did you face a problem with your migration?

It is handled here: https://github.com/jonathanpmartins/v-money3/blob/ad029f9f838d7f8521daa772ac8a670adad22130/src/component.vue#L4
And here: https://github.com/jonathanpmartins/v-money3/blob/ad029f9f838d7f8521daa772ac8a670adad22130/src/component.vue#L202-L211
All properties you include in the component should be passed down to the input element. Your focus, blur, or click events should function properly.
Have you encountered any issues during your migration?


Discord link is invalid 🤦♂

somebody forgot to make it not expire :/

Discord link is working here just fine https://discord.geckolib.com

But I don't mcraptor users to have much brain power


[Feature] Image pipeline mutator

Works similarly to the REPLACE mutator, but instead of a noise function, it would accept an image, working the same as the IMAGE biome provider.

I feel like this would be better as a source rather than a mutator.

Implemented as a source  via the pipeline-image addon https://terra.polydev.org/config/documentation/image/pipeline-image-source.html


Enterprise Enrollement failed (Failed to determine device ID)

Hi,
I trying to enroll my Raspberry Pi4, but i'm getting "Oops! The system failed to determine device identifiers for this device." I tries to play with write-machine-info, but without success. Any idea?
Thanks

It's a feature that we have not implemented

We will need AirWatch/Intelligent hub/MDM Agent if this is to be used in NAC (Network Access Control) environments.

with the added vpd support, Google Enterprise Enrollment should work.


[5.1] [FileManager] Revert r347205 to avoid PCH file-descriptor leak.

Cherry-pick of https://reviews.llvm.org/D57165 (from January!) to fix a file descriptor leak. See there for details.
rdar://problem/49785385

@swift-ci Please smoke test

Explanation: A change in open-source LLVM to fix a bug where opening file descriptors wouldn't be cached ended up creating a bug where file descriptors wouldn't be closed, which is much worse. This change reverts that original fix, and has been in open-source LLVM since January.
Scope: Affects many uses of Clang's FileManager.
Risk: Low: public LLVM has been living on this, and the revert brings us back to the behavior in Swift 5.0.
Testing: The revert includes a new regression test, and I also verified that this fixes the issue with a precompiled bridging header in rdar://problem/49785385.
Reviewer: Originally reviewed by Nico Weber.

@swift-ci Please test

@swift-ci test

@swift-ci test


nydus-image: fix inspect to get correct path of rafs v6 file

A similar patch for stable/v2.1 does not work for the master branch now. Therefore, we need to update it.
Moreover, improve the performance for getting rafs v6 files path. This operation just impacts nydus-image inspect icheck and nydus-image inspect prefetch.

This PR is related to https://github.com/dragonflyoss/image-service/pull/785
Signed-off-by: Bin Tang<EMAIL_ADDRESS>

cc @changweige

Could you please also fix
Inspecting Rafs :> stat VNADRRYHWrWTZkBFycuxUIi.regular
[2022-11-01 16:50:26.989735 +08:00] ERROR [error/src/error.rs:22] Error:
	"can't get extended inode for 1941"
	at rafs/src/metadata/direct_v6.rs:359
	note: enable `RUST_BACKTRACE=1` env to display a backtraceInspecting Rafs :> stat VNADRRYHWrWTZkBFycuxUIi.regular

Fixed. PTAL @changweige


Bump to 0.36.0

r? @dwijnand
(rust_highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 1a0430fd88f71fe8d2069519c3839eff709f47a0 has been approved by dwijnand

:hourglass: Testing commit 1a0430fd88f71fe8d2069519c3839eff709f47a0 with merge 0d2aac707979021dcfc8c304bd21b0012cddbde9...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: dwijnand
Pushing 0d2aac707979021dcfc8c304bd21b0012cddbde9 to master...


Fix jenkins cobertura coverage

This may be a legitimate failure. If nothing else, it should prompt a change to the error handling.
  12) JenkinsCoverage
       cobertura: valid coverage

	[ GET /c/https/updates.jenkins-ci.org/job/hello-project/job/master.json ]:

      AssertionError: expected { Object (name, value) } to deeply equal { name: 'coverage', value: '64%' }
      + expected - actual

       {
         "name": "coverage"
      -  "value": "invalid response data"
      +  "value": "64%"
       }

      at Object.pathMatch.matchJSON (node_modules/icedfrisby/lib/pathMatch.js:138:38)
      at _expect (node_modules/icedfrisby/lib/icedfrisby.js:583:10)
      at IcedFrisbyNock._invokeExpects (node_modules/icedfrisby/lib/icedfrisby.js:1261:26)
      at start (node_modules/icedfrisby/lib/icedfrisby.js:1244:12)
      at Request.runCallback [as _callback] (node_modules/icedfrisby/lib/icedfrisby.js:1131:16)
      at Request.self.callback (node_modules/request/request.js:185:22)
      at Request.<anonymous> (node_modules/request/request.js:1161:10)
      at IncomingMessage.<anonymous> (node_modules/request/request.js:1083:12)
      at endReadableNT (_stream_readable.js:1064:12)
      at _combinedTickCallback (internal/process/next_tick.js:139:11)
      at process._tickDomainCallback (internal/process/next_tick.js:219:9)

  13) JenkinsCoverage
       cobertura: valid coverage (badge URL without leading /job after Jenkins host)

	[ GET /c/https/updates.jenkins-ci.org/hello-project/job/master.json ]:

      AssertionError: expected { Object (name, value) } to deeply equal { name: 'coverage', value: '64%' }
      + expected - actual

       {
         "name": "coverage"
      -  "value": "invalid response data"
      +  "value": "64%"
       }

      at Object.pathMatch.matchJSON (node_modules/icedfrisby/lib/pathMatch.js:138:38)
      at _expect (node_modules/icedfrisby/lib/icedfrisby.js:583:10)
      at IcedFrisbyNock._invokeExpects (node_modules/icedfrisby/lib/icedfrisby.js:1261:26)
      at start (node_modules/icedfrisby/lib/icedfrisby.js:1244:12)
      at Request.runCallback [as _callback] (node_modules/icedfrisby/lib/icedfrisby.js:1131:16)
      at Request.self.callback (node_modules/request/request.js:185:22)
      at Request.<anonymous> (node_modules/request/request.js:1161:10)
      at IncomingMessage.<anonymous> (node_modules/request/request.js:1083:12)
      at endReadableNT (_stream_readable.js:1064:12)
      at _combinedTickCallback (internal/process/next_tick.js:139:11)
      at process._tickDomainCallback (internal/process/next_tick.js:219:9)

Ref: #1359

So one thing I've found is that if I remove the Conditionals coverage object from the elements array in the mocked reply object that these two tests will start passing again.
I.e. the current response fails
.reply(200, {
  results: {
    elements: [
      {
        name: 'Conditionals',
        ratio: 95.146,
      },
      {
        name: 'Lines',
        ratio: 63.745,
      },
    ],
  },
})

but the same response object with just the one Lines object in elements will pass:
.reply(200, {
  results: {
    elements: [
      {
        name: 'Lines',
        ratio: 63.745,
      },
    ],
  },
})

When I hit a live instance of the API I get the following JSON response with various objects in the elements array:
{
   "_class":"hudson.plugins.cobertura.targets.CoverageResult",
   "results":{
      "elements":[
         {
            "name":"Packages",
            "ratio":92.47312
         },
         {
            "name":"Files",
            "ratio":90.55556
         },
         {
            "name":"Classes",
            "ratio":90.94693
         },
         {
            "name":"Methods",
            "ratio":77.76264
         },
         {
            "name":"Lines",
            "ratio":74.3159
         },
         {
            "name":"Conditionals",
            "ratio":65.21124
         }
      ]
   }
}

And i also see that the joi schema for the cobertura response here has name: 'Lines'. I don't have a ton of experience with joi, so should that line filter the objects in elements to exclude those with a name other than Lines? Or does that schema expect the name for each object to be Lines?

Ooh, thanks for looking into this!
I see. Yea, array.items() wants each item to match the schema.
I think the thing to do is change that name: 'Lines' to name: Joi.string().required(). We could chain on an array.has(schema) to make sure name: 'Lines' for one of the elements.
Then we can filter the results in the handler.

That's what I was thinking as well. I'll happily take this one and implement that change

I didn't want to open a new issue for this (yet) but as an FYI..
The live test I added failed in the most recent daily build but i'm positive this was simply due to the test taking longer than the mocha timeout period of 5 seconds. I've seen this a couple times when I run the test locally where it occasionally takes 5-7 seconds.
I'll try to keep an eye on this test and if it keeps intermittently failing I can try to find a different live jenkins endpoint that will hopefully respond more quickly, unless there's a possibility of increasing the mocha timeout period for the service tests in the daily build? I think this particular test would be fine as is with a timeout period of 7500ms vs. the current 5000ms
(5) JenkinsCoverage
       cobertura: job found

	[ GET /c/https/builds.apache.org/job/olingo-odata4-cobertura.json ]:
     Error: Request timed out after 5000 ms
      at Timeout.handleRequestTimeout [as _onTimeout] (node_modules/icedfrisby/lib/icedfrisby.js:1098:35)

@calebcartwright you can increase the timeout on a per test basis. Simply add .timeout(10000) as we do in the F-Droid service for example.

Excellent! Semi-random question for you all.. do you care if I add on a change like this to a different, but existing, PR I already have open (say #2477 ), or do you prefer separate PRs for different changes?

I would recommend opening a new PR, as the currently opened one is for an unrelated service. 😉

Gotcha, thanks @PyvesB!


Can't get the "RenderPlayerInfo" when play audible(always) and kindleBook(click in alexa.amazon.com)

Briefly summarize your issue:
Can't get the "RenderPlayerInfo" when play audible(always) and kindleBook(click in alexa.amazon.com).
But always ok when play Amazon Music.
click-on-alexa.amazon.com-kindlebook.log
wakeup-audible.log
What is the expected behavior?
Can't get the "RenderPlayerInfo"
Tell us about your environment:
What version of the AVS Device SDK are you using?
  <1.7.1>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[x] Raspberry Pi
[] Other - tell us more:

Tell us about your OS (Type & version):

[x] Linux
[ ] MacOS
[x] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @leino11121,
Display cards are only supported for music currently. They aren't supported for Audible and KindleBooks.
Thanks,
Sanjay

Hi @leino11121,
Display cards are only supported for music currently. Audible and KindleBooks don't have this feature.
Thanks,
Sanjay

Thanks @sanjayrd .
I will close this issue.
Leon


✨  [experimental] Add probe code and support for Tool-Update-Dependency

This PR:

adds the probes directory where we will implement the probes.
Proves an implementation and definition files for the Tool-Update-Dependencies check

Reminder to myself: update the unit tests.
Ina a follow-up PR, I will add support for displaying these results with the --format finding and --format probe.
Add probe code and support for Tool-Update-Dependency

friendly ping for re-review :-)

I think it's fine to have a utils folder, but not necessarily the package name. Would a updatetools packagename work? Would let us de-dup some names

This folder is used by all checks that check for a tool, it's not specific to dependency tools. Any better name?

I understand the benefit, but it seems like it adds unnecessary confusion (at least for me). Especially when you rename it elsewhere

I've removed the prunner part. Can you suggest something you're prefer to remove the confusion? Maybe explain what you mean by confusion and I may be able to think more about it. I created https://github.com/ossf/scorecard/issues/3047 for the time being.


Non dimensionalize convection miniapp

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Additional details and impacted files

:loudspeaker: Thoughts on this report? Let us know!


Same file opened multiple times

If you click a file in the File Explorer that's already opened it will open the file again in a new editor tab.  Would be better to check if the file is already open and if it is then bring that editor and tab into focus.

fixed, the bugfix will be on the next release.


getWeekofYear() function starts week on Tuesdays instead of Monday

May make sense to replace that function with the following simpler one:
function getWeekOfYear(date) {
    date = new Date(Date.UTC(date.getFullYear(), date.getMonth(), date.getDate()));
    date.setUTCDate(date.getUTCDate() + 4 - (date.getUTCDay()||7));
    var yearStart = new Date(Date.UTC(date.getUTCFullYear(),0,1));
    var weekNo = Math.ceil(( ( (date - yearStart) / 86400000) + 1)/7);
    return [weekNo];
}

https://github.com/thesved/ViktoRoam/blob/d90eae7814c359976b954ca0ed5d6e5d684136f1/js/dateformatter.js
You can just replace lines 353 to 375 with the above.

Thank you @abhayprasanna, updated the code!


Create react app dependency error

When i try to create a new react application using create-react-app, it tries to download fsevents but fails ,also gives  Error: Can't find Python executable "python" and Error: Failed to execute 'node-gyp.cmd configure errors. I have attached the screenshot. Thank you in advance.

same error in the instalation it gives me:
warning<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check.
I have been trying to debug this all morning. Only just started happening to me. NPM version is 5.0.3
Can somebody please find a solution.

fsevents should only be installed on osx. I think it's a bug with npm@5 https://github.com/mapbox/node-pre-gyp/issues/298
can you all try with npm 4 / use the proposed workaround (deleting and disabling package-lock)?

I have a feeling the recently merged #2550 will solve this in the next release.

Can someone please try downgrading to Node 6 or 7 to see if this persists for them?

I think this issue is related to Webpack, when I tried to create my own boilerplate without using create-react-app, the issue appears when I tried to add Webpack

I have the same problem, enviroment win7 64bit, create-react-app version : 1.3.1.  what ?

I have same problem.

node 8.1.2
npm 5.0.3
create-react-app 1.3.1

I downgrade to node 6.11.0 and npm 4.6 but the issue still there

+1。and i install react-router, then the issue still there

cc @thelarkinn, any ideas what happened? We didn't change anything on our side.

Same issue for me.

node v6.11.0
npm 5.0.3
create-react-app 1.3.1
windows 10

The exact error it gives me after running yarn start is:
yarn start v0.24.5
$ react-scripts start
module.js:471
    throw err;
    ^

Error: Cannot find module 'iconv-lite'
    at Function.Module._resolveFilename (module.js:469:15)
    at Function.Module._load (module.js:417:25)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\amnai\Desktop\react-tutorials\test\node_modules\external-editor\main\index.js:23:15)
    at Object.<anonymous> (C:\Users\amnai\Desktop\react-tutorials\test\node_modules\external-editor\main\index.js:218:4)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
error Command failed with exit code 1.

Try:

Removing package-lock.json if you have one
Removing yarn.lock if you have one
Downgrading npm to 3.x if it's newer
Run npm install
Then run npm start

Does this help anyone?

@gaearon are you suggesting that just to diagnose the issue?  Because I think it would be inconvenient to be forced to use an old npm...

Changing npm version takes a few minutes in my experience. npm@5 is known to have a lot of bugs, and I want to figure out if at least some cases are caused by npm@5 or not.

I just tried with npm@5 and I saw the error noise (although eventually the installation finished successfully for me). In the meantime I recommend downgrading: npm i -g npm@4.

I'm fairly sure it is this npm bug: https://github.com/npm/npm/issues/16810.
Unfortunately there's nothing we can do until it's fixed.
If you're having this issue please roll back npm to a version without this bug: npm install -g npm@4.
If you still have a problem after downgrading npm please file a new issue with screenshots and details about your system.

npm install -g npm@4 it works, thanks very much

I've managed to make it work with the following setup:
node - v6.10.0
npm - v5.0.4
react-scripts - 1.0.10
os - win10
After the update to 1.0.10 I've also updated the react and react-dom versions to v15.6.1, deleted the node_modules and re-installed the dependencies and then everything started working as it should be.
Hope this helps.

For me this worked:

delete package-lock.json
npm i -g npm
npm install


Can you make BSD license

This is very good code. Code you change it to BSD rather than GPL?

No problem.

done


Surface the right Name() from our principal.

Summary
The cosign logic for interacting with Fulcio treats identity tokens as largely opaque, and most of the logic for how issuers and subjects and whatnot is handled happens server-side.  However, for the "proof of possession" cosign has some logic (from sigstore/sigstore) that fumbles with email and sub claims in ways that have (until now) been compatible with Fulcio principals.
The Chainguard provider is the first provider that optionally includes an email claim, but we always want the subject we use to be our opaque identifier string (from sub).  This creates a tear in the fulcio/cosign continuum, and so we must surface what cosign is signing as Name() even though that isn't necessarily what we embed in the certificate.
The only correct way to implement Name() today is to match what this function does, and current implementations happen to align, but unfortunately because of how this abstraction is formulated it is challenging to actually change how we confirm the proof of possession to use this directly in place of the principal itself.
Fixes: https://github.com/sigstore/cosign/issues/3777
Release Note
This corrects the Chainguard PoP verification flow for tokens that embed email claims (makes Name() consistent with cosign).
Documentation
N/A

whoops, amended with my test file

I'll cut 1.5.1 with this fix. I'm going to need to revert a PR that when in recently first, as a cherry-picked release is a bit of a pain.


[Beta] Fix layout shift from previews

This should fix the layout shift from previews on layouts where we overflow to the "vertically stacked" code / preview blocks.  In this case we don't know the preview height, so we're going to always render 40% of the viewport. This is not ideal but it's better than jumpy unpredictable scroll.

Hmm. Looks like long sandboxes like in Thinking in React now get expanded in mobile mode. Need to fix this somehow.

Still seems a bit wrong because on desktop we don't want vertical resize to "squeeze" the sandbox. We probably need to somehow make the vh max-height conditional on the media breakpoint.

Are you looking for this https://github.com/reactjs/reactjs.org/blob/52393daffe7baec8af53bc2359d74077ddd1e2bb/beta/src/components/Layout/useMediaQuery.tsx#L7 ? 👀

I'd prefer if we did this in CSS without any JS code to track the media query.

So I think we just need to turn these styles into tailwind classes.

I don't think SandpackCodeEditor accepts a className, but maybe we could put it in a div and style that.

If you wanna give it a go, feel free to :)

This change adds scroll for larger previews. I hope that should be fine 😄

In smaller previews we have too much of empty space (bigger than the code area)? Is this okay? Or shall we rather arrange the output in the center?

This change adds scroll for larger previews.

Yeah, that's the tradeoff. One thing we could do is just to tweak the code examples to assume they need to fill in a bit more space.

Or shall we rather arrange the output in the center?

I'd be curious to see how this looks, if you wanna try! Not sure it'll work.


Citing GBIF data

Hi,
Can't remember if we've been in touch about this before, but I wondered if you have an idea of how to improve the way users of the plugin cite GBIF-mediated data?
I've tried adding some instructions to our QGIS page, but I wonder if it could also be made more clear directly in the plugin?
Thanks!

That's a very good idea. My problem is the same as for the other GitHub issues: I don't know when I'll have time to work on this (this plugin started as a tiny side project when I was working for the Belgian Biodiversity Platform. I'm very surprised and grateful it is still used. If anyone wants to tackle that, you're very welcome).

The plugin is written in Python, right?
I wonder if @manongros might have time to help


time_event function

Hi,
I am using mixpanel in Electron application on Windows.
I want to implement session duration tracking using following help page#Javascript as reference.
It suggests to use time_event function but it does not exist in nodejs module.
Searching around the web and this issue tracker the only thing I came with is to use time.
I tried to use timeproperty on application close event:
    tracker.track('Application Closed', {
        "distinct_id": machine_id,
        "release": `${os.type()} ${os.release()}`,
        "source": "desktop app",
        "time": moment.utc().toISOString()
    }, app.quit);

But I got this:

Is there workaround to track session length, rather then calculating itself in application?
Thanks

Even if you added a timestamp correctly in your time field, that would give you the current time, not your session duration. Although time_event hasn't been implemented in the node lib, it's pretty easy to add a one-off for your application:
// session begins: this is where you would call time_event() in another lib
const sessionStartTime = new Date().getTime();

// then when the user quits
tracker.track('Application Closed', {
  "distinct_id": machine_id,
  "release": `${os.type()} ${os.release()}`,
  "source": "desktop app",
  "Duration": new Date().getTime() - sessionStartTime,
}, app.quit);

If you have more implementation questions, I'd suggest contacting<EMAIL_ADDRESS>they'll be quite happy to go over your code with you and work through the details.


[#63] Fix @With interceptors in Java

Fixes #63: it allows to compose actions using the @With annotation as explained in the documentation

Thanks so much for the fix Julien!
If you still have more time to work on interceptors a far more annoying interceptor bug is that you can't place the interception annotations on a parent class:
https://play.lighthouseapp.com/projects/82401/tickets/65-composing-actions-does-not-work-with-inheritance

@benmccann see my comment in the ticket discussion (on lighthouse)

Thanks Julien.  I responded on the ticket.  (btw, feel free to close issue #63 now that this fix has been committed)


number/integer without format should use BigDecimal/BigInteger

Without format information, the potential numbers used may exceed the limits for the Java primitive or wrapper types.

Given the fact that there is no default defined this is correct, ref.


cmd/go: no way to omit package information from binary

What version of Go are you using (go version)?

go version go1.17.5 linux/amd64

Does this issue reproduce with the latest release?
After compiling and striping a binary it still has inside package information like:

Full system paths of packages.
Package versions.
Data structure information.

What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/d3ni/.cache/go-build"
GOENV="/home/d3ni/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/d3ni/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/d3ni/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.5"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/d3ni/go/src/github.com/denimyftiu/lilurl/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build258303585=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.17.5 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.17.5
uname -sr: Linux 5.10.0-1053-oem
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.3 LTS
Release:	20.04
Codename:	focal
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Ubuntu GLIBC 2.31-0ubuntu9.2) stable release version 2.31.
gdb --version: GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2

What did you do?

I tried to compile https://github.com/denimyftiu/lilurl .
Command: go build -ldflags="-w -s" ./cmd/shortner.
The binary functions fine but still has some information that i might not want inside it. And could lead to later problems if it falls into the wrong hands.
When i run strings shortner i can read the following strings left inside the binary:

// Go modules compiled inside the binary
github.com/jackc/pgconn
github.com/jackc/pgtype
github.com/jackc/pgx/v4
github.com/jackc/puddle
golang.org/x/text/cases
golang.org/x/text/runes
golang.org/x/text/width

// My github repo which might be a problem if my repo is private (maybe a problem)
github.com/denimyftiu/lilurl/pkg/config

// And all my go.mod info
path    github.com/denimyftiu/lilurl/cmd/shortner
mod github.com/denimyftiu/lilurl    (devel)
dep github.com/cespare/xxhash/v2    v2.1.2  h1:YRXhKfTDauu4ajMg1TPgFO5jnlC2HCbmLXMcTG5cbYE=
dep github.com/dgryski/go-rendezvous    v0.0.0-20200823014737-9f7001d12a5f  h1:lO4WD4F/rVNCu3HqELle0jiPLLBs70cWOduZpkS1E78=
dep github.com/go-redis/redis/v8    v8.11.4 h1:kHoYkfZP6+pe04aFTnhDH6GDROa5yJdHJVNxV3F46Tg=
dep github.com/gorilla/mux  v1.8.0  h1:i40aqfkR1h2SlN9hojwV5ZA91wcXFOvkdNIeFDP5koI=
dep github.com/jackc/chunkreader/v2 v2.0.1  h1:i+RDz65UE+mmpjTfyz0MoVTnzeYxroil2G82ki7MGG8=
dep github.com/jackc/pgconn v1.10.1 h1:DzdIHIjG1AxGwoEEqS+mGsURyjt4enSmqzACXvVzOT8=
dep github.com/jackc/pgio   v1.0.0  h1:g12B9UwVnzGhueNavwioyEEpAmqMe1E/BN9ES+8ovkE=
dep github.com/jackc/pgpassfile v1.0.0  h1:/6Hmqy13Ss2zCq62VdNG8tM1wchn8zjSGOBJ6icpsIM=
dep github.com/jackc/pgproto3/v2    v2.2.0  h1:r7JypeP2D3onoQTCxWdTpCtJ4D+qpKr0TxvoyMhZ5ns=
dep github.com/jackc/pgservicefile  v0.0.0-20200714003250-2b9c44734f2b  h1:C8S2+VttkHFdOOCXJe+YGfa4vHYwlt4Zx+IVXQ97jYg=
dep github.com/jackc/pgtype v1.9.1  h1:MJc2s0MFS8C3ok1wQTdQxWuXQcB6+HwAm5x1CzW7mf0=
dep github.com/jackc/pgx/v4 v4.14.1 h1:71oo1KAGI6mXhLiTMn6iDFcp3e7+zon/capWjl2OEFU=
dep github.com/jackc/puddle v1.2.0  h1:DNDKdn/pDrWvDWyT2FYvpZVE81OAhWrjCv19I9n108Q=
dep github.com/teris-io/shortid v0.0.0-20201117134242-e59966efd125  h1:3SNcvBmEPE1YlB1JpVZouslJpI3GBNoiqW7+wb0Rz7w=
dep golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97  h1:/UOmuWzQfxxo9UtlXMwuQU8CMgg1eZXqTRwkSQJWKOI=
dep golang.org/x/text   v0.3.6  h1:aRYxNxv6iGQlyVaZmk6ZgYEDa+Jg18DxebPSrd6bg1M=

All of these are not static/constant strings i have used inside my binary.

What did you expect to see?

I wanted to just have compiled code inside the binary and not additional information.
This information i guess is there for debugging and profiling reasons.
Is there a compiler flag for this??

What did you see instead?

Additional information that i don't want someone else with access to the binary to read.

At least on tip that information does seem to be there even when using -buildinfo=false -buildvcs=false.  Perhaps I'm misunderstanding something, but my reading of #37475 is that there is supposed to be a way to not emit this information.
CC @bcmills @matloob @rsc

I still can not figure out where to position these arguments in the go/build command.

go build -buildinfo=false -buildvcs-false PACKAGE

I don't think -buildinfo=false -buildvcs=false are flags that go build supports.

Mmmm these flags maybe added in go 1.18.

-buildinfo and -buildvcs affects this part (added in 1.18)
	build	-compiler=gc
	build	CGO_ENABLED=1
	build	CGO_CFLAGS=
	build	CGO_CPPFLAGS=
	build	CGO_CXXFLAGS=
	build	CGO_LDFLAGS=
	build	GOARCH=amd64
	build	GOOS=linux
	build	GOAMD64=v1
	build	vcs=git
	build	vcs.revision=7295d66255e394de962154f806066c611c7b9b87
	build	vcs.time=2022-01-04T22:01:22Z
	build	vcs.modified=true

afaik module dependency information can't be stripped.
As a note, requiring the package/module names to not be present in the final executable seems unreasonable as it would break things like reflect and stacktraces.

I understand. Thank you @seankhliao and @ianlancetaylor.

I think the only thing that is a release-blocker here is a decision about whether the new -buildinfo=false flag should also strip module version information.
(Setting -buildinfo=false at tip today gives the same behavior as go1.17.6 without flags, so this is not really a regression so much as a usability/documentation issue for the new flag.)
$ go1.17.6 build -o a.out .

$ go1.17.6 version -m a.out
a.out: go1.17.6
        path    example
        mod     example (devel)

$ gotip build -o a.out -buildinfo=false .

$ gotip version -m a.out
a.out: devel go1.18-11b28e7e9 Fri Jan 7 06:34:04 2022 +0000
        path    example
        mod     example (devel)

I'm inclined to think that there should be some way to tell the go tool to not add all the module info to the binary.  If that is -buildinfo=false, that seems reasonable.
@seankhliao is quite correct in pointing out that the package names are going to remain in the binary in all the cases for stack trace purposes.  But we can at least omit the details of the package versions.

I took a stab at it because it seemed trivial. If that CL is fundamentally flawed, which it might be because I don't really know this part of the codebase, feel free to just disregard it and send a better one.

It sounds like the right answer is to remove the -buildinfo flag.
It is intentional that it is impossible to omit package information from the binary.
It's very small compared to the rest of the binary, and we don't need the long-term complexity of the second mode.
And removing the information makes things like 'go version -m' much less useful.
-buildvcs is different, because that can produce spurious binary differences and can be slow.
That should stay.

It sounds like the right answer is to remove the -buildinfo flag.

I'm not a huge fan of that. From an info leak perspective, sometimes I'd prefer binaries have less information rather than more. Not everybody's use case involves something being built from google3 or whatever. I realize there are other ways of obtaining that info from a given binary, but from some perspectives, the less you have there, the better.
I realize you might not share that perspective though. That's fine. Just thought I'd make record of my "aw shucks" before it's gone for good.

I realize there are other ways of obtaining that info from a given binary, but from some perspectives, the less you have there, the better.

Right, that's the thing: the -buildinfo=false flag suggests that we're omitting information, but that information may well still be present in the binary (for example, embedded in file-and-line debug information). Obfuscating a Go binary for deployment to a hostile environment is a whole other can of worms, and one that we certainly cannot address for Go 1.18.

@denimyftiu I want to be clear that the suggested resolution for this issue is to say that the tools are behaving as expected when they record package names in the binary.

FYI the above CL removed the flag, but it's still mentioned in the release notes.

@zikaeroh Thanks, sent https://go.dev/cl/379314.

My friend was reverseenginierd my binary and steal my real name from path information present in the binary

Trying to pass some secret value with "-ldflags", with go 1.18, it's impossible to avoid someone getting that secret value simply find "ldflags" in an editor with the binary file. For me, it's definitely a regressing.


Add missing documents

Add missing documents and enable missing_docs for:

burn-tensor
burn-ndarray
burn-train
burn-import

I wouldn't add documentation for the internal traits (the ones in burn-tensor/api/ that are used for static dispatch to the right backend function depending on the data type. Maybe just redirect to the right functions to use.
Some minor typos to fix, but otherwise great job.
I think we may update a few methods in future PRs.
index, index_assign => slice, slice_assign. index_select, index_select_assign => select, select_assign. mask_fill, mask_where => mask_fill_elem, mask_fill
Those are just suggestions, but I think they better represent what each function does.

For the name changes I have a ticket: https://github.com/burn-rs/burn/issues/426
Also I have fixed other issues, please take a look when you get a chance.


Update README.md, introduce INSTALL.md

Description

This PR updates updates content in the "Developer documentation" section and introduces INSTALL.md.
This file describes the actions needed, to just run MIW.  Nothing else.
Beside that main purpose of the PR, there are some minor adjustments / fixes, which popped up during the verification of the README.md file.

This PR fixes #150
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

@DominikPinsel @borisrizov-zf @mknoopvw
It would be great, if you could verify the INSTALL.md.

I tested the changes made in order to get started: it worked as described in install.md.


Found only 2 packages

I have about 130 installed apps, the package found me only 2(!)
I checked other flutter package and it found me all of my installed packages.
the device_apps package not found all the packages, please fix it.
Example of packages that can't found:
https://play.google.com/store/apps/details?id=com.alibaba.aliexpresshd
https://play.google.com/store/apps/details?id=com.booking
https://play.google.com/store/apps/details?id=com.yahoo.mobile.client.android.finance
And more..

I am facing the exact same issue. Only two apps are being returned.

Could you give extra information on which device you test?
And with which Android version?
Your bug is similar to a "it doesn't work".


Resize with only target width or height

Summary
I've added the image resize plugin to filepond and am using the ImageResizeTargetWidth-parameter to resize an image, but this value is being used as height-value instead.
How to reproduce

set
allowImageResize: true
imageResizeTargetWidth: 800
imageResizeTargetHeight: null
upload an image, for example with sizes: 1920 x 1200.
the image is saved as 1280 x 800

Expected behaviour
That the image would be saved as 800 x 500

You have to set imageResizeMode to 'contain'
https://pqina.nl/filepond/docs/patterns/plugins/image-resize/

This works to some effect, but not entirely: for a landscape image with a set ImageResizeTargetWidth this works, but if I only set the ImageResizeTargetHeight it doesn't work. For this one to work, I have to set the mode to cover.
I guess this has to do with the resize plugin using the ImageResizeTargetWidth value if ImageResizeTargetHeight is not set, so for now I've fixed this by manually multiplying the ImageResizeTargetWidth value by 2 and using that as the ImageResizeTargetHeight if it is not provided, and vice versa.

This solves it in some cases, but not always: when I set the imageResizeTargetHeight and no imageResizeTargetWidth has been set, according to the documentation the height-value is used for the width as well. When uploading an image with a landscape ratio, this results in an image that has the height-value as its width.
For now I've solved this by checking if I have only a width set, then multiply that value by 2 to use as the height-value, and vice versa.


Add uid/gid fields

These seem useful

(Sorry for taking so long to merge this, I've been a little busy.)


feat: Update script and SDK to support Token 2022 transaction data

Checklist:

README.md includes:

[ ] The details of signing data and transaction data, this includes parameters.
[ ] Official docs or white paper.
[ ] Website or api can query assets and broadcast transaction.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Task linked: CW-20220 SDK 發送 2022 Token 簽章不會上鏈


[themes] theme names are all not localized

VSCode Version: 1.50.1

Steps to Reproduce:

Install VScode and Language Extension Chinese(Simplified)
Set the Display Language to "zh-cn" and restart VScode
Input "theme" in command palette and observe the theme name

Expected:
Theme name are all localized
Actual:
Theme name are all not localized
(Repro on Windows, Linux and Mac)

Does this issue occur when all extensions are disabled?: Yes

The labels of the themes now can be translated. It will be up to the translation team to decide how and whether to use a translated name.
Note: the settings id will remain the same as to not break any users with existing settings.


tail -F /dev/random

Hi *,
Running a "onboard" operation with "productsecurity" profile.
It became slower and slower and I detected the following command running 100% of the CPU (and up for 32 hours!):
tail -F /dev/random
The parent process is:
/usr/bin/containerd-shim-runc-v2 -namespace moby -id 8da7d4f4215c919e01e68abffa7079c73839e0136961bd1aadb00b6ba23fcaaf -address /run/containerd/containerd.sock
Any idea how to fix this?
The server is a freshly installed Ubuntu 22.04 LTS

The usage of tail -F /dev/random was a hack-ish way to keep the Mantis container from exiting. Will fix this more gracefully.
However, I don't think this command would cause the CPU usage spike. Have you been running Mantis scans during this time? Mantis scans tend to be CPU intensive and could have been the cause for the spike.

Ok, I understand the purpose of this command. I see now that one of my CPUs is at 100% and no scan is running. This is not super critical but it hurts me to see so many CPU cycles for nothing :-)

I got the issue the tail command cause busy waiting. So it's better to use sleep command to keep container alive. While debugging this issue i found another small issue with Dockerfile of dashboard for which build process was failing for me. So I also fixed the update command under that file

PR Link - https://github.com/PhonePe/mantis/pull/18

Thanks for the PR. This is merged.


Some CTE statement is parse wrongly

Bug Report
Please answer these questions before submitting your issue. Thanks!

What did you do?
If possible, provide a recipe for reproducing the error.

with cte as (select 1) select 1 union with cte as (select 1) select * from cte;
with cte as (select 1) (select 1);
with cte as (select 1) (select 1 union select 1);
select * from (with cte as (select 1) select 1 union select 2) qn;
select * from t where 1 > (with cte as (select 2) select * from cte);
( with cte(n) as ( select 1 ) select n+1 from cte union select n+2 from cte) union select 1;
( with cte(n) as ( select 1 ) select n+1 from cte) union select 1;
( with cte(n) as ( select 1 ) (select n+1 from cte)) union select 1;

What did you expect to see?

The same as MySQL

What did you see instead?
Inconsistent with MySQL

What version of TiDB SQL Parser are you using?

master

subtask of  https://github.com/pingcap/tidb/issues/17472


Move to Conan-based developer workflow.

If should be possible to do everything via CMake but it should also be possible to do everything via Conan more easily.

Add a job which tests CNL as described in #594 and then installs it on the system.
Move all other jobs over to using Conan commands such as conan build to configure, build and test CNL.
Update the README accordingly.

Completed in #590


Clear form fields/widgets data with button.

Prerequisites

[x] I have read the documentation;
[x] In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.

Description
Is there a clear button for each fields that we can use to clear for forms fields?
I am looking for a button on each field/widget that would either reset the field or set it to default.
Any help would be appreciated.

No, there currently isn't. You could make a custom widget for it though.


Question:  Ambiguous alternatives

Hi,
I'm still at my grammar for relational algebra. :)
This time, I've got a problem with ambiguous alternatives.
I have two rules:
$.RULE('joinClause', () => {
      $.SUBRULE($.tableExpression, { LABEL: 'lhs' })
      $.SUBRULE($.joinOperator)
      $.SUBRULE1($.tableExpression, { LABEL: 'rhs' })
    })

and
$.RULE('tableExpression', () => {
      $.OR([
        { ALT: () => $.CONSUME(Identifier, { LABEL: 'tableName' }) }
      , { ALT: () => $.SUBRULE($.renameClause) }
      ])
    })

But when I try to combine them in one rule, I got the error message of ambiguous alternatives. As in the docs described, I put the longer rule at the beginning, but still get this error.
$.RULE('raStatement', () => {
      $.OR([
        { ALT: () => $.SUBRULE($.projectionClause) }
      , { ALT: () => $.SUBRULE($.selectionClause) }
      , { ALT: () => $.SUBRULE($.joinClause) }
      , { ALT: () => $.SUBRULE($.tableExpression) }
      ])
    })

Do you have any recommendations? Thanks!

how does "renameClause" look like?

Hi,
thank you for your quick response. The renameClause looks like this:
$.RULE('renameClause', () => {
      $.CONSUME(Rename)
      $.CONSUME(Identifier, { LABEL: 'tableAlias' })
      $.SUBRULE($.tableExpression)
    })

O.k. I think I understand.

$.RULE('raStatement', () => {
$.OR([
{ ALT: () => $.SUBRULE($.projectionClause) }
, { ALT: () => $.SUBRULE($.selectionClause) }
, { ALT: () => $.SUBRULE($.joinClause) }
, { ALT: () => $.SUBRULE($.tableExpression) }
])
})

Alternatives 3 & 4 both start with tableExpression.
To distinguish between these alternatives we need to "lookahead" until we find the "joinOperator" token.
but because a tableExpression may be of infinite length we cannot look ahead enough
fixed number of tokens to make this distinction.
This normally means we need to refactor the grammar so it would be LL(K)
This is normally done by extracting the common infinite length prefix.
in your case you could try to combine alternatives 3 and 4 so
the join clause is a possible optional suffix of the combined production.

Thank you very much for your suggestion and advice. I (think I) solved the problem, by neutralization the infinite loop.
In the renameClause I introduced an new rule atomicTableExpression, which is a terminal symbol. A chaining is no more possible.
$.RULE('renameClause', () => {
      $.CONSUME(Rename)
      $.CONSUME(Identifier, { LABEL: 'tableAlias' })
      $.SUBRULE($.atomicTableExpression)
    })

Not totally sure if this is confirm with the definition of relational algebra, but I'm confinced this is more an academically problem. Ironically its exactly the case. :D
This work is for an application for my university. With this application the students will be able to practice relational algebra. In the following action part, the relational algebra statements will be transformed in SQL statements, which will be executed on a normal postgres database.
If you want to see your technology in action, I will leave you a link to the final application. ;)

In the tableExpression I introduced a new rule atomicTableExpression, which acts as a terminal symbol. A chaining is no more possible.

That is one way to solve the problem.
Note that binary expressions have infinite chaining, but they can still be modeled as an LL(K) grammar.
Also note that it is possible to use backtracking to resolve such ambiguities but that normally not recommended.

https://sap.github.io/chevrotain/docs/features/backtracking.html

If you want to see your technology in action, I will leave you a link to the final application. ;)

Sure 👍

I understood your case would generate this kind of message.  But when I looked at mine, it didn't feature two potentially empty alternative.  Instead, my first rule has several optional patterns in the first rule before finally consuming a token while the second rule had an immediate token consume rule.  Because the possible first tokens for the first rule are mutually exclusive from the mandatory first token in the second rule.  So it appears that you take the next token and if it matches the token of the second rule, use that.  If it doesn't, it must be the first rule.
However, that clearly isn't how the parser works.  Fortunately, the solution was simple...I just reversed the two alternatives.  With the first rule starting unconditionally with a specific token, the ambiguity goes away.  I know that in the case of common prefixes order matters (longer potential match first).  But I didn't think order would matter in this case.  It might be useful to put a note in the error message about this.


Problem with array#sequence type when upgrading fp-ts to 2.8.2

I got a monorepo where we use fp-ts on almost every package.
When upgrading to version 2.8.2 (from version 2.6.2), I got a problem in two of my packages involving array#sequence.
Instead of getting this:
pipe(
    tuples.map(saveThread),
    x => x, // TaskEither<CustomError, RequisitionFileThread>[]
    array.sequence(taskEither),
    x => x, // TaskEither<CustomError, RequisitionFileThread[]>
    map(threads =>
      threads.map((thread, i) => {
        const tuple = tuples[i];
        const [_, file] = tuple;

        return [thread, file] as const;
      })
    )
  )

I'm getting this:
pipe(
    tuples.map(saveThread),
    x => x, // TaskEither<CustomError, RequisitionFileThread>[]
    array.sequence(taskEither),
    x => x, // TaskEither<unknown, any>
    map(threads =>
      threads.map((thread, i) => {
        const tuple = tuples[i];
        const [_, file] = tuple;

        return [thread, file] as const;
      })
    )
  )

The code worked properly in version 2.6.2.
Erros like that popped with other types as well, like Either.
Strangest thing, I use array#sequence in other places (but not in the packages I got those errors) and it seems to work as expected. At first, I thought it was something with typescript or the tsconfig files, but I updated the first and the error was not solved. Looking into my tsconfig files, I found nothing that could cause such.
Anyone has experienced something similar, or know a path to solve this?

I suspect for this to gain traction you'll want to provide a small repro.


Nasty hack to support bundle resource files for XCode

Todo: find a way to do this in the CMake include file which would allow removing these special cases for xcassets and bundle files

:see_no_evil:

Ah, that's a bit neater. Still makes my eyes burn though.

Nice, does that delete the rest of the tree in place?

del dires[:] removes all items from the dires list, which prevents os.walk from recursing into any subdirectories of the current root directory.


Consider supporting Windows

Windows lovers use neovim too =).

Closed duplicate.  Found out that it is not possible ( per another issue ).  So sad.  Guess I'll have to wait for support in neovim.

I have so little Windows knowledge that even having a Win VM around doesn't help me much.
I'd welcome any patches, though! I mean, the code that forks nvim from nvr is probably totally different on Windows, but supporting --remote and friends shouldn't be too hard and would still be a big win.


[add] job specs

Coverage decreased (-10.1%) to 64.391% when pulling a4147fe664d5d9a0edf330358e9c5d4ada3b87bb on tany:dev into 37f38db607115ef348021cc20b7d4b6db7ef9580 on shirasagi:master.

Coverage decreased (-10.1%) to 64.391% when pulling a4147fe664d5d9a0edf330358e9c5d4ada3b87bb on tany:dev into 37f38db607115ef348021cc20b7d4b6db7ef9580 on shirasagi:master.


Uncaught TypeError: undefined is not a function

Uncaught TypeError: undefined is not a function
Atom Version: 0.156.0
System: Mac OS X 10.10.2
Thrown From: github-issues package, v0.2.0
Steps To Reproduce
Just opened from command pane.
Stack Trace
At /Users/yg/.atom/packages/github-issues/GitIssueView.coffee:17

TypeError: undefined is not a function
  at new GitIssueView (/Users/yg/.atom/packages/github-issues/GitIssueView.coffee:17:8)
  at /Users/yg/.atom/packages/github-issues/index.coffee:51:13
  at Workspace.module.exports.Workspace.openUriInPane (/Applications/Atom.app/Contents/Resources/app/src/workspace.js:476:22)
  at Workspace.module.exports.Workspace.open (/Applications/Atom.app/Contents/Resources/app/src/workspace.js:409:19)
  at atom-workspace.<anonymous> (/Users/yg/.atom/packages/github-issues/index.coffee:44:24)
  at atom-workspace.handler (/Applications/Atom.app/Contents/Resources/app/src/space-pen-extensions.js:115:32)
  at atom-workspace.jQuery.event.dispatch (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4681:9)
  at atom-workspace.elemData.handle (/Applications/Atom.app/Contents/Resources/app/node_modules/space-pen/vendor/jquery.js:4359:46)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app/src/command-registry.js:243:29)
  at /Applications/Atom.app/Contents/Resources/app/src/command-registry.js:3:61
  at CommandPaletteView.module.exports.CommandPaletteView.confirmed (/Applications/Atom.app/Contents/Resources/app/node_modules/command-palette/lib/command-palette-view.js:120:32)
  at CommandPaletteView.module.exports.SelectListView.confirmSelection (/Applications/Atom.app/Contents/Resources/app/node_modules/autocomplete/node_modules/atom-space-pen-views/lib/select-list-view.js:335:21)
  at space-pen-div.atom.commands.add.core:confirm (/Applications/Atom.app/Contents/Resources/app/node_modules/autocomplete/node_modules/atom-space-pen-views/lib/select-list-view.js:109:19)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app/src/command-registry.js:243:29)
  at /Applications/Atom.app/Contents/Resources/app/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/keymap-manager.js:549:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/keymap-manager.js:391:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:167:20)

/cc @atom/core

Should be fixed in 0.5.0