feat: Sentient Anomaly rotation #759

Sainan · 2025-01-09T10:36:38-08:00

AMelonInsideLemon commented

2025-01-09 10:36:38 -08:00

(Migrated from github.com)

No description provided.

coderabbitai[bot] commented

2025-01-09 10:36:47 -08:00

(Migrated from github.com)

Warning

Rate limit exceeded

@Sainan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 17 minutes and 50 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e343bcdcba and 2bf6b8dacc.

📒 Files selected for processing (1)

src/controllers/dynamic/worldStateController.ts (3 hunks)

Walkthrough

The pull request introduces enhancements to the world state management system by adding a new dynamic feature related to a "Sentient Anomaly" that cycles every 30 minutes. The changes primarily involve modifying the worldStateController in the TypeScript source code and updating a corresponding JSON configuration file.

In the worldStateController, a new mechanism is implemented to generate a temporary object (tmp) based on the current time. This object is then serialized and added to the world state as a new Tmp property. The IWorldState interface is updated to accommodate this new optional string property.

The accompanying JSON file in the static responses has been updated to include a new "Tmp" key, which contains a JSON-encoded string with additional metadata about custom decals and time-related information. These modifications appear to introduce a cyclical, time-based dynamic element to the world state management system.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Generate unit testing code for this file.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai generate unit testing code for this file.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and generate unit testing code.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

> [!WARNING] > ## Rate limit exceeded > > @Sainan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait **17 minutes and 50 seconds** before requesting another review. > > <details> > <summary>⌛ How to resolve this issue?</summary> > > After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. > > We recommend that you space out your commits to avoid hitting the rate limit. > > </details> > > > <details> > <summary>🚦 How do rate limits work?</summary> > > CodeRabbit enforces hourly rate limits for each developer per organization. > > Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. > > Please see our [FAQ](https://docs.coderabbit.ai/faq) for further information. > > </details> > > <details> > <summary>📥 Commits</summary> > > Reviewing files that changed from the base of the PR and between e343bcdcbad74478d097b6979427fd7e506cfc0c and 2bf6b8dacc1cff2acf0c98de3fee911fab499ea3. > > </details> > > <details> > <summary>📒 Files selected for processing (1)</summary> > > * `src/controllers/dynamic/worldStateController.ts` (3 hunks) > > </details>   ## Walkthrough The pull request introduces enhancements to the world state management system by adding a new dynamic feature related to a "Sentient Anomaly" that cycles every 30 minutes. The changes primarily involve modifying the `worldStateController` in the TypeScript source code and updating a corresponding JSON configuration file. In the `worldStateController`, a new mechanism is implemented to generate a temporary object (`tmp`) based on the current time. This object is then serialized and added to the world state as a new `Tmp` property. The `IWorldState` interface is updated to accommodate this new optional string property. The accompanying JSON file in the static responses has been updated to include a new "Tmp" key, which contains a JSON-encoded string with additional metadata about custom decals and time-related information. These modifications appear to introduce a cyclical, time-based dynamic element to the world state management system.      --- Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? <details> <summary>❤️ Share</summary> - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code) </details> <details> <summary>🪧 Tips</summary> ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit <commit_id>, please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai generate docstrings` to [generate docstrings](https://docs.coderabbit.ai/finishing-touches/docstrings) for this PR. ([Beta](https://docs.coderabbit.ai/early-access#beta)) - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements. </details>

coderabbitai[bot] (Migrated from github.com) reviewed 2025-01-09 10:49:27 -08:00

coderabbitai[bot] (Migrated from github.com) left a comment

Actionable comments posted: 1

🧹 Nitpick comments (2)

src/controllers/dynamic/worldStateController.ts (2)
94-94: Document the significance of sfn values.

The array [550, 553, 554, 555] contains magic numbers without explanation of their purpose.

Add a comment explaining what these numbers represent:
-        sfn: [550, 553, 554, 555][halfHour % 4]
+        // Sentient Faction Numbers representing different anomaly states
+        sfn: [550, 553, 554, 555][halfHour % 4]
108-108: Improve type safety for the Tmp property.

Instead of using a string type that requires parsing, consider using a strongly typed approach.
-    Tmp?: string;
+    Tmp?: ITemporaryState;
Then update the assignment:
-    worldState.Tmp = JSON.stringify(tmp);
+    worldState.Tmp = tmp;
This would provide better type safety and eliminate the need for JSON serialization/deserialization.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1c654650d4 and 2306a6a0a73cbbef5d601c6b74089babd25dd25c.

📒 Files selected for processing (2)

src/controllers/dynamic/worldStateController.ts (3 hunks)
static/fixed_responses/worldState.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

static/fixed_responses/worldState.json

🔇 Additional comments (3)

src/controllers/dynamic/worldStateController.ts (3)

5-5: LGTM!

The import of time constants is well-organized and follows good practices.

86-98: Verify consistency with other rotation implementations.

Let's check if similar rotation logic exists elsewhere in the codebase to ensure consistency.

✅ Verification successful

Implementation is consistent with existing rotation patterns

The half-hour rotation logic follows the same patterns used in other time-based rotations within the codebase, including:

Elite Sanctuary Onslaught (weekly)

Bounty cycles

Daily reset mechanics
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:
#!/bin/bash
# Search for similar rotation implementations
rg -A 5 "Math\.trunc.*getTime" --type ts

# Look for other uses of unixTimesInMs
rg "unixTimesInMs" --type ts

# Search for other temporary state management
ast-grep --pattern 'interface $interface {
  $$$
  Tmp?: $type;
  $$$
}'
Length of output: 3692
86-87: Add validation for time-based calculations.

The halfHour calculation could potentially cause issues with invalid dates or time manipulation.

Consider adding validation:
-    const halfHour = Math.trunc(new Date().getTime() / (unixTimesInMs.hour / 2));
+    const currentTime = new Date().getTime();
+    if (isNaN(currentTime)) {
+        throw new Error('Invalid date');
+    }
+    const halfHour = Math.trunc(currentTime / (unixTimesInMs.hour / 2));

**Actionable comments posted: 1** <details> <summary>🧹 Nitpick comments (2)</summary><blockquote> <details> <summary>src/controllers/dynamic/worldStateController.ts (2)</summary><blockquote> `94-94`: **Document the significance of sfn values.** The array `[550, 553, 554, 555]` contains magic numbers without explanation of their purpose. Add a comment explaining what these numbers represent: ```diff - sfn: [550, 553, 554, 555][halfHour % 4] + // Sentient Faction Numbers representing different anomaly states + sfn: [550, 553, 554, 555][halfHour % 4] ``` --- `108-108`: **Improve type safety for the Tmp property.** Instead of using a string type that requires parsing, consider using a strongly typed approach. ```diff - Tmp?: string; + Tmp?: ITemporaryState; ``` Then update the assignment: ```diff - worldState.Tmp = JSON.stringify(tmp); + worldState.Tmp = tmp; ``` This would provide better type safety and eliminate the need for JSON serialization/deserialization. </blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: .coderabbit.yaml** **Review profile: CHILL** **Plan: Pro** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 1c654650d4559c4a8c0e2ede5f22f0db2cecb2f6 and 2306a6a0a73cbbef5d601c6b74089babd25dd25c. </details> <details> <summary>📒 Files selected for processing (2)</summary> * `src/controllers/dynamic/worldStateController.ts` (3 hunks) * `static/fixed_responses/worldState.json` (1 hunks) </details> <details> <summary>✅ Files skipped from review due to trivial changes (1)</summary> * static/fixed_responses/worldState.json </details> <details> <summary>🔇 Additional comments (3)</summary><blockquote> <details> <summary>src/controllers/dynamic/worldStateController.ts (3)</summary> `5-5`: **LGTM!** The import of time constants is well-organized and follows good practices. --- `86-98`: **Verify consistency with other rotation implementations.** Let's check if similar rotation logic exists elsewhere in the codebase to ensure consistency. <details> <summary>✅ Verification successful</summary>  **Implementation is consistent with existing rotation patterns** The half-hour rotation logic follows the same patterns used in other time-based rotations within the codebase, including: - Elite Sanctuary Onslaught (weekly) - Bounty cycles - Daily reset mechanics </details> <details> <summary>🏁 Scripts executed</summary> The following scripts were executed for the analysis: Script: ```shell #!/bin/bash # Search for similar rotation implementations rg -A 5 "Math\.trunc.*getTime" --type ts # Look for other uses of unixTimesInMs rg "unixTimesInMs" --type ts # Search for other temporary state management ast-grep --pattern 'interface $interface { $$$ Tmp?: $type; $$$ }' ``` Length of output: 3692 </details> --- `86-87`: **Add validation for time-based calculations.** The halfHour calculation could potentially cause issues with invalid dates or time manipulation. Consider adding validation: ```diff - const halfHour = Math.trunc(new Date().getTime() / (unixTimesInMs.hour / 2)); + const currentTime = new Date().getTime(); + if (isNaN(currentTime)) { + throw new Error('Invalid date'); + } + const halfHour = Math.trunc(currentTime / (unixTimesInMs.hour / 2)); ``` </details> </blockquote></details> </details>

src/controllers/dynamic/worldStateController.ts

coderabbitai[bot] (Migrated from github.com) commented

2025-01-09 10:49:26 -08:00

🛠️ Refactor suggestion

Define types and improve naming clarity.

The temporary state object has several issues:

Cryptic boolean property names (tcsn, ennnd, mbrt) lack clarity
Magic numbers in sfn array need documentation
Hardcoded timestamp needs explanation

Consider creating an interface and using more descriptive names:

interface ITemporaryState {
  caveatBeginTimestamp: string;
  purchasePlatformLockEnabled: boolean;
  // TODO: Replace with descriptive names
  tcsn: boolean;
  ennnd: boolean;
  mbrt: boolean;
  sentientFactionNumber: number;
}

_:hammer_and_wrench: Refactor suggestion_ **Define types and improve naming clarity.** The temporary state object has several issues: 1. Cryptic boolean property names (`tcsn`, `ennnd`, `mbrt`) lack clarity 2. Magic numbers in `sfn` array need documentation 3. Hardcoded timestamp needs explanation Consider creating an interface and using more descriptive names: ```typescript interface ITemporaryState { caveatBeginTimestamp: string; purchasePlatformLockEnabled: boolean; // TODO: Replace with descriptive names tcsn: boolean; ennnd: boolean; mbrt: boolean; sentientFactionNumber: number; } ```

Sainan commented

2025-01-09 17:10:40 -08:00

I think mbrt can be removed, but no pager text? :megamind:

AMelonInsideLemon commented

2025-01-09 17:21:47 -08:00

(Migrated from github.com)

I decided not to touch the values I don't know anything about so that nothing would break. I think that leaving a static phrase on the pager is not a good solution.

Sainan commented

2025-01-09 17:23:07 -08:00

Make it say "CUSTOM DECALS @ OPENWF" :trollface:

coderabbitai[bot] (Migrated from github.com) reviewed 2025-01-11 03:59:26 -08:00

coderabbitai[bot] (Migrated from github.com) left a comment

Actionable comments posted: 0

♻️ Duplicate comments (1)

src/controllers/dynamic/worldStateController.ts (1)

101-111: 🛠️ Refactor suggestion

Improve code clarity and maintainability.

The Sentient Anomaly rotation implementation has several issues:

Cryptic boolean property names lack clarity
Magic numbers in the sfn array need documentation
Hardcoded timestamp in cavabegin

Consider this refactor:

 // Sentient Anomaly cycling every 30 minutes
 const halfHour = Math.trunc(new Date().getTime() / (unixTimesInMs.hour / 2));
 const tmp = {
-    cavabegin: "1690761600",
-    PurchasePlatformLockEnabled: true,
-    tcsn: true,
-    ennnd: true,
-    mbrt: true,
-    sfn: [550, 553, 554, 555][halfHour % 4]
+    caveatBeginTimestamp: "1690761600", // Document the significance of this timestamp
+    purchasePlatformLockEnabled: true,
+    // TODO: Replace with descriptive names
+    targetCaptureSystemEnabled: true,  // tcsn
+    enhancedNavigationEnabled: true,   // ennnd
+    // Remove mbrt as suggested in PR comments
+    // Sentient Faction Numbers - Document what each number represents
+    sentientFactionNumber: [
+        550, // Faction A
+        553, // Faction B
+        554, // Faction C
+        555  // Faction D
+    ][halfHour % 4]
 };

🧹 Nitpick comments (1)

src/controllers/dynamic/worldStateController.ts (1)
123-123: Improve interface type safety.

The Tmp property could be improved:

Use a more descriptive name

Define a proper interface instead of using string type
interface ISentientAnomalyState {
  caveatBeginTimestamp: string;
  purchasePlatformLockEnabled: boolean;
  targetCaptureSystemEnabled: boolean;
  enhancedNavigationEnabled: boolean;
  sentientFactionNumber: number;
}

interface IWorldState {
  // ... other properties
  sentientAnomalyState?: ISentientAnomalyState;
}

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2306a6a0a73cbbef5d601c6b74089babd25dd25c and e343bcdcba.

📒 Files selected for processing (2)

src/controllers/dynamic/worldStateController.ts (3 hunks)
static/fixed_responses/worldState/worldState.json (1 hunks)

🔇 Additional comments (2)

src/controllers/dynamic/worldStateController.ts (1)

9-9: LGTM! Good use of time constants.

Using unixTimesInMs constant instead of magic numbers for time calculations improves code maintainability.

static/fixed_responses/worldState/worldState.json (1)

Line range hint 1-1264: Unable to review changes without clear annotations.

The changes to this JSON file are not clearly marked. Please provide a diff or annotated version showing the specific changes made to this configuration file.

**Actionable comments posted: 0** <details> <summary>♻️ Duplicate comments (1)</summary><blockquote> <details> <summary>src/controllers/dynamic/worldStateController.ts (1)</summary><blockquote> `101-111`: _:hammer_and_wrench: Refactor suggestion_ **Improve code clarity and maintainability.** The Sentient Anomaly rotation implementation has several issues: 1. Cryptic boolean property names lack clarity 2. Magic numbers in the `sfn` array need documentation 3. Hardcoded timestamp in `cavabegin` Consider this refactor: ```diff // Sentient Anomaly cycling every 30 minutes const halfHour = Math.trunc(new Date().getTime() / (unixTimesInMs.hour / 2)); const tmp = { - cavabegin: "1690761600", - PurchasePlatformLockEnabled: true, - tcsn: true, - ennnd: true, - mbrt: true, - sfn: [550, 553, 554, 555][halfHour % 4] + caveatBeginTimestamp: "1690761600", // Document the significance of this timestamp + purchasePlatformLockEnabled: true, + // TODO: Replace with descriptive names + targetCaptureSystemEnabled: true, // tcsn + enhancedNavigationEnabled: true, // ennnd + // Remove mbrt as suggested in PR comments + // Sentient Faction Numbers - Document what each number represents + sentientFactionNumber: [ + 550, // Faction A + 553, // Faction B + 554, // Faction C + 555 // Faction D + ][halfHour % 4] }; ``` </blockquote></details> </blockquote></details> <details> <summary>🧹 Nitpick comments (1)</summary><blockquote> <details> <summary>src/controllers/dynamic/worldStateController.ts (1)</summary><blockquote> `123-123`: **Improve interface type safety.** The `Tmp` property could be improved: 1. Use a more descriptive name 2. Define a proper interface instead of using string type ```typescript interface ISentientAnomalyState { caveatBeginTimestamp: string; purchasePlatformLockEnabled: boolean; targetCaptureSystemEnabled: boolean; enhancedNavigationEnabled: boolean; sentientFactionNumber: number; } interface IWorldState { // ... other properties sentientAnomalyState?: ISentientAnomalyState; } ``` </blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: .coderabbit.yaml** **Review profile: CHILL** **Plan: Pro** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between 2306a6a0a73cbbef5d601c6b74089babd25dd25c and e343bcdcbad74478d097b6979427fd7e506cfc0c. </details> <details> <summary>📒 Files selected for processing (2)</summary> * `src/controllers/dynamic/worldStateController.ts` (3 hunks) * `static/fixed_responses/worldState/worldState.json` (1 hunks) </details> <details> <summary>🔇 Additional comments (2)</summary><blockquote> <details> <summary>src/controllers/dynamic/worldStateController.ts (1)</summary> `9-9`: **LGTM! Good use of time constants.** Using `unixTimesInMs` constant instead of magic numbers for time calculations improves code maintainability. </details> <details> <summary>static/fixed_responses/worldState/worldState.json (1)</summary> Line range hint `1-1264`: **Unable to review changes without clear annotations.** The changes to this JSON file are not clearly marked. Please provide a diff or annotated version showing the specific changes made to this configuration file. </details> </blockquote></details> </details>

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: OpenWF/SpaceNinjaServer#759