Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Merge | Fix/commands null#3310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
paulmedynski merged 4 commits intodotnet:mainfromdeusanyjunior:fix/commands_null
May 8, 2025

Conversation

deusanyjunior
Copy link
Contributor

Currently the method is returningObject reference not set to an instance of an object when we try to run a batch without commands. This PR returnsSqlBatchCommand list has not been initialized instead.

I'd appreciate a CI & Test run.

@deusanyjunior
Copy link
ContributorAuthor

@dotnet-policy-service agree company="VTEX"

@deusanyjuniordeusanyjunior marked this pull request as ready for reviewApril 29, 2025 14:31
@benrr101
Copy link
Contributor

It looks like a good idea - the change is pretty simple. However, we want to make sure that these get caught by our localization process (and that we have consistent error messaging). Could you put the error message in our /resources/string.resx file and reference that when throwing the exception, please?

@paulmedynski
Copy link
Contributor

/azp run

@azure-pipelinesAzure Pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

Copy link
Contributor

@paulmedynskipaulmedynski left a comment

Choose a reason for hiding this comment

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

Use string resources to support localization.

@benrr101benrr101 added this to the6.1-preview2 milestoneApr 30, 2025
@paulmedynski
Copy link
Contributor

/azp run

@azure-pipelinesAzure Pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

Copy link
Contributor

@benrr101benrr101 left a comment

Choose a reason for hiding this comment

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

Found the test failure! One character change, should be easy fix. :)

{
get
{
return ResourceManager.GetString("ADP_NoSqlBatchCommandList", resourceCulture);
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks real goodexcept ... Either this line should beADP_NoSqlBatchCommandsList (with ans) OR the resx file should beADP_NoSqlBatchCommandList (without ans). I personally would vote for the second choice

As it stands right now, the mismatch is causing the unit test to fail due to ArgumentNullException coming from looking up the resx.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Good catch! Great suggestion. Just fixed.

@benrr101
Copy link
Contributor

/azp run

Copy link
Contributor

@benrr101benrr101 left a comment

Choose a reason for hiding this comment

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

If the build passes, I'm on board with this change 🚢

@azure-pipelinesAzure Pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@deusanyjunior
Copy link
ContributorAuthor

@benrr101 Do you have any clue about tests? It seems the results are not good. =\

@paulmedynski
Copy link
Contributor

Looks like some network blips. I'm re-running the failed tests.

deusanyjunior reacted with heart emoji

@paulmedynskipaulmedynski merged commite5cef80 intodotnet:mainMay 8, 2025
237 checks passed
@codecovCodecov
Copy link

codecovbot commentedMay 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.00%. Comparing base(a11dae7) to head(f8cc913).
Report is 16 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@##             main   #3310       +/-   ##==========================================- Coverage   72.94%       0   -72.95%==========================================  Files         298       0      -298       Lines       57002       0    -57002     ==========================================- Hits        41579       0    -41579+ Misses      15423       0    -15423
FlagCoverage Δ
addons?
netcore?
netfx?

Flags with carried forward coverage won't be shown.Click here to find out more.

☔ 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.

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

@benrr101benrr101benrr101 approved these changes

@paulmedynskipaulmedynskipaulmedynski approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
6.1-preview2
Development

Successfully merging this pull request may close these issues.

3 participants
@deusanyjunior@benrr101@paulmedynski

[8]ページ先頭

©2009-2025 Movatter.jp