Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Updated

Updated

I didn't added any code for override. I also can't stop anyone to send in an override command with random numbers. The allowing of override should be on the FW part, where sending the override with...

I didn't added any code for override.
I also can't stop anyone to send in an override command with random numbers.
The allowing of override should be on the FW part, where sending the override with (sensor_id, value, no reset) should return false for those that are not accepted.

We should not allow overrides for newly added internal temperatures

We should not allow overrides for newly added internal temperatures

Renamed

Renamed

Moved it into login request

Moved it into login request

I added the unique decorator back, except for the few that have aliases

I added the unique decorator back, except for the few that have aliases

Renamed, also flagged for future type change.

Renamed, also flagged for future type change.

LEAHI-DIALIN-LDT-2980_Request: add ability to get the flowmeter measured internal temperature
LEAHI-DIALIN-LDT-2980_Request: add ability to get the flowmeter measured internal temperature
This will always return 0 and delay init from completing by up to 0.5s as the user is not logged in at the time of init.

This will always return 0 and delay init from completing by up to 0.5s as the user is not logged in at the time of init.

The naming of this method is misleading as it sends the message to request defeatured status and it is retrieved in a separate callback. The 'get' implies that the value returned from this method i...

The naming of this method is misleading as it sends the message to request defeatured status and it is retrieved in a separate callback. The 'get' implies that the value returned from this method is the defeatured status. The value returned is not the defeatured status but rather a T/F condition on if the FW replied back to dialin successfully.

suggestion: cmd_request_defeatured_status()

"No one should interact with it or be aware of it's existence, so the name shouldn't matter." *it matters to those who read the code in inconsistent intervals ( like those who participate in code...

"No one should interact with it or be aware of it's existence, so the name shouldn't matter."

  • it matters to those who read the code in inconsistent intervals ( like those who participate in code review or teaching ).


"As we only have 2 version in test at the same time."

  • Currently. By summer, i'd expect dialin to be considering 1.0's, 1.9s, and 2.0s/DVTs.


We have the choice to handle the redesign effort then or now.


Edit:
Follow up comment.

Looking at the other files. Users of dialin will not be aware of existence, but developers of dialin will as it impacts the behavior of overrides like temp & pressure.