linkedin / linkedin/flashback

Where are scenes supposed to write to on disk?

Open
#16 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
580
Forks
48
PR merge metrics
No merged PRs in 30d

Description

I've been noticing some non-static behavior that is throwing me off. Using the "golden flow" example in the readme, on Windows 10, I've seen my test1 file appear in the following locations

- Directly on **C:\\**
- In **\flashback-admin** inside the repo
- Not appearing at all, but both startFlashback and shutDownFlashback respond with a 200 OK.

Why am I seeing it appear (or not appear) in different locations when I am following the same workflow?

This is the post body I am using to start Flashback:

```
{
"sceneMode": "record",
"sceneName": "test1",
"matchRule": "matchEntireRequest",
"scenePath": "/tmp",
"proxyHost": "localhost",
"proxyPort": "5555"
}
```

Contributor guide

Open the contributing guide

Research direction

Start with the README's “golden flow” example and reproduce the Windows 10 workflow using the supplied startFlashback request, especially its scenePath of /tmp. Trace where the test1 scene is written and how startFlashback and shutDownFlashback report success. Done means the storage location and the conditions for a missing scene are explained or made consistent.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.