robotframework / robotframework/RIDE
Message Log disable/enable destroys existing log
Open
Nobody has claimed this yet.
enhancement
prio-medium
- Dominant language
- Python
- Stars
- 1k
- Forks
- 385
- Avg merge
- 13m
- Merged PRs (30d)
- 2
Description
Originally submitted to Google Code by @mikahanninen on 16 Apr 2013
If you have messages in the log and disable, and then re-enable the log it does not have anything on it.
Would be good if it would show the latest message log if available.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in RIDE's Message Log: add messages, disable the log, and enable it again. Trace the Message Log entry point and existing tests, if any, to determine where the latest log is lost. Done means re-enabling the log displays the messages that existed before it was disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100