Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Improve logging consistency #1424

Merged
merged 4 commits into from
May 1, 2023

Conversation

orpheuslummis
Copy link
Contributor

@orpheuslummis orpheuslummis commented Apr 30, 2023

Relevant issue(s)

Tackles #1430 (but doesn't fully resolve it)

Description

  • fix one SchemaID value logging the function instead of the resulting of calling the function
  • more consistency. prefer PeerID over PID

Tasks

  • I made sure the code is well commented, particularly hard-to-understand areas.
  • I made sure the repository-held documentation is changed accordingly.
  • I made sure the pull request title adheres to the conventional commit style (the subset used in the project can be found in tools/configs/chglog/config.yml).
  • I made sure to discuss its limitations such as threats to validity, vulnerability to mistake and misuse, robustness to invalidation of assumptions, resource requirements, ...

How has this been tested?

CI

@orpheuslummis orpheuslummis added the action/no-benchmark Skips the action that runs the benchmark. label Apr 30, 2023
@orpheuslummis orpheuslummis self-assigned this Apr 30, 2023
@codecov
Copy link

codecov bot commented Apr 30, 2023

Codecov Report

Merging #1424 (81fc86c) into develop (4b06a49) will increase coverage by 0.19%.
The diff coverage is 30.00%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #1424      +/-   ##
===========================================
+ Coverage    72.03%   72.23%   +0.19%     
===========================================
  Files          185      185              
  Lines        18185    18160      -25     
===========================================
+ Hits         13100    13118      +18     
+ Misses        4048     4010      -38     
+ Partials      1037     1032       -5     
Impacted Files Coverage Δ
api/http/errors.go 100.00% <ø> (ø)
cli/replicator_delete.go 31.25% <0.00%> (+7.44%) ⬆️
cli/replicator_set.go 29.41% <0.00%> (+4.82%) ⬆️
client/dockey.go 51.16% <ø> (ø)
net/peer.go 49.34% <20.00%> (ø)
cli/peerid.go 45.16% <50.00%> (ø)
net/server.go 63.12% <50.00%> (ø)
api/http/server.go 100.00% <100.00%> (ø)
db/collection.go 68.66% <100.00%> (ø)
net/client.go 85.71% <100.00%> (ø)
... and 1 more

... and 4 files with indirect coverage changes

Copy link
Contributor

@AndrewSisley AndrewSisley left a comment

Choose a reason for hiding this comment

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

LGTM, thanks Orpheus :)

@orpheuslummis orpheuslummis force-pushed the orpheus/chore/logging-consistency branch from 1d7e74d to 81fc86c Compare May 1, 2023 15:24
Copy link
Collaborator

@fredcarle fredcarle left a comment

Choose a reason for hiding this comment

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

LGTM.

@orpheuslummis orpheuslummis merged commit 7233d0b into develop May 1, 2023
20 checks passed
@orpheuslummis orpheuslummis deleted the orpheus/chore/logging-consistency branch May 1, 2023 15:34
shahzadlone pushed a commit to shahzadlone/defradb that referenced this pull request Feb 23, 2024
## Relevant issue(s)

Improves on sourcenetwork#1430 (but doesn't resolve it)

## Description

- fix one SchemaID value logging the function instead of the resulting
of calling the function
- more consistency. prefer PeerID over PID

## Tasks

- [x] I made sure the code is well commented, particularly
hard-to-understand areas.
- [x] I made sure the repository-held documentation is changed
accordingly.
- [x] I made sure the pull request title adheres to the conventional
commit style (the subset used in the project can be found in
[tools/configs/chglog/config.yml](tools/configs/chglog/config.yml)).
- [x] I made sure to discuss its limitations such as threats to
validity, vulnerability to mistake and misuse, robustness to
invalidation of assumptions, resource requirements, ...

## How has this been tested?

CI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action/no-benchmark Skips the action that runs the benchmark.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants