bcgov / bcgov/wps

HFI Calc: follow up with KFC/PGFC to identify fuel types bug

Open
#2,182 0 comments 0 reactions 0 assignees View on GitHub
Bug
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

**Describe the Bug**
A couple of sprints ago, HFI Calc users in KFC & PGFC reported issues where the fuel type displayed for a particular station (West Kelowna station in KFC, McBridge station in PGFC) changes for different users (but who I think are using the same IDIR account to log in). In solitary investigation of the bug, I wasn't able to reproduce the issue.

Recommend that we sit in on a prep morning with either KFC or PGFC to observe & try to identify what they might be doing that causes the bug to appear.

**Context**
We've found and fixed one possible cause of the bug, related to prep period date ranges. Haven't heard back from the fire centres since the bug was pushed to prod, but suspect that something else was causing it. We might first just want to follow up with RB in KFC or PO in PGFC to see if they have encountered the bug in the last week or so.
Might also be worthwhile trying one more time to reproduce it in our own.

**Actual Behaviour**
Sometimes West Kelowna displays fuel type C7, other times C7B.
Sometimes McBride displays fuel type C3, other times M2 50%.

** Steps To Reproduce**
Steps to reproduce the behaviour:
1. That's the problem, we don't know the steps to reproduce.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Version [e.g. 22]

**Additional context**
Add any other context about the problem here.

Contributor guide

Open the contributing guide

Research direction

No source file or test is identified. Start by following up with RB in KFC or PO in PGFC and, if possible, observe a prep morning or attempt reproduction; done means identifying the trigger and documenting reliable reproduction steps.

Written by the indexing model from the issue text.

Assessment

Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.