long_term project : cannot launch scheduler
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Fix Released
|
High
|
OpenERP R&D Addons Team 1 |
Bug Description
in project long term module, i get a bug while i am computing the scheduler :
To check, you have to update addons because we done some changes in this module. then, run the scheduler with demo data or without demo data (if you have no demo data, create one)
Compute the phase scheduler :
[2011-10-26 07:23:54,226][?] ERROR:web-
Traceback (most recent call last):
File "/home/
return f(self, dbname, *args, **kwargs)
File "/home/
res = self.execute_cr(cr, uid, obj, method, *args, **kw)
File "/home/
return getattr(object, method)(cr, uid, *args, **kw)
File "/home/
return self.compute_
File "/home/
project_
File "/home/
projects_gantt = Task.BalancedPr
File "/home/
_Allocation
File "/home/
self.
File "/home/
task.
File "/home/
c._
File "/home/
self.
File "/home/
self.
File "<string>", line 17, in Project_1
File "/home/
self.
File "/home/
set_
File "/home/
self.
File "/home/
days = _to_days(day_range)
File "/home/
tokens = src.split(",")
AttributeError: 'NoneType' object has no attribute 'split'
Related branches
- OpenERP Core Team: Pending requested
-
Diff: 16 lines (+3/-1)1 file modifiedresource/resource.py (+3/-1)
- OpenERP Core Team: Pending requested
-
Diff: 26 lines (+7/-1)1 file modifiedresource/resource.py (+7/-1)
Changed in openobject-addons: | |
importance: | Undecided → High |
Changed in openobject-addons: | |
status: | New → Confirmed |
Changed in openobject-addons: | |
assignee: | nobody → OpenERP R&D Addons Team 1 (openerp-dev-addons1) |
Hello,
This error usually comes under following circumstances:
1. There exists a calendar(working time) linked to Selected project for scheduling.
2. The working time has no working schedule defined(no o2m records).
3. OR The O2M field contains a record with NO day of the week defined.
There seems 3 possible ways to get rid of this situation.
A. Undoubtedly, the day of the week should be made mandatory.(I have no exceptional case as of now where we never need it defined).
B. Prompting the user to realize the configuration error.
C. If neither of the solutions can go as accepted, we can assign _defaults value.(We observed that the field is selection and no default is set, which is special mistake in itself). Still, GTK will have no issues, but web is subjected to throw error because web always adds a blank '' option to selection fields.
Attached branches contains the solutions.
Thanks,
Serpent Consulting Services.