Skip to content

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

logto

Trending repository

🧑‍🚀 Logto helps you build the sign-in, auth, and user identity within minutes. We provide an OIDC-based identity service and the end-user experience with username, phone number, email, and social sign-in, with extendable multi-language support.

  • Updated Jul 20, 2022
  • TypeScript
Rails logo

Popular topic

Ruby on Rails (Rails) is a web application framework written in Ruby.

Trending repository

Kansas City Developer Conference 2022

Upcoming event recommended by GitHub

Aug
8

Kansas City Developer Conference 2022

August 08, 2022 - August 10, 2022 • Kansas City, MO

The Kansas City Developer Conference is excited to announce our 13th annual event! Our 2022 conference will be held August 8–10, 2022, with both two full conference days, as well as a post-conference workshop day. Once again, the event will be held at the Kansas City Convention Center in downtown Kansas City
Zenhub screenshot

App recommended by GitHub

Zenhub

ZenHub is the only project management tool that integrates natively within GitHub’s user interface. No lengthy onboarding. No configuration headaches. No separate logins. Developers stay in an environment they love and Project Managers get total visibility into the development process.

Dev teams at companies like NASA, Microsoft, Adobe, Comcast, Docker, VMware, and Leap Motion trust ZenHub's powerful browser extension to help them ship better software.

freqtrade

Trending repository

JhorAVi
JhorAVi commented Jul 13, 2022

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

Good first issue Stoploss

Trending repository

Trending repository

dominikbraun
dominikbraun commented Jul 17, 2022

At the moment, edges consist of a source vertex, a target vertex, and a weight. It would be great to have a label as well:

type Edge[T any] struct {
	Source T
	Target T
	Weight int
	Label string
}

Possible APIs

  1. One approach to provide an API for adding a label to an edge is to implement methods such as EdgeWithLabel and WeightedEdgeWithLabel. This is a very sim
enhancement help wanted good first issue
docs

Trending repository

vedantsinghania05
vedantsinghania05 commented Apr 8, 2022

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/get-started/quickstart/create-a-repo

What part(s) of the article would you like to see updated?

I think that in the notes section of this page, there should be

help wanted good first issue content get started

Trending repository

cryptk
cryptk commented Aug 26, 2021

Description

If creating multiple VPCs on the same account, and creating the same endpoint type in those VPCs, you receive the following error:

Error: multiple VPC Endpoint Services matched; use additional constraints to reduce matches to a single VPC Endpoint Service

Versions

  • Terraform: 0.15.5
  • Provider(s):
  • provider registry.terraform.io/hashic
TestQuality screenshot

App recommended by GitHub

TestQuality

TestQuality is the #1 Test Case Creation and Management app for GitHub Workflows. TestQuality extends your Github DevOps workflow to provide powerful and modern GitHub issue powered test case creation and management. TestQuality integrates with GitHub, Jira, Selenium, Jenkins, Cloudbees, Cucumber, JUnit and more to complement your entire DevOps workflow. TestQuality is FREE for GitHub public repo’s and affordable for teams on private repo's.