Updates Slack integration

This update fixes the issue with the first letter being removed from a private channel. However, it also changes the current behaviour of the Toggl button in Slack. I think it's an improvement, but that may just be my opinion. Changes included here are:

Project is now taken from the channel name not team name as before
Hyphens (-) and underscores (_) are converted to spaces
Project name is converted to Title Case
Task description is left undefined for the channel title button
Adds a Toggl button to the hover message actions list
Task description for this button is taken from the message body
Fixes #1002
Fixes #601

Thanks @nunofmn I reverted to the default behaviour (although the description in the hover message is taken from the message body, which I think is logical from the context). Also squashed and rebased.

Yes the behaviour in the hover message is fine 👍
LGTM 👍
Thank you for you contribution. 🎉


Update the collection status

The collection needs a status which reflects both the current state, version and digests of the collection but also any errors applying collection contents. A common error applying collection contents results from RBAC limitations within the collection contents. Some of the status recording needs to be per resource, while other parts are per collection.
Example:
status:
    # Here available version > current reflects an available update
    availableVersion: <IP_ADDRESS>
    currentVersion: <IP_ADDRESS>
    resources:
    - name: <resource name or path>
      currentDigest: <digest>
      status: applied
    - name: <resource name or path>
      currentDigest: <digest>
      status: failed
      statusMessage: "role" is forbidden from creating objects of kind

Phases and Conditions
Some Kubernetes objects are treated as a state machine and record their status using "phases and conditions" concepts. This allows the status to record such things as whether it is initializing, ready, failed, etc. The use of phases and conditions is advanced and optional at this point, however, some of this idea is present in the above modeling in order to account for individual resource application failures.
For an example of this, see:

https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/conditions.go#L83
https://github.com/openshift-knative/knative-eventing-operator/blob/62770a4fec0e75e81377731073c94cb3b1ca82ef/pkg/apis/eventing/v1alpha1/knativeeventing_lifecycle.go

The digest and message sections of the status were resolved in PR #76.  I'd like to handle the version status in issue #61.  I'm going to close this issue.


[Feature #159951206] Add docstrings where necessary to implement feed…

What does this PR do?

Implements feedback given to me concerning challenge three by my LFA

Description of Task to be completed?
Using git best practice to make greate and atomic commit messages.
What are the relevant pivotal tracker stories?
Pivotal story 159951206

Pull Request Test Coverage Report for Build 220

9 of 9 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.355%

Totals

Change from base Build 218:
0.0%

Covered Lines:
1341

Relevant Lines:
1452

💛  - Coveralls


Txn dissapears from history after going into the paper wallet option

I received LTC from someone and it showed up in my history. About 6 hours later, I then went through the Paper Wallet process, including the verification.  When I completed that, the receipt had disappeared from the history.  Only way to get it back was to sync with the blockchain.  This was in 3.1.1 (3)
Transaction: https://blockchair.com/litecoin/address/LgXYwz7iLaSJsFP6pAM7zMMQpXxZhLjQGh
Wallet address

Missing from history

Thanks @jeff169 .  This will be labeled and looked at.

Thanks @jeff169 .  This will be labeled and looked at.