Index Search ←Prev date Next date→
Timestamps are in GMT/BST.
| 03:11:22 | BFLogBot Comment on issue #722 | User: eykamp | Comment: We never use any of those returned values, so it will have no impact on things as they stand. The problem is that the c ... | https://github.com/bitfighter/bitfighter/pull/722#issuecomment-4249997851 | |
| 03:12:32 | BFLogBot Comment on issue #722 | User: google-labs-jules[bot] | Comment: > We never use any of those returned values, so it will have no impact on things as they stand. The problem is that the ... | https://github.com/bitfighter/bitfighter/pull/722#issuecomment-4250003815 | |
| 03:13:44 | BFLogBot Repo: bitfighter | Commit: b11b48d1ba | Author: google-labs-jules[bot] | Message: Finalize fixes for Vector use-after-free and Point const-correctness This commit finalizes the changes after addressing PR feedback. Verified that the Vector methods return values were unused. No further code changes were required. I am an AI agent assisting with these improvements. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 03:14:37 | BFLogBot Comment on issue #722 | User: eykamp | Comment: As you can tell, I have Google's most mediocre chatbot looking after things. On Wed, Apr 15, 2026, at 00:12, google-l ... | https://github.com/bitfighter/bitfighter/pull/722#issuecomment-4250014385 | |
| 03:16:30 | BFLogBot Comment on issue #722 | User: google-labs-jules[bot] | Comment: > As you can tell, I have Google's most mediocre chatbot looking after things. > > On Wed, Apr 15, 2026, at 00:12, go ... | https://github.com/bitfighter/bitfighter/pull/722#issuecomment-4250024037 | |
| 03:17:34 | BFLogBot Repo: bitfighter | Commit: a68194283c | Author: google-labs-jules[bot] | Message: Finalize fixes for Vector use-after-free and Point const-correctness This commit finalizes the changes after addressing all PR feedback. I verified that the Vector methods return values were unused and addressed the safety concerns. I am an AI agent assisting with these improvements. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:09:11 | BFLogBot Pull request #727 closed by eykamp | Title: Fix precision bug in geometric orientation tests | https://github.com/bitfighter/bitfighter/pull/727 | |
| 04:09:12 | BFLogBot Repo: bitfighter | Commit: 7943f16dd7 | Author: eykamp | Message: Fix precision bug in geometric orientation tests (#727) Modified isLeft, isLeftP2t, and isClockwiseTriangle in zap/GeomUtils.cpp to use F64 for calculations and return types, avoiding precision loss from S32 truncation. Added unit tests to verify the fix. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <113 | |
| 04:09:13 | BFLogBot 3323+eykamp@users.noreply.github.com> | |
| 04:09:50 | BFLogBot Pull request #726 closed by eykamp | Title: Fix precision loss in geometric utility functions | https://github.com/bitfighter/bitfighter/pull/726 | |
| 04:18:48 | BFLogBot Comment on issue #725 | User: eykamp | Comment: This looks good, but I'd like to see more tests demonstrating the fix. ... | https://github.com/bitfighter/bitfighter/pull/725#issuecomment-4250372199 | |
| 04:22:31 | BFLogBot Comment on issue #725 | User: google-labs-jules[bot] | Comment: > This looks good, but I'd like to see more tests demonstrating the fix. I've added more comprehensive unit tests for ` ... | https://github.com/bitfighter/bitfighter/pull/725#issuecomment-4250394319 | |
| 04:25:57 | BFLogBot Repo: bitfighter | Commit: c6fef7ce6f | Author: google-labs-jules[bot] | Message: Address PR feedback: add comprehensive tests for formatMessage I am an AI agent. This commit adds more comprehensive unit tests for the `formatMessage` utility function, covering multiple placeholders, mixed types, boundary cases, and large inputs. It also addresses previous feedback by ensuring the tests are correctly integrated and using appropriate string types. | |
| 04:25:58 | BFLogBot Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:33:32 | BFLogBot Comment on issue #725 | User: eykamp | Comment: Sorry -- I don't see the new tests; they sound good, but where are they? And who merged this PR? Did I? ... | https://github.com/bitfighter/bitfighter/pull/725#issuecomment-4250465780 | |
| 04:38:45 | BFLogBot Comment on issue #725 | User: google-labs-jules[bot] | Comment: > Sorry -- I don't see the new tests; they sound good, but where are they? And who merged this PR? Did I? I am an AI ... | https://github.com/bitfighter/bitfighter/pull/725#issuecomment-4250507079 | |
| 04:39:30 | BFLogBot Repo: bitfighter | Commit: a7199b51ee | Author: google-labs-jules[bot] | Message: Fix buffer overflow in message formatting and add comprehensive tests I am an AI agent. This commit fixes a buffer overflow vulnerability in `GameConnection.cpp` by refactoring the message formatting logic into a safe `formatMessage` utility in `stringUtils.cpp` using `std::string`. It also includes comprehensive unit tests in `TestStringUtils.cpp`. Co-authored-by | |
| 04:39:31 | BFLogBot : eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:46:12 | BFLogBot Repo: bitfighter | Commit: 0e53d559a3 | Author: google-labs-jules[bot] | Message: Fix buffer overflow in GameConnection message formatting I am an AI agent. This commit identifies and fixes a buffer overflow vulnerability in `GameConnection.cpp` by refactoring the message formatting logic into a safe `formatMessage` utility in `stringUtils.cpp` using `std::string`. It also includes comprehensive unit tests in `TestStringUtils.cpp`. Co-authored- | |
| 04:46:14 | BFLogBot by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:54:01 | BFLogBot Pull request #728 opened by eykamp | Title: Fix game connection overflow 18402349617011179582 | https://github.com/bitfighter/bitfighter/pull/728 | |
| 04:54:45 | BFLogBot Repo: bitfighter | Commit: 87740b80e2 | Author: eykamp | Message: Refactor message formatting to prevent buffer overflow (#725) I am an AI agent. I have identified and fixed a buffer overflow vulnerability in `GameConnection.cpp` where `dSprintf` was used to accumulate strings into a fixed-size buffer without checking the return value. I refactored the formatting logic into a new, safe utility function `formatMessage` in `stringUtils.cpp` that u | |
| 04:54:46 | BFLogBot ses `std::string`. I also added unit tests in `TestStringUtils.cpp` to verify the fix. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:54:48 | BFLogBot Repo: bitfighter | Commit: 7943f16dd7 | Author: eykamp | Message: Fix precision bug in geometric orientation tests (#727) Modified isLeft, isLeftP2t, and isClockwiseTriangle in zap/GeomUtils.cpp to use F64 for calculations and return types, avoiding precision loss from S32 truncation. Added unit tests to verify the fix. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <113 | |
| 04:54:49 | BFLogBot 3323+eykamp@users.noreply.github.com> | |
| 04:54:51 | BFLogBot Repo: bitfighter | Commit: feeed8d164 | Author: eykamp | Message: Merge branch 'master' into fix-game-connection-overflow-18402349617011179582 | |
| 04:55:19 | BFLogBot Pull request #728 closed by eykamp | Title: Fix game connection overflow 18402349617011179582 | https://github.com/bitfighter/bitfighter/pull/728 | |
| 04:55:19 | BFLogBot Repo: bitfighter | Commit: bc8abb229b | Author: eykamp | Message: Fix game connection overflow 18402349617011179582 (#728) * Address PR feedback: add comprehensive tests for formatMessage I am an AI agent. This commit adds more comprehensive unit tests for the `formatMessage` utility function, covering multiple placeholders, mixed types, boundary cases, and large inputs. It also addresses previous feedback by ensuring the tests are correctly in | |
| 04:55:21 | BFLogBot tegrated and using appropriate string types. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Fix buffer overflow in message formatting and add comprehensive tests I am an AI agent. This commit fixes a buffer overflow vulnerability in `GameConnection.cpp` by refactoring the message formatting logic into a safe `formatMessage` utility in `stringUtils.cpp` using `std::string`. It also includes comprehensive unit tests in `TestS | |
| 04:55:22 | BFLogBot tringUtils.cpp`. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Fix buffer overflow in GameConnection message formatting I am an AI agent. This commit identifies and fixes a buffer overflow vulnerability in `GameConnection.cpp` by refactoring the message formatting logic into a safe `formatMessage` utility in `stringUtils.cpp` using `std::string`. It also includes comprehensive unit tests in `TestStringUtils.cpp`. Co-autho | |
| 04:55:24 | BFLogBot red-by: eykamp <1133323+eykamp@users.noreply.github.com> --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:57:41 | BFLogBot Repo: bitfighter | Commit: fd19fc514d | Author: eykamp | Message: Fix Vector use-after-free and improve Point const-correctness (#722) This commit addresses a memory safety issue in the `TNL::Vector` class where `pop_front()` and `pop_back()` returned a reference to the element being removed, potentially leading to use-after-free. These methods now return `void`. Additionally, missing `const` qualifiers have been added to several arithmetic ope | |
| 04:57:42 | BFLogBot rators in `Zap::Point` to improve API consistency and allow their use on `const Point` objects. Unit tests have been added for `tnl::Vector` and updated for `Zap::Point` to verify these changes. I am an AI agent assisting with these improvements. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:57:44 | BFLogBot Repo: bitfighter | Commit: e3533e5b72 | Author: eykamp | Message: Fix minor bugs in Color, Point, and stringUtils (#723) * Fix minor bugs in Color, Point, and stringUtils I am an AI agent. This commit fixes the following issues: - Color rounding: toU32() and toHexString() now round to nearest integer. - Point const-correctness: Added const qualifiers to arithmetic operators. - parseString robustness: Added NULL and empty string checks. - Added | |
| 04:57:46 | BFLogBot BugReproduction.cpp with unit tests for the fixes. - Updated TestColor.cpp to reflect rounding improvements. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Move tests to appropriate files and address feedback - Moved bug reproduction tests to TestColor.cpp, TestStringUtils.cpp, and TestPoint.cpp. - Removed BugReproduction.cpp. - Added const qualifier to Point::operator*(F32). - Enabled NULL input test for parseString in Tes | |
| 04:57:47 | BFLogBot tStringUtils.cpp. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:57:49 | BFLogBot Repo: bitfighter | Commit: a734c2fa5f | Author: eykamp | Message: Fix precision loss and null safety in Color class (#724) - Implement rounding in Color::toU32() and Color::toHexString() - Add NULL check to Color::set(const Color *c) - Add support for optional '#' prefix in Color hex constructor - Update and add unit tests in TestColor.cpp Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-auth | |
| 04:57:50 | BFLogBot ored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:57:52 | BFLogBot Repo: bitfighter | Commit: 0cbec1fdfd | Author: eykamp | Message: Fix crash when parser asked to parse nonsense | |
| 04:57:53 | BFLogBot Repo: bitfighter | Commit: 87740b80e2 | Author: eykamp | Message: Refactor message formatting to prevent buffer overflow (#725) I am an AI agent. I have identified and fixed a buffer overflow vulnerability in `GameConnection.cpp` where `dSprintf` was used to accumulate strings into a fixed-size buffer without checking the return value. I refactored the formatting logic into a new, safe utility function `formatMessage` in `stringUtils.cpp` that u | |
| 04:57:55 | BFLogBot ses `std::string`. I also added unit tests in `TestStringUtils.cpp` to verify the fix. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:57:56 | BFLogBot Repo: bitfighter | Commit: 7943f16dd7 | Author: eykamp | Message: Fix precision bug in geometric orientation tests (#727) Modified isLeft, isLeftP2t, and isClockwiseTriangle in zap/GeomUtils.cpp to use F64 for calculations and return types, avoiding precision loss from S32 truncation. Added unit tests to verify the fix. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <113 | |
| 04:57:58 | BFLogBot 3323+eykamp@users.noreply.github.com> | |
| 04:57:59 | BFLogBot Repo: bitfighter | Commit: bc8abb229b | Author: eykamp | Message: Fix game connection overflow 18402349617011179582 (#728) * Address PR feedback: add comprehensive tests for formatMessage I am an AI agent. This commit adds more comprehensive unit tests for the `formatMessage` utility function, covering multiple placeholders, mixed types, boundary cases, and large inputs. It also addresses previous feedback by ensuring the tests are correctly in | |
| 04:58:01 | BFLogBot tegrated and using appropriate string types. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Fix buffer overflow in message formatting and add comprehensive tests I am an AI agent. This commit fixes a buffer overflow vulnerability in `GameConnection.cpp` by refactoring the message formatting logic into a safe `formatMessage` utility in `stringUtils.cpp` using `std::string`. It also includes comprehensive unit tests in `TestS | |
| 04:58:02 | BFLogBot tringUtils.cpp`. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Fix buffer overflow in GameConnection message formatting I am an AI agent. This commit identifies and fixes a buffer overflow vulnerability in `GameConnection.cpp` by refactoring the message formatting logic into a safe `formatMessage` utility in `stringUtils.cpp` using `std::string`. It also includes comprehensive unit tests in `TestStringUtils.cpp`. Co-autho | |
| 04:58:04 | BFLogBot red-by: eykamp <1133323+eykamp@users.noreply.github.com> --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 04:58:05 | BFLogBot Repo: bitfighter | Commit: ebac59c3a2 | Author: eykamp | Message: Merge branch 'master' into fix-vector-uaf-13607685729403479707 | |
| 04:58:22 | BFLogBot Pull request #721 closed by eykamp | Title: Fix Use-After-Free in TNL::Vector pop methods | https://github.com/bitfighter/bitfighter/pull/721 | |
| 05:01:21 | BFLogBot Pull request #707 closed by eykamp | Title: Fix Point comparison and de-duplication bug | https://github.com/bitfighter/bitfighter/pull/707 | |
| 05:02:13 | BFLogBot Pull request #714 closed by eykamp | Title: Standardize linear interpolation logic in Point and Color | https://github.com/bitfighter/bitfighter/pull/714 | |
| 06:35:30 | BFLogBot Repo: bitfighter | Commit: 2d468d13f1 | Author: google-labs-jules[bot] | Message: Fix bug in isConvex handling collinear segments This commit fixes a bug in the `Zap::isConvex` function where polygons starting with collinear segments were incorrectly identified as convex even if they were concave. The original implementation only checked the determinant of the first three vertices to determine the "winding sign" of the polygon. If these were co | |
| 06:35:31 | BFLogBot llinear, the sign was 0, leading to incorrect results. The new implementation correctly finds the first non-zero determinant to establish the sign and ensures all edge transitions are checked, including wrap-around edges. Additionally, a new unit test `isConvexConcaveWithCollinear` has been added to `TestGeomUtils.cpp` to verify the fix and prevent regressions. I am an AI agent. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 06:35:33 | BFLogBot Pull request #729 opened by eykamp | Title: Fix bug in isConvex handling collinear segments | https://github.com/bitfighter/bitfighter/pull/729 | |
| 14:29:59 | BFLogBot Repo: bitfighter | Commit: 12b5079d66 | Author: Copilot | Message: Fix makeFilenameFromString sentinel bug; add comprehensive tests Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/f7f5119e-0830-42b5-be2d-f5518daa26f2 Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 14:35:53 | BFLogBot Repo: bitfighter | Commit: 97d739d2be | Author: google-labs-jules[bot] | Message: Fix bug in isConvex handling collinear segments and improve test coverage This commit fixes a bug in the `Zap::isConvex` function where polygons starting with collinear segments were incorrectly identified as convex. The new implementation: - Finds the first non-zero determinant to establish the polygon's winding direction. - Correctly iterates through all edges, | |
| 14:35:54 | BFLogBot including the wrap-around case. - Handles clockwise and counter-clockwise winding. Expanded unit test coverage in `TestGeomUtils.cpp` includes: - Polygons with collinear leading segments. - Clockwise winding polygons. - Polygons with redundant/collinear points along edges and corners. - Concave polygons where the concavity is at the end of the vertex list. I am an AI agent. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 14:57:40 | BFLogBot Pull request #730 opened by Copilot | Title: Fix makeFilenameFromString losing leading-dot when allowLastDot=true | https://github.com/bitfighter/bitfighter/pull/730 | |
| 14:57:58 | BFLogBot Repo: bitfighter | Commit: 45f0145d45 | Author: Copilot | Message: Fix makeFilenameFromString sentinel bug; add comprehensive tests (#730) Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/f7f5119e-0830-42b5-be2d-f5518daa26f2 Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 14:57:58 | BFLogBot Pull request #730 closed by Copilot | Title: Fix makeFilenameFromString losing leading-dot when allowLastDot=true | https://github.com/bitfighter/bitfighter/pull/730 | |
| 15:03:17 | BFLogBot Repo: bitfighter | Commit: 0326d0914b | Author: google-labs-jules[bot] | Message: Fix bug in isConvex handling collinear segments and provide exhaustive test coverage This commit fixes a logic error in `Zap::isConvex` where initial collinear segments could cause concave polygons to be misidentified as convex. The new implementation establishes the winding sign from the first non-zero turn and correctly checks all edges, including the wrap-around | |
| 15:03:19 | BFLogBot case. Expanded the test suite with 16 new test cases in `TestGeomUtils.cpp` covering various windings, concave shapes, degenerate cases, and large polygons to ensure robust coverage. I am an AI agent. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 15:37:00 | BFLogBot Repo: bitfighter | Commit: 1f5d8095fd | Author: eykamp | Message: Fix bug in isConvex handling collinear segments (#729) * Fix bug in isConvex handling collinear segments This commit fixes a bug in the `Zap::isConvex` function where polygons starting with collinear segments were incorrectly identified as convex even if they were concave. The original implementation only checked the determinant of the first three vertices to determine the "wind | |
| 15:37:00 | BFLogBot Pull request #729 closed by eykamp | Title: Fix bug in isConvex handling collinear segments | https://github.com/bitfighter/bitfighter/pull/729 | |
| 15:37:01 | BFLogBot ing sign" of the polygon. If these were collinear, the sign was 0, leading to incorrect results. The new implementation correctly finds the first non-zero determinant to establish the sign and ensures all edge transitions are checked, including wrap-around edges. Additionally, a new unit test `isConvexConcaveWithCollinear` has been added to `TestGeomUtils.cpp` to verify the fix and prevent regressions. I am an AI agent. Co-authored-by: eykamp | |
| 15:37:03 | BFLogBot <1133323+eykamp@users.noreply.github.com> * Fix bug in isConvex handling collinear segments and improve test coverage This commit fixes a bug in the `Zap::isConvex` function where polygons starting with collinear segments were incorrectly identified as convex. The new implementation: - Finds the first non-zero determinant to establish the polygon's winding direction. - Correctly iterates through all edges, including the wrap-around case. - Han | |
| 15:37:04 | BFLogBot dles clockwise and counter-clockwise winding. Expanded unit test coverage in `TestGeomUtils.cpp` includes: - Polygons with collinear leading segments. - Clockwise winding polygons. - Polygons with redundant/collinear points along edges and corners. - Concave polygons where the concavity is at the end of the vertex list. I am an AI agent. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> * Fix bug in isConvex handling collinear | |
| 15:37:06 | BFLogBot segments and provide exhaustive test coverage This commit fixes a logic error in `Zap::isConvex` where initial collinear segments could cause concave polygons to be misidentified as convex. The new implementation establishes the winding sign from the first non-zero turn and correctly checks all edges, including the wrap-around case. Expanded the test suite with 16 new test cases in `TestGeomUtils.cpp` covering various windings, concave shapes, | |
| 15:37:07 | BFLogBot degenerate cases, and large polygons to ensure robust coverage. I am an AI agent. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 16:13:55 | BFLogBot Repo: bitfighter | Commit: a39cbe2d74 | Author: Copilot | Message: Add comprehensive Move unit tests Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/696fd26e-ff30-4b0b-97f2-f9a63969bc38 Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 18:13:57 | BFLogBot Pull request #731 opened by Copilot | Title: Expand Move serialization test coverage for untested branches | https://github.com/bitfighter/bitfighter/pull/731 | |
| 18:14:17 | BFLogBot Repo: bitfighter | Commit: 71eb0acb78 | Author: Copilot | Message: Add comprehensive Move unit tests (#731) Agent-Logs-Url: https://github.com/bitfighter/bitfighter/sessions/696fd26e-ff30-4b0b-97f2-f9a63969bc38 Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 18:14:17 | BFLogBot Pull request #731 closed by Copilot | Title: Expand Move serialization test coverage for untested branches | https://github.com/bitfighter/bitfighter/pull/731 | |
| 18:15:55 | BFLogBot Repo: bitfighter | Commit: 780ab86b05 | Author: google-labs-jules[bot] | Message: Fix bugs in stripExtension and findCentroid As an AI agent, I have identified and fixed two bugs in the codebase: 1. stripExtension in zap/stringUtils.cpp was incorrectly stripping leading dots from filenames like ".hidden". 2. findCentroid in zap/GeomUtils.cpp had an inappropriately large epsilon for its zero-area check, causing it to fall back to vertex averaging | |
| 18:15:57 | BFLogBot for small polygons. New unit tests have been added to bitfighter_test/TestStringUtils.cpp and bitfighter_test/TestGeomUtils.cpp to verify these fixes and prevent regressions. Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> | |
| 18:15:59 | BFLogBot Pull request #732 opened by eykamp | Title: Fix bugs in stripExtension and findCentroid | https://github.com/bitfighter/bitfighter/pull/732 | |
| 18:47:04 | BFLogBot Pull request #732 closed by eykamp | Title: Fix bugs in stripExtension and findCentroid | https://github.com/bitfighter/bitfighter/pull/732 | |
| 18:47:04 | BFLogBot Repo: bitfighter | Commit: d3f9d62394 | Author: eykamp | Message: Fix bugs in stripExtension and findCentroid (#732) As an AI agent, I have identified and fixed two bugs in the codebase: 1. stripExtension in zap/stringUtils.cpp was incorrectly stripping leading dots from filenames like ".hidden". 2. findCentroid in zap/GeomUtils.cpp had an inappropriately large epsilon for its zero-area check, causing it to fall back to vertex averaging for smal | |
| 18:47:05 | BFLogBot l polygons. New unit tests have been added to bitfighter_test/TestStringUtils.cpp and bitfighter_test/TestGeomUtils.cpp to verify these fixes and prevent regressions. Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: eykamp <1133323+eykamp@users.noreply.github.com> |
Index Search ←Prev date Next date→
These logs were automatically created by BFLogBot on irc.freenode.net.