Skip to content

Conversation

@cmaynard-ngwpc
Copy link

@cmaynard-ngwpc cmaynard-ngwpc commented Sep 25, 2025

This WARNING log entry was producing the same message thousands of times with no benefit gained after the 1st log entry. Throttled this to a single entry in the log.

Additions

  • Add flag to indicate the groundwater flux warning message log state
  • Add if test of flag and if not set, log the entry and set the flag.

Changes

  • Indented block after test for groundwater flux where the log message is generated.

Checklist

  • PR has an informative and human-readable title
  • Changes are limited to a single goal (no scope creep)
  • Code can be automatically merged (no conflicts)
  • Code follows project standards (link if applicable)
  • Passes all existing automated tests
  • Any change in functionality is tested
  • New functions are documented (with a description, list of inputs, and expected output)
  • Placeholder code is flagged / future todos are captured in comments
  • Visually tested in supported browsers and devices (see checklist below 👇)
  • Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
  • Reviewers requested with the Reviewers tool ➡️

@cmaynard-ngwpc cmaynard-ngwpc merged commit 54e5de1 into development Sep 25, 2025
1 check failed
@cmaynard-ngwpc cmaynard-ngwpc deleted the cmaynard_throttle_groundwater_flux branch September 25, 2025 20:03
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.

1 participant