Skip to content

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

Gulp logo
Popular topic
Gulp is a toolkit for automating and streamlining web development.
codebeat screenshot
App recommended by GitHub

codebeat

Tired of manually scraping your code looking for the smallest issues? Take codebeat for a spin! 🚀

codebeat is an automated static code analysis tool supporting multiple languages used by both web and mobile developers worldwide. Now also providing style analysis for projects written in Swift🔥.

We've integrated SwiftLint, the best linter for Swift in our code review app and fixed you with a help page. about the feature. Enjoy!

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

Buddy

Get back your time with Buddy’s delivery pipelines that eliminate repeatable tasks in your daily development.

Automatically build & ship web projects on a single git push, on click, or recurrently. Easily define your own delivery process just like you build a house of bricks: from builds and tests, to deployments, custom scripts, and website monitoring.

Bring the newest tech to your team’s stack with native Docker support: containers, microservices, Kubernetes deployments, and more.

You can’t perform that action at this time.