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: "*Acceptance*  * NXRM supports {{npm dist-tag add}}, {{npm dist-tag ls}}, {{npm dist-tag rm}}  * A user can add multiple tags to a package  * A user can install  by tag (with 'latest' being the default)  * in general, this command behaves as described in https://docs.npmjs.com/cli/dist-tag  * npm dist-tag ls should work against proxy, hosted and group repositories.  * npm dist-tag add, rm should work against hosted repositories."
Answer: 1854958.0

User story: "*Background*  NX2 allows for the configuration of the LDAP query cache duration (as per http://books.sonatype.com/nexus-book/reference/ldap-sect-enterprise.html). This is pretty important to control the impact of a busy repo manager onto the LDAP server.  The NX3 apparently does have cache support, but lack the ability to control the duration.    *Acceptance*  * NX3 admins can configure the LDAP query cache duration   ** *REFINE* the definition of this field - what zero or -1 means, for instance  * The 2x-3x upgrade process brings this setting over from NX2"
Answer: 790317.0

User story: "Modal dialogs can&rsquo;t be quit by hitting ESC when the &ldquo;x&rdquo; icon is not shown. This is the default behavior for most of our modals, and should not be due to accessibility/usability reasons.    From Jason:    I belive we should use the window.closable:true feature to gain ESC functionality at the expense of the additional (x). I have no issue with the 2 buttons which do the same thing in this case. I prefer it actually. But abs want to ensure that ESC works properly and to hack in our own impl for this would be bloated waste and would rely on private internals of Ext.window.Window which could cause problems for any upgrade.    Acceptance:    * Modal dialogs can be quit with the ESC button   * Choosing to quit a dialog should result in no state change to the system.   ** It is essentially the same as Cancel"
Answer: 305459.0

User story: "I want to create daily backups for nexus ( repositories and configurations) . "
Answer: 801.0

User story: "The chapter Configuring Maven and Other Build Tools should be renamed and repurposed to be a generic chapter about the Maven repo format just like we have the chapters for Docker, Nuget, Raw and NPM now. "
Answer: 164035.0

User story: "Today, we allow you to remove the Nexus authorizing or Nexus authentication realm, which (if you haven’t configured any other realms) prevents anyone (including the admin) from logging into the web UI. This is bad UX.    Demo: http://take.ms/vTBEX    Ideas for improvement:    + Combine the Nexus authenticating and authorizing realms into one.  + Make the Nexus authenticating and authorizing realms mandatory.  + Create a separate realm, tied to the admin account, which cannot be deactivated"
Answer: 672811.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: "On a fresh Nexus 3 install the browse as well as the search functionality for a Maven repository orders the columns from left to right as     Name, Group, Version    For a regular Maven repo format user (Maven, Gradle, Ivy...) this seems weird. E.g. the coordinates are called GAV coordinates and the directory structure in a Maven repo also uses the order from larger to smaller. So I think the default should maybe be    Group, Name, Version    This might be weird for other formats, especially if they dont use group. Maybe a format specific order or hiding if no values would work."
Answer: 202919.0

User story: Properties I think are:  * MavenAttributes.P_CONTENT_LAST_MODIFIED  * MavenAttributes.P_CONTENT_ETAG  * MavenAttributes.P_LAST_VERIFIED (this one is triplicated as NugetGalleryFacetImpl. P_LAST_VERIFIED_DATE and RawContentFacetImpl. P_LAST_VERIFIED_DATE). These all serve same purpose: helps ProxyFacetSupport in age calculation.    Also, all these are currently saved as "format specific" attributes, which clearly they are not.    It seems this should be generalized, and the attribute should not be format specific, but "lifted" to core attributes and handled by core.
Answer: 11378.0

User story: "Published SNAPSHOTs appear in search results with their raw timestamped version, when the expectation is that we can search at the x-SNAPSHOT version and find only the latest one.    *Acceptance criteria*  * Show only the latest snapshot in the search results (our assumption is that people don't care about older snapshots)    h5. Technical Notes  * To accomplish this we'll have to parse the version string from the results to pull out the timestamp.  * Possibly also we can pull the latest version from maven-metadata.xml"
Answer: 1683487.0

User story: As a new user, I want to have a clear status indicator for staging repositories, so that I can not search google for hours trying to find answers because I'm lazy and don't read the documentation.  Can this be changed from open/closed to "needs validation"/"validated" statuses and the "close" button changed to "Validate" 
Answer: 9.0

User story: "In https://issues.sonatype.org/browse/NEXUS-7800, I tested this feature in NX2 and NX3.  There are some differences in NX3, I wanted to make sure were noted in the new documentation.    Manfred said they should be but asked for a ticket to confirm that all the notes there were updated.  This is that ticket."
Answer: 128272.0

User story: "And adapt to the RAW format including other cases beyond a Maven site.. probably rename the chapter as well. "
Answer: 200080.0

User story: I don't know if this goes in the Foreword or the Preface, but I think we need a section of the book that tells the reader how to approach Nexus.   How the book can be read.    "To start using Nexus, we recommends reading the introduction and then following the instructions in the blahblah blah.....
Answer: 2984798.0

User story: "Meaning the SSL management UI in Nexus .. not setting up serving via SSL and such.. "
Answer: 361444.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: "Added/updated subsections to LDAP connection and auth, user/group mapping & a link to external role mapping"
Answer: 604512.0

User story: Maven2 hosted repositories somehow (how?) expose the capability to regenerate Maven metadata.    Acceptance Criteria:    - A user will be able to regenerate the Maven metadata that is based on inspecting the Maven poms   - Only applies to Maven hosted repos     Question:    - This implies that we'd have another story for a means to process the contents of a repository   - Index.html could potentially be done in a similar fashion, should we? Leaning towards not doing anything (for now)     Technical Direction:    - -This will involve some clean, fast and efficient way of walking component metadata, a CMA equivalent of the Walker API- moved out to [NEXUS-8474|https://issues.sonatype.org/browse/NEXUS-8474]    -- We need to be careful about loading the data   - Observe code to see if we need to do this beyond hosted repos (<USER> NX2 performs the task only against hosted and group repositories, hosted ones are where work is done, and groups "cascade" the operations to members)
Answer: 119489.0

User story: "Currently CMA's httpbridge component does not support HEAD (probably would respond with 405 Method not allowed, which would probably choke some clients, as HEAD is usually supported (and used by clients like Maven).    This means, that verb HEAD should behave exactly same as GET (as HTTP response headers, all of them matters), except no response body should be sent downstream."
Answer: 11554.0

User story: "In order to rebuild metadata from blobs (or other disaster recovery type work), we need a way of visiting/walking/iterating the blobs in a blob store."
Answer: 62062.0

User story: "Acceptance criteria:  * There is a service to generate hashes for assets in one or more standard algorithms  * There's a standard spot in asset metadata for storing these hashes  * Wire it up so that Raw and Simple assets record these actual hashes (as opposed to format-specific ways of obtaining the expected hashes, which should also eventually be stored)  "
Answer: 6591.0

User story: "A few places still not using NX.I18n.    * -Review all usage of NX.Messages API-  * -Review all usage of NX.Dialogs API-  * -Review all usage of NX.Security API-  * -Review all usage of 'waitMsg:' specifications    Classes in nexus-rapture-plugin:  * -NX.view.AboutWindow-  * -NX.view.Authenticate-  * -NX.view.ExpireSession-  * -NX.view.UnsupportedBrowser-  * -NX.view.header.AdminMode-  * -NX.view.header.BrowseMode-  * -NX.view.header.UserMode-  * -NX.view.header.Help-  * -NX.view.header.Messages-  * -NX.view.feature.NotFound-    Classes in nexus-coreui-plugin:  * -NX.coreui.controller.Metrics-  * -NX.coreui.controller.NuGetRepositorySettings-    -Pending further investigation fore coreui and proui modules.-"
Answer: 18409.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: "If you call storageFacet.createBlob(), or storageFacet.deleteBlob() but then roll back the transaction, the changes occur anyways. This can lead to orient and the blob store getting out of sync.    A simple pattern for handling this was built into some older CMA work where it was called BlobTx - it just accumulated new and to-be-deleted blobs in separate lists, and when the transaction was rolled back or committed, the corresponding list of blobs all get soft-deleted.    This isn't bulletproof transactionality, but it's much better than the current approach which completely ignores transactions for blob operations, and will err on the side of stray blobs rather than over-eagerly deleted blobs."
Answer: 2714.0

User story: "Following the pattern established by the Simple repository format, add permissions and permission-checking to the raw repositories."
Answer: 4234.0

User story: Update to more recent Groovy version. Groovy 2.3.7 appears to be the latest available version with a corresponding groovy-eclipse compiler, with 2.3.9 being the last release published at this time.    Java 8 interoperability is only "official" since 2.3.x so hopefully this will head off any compatibility issues    Acceptance Criteria:  - Nexus 3 OSS and Pro will use Groovy 2.3.7
Answer: 15794.0

User story: "Implement a repository which proxies a remote HTTP site and stores any files (of any format) in the CMA repository storage facet. Only GET requests are honored (others are rejected). Configuration parameters include the remote URL being proxied, the not-found and stored-item expiry times.    This will serve as a reference implementation for more complex formats' proxy repositories."
Answer: 41621.0

User story: "Implement a simple bucket of files that allows for any file to be shared, so that they appear to be a repository while preserving the path. This is the simplest of the repo formats in Nexus.     Equivalant of Site Repository from Nexus 2. We did this because Maven uploaded files such as HTML to describe your repo. This allows for documentation/etc... to be shared. "
Answer: 30184.0

User story: "Implement settings UI for Kenai (similar to Crowd UI)"
Answer: 9203.0

User story: "Staging has already been moved to orient db but old modello based config classes are still in place and used to upgrade from staging.xml.    Lets remove the modello classes and take care of upgrade during NX2->NX3 migration.    Note: Removing modello will mean that quite a bunch of staging legacy ITs will have to be rewritten as they are copying over a staging.xml"
Answer: 27685.0

User story: "PGP configuration has already been moved to a capability but old modello based config classes are still in place and used to upgrade from pgp.xml.    Lets remove the modello classes and take care of upgrade during NX2->NX3 migration    Note: Removing modello will mean that a bunch of staging/pgp legacy ITs will have to be rewritten as they are copying over a pgp.xml"
Answer: 17586.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: "Crowd configuration has already been moved to a capability but old modello based config classes are still in place and used to upgrade from crowd-plugin.xml.    Lets remove the modello classes and take care of upgrade during NX2->NX3 migration"
Answer: 17790.0

User story: Replace modello based LDAP configuration with orient db    Acceptance Criteria:  - Make LDAP plugin stop use Modello (and have dropped use of it alltogether), and have it tied into "config" OrientDB instance. (/)  - Module tests related changes as needed (as many of those "stuff" ldap.xml under tests), true for nexus-ldap-plugin module UTs as for nexus-ldap-plugin module ITs (/)  - Remove use of Plexus from module UTs and ITs (as current tests were unmaintable, this was a desperate step of mine -- <USER> (/)  - Update nexus-ldap-testsupport, remove Plexus (as use of the ldap testsupport module implied use of Plexus in dependant module, which is unwanted) (/)  - Introduce nexus-ldap-client (needed to be able to manipulate LDAP configuration from "real" ITs, as copying ldap.xml does not work anymore) (/)  - Update OSS legacy and modern ITs as needed (replace copied ldap.xml's with LDAP Rest Client use) (/)  - Update Pro legacy and modern ITs as needed (replace copied ldap.xml's with LDAP Rest Client use) (/)
Answer: 78211.0

User story: "Replace modello based Kenai configuration with a capability"
Answer: 59557.0

User story: "Content from sources needs to be able to detect the type, by asking Tika and recoding this in metadata.  Additional logic will also be needed to layer ontop to validate that content we get is what we think, to cope with issues like asking for a .jar file and getting a .html error page.    Acceptance Criteria:  - You will be able to deploy a Maven site to a hosted raw repo and when viewing it in the browser it will display properly due to content types being returned"
Answer: 131101.0

User story: "Implement the 8shapes visual index as a tab in the developer console.    Reference:    https://www.dropbox.com/sh/hh02tj5th6dsh2q/AABNgGt8ZNk41i-ZlzvSZSLsa/visual%20index?dl=0#lh:null-Sonatype%20Nexus%20Visual%20Index.psd    Out of scope items:    - Icons (we aren’t using all the icons represented in the style guide)"
Answer: 20319.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: "As a .NET developer, so that I can get quicker and more reliable access to remote packages, I want the ability to have NuGet repos cached locally     Acceptance Criteria:  - Implement handlers for the various read-only NuGet gallery protocol endpoints (ODATA queries, downloading, etc.).   - Implement the caching of remotely-fetched components in component storage.  - If a user requests a package we don't have by URL we should send a request to fetch the metadata from the remote proxy  - Feed counts should reflect what the upstream repo reports  -- Search results will be slightly different due to the algorithms we use versus NuGet.org  - If the remote repo goes down, a user should be able to still use the proxy repo with locally available metadata and packages  - Locally cached NuGet metadata should be visible in Nexus ElasticSearch results (regardless of whether we have the packages yet)  - Nexus Admins will be able to configure the cache duration/size for queries to remote repos so that we don't overload the remote repo  - If a user Searches on the NuGet Feed search results are capped at 40 entries  - Supported clients are Visual Studio 2013's package manager, the VS package manager powershell utility, the standalone Nuget.exe command-line client, and the Nuget Package Manager."
Answer: 182870.0

User story: "Implement storage for NuGet metadata and content."
Answer: 63492.0

User story: "Placeholder story.    Determine when cached components should be deleted (seems likely in response to the originating Source being deleted). Consider soft deletion of the source, the component metadata, the blobs."
Answer: 129408.0

User story: "Implement a NuGet ComponentSource.    Create the source, the domain object for the metadata/asset (as appropriate), config/factory.    Support all of the read-only aspects of the NuGet gallery protocol (e.g. fetching content, ODATA queries such as feeds, counts, etc.)."
Answer: 44598.0

User story: "View config includes a content storage policy: the view either to uses the default blob store, or one which writes to a location specified in the view config. (Well, really it's a sort of inline blob store config.)"
Answer: 134136.0

User story: "Acceptance Criteria:  - Add and test support for the ability to use the npm deprecate command to deprecate a package  - Add and test support for the ability to use the npm deprecate command to UNdeprecate a package  - Visually show that the package has been deprecated in Search and Browse    This is the alternative for npm unpublish ( NEXUS-6892 )"
Answer: 485445.0

User story: "Need UI for administration of various CMA components like:    * sources  * views  * blobstores"
Answer: 143089.0

User story: "Elaborate on the concept of source availability. In both config and instantiated sources, handle state tracking for:    * auto-blocking on communication errors with escalating retry times  * manual blocking  * correct view behavior when sources are removed entirely"
Answer: 90899.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: "Component sources need configurable HTTP connection parameters, including:    thread/connection pool sizes  authentication credentials  redirection-following policy  schema downgrade policy    Expose a standard way of configuring HTTP connection parameters for connection sources (presumably written into ComponentSourceConfig's Map), and a framework for instantiating those pools and serving connections to HTTP-based component sources.    Consider SSLSocketFactory functionality described in NEXUS-7594"
Answer: 48599.0

User story: "The regular NPM Registry servers provide the API that allows Web clients to easily integrate with them to navigate, search, etc.    https://registry.npmjs.org/  http://registry.nodejitsu.com/    Those can be used by solutions that will be reading data from CouchDB and ElasticSearch...     https://github.com/npm/npm-www  https://github.com/nodejitsu/browsenpm.org    Instead, could Sonatype provide a refactored version of npm-www that provides what https://github.com/npm/npm-www#3b-running-the-databases-and-www-separately describes? That way, we can provide enterprise users with a familiar website Node JS experience when looking for private/internal modules, as well as public ones."
Answer: 370063.0

User story: "We are currently unofficially supporting Java 8 - we would like to officially support it. The only way to do that is run all Nexus tests using CI Java 8 on release branches.    This task is about setting this up permanently.    In addition any further work required to officially support Java 8 should be done."
Answer: 288226.0

User story: "this is a test"
Answer: 2.0

User story: "Currently the MESOS HTTP/HTTPS health checks hardcode the IP address to 127.0.0.1 while performing the pings on the containers. With IPv6 containers, even dual stack kernels the container will have both the IPv4 and IPv6 loopback interfaces (127.0.0.1 and ::1). Further, its upto the application's discretion to either open a INET or an INET6 socket which would imply that to support IPv6 containers the MESOS HTTP/HTTPS health checks need to be configurable to perform health checks on 127.0.0.1 or ::1.   A proposal here would be to introduce the concept of a transport on which MESOS HTTP/HTTPS health checks work. That is the framework specifies whether MESOS HTTP healthchecks work over TCP or TCP6. "
Answer: 81493.0

User story: "When checking http://mesos.apache.org/documentation/latest/. The API list is not friendly. I would like to propose using http://swagger.io/.  It will be more readable and friendly. Looking forward to having one Shepherd to help here."
Answer: 14.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: "When stateful services like Apache Samza, Kafka must be restarted with using Mesos, the framework must have a way of specifying a preferred host with the request.   More background: I work on Apache Samza , a distributed stream processing framework. Currently Samza supports only Yarn as a resource manager. (there have been requests to run Samza with mesos). A cluster (200 nodes 'ish) runs many Samza Jobs (about 3500). Each Samza Job has its own framework that requests resources (containers) for the job to run. Each such container uses GBs of local state  . When such a container(resource) is started on a different host by the framework, the local state must be re-bootstrapped.  (this results in a long bootstrap time, which is essentially down time).  The same is true for Apache Kafka, a distributed pub-sub logging system.  When a Kafka broker must be restarted by the framework, it should ideally be re-started on the same host. (otherwise, each broker has to re-bootstrap several GBs of logs from its peers before it can start to service a request.)  I'm sure many stateful services have similar requirements.  My framework can update/ filter resource offers, but with many frameworks (thousands) on several nodes, I'm concerned about the wait-time for a particular available resource to be offered to a framework that needs it."
Answer: 2947.0

User story: "Create a document that describes the problems with having only single-role frameworks and proposes an MVP solution and implementation approach."
Answer: 1521675.0

User story: "Right now, we have setup one mesos cluster,  one Master Node, and several Slave Nodes,  We found that seems mesos not support slave nodes app reschudeling , for example a simple user case:  1. I have several containers running on one Slave Node.  2. The slave node down for some issue  How can use those containers ?  Could those containers rescheduled to other Slave Nodes ?    From our test, it seems Mesos Not support this feature. Which means, users can not use those containers anymore.  Could any Mesos developers confirmed that ?"
Answer: 8407.0

User story: "Currently, the HTTP Scheduler library does not support SSL-enabled Mesos.   (You can manually test this by spinning up an SSL-enabled master and attempt to run the event-call framework example against it.)  We need to add tests that check the HTTP Scheduler library against SSL-enabled Mesos: * with downgrade support, * with required framework/client-side certifications, * with/without verification of certificates (master-side), * with/without verification of certificates (framework-side), * with a custom certificate authority (CA)  These options should be controlled by the same environment variables found on the [SSL user doc|http://mesos.apache.org/documentation/latest/ssl/].  Note: This issue will be broken down into smaller sub-issues as bugs/problems are discovered."
Answer: 1636674.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: "As a developer working on the JVM I would like mesos to provide a JAR containing the new protobuf classes for the HTTP API.  Please create a new jar that contains the Protobuf message file and generated java and class files generated from the message file. This jar should be published to maven central."
Answer: 1666822.0

User story: "A common way to specify a Docker image with the docker engine is through {{repo:tag}}, which is convenient and sufficient for most people in most scenarios. However this combination is neither precise nor immutable.  For this reason, it's possible when an image with a {{repo:tag}} already cached locally on an agent host and a task requiring this {{repo:tag}} arrives, it's using an image that's different than the one the user intended.  Docker CLI already supports referring to an image by {{repo@id}}, where the ID can have two forms: * v1 Image ID * digest  Native Mesos provisioner should support the same for Docker images. IMO it's fine if image discovery by ID is not supported (and thus still requiring {{repo:tag}} to be specified) (looks like [v2 registry|http://docs.docker.com/registry/spec/api/] does support it) but the user can optionally specify an image ID and match it against the cached / newly pulled image. If the ID doesn't match the cached image, the store can re-pull it; if the ID doesn't match the newly pulled image (manifest), the provisioner can fail the request without having the user unknowingly running its task on the wrong image."
Answer: 1669787.0

User story: Tasks currently log their output (i.e. stdout/stderr) to files (the "sandbox") on an agent's disk.  In some cases, the accumulation of these logs can completely fill up the agent's disk and thereby kill the task or machine.  To prevent this, we should either implement a log rotation mechanism or capped-size logging.  This would be used by executors to control the amount of logs they keep.    Master/agent logs will not be affected.  We will first scope out several possible approaches for log rotation/capping in a design document (see [MESOS-3356]).  Once an approach is chosen, this story will be broken down into some corresponding issues.
Answer: 1702788.0

User story: "With the new JSON {{MasterInfo}} published to ZK, we want to provide a simple library class for Java Framework developers to retrieve info about the masters and the leader."
Answer: 1740566.0

User story: "With the new JSON {{MasterInfo}} published to ZK, we want to provide a simple library class for Python developers to retrieve info about the masters and the leader."
Answer: 1740566.0

User story: "Following from MESOS-2902 we want to enable the same functionality in the Mesos Agents too.  This is probably best done once we implement the new {{os::shell}} semantics, as described in MESOS-3142."
Answer: 1753556.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: When reviewing the code in [r/36425|https://reviews.apache.org/r/36425/] [~<USER> noticed that there is a better abstraction that is possible to introduce for {{os::shell()}} that will simplify the caller's life.  Instead of having to handle all possible outcomes, we propose to refactor {{os::shell()}} as follows:  {code} /**  * Returns the output from running the specified command with the shell.  */ Try<std::string> shell(const string& command) {   // Actually handle the WIFEXITED, WIFSIGNALED here! } {code}  where the returned string is {{stdout}} and, should the program be signaled, or exit with a non-zero exit code, we will simply return a {{Failure}} with an error message that will encapsulate both the returned/signaled state, and, possibly {{stderr}}.  And some test driven development: {code} EXPECT_ERROR(os::shell("false")); EXPECT_SOME(os::shell("true"));  EXPECT_SOME_EQ("hello world", os::shell("echo hello world")); {code}  Alternatively, the caller can ask to have {{stderr}} conflated with {{stdout}}: {code} Try<string> outAndErr = os::shell("myCmd --foo 2>&1"); {code}  However, {{stderr}} will be ignored by default: {code} // We don't read standard error by default. EXPECT_SOME_EQ("", os::shell("echo hello world 1>&2"));  // We don't even read stderr if something fails (to return in Try::error). Try<string> output = os::shell("echo hello world 1>&2 && false"); EXPECT_ERROR(output); EXPECT_FALSE(strings::contains(output.error(), "hello world")); {code}  An analysis of existing usage shows that in almost all cases, the caller only cares {{if not error}}; in fact, the actual exit code is read only once, and even then, in a test case.  We believe this will simplify the API to the caller, and will significantly reduce the length and complexity at the calling sites (<6 LOC against the current 20+).
Answer: 1758603.0

User story: "Following from MESOS-2340, which now allows Master to correctly decode JSON information ({{MasterInfo}}) published to Zookeeper, we can now enable the Master Leader Contender to serialize it too in JSON."
Answer: 1760007.0

User story: "In the process of adding the Cmake build system, [~<USER> noted and stubbed out all OS-specific code. That sweep (mostly of libprocess and stout) is here: https://github.com/<USER>mesos/commit/b862f66c6ff58c115a009513621e5128cb734d52  Instead of having inline {{#if defined(...)}}, the OS-specific code will be separated into directories. The Windows code will be stubbed out."
Answer: 1763394.0

User story: "This is a simple test story to try out the new workflow.  Unfortunately, testing and getting it to work seems to be something that actually does take up time, so I'm tracking this here."
Answer: 1799671.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 is the first basic step in ensuring the basic {{/call}} functionality: processing a  {noformat} POST /call {noformat} and returning:  - {{202}} if all goes well; - {{401}} if not authorized; and - {{403}} if the request is malformed.  We'll get more sophisticated as the work progressed (eg, supporting {{415}} if the content-type is not of the right kind)."
Answer: 1819663.0

User story: "The information exposed by the Framework via the {{WebUIUrl}} does not always resolves to a routable endpoint (eg, when the {{hostname}} is not publicly resolvable, or resolvable at all).  In order to facilitate service discovery (via, eg, Marathon UI) we want to add the information in {{FrameworksPid}} via the {{/state-summary}} endpoint."
Answer: 142.0

User story: This is a component of the slave that informs the slave about the possible "corrections" that need to be performed (e.g., shutdown container using recoverable resources).  This needs to be integrated with the resource monitor.  Need to figure out the metrics used for sending corrections (e.g., scheduling latency, usage, informed by executor/scheduler)  We also need to figure out the feedback loop between the QoS controller and the Resource Estimator.  {code} class QoSController { public:   QoSController(ResourceMonitor* monitor);    process::Queue<QoSCorrection> correction(); }; {code}  
Answer: 1891560.0

User story: "Example: I'm developing a framework that makes use of persistent volumes, MESOS-1554. At startup I want my scheduler to verify the Mesos master's version and abort if it's less than e.g. {{0.23.0}}, which I know is the minimum version for that feature.  I've looked at MESOS-753 and MESOS-986 and they don't seem to address  this cleanly.  Version may be available in {{state.json}}, but this is an unboundedly large value to parse. It would seem sensible to have an HTTP endpoint {{/version}} or similar."
Answer: 1891642.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 k8s pods abstraction is not the only way to run multiple containers on a single host. In my use of Mesos, I have two use cases for running multiple containers together:  1. I run a job that needs a "babysitter" process to run with it, such that it can inspect the filesystem being written to by the primary job. The babysitter verifies that the job is operating correctly, and takes automated recovery/termination actions on failure.  2. I run a webserver that writes logs. I also run logstash in the same container, in order to ship the logs to our main log storage system.  In both of these cases, I need to run common initialization code, and then I start the various sub-tasks that need to be isolated. Rather than need my framework's scheduler to be able to make decisions at launch time about how it wants to carve up the process, I'd like my executor to be able to locally create subgroups for CPU and Memory containerization, so that it can decide on-the-fly whether to carve its container into smaller pieces.  I think that by triggering the splitting of containers in the executor, this will enable more dynamic usage.  The downside to this is that the container splitting would have to be rebuilt for every containerizer; the upside is the flexibility in creating temporary subcontainers only when they're needed.  I think that this would only require for command-line utilities that understood the Mesos environment (that the executor could shell out to), or perhaps it would be done with an executor API call to the slave, to ensure the subcontainers didn't break cleanup.  I've heard rumors that Aurora can do something like this; perhaps their implementation could graduate to Mesos proper?
Answer: 696683.0

User story: "Currently, the C++ library sends different messages to Master instead of a single Call message. To vet the new Call API it should send Call messages. Master should be updated to handle all types of Calls."
Answer: 158144.0

User story: "Mesos provides the ability to enable authentication however credentials and authentication is for either master/slave or master/framework.   We need to add the ability have credential support for users at the web ui level (default port: 5050). "
Answer: 810021.0

User story: "Right now, the port mapping network isolator used by mesos containerizer is based on the assumption that there is not enough public IPs (a unique IP per container). That introduces a lot of the complexities and limits the number ports that can be used by a container.  If we have enough public IPs, we can use macvlan to bridge containers. That's much more cleaner and efficient."
Answer: 31709.0

User story: "Right now it appears maven is using http://repo.maven.apache.org"
Answer: 136753.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 master exports a monotonically-increasing counter of tasks transitioned to TASK_LOST.  This loses fidelity of the source of the lost task.  A first step in exposing the source of lost tasks might be to just differentiate between TASK_LOST transitions initiated by the master vs the slave (and maybe bad input from the scheduler)."
Answer: 199006.0

User story: "We want to be able to specify a default image setting for all the mesos containerizers (external, mesos, docker, etc)."
Answer: 187984.0

User story: There is some known kernel issue when we freeze the whole cgroup upon OOM. Mesos probably can just use PID namespace so that we will only need to kill the "init" of the pid namespace, instead of freezing all the processes and killing them one by one. But I am not quite sure if this would break the existing code.
Answer: 76469.0

User story: We tell developers to follow the Google C++ Style Guide (http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml) which says, "Do not use a using-directive."  At the moment 134 files in src/ do not conform to this practice. $ grep -r -l "using namespace" src | wc -l 134  Using directives increase compile time by requiring a larger lookup space for unqualified ids.
Answer: 27002.0

User story: "Looking through [the review introducing the /shutdown http endpoint|https://reviews.apache.org/r/22832], it appears that any framework's credentials can be used to shutdown any other framework:  Around line 650: {code}   foreach (const Credential& credential, master->credentials.get().http()) {     if (credential.principal() == username &&         (!credential.has_secret() || credential.secret() == password)) {       // TODO(<USER> make removeFramework asynchronously       master->removeFramework(framework);       return OK();     }   } {code}  Thanks to [~<USER>, I looked into in [authorization doc|https://github.com/apache/mesos/blob/master/docs/authorization.md], however I don't see where the ACL-checking is happening within that code."
Answer: 17.0

User story: "For C++ framework developers that want to use libprocess in their code base, it would be great if Mesos provides a way to easily get access to the headers. A first step in that direction would be to provide a install target in the libprocess Makefile for the same."
Answer: 5297.0

User story: "The Java API documentation on the website (http://mesos.apache.org/api/latest/java/) should include protobuf documentation. protoc automatically generates javadoc based on comments in the .proto so this should be a matter of wiring."
Answer: 563217.0

User story: While a "cpu-seconds per second" metric can be computed with 2 samples of cpu_*_secs at different times, it's often convenient to have a single self-contained value, for example if sample collection interval is long, or so that an operator can glance at the cpu usage of a task with a single curl command.  Add user_cpus, system_cpus, and total_cpus metrics to the available container stats.
Answer: 440336.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: "* Parsing the output  (3) * Running the binary with error checking  (2) * Test perf with different distributions etc  (3) * Test slave roll forward/roll back  (2) * Create new protobuf for perf stats  (2) * Rename resource metrics and expose through existing endpoint  (8) * Documentation (e.g. for command line flags)   (1) "
Answer: 53595.0

User story: "In this iteration: - Rate limits are configured via Master flag {{--ratelimits=config.JSON}} - The configuration is not persisted. - No online tuning for the configuration, reconfiguration is through Master restart with new flags.  * Create a protobuf for configuration and read through master flags  (2) * Integrate rate limiter into the master  (5) * Add new tests for rate limiter  (3) * Convert all existing tests to use rate limiter  (20)"
Answer: 60336.0

User story: "See summary."
Answer: 2724426.0

User story: "Blog about the release of the catch-up replicated log:  https://issues.apache.org/jira/browse/MESOS-736 "
Answer: 969615.0

User story: "Couple references to when the project was in the incubator are still in the codebase, removing and updating pom to point to correct mailing list"
Answer: 20259.0

User story: "MESOS-704 added basic authentication support using CRAM-MD5 through SASL. Now we should integrate Kerberos authentication using GSS-API, which is already supported by SASL. Kerberos is a widely-used industry standard authentication service, and integration with Mesos will make it easier for customers to integrate their existing security process with Mesos."
Answer: 2451669.0

User story: "TBD [~<USER>"
Answer: 248768.0

User story: "This ticket is an effort to capture requirements and link to related tickets for the future version of the Scheduler API. We should split these out as needed but for now I'll just document things off the top of my head:  1. Batch status update acknowledgements. The current mechanism for acknowledging a status update is for the call to Scheduler::statusUpdate to return. At this point we send an acknowledgement to the slave. This simplistic approach forces schedulers to serially persist status updates if operating in a stateful manner, ultimately leading to scaling issues.  2. Explicit behavior. By this I mean that when a Scheduler calls something like killTask, we'll currently implicitly drop it when we're disconnected from the Master. Rather than implicitly doing this, we either need to deliver things reliably or inform schedulers when their request was dropped. Returning Futures could be very powerful here.  3. Statefulness and access to state. The scheduler driver is currently stateless (no persistence). This means schedulers currently have to persist state using our State abstraction or the replicated log, or through their own persistence mechanism. Providing a stateful scheduler driver increases the simplicity of framework schedulers substantially, and providing access to state makes it very simple to implement a framework."
Answer: 734172.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: "Determining the health of a task during its lifetime (during start up, while it is running, shutting down etc.) can be considered a more elaborate matter than only observing its process state.  The task health might be determined by any combination of observable behavior; for example the process being listening to a certain range of ports, writing certain files or pipes, responding to messages, utilizing resources to or below certain thresholds etc.  It could be a powerful extension to extend the interface for launching and running tasks by an optional HealthCommand message. This message could encode:  1) A command to be run at the slave to determine the health of the task. The return value of the command will tell if the task is healthy or unhealthy.   2) An interval which to run the health command.  In connection with this, it could make sense to introduce new healthy and unhealthy task states."
Answer: 386049.0

User story: "When a replica joins Paxos with an empty log, we don't allow this replica to fully participate in Paxos immediately. Instead, this replica is treated as a non-voting member, meaning that it will not reply to any requests from other replicas. It simply learns those log entries that have been agreed on and tries to catch up the leader. When the catch-up process is done, we re-admit this replica to Paxos and allow it to vote.  If we have a disk failure and want to swap a master machine, we can simply start the scheduler on a new machine with an empty log (and that's it)."
Answer: 135737.0

User story: "To avoid style glitches, it would be handy to have a style checker to catch the most common (and hard to find) errors such as whitespaces, tabs, line widths and so forth. While it is not likely to find a fully compatible style checker, Google's cpplint can be configured to match a small subset of rules.  An example of such a script can be found here: https://gist.github.com/nqn/6814621  This is just an example, which find about 170 whitespace and readability errors in the current master branch. Can be configured to the extent needed."
Answer: 16093.0

User story: "Given I am a public user When I enter a valid userid And I enter a valid password And I click on the login button Then I am successfully directed to the HomePage"
Answer: 328744.0

User story: "This adds support to both scheduler and masters."
Answer: 21733.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: "It would be very valuable for the slave resource monitor to export hardware counters.  There are a few ways this could be done -- either by invoking perf directly or by accessing the counters via the syscall/read interface described by http://lxr.free-electrons.com/source/tools/perf/design.txt  I'd imagine this would just get plumbed through Isolator::usage in the end and get exported via the resource monitor endpoint.  Correct me if I'm wrong but there's currently no information exposed (programmatically) at the granularity level of executor, so I don't really know how this information could ever make its way into the hands of a scheduler for the purpose of making better scheduling decisions vis-a-vis things like task-level interference.  Given Google's CPI paper (http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/pubs/archive/40737.pdf) it sounds like something worth investigating."
Answer: 824545.0

User story: "Rework the abstraction to make it easier to support isolating other resources and multiple isolation mechanisms."
Answer: 284099.0

User story: "On my wish list, I'd love if there was an bot that would send out JIRA activity into the #mesos IRC channel. I thought about creating an INFRA ticket for this, but a) wasn't sure what others thought, and b) I don't know if this is something INFRA supports for other projects or if they would consider it.  What do you think? Anyone have experience creating these bots?"
Answer: 107704.0

User story: Given that multiple frameworks can be present on a machine at a time, and writing "node drain" for each possible framework is an intractable task, it would nice if the slave-master core had a means to tell frameworks that tasks were killed to drain a host.  Or possibly that the slave was told to drain the host of all tasks (graceful shutdown, etc).  {noformat} # drain current host pkill -USR1 mesos-slave {noformat}  This would make writing scripts for site-ops to do node maintenance much easier... :)
Answer: 483963.0

User story: "I'm writing a ruby gem that links with mesos in order to write frameworks in ruby.  I'm using native extensions obviously, however, I can't compile anything out of tree because 'mesos/mesos.hpp' includes 'mesos.pb.h' which doesn't seem to be included after make install, and it's in nodist_pkginclude_HEADERS in the Makefile.  Is it possible to link against Mesos without doing it during the build process?  I would assume I can just #include <mesos/scheduler.hpp> and implement a scheduler that way."
Answer: 2144.0

User story: "This allows one to run their Jenkins slaves on the Mesos cluster, completely dynamically and on demand! The scheduler spins up Jenkins slaves as Mesos tasks based on the pending jobs in the Jenkins master. "
Answer: 17838.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 MasterDetector code still uses old Zookeeper abstractions and it's error-prone for maintenance and further development.   There exists newer and higher-level zookeeper group management abstractions such as zookeeper::Group. After this refactoring Mesos master detecting and contending logic should reside in separate classes which depend on general Zookeeper group leader detection and contention abstractions with Future-pattern APIs. Masters should then use the MasterContender while Slaves and Schedulers should use the MasterDetector.  The following is a summary of the change ===  Two layers of ZK abstractions are added: - zookeeper::LeaderContender is responsible for contending to be a leader. It does not detect whether it is elected but only registers itself in ZK and watch the membership change.   zookeeper::LeaderDetector is responsible for detecting the current leader. The contender and detector run independent of each other. - mesos::internal::MasterContender and mesos::internal::MasterDetector wrap around the zookeeper contender and detector abstractions as adapters to provide/interpret the ZooKeeper data (as Master PIDs, later as MasterInfo after MESOS-672 change). - MasterContender is used only by the master and MasterDetector is used by master, slave and scheduler driver. With the new abstractions the master election logic starts after the client components (master/slave/sched) are fully initialized (e.g. after slave recovery for slaves) instead of before they start. "
Answer: 240528.0

User story: "hi,  I would like to know how i set  --frameworks_home properly when I launch my slave, i also want to know how to set the ExecutorInfo to be a relative path, that will be appended to the slaves --frameworks_home path, i want to do this for deploying Mesos on two laptops, one is the master and the other is the slave, i mounted  NFS and put the exector in it, and in my scheduler i set the uri of the executor to be the absolute path in the slave, but that did not work, can anyone explain to me how to do it using NFS and how to set the --frameworks_home and the executor's uri properly ?  Thank you"
Answer: 16872.0

User story: "I would like to know how to proceed from scatch if one wants to develop his own framework, what is written in the documentation left me with a lot of unanswered questions, like what is the role of the executor file, how is it invoked in the case of test-framework and test-executor (c++ framework), and how could i make it run  tasks."
Answer: 40617.0