Skip to content

metadata: update container error messages#1847

Merged
AkihiroSuda merged 1 commit intocontainerd:masterfrom
jessvalarezo:metadata-errors
Dec 1, 2017
Merged

metadata: update container error messages#1847
AkihiroSuda merged 1 commit intocontainerd:masterfrom
jessvalarezo:metadata-errors

Conversation

@jessvalarezo
Copy link
Copy Markdown
Contributor

Part of an effort to make error messages consistent and as helpful as possible. Very open to any suggestions!!

Signed-off-by: Jess Valarezo [email protected]

@codecov-io
Copy link
Copy Markdown

codecov-io commented Dec 1, 2017

Codecov Report

Merging #1847 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1847   +/-   ##
=======================================
  Coverage   49.12%   49.12%           
=======================================
  Files          86       86           
  Lines        8246     8246           
=======================================
  Hits         4051     4051           
  Misses       3525     3525           
  Partials      670      670
Flag Coverage Δ
#linux 52.52% <0%> (ø) ⬆️
#windows 44.25% <0%> (ø) ⬆️
Impacted Files Coverage Δ
metadata/containers.go 47.31% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 38fdf9c...b873ae8. Read the comment docs.

@stevvooe
Copy link
Copy Markdown
Member

stevvooe commented Dec 1, 2017

LGTM

Comment thread metadata/containers.go Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change seems unneeded

Copy link
Copy Markdown
Contributor Author

@jessvalarezo jessvalarezo Dec 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

within all the validation packages errors are wrapped with errdefs.ErrInvalidArgument and whenever validateContainer is called the err message includes "... failed validation". thought this would help avoid redundancy.

Comment thread metadata/containers.go Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer to no "from bucket". The user don't know bucket.

Comment thread metadata/containers.go Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. duplicated "id"
  2. namespace and bucket is unnecessary

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

leaving in namespace since it's helpful for the user

Comment thread metadata/containers.go Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unnecessary

Comment thread metadata/containers.go Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto

Comment thread metadata/containers.go Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no "to bucket"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sounds good

@stevvooe
Copy link
Copy Markdown
Member

stevvooe commented Dec 1, 2017

LGTM

@AkihiroSuda AkihiroSuda merged commit 222156d into containerd:master Dec 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants