udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This will have an effect on both singlenode and distributed mode as  described below...  *singlenode:*  Currently, when running in singlenode mode, an embedded ZooKeeper server is started, and it discovers an available port for client connections and exposes it via a getClientPort() method.  With this change, IF a client connect string is provided explicitly, the embedded ZooKeeper server should not be started, but instead the client connection should be established using that explicitly provided connect string. SEE the "todo" comment above the `SpringApplicationBuilder admin` line within `SingleNodeApplication`.  *distributed:*  Currently, when running in distributed mode, the client connect string is hardcoded to `localhost:2181`. Obviously that is only a short term solution since a real-world distributed runtime would span multiple machines (including the ZooKeeper ensemble itself). That is also why the connect string must support a comma-delimited list of `host:port` values (for redundancy), but the constructor for `ZooKeeperConnection` that accepts a client connect string already supports that via the underlying `CuratorFramework` builder.  With this change, a command-line argument for the client connect string will be passed into the `ZooKeeperConnection` constructor, within the configuration (e.g. SEE the "todo" statement within `ContainerServerApplication.DistributedZooKeeperConnectionConfiguration`).
Answer: 11891.0

User story: When the job is run with its jobParameters by SimpleJobLauncher, its lastJobExecution's stepExecutions are checked for UNKNOWN status to throw JobRestartException. It looks like the stepExecutions for the lastJobExecution are never set and the collection 'stepExecutions' is not fetched from job repository.  Hence, not sure if the following condition in SimpleJobLauncher's run(final Job job, final JobParameters jobParameters) would ever get executed:  for (StepExecution execution : lastExecution.getStepExecutions()) {     if (execution.getStatus() == BatchStatus.UNKNOWN) {      //throw      throw new JobRestartException("Step [" + execution.getStepName() + "] is of status UNKNOWN");     }//end if    }//end for
Answer: 170983.0

User story: "Need to be able to test the following sources: TCP, HTTP, Time,"
Answer: 4270.0

User story: "When sending data to the TCP Source if the data is not terminated with a \r\n when the socket is closed by the client, XD throws an exception.  "
Answer: 995.0

User story: If stream fails to create while using sources or sinks that need ports.  Ports are not released.  If while creating a stream you see: "Command failed org.springframework.xd.rest.client.impl.SpringXDException: Failed to bind to: 0.0.0.0/0.0.0.0:9000. Possibly the port is already in use." then destroy the stream (or all streams for that matter) you will not be able to create another stream that uses that port.    The work around is to cycle the container.
Answer: 5103.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: [Problem] Can't use tcp source, sink and http together on Single Node.  While creating tests for CI I tried to create the following: [Steps to Reproduce] xd:>stream create fooOut --definition "tcp|file" Created new stream 'fooOut' xd:>stream create fooIn --definition "http --port=9002|tcp" Command failed org.springframework.xd.rest.client.impl.SpringXDException: Failed to bind to: 0.0.0.0/0.0.0.0:9000. Possibly the port is already in use. Even if I use different ports for the tcp I still get failures pointing to 9000. [Extra Notes] The stream below is works. xd:>stream create fooOut --definition "tcp|file" Created new stream 'fooOut' xd:>stream create fooIN --definition "time|tcp"  *Stack Trace Attached*
Answer: 5109.0

User story: "When executing tests and failures occur (should be easy to simulate with a forced failure), several other side-effect failures occur with the following error:  {code} Caused by: java.lang.IllegalArgumentException: HSQLDB could not be started. Maybe another instance is already running on 0.0.0.0:13583 ? {code}  It seems that the failing tests are not properly cleaning up, so the HSQLDB instance they started is still running thereby causing the other failures.  In the case I last witnessed this on a dev branch, I had a valid failure in LocalControlRedisDataInitializationTests (the environmentMatchesTransport method, specifically) and TypeConvertingStreamTests. So, perhaps a good way to start exploring this issue is to simulate a failure in one or both of those classes. The false negatives I'm seeing are in the following:  {code} LocalSingleNodeInitializationTests.environmentMatchesTransport RabbitSingleNodeInitializationTests.environmentMatchesTransport RedisSingleNodeInitializationTests.environmentMatchesTransport FileSourceModuleTests.classMethod LocalSingleNodeStreamDeploymentIntegrationTests.classMethod RabbitSingleNodeStreamDeploymentIntegrationTests.classMethod RabbitSingleNodeStreamDeploymentIntegrationTests.classMethod {code}  They all seem to be tests that start the SingleNodeApplication."
Answer: 2184.0

User story: e.g. rabbit.xml source.   <context:property-placeholder location="${xd.config.home}/${configProperties:rabbit}.properties" ignore-resource-not-found="true" />  would be removed and   <rabbit:connection-factory id="rabbitConnectionFactory" host="${host:${spring.rabbitmq.host:localhost}}" port="${port:${spring.rabbitmq.port:5672}}" virtual-host="${vhost:${spring.rabbitmq.virtualHost:/}}" username="${username:${spring.rabbitmq.username:guest}}" password="${password:${spring.rabbitmq.password:guest}}"/>  would look like port="${port}" and a property file in the module directory or POJO in the module lib would specify the default value of the port.  For POJO it would be options_class = org.springframework.xd.dirt.modules.metadata.RabbitSourceOptionsMetadata  For property file it would be option.port.default=5672 option.port.description="cool port number"  This needs to be consistently done across all the modules.       
Answer: 55234.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This applies to a few places (when addressing the issue, a search should be done to uncover any others), e.g.:  ContainerServerApplication:     public static final String NODE_PROFILE = "node";  *Options classes:      "The transport to use for data messages (from node to node)"      "The transport to use for control messages (between admin and nodes)" 
Answer: 69479.0

User story: The XD shell crashes when the following command issued:  stream create test --definition "http | filter --expression=!payload.contains('test') | log"  It looks like the JLine ConsoleReader's expandEvents is set to true by default and this causes the issue:  Exception in thread "Spring Shell" java.lang.IllegalArgumentException: !payload.contains('test') | log": event not found  at jline.console.ConsoleReader.expandEvents(ConsoleReader.java:734)  at jline.console.ConsoleReader.finishBuffer(ConsoleReader.java:604)  at jline.console.ConsoleReader.accept(ConsoleReader.java:1912)  at jline.console.ConsoleReader.readLine(ConsoleReader.java:2537)  at jline.console.ConsoleReader.readLine(ConsoleReader.java:2162)  at jline.console.ConsoleReader.readLine(ConsoleReader.java:2150)  at org.springframework.shell.core.JLineShell.promptLoop(JLineShell.java:517)  at org.springframework.shell.core.JLineShell.run(JLineShell.java:178)  at java.lang.Thread.run(Thread.java:722) 
Answer: 26791.0

User story: "Need to update the spring-xd-extension-reactor support to reflect the changes to Reactor refactorings introduced in v1.1."
Answer: 11215.0

User story: "I am trying to use HDFS as sink while creating streams and I am encountering the following error :  Please refer attached document : Exception - localhost - 8020.txt   The fs.default.name set in hadoop.properties is : fs.default.name=hdfs://localhost:8020  I have also tried the following variation in the hadoop.properties file : fs.default.name=hdfs://127.0.0.2:8020 fs.default.name=hdfs://127.0.0.2:50070  Using these values are also throwing me exceptions as mentioned in the following files attached :  Exception - 127.0.0.2 - 8020.txt  Exception - 127.0.0.2 - 50070.txt   We are using : Pivotal HD 1.0.1 spring-xd-1.0.0.M5-dist  Kindly let us know the way around for this issue.   "
Answer: 37967.0

User story: "The main container context becomes the shared context for modules."
Answer: 10291.0

User story: "xd/lib includes jcl-over-slf4j so we don't need additional commons-logging jars in the modules or extensions:  https://github.com/spring-projects/spring-xd/pull/610"
Answer: 1249.0

User story: "The YARN support in M6 changes most of the config properties, need to update XD to use new ones."
Answer: 5911.0

User story: "Currently, the job notification channels are direct channels. We need to make these pub/sub channels.  With XD-885 (allowing automatic job listeners registration),  this would allow us to create named channel syntax like:  topic:job:myjobname-jobExecution > log topic:job:myjobname-stepExecution > log   "
Answer: 20064.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This will be used by SingleNodeApplication if no ZooKeeper process is available based on the provided client connect string. It will still be recommended that user's run ZooKeeper externally, at least in standalone mode, when running SingleNodeApplication. We should clarify that in the documentation and logs.  It should implement SmartLifecycle so that it can be managed as a bean within an ApplicationContext."
Answer: 17351.0

User story: "The /xd/containers node is the parent where each Container will write an ephemeral child node. The node name should be the Container's ID, and the node data should be the Container's attributes (host, pid, and much more to be added later).  When a Container shuts down cleanly, it should eagerly delete the ephemeral node so that watchers are notified immediately. For any other case (including a network partition), the ephemeral node will disappear after the timeout elapses."
Answer: 1669.0

User story: "When the container shuts down, ContainerStoppedEvent should be published so that appropriate listeners would act on.  Please refer to this discussion here:  https://github.com/spring-projects/spring-xd/pull/612"
Answer: 142607.0

User story: "Post-boot refactoring. XDContainer lifecycle methods are not being used. Refactor by merging relevant functionality into LauncherApplication. Rename LauncherApplication to ContainerServerApplication (consistent with AdminServerApplication).  "
Answer: 226.0

User story: "The Spring Data team recommends using the Jedis driver since the Lettuce driver hasn't had any update activity for several months. Jedis is actively maintained.  We might also want to investigate Redisson which is a fork of Lettuce - https://github.com/mrniko/redisson"
Answer: 140910.0

User story: "This will allow us to control the order of plugins and use plugin(s) to manage the common module context, replacing BeanDefinitionAddingBeanPostProcesser"
Answer: 1798.0

User story: The enum unnecessarily restricts the ability to add new transport (MessageBus implementations) whereas the config location path is open for extensions since it uses wildcards (in message-bus.xml):  {code} <import resource="../../transports/${XD_TRANSPORT}-bus.xml"/> {code} 
Answer: 20431.0

User story: "We currently pull all hdfs config properties from hdfs.properties - change that to use application.yml"
Answer: 10332.0

User story: "This requires exposing properties to the ListenerContainer. Probably cleaner to inject the ListenerContainer into the RabbitMessageBus and expose property placeholders on the LC. Maybe do the same for RabbitAdmin as well. "
Answer: 92123.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Following merge of https://github.com/spring-projects/spring-xd/pull/601, expose a unique id under which a module is known inside a stream. That id (which defaults to the module name) is what should be used as the qualifier for an option name inside a composed module, ie  {noformat} module compose foo --definition "f1: filter | filter"  ==> f1.expression and filter.expression are available {noformat}
Answer: 719718.0

User story: "Following merge of https://github.com/spring-projects/spring-xd/pull/601, allow a module option to be known by several names and elect a short name in composed module options when there is no ambiguity"
Answer: 377046.0

User story: "Following merge of https://github.com/spring-projects/spring-xd/pull/601, use dot as the separator for a composed module option.  Need change to the parser to accept dots"
Answer: 19178.0

User story: "Provide an easy way for users to add beans (e.g., Gemfire cache configuration) or modify default XD configuration such as serializers, and message converters. A simple approach is to add a well known resource selector such as classpath*:META-INF/spring/xd/extensions or include this path in an extensible @Configuration base class.  In addition, we should adopt conventional names for beans that are meant to be extended, e.g. use an xd. prefix."
Answer: 34929.0

User story: "Currently, hsqldb, postgres and mysql job repositories are supported. We need to add configurable oracle jdbc settings."
Answer: 642331.0

User story: "Currently, the XD container uses embedded tomcat only to support management server that acts as the RESTful server for boot's actuator MVC and jolokia endpoints.  If the configuration is set to use a specific management port (using the fixes addressed via XD-1122), then we don't need to have embedded tomcat servlet container in XD container. "
Answer: 724345.0

User story: We need a methodology for providing partitioning hints.  A current proposal uses message headers to provide:  * partition_key – the item to partition on * destination_region – what to target  In the proposal the developer used "partition_key" to route the stream message to the node where data was stored in process.  This was done so downstream stream operations could work on the data with out suffering any network IO.  The "destination_region" was used to target the type of data the downstream streams were going to use in their stream processing.   
Answer: 142384.0

User story: "When importing XD as a gradle project into STS, it fails with  Missing directories spring-xd-hadoop/hdp20 and spring-xd-yarn  mkdir on these directories solves the problem.  The hdp20 case relates to XD-599 - it is not clear why spring-xd-yarn is needed. "
Answer: 223313.0

User story: "While the current setting work while running from your laptop to local deployments.  Or running from your laptop to ec2, they are not long enough for CI to Ec2. This should have good defaults and have CI set them to what it needs."
Answer: 11257.0

User story: "See also XD-1320."
Answer: 31669.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "From https://jira.springsource.org/browse/XD-1231 we understand the importance of modularizing client side javascript code. This story tracks modularization of XD UI."
Answer: 45340.0

User story: "Command such as  yarn app list yarn deploy-xd --zipFile /tmp/myapp.zip --config /tmp/myconfig.yml "
Answer: 35901.0

User story: "Suggest trying with Hortonworks 2.0"
Answer: 38589.0

User story: "There seems to be some intersection with the work for this issue and the rationalization of how module properties are handled.  There will be changes to configuration/property management support such that each module (source, sink, etc) will be able to also be overridden in spring-xd.yml (or wherever -Dspring.config.location points to.  The HDFS sink module for example, will have default values based on it's OptionsMetadata and will be of the form <type>.<module>.<option>   That means in the configuration for hdfs.xml sink, there would be a config section such as  {code:xml}     <configuration>       fs.default.name=${sink.hdfs.hd.fs}       mapred.job.tracker=${sink.hdfs.hd.jt}       yarn.resourcemanager.address=${sink.hdfs.hd.rm}       mapreduce.framework.name=${sink.hdfs.mr.fw}     </configuration> {code}  With default values defined by a HdfsSinkOptionsMetadata class.  The hdfs.xml module file would not contain any references to a properties file.  A file specified by -Dspring.config.location could override the values in a config section such as  sink:   hdfs:     hd.fs : hdfs://foobarhost:8020     hd.jt : 10.123.123.123:9000  etc.  "
Answer: 17068.0

User story: "Add YARN specific code based on Janne's prototyping  Add YARN Client and AppMaster implementations and startup config files  This includes shell scripts to deploy XD to YARN  Test working on Apache 2.2 distribution  We can modify config files, everything should be possible to override by providing command-line args or env variables. ./xd-yarn-deploy --zipFile /tmp/spring-xd-yarn.zip --config /tmp/spring-xd-yarn.yml  "
Answer: 17070.0

User story: "Job restart fails with NPE. See PR for XD-1090:  https://github.com/spring-projects/spring-xd/pull/572 "
Answer: 88037.0

User story: A lot of modules have similar options. Moreover, job modules often have options that belong to at least two domains (eg jdbc + hdfs).  I think that by using FlattenedCompositeModuleOptionsMetadata, we could come up with a way to combine several options POJOs into one. Something like:  public class JdbcHdfsOptionsMetadata {    @OptionsMixin   private JdbcOptionsMetadata jdbc;    @OptionsMixin   private HdfsOptionsMetadata hdfs; }  this would expose eg "driverClass" as well as "rolloverSize" as top level options. Values could be actually injected into the fields, so that eg custom validation could occur (default validation for the mixin class would occur by default)
Answer: 66449.0

User story: "This is so that we can have an ENUM that can show the possible values and autocomplete.  Using just the XML the user has a greater chance to enter an invalid mode.   "
Answer: 9965.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Create XD .zip distribution for YARN that adds an additional sub-project to the spring-xd repo for building the xd-YARN.zip  Link into main build file  Produce a new artifact spring-xd-v-xyz-yarn.zip as part of the nightly CI process -- will now have 2 artifacts, main xd.zip distribution and xd-yarn.zip  Does not include any Hadoop distribution libraries  Does include spring-hadoop jars for Apache22 ‘unflavored’ "
Answer: 2712.0

User story: "See discussion at https://github.com/spring-projects/spring-xd/pull/572"
Answer: 99704.0

User story: "Create a job, launch it but make it fail (eg filejdbc with missing file)  job execution list => it's there, as FAILED. Good  job execution restart <theid> ==> Fails with NPE:  {noformat} 16:59:42,160 ERROR http-nio-9393-exec-7 rest.RestControllerAdvice:191 - Caught exception while handling a request java.lang.NullPointerException  at org.springframework.batch.core.job.AbstractJob.execute(AbstractJob.java:351)  at org.springframework.batch.core.launch.support.SimpleJobLauncher$1.run(SimpleJobLauncher.java:135)  at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50)  at org.springframework.batch.core.launch.support.SimpleJobLauncher.run(SimpleJobLauncher.java:128)  at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source)  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  at java.lang.reflect.Method.invoke(Method.java:606)  at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)  at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)  at org.springframework.batch.core.configuration.annotation.SimpleBatchConfiguration$PassthruAdvice.invoke(SimpleBatchConfiguration.java:117)  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)  at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)  at com.sun.proxy.$Proxy39.run(Unknown Source)  at org.springframework.batch.admin.service.SimpleJobService.restart(SimpleJobService.java:179)  at org.springframework.xd.dirt.plugins.job.DistributedJobService.restart(DistributedJobService.java:77)  at org.springframework.xd.dirt.rest.BatchJobExecutionsController.restartJobExecution(BatchJobExecutionsController.java:146)  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)  at java.lang.reflect.Method.invoke(Method.java:606)  at org.springfram {noformat}"
Answer: 60835.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Create a job, execute it a couple of times, destroy it and then invoke job execution list.  The job name column should mention that a job is defunct (even though a job with the same name could have been re-created in the interim)"
Answer: 179614.0

User story: "Disregard the missing date that is caused by another problem. Here is the setup: {noformat} xd:>job execution list   Id  Job Name  Start Time                        Step Execution Count  Status   --  --------  --------------------------------  --------------------  ---------   13  foo         Europe/Paris                    0                     STARTING   12  foo       2014-02-12 15:39:46 Europe/Paris  1                     FAILED   11  foo       2014-02-12 15:39:29 Europe/Paris  1                     COMPLETED   10  foo       2014-02-12 15:38:36 Europe/Paris  1                     COMPLETED   9   foo       2014-02-12 15:38:21 Europe/Paris  1                     COMPLETED   8   foo         Europe/Paris                    0                     STARTING   7   foo       2014-02-12 15:25:41 Europe/Paris  1                     COMPLETED   6   foo       2014-02-12 15:25:04 Europe/Paris  1                     FAILED   5   foo       2014-02-12 15:14:32 Europe/Paris  1                     FAILED   4   foo       2014-02-12 15:14:13 Europe/Paris  1                     FAILED   3   foo       2014-02-12 15:13:54 Europe/Paris  1                     FAILED   2   foo       2014-02-12 15:13:18 Europe/Paris  1                     FAILED   1   foo       2014-02-12 15:12:58 Europe/Paris  1                     FAILED   0   foo       2014-02-12 15:11:44 Europe/Paris  1                     FAILED  xd:>job execution restart --id 12 Command failed org.springframework.xd.rest.client.impl.SpringXDException: Job Execution 12 is already running. {noformat}  while the server exception is a bit better: {noformat} Caused by: org.springframework.batch.core.repository.JobExecutionAlreadyRunningException: A job execution for this job is already running: JobInstance: id=11, version=0, Job=[foo]  at org.springframework.batch.core.repository.support.SimpleJobRepository.createJobExecution(SimpleJobRepository.java:120) {noformat}  I'd argue we should not speak in terms of execution ids if possible, but rather in terms of job names "
Answer: 149827.0

User story: "When using a JSR303 annotated class for module options, the binding failures should be bypassed, as they interfere with completion proposals. "
Answer: 17303.0

User story: When trying some of the examples of XD-159, came up with weird behavior of the transform module.  This boils down to: {noformat} stream create foo --definition "http |transform --expression='new java.lang.Integer(payload)' |  transform --expression=payload.getClass() | log" http post --data 42   ==> Integer (OK) http post --data WTH => WTH (!) {noformat}  Seems that when the expression can not be evaluated, the incoming payload is transmitted as is
Answer: 111590.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "HATEOAS 0.9 introduced some support for templated links. This should be leveraged to properly handle eg /streams/{id} instead of using string concatenation"
Answer: 737933.0

User story: "Commit https://github.com/spring-projects/spring-xd/commit/761cd5e8250c055878caf3a789ab5b3254ba48e8 introduced support for FTP and added a bunch of .x classes.  These should not belong to DIRT proper though, and should be added to an extension style project. The job(s) module would then depend on them"
Answer: 212466.0

User story: "currently the file sink only supports append.  User should support an overwrite feature."
Answer: 1172.0

User story: There are few boolean type module option properties whose default values are specified in the module definitions than their corresponding ModuleOptionsMetaData.   Also, when using boolean we need to have module option using primitive type boolean than Boolean type.  Currently, these are some of the module options that require this change:  "initializeDatabase" in modules filejdbc, hdfsjdbc job modules, aggregator processor module, jdbc sink module  "restartable" in all the job modules  "deleteFiles" in filejdbc, filepollhdfs job modules       
Answer: 31110.0

User story: Currently, the fileDeletion listeners are added to filepollhdfs and filejdbc OOTB job modules so that the files are deleted after successful completion of jobs that write the file into hdfs/jdbc.  We have "--deleteFiles" option in ResourcesIntoJdbcJobModuleOptionsMetadata (from https://github.com/spring-projects/spring-xd/pull/562)  which makes it available for hdfsjdbc job module as well. But it is not supported yet as it involves deletion of HDFS files.  We need the file deletion listeners for the hdfsjdbc and hdfsmongodb job modules so that if opted to delete files, it can be supported.  
Answer: 203962.0

User story: "Commit 96de9fcfaf32719413015a1a6bace1b30b6b9610 strengthened module type inference, but some corner cases remain (marked as TODOs and commented out assertions in tests).  To be effective, we need to look at the whole deployed stream (or composed module). Modify ParsinContext accordingly."
Answer: 37.0

User story: "If JMX is enabled, some of the integration tests fail.  This is similar to what we see in XD-1295.  One example of this case is, the test classes that extend StreamTestSupport.  In StreamTestSupport, the @BeforeClass has this line:  moduleDeployer = containerContext.getBean(ModuleDeployer.class);  When JMX is enable, the IntegrationMBeanExporter creates JdkDynamicProxy for the ModuleDeployer (since it is of type MessageHandler) and thereby the above line to get bean by the implementing class type (ModuleDeployer) fails.  There are few other places where we use to refer the implementing classes on getBean(). Looks like we need to fix those as well.  "
Answer: 32182.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently, the reactorEnv bean is defined in module-common context and the spring-xd-dirt has the runtime dependency over spring-xd-extension-reactor project.   This enables boot's ReactorAutoConfiguration to initialize the reactor environment, we have the reactor setup configured for both admin and container server applications.  Since reactor environment is not being used by container and only used by the reactor-syslog module, we can move the reactorEnv bean definition in reactor-syslog module.  There is one caveat in this approach as the reactor environment gets setup everytime a new reactor-syslog module is deployed."
Answer: 6954.0

User story: Currently, the job module's batch job's bean id should be "job". This also causes the job name to be 'actual-job-name + ".job"' and the batch job controllers require to search for job with suffix ".job".   Removing this constraint would help us avoiding these.
Answer: 4256.0

User story: "There is no point in providing completion with something that will fail when the user tries it. The information about a module being a composed is now available at the REST layer, so should be used"
Answer: 582223.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The current configuration prevents modules to have default values that evaluate to null. The workaround is to either:  - have the module have its own PPC (which allows nulls) - rid the placeholders with ${foo:}"
Answer: 185569.0

User story: xd:>stream create --name simple --definition "http | transform | filter | transform | file" Created new stream 'simple' xd:>stream create --name tapSimple --definition "tap:stream:mystream.transform > file" Created new stream 'tapSimple'  There isn't a stream named "mystream"... I don't remember if we want to allow for this (set up taps before there is a stream) or if it should be an error.  Otherwise, works as expected  xd:>stream create --name tapSimple2 --definition "tap:stream:simple.transform > file" Command failed org.springframework.xd.rest.client.impl.SpringXDException: XD144E:(pos 11): Reference to 'transform' is not unique in the target stream 'http | transform | filter | transform | file', please label the relevant module and use the label, or use a suffix index to indicate which occurrence of the module, e.g. 'transform.0' tap:simple.transform
Answer: 88046.0

User story: "see discussion at https://github.com/spring-projects/spring-xd/pull/495#discussion-diff-9291037"
Answer: 955185.0

User story: "see CompletionProviderTests#testUnfinishedModuleNameShouldReturnCompletions()  Ideally, would require a change in the parser so that it knows which kind of module was expected when it failed."
Answer: 11840.0

User story: "When doing dsl completion in a stream definition and a module option accepts a value that has a closed set of possible values (eg booleans, enums), we can provide completions for those.  "
Answer: 955232.0

User story: "This is about computing the value to support expressions such as ${xd.stream.name} as a default.  Initial discussion suggested to leverage the work done in XD-1175 by having a custom @LateValue (or @DeployTimeValue, etc) be resolved at deployment time"
Answer: 110517.0

User story: "Will likely involve having the module identity (type+name) be part of the OptionsMetadata identity/cache key"
Answer: 756481.0

User story: Create a better UI instead of Boot's default "Whitelabel Error Page"
Answer: 142286.0

User story: "The kite SDK is used to write Avro records in a Kite specific format and also it support the parquet format for which we will eventually support."
Answer: 93393.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: May want to fix "properly" when tackling the module options for composed modules, but this is currently broken (and wasn't at some point):  module compose upperHttp --definition "http | transform --expression=payload.toUpperCase()" stream create foo --definition "upperHttp | log"  This will fail saying that ${port} can't be resolved  This will work though: module compose upperHttp --definition "http --port=9000 | transform --expression=payload.toUpperCase()" stream create foo --definition "upperHttp | log"   Note that  stream create foo --definition "upperHttp --port=xxx | log" should work too wut won't, but that's another bug (will create after this one)
Answer: 39127.0

User story: "To show best practice, our batch jobs should include these listeners so that notifications can be sent.  In particular it is desirable that jobs with file item readers can send the files that were processed so another stream can be sent the file name when the job completes to move/delete the file"
Answer: 4069.0

User story: "Since makeUnique, dateFormat and numberFormat now have their own module options now, they are nicely advertised as options to a job (and will benefit from code completion soon), so they can be removed from the shell (where they currently allow for a misconfiguration if set at both the job and shell level)"
Answer: 109.0

User story: "Currently, few of the boot's actuator endpoints go missing in the EndpointHandler mapping. They are: BeansEndpoint, dumpEndpoint, traceEndpoint, healthEndpoint, infoEndpoint.  Also, the EndpointHandler mapping doesn't even happen in case of LauncherApplication. I think this is because the LauncherApplication context starts with port '0' and the TomcatEmbeddedServletContainer sets the local port for it later. With port '0', the Endpointhandler mapping is disabled during the EndpointHandler mapping bean creation."
Answer: 80326.0

User story: "Improve how the state of the stream is managed.  A deploy command moves the stream from the undeployed state to the deploying state. If all modules in the stream are successfully deployed, the stream state is ‘deployed’ If one or more module deployments failed, the stream state is failed.  Any modules that were successfully deployed, are still running.    Sending an undeploy command will stop all modules of the stream and return the stream to the undeployed state.  For the individual modules that failed, we will be able to find out which ones failed.  Not yet sure if we can try to redeploy just those parts of the stream that failed.  See the [design doc|https://docs.google.com/a/gopivotal.com/document/d/1kWtoH_xEF1wMklzQ8AZaiuhBZWIlpCDi8G9_hAP8Fgc/edit#heading=h.2rk74f16ow4i] for more details.  Story points for this issue are the total of all the story points for the subtasks."
Answer: 210823.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The logic can be found in DefaultModuleOptionsMetadataCollector but caused problems in the initial PR. Revisit if needed"
Answer: 141848.0

User story: The modules are exposed via JMX and in turn exposed over http via jolokia.  See https://jira.springsource.org/browse/XD-343.  This issue is to develop a helper method that given a stream id and/or module name, assert that the number of messages processed after sending stimulus messages is as expected. e.g.  int originalCount = getCount("testStream", "file");  //do stuff that generates 100 messages assertCount("testStream", "file", 100, originalCount)  For now we can assume we know the location of where the modules are located by assuming we have only one container deployed.
Answer: 142541.0

User story: Currently, if we want to bind values to script variables we need to put them in a properties file like so:  xd:> stream create --name groovyprocessortest --definition "http --port=9006 | script --location=custom-processor.groovy --properties-location=custom-processor.properties | log  Ideally it should be:  xd:> stream create --name groovyprocessortest --definition "http --port=9006 | script --location=custom-processor.groovy --foo=bar --baz=boo | log   
Answer: 775313.0

User story: "See also XD-451 as reference."
Answer: 15375.0

User story: "Create a first pass at an acceptance test app for a stream definition of http | log.    This will involve creating two new projects in xd  1. spring-xd-integration-test 2. spring-xd-acceptance-tests  #1 will contain generally useful utility methods for acceptance test, such as sending data over http, obtaining and asserting JMX values of specific modules. #2 will contain tests that use #1 to test the various out of the box modules provides in XD."
Answer: 50344.0

User story: "* Use the cleanup app from XD-1243 to stop previous CI runs of XD on EC2. * Build XD-EC2 deployer from github. * Use XD-EC2 Deployer to deploy the CI XD-Instance * Should produce artifact that contains the URL     * admin server of the XD cluster.    * container servers of the XD cluster"
Answer: 22081.0

User story: "Application will shutdown all servers with a specific name.   Application will take a --cluster-name parameter.    Generate artifact to state success or failure  "
Answer: 10389.0

User story: "The deployment of nodes is sequential, we can reduce the time to deploy a cluster greatly by having these tasks execute in parallel."
Answer: 2579.0

User story: See https://quickstart.atlassian.com/download/bamboo/get-started/bamboo-elements  "Stages are comprised of one or more Jobs, which run in parallel"  we would like the tests across the rabbit and redis transport to occur in parallel.
Answer: 69767.0

User story: See https://quickstart.atlassian.com/download/bamboo/get-started/bamboo-elements  "Stages are comprised of one or more Jobs, which run in parallel"  we would like the tests across the rabbit and redis transport to occur in parallel. 
Answer: 69768.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Run test application developed in XD-1245  "
Answer: 38425.0

User story: "Add a stage to the plan that will stop any instances that the CI process may have started before and relaunch a 2 node install based on rabbit.  https://build.springsource.org/browse/XD-ATEC2 was created as an empty shell.  The running of across different transports will be handled in a separate story along with adding a stage to run a 'hello world' acceptance test.  "
Answer: 38386.0

User story: "This functionality should be added as a command line option to the main app in the spring-xd-ec2 project"
Answer: 10738.0

User story: "Blog post http://naleid.com/blog/2013/01/24/calling-gruntjs-tasks-from-gradle/  seems to be the definitive reference...."
Answer: 29648.0

User story: "Create a project that includes build and test automation for a new Angular based UI.  This work is independent of calling the UI build step from gradle.  A super minimal UI, just to have some basic code, is all that is required.   This should use   Grunt Jasmine Karma Bower YUIdoc (separate story?)  UI Components from backbone should be available in the base project.  "
Answer: 29651.0

User story: "AbstractSingleNodeStreamDeploymentIntegrationTests is the basis of 'state of the art' testing for a stream that allows you to get a reference to the input and output channel of the stream  http | filter | transform | file.  One can send messages to the channel after the http module, but before filter and one can retrieve the messages that were sent to the channel after the transform module but before file.  The current implementation inside AbstractSingleNodeStreamDeploymentIntegrationTests can be improved in terms of ease of use for end-users.    The issue is to create as simple a way as possible for a user to test their processing modules/stream definitions without having to actually do a real integration test by sending data to the input module.  Either as a separate issue or as part of this one, the documentation   https://github.com/spring-projects/spring-xd/wiki/Creating-a-Processor-Module  should be updated to explicitly show how to use this issue's test functionality. "
Answer: 49623.0

User story: "https://sonar.springsource.org/dashboard/index/7173?did=3  Shows which of our current tests take the most time to execute.  xd.dirt.stream and xd.shell.command are where the most time is spent.  In xd.dirt.stream it seems likely that time can be reduced by not restarting a new single node server per test, but sharing it across tests, e.g.   RabbitSingleNodeStreamDeploymentIntegrationTests    LocalSingleNodeStreamDeploymentIntegrationTests  RedisSingleNodeStreamDeploymentIntegrationTests    As a first pass, the test that take longer than 15 seconds in that report should be investigated. "
Answer: 17965.0

User story: "Not sure if this is best done via Sonar our sonar build plan, the nightly one, or the frequent one off master...  Open question is if we want to fail a build do to code coverage levels."
Answer: 10652.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Build should be able to generate code coverage reports.  After a quick tour of the intertubes it seems that JaCoCo is a well maintained project and has first class support inside gradle.  http://www.gradle.org/docs/current/userguide/jacoco_plugin.html "
Answer: 9336.0

User story: "Currently, there are test data(e.g: stream name) not being cleaned up during teardown especially when there is a test case failure. This breaks the test suite when the same test data is used by other tests.  We need to move the cleanup logic at an appropriate level so that the test data is always cleaned up irrespective of the test result."
Answer: 18709.0

User story: The MBeanServer is referred by XD admin/launcher when JMX is enabled (by setting --jmxEnabled option) and this is defined in xd-global-beans.xml.  The MBeans that are exposed by the modules also use the same MBeanServer define above and there is a duplicate MBeanServer definition (from jmx/common.xml) which the MBeanExportingPlugin adds as a component to the module which doesn't seem to be needed.  Also, currently the flag "jmxEnabled" is generic and used by adminserver/launcher as well as the module MBeanExportingPlugin. If we have a separate flag to enable the JMX *only* for modules then, a separate definition of MBeanServer could be necessary. 
Answer: 1504.0

User story: "Currently, the 'modules' project is marked as java project to enable eclipse/idea metadata files generation. But it generates a 'build' directory with a jar that has empty MANIFEST file.  This build directory also gets copied into the bundle after 'dist'."
Answer: 1524.0

User story: "Batch jobs should use application.yml provided connection as default. They now have their own configuration in batch-jdbc.properties. This config needs to account for any changes made to application.yml settings so the data is written to the batch metadata database by default."
Answer: 8647.0

User story: "Currently twitterstream emits native twitter json whereas twittersearch uses SI/Spring Social and emits spring social Tweet types. This makes it difficult to replace twitter sources and reuse XD stream definitions.  This requires coordination with SS 1.1.0 and SI 4.0 GA releases. NOTE: I think it's a good idea to continue to support native twitter JSON, keep as an option for twitterstream, but the default should be Tweet types."
Answer: 198155.0

User story: "In distributed batch processing in XD, the JobLocator implementation for getJob(String jobName) should return a valid Job (FlowJob/SimpleJob).  Since we won't we relying on the MapJobRegistry's joblocator implementation which doesn't work in distributed use case, we need to have an appropriate way to return FlowJob/SimpleJob using XD's BatchJobLocator."
Answer: 60456.0

User story: "The job names used by the tests should be unique across the tests when use the same JobRepository.  "
Answer: 27585.0

User story: "Using JSR303 groups, which should be derived from injected values"
Answer: 10476.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Some boot classes we compile against have changed or been replaced."
Answer: 19206.0

User story: batchHashtagCount and batchWordCount  projects need "hadoop fs ls" instructions need to be updated.  
Answer: 19.0

User story: "This was added in bash scripts as part of XD-1186."
Answer: 70893.0

User story: "For some reason, the partitioned batch jobs are storing  {{StepExecutions}}s in the DB with a null ID.  This causes {{JobCommandTests.testListStepExecutionsForSpecificJobExecution()}} to fail because the HATEOS code asserts not null...  {code} 18:25:26,185 ERROR http-nio-9393-exec-3 rest.RestControllerAdvice:186 - Caught exception while handling a request java.lang.IllegalArgumentException: [Assertion failed] - this argument is required; it must not be null  at org.springframework.util.Assert.notNull(Assert.java:112)  at org.springframework.util.Assert.notNull(Assert.java:123)  at org.springframework.hateoas.mvc.ResourceAssemblerSupport.createResourceWithId(ResourceAssemblerSupport.java:87)  at org.springframework.xd.dirt.rest.StepExecutionInfoResourceAssembler.toResource(StepExecutionInfoResourceAssembler.java:39)  at org.springframework.xd.dirt.rest.BatchStepExecutionsController.list(BatchStepExecutionsController.java:107) {code}  For some reason, the query for objects with the {{jobExecutionId}} also returned these two objects with null keys.  Blowing away my data directory fixes the problem (until I run another partitioned batch job).  I need to figure out why spring batch is creating these bad records, but we should probably add some defensive code to protect against null IDs.  You can reproduce by building against my XD-1146 branch. "
Answer: 50166.0

User story: "The filejdbc jobs isn't included in the test scripts"
Answer: 1520.0

User story: "We should use fileName, fileExtension properties and default to /xd/jobname as directory"
Answer: 1912.0

User story: "xd-shell is using the default spring-shell help command.  Need to create a help command specific to XD so that it can list the --hadoopDistro command line option.  Note, the hadoopDistro command line option is actually processed by the xd-shell bash script"
Answer: 989450.0