Skip to content

Don't place bogus data in an in/out variable in venus#64148

Merged
CyrusNajmabadi merged 1 commit intodotnet:mainfrom
CyrusNajmabadi:bogusVenueData
Sep 20, 2022
Merged

Don't place bogus data in an in/out variable in venus#64148
CyrusNajmabadi merged 1 commit intodotnet:mainfrom
CyrusNajmabadi:bogusVenueData

Conversation

@CyrusNajmabadi
Copy link
Contributor

No description provided.

@CyrusNajmabadi CyrusNajmabadi requested a review from a team as a code owner September 20, 2022 18:26
@ghost ghost added the Area-IDE label Sep 20, 2022

// Next, we'll check to see if there is actually a DataTip for this candidate.
// If there is, we'll map this span back to the DataBuffer and return it.
pSpan[0] = candidateSpan.ToVsTextSpan();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

problem was here. we were placing a span in our subject-buffer coordinates into an in/out parameter that is referring to the surface buffer. If we ended up succeeding below, this wasn't a problem, as we'd overwrite this. But if we failed, we'd leave this bogus data in here.

Copy link
Contributor

@ToddGrun ToddGrun left a comment

Choose a reason for hiding this comment

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

:shipit:

@CyrusNajmabadi CyrusNajmabadi merged commit 5c96e99 into dotnet:main Sep 20, 2022
@ghost ghost added this to the Next milestone Sep 20, 2022
@CyrusNajmabadi CyrusNajmabadi deleted the bogusVenueData branch September 20, 2022 19:50
@Cosifne Cosifne modified the milestones: Next, 17.4 P3 Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants