erlichmen/fantasm

Automatically exported from code.google.com/p/fantasm

fantasm's Issues

update to support webapp2 response status code assignment change

https://code.google.com/p/fantasm/source/browse/src/fantasm/handlers.py#263

response.status_code is deprecated in the most recent version of webapp2, 
response.set_status(200) is supported in different versions of webapp and 
webapp2 libs.  

Original issue reported on code.google.com by [email protected] on 25 Apr 2013 at 9:14

Python27 Support

Is it possible to use this under Python27?  

It errors as a CGI app.  I'm just learning Python (and App Engine) so I'm not 
certain if this is a simple change or something vastly improbable.

Original issue reported on code.google.com by [email protected] on 1 Dec 2011 at 6:47

startStateMachine does not provide unique instance names when multiple contexts are given

*Needs to be verified with a unit test*

When startStateMachine() is called with multiple contexts, the machines that 
are started must get unique instance names. Needs to also consider if a 
taskName is provided to startStateMachine.

Original issue reported on code.google.com by [email protected] on 6 Nov 2012 at 8:30

gcloud preview app run: error while parsing test/backup.yaml (Unexpected attribute 'state_machines')

$ gcloud preview app run .
WARNING: The datastore_admin builtin is deprecated. You can find information on 
how to enable it through the Administrative Console here: 
http://developers.google.com/appengine/docs/adminconsole/datastoreadmin.html
ERROR: (gcloud.preview.app.run) An error occurred while parsing file: 
[/home/james/projects/pipemail/gae/splash/fantasm/test/backup.yaml]
Unexpected attribute 'state_machines' for object of type AppInfoExternal.
  in "/home/james/projects/pipemail/gae/splash/fantasm/test/backup.yaml", line 8, column 1

Original issue reported on code.google.com by james.thornton on 7 Feb 2015 at 12:52

importing a machine destroys the root_url configuration

You can specific root_url in your fantasm.yaml file. However, when you import 
another yaml file, it overwrites the root_url specification.

Fantasm should only allow root_url to be specified in the root yaml file, and 
it should raise a configuration error if the root_url is specified in any of 
the imports.

Original issue reported on code.google.com by [email protected] on 18 Apr 2012 at 8:03

java implementation

any plan for future implementation in java ? =) 

Original issue reported on code.google.com by [email protected] on 12 Mar 2011 at 5:38

Async states support

What steps will reproduce the problem?
1.Send email and act upon response
2.Wait until eta or for a delay
3.

What is the expected output? What do you see instead?
I would like to setup asynchronous states.

What version of the product are you using? On what operating system?


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 6 May 2011 at 4:12

Namespace support for event names

Managing event names in fsm.yaml and in the corresponding action classes is 
currently difficult because event names in yaml files are simple strings. 
Changing event names requires manual changes in all places the names were 
defined.

It would be nice to reference event constants defined in action classes from 
the yaml definitions.

What version of the product are you using?
- revision 135

Original issue reported on code.google.com by saidimu on 6 Apr 2011 at 6:26

Please review r193

Can you have a look at this diff. Most of the changes are test code. 
Unfortunately, the NDB Key class doesn't have the nice serialization aspects of 
the db.Key class.

r193

Original issue reported on code.google.com by [email protected] on 4 Jan 2012 at 10:13

Expose GraphViz parameters before calling Google Chart APIs

Presently, no option is given when graphing an FSM, the default 'dot' chart is 
used 
(http://code.google.com/p/fantasm/source/browse/trunk/src/fantasm/handlers.py#96
). 

It would be nice to expose more Google Chart API portions: 
http://code.google.com/apis/chart/docs/gallery/graphviz.html

It would help to experiment with alternate chart types/sizes/formats, and to 
only graph portions of an FSM (in complex machines). 

Original issue reported on code.google.com by saidimu on 6 Apr 2011 at 6:47

Additional fan_in attribute conditions (in addition to 'time in seconds')

At present, the fan_in attribute accepts an integer representing 
time-in-seconds for how often the "boxcars should ship" 
http://code.google.com/p/fantasm/wiki/AdvancedConcepts.

Additional conditions could be very useful. Examples include:

- size: if the total size of the machine contexts is greater than 'size', batch 
the relevant machines.
- number: analogous to 'size', except the condition is number of some specified 
entity in each machine contexts (this can be distinct from the number of 
machines in cases where each machines operates on >1 entity).

These are extremely useful constructs when batching datastore and memcache 
operations. This is essential how the AppEngine mapreduce framework's mutation 
pool works. 
http://code.google.com/p/appengine-mapreduce/source/browse/trunk/python/src/mapr
educe/context.py#108

Original issue reported on code.google.com by saidimu on 6 Apr 2011 at 6:40

Upgrade to appengine python 3.7 runtime

Hello,

we are currently running python 2.7 codebase and we want to upgrade to python 3.7 in AppEngine. I know that the codebase has last updates about 8-9 years ago, but please could you point some direction what would be the nowadays alternative on AppEngine to this library?

Any advice much appreciated

Thanks a lot

Jan