Replace "the the" with "the" in documentation and comments

This commit is contained in:
Ben Barnard 2016-10-11 15:31:40 -04:00
parent 2e78c2b8b9
commit 83f647ed84
27 changed files with 43 additions and 43 deletions

View File

@ -68,7 +68,7 @@ func TestAllocRunner_SimpleRun(t *testing.T) {
}
// TestAllocRuner_RetryArtifact ensures that if one task in a task group is
// retrying fetching an artifact, other tasks in the the group should be able
// retrying fetching an artifact, other tasks in the group should be able
// to proceed.
func TestAllocRunner_RetryArtifact(t *testing.T) {
ctestutil.ExecCompatible(t)

View File

@ -47,7 +47,7 @@ var (
// regardless of driver.
TaskLocal = "local"
// TaskSecrets is the the name of the secret directory inside each task
// TaskSecrets is the name of the secret directory inside each task
// directory
TaskSecrets = "secrets"

View File

@ -28,7 +28,7 @@ const (
// killing a task.
killBackoffBaseline = 5 * time.Second
// killBackoffLimit is the the limit of the exponential backoff for killing
// killBackoffLimit is the limit of the exponential backoff for killing
// the task.
killBackoffLimit = 2 * time.Minute

View File

@ -18,7 +18,7 @@ const (
nomad run -check-index %d %s
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.`
)
@ -51,7 +51,7 @@ Usage: nomad plan [options] <file>
give insight into what the scheduler will attempt to do and why.
If the job has specified the region, the -region flag and NOMAD_REGION
environment variable are overridden and the the job's region is used.
environment variable are overridden and the job's region is used.
Plan will return one of the following exit codes:
* 0: No allocations created or destroyed.
@ -226,7 +226,7 @@ func formatDryRun(resp *api.JobPlanResponse, job *structs.Job) string {
return out
}
// formatJobDiff produces an annoted diff of the the job. If verbose mode is
// formatJobDiff produces an annoted diff of the job. If verbose mode is
// set, added or deleted task groups and tasks are expanded.
func formatJobDiff(job *api.JobDiff, verbose bool) string {
marker, _ := getDiffString(job.Type)

View File

@ -50,7 +50,7 @@ Usage: nomad run [options] <path>
issues or internal errors, are indicated by exit code 1.
If the job has specified the region, the -region flag and NOMAD_REGION
environment variable are overridden and the the job's region is used.
environment variable are overridden and the job's region is used.
The run command will set the vault_token of the job based on the following
precedence, going from highest to lowest: the -vault-token flag, the
@ -63,7 +63,7 @@ General Options:
Run Options:
-check-index
If set, the job is only registered or updated if the the passed
If set, the job is only registered or updated if the passed
job modify index matches the server side version. If a check-index value of
zero is passed, the job is only registered if it does not yet exist. If a
non-zero value is passed, it ensures that the job is being updated from a

View File

@ -179,7 +179,7 @@ func (p *ConnPool) Shutdown() error {
// pooled or to return a new connection
func (p *ConnPool) acquire(region string, addr net.Addr, version int) (*Conn, error) {
// Check to see if there's a pooled connection available. This is up
// here since it should the the vastly more common case than the rest
// here since it should the vastly more common case than the rest
// of the code here.
p.Lock()
c := p.pool[addr.String()]

View File

@ -2225,7 +2225,7 @@ var (
// Template represents a template configuration to be rendered for a given task
type Template struct {
// SourcePath is the the path to the template to be rendered
// SourcePath is the path to the template to be rendered
SourcePath string `mapstructure:"source"`
// DestPath is the path to where the template should be rendered

View File

@ -112,7 +112,7 @@ func (w *Worker) run() {
return
}
// Wait for the the raft log to catchup to the evaluation
// Wait for the raft log to catchup to the evaluation
if err := w.waitForIndex(eval.ModifyIndex, raftSyncLimit); err != nil {
w.sendAck(eval.ID, token, false)
continue
@ -327,7 +327,7 @@ SUBMIT:
// allocations.
var state scheduler.State
if result.RefreshIndex != 0 {
// Wait for the the raft log to catchup to the evaluation
// Wait for the raft log to catchup to the evaluation
w.logger.Printf("[DEBUG] worker: refreshing state to index %d for %q", result.RefreshIndex, plan.EvalID)
if err := w.waitForIndex(result.RefreshIndex, raftSyncLimit); err != nil {
return nil, nil, err

View File

@ -520,7 +520,7 @@ func inplaceUpdate(ctx Context, eval *structs.Evaluation, job *structs.Job,
}
// evictAndPlace is used to mark allocations for evicts and add them to the
// placement queue. evictAndPlace modifies both the the diffResult and the
// placement queue. evictAndPlace modifies both the diffResult and the
// limit. It returns true if the limit has been reached.
func evictAndPlace(ctx Context, diff *diffResult, allocs []allocTuple, desc string, limit *int) bool {
n := len(allocs)
@ -538,7 +538,7 @@ func evictAndPlace(ctx Context, diff *diffResult, allocs []allocTuple, desc stri
}
// markLostAndPlace is used to mark allocations as lost and add them to the
// placement queue. evictAndPlace modifies both the the diffResult and the
// placement queue. evictAndPlace modifies both the diffResult and the
// limit. It returns true if the limit has been reached.
func markLostAndPlace(ctx Context, diff *diffResult, allocs []allocTuple, desc string, limit *int) bool {
n := len(allocs)

View File

@ -219,7 +219,7 @@ types similar to the standard %v format specifier.
The custom formatter only responds to the %v (most compact), %+v (adds pointer
addresses), %#v (adds types), and %#+v (adds types and pointer addresses) verb
combinations. Any other verbs such as %x and %q will be sent to the the
combinations. Any other verbs such as %x and %q will be sent to the
standard fmt package for formatting. In addition, the custom formatter ignores
the width and precision arguments (however they will still work on the format
specifiers not handled by the custom formatter).

View File

@ -156,7 +156,7 @@ standard %v format specifier.
The custom formatter only responds to the %v (most compact), %+v (adds pointer
addresses), %#v (adds types), or %#+v (adds types and pointer addresses) verb
combinations. Any other verbs such as %x and %q will be sent to the the
combinations. Any other verbs such as %x and %q will be sent to the
standard fmt package for formatting. In addition, the custom formatter ignores
the width and precision arguments (however they will still work on the format
specifiers not handled by the custom formatter).

View File

@ -405,7 +405,7 @@ types similar to the standard %v format specifier.
The custom formatter only responds to the %v (most compact), %+v (adds pointer
addresses), %#v (adds types), or %#+v (adds types and pointer addresses) verb
combinations. Any other verbs such as %x and %q will be sent to the the
combinations. Any other verbs such as %x and %q will be sent to the
standard fmt package for formatting. In addition, the custom formatter ignores
the width and precision arguments (however they will still work on the format
specifiers not handled by the custom formatter).

View File

@ -211,7 +211,7 @@ type PreparedQueryExecuteRemoteRequest struct {
Limit int
// QueryOptions (unfortunately named here) controls the consistency
// settings for the the service lookups.
// settings for the service lookups.
QueryOptions
}

View File

@ -36,7 +36,7 @@ func (c *userEventCoalescer) Coalesce(e Event) {
return
}
// If the the same age, save it
// If the same age, save it
if latest.LTime == user.LTime {
latest.Events = append(latest.Events, e)
}

View File

@ -104,7 +104,7 @@ func DefaultConfig() *Config {
return config
}
// ConfigureTLS takes a set of TLS configurations and applies those to the the HTTP client.
// ConfigureTLS takes a set of TLS configurations and applies those to the HTTP client.
func (c *Config) ConfigureTLS(t *TLSConfig) error {
if c.HttpClient == nil {

View File

@ -88,7 +88,7 @@ func CompareDomainName(s1, s2 string) (n int) {
return
}
// CountLabel counts the the number of labels in the string s.
// CountLabel counts the number of labels in the string s.
// s must be a syntactically valid domain name.
func CountLabel(s string) (labels int) {
if s == "." {
@ -107,7 +107,7 @@ func CountLabel(s string) (labels int) {
// Split splits a name s into its label indexes.
// www.miek.nl. returns []int{0, 4, 9}, www.miek.nl also returns []int{0, 4, 9}.
// The root name (.) returns nil. Also see SplitDomainName.
// The root name (.) returns nil. Also see SplitDomainName.
// s must be a syntactically valid domain name.
func Split(s string) []int {
if s == "." {

View File

@ -112,7 +112,7 @@ while(<>) {
my @out = parseparamlist($out);
# Try in vain to keep people from editing this file.
# The theory is that they jump into the middle of the file
# theory is that they jump into the middle of the file
# without reading the header.
$text .= "// THIS FILE IS GENERATED BY THE COMMAND AT THE TOP; DO NOT EDIT\n\n";
@ -185,7 +185,7 @@ while(<>) {
}
} elsif($type eq "int64" && $_32bit ne "") {
if(@args % 2 && $arm) {
# arm abi specifies 64-bit argument uses
# arm abi specifies 64-bit argument uses
# (even, odd) pair
push @args, "0"
}
@ -282,7 +282,7 @@ while(<>) {
$text .= "\t$use\n";
}
$text .= $body;
if ($plan9 && $ret[2] eq "e1") {
$text .= "\tif int32(r0) == -1 {\n";
$text .= "\t\terr = e1\n";

2
vendor/gopkg.in/fsnotify.v1/fen.go generated vendored
View File

@ -31,7 +31,7 @@ func (w *Watcher) Add(name string) error {
return nil
}
// Remove stops watching the the named file or directory (non-recursively).
// Remove stops watching the named file or directory (non-recursively).
func (w *Watcher) Remove(name string) error {
return nil
}

View File

@ -104,7 +104,7 @@ func (w *Watcher) Add(name string) error {
return err
}
// Remove stops watching the the named file or directory (non-recursively).
// Remove stops watching the named file or directory (non-recursively).
func (w *Watcher) Remove(name string) error {
name = filepath.Clean(name)
w.mu.Lock()

View File

@ -81,7 +81,7 @@ func (w *Watcher) Add(name string) error {
return <-in.reply
}
// Remove stops watching the the named file or directory (non-recursively).
// Remove stops watching the named file or directory (non-recursively).
func (w *Watcher) Remove(name string) error {
in := &input{
op: opRemoveWatch,

View File

@ -493,7 +493,7 @@ documentation [here](/docs/drivers/index.html)
* `Administrator`
* `user.checked_drivers`: An operator specifiable list of drivers to enforce
the the `user.blacklist`. For drivers using containers, this enforcement often
the `user.blacklist`. For drivers using containers, this enforcement often
doesn't make sense and as such the default is set to:
* `exec`

View File

@ -42,7 +42,7 @@ A structured diff between the local and remote job is displayed to
give insight into what the scheduler will attempt to do and why.
If the job has specified the region, the `-region` flag and `NOMAD_REGION`
environment variable are overridden and the the job's region is used.
environment variable are overridden and the job's region is used.
Plan will return one of the following exit codes:
@ -81,7 +81,7 @@ To submit the job with version verification run:
nomad run -check-index 0 example.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```
@ -108,7 +108,7 @@ To submit the job with version verification run:
nomad run -check-index 15 example.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```
@ -135,7 +135,7 @@ To submit the job with version verification run:
nomad run -check-index 7 example.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```
@ -194,7 +194,7 @@ To submit the job with version verification run:
nomad run -check-index 7 example.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```

View File

@ -37,7 +37,7 @@ exhaustion, etc), then the exit code will be 2. Any other errors, including
client connection issues or internal errors, are indicated by exit code 1.
If the job has specified the region, the -region flag and NOMAD_REGION
environment variable are overridden and the the job's region is used.
environment variable are overridden and the job's region is used.
The run command will set the `vault_token` of the job based on the following
precedence, going from highest to lowest: the `-vault-token` flag, the
@ -50,7 +50,7 @@ precedence, going from highest to lowest: the `-vault-token` flag, the
## Run Options
* `-check-index`: If set, the job is only registered or
updated if the the passed job modify index matches the server side version.
updated if the passed job modify index matches the server side version.
If a check-index value of zero is passed, the job is only registered if it does
not yet exist. If a non-zero value is passed, it ensures that the job is being
updated from a known state. The use of this flag is most common in conjunction

View File

@ -54,7 +54,7 @@ environment variables.
</tr>
<tr>
<td>`NOMAD_IP_<label>`</td>
<td>The IP of the the port with the given label</td>
<td>The IP of the port with the given label</td>
</tr>
<tr>
<td>`NOMAD_PORT_<label>`</td>
@ -62,7 +62,7 @@ environment variables.
</tr>
<tr>
<td>`NOMAD_ADDR_<label>`</td>
<td>The IP:Port pair of the the port with the given label</td>
<td>The IP:Port pair of the port with the given label</td>
</tr>
<tr>
<td>`NOMAD_HOST_PORT_<label>`</td>

View File

@ -88,7 +88,7 @@ To submit the job with version verification run:
nomad run -check-index 0 docs.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```
@ -156,7 +156,7 @@ To submit the job with version verification run:
nomad run -check-index 131 docs.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```

View File

@ -58,7 +58,7 @@ To submit the job with version verification run:
nomad run -check-index 7 my-web.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```

View File

@ -168,7 +168,7 @@ To submit the job with version verification run:
nomad run -check-index 6 example.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```
@ -232,7 +232,7 @@ To submit the job with version verification run:
nomad run -check-index 42 example.nomad
When running the job with the check-index flag, the job will only be run if the
server side version matches the the job modify index returned. If the index has
server side version matches the job modify index returned. If the index has
changed, another user has modified the job and the plan's results are
potentially invalid.
```