fix: Don't use ValueStr, get raw bytes instead #2220
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
murarustefaan approved these changes Jul 9, 2025
kodiakhq bot pushed a commit that referenced this pull request Jul 9, 2025
🤖 I have created a release *beep* *boop* --- ## [4.87.1](v4.87.0...v4.87.1) (2025-07-09) ### Bug Fixes * **deps:** Update module github.com/cloudquery/codegen to v0.3.30 ([#2221](#2221)) ([0453cbe](0453cbe)) * Don't use `ValueStr`, get raw bytes instead ([#2220](#2220)) ([6d71d18](6d71d18)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
5 tasks
kodiakhq bot pushed a commit that referenced this pull request Jul 16, 2025
Cleans up #2226, #2220 and #2217. I believe I found the issue and the fix is cloudquery/cloudquery#21058 ---
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Summary
Follow up to #2217
Apparently
ValueStrcalls the same code that generated the original panic. Hopefully this worksUse the following steps to ensure your PR is ready to be reviewed
go fmtto format your code 🖊golangci-lint run🚨 (install golangci-lint here)