Skip to content

Here's what's popular on GitHub today...

IPFS logo
Popular topic
IPFS is a peer-to-peer protocol for content-addressed sharing of data via a distributed file system.
App recommended by GitHub

Pageclip

Pageclip is a simple way to save information from your website via forms or front-end JavaScript. That is, you can save data from your website without a serverโ€”Pageclip is your server.

Pageclip is perfect compliment to your GitHub pages site: collect leads for your new product, setup a contact form, capture emails for a Newsletter, or create white-Labeled survey forms. All from your static website and without a server.

strapi
Trending repository
sam-pires
sam-pires commented Dec 4, 2020

Bug report

Describe the bug

There is an extra space in the French wording in the modal to add a single unilateral relation in the CTB. But I also wonder if the wording is actually correct: for the 2 first relationship types we use "[CT1] a un [CT2]".

See video: https://www.loom.com/share/95e8b07f2dff4dc3801624dd9d6bafc4

Steps to reproduce the behavior

  1. In dev env, Go to
Trending repository
sanket1729
sanket1729 commented Oct 8, 2020

IRC logs

sanket1729: How can decoderawtransaction RPC know reqSigs if the output scriptpubkey is p2sh/p2wsh? I think it is returning 1 everytime.
sipa: sanket1729: it only works for bare multisig
sipa: we should probably just remove it

The output parameter for reqSigs is confusing as it outputs 1 for all scripts but bare multisig in the scriptpubkey. Considering the limited applicab

packer
Trending repository
tking2096
tking2096 commented Dec 4, 2020

Overview of the Issue

Using PowerShell, I have successfully enabled logging using the PACKER_LOG and PACKER_LOG_PATH environment variables. I would like the error-cleanup-provisioner to publish the last n lines of this log, but I can't seem to get the value of PACKER_LOG_PATH in my template.

Reproduction Steps

In PowerShell:

$env:PACKER_LOG = "1"
$env:PACKER_LOG
App recommended by GitHub

LGTM

Continuous security analysis

LGTM is a code analysis platform for identifying vulnerabilities and preventing them from reaching production.

LGTM automatically runs 1600+ standard analyses contributed by researchers from the Semmle Security Research Team and our customer community, including Microsoft, Google, Uber and Mozilla.

Quickly refine and run custom QL queries to find variants of known issues and prevent them from being re-introduced into your codebase.

You canโ€™t perform that action at this time.