Skip to content

Conversation

@dlapko
Copy link

@dlapko dlapko commented Apr 21, 2025

No description provided.

@dlapko
Copy link
Author

dlapko commented Apr 21, 2025

@microsoft-github-policy-service agree

@codecov-commenter
Copy link

codecov-commenter commented Apr 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.91%. Comparing base (b9933eb) to head (1444147).

Additional details and impacted files
@@ Coverage Diff @@ ## main #253 +/- ## ========================================== + Coverage 74.82% 74.91% +0.09%  ========================================== Files 32 32 Lines 6466 6467 +1 ========================================== + Hits 4838 4845 +7  + Misses 1337 1333 -4  + Partials 291 289 -2 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
@shueybubbles
Copy link
Collaborator

 {"test_intnvarchar", 1234, "1234"}, 

would it be just as good a test to put the name with the special character in this array instead of having a dedicated test?


Refers to: bulkcopy_test.go:262 in f5fd314. [](commit_id = f5fd314, deletion_comment = False)

// This example shows the usage of Connector type
func ExampleLastInsertId() {
func ExampleResult_LastInsertId() {

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why this name change?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dlapko added 3 commits April 21, 2025 18:49
The new tests analyzer reports common mistakes in declarations of tests, fuzzers, benchmarks, and examples in test packages, such as malformed names, incorrect signatures, or examples that document non-existent identifiers. Some of these mistakes may cause tests not to run. This analyzer is among the subset of analyzers that are run by go test. See: https://go.dev/doc/go1.24#vet https://go.dev/blog/examples#example-function-names
@dlapko dlapko force-pushed the fix-column-escaping branch from f5fd314 to 1444147 Compare April 21, 2025 15:49
@dlapko dlapko requested a review from shueybubbles April 21, 2025 16:12
Copy link
Collaborator

@shueybubbles shueybubbles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@dlapko
Copy link
Author

dlapko commented Apr 29, 2025

@shueybubbles Is there something wrong with the test environment? The linter is failing.

@shueybubbles
Copy link
Collaborator

@dlapko can you resolve the conflicts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants