-
-
Notifications
You must be signed in to change notification settings - Fork 388
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
Get default port address and protocol from sketch profile using monitor -s <sketchPath>
#2329
Get default port address and protocol from sketch profile using monitor -s <sketchPath>
#2329
Conversation
9a33f35
to
710cee4
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2329 +/- ##
==========================================
+ Coverage 64.06% 64.48% +0.41%
==========================================
Files 207 207
Lines 19546 19593 +47
==========================================
+ Hits 12523 12634 +111
+ Misses 5927 5867 -60
+ Partials 1096 1092 -4
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
This won't solve the issue request #2280:
The expected output of
|
c0704e7
to
f45c9fc
Compare
ffc5920
to
049861a
Compare
049861a
to
05346d3
Compare
05346d3
to
93b2b86
Compare
2009221
to
65eb91d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏼
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
Code enhancement
What is the current behavior?
It is not possible to retrieve port address and protocol information from a sketch profile.
monitor
cannot run if-p <port>
is not specified.What is the new behavior?
Default port address and protocol can be retrieved from the sketch profile using the
-s <sketchPath>
flag.-p <port>
and-l <protocol>
have priority over the information stored in the profile.Does this PR introduce a breaking change, and is titled accordingly?
No
Other information