Engineering request for testing: stateful operations

Next topic

Author	Message
Bertrand Dunogier	Friday 14 January 2011 3:30:57 am Hi ! Yesterday, we came across an issue in the workflow/operation system. While operations interrupted by a workflow (for instance approval) will be resumed where they left off, interruptions from an operation method will restart the operation from scratch. This is quite severe, even though it fortunately only affects the kernel aspect of operations. No default method that I know of halts an operation by default, and therefore it had never been seen. You can see the issue here, as well as the proposed patch: http://issues.ez.no/IssueView.php?Id=17840. If you have a possibility to test it, please do ! I'm especially interested in tests on systems where real life workflows are used, interactive or not, and whatever the operation is. If it is a custom operation, it is even bettter ! Please let me know here. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Gaetano Giunta	Friday 14 January 2011 5:10:46 am 1. Care to explain the interaction between interactions and operations, for the people who rae not that deep into them (or just forgopt ;-) ) ? 2. while working on this one thing that should be added to the current workflow events api is support for XA transactions: if an event at the end of the workflow ends in ABORT, the db transaction is currently rolled back, but the event handlers that previously executed get no chance to rollback their work Principal Consultant International Business Member of the Community Project Board
Bertrand Dunogier	Friday 14 January 2011 5:38:07 am 2) honestly, I can't add much more. I've already spent quite some time on this while it was unplanned, and really won't be able to fit more right now :( 1) which aspect exactly do you wish I elaborate upon here ? Just guide me, I'm a little slow today :) Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier
Gaetano Giunta	Saturday 15 January 2011 4:55:00 am About point 1: just general info about "operations" will do - some operations have triggers (and thus can have workflows added to them), while some olthers do not declare triggers. Correct? The list of operations that have triggers is found in workflow.ini - operations are grouped in modules; the ggsysinfo extension can be used to show all of the operations available on a given install - operations are declared in a operation_definition.php file inside the module directory; every operation can consist of a series of php methods that will be invoked one after the other (eg. content/publish has 19 php methods in it) - what are the expected return values for those php methods that are declared as part of oeprations, and how can they "interrupt" the operation? Principal Consultant International Business Member of the Community Project Board

eZ debug

Timing:	Jan 29 2025 23:49:15
Script start
Timing:	Jan 29 2025 23:49:15
Module start 'layout'
Timing:	Jan 29 2025 23:49:15
Module start 'content'
Timing:	Jan 29 2025 23:49:16
Module end 'content'
Timing:	Jan 29 2025 23:49:16
Script end

Main resources:

Total runtime	1.0299 sec
Peak memory usage	4,096.0000 KB
Database Queries	61

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0044	588.2813	151.2266
Module start 'layout'	0.0044	0.0023	739.5078	36.6875
Module start 'content'	0.0067	1.0224	776.1953	502.5547
Module end 'content'	1.0290	0.0008	1,278.7500	15.8125
Script end	1.0298		1,294.5625

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.2909	16	0.0002
Check MTime	0.0013	0.1260	16	0.0001
Mysql Total
Database connection	0.0006	0.0626	1	0.0006
Mysqli_queries	0.9905	96.1795	61	0.0162
Looping result	0.0004	0.0397	59	0.0000
Template Total	1.0015	97.3	2	0.5008
Template load	0.0022	0.2100	2	0.0011
Template processing	0.9994	97.0394	2	0.4997
Template load and register function	0.0001	0.0078	1	0.0001
states
state_id_array	0.0009	0.0834	1	0.0009
state_identifier_array	0.0011	0.1086	2	0.0006
Override
Cache load	0.0018	0.1755	25	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.0915	2	0.0005
Fetch class attribute name	0.0009	0.0898	6	0.0002
XML
Image XML parsing	0.0020	0.1957	2	0.0010
class_abstraction
Instantiating content class attribute	0.0000	0.0010	8	0.0000
General
dbfile	0.0034	0.3333	22	0.0002
String conversion	0.0000	0.0008	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
4	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
4	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/link.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/link.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 16 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs