mbucc / mbucc/ai

logtail doesn't like -s arg when used with -o

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

Description

mark@marks-mbp:~/src/ai% ./logtail -s testing/1.log -o testing/1.offset                                                                                                                                 <<<
ERROR 181 - Input parameter error, testing/1.log.
mark@marks-mbp:~/src/ai% ./logtail testing/1.log -s -o testing/1.offset

  Usage: logtail [log_file] <offset_file>
     or: logtail [-l log_file] <-o offset_file> <-d rolled_log_directory>
       : <-f rolled_log_filename> <-r> <-s> <-t> <-b>
     or: logtail -h

mark@marks-mbp:~/src/ai% ./logtail testing/1.log -o testing/1.offset -s

  Usage: logtail [log_file] <offset_file>
     or: logtail [-l log_file] <-o offset_file> <-d rolled_log_directory>
       : <-f rolled_log_filename> <-r> <-s> <-t> <-b>
     or: logtail -h

mark@marks-mbp:~/src/ai% ./logtail testing/1.log -s
mark@marks-mbp:~/src/ai% echo $?
0
mark@marks-mbp:~/src/ai% 

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the three command invocations shown against ./logtail and inspect its argument parsing. The issue does not define the intended interaction between -s and -o, so clarify the expected syntax before changing anything. Done should include a check that the supported invocation no longer produces the reported parameter error or usage output.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.