Skip to content
This repository was archived by the owner on Oct 30, 2018. It is now read-only.

Commit c4b518f

Browse files
authored
Merge pull request #723 from tempestb/feature/ToolTips
Adds ToolTips to column objects. knowledge@storj.io
2 parents 4d73e5c + 9014195 commit c4b518f

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

app/views/overview/index.js

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -109,9 +109,9 @@ module.exports = {
109109
class="checkbox">
110110
</td>
111111
112-
<td><b-tooltip :content="share.id"><span>#{{index}}</span></b-tooltip></td>
112+
<td><span>#{{index}}</span></td>
113113
114-
<td><span>{{share.id}}</span></td>
114+
<td><b-tooltip content="The Node ID of the node."><span>{{share.id}}</span></b-tooltip></td>
115115
116116
<td>
117117
<div v-if="share.isValid && share.isRunning"><b-tooltip content="Online"><span class="node-status-on">ON</span></b-tooltip></div>
@@ -123,25 +123,25 @@ module.exports = {
123123
<!-- <td class="storj">25,920 <span>STORJ</span></td> -->
124124
<td>{{share.config.storagePath}}</td>
125125
<td><span v-if="share.isRunning">{{share.meta.uptimeReadable}}</span></td>
126-
<td>{{share.meta.numRestarts}}</td>
127-
<td>{{share.meta.farmerState.totalPeers}}</td>
126+
<td><b-tooltip content="A node will often restart when you receive an error. Search the log for ECONNRESET if this happens frequently.">{{share.meta.numRestarts}}</b-tooltip></td>
127+
<td><b-tooltip content="Used for legacy compatibility.">{{share.meta.farmerState.totalPeers}}</b-tooltip></td>
128128
<td>
129129
<div v-if="!share.isValid || (share.isValid && !share.isRunning) || share.meta.farmerState.bridgesConnectionStatus === 0"><b-tooltip content="Not connected to any bridges"><span class="node-status-off">Disconnected</span></b-tooltip></div>
130130
<div v-if="share.isValid && share.isRunning && share.meta.farmerState.bridgesConnectionStatus === 1"><b-tooltip content="Connecting to bridges"><span class="node-status-loading">Connecting</span></b-tooltip></div>
131131
<div v-if="share.isValid && share.isRunning && share.meta.farmerState.bridgesConnectionStatus === 2"><b-tooltip content="Performing Proof of Work to join the network"><span class="node-status-loading">Confirming</span></b-tooltip></div>
132132
<div v-if="share.isValid && share.isRunning && share.meta.farmerState.bridgesConnectionStatus === 3"><b-tooltip content="Connected to bridges"><span class="node-status-on">Connected</span></b-tooltip></div>
133133
</td>
134-
<td>{{share.meta.farmerState.contractCount}} ({{share.meta.farmerState.dataReceivedCount}} received)</td>
135-
<td>{{share.meta.farmerState.spaceUsed}} ({{share.meta.farmerState.percentUsed}}%)</td>
134+
<td><b-tooltip content="How many times since you reset your node that the Bridge has asked your node for an alloc message. An alloc is basically telling the Bridge your node's status.">{{share.meta.farmerState.contractCount}}</b-tooltip><b-tooltip content="This is a count of how many shards you have received."> ({{share.meta.farmerState.dataReceivedCount}} received)</b-tooltip></td>
135+
<td><b-tooltip content="This shows how much space is being used by shards and the percentage of total space that is being used. If this says ... either your node is new and doesn't yet have any data, or there is potentially a corruption issue.">{{share.meta.farmerState.spaceUsed}} ({{share.meta.farmerState.percentUsed}}%)</b-tooltip></td>
136136
<td v-if="share.meta.farmerState.ntpStatus && share.meta.farmerState.ntpStatus.status === 2">
137137
<b-tooltip content="Your computer clock is out of sync. Consider installing a sync tool such as NetTime">
138-
<span class="connection" v-if="share.meta.farmerState.ntpStatus && share.isRunning" v-bind:status="share.meta.farmerState.ntpStatus.status">{{share.meta.farmerState.ntpStatus.delta}}</span>
138+
<span class="connection" v-if="share.meta.farmerState.ntpStatus && share.isRunning" v-bind:status="share.meta.farmerState.ntpStatus.status"><b-tooltip content="This is your node clock's precision. It should be within +/- 500. If it says 9999 this may indicate a one time NTP communication failure. It is not a problem unless you see it at this number for a long period of time (Hours) ">{{share.meta.farmerState.ntpStatus.delta}}</b-tooptip></span>
139139
</b-tooltip>
140140
</td>
141141
<td v-else>
142142
<span class="connection" v-if="share.meta.farmerState.ntpStatus && share.isRunning" v-bind:status="share.meta.farmerState.ntpStatus.status">{{share.meta.farmerState.ntpStatus.delta}}</span>
143143
</td>
144-
<td><span class="connection" v-if="share.meta.farmerState.portStatus && share.isRunning" v-bind:status="share.meta.farmerState.portStatus.connectionStatus">{{share.meta.farmerState.portStatus.listenPort}} {{share.meta.farmerState.portStatus.connectionType}}</span></td>
144+
<td><b-tooltip content="The port your node is listening on for communication. Each node should be on a different port. Port status should be green in color. If your port status says UPnP, Tunneling, or is Red you should manually setup port forwarding. If your node status is black, you may either need to configure port forwarding manually or you may have a loopback error that prevents it from self testing. Please visit https://community.storj.io and join the channel #storjshare for further help."><span class="connection" v-if="share.meta.farmerState.portStatus && share.isRunning" v-bind:status="share.meta.farmerState.portStatus.connectionStatus">{{share.meta.farmerState.portStatus.listenPort}} {{share.meta.farmerState.portStatus.connectionType}}</span></b-tooltip></td>
145145
<td class="text-right">
146146
<b-dropdown :id="'dropdownMenuLink' + share.id">
147147
<span slot="text">

0 commit comments

Comments
 (0)