2025-04-24 18:03:33 -07:00
/ * *
* @license
* Copyright 2025 Google LLC
* SPDX - License - Identifier : Apache - 2.0
* /
import fs from 'fs' ;
2025-04-27 18:57:10 -07:00
import path from 'path' ;
2025-05-06 10:44:40 -07:00
import os from 'os' ;
import crypto from 'crypto' ;
2025-04-24 18:03:33 -07:00
import { Config } from '../config/config.js' ;
2025-04-25 14:05:58 -07:00
import {
BaseTool ,
ToolResult ,
ToolCallConfirmationDetails ,
ToolExecuteConfirmationDetails ,
ToolConfirmationOutcome ,
2025-07-17 16:25:23 -06:00
Icon ,
2025-04-25 14:05:58 -07:00
} from './tools.js' ;
2025-08-08 04:33:42 -07:00
import { ToolErrorType } from './tool-error.js' ;
2025-04-27 18:57:10 -07:00
import { SchemaValidator } from '../utils/schemaValidator.js' ;
fix(shell): Improve error reporting for shell command failures
This commit enhances the tool to provide more informative feedback to the user when a shell command fails, especially in non-debug mode.
Previously, if a command terminated due to a signal (e.g., SIGPIPE during a with no upstream) or failed without producing stdout/stderr, the user would see no output, making it difficult to diagnose the issue.
Changes:
- Modified to update the logic.
- If a command produces no direct output but results in an error, signal, non-zero exit code, or user cancellation, a concise message indicating this outcome is now shown in .
- Utilized the existing utility from for consistent error message formatting, which also resolved previous TypeScript type inference issues.
This ensures users receive clearer feedback on command execution status, improving the tool's usability and aiding in troubleshooting.
Fixes https://b.corp.google.com/issues/417998119
2025-05-18 00:23:57 -07:00
import { getErrorMessage } from '../utils/errors.js' ;
2025-07-25 21:56:49 -04:00
import { summarizeToolOutput } from '../utils/summarizer.js' ;
import {
ShellExecutionService ,
ShellOutputEvent ,
} from '../services/shellExecutionService.js' ;
import { formatMemoryUsage } from '../utils/formatters.js' ;
2025-07-25 12:25:32 -07:00
import {
getCommandRoots ,
isCommandAllowed ,
stripShellWrapper ,
} from '../utils/shell-utils.js' ;
2025-06-02 14:50:12 -07:00
2025-07-25 21:56:49 -04:00
export const OUTPUT_UPDATE_INTERVAL_MS = 1000 ;
2025-04-24 18:03:33 -07:00
export interface ShellToolParams {
command : string ;
description? : string ;
2025-04-27 18:57:10 -07:00
directory? : string ;
2025-04-24 18:03:33 -07:00
}
2025-05-30 01:58:09 -07:00
2025-04-24 18:03:33 -07:00
export class ShellTool extends BaseTool < ShellToolParams , ToolResult > {
2025-06-09 08:57:30 -07:00
static Name : string = 'run_shell_command' ;
2025-07-25 12:25:32 -07:00
private allowlist : Set < string > = new Set ( ) ;
2025-04-24 18:03:33 -07:00
2025-05-02 09:31:18 -07:00
constructor ( private readonly config : Config ) {
2025-06-28 02:53:03 -07:00
super (
ShellTool . Name ,
'Shell' ,
` This tool executes a given shell command as \` bash -c <command> \` . Command can start background processes using \` & \` . Command is executed as a subprocess that leads its own process group. Command process group can be terminated as \` kill -- -PGID \` or signaled as \` kill -s SIGNAL -- -PGID \` .
Ignore folders files (#651)
# Add .gitignore-Aware File Filtering to gemini-cli
This pull request introduces .gitignore-based file filtering to the gemini-cli, ensuring that git-ignored files are automatically excluded from file-related operations and suggestions throughout the CLI. The update enhances usability, reduces noise from build artifacts and dependencies, and provides new configuration options for fine-tuning file discovery.
Key Improvements
.gitignore File Filtering
All @ (at) commands, file completions, and core discovery tools now honor .gitignore patterns by default.
Git-ignored files (such as node_modules/, dist/, .env, and .git) are excluded from results unless explicitly overridden.
The behavior can be customized via a new fileFiltering section in settings.json, including options for:
Turning .gitignore respect on/off.
Adding custom ignore patterns.
Allowing or excluding build artifacts.
Configuration & Documentation Updates
settings.json schema extended with fileFiltering options.
Documentation updated to explain new filtering controls and usage patterns.
Testing
New and updated integration/unit tests for file filtering logic, configuration merging, and edge cases.
Test coverage ensures .gitignore filtering works as intended across different workflows.
Internal Refactoring
Core file discovery logic refactored for maintainability and extensibility.
Underlying tools (ls, glob, read-many-files) now support git-aware filtering out of the box.
Co-authored-by: N. Taylor Mullen <ntaylormullen@google.com>
2025-06-03 21:40:46 -07:00
2025-07-25 12:25:32 -07:00
The following information is returned :
Command : Executed command .
Directory : Directory ( relative to project root ) where command was executed , or \ ` (root) \` .
Stdout : Output on stdout stream . Can be \ ` (empty) \` or partial on error and for any unwaited background processes.
Stderr : Output on stderr stream . Can be \ ` (empty) \` or partial on error and for any unwaited background processes.
Error : Error or \ ` (none) \` if no error was reported for the subprocess.
Exit Code : Exit code or \ ` (none) \` if terminated by signal.
Signal : Signal number or \ ` (none) \` if no signal was received.
Background PIDs : List of background processes started or \ ` (none) \` .
Process Group PGID : Process group started or \ ` (none) \` ` ,
2025-07-17 16:25:23 -06:00
Icon . Terminal ,
2025-06-28 02:53:03 -07:00
{
2025-08-11 16:12:41 -07:00
type : 'object' ,
Ignore folders files (#651)
# Add .gitignore-Aware File Filtering to gemini-cli
This pull request introduces .gitignore-based file filtering to the gemini-cli, ensuring that git-ignored files are automatically excluded from file-related operations and suggestions throughout the CLI. The update enhances usability, reduces noise from build artifacts and dependencies, and provides new configuration options for fine-tuning file discovery.
Key Improvements
.gitignore File Filtering
All @ (at) commands, file completions, and core discovery tools now honor .gitignore patterns by default.
Git-ignored files (such as node_modules/, dist/, .env, and .git) are excluded from results unless explicitly overridden.
The behavior can be customized via a new fileFiltering section in settings.json, including options for:
Turning .gitignore respect on/off.
Adding custom ignore patterns.
Allowing or excluding build artifacts.
Configuration & Documentation Updates
settings.json schema extended with fileFiltering options.
Documentation updated to explain new filtering controls and usage patterns.
Testing
New and updated integration/unit tests for file filtering logic, configuration merging, and edge cases.
Test coverage ensures .gitignore filtering works as intended across different workflows.
Internal Refactoring
Core file discovery logic refactored for maintainability and extensibility.
Underlying tools (ls, glob, read-many-files) now support git-aware filtering out of the box.
Co-authored-by: N. Taylor Mullen <ntaylormullen@google.com>
2025-06-03 21:40:46 -07:00
properties : {
2025-06-28 02:53:03 -07:00
command : {
2025-08-11 16:12:41 -07:00
type : 'string' ,
2025-06-28 02:53:03 -07:00
description : 'Exact bash command to execute as `bash -c <command>`' ,
} ,
description : {
2025-08-11 16:12:41 -07:00
type : 'string' ,
2025-06-28 02:53:03 -07:00
description :
'Brief description of the command for the user. Be specific and concise. Ideally a single sentence. Can be up to 3 sentences for clarity. No line breaks.' ,
} ,
directory : {
2025-08-11 16:12:41 -07:00
type : 'string' ,
2025-06-28 02:53:03 -07:00
description :
'(OPTIONAL) Directory to run the command in, if not the project root directory. Must be relative to the project root directory and must already exist.' ,
} ,
Ignore folders files (#651)
# Add .gitignore-Aware File Filtering to gemini-cli
This pull request introduces .gitignore-based file filtering to the gemini-cli, ensuring that git-ignored files are automatically excluded from file-related operations and suggestions throughout the CLI. The update enhances usability, reduces noise from build artifacts and dependencies, and provides new configuration options for fine-tuning file discovery.
Key Improvements
.gitignore File Filtering
All @ (at) commands, file completions, and core discovery tools now honor .gitignore patterns by default.
Git-ignored files (such as node_modules/, dist/, .env, and .git) are excluded from results unless explicitly overridden.
The behavior can be customized via a new fileFiltering section in settings.json, including options for:
Turning .gitignore respect on/off.
Adding custom ignore patterns.
Allowing or excluding build artifacts.
Configuration & Documentation Updates
settings.json schema extended with fileFiltering options.
Documentation updated to explain new filtering controls and usage patterns.
Testing
New and updated integration/unit tests for file filtering logic, configuration merging, and edge cases.
Test coverage ensures .gitignore filtering works as intended across different workflows.
Internal Refactoring
Core file discovery logic refactored for maintainability and extensibility.
Underlying tools (ls, glob, read-many-files) now support git-aware filtering out of the box.
Co-authored-by: N. Taylor Mullen <ntaylormullen@google.com>
2025-06-03 21:40:46 -07:00
} ,
required : [ 'command' ] ,
2025-06-28 02:53:03 -07:00
} ,
2025-05-30 13:59:05 -07:00
false , // output is not markdown
true , // output can be updated
2025-04-24 18:03:33 -07:00
) ;
2025-04-25 14:05:58 -07:00
}
getDescription ( params : ShellToolParams ) : string {
2025-04-27 18:57:10 -07:00
let description = ` ${ params . command } ` ;
2025-04-30 12:27:56 -07:00
// append optional [in directory]
2025-04-29 15:31:46 -07:00
// note description is needed even if validation fails due to absolute path
2025-04-28 08:17:52 -07:00
if ( params . directory ) {
2025-04-30 12:27:56 -07:00
description += ` [in ${ params . directory } ] ` ;
2025-04-28 08:17:52 -07:00
}
// append optional (description), replacing any line breaks with spaces
2025-04-27 18:57:10 -07:00
if ( params . description ) {
description += ` ( ${ params . description . replace ( /\n/g , ' ' ) } ) ` ;
}
return description ;
2025-04-25 14:05:58 -07:00
}
2025-04-27 18:57:10 -07:00
validateToolParams ( params : ShellToolParams ) : string | null {
2025-07-25 12:25:32 -07:00
const commandCheck = isCommandAllowed ( params . command , this . config ) ;
2025-07-07 14:03:36 +09:00
if ( ! commandCheck . allowed ) {
if ( ! commandCheck . reason ) {
console . error (
'Unexpected: isCommandAllowed returned false without a reason' ,
) ;
return ` Command is not allowed: ${ params . command } ` ;
}
return commandCheck . reason ;
2025-06-29 15:32:26 -04:00
}
2025-08-11 16:12:41 -07:00
const errors = SchemaValidator . validate (
this . schema . parametersJsonSchema ,
params ,
) ;
2025-07-07 23:48:44 -07:00
if ( errors ) {
return errors ;
2025-04-27 18:57:10 -07:00
}
if ( ! params . command . trim ( ) ) {
return 'Command cannot be empty.' ;
}
2025-07-25 12:25:32 -07:00
if ( getCommandRoots ( params . command ) . length === 0 ) {
2025-04-27 18:57:10 -07:00
return 'Could not identify command root to obtain permission from user.' ;
}
if ( params . directory ) {
if ( path . isAbsolute ( params . directory ) ) {
2025-07-31 05:38:20 +09:00
return 'Directory cannot be absolute. Please refer to workspace directories by their name.' ;
2025-04-27 18:57:10 -07:00
}
2025-07-31 05:38:20 +09:00
const workspaceDirs = this . config . getWorkspaceContext ( ) . getDirectories ( ) ;
const matchingDirs = workspaceDirs . filter (
( dir ) = > path . basename ( dir ) === params . directory ,
2025-04-27 18:57:10 -07:00
) ;
2025-07-31 05:38:20 +09:00
if ( matchingDirs . length === 0 ) {
return ` Directory ' ${ params . directory } ' is not a registered workspace directory. ` ;
}
if ( matchingDirs . length > 1 ) {
return ` Directory name ' ${ params . directory } ' is ambiguous as it matches multiple workspace directories. ` ;
2025-04-27 18:57:10 -07:00
}
}
2025-04-25 14:05:58 -07:00
return null ;
}
async shouldConfirmExecute (
params : ShellToolParams ,
2025-05-27 23:40:25 -07:00
_abortSignal : AbortSignal ,
2025-04-25 14:05:58 -07:00
) : Promise < ToolCallConfirmationDetails | false > {
2025-04-27 18:57:10 -07:00
if ( this . validateToolParams ( params ) ) {
return false ; // skip confirmation, execute call will fail immediately
}
2025-07-25 12:25:32 -07:00
const command = stripShellWrapper ( params . command ) ;
const rootCommands = [ . . . new Set ( getCommandRoots ( command ) ) ] ;
const commandsToConfirm = rootCommands . filter (
( command ) = > ! this . allowlist . has ( command ) ,
) ;
if ( commandsToConfirm . length === 0 ) {
2025-04-27 18:57:10 -07:00
return false ; // already approved and whitelisted
2025-04-25 14:05:58 -07:00
}
2025-07-25 12:25:32 -07:00
2025-04-25 14:05:58 -07:00
const confirmationDetails : ToolExecuteConfirmationDetails = {
2025-05-22 06:00:36 +00:00
type : 'exec' ,
2025-04-25 14:05:58 -07:00
title : 'Confirm Shell Command' ,
command : params.command ,
2025-07-25 12:25:32 -07:00
rootCommand : commandsToConfirm.join ( ', ' ) ,
2025-04-25 14:05:58 -07:00
onConfirm : async ( outcome : ToolConfirmationOutcome ) = > {
if ( outcome === ToolConfirmationOutcome . ProceedAlways ) {
2025-07-25 12:25:32 -07:00
commandsToConfirm . forEach ( ( command ) = > this . allowlist . add ( command ) ) ;
2025-04-25 14:05:58 -07:00
}
} ,
} ;
return confirmationDetails ;
2025-04-24 18:03:33 -07:00
}
2025-05-09 23:29:02 -07:00
async execute (
params : ShellToolParams ,
2025-07-25 12:25:32 -07:00
signal : AbortSignal ,
updateOutput ? : ( output : string ) = > void ,
2025-05-09 23:29:02 -07:00
) : Promise < ToolResult > {
2025-07-25 12:25:32 -07:00
const strippedCommand = stripShellWrapper ( params . command ) ;
const validationError = this . validateToolParams ( {
. . . params ,
command : strippedCommand ,
} ) ;
2025-04-27 18:57:10 -07:00
if ( validationError ) {
return {
2025-08-08 04:33:42 -07:00
llmContent : ` Could not execute command due to invalid parameters: ${ validationError } ` ,
2025-07-25 12:25:32 -07:00
returnDisplay : validationError ,
2025-08-08 04:33:42 -07:00
error : {
message : validationError ,
type : ToolErrorType . INVALID_TOOL_PARAMS ,
} ,
2025-04-27 18:57:10 -07:00
} ;
}
2025-07-25 12:25:32 -07:00
if ( signal . aborted ) {
2025-06-08 15:42:49 -07:00
return {
llmContent : 'Command was cancelled by user before it could start.' ,
returnDisplay : 'Command cancelled by user.' ,
} ;
}
2025-06-09 12:19:42 -07:00
const isWindows = os . platform ( ) === 'win32' ;
2025-06-15 02:19:19 -07:00
const tempFileName = ` shell_pgrep_ ${ crypto
. randomBytes ( 6 )
. toString ( 'hex' ) } . tmp ` ;
const tempFilePath = path . join ( os . tmpdir ( ) , tempFileName ) ;
2025-05-06 10:44:40 -07:00
2025-07-25 21:56:49 -04:00
try {
// pgrep is not available on Windows, so we can't get background PIDs
const commandToExecute = isWindows
? strippedCommand
: ( ( ) = > {
// wrap command to append subprocess pids (via pgrep) to temporary file
let command = strippedCommand . trim ( ) ;
if ( ! command . endsWith ( '&' ) ) command += ';' ;
return ` { ${ command } }; __code= $ ?; pgrep -g 0 > ${ tempFilePath } 2>&1; exit $ __code; ` ;
} ) ( ) ;
2025-04-27 18:57:10 -07:00
2025-07-25 21:56:49 -04:00
const cwd = path . resolve (
this . config . getTargetDir ( ) ,
params . directory || '' ,
) ;
2025-05-30 01:58:09 -07:00
2025-07-25 21:56:49 -04:00
let cumulativeStdout = '' ;
let cumulativeStderr = '' ;
2025-05-30 01:58:09 -07:00
2025-07-25 21:56:49 -04:00
let lastUpdateTime = Date . now ( ) ;
let isBinaryStream = false ;
2025-04-27 18:57:10 -07:00
2025-07-25 21:56:49 -04:00
const { result : resultPromise } = ShellExecutionService . execute (
commandToExecute ,
cwd ,
( event : ShellOutputEvent ) = > {
if ( ! updateOutput ) {
return ;
}
2025-04-27 18:57:10 -07:00
2025-07-25 21:56:49 -04:00
let currentDisplayOutput = '' ;
let shouldUpdate = false ;
2025-05-09 23:29:02 -07:00
2025-07-25 21:56:49 -04:00
switch ( event . type ) {
case 'data' :
if ( isBinaryStream ) break ; // Don't process text if we are in binary mode
if ( event . stream === 'stdout' ) {
cumulativeStdout += event . chunk ;
} else {
cumulativeStderr += event . chunk ;
}
currentDisplayOutput =
cumulativeStdout +
( cumulativeStderr ? ` \ n ${ cumulativeStderr } ` : '' ) ;
if ( Date . now ( ) - lastUpdateTime > OUTPUT_UPDATE_INTERVAL_MS ) {
shouldUpdate = true ;
}
break ;
case 'binary_detected' :
isBinaryStream = true ;
currentDisplayOutput =
'[Binary output detected. Halting stream...]' ;
shouldUpdate = true ;
break ;
case 'binary_progress' :
isBinaryStream = true ;
currentDisplayOutput = ` [Receiving binary output... ${ formatMemoryUsage (
event . bytesReceived ,
) } received ] ` ;
if ( Date . now ( ) - lastUpdateTime > OUTPUT_UPDATE_INTERVAL_MS ) {
shouldUpdate = true ;
2025-06-09 12:19:42 -07:00
}
2025-07-25 21:56:49 -04:00
break ;
default : {
throw new Error ( 'An unhandled ShellOutputEvent was found.' ) ;
2025-06-09 12:19:42 -07:00
}
2025-05-09 23:29:02 -07:00
}
2025-04-27 18:57:10 -07:00
2025-07-25 21:56:49 -04:00
if ( shouldUpdate ) {
updateOutput ( currentDisplayOutput ) ;
lastUpdateTime = Date . now ( ) ;
}
} ,
signal ,
) ;
2025-05-09 23:29:02 -07:00
2025-07-25 21:56:49 -04:00
const result = await resultPromise ;
const backgroundPIDs : number [ ] = [ ] ;
if ( os . platform ( ) !== 'win32' ) {
if ( fs . existsSync ( tempFilePath ) ) {
const pgrepLines = fs
. readFileSync ( tempFilePath , 'utf8' )
. split ( '\n' )
. filter ( Boolean ) ;
for ( const line of pgrepLines ) {
if ( ! /^\d+$/ . test ( line ) ) {
console . error ( ` pgrep: ${ line } ` ) ;
}
const pid = Number ( line ) ;
if ( pid !== result . pid ) {
backgroundPIDs . push ( pid ) ;
}
2025-06-09 12:19:42 -07:00
}
2025-07-25 21:56:49 -04:00
} else {
if ( ! signal . aborted ) {
console . error ( 'missing pgrep output' ) ;
2025-06-09 12:19:42 -07:00
}
2025-05-06 10:44:40 -07:00
}
}
2025-07-25 21:56:49 -04:00
let llmContent = '' ;
if ( result . aborted ) {
llmContent = 'Command was cancelled by user before it could complete.' ;
if ( result . output . trim ( ) ) {
llmContent += ` Below is the output (on stdout and stderr) before it was cancelled: \ n ${ result . output } ` ;
} else {
llmContent += ' There was no output before it was cancelled.' ;
}
2025-05-27 13:47:40 -07:00
} else {
2025-07-25 21:56:49 -04:00
// Create a formatted error string for display, replacing the wrapper command
// with the user-facing command.
const finalError = result . error
? result . error . message . replace ( commandToExecute , params . command )
: '(none)' ;
llmContent = [
` Command: ${ params . command } ` ,
` Directory: ${ params . directory || '(root)' } ` ,
` Stdout: ${ result . stdout || '(empty)' } ` ,
` Stderr: ${ result . stderr || '(empty)' } ` ,
` Error: ${ finalError } ` , // Use the cleaned error string.
` Exit Code: ${ result . exitCode ? ? '(none)' } ` ,
` Signal: ${ result . signal ? ? '(none)' } ` ,
` Background PIDs: ${
backgroundPIDs . length ? backgroundPIDs . join ( ', ' ) : '(none)'
} ` ,
` Process Group PGID: ${ result . pid ? ? '(none)' } ` ,
] . join ( '\n' ) ;
2025-05-27 13:47:40 -07:00
}
2025-04-28 15:05:36 -07:00
2025-07-25 21:56:49 -04:00
let returnDisplayMessage = '' ;
if ( this . config . getDebugMode ( ) ) {
returnDisplayMessage = llmContent ;
fix(shell): Improve error reporting for shell command failures
This commit enhances the tool to provide more informative feedback to the user when a shell command fails, especially in non-debug mode.
Previously, if a command terminated due to a signal (e.g., SIGPIPE during a with no upstream) or failed without producing stdout/stderr, the user would see no output, making it difficult to diagnose the issue.
Changes:
- Modified to update the logic.
- If a command produces no direct output but results in an error, signal, non-zero exit code, or user cancellation, a concise message indicating this outcome is now shown in .
- Utilized the existing utility from for consistent error message formatting, which also resolved previous TypeScript type inference issues.
This ensures users receive clearer feedback on command execution status, improving the tool's usability and aiding in troubleshooting.
Fixes https://b.corp.google.com/issues/417998119
2025-05-18 00:23:57 -07:00
} else {
2025-07-25 21:56:49 -04:00
if ( result . output . trim ( ) ) {
returnDisplayMessage = result . output ;
} else {
if ( result . aborted ) {
returnDisplayMessage = 'Command cancelled by user.' ;
} else if ( result . signal ) {
returnDisplayMessage = ` Command terminated by signal: ${ result . signal } ` ;
} else if ( result . error ) {
returnDisplayMessage = ` Command failed: ${ getErrorMessage (
result . error ,
) } ` ;
} else if ( result . exitCode !== null && result . exitCode !== 0 ) {
returnDisplayMessage = ` Command exited with code: ${ result . exitCode } ` ;
}
// If output is empty and command succeeded (code 0, no error/signal/abort),
// returnDisplayMessage will remain empty, which is fine.
fix(shell): Improve error reporting for shell command failures
This commit enhances the tool to provide more informative feedback to the user when a shell command fails, especially in non-debug mode.
Previously, if a command terminated due to a signal (e.g., SIGPIPE during a with no upstream) or failed without producing stdout/stderr, the user would see no output, making it difficult to diagnose the issue.
Changes:
- Modified to update the logic.
- If a command produces no direct output but results in an error, signal, non-zero exit code, or user cancellation, a concise message indicating this outcome is now shown in .
- Utilized the existing utility from for consistent error message formatting, which also resolved previous TypeScript type inference issues.
This ensures users receive clearer feedback on command execution status, improving the tool's usability and aiding in troubleshooting.
Fixes https://b.corp.google.com/issues/417998119
2025-05-18 00:23:57 -07:00
}
}
2025-07-12 21:09:12 -07:00
2025-07-25 21:56:49 -04:00
const summarizeConfig = this . config . getSummarizeToolOutputConfig ( ) ;
if ( summarizeConfig && summarizeConfig [ this . name ] ) {
const summary = await summarizeToolOutput (
llmContent ,
this . config . getGeminiClient ( ) ,
signal ,
summarizeConfig [ this . name ] . tokenBudget ,
) ;
return {
llmContent : summary ,
returnDisplay : returnDisplayMessage ,
} ;
}
2025-07-15 10:22:31 -07:00
return {
2025-07-25 21:56:49 -04:00
llmContent ,
2025-07-15 10:22:31 -07:00
returnDisplay : returnDisplayMessage ,
} ;
2025-07-25 21:56:49 -04:00
} finally {
if ( fs . existsSync ( tempFilePath ) ) {
fs . unlinkSync ( tempFilePath ) ;
}
2025-07-15 10:22:31 -07:00
}
2025-04-24 18:03:33 -07:00
}
}