Bugs
Open and resolved bugs across all Halfmoon products
Colours Shift on CopyJonahOur brand green comes out about a shade off in the notes. Close enough that nobody queried it for a month, far enough that an engineer built a component with the wrong value.Support Team A colour that is nearly right is worse than one that is obviously wrong, because it ships. On it.
BrambleBristol Reads EarlyRobEverywhere else I've checked is right. Bristol reads about an hour early for two or three days after a spring tide, then sorts itself out. I sail there most weekends so I've now watched it happen twice.Support Team Rob, the detail that it corrects itself after a couple of days narrows this a lot. Thank you. We'll post here when we know more.
TidelineReviews Generated FilesBeaIt reviews everything in our build folder and our generated API client, which is 80% of the findings and none of the useful ones. Both are in .gitignore.Support Team Findings nobody can act on are worse than no findings, because they train you to skim. Looking now.
CragReceipt Scan MisreadsMarekIt reads the service charge as a separate item and then adds it again as a percentage, so our meal came out about 24% over. Only on receipts where the service is printed as its own line.Support Team Counting the same charge twice is worse than not reading it at all, because the number still looks plausible. On it now.
Kettle
BrambleBristol Reads EarlyRobEverywhere else I've checked is right. Bristol reads about an hour early for two or three days after a spring tide, then sorts itself out. I sail there most weekends so I've now watched it happen twice.Support Team Rob, the detail that it corrects itself after a couple of days narrows this a lot. Thank you. We'll post here when we know more.TidelineReviews Generated FilesBeaIt reviews everything in our build folder and our generated API client, which is 80% of the findings and none of the useful ones. Both are in .gitignore.Support Team Findings nobody can act on are worse than no findings, because they train you to skim. Looking now.CragReceipt Scan MisreadsMarekIt reads the service charge as a separate item and then adds it again as a percentage, so our meal came out about 24% over. Only on receipts where the service is printed as its own line.Support Team Counting the same charge twice is worse than not reading it at all, because the number still looks plausible. On it now.Kettle