Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
L
lmc-base-classes
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
LOFAR2.0
lmc-base-classes
Commits
a255530b
Commit
a255530b
authored
May 18, 2020
by
Anton Joubert
Browse files
Options
Downloads
Patches
Plain Diff
Fix typos
parent
dc4a2b13
Branches
Branches containing commit
Tags
v0.31.0
v0.31.0-1
Tags containing commit
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
README.md
+2
-2
2 additions, 2 deletions
README.md
tests/test_base_device.py
+1
-1
1 addition, 1 deletion
tests/test_base_device.py
with
3 additions
and
3 deletions
README.md
+
2
−
2
View file @
a255530b
...
@@ -252,7 +252,7 @@ is set, we internally update the TLS logging level as well.
...
@@ -252,7 +252,7 @@ is set, we internally update the TLS logging level as well.
### Additional logging targets
### Additional logging targets
Note that the
the
`loggingTargets`
attribute says "excluding ska_logging defaults".
Note that the
`loggingTargets`
attribute says "excluding ska_logging defaults".
Even when empty, you will still have the logging to stdout that is already provided
Even when empty, you will still have the logging to stdout that is already provided
by the ska_logging library. If you want to forward logs to other targets, then you can use
by the ska_logging library. If you want to forward logs to other targets, then you can use
this attribute. Since we also want logging to TLS, it should include the
`"tango::logger"`
this attribute. Since we also want logging to TLS, it should include the
`"tango::logger"`
...
@@ -325,7 +325,7 @@ method from an instance of a `tango.DeviceProxy` object.
...
@@ -325,7 +325,7 @@ method from an instance of a `tango.DeviceProxy` object.
If you want file and syslog targets, you could do something like:
If you want file and syslog targets, you could do something like:
`proxy.loggingTargets = ["file::/tmp/my.log", "syslog::udp://server.domain:514"]`
.
`proxy.loggingTargets = ["file::/tmp/my.log", "syslog::udp://server.domain:514"]`
.
**Note:**
There is a limit of 4 additional handlers. That the maximum length
**Note:**
There is a limit of 4 additional handlers. That
is
the maximum length
of the spectrum attribute. We could change this if there is a reasonable use
of the spectrum attribute. We could change this if there is a reasonable use
case for it.
case for it.
...
...
This diff is collapsed.
Click to expand it.
tests/test_base_device.py
+
1
−
1
View file @
a255530b
...
@@ -443,7 +443,7 @@ class TestSKABaseDevice(object):
...
@@ -443,7 +443,7 @@ class TestSKABaseDevice(object):
mocked_creator
.
side_effect
=
null_creator
mocked_creator
.
side_effect
=
null_creator
# test
adding
console target
# test console target
tango_context
.
device
.
loggingTargets
=
[
"
console::cout
"
]
tango_context
.
device
.
loggingTargets
=
[
"
console::cout
"
]
assert
tango_context
.
device
.
loggingTargets
==
(
"
console::cout
"
,
)
assert
tango_context
.
device
.
loggingTargets
==
(
"
console::cout
"
,
)
mocked_creator
.
assert_called_once_with
(
"
console::cout
"
,
mock
.
ANY
)
mocked_creator
.
assert_called_once_with
(
"
console::cout
"
,
mock
.
ANY
)
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment