-
Updated
Dec 16, 2020 - C++
Here's what's popular on GitHub today...
-
Updated
Dec 18, 2020 - Python
R
-
Updated
Dec 19, 2020 - TypeScript
-
Updated
Dec 19, 2020 - Python
-
Updated
Dec 18, 2020
Sentry
Sentry provides real-time crash reporting, giving your team insight into errors affecting your customers in production. Sentry supports dozens of languages and frameworks and is trusted by thousands of companies like Pinterest, Uber, Stripe, Dropbox, and Airbnb.
Sentry doesn't just alert you to errors, but integrates into your GitHub development flow by linking errors to the commit and author likely responsible, creating new GitHub Issues, and resolving errors with commit message.
-
Updated
Dec 3, 2020 - Python
-
Updated
Dec 18, 2020 - Java
-
Updated
Dec 19, 2020 - Python
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
-
Updated
Dec 18, 2020 - C++
-
Updated
Dec 18, 2020
Describe the bug
A lot of the targets in programs/Makefile are actually "phony" in that they don't emit a file of their name. These files are mostly variants of the main zstd build, but as a matter of correctness this is wrong.
The lib/Makefile has a similar problem where the install-* targets are not labeled as PHONY.
I don't have time to check the other makefiles, but chances
First check
- I added a very descriptive title to this issue.
- I used the GitHub search to find a similar issue and didn't find it.
- I searched the FastAPI documentation, with the integrated search.
- I already searched in Google "How to X in FastAPI" and didn't find any information.
- I already read and followed all the tutorial in the docs and didn't find an answ
-
Updated
Dec 18, 2020 - Python
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
- In dev env, Go to
-
Updated
Dec 18, 2020 - Go
is this intentional?
on scaleway instance:
$ k0s default-config
apiVersion: k0s.k0sproject.io/v1beta1
kind: Cluster
metadata:
name: k0s
spec:
api:
address: 10.18.80.227
sans:
- 10.18.80.227
- 10.18.80.227
^-- two same sans?
$ ip address
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loo
-
Updated
Dec 17, 2020 - Python
-
Updated
Dec 18, 2020 - Shell
IRC logs
sanket1729: How can
decoderawtransactionRPC 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
LogRocket
LogRocket lets you replay problems as if they happened in your own browser. Instead of guessing why errors happen, or asking users for screenshots and log dumps, you can replay sessions to quickly understand what went wrong.
LogRocket records pixel-perfect videos of user activity along with console logs, JavaScript errors, network requests, and browser metadata. It also has deep integrations with React, Redux, Angular and Vue.js to record application state.
Allow disabling a nav item.
Steps to follow:
nav.tsx.make generatefrom project root - this generates python API.