search

loonwerks / AGREE

Assume-Guarantee REasoning Environment
BSD 3-Clause "New" or "Revised" License
13 stars 5 forks source link

AGREE Timeout doesn't always take effect #9

Open kfhoech opened 4 years ago

kfhoech commented 4 years ago

Issue by jendavis Friday May 04, 2018 at 19:56 GMT Originally opened as https://github.com/smaccm/smaccm/issues/132

On rare occasions, when I update my Timeout for AGREE in the analysis settings and press 'Apply' or 'Apply and Close', it does not take effect. The effective timeout is the one I had previously. I think this happens when I use 'Apply and Close' instead of 'Apply', but it is not repeatable in that I cannot cause this to happen every time. It has happened enough (maybe three times over the course of my use of AGREE) that I'm convinced it is not just that I accidentally hit 'Cancel' or something like that.

I should note that I am currently using the Agree bundled with OSATE 2.3.2-vfinal

kfhoech commented 4 years ago

Comment by kfhoech Tuesday May 08, 2018 at 14:04 GMT

Have you observed this happening with other preference settings as well?

Just to clarify, the preference setting is unchanged in the AGREE preferences dialog when you re-open it, correct? Or, is the analysis merely ignoring the changed value and continuing to terminate the analysis at the old timeout value?

kfhoech commented 4 years ago

Comment by jendavis Tuesday May 08, 2018 at 14:16 GMT

If I recall correctly, it is the latter--the analysis is ignoring the changed value and continuing to terminate the analysis at the old timeout value.

kfhoech commented 4 years ago

Comment by kfhoech Tuesday May 08, 2018 at 15:28 GMT

That behavior sounds more likely than the preference value not being saved. Preferences are handled by Eclipse itself; AGREE just tells it the fields and types and then retrieves the current value through an API.

It is likely that AGREE is not fetching the updated value from the preferences store when a new analysis is started.

kfhoech commented 4 years ago

Comment by jendavis Tuesday May 08, 2018 at 15:30 GMT

I neglected to answer this question: "Have you observed this happening with other preference settings as well?"

No, I have not.