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

List "failed" entity IDs after execution

Open
  • Is something wrong?
#5 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
backend

Research direction

No source files, tests, or entry points are named. Start by locating the entity-processing execution path and the existing log message shown in the issue, then trace how failed or unprocessed entities are identified. Done means the execution output lists each failed entity ID individually and the relevant behavior is covered by a test.

Written by the indexing model from the issue text.

Description

I see log messages like this
screen shot 2016-12-06 at 9 48 44 pm

and I immediately want to know which entities didn't process so that I can then follow-up on why. It would be immensely helpful if the unprocessed entities were listed out individually. Something like

screen shot 2016-12-06 at 9 57 40 pm

What do you think @e0ipso?

Dominant language
PHP
Stars
1
Forks
0
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 e0ipso/entity_process_callback

All issues in e0ipso/entity_process_callback

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.