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

fix: Add inspection of values for ENV flags #900

Merged
merged 2 commits into from
Oct 17, 2022

Conversation

fredcarle
Copy link
Collaborator

Relevant issue(s)

Resolves #684

Description

This PR improved the handling of ENV flags for our integration tests.

Tasks

  • I made sure the code is well commented, particularly hard-to-understand areas.
  • I made sure the repository-held documentation is changed accordingly.
  • I made sure the pull request title adheres to the conventional commit style (the subset used in the project can be found in tools/configs/chglog/config.yml).
  • I made sure to discuss its limitations such as threats to validity, vulnerability to mistake and misuse, robustness to invalidation of assumptions, resource requirements, ...

How has this been tested?

integration tests

Specify the platform(s) on which this was tested:

  • MacOS

@fredcarle fredcarle added area/testing Related to any test or testing suite action/no-benchmark Skips the action that runs the benchmark. labels Oct 16, 2022
@fredcarle fredcarle added this to the DefraDB v0.4 milestone Oct 16, 2022
@fredcarle fredcarle requested a review from a team October 16, 2022 22:46
@fredcarle fredcarle self-assigned this Oct 16, 2022
@fredcarle fredcarle marked this pull request as ready for review October 16, 2022 22:46
Copy link
Member

@shahzadlone shahzadlone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks soooooo much for this!

databaseDir = databaseDirValue
}

mapStore = true // default to true
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

todo: This is a behaviour change, as now if you only provide a badgerFile param, you will also get badger IM and map running too. This wasn't desirable before, and I doubt it is now.

If you are in faviour of the behaviour change, would recommend checking in with the rest of the team on discord first (I prefer the original, but pretty much never use it)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

didn't we want to remove the map store here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not yet, this PR doesnt drop support for it. The original comment also applies to badgerInMemory so we cant really just shrung this one off and assume/hope we'll drop support anyway

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah right there's even an issue about removing testing using map store #683

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right this was indeed a behaviour change. I had misunderstood the impact of that if statement. Should be fixed now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, approved :)

Copy link
Contributor

@AndrewSisley AndrewSisley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You appear to have changed the behaviour of the defaults - strongly suggest checking in with the rest of the team first

@codecov
Copy link

codecov bot commented Oct 17, 2022

Codecov Report

Merging #900 (8153172) into develop (4202950) will increase coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop     #900      +/-   ##
===========================================
+ Coverage    59.68%   59.69%   +0.01%     
===========================================
  Files          156      156              
  Lines        17306    17306              
===========================================
+ Hits         10329    10331       +2     
+ Misses        6042     6041       -1     
+ Partials       935      934       -1     
Impacted Files Coverage Δ
events/simple.go 86.76% <0.00%> (+2.94%) ⬆️

Copy link
Contributor

@AndrewSisley AndrewSisley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, cheers for sorting it out

@fredcarle fredcarle merged commit 98d2e09 into develop Oct 17, 2022
@fredcarle fredcarle deleted the fredcarle/fix/I684-ENV-flags-handling branch October 17, 2022 18:48
shahzadlone pushed a commit to shahzadlone/defradb that referenced this pull request Feb 23, 2024
Relevant issue(s)
Resolves sourcenetwork#684

Description
This PR improved the handling of ENV flags for our integration tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action/no-benchmark Skips the action that runs the benchmark. area/testing Related to any test or testing suite
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handle ENV flags properly (parse the string value)
4 participants