Skip to content

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

Maven logo
Popular topic
Maven is a build automation tool used primarily for Java projects.
App recommended by GitHub

Snyk

Snyk is on a mission to help developers use open source and stay secure.
Snyk helps find, fix & prevent known vulnerabilities in your Node.js, Java, Ruby, Python and Scala apps. Snyk is free for open source.

Snyk tracks vulnerabilities in over 800,000 open source packages, and helps protect over 25,000 applications.

83% of Snyk users found vulnerabilities in their applications, and new vulnerabilities are disclosed regularly, putting your application at risk.

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
Code Climate screenshot
App recommended by GitHub

Code Climate

Collaboratively improve code quality with Code Climate and GitHub

Code Climate combines line-by-line test coverage reports, technical debt assessments, and style checks in every pull request so that your team only merges clear, maintainable, and well-tested code.

You can’t perform that action at this time.