LBRYCommunity/lbry.go

Fork

You've already forked lbry.go

Code Issues 5 Pull requests Projects Releases 46 Packages Wiki Activity

extract slack logging to own package #22

New issue

Open

opened 2018-07-17 20:01:02 +02:00 by nikooo777 · 0 comments

nikooo777 commented

2018-07-17 20:01:02 +02:00

(Migrated from github.com)

Copy link

As per comment here: https://github.com/lbryio/lbry.go/pull/10#discussion_r190252247

slack logging package should be extracted to own package. Please wait for #10 to be merged first.

As per comment here: https://github.com/lbryio/lbry.go/pull/10#discussion_r190252247 slack logging package should be extracted to own package. Please wait for #10 to be merged first.

No Branch/Tag specified

Branches Tags

master

lbcd-port

cors

lbryinc-errors

stake_supports

mod-updates

improvement/get_response

lbrycrd_go

add_ordered_maps

stopper_propagation

latest_client

feature/lbryinc_client_caller

latest_btcd

interpolation

ucb-rework

v3.0.1-beta

v2.7.1

v2.7.0

v2.6.0

v2.5.3

v2.5.2

v2.5.1

v2.5.0

v2.4.6

v2.4.5

v2.4.4

v2.4.3

v2.4.2

v2.4.1

v2.4.0

v2.3.2

v2.3.1

v2.3.1-pre3

v2.3.1-pre2

v2.3.1-pre

v2.3.0

v2.2.1

v2.2.0

v2.1.0

v2.0.6

v2.0.5

v2.0.4

v2.0.3

v2.0.2

v2.0.1

v2.0.0

v1.1.2

v1.1.1

v1.1.0

v1.0.18

v1.0.16

v1.0.17

v0.1.0

v1.0.15

v1.0.14

v1.0.13

v1.0.12

v1.0.11

v1.0.10

v1.0.9

v1.0.8

v1.0.7

v1.0.6

v1.0.5

v1.0.4

v1.0.3

v1.0.3-pre

v1.0.2

v1.0.1

v1.0.0

v0.0.1

sdk-0.32

Labels

Clear labels

Work is part of a proposal

consider soon

Discuss this issue at the next planning meeting, then remove this label

dependencies

Pull requests that update a dependency file

Epic

good first issue

hacktoberfest

Welcome to Hacktoberfest

No knowledge of the existing code required

level: 2

Some knowledge of the existing code is recommended

level: 3

Significant knowledge of the existing code is recommended

level: 4

Intimate knowledge of the existing code is recommended

needs: exploration

Solution unclear, needs research

needs: grooming

Issue needs to be groomed before work can start

needs: priority

Priority level needs to be defined

needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

needs: tech design

Needs technical design signoff before implementation can begin

on hold

Temporarily paused

priority: blocker

Issue is blocking release, do ASAP

priority: high

Work needs to be moved into sprint ASAP

priority: low

Work should be done but can stay in the backlog for now

priority: medium

Work needs to be done within 2-3 sprints

resilience

Tom's Wishlist

type: bug

Existing functionality is wrong or broken

type: discussion

A conversation. No specific changes requested

type: improvement

Existing (or partially existing) functionality needs to be changed

type: new feature

New functionality that does not exist yet

type: refactor

Minimal user-visible changes, but significant internal work

type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

type: testing

Solution needs additional user testing

unplanned

Work that was not planned into the spirnt, took priority over planned work

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry.go#22

Reference in a new issue

Repository

LBRYCommunity/lbry.go

Title

Body

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?