good morning!!!!
Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
B
bor
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Harbor Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
open
bor
Commits
2855a93e
Commit
2855a93e
authored
Mar 16, 2016
by
Péter Szilágyi
Browse files
Options
Downloads
Plain Diff
Merge pull request #2341 from leijurv/patch-2
core: fixed various typos
parents
b5cee973
c7727191
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
core/blockchain.go
+3
-3
3 additions, 3 deletions
core/blockchain.go
with
3 additions
and
3 deletions
core/blockchain.go
+
3
−
3
View file @
2855a93e
...
@@ -99,7 +99,7 @@ type BlockChain struct {
...
@@ -99,7 +99,7 @@ type BlockChain struct {
futureBlocks
*
lru
.
Cache
// future blocks are blocks added for later processing
futureBlocks
*
lru
.
Cache
// future blocks are blocks added for later processing
quit
chan
struct
{}
// blockchain quit channel
quit
chan
struct
{}
// blockchain quit channel
running
int32
// running must be called a
u
tomically
running
int32
// running must be called atomically
// procInterrupt must be atomically called
// procInterrupt must be atomically called
procInterrupt
int32
// interrupt signaler for block processing
procInterrupt
int32
// interrupt signaler for block processing
wg
sync
.
WaitGroup
// chain processing wait group for shutting down
wg
sync
.
WaitGroup
// chain processing wait group for shutting down
...
@@ -792,7 +792,7 @@ func (self *BlockChain) WriteBlock(block *types.Block) (status WriteStatus, err
...
@@ -792,7 +792,7 @@ func (self *BlockChain) WriteBlock(block *types.Block) (status WriteStatus, err
glog
.
Fatalf
(
"failed to write block total difficulty: %v"
,
err
)
glog
.
Fatalf
(
"failed to write block total difficulty: %v"
,
err
)
}
}
if
err
:=
WriteBlock
(
self
.
chainDb
,
block
);
err
!=
nil
{
if
err
:=
WriteBlock
(
self
.
chainDb
,
block
);
err
!=
nil
{
glog
.
Fatalf
(
"filed to write block contents: %v"
,
err
)
glog
.
Fatalf
(
"f
a
iled to write block contents: %v"
,
err
)
}
}
self
.
futureBlocks
.
Remove
(
block
.
Hash
())
self
.
futureBlocks
.
Remove
(
block
.
Hash
())
...
@@ -1134,7 +1134,7 @@ func reportBlock(block *types.Block, err error) {
...
@@ -1134,7 +1134,7 @@ func reportBlock(block *types.Block, err error) {
//
//
// The verify parameter can be used to fine tune whether nonce verification
// The verify parameter can be used to fine tune whether nonce verification
// should be done or not. The reason behind the optional check is because some
// should be done or not. The reason behind the optional check is because some
// of the header retrieval mechanisms already need to verfy nonces, as well as
// of the header retrieval mechanisms already need to ver
i
fy nonces, as well as
// because nonces can be verified sparsely, not needing to check each.
// because nonces can be verified sparsely, not needing to check each.
func
(
self
*
BlockChain
)
InsertHeaderChain
(
chain
[]
*
types
.
Header
,
checkFreq
int
)
(
int
,
error
)
{
func
(
self
*
BlockChain
)
InsertHeaderChain
(
chain
[]
*
types
.
Header
,
checkFreq
int
)
(
int
,
error
)
{
// Make sure only one thread manipulates the chain at once
// Make sure only one thread manipulates the chain at once
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment