Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
jami-nameservice
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
savoirfairelinux
jami-nameservice
Commits
463f5c9d
Commit
463f5c9d
authored
8 years ago
by
Adrien Béraud
Browse files
Options
Downloads
Patches
Plain Diff
nameservice: cleanup name registration log
Change-Id: I46d2df4d6b0a88cc6e2a0b6512a64663a774df2d
parent
f0a6d54e
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
index.js
+1
-1
1 addition, 1 deletion
index.js
with
1 addition
and
1 deletion
index.js
+
1
−
1
View file @
463f5c9d
...
...
@@ -17,7 +17,6 @@ Object.getPrototypeOf(web3.eth).awaitConsensus = function(txhash, mined_cb) {
console
.
log
(
"
watch error:
"
+
error
);
var
receipt
=
ethP
.
getTransactionReceipt
(
txhash
);
if
(
receipt
&&
receipt
.
transactionHash
==
txhash
)
{
console
.
log
(
receipt
);
filter
.
stopWatching
();
mined_cb
();
}
else
if
(
!--
tries
)
{
...
...
@@ -235,6 +234,7 @@ function startServer() {
http_res
.
status
(
403
).
end
(
JSON
.
stringify
({
"
success
"
:
false
}));
return
;
}
console
.
log
(
"
Ended registration for
"
+
req
.
params
.
name
+
"
->
"
+
addr
);
reg
.
addr
(
req
.
params
.
name
,
function
(
err
,
reg_addr
)
{
//console.log(reg_c + "Found address " + reg_addr);
if
(
reg_addr
!=
addr
)
{
...
...
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