Trending repository
-
Updated
Jul 17, 2022 - Rust
On this episode of The Download, Christina returns from some downtime with a random t-shirt and the latest developer and open source project news, including GitHub Copilot, Deno Fresh, GPT-3 code explanation, TensorFlow Lite for Commodore 64s, and more!
August 08, 2022 - August 10, 2022 • Kansas City, MO
Creating pixel art for fun or animated sprites for a game? The digital artist in you will love these apps and tools!
Say goodbye to notification fatigue. PR Chat creates a single Slack message for every PR. Any changes to the PR instantly and silently update the Slack message
Your PR looks the same as it does on Github. All formatting is preserved including text formatting, images and even code diffs.
Use Slack to power your PR discussions. Conversations in the Slack message's thread are two way synced with Github comments.
Hi, I have a trailing_stop_loss exit with small loss of -0.42% probably due to slippage. The problem is the StopLossGuard caught it because it's still considered a stoploss exit even though loss is small. Is there a workaround so that StopLossGuard won't mind those micro losses? Or even better is a way to exclude trailing_stop_loss from StopLossGuard's radar?
Thanks for the help
I can't find any documentation or thorough tests of the path substitution performed by compiler/options/pathSubs.
From looking at the code, these are the substitutions:
$nim: global nim prefix directory path$lib: stdlib directory path$home: user's home directory path$config: I think this is the directory path to the either the nimscript callinghttps://docs.github.com/en/get-started/quickstart/create-a-repo
I think that in the notes section of this page, there should be
Every "section" of the video is separated by a clip of what's in ./img/hh-fcc-background.png. We currently have the title text of each section in this repo, but we don't have the timestamp in here!
Sonatype Lift helps you find and fix your most elusive bugs so you can spend time writing great code, not debugging it. Lift looks for a broad range of performance, security, and reliability errors in the code you write and the libraries you depend on, making it an ideal all-in-one bug catcher for your entire company. Running at each pull request, Lift delivers results as code review comments so you can fix bugs in minutes. (Yes really)
Checklist