The Wayback Machine - https://web.archive.org/web/20221201030013/https://github.com/dotnet/aspnetcore/issues/30287
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

Jump to bottom

Ability to monitor circuit activity #30287

Open
SteveSandersonMS opened this issue Feb 19, 2021 · 6 comments
Open

Ability to monitor circuit activity #30287

SteveSandersonMS opened this issue Feb 19, 2021 · 6 comments
Assignees
@surayya-MS
Labels
affected-few This issue impacts only small number of customers area-blazor Includes: Blazor, Razor Components blazor-server enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-circuit-lifecycle Issues to do with blazor server lifecycle events needs-prototype Priority:1 Work that is critical for the release, but we could probably ship without severity-major triaged Reviewed during triage webui-P1-DR Temporary label to help with planning webui-P2-JC Temporary label to help with planning webui-P2-MB Temporary label to help with planning webui-P3-SS Temporary label to help with planning webui-P3-TP Temporary label to help with planning
Milestone
8.0-preview1

Comments

@SteveSandersonMS
Copy link
Member

SteveSandersonMS commented Feb 19, 2021 •
edited by danroth27

Ability to monitor circuit activity so that circuits can then be terminated as appropriate. Provide callbacks when an event, JS interop call, or other activity happens on the circuit.

The ability to terminate circuits from client/server is tracked separately by #17866.

Split out from #27885
@SteveSandersonMS SteveSandersonMS added the area-blazor Includes: Blazor, Razor Components label Feb 19, 2021
@SteveSandersonMS SteveSandersonMS added this to the Backlog milestone Feb 19, 2021
@msftbot
Copy link
Contributor

msftbot bot commented Feb 19, 2021

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@SteveSandersonMS SteveSandersonMS added affected-few This issue impacts only small number of customers enhancement This issue represents an ask for new feature or an enhancement to an existing one severity-major labels Feb 19, 2021 — with ASP.NET Core Issue Ranking
@msftbot
Copy link
Contributor

msftbot bot commented Mar 9, 2021

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@mkArtakMSFT mkArtakMSFT mentioned this issue Mar 23, 2021
Closed
27 tasks
@javiercn javiercn added feature-circuit-lifecycle Issues to do with blazor server lifecycle events blazor-server labels Apr 20, 2021
@guardrex guardrex mentioned this issue May 2, 2021
Closed
41 tasks
@mkArtakMSFT mkArtakMSFT added this to 6.0-rc1 (17th Aug) in ASP.NET Core Blazor & MVC 6.0 Jul 13, 2021
@mkArtakMSFT
Copy link
Contributor

mkArtakMSFT commented Jul 15, 2021

Moving this out of 6.0 to make room for Razor tooling asks for the Razor compiler.

@mkArtakMSFT mkArtakMSFT modified the milestones: 6.0-rc1, Backlog Jul 15, 2021
@msftbot
Copy link
Contributor

msftbot bot commented Jul 15, 2021

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@mkArtakMSFT mkArtakMSFT removed this from 6.0-rc1 (17th Aug) in ASP.NET Core Blazor & MVC 6.0 Jul 15, 2021
@pranavkm pranavkm modified the milestones: Backlog, .NET 7 Planning Oct 19, 2021
@pranavkm pranavkm added the Priority:2 Work that is important, but not critical for the release label Oct 28, 2021
@mkArtakMSFT mkArtakMSFT added triaged Reviewed during triage Priority:1 Work that is critical for the release, but we could probably ship without and removed Priority:2 Work that is important, but not critical for the release labels Nov 5, 2021
@mkArtakMSFT mkArtakMSFT mentioned this issue Nov 5, 2021
Open
@javiercn
Copy link
Member

javiercn commented Jan 19, 2022

#39615

@javiercn javiercn mentioned this issue Jan 19, 2022
Closed
@mkArtakMSFT mkArtakMSFT mentioned this issue Jan 23, 2022
Closed
@guardrex guardrex mentioned this issue Jul 8, 2022
Closed
8 tasks
@danroth27 danroth27 changed the title More control over circuits lifetime (ability to monitor circuit activity and terminate from client/server) More control over circuits lifetime Aug 24, 2022
@danroth27 danroth27 changed the title More control over circuits lifetime More control over Blazor Server circuit lifetime Aug 24, 2022
@danroth27 danroth27 changed the title More control over Blazor Server circuit lifetime Ability to monitor circuit activity Aug 24, 2022
@vflame
Copy link

vflame commented Sep 20, 2022 •
edited

Is it possible to access Blazor's signalr hub/hubcontext to disconnect clients and to override the OnConnectedAsync and OnDisconnectedAsync events as a workaround? How about making the HttpContext used to establish the underlying signalr connection available when a circuit is opened/up?

@mkArtakMSFT mkArtakMSFT removed the triaged Reviewed during triage label Sep 28, 2022
@mkArtakMSFT mkArtakMSFT added the triaged Reviewed during triage label Oct 20, 2022
@MackinnonBuck MackinnonBuck added the webui-P2-MB Temporary label to help with planning label Nov 8, 2022
@TanayParikh TanayParikh added the webui-P3-TP Temporary label to help with planning label Nov 9, 2022
@TanayParikh TanayParikh mentioned this issue Nov 9, 2022
Open
@SteveSandersonMS SteveSandersonMS added the webui-P3-SS Temporary label to help with planning label Nov 10, 2022
@javiercn javiercn added needs-prototype webui-P2-JC Temporary label to help with planning labels Nov 10, 2022
@danroth27 danroth27 added the webui-P1-DR Temporary label to help with planning label Nov 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@surayya-MS surayya-MS

Labels
affected-few This issue impacts only small number of customers area-blazor Includes: Blazor, Razor Components blazor-server enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-circuit-lifecycle Issues to do with blazor server lifecycle events needs-prototype Priority:1 Work that is critical for the release, but we could probably ship without severity-major triaged Reviewed during triage webui-P1-DR Temporary label to help with planning webui-P2-JC Temporary label to help with planning webui-P2-MB Temporary label to help with planning webui-P3-SS Temporary label to help with planning webui-P3-TP Temporary label to help with planning
Projects
None yet
Milestone
8.0-preview1
Development

No branches or pull requests
9 participants
@pranavkm @SteveSandersonMS @danroth27 @javiercn @MackinnonBuck @vflame @TanayParikh @mkArtakMSFT @surayya-MS