[Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
-+-
  Reporter:  olemis  |Owner:
  Type:  defect  |   Status:  new
  Priority:  major   |  Version:  0.6.0
Resolution:  |
-+-
 After adding / removing milestone via admin web form all pages in product
 context render a message like

 {{{
 Error: Invalid milestone name

 Milestone milestone_name does not exist.
 }}}

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 7
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone
---+---
Changes (by olemis):

 * component:   => multiproduct
 * priority:  major => blocker
 * keywords:   => milestone
 * milestone:   => Release 7
 * owner:   => nobody


Old description:

> After adding / removing milestone via admin web form all pages in product
> context render a message like
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone_name does not exist.
> }}}

New description:

 After adding / removing milestone via admin web form all pages in product
 context render a message like

 {{{
 Error: Invalid milestone name

 Milestone milestone_name does not exist.
 }}}

 The following image illustrates the error displayed while rendering
 components admin panel.

 [[Image(bh_theme_x_122_milestone_error.png)]]

 **Update** I've noticed that the error goes away after a while (minutes)
 so maybe this is related to caching or code not committed DB changes right
 away ?

 PS: This may be an issue caused by either theme (qct) or multi-product or
 interactions between both of them .

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 7
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone
---+---
Description changed by olemis:

Old description:

> After adding / removing milestone via admin web form all pages in product
> context render a message like
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone_name does not exist.
> }}}
>
> The following image illustrates the error displayed while rendering
> components admin panel.
>
> [[Image(bh_theme_x_122_milestone_error.png)]]
>
> **Update** I've noticed that the error goes away after a while (minutes)
> so maybe this is related to caching or code not committed DB changes
> right away ?
>
> PS: This may be an issue caused by either theme (qct) or multi-product or
> interactions between both of them .

New description:

 After adding / removing milestone via admin web form all pages in product
 context render a message like

 {{{
 Error: Invalid milestone name

 Milestone milestone_name does not exist.
 }}}

 The following image illustrates the error displayed while rendering
 components admin panel.

 [[Image(bh_theme_x_122_milestone_error.png)]]

 **Update** I've noticed that the error goes away after a while (minutes)
 so maybe this is related to caching or code not committed DB changes right
 away ?

 PS: This may be an issue caused by either theme (qct) or multi-product or
 interactions between both of them . It may be specific to PostgreSQL
 backend .

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 7
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone
---+---
Description changed by olemis:

Old description:

> After adding / removing milestone via admin web form all pages in product
> context render a message like
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone_name does not exist.
> }}}
>
> The following image illustrates the error displayed while rendering
> components admin panel.
>
> [[Image(bh_theme_x_122_milestone_error.png)]]
>
> **Update** I've noticed that the error goes away after a while (minutes)
> so maybe this is related to caching or code not committed DB changes
> right away ?
>
> PS: This may be an issue caused by either theme (qct) or multi-product or
> interactions between both of them . It may be specific to PostgreSQL
> backend .

New description:

 After adding / removing milestone via admin web form all pages in product
 context render a message like

 {{{
 Error: Invalid milestone name

 Milestone milestone_name does not exist.
 }}}

 The following image illustrates the error displayed while rendering
 components admin panel.

 [[Image(bh_theme_x_122_milestone_error.png)]]

 **Update** I've noticed that the error goes away after a while (minutes)
 so maybe this is related to caching or code not committed DB changes right
 away ?

 **Update** : I've also noticed that the error happens immediately after
 deleting default milestones (1,2,3,4) . Error message will be

 {{{
 Error: Invalid milestone name

 Milestone milestone2 does not exist.
 }}}

 PS: This may be an issue caused by either theme (qct) or multi-product or
 interactions between both of them . It may be specific to PostgreSQL
 backend .

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 7
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone
---+---
Description changed by olemis:

Old description:

> After adding / removing milestone via admin web form all pages in product
> context render a message like
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone_name does not exist.
> }}}
>
> The following image illustrates the error displayed while rendering
> components admin panel.
>
> [[Image(bh_theme_x_122_milestone_error.png)]]
>
> **Update** I've noticed that the error goes away after a while (minutes)
> so maybe this is related to caching or code not committed DB changes
> right away ?
>
> **Update** : I've also noticed that the error happens immediately after
> deleting default milestones (1,2,3,4) . Error message will be
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone2 does not exist.
> }}}
>
> PS: This may be an issue caused by either theme (qct) or multi-product or
> interactions between both of them . It may be specific to PostgreSQL
> backend .

New description:

 After adding / removing milestone via admin web form all pages in product
 context render a message like

 {{{
 Error: Invalid milestone name

 Milestone milestone_name does not exist.
 }}}

 The following image illustrates the error displayed while rendering
 components admin panel.

 [[Image(bh_theme_x_122_milestone_error.png)]]

 **Update** I've noticed that the error goes away after a while (minutes)
 so maybe this is related to caching or code not committed DB changes right
 away ?

 **Update** : I've also noticed that the error happens immediately after
 deleting default milestones (1,2,3,4) . Error message will be

 **Update** : After renaming a milestone using admin panel the old name is
 still displayed in milestones list

 {{{
 Error: Invalid milestone name

 Milestone milestone2 does not exist.
 }}}

 PS: This may be an issue caused by either theme (qct) or multi-product or
 interactions between both of them . It may be specific to PostgreSQL
 backend .

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 7
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone
---+---
Description changed by olemis:

Old description:

> After adding / removing milestone via admin web form all pages in product
> context render a message like
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone_name does not exist.
> }}}
>
> The following image illustrates the error displayed while rendering
> components admin panel.
>
> [[Image(bh_theme_x_122_milestone_error.png)]]
>
> **Update** I've noticed that the error goes away after a while (minutes)
> so maybe this is related to caching or code not committed DB changes
> right away ?
>
> **Update** : I've also noticed that the error happens immediately after
> deleting default milestones (1,2,3,4) . Error message will be
>
> **Update** : After renaming a milestone using admin panel the old name is
> still displayed in milestones list
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone2 does not exist.
> }}}
>
> PS: This may be an issue caused by either theme (qct) or multi-product or
> interactions between both of them . It may be specific to PostgreSQL
> backend .

New description:

 After adding / removing milestone via admin web form all pages in product
 context render a message like

 {{{
 Error: Invalid milestone name

 Milestone milestone_name does not exist.
 }}}

 The following image illustrates the error displayed while rendering
 components admin panel.

 [[Image(bh_theme_x_122_milestone_error.png)]]

 **Update** I've noticed that the error goes away after a while (minutes)
 so maybe this is related to caching or code not committed DB changes right
 away ?

 **Update** : I've also noticed that the error happens immediately after
 deleting default milestones (1,2,3,4) . Error message will be

 {{{
 Error: Invalid milestone name

 Milestone milestone2 does not exist.
 }}}

 **Update** : After renaming a milestone using admin panel the old name is
 still displayed in milestones list

 PS: This may be an issue caused by either theme (qct) or multi-product or
 interactions between both of them . It may be specific to PostgreSQL
 backend .

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 7
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone
---+---
Description changed by olemis:

Old description:

> After adding / removing milestone via admin web form all pages in product
> context render a message like
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone_name does not exist.
> }}}
>
> The following image illustrates the error displayed while rendering
> components admin panel.
>
> [[Image(bh_theme_x_122_milestone_error.png)]]
>
> **Update** I've noticed that the error goes away after a while (minutes)
> so maybe this is related to caching or code not committed DB changes
> right away ?
>
> **Update** : I've also noticed that the error happens immediately after
> deleting default milestones (1,2,3,4) . Error message will be
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone2 does not exist.
> }}}
>
> **Update** : After renaming a milestone using admin panel the old name is
> still displayed in milestones list
>
> PS: This may be an issue caused by either theme (qct) or multi-product or
> interactions between both of them . It may be specific to PostgreSQL
> backend .

New description:

 After adding / removing milestone via admin web form all pages in product
 context render a message like

 {{{
 Error: Invalid milestone name

 Milestone milestone_name does not exist.
 }}}

 The following image illustrates the error displayed while rendering
 components admin panel.

 [[Image(bh_theme_x_122_milestone_error.png)]]

 **Update** I've noticed that the error goes away after a while (minutes)
 so maybe this is related to caching or code not committed DB changes right
 away ?

 **Update** : I've also noticed that the error happens immediately after
 deleting default milestones (1,2,3,4) . Error message will be

 {{{
 Error: Invalid milestone name

 Milestone milestone2 does not exist.
 }}}

 **Update** : After renaming a milestone using admin panel the old name is
 still displayed in milestones list

 **Update** : After some time milestone is visible in both admin panel and
 field drop down menu in ticket form . Even at that time scheduling a
 ticket for that milestone triggers a similar error message .

 PS: This may be an issue caused by either theme (qct) or multi-product or
 interactions between both of them . It may be specific to PostgreSQL
 backend .

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+--
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 7
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql db
---+--
Changes (by olemis):

 * keywords:  milestone => milestone, postgresql db


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+-
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 7
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql db, bhnet
---+-
Changes (by olemis):

 * keywords:  milestone, postgresql db => milestone, postgresql db, bhnet


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 8
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db
---+---

Comment (by mrchapp):

 I have this problem as well, with SQLite.

 By dumping the milestone table I can see only 3 INSERT's, but the default
 milestones ("milestone{1,2,3}") still appear occasionally, while my own
 milestones disappear, generating errors while trying to display a ticket.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 8
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---
Changes (by olemis):

 * keywords:  milestone, postgresql, db => milestone, postgresql, db, sqlite


Comment:

 Based on your feedback I'm tagging this issue with ''sqlite'' keyword as
 well . Considering the fact that I've never being able to reproduce it
 that way (running TracStandalone server) ... have you been able to
 identify under what circumstances this behavior is triggered ? For
 instance , do you get this immediately after the server is started ? Does
 it stop if web server is restarted ?

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  Release 8
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---
Description changed by olemis:

Old description:

> After adding / removing milestone via admin web form all pages in product
> context render a message like
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone_name does not exist.
> }}}
>
> The following image illustrates the error displayed while rendering
> components admin panel.
>
> [[Image(bh_theme_x_122_milestone_error.png)]]
>
> **Update** I've noticed that the error goes away after a while (minutes)
> so maybe this is related to caching or code not committed DB changes
> right away ?
>
> **Update** : I've also noticed that the error happens immediately after
> deleting default milestones (1,2,3,4) . Error message will be
>
> {{{
> Error: Invalid milestone name
>
> Milestone milestone2 does not exist.
> }}}
>
> **Update** : After renaming a milestone using admin panel the old name is
> still displayed in milestones list
>
> **Update** : After some time milestone is visible in both admin panel and
> field drop down menu in ticket form . Even at that time scheduling a
> ticket for that milestone triggers a similar error message .
>
> PS: This may be an issue caused by either theme (qct) or multi-product or
> interactions between both of them . It may be specific to PostgreSQL
> backend .

New description:

 After adding / removing milestone via admin web form all pages in product
 context render a message like

 {{{
 Error: Invalid milestone name

 Milestone milestone_name does not exist.
 }}}

 The following image illustrates the error displayed while rendering
 components admin panel.

 [[Image(bh_theme_x_122_milestone_error.png)]]

 **Update** I've noticed that the error goes away after a while (minutes)
 so maybe this is related to caching or code not committing DB changes
 right away ?

 **Update** : I've also noticed that the error happens immediately after
 deleting default milestones (1,2,3,4) . Error message will be

 {{{
 Error: Invalid milestone name

 Milestone milestone2 does not exist.
 }}}

 **Update** : After renaming a milestone using admin panel the old name is
 still displayed in milestones list

 **Update** : After some time milestone is visible in both admin panel and
 field drop down menu in ticket form . Even at that time scheduling a
 ticket for that milestone triggers a similar error message .

 PS: This may be an issue caused by either theme (qct) or multi-product or
 interactions between both of them . It may be specific to PostgreSQL
 backend .

--

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---

Comment (by hb):

 A 'me too' message:
 version 0.7, imported from trac. Postgres.

 ANY change in milestones or versions or components will result in erratic
 behaviour from BH.
 Restarting apache makes the errors go away and will activate the changes.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---

Comment (by wimh):

 I can "fix" this problem if I modify the apache2 virtual host definition
 for bh, and add {{{processes=1 threads=1}}} to the line containing
 {{{WSGIDaemonProcess}}}. If I set either value to 2, the problem
 reappears. I assume this fix is bad for performance, in particular on
 multi-core servers.

 I don't know much about WSGI, but I found this document with some related
 info: https://code.google.com/p/modwsgi/wiki/ProcessesAndThreading

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---

Comment (by gjm):

 Replying to [comment:17 wimh]:
 > I can "fix" this problem if I modify the apache2 virtual host definition
 for bh, and add {{{processes=1 threads=1}}} to the line containing
 {{{WSGIDaemonProcess}}}. If I set either value to 2, the problem
 reappears. I assume this fix is bad for performance, in particular on
 multi-core servers.
 >
 > I don't know much about WSGI, but I found this document with some
 related info: https://code.google.com/p/modwsgi/wiki/ProcessesAndThreading
 >

 Yes, this is correct. It is possible to deal with in this way although I
 have been reluctant to advise on that when there should be a better
 solution.

 I have added a unit test that demonstrates the problem making use of
 threads in r1609909. One solution to this is to drop the lru_cache
 decorator from
 source:trunk/bloodhound_multiproduct/multiproduct/env.py#L386 which seems
 to interact badly with the pre-existing caching that milestones have.

 The alternative that I am currently looking at is to clear the cache close
 to the beginning of a request with:

 {{{#!diff
 Index: bloodhound_multiproduct/multiproduct/env.py
 ===
 --- bloodhound_multiproduct/multiproduct/env.py (revision 1611839)
 +++ bloodhound_multiproduct/multiproduct/env.py (working copy)
 @@ -365,6 +365,8 @@
  g_env = env.parent if isinstance(env,
   ProductEnvironment) else
 env
  return f(self, g_env, *args, **kwargs)
 +__call__.clear = f.clear
 +
  return __call__

  def product_env_keymap(args, kwds, kwd_mark):
 @@ -397,6 +399,10 @@
  setup_participants =
 ExtensionPoint(trac.env.IEnvironmentSetupParticipant)
  multi_product_support_components =
 ExtensionPoint(ISupportMultiProductEnvironment)

 +@classmethod
 +def clear_env_cache(cls):
 +cls.__metaclass__.__call__.clear()
 +
  @property
  def product_setup_participants(self):
  return [
 Index: bloodhound_multiproduct/multiproduct/hooks.py
 ===
 --- bloodhound_multiproduct/multiproduct/hooks.py   (revision 1611839)
 +++ bloodhound_multiproduct/multiproduct/hooks.py   (working copy)
 @@ -37,6 +37,7 @@

  class MultiProductEnvironmentFactory(EnvironmentFactoryBase):
  def open_environment(self, environ, env_path, global_env,
 use_cache=False):
 +multiproduct.env.ProductEnvironment.clear_env_cache()
  environ.setdefault('SCRIPT_NAME', '')  # bh:ticket:594

  env = pid = product_path = None
 }}}

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  nobody
  Type:  defect| Status:  new
  Priority:  blocker   |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---

Comment (by wimh):

 I currently can't respond to the lru_cache decorator, I did not look into
 that part of the code.

 But I think there are two separate issues with the adding/removing of
 milestones.

 = !QuickCreateTicketDialog =
 If I disable the !QuickCreateTicketDialog from the !BloodhoundTheme
 plugin, this error will not be shown again after deleting a milestone:
 {{{
 Error: Invalid milestone name

 Milestone milestone2 does not exist.
 }}}
 = !MilestoneCache =
 But still after adding or deleting milestones, the changes are not always
 visible in the list. If I remove the {{{@cached}}} decorator from
 source:/trunk/trac/trac/ticket/model.py#L949 (ie replace it with
 {{{@property}}} and remove both lines containing {{{del
 self.cache.milestones}}}), that is fixed too. But this alone is not
 sufficient to fix the !QuickCreateTicketDialog.

 The first issue seems to resolve itself after a few minutes. I am not sure
 about the second issue, it looks like apache must be restarted to fix
 that.

 Note that another easy way to reproduce this is running two {{{tracd}}}
 processes on different ports.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  gjm
  Type:  defect| Status:  accepted
  Priority:  blocker   |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---
Changes (by gjm):

 * owner:  nobody => gjm
 * status:  new => accepted


Comment:

 patch from comment:18 committed in r1611921

 I think wimh's findings are still consistent with my analysis and there
 are multiple symptoms resulting from the same underlying problem. Running
 multiple tracd processes can be considered roughly the same as having
 {{{processes=2}}} for the {{{WSGIDaemonProcess}}}.

 To be fair I haven't replicated any errors around this that I believe
 resolve themselves after a few minutes as the errors I observed will
 continue to appear intermittently until the webserver restarts.

 With luck the commit is a good enough solution for now.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  gjm
  Type:  defect| Status:  accepted
  Priority:  blocker   |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---

Comment (by wimh):

 Replying to [comment:20 gjm]:
 > With luck the commit is a good enough solution for now.

 It fixes the problems for me, but do I understand it correctly it flushes
 all caches each time for each request? At least in the
 {{{MilestoneCache}}} it looks like a new SQL query is done each time I
 refresh the milestones admin page.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  gjm
  Type:  defect| Status:  accepted
  Priority:  blocker   |  Milestone:  next 0.x
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---

Comment (by gjm):

 Replying to [comment:21 wimh]:
 > Replying to [comment:20 gjm]:
 > > With luck the commit is a good enough solution for now.
 >
 > It fixes the problems for me, but do I understand it correctly it
 flushes all caches each time for each request? At least in the
 {{{MilestoneCache}}} it looks like a new SQL query is done each time I
 refresh the milestones admin page.

 It is only intended to flush a specific cache but there may be
 consequences for other caching. I haven't gone through all the
 implications which is part of the reason that I haven't closed this ticket
 yet.

 Effectively the solution should be safe enough though there is likely to
 be some degradation in performance. Given that changes in milestone are
 relatively rare this could look like an overreaction.

 If this requires further discussion, it might be better to discuss it on
 the dev mailing list as it should get a wider audience.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  gjm
  Type:  defect| Status:  accepted
  Priority:  blocker   |  Milestone:  Release 8
 Component:  multiproduct  |Version:  0.6.0
Resolution:|   Keywords:  milestone, postgresql, db, sqlite
---+---
Changes (by gjm):

 * milestone:  next 0.x => Release 8


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  gjm
  Type:  defect| Status:  closed
  Priority:  blocker   |  Milestone:  Release 8
 Component:  multiproduct  |Version:  0.6.0
Resolution:  fixed |   Keywords:  milestone, postgresql, db, sqlite
---+---
Changes (by rjollos):

 * status:  accepted => closed
 * resolution:   => fixed


-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker

Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product

[Apache Bloodhound]

#613: Add / remove milestone breaks a whole product
---+---
  Reporter:  olemis|  Owner:  gjm
  Type:  defect| Status:  closed
  Priority:  blocker   |  Milestone:  Release 8
 Component:  multiproduct  |Version:  0.6.0
Resolution:  fixed |   Keywords:  milestone, postgresql, db, sqlite
---+---

Comment (by rjollos):

 This is reported to be an issue after [milestone:"Release 8"]. See #840.

-- 
Ticket URL: 
Apache Bloodhound 
The Apache Bloodhound issue tracker