Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Make retest optional for in-memory flumelogs #2

Closed
wants to merge 1 commit into from

Conversation

christianbundy
Copy link
Member

This change would be necessary to resolve flumedb/flumeview-level#13.

@christianbundy
Copy link
Member Author

Actually I haven't tested this, so I don't want anyone to waste time thinking about it until I'm sure it works. Sorry for the noise!

@dominictarr
Copy link
Contributor

oh, I was just about to merge then I saw it wasn't tested!

@dominictarr dominictarr changed the title Make retest optional for in-memory flumelogs WIP: Make retest optional for in-memory flumelogs Dec 20, 2018
@dominictarr
Copy link
Contributor

should probably make retest into an options object where retest defaults to true.
hmm, I think i'd call it reload. this tests that the view correctly reloads the state again. This is pretty important to cover, certainly this test has caught problems!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[question] can only be used with a log that provides a directory
2 participants