mirror of
https://github.com/percona/percona-toolkit.git
synced 2025-09-01 18:25:59 +00:00
Fixed typos found by the GitHub workflow
This commit is contained in:
@@ -9396,12 +9396,12 @@ sub main {
|
||||
};
|
||||
if ( $EVAL_ERROR ) {
|
||||
chomp $EVAL_ERROR;
|
||||
_die("Error checking --max-load or --critial-load: $EVAL_ERROR. "
|
||||
_die("Error checking --max-load or --critical-load: $EVAL_ERROR. "
|
||||
. "Check that the variables specified for --max-load and "
|
||||
. "--critical-load are spelled correctly and exist in "
|
||||
. "SHOW GLOBAL STATUS. Current values for these options are:\n"
|
||||
. " --max-load " . (join(',', @{$o->get('max-load')})) . "\n"
|
||||
. " --critial-load " . (join(',', @{$o->get('critical-load')}))
|
||||
. " --critical-load " . (join(',', @{$o->get('critical-load')}))
|
||||
, INVALID_PARAMETERS);
|
||||
}
|
||||
|
||||
|
@@ -529,7 +529,7 @@ list of supported platforms and versions.
|
||||
|
||||
In order to support IPv6 addresses to connect to MySQL, Perl DBD::MySQL driver v4.033_01 is
|
||||
required. Also, as stated in RFC 3986 L<https://www.ietf.org/rfc/rfc3986.txt> section 3.2.2
|
||||
brackes must be used to distinguish host and port.
|
||||
brackets must be used to distinguish host and port.
|
||||
Examples: L<https://metacpan.org/pod/DBD::mysql#port>
|
||||
|
||||
=head1 BUGS
|
||||
|
@@ -56,7 +56,7 @@ sub check_type_constraints {
|
||||
. (defined $val ? Lmo::Dumper($val) : 'undef') )
|
||||
}
|
||||
|
||||
# Nested (or parametized) constraints look like this: ArrayRef[CONSTRAINT] or
|
||||
# Nested (or parameritized) constraints look like this: ArrayRef[CONSTRAINT] or
|
||||
# Maybe[CONSTRAINT]. This function returns a coderef that implements one of
|
||||
# these.
|
||||
sub _nested_constraints {
|
||||
@@ -64,7 +64,7 @@ sub _nested_constraints {
|
||||
|
||||
my $inner_types;
|
||||
if ( $type =~ /\A(ArrayRef|Maybe)\[(.*)\]\z/ ) {
|
||||
# If the inner constraint -- the part within brackets -- is also a parametized
|
||||
# If the inner constraint -- the part within brackets -- is also a parametirized
|
||||
# constraint, then call this function recursively.
|
||||
$inner_types = _nested_constraints($1, $2);
|
||||
}
|
||||
|
@@ -507,7 +507,7 @@ sub find {
|
||||
}
|
||||
my $reason = 'Exceeds busy time';
|
||||
PTDEBUG && _d($reason);
|
||||
# Saving the reasons for each query in the objct is a bit nasty,
|
||||
# Saving the reasons for each query in the object is a bit nasty,
|
||||
# but the alternatives are worse:
|
||||
# - Saving internal data in the query
|
||||
# - Instead of using the stringified hashref as a key, using
|
||||
|
@@ -1140,7 +1140,7 @@ sub timestampdiff {
|
||||
# Some column types can store invalid values, like most of the temporal
|
||||
# types. When evaluated, invalid values return NULL. If the value is
|
||||
# NULL to begin with, then it is not invalid because NULL is valid.
|
||||
# For example, TO_DAYS('2009-00-00') evalues to NULL because that date
|
||||
# For example, TO_DAYS('2009-00-00') evaluates to NULL because that date
|
||||
# is invalid, even though it's storable.
|
||||
sub get_valid_end_points {
|
||||
my ( $self, %args ) = @_;
|
||||
|
Reference in New Issue
Block a user