Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Class Scope was being returned in Memory Snapshot #2707

Merged
merged 3 commits into from
Oct 11, 2019
Merged

Conversation

tomlm
Copy link
Contributor

@tomlm tomlm commented Oct 11, 2019

As was Settings scope.

Since these are immutable values I don't think it makes sense for them to be sent as part of the memory snapshot, as that would push settings secrets into transcript logs as well as attempt to serialize objects that aren't designed to be serialized.

  • changed GetSnapshotMemory() to not take snapshot of readonly memory
  • Made settings an explicit implemented memoryscope. Old code was "filling" the settings in external location, now it's internal to SettingsMemoryScope

Tom Laird-McConnell added 3 commits October 10, 2019 16:23
Readonly memory (dialog class instance and settings) should not be sent to transcript or to emulator
Make SettingsMemoryScope() be from settings explicitely instead of external code populating it
@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 82841

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 12 unchanged lines in 7 files lost coverage.
  • Overall coverage increased (+0.03%) to 78.597%

Files with Coverage Reduction New Missed Lines %
/libraries/Microsoft.Bot.Builder.Dialogs/DialogManager.cs 1 70.64%
/libraries/Microsoft.Bot.Builder.Dialogs/DialogSet.cs 1 90.48%
/libraries/Microsoft.Bot.Builder.Dialogs/ObjectPath.cs 1 76.24%
/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/OAuthPrompt.cs 1 57.23%
/libraries/Microsoft.Bot.Builder.Azure/CosmosDbStorageOptions.cs 2 50.0%
/libraries/Microsoft.Bot.Builder/MemoryTranscriptStore.cs 2 86.09%
/libraries/Microsoft.Bot.Builder.Dialogs/Memory/Scopes/MemoryScope.cs 4 85.71%
Totals Coverage Status
Change from base Build 82810: 0.03%
Covered Lines: 5402
Relevant Lines: 6873

💛 - Coveralls

@coveralls
Copy link
Collaborator

Pull Request Test Coverage Report for Build 82841

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 11 unchanged lines in 3 files lost coverage.
  • Overall coverage decreased (-1.3%) to 77.275%

Files with Coverage Reduction New Missed Lines %
/libraries/Microsoft.Bot.Builder.Dialogs/DialogManager.cs 3 67.07%
/libraries/Microsoft.Bot.Builder.Dialogs/DialogSet.cs 3 87.32%
/libraries/Microsoft.Bot.Builder.Dialogs/Memory/Scopes/MemoryScope.cs 5 88.37%
Totals Coverage Status
Change from base Build 82810: -1.3%
Covered Lines: 7583
Relevant Lines: 9813

💛 - Coveralls

@fuselabs
Copy link
Collaborator

✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
✔️ No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

@tomlm tomlm merged commit bd0dc1e into master Oct 11, 2019
@cleemullins cleemullins deleted the tomlm/fixclassScope branch October 24, 2019 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants