GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
Passed
Push — master ( fbdd84...45bad2 )
by P.R.
04:28
created

LogFileMessage   A

Complexity

Total Complexity 2

Size/Duplication

Total Lines 73
Duplicated Lines 0 %

Test Coverage

Coverage 0%

Importance

Changes 1
Bugs 0 Features 0
Metric Value
c 1
b 0
f 0
dl 0
loc 73
ccs 0
cts 12
cp 0
rs 10
wmc 2

2 Methods

Rating   Name   Duplication   Size   Complexity  
A send_message() 0 9 1
A __init__() 0 50 1
1
"""
2
Enarksh
3
4
Copyright 2013-2016 Set Based IT Consultancy
5
6
Licence MIT
7
"""
8
from enarksh.message.Message import Message
0 ignored issues
show
Bug introduced by
The name message does not seem to exist in module enarksh.
Loading history...
Configuration introduced by
The import enarksh.message.Message could not be resolved.

This can be caused by one of the following:

1. Missing Dependencies

This error could indicate a configuration issue of Pylint. Make sure that your libraries are available by adding the necessary commands.

# .scrutinizer.yml
before_commands:
    - sudo pip install abc # Python2
    - sudo pip3 install abc # Python3
Tip: We are currently not using virtualenv to run pylint, when installing your modules make sure to use the command for the correct version.

2. Missing __init__.py files

This error could also result from missing __init__.py files in your module folders. Make sure that you place one file in each sub-folder.

Loading history...
9
10
11
class LogFileMessage(Message):
12
    """
13
    Message type for instructing the logger that a log file is available for storing into the database.
14
    """
15
    MESSAGE_TYPE = 'logger:LogFileMessage'
16
    """
17
    The message type.
18
19
    :type: str
20
    """
21
22
    # ------------------------------------------------------------------------------------------------------------------
23
    def __init__(self, rnd_id, name, total_size, filename1, filename2):
24
        """
25
        Object constructor.
26
27
        :param int rnd_id: The ID of the run node.
28
        :param str name: The name of he output:
29
                         - 'out' for stdout
30
                         - 'err' for stderr
31
        :param int total_size: The total size in bytes of the log.
32
        :param str|None filename1: The name of the file where the first chunk of the log is stored.
33
        :param str|None filename2: The name of the file where the last chunk of the log is stored.
34
        """
35
        Message.__init__(self, LogFileMessage.MESSAGE_TYPE)
36
37
        self.rnd_id = rnd_id
38
        """
39
        The ID of the run node.
40
41
        :type: int
42
        """
43
44
        self.name = name
45
        """
46
        The name of he output:
47
        - 'out' for stdout
48
        - 'err' for stderr
49
50
        :type: str
51
        """
52
53
        self.total_size = total_size
54
        """
55
        The total size in bytes of the log.
56
57
        :type: int
58
        """
59
60
        self.filename1 = filename1
61
        """
62
        The name of the file where the first chunk of the log is stored.
63
64
        :type: str
65
        """
66
67
        self.filename2 = filename2
68
        """
69
        The name of the file where the last chunk of the log is stored.
70
71
        :type: str
72
        """
73
74
    # ------------------------------------------------------------------------------------------------------------------
75
    def send_message(self, end_point):
76
        """
77
        Sends the message to an end point.
78
79
        :param str end_point: The end point.
80
81
        :rtype: None
82
        """
83
        self.message_controller.send_message(end_point, self)
0 ignored issues
show
Bug introduced by
The Instance of LogFileMessage does not seem to have a member named message_controller.

This check looks for calls to members that are non-existent. These calls will fail.

The member could have been renamed or removed.

Loading history...
84
85
# ----------------------------------------------------------------------------------------------------------------------
86