Page MenuHomePhabricator

Remove all references to the Conduit ConnectionLog
ClosedPublic

Authored by epriestley on Dec 14 2015, 8:52 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Mar 22, 12:47 PM
Unknown Object (File)
Fri, Mar 15, 2:51 PM
Unknown Object (File)
Tue, Mar 5, 6:58 AM
Unknown Object (File)
Feb 12 2024, 9:04 AM
Unknown Object (File)
Feb 12 2024, 8:56 AM
Unknown Object (File)
Feb 3 2024, 7:50 AM
Unknown Object (File)
Jan 27 2024, 4:32 AM
Unknown Object (File)
Jan 7 2024, 9:18 PM
Subscribers
None

Details

Summary

Ref T5955, T9980, T9982.

We currently store two types of Conduit logs: connection logs and method logs.

Originally, Conduit worked like web logins: you'd call conduit.connect and then get a session back. This approach still works, but new clients don't use it and it will probably stop working eventually after T5955 is further along.

There was no real reason for things to work like this and no other API in the world does, I think it was just slightly easier to implement back in 2011.

This table was used to group up related calls in a UI long ago, I think, but that got deleted at some point. In any case, it serves no purpose in modern Phabricator.

Test Plan

grep

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

chad edited edge metadata.
This revision is now accepted and ready to land.Dec 14 2015, 8:55 PM
This revision was automatically updated to reflect the committed changes.