Unexpected Trigger Fire
Posted: Thu Aug 06, 2020 7:36 pm
At the begining, I want to confirm a consensus against trigger firing mechanism in mudlet that any trigger can only be fired by new arriving lines after the point of time the trigger itself being created, isn't it?
If the above view is correct, the below scenario should not get the trigger fired:
The issue only occurs when the trigger is created immediately after the matched line arriving.
Here's an example to easily re-produce the issue:
Create an one shot trigger #A with pattern line1, its send command is creating another one shot trigger #B with pattern line1 also. The purpose for such case is to get the exact action being run only when the line1 arrive twice.
The expected result is:
1. trigger #A created
2. line1 arrives
3. trigger #A fired
4. trigger #B created by trigger #A
5. line1 arrives second time
6. trigger #B fired
The current issue result is :
1. trigger #A created
2. line1 arrives
3. trigger #A fired
4. trigger #B created by trigger #A
5. trigger #B fired immediately by the previous arrived line1
If the above view is correct, the below scenario should not get the trigger fired:
- new ling arrived
- trigger matches the above line is created
The issue only occurs when the trigger is created immediately after the matched line arriving.
Here's an example to easily re-produce the issue:
Create an one shot trigger #A with pattern line1, its send command is creating another one shot trigger #B with pattern line1 also. The purpose for such case is to get the exact action being run only when the line1 arrive twice.
The expected result is:
1. trigger #A created
2. line1 arrives
3. trigger #A fired
4. trigger #B created by trigger #A
5. line1 arrives second time
6. trigger #B fired
The current issue result is :
1. trigger #A created
2. line1 arrives
3. trigger #A fired
4. trigger #B created by trigger #A
5. trigger #B fired immediately by the previous arrived line1