Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`file` input deletes empty files but doesn't actually process them

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go

Research direction

Reproduce the issue with the emptyfile and newlinefile commands and the shown YAML configuration, then trace the file input processing path. Done means an empty file runs the configured processors and outputs before it is deleted when delete_on_finish is enabled.

Written by the indexing model from the issue text.

Description

bug needs investigation scanners

For instance, try echo -n > inputs/emptyfile vs echo > inputs/newlinefile. The empty file will send the message Consuming from file 'inputs/emptyfile' to the debug logger and will delete the file, but won't actually run any processors or outputs.

Example connect config:

logger:
  level: DEBUG

input:
  file:
    delete_on_finish: true
    paths:
    - inputs/*

pipeline:
  processors:
  - log:
      message: "This won't appear for empty files!"
Dominant language
Go
Stars
578
Forks
124
Avg merge
2d 13h
Merged PRs (30d)
10

Getting set up

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.

More from redpanda-data/benthos

All issues in redpanda-data/benthos

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.