Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix/server api not started #8645

Merged
merged 3 commits into from
Dec 29, 2024
Merged

Fix/server api not started #8645

merged 3 commits into from
Dec 29, 2024

Conversation

syns2191
Copy link
Collaborator

@syns2191 syns2191 commented Dec 29, 2024

PR

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.


Summary by CodeRabbit

  • Dependencies

    • Added multiple Gauzy ecosystem packages to desktop and server applications
    • Included plugins for integrations with GitHub, Hubstaff, Jira, Upwork, and other services
    • Added core configuration, authentication, and plugin packages
  • Configuration

    • Updated dependency management and package references
    • Modified logging and migration file resolution for Electron environment

Copy link
Contributor

coderabbitai bot commented Dec 29, 2024

Walkthrough

This pull request introduces a comprehensive update to the dependency management for the Gauzy desktop and server applications. The changes involve adding multiple local package dependencies from the Gauzy ecosystem, including configuration, authentication, core functionalities, and various plugins for integrations with services like GitHub, Hubstaff, Jira, and others. Additionally, modifications were made to the bootstrap process in the core package, adjusting logging and migration file handling based on the Electron environment.

Changes

File Change Summary
apps/desktop/src/package.json Added multiple local Gauzy dependencies including config, auth, core, and various integration plugins (GitHub, Hubstaff, Jira, etc.)
apps/server/src/package.json Reordered and updated dependencies for Gauzy auth, core, desktop libraries, and changelog plugin
packages/core/src/lib/bootstrap/index.ts Modified logging buffer settings and migration file inclusion logic to be environment-specific (Electron vs. non-Electron)

Sequence Diagram

sequenceDiagram
    participant App as Gauzy Application
    participant Config as @gauzy/config
    participant Auth as @gauzy/auth
    participant Core as @gauzy/core
    participant Plugins as Gauzy Plugins

    App->>Config: Load configuration
    App->>Auth: Initialize authentication
    App->>Core: Bootstrap core functionality
    App->>Plugins: Load integration plugins
    Plugins->>App: Register integrations (GitHub, Hubstaff, Jira)
Loading

Possibly related PRs

Poem

🐰 Hop, hop, dependencies dance!
Local packages in a rabbit's glance
Plugins spinning, integrations bright
Gauzy's ecosystem takes its flight
Code leaps forward with each new line 🚀

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.


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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

@syns2191 syns2191 linked an issue Dec 29, 2024 that may be closed by this pull request
5 tasks
@syns2191 syns2191 added the FIX label Dec 29, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/core/src/lib/bootstrap/index.ts (1)

75-75: Consider simplifying the ternary expression.

Currently, you use:

bufferLogs: env.isElectron ? false : true

You can replace it with:

bufferLogs: !env.isElectron

This is shorter, clearer, and avoids an unnecessary ternary.

- bufferLogs: env.isElectron ? false : true
+ bufferLogs: !env.isElectron
🧰 Tools
🪛 Biome (1.9.4)

[error] 75-75: Unnecessary use of boolean literals in conditional expression.

Simplify your code by directly assigning the result without using a ternary operator.
If your goal is negation, you may use the logical NOT (!) or double NOT (!!) operator for clearer and concise code.
Check for more details about NOT operator.
Unsafe fix: Remove the conditional expression with

(lint/complexity/noUselessTernary)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 602479e and 94b9c26.

📒 Files selected for processing (3)
  • apps/desktop/src/package.json (2 hunks)
  • apps/server/src/package.json (2 hunks)
  • packages/core/src/lib/bootstrap/index.ts (2 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
packages/core/src/lib/bootstrap/index.ts

[error] 75-75: Unnecessary use of boolean literals in conditional expression.

Simplify your code by directly assigning the result without using a ternary operator.
If your goal is negation, you may use the logical NOT (!) or double NOT (!!) operator for clearer and concise code.
Check for more details about NOT operator.
Unsafe fix: Remove the conditional expression with

(lint/complexity/noUselessTernary)

🔇 Additional comments (3)
packages/core/src/lib/bootstrap/index.ts (1)

504-505: Logic check for Electron migrations handling looks good.

The conditional approach to only include .js files when running in Electron while including both .ts and .js otherwise is a clean solution to separate compiled and source migration files.

apps/desktop/src/package.json (1)

127-143: New Gauzy ecosystem plugins successfully added.

The file-based references to these local packages look correct. Ensure that the project's build or bundling process supports local file dependencies, which sometimes require additional steps to function properly in the Electron environment.

apps/server/src/package.json (1)

Line range hint 137-153: Dependency reorganization is consistent with the newly introduced packages.

The changes re-add important Gauzy packages, aligning them with the desktop application's approach. Confirm that there are no version mismatches or conflicting references in the build pipeline after this restructuring.

Copy link

nx-cloud bot commented Dec 29, 2024

View your CI Pipeline Execution ↗ for commit 94b9c26.

Command Status Duration Result
nx build desktop --base-href ./ ✅ Succeeded 1m 43s View ↗
nx build desktop-api --output-path=dist/apps/de... ✅ Succeeded 28s View ↗
nx run api:desktop-api ✅ Succeeded 1m 12s View ↗
nx build gauzy -c=production --prod --verbose ✅ Succeeded 3m 54s View ↗
nx run gauzy:desktop-ui --base-href ./ ✅ Succeeded 3m 22s View ↗
nx build api -c=production --prod ✅ Succeeded 1m 10s View ↗
nx build desktop-ui-lib --configuration=develop... ✅ Succeeded 31s View ↗
nx build desktop-ui-lib --configuration=production ✅ Succeeded 28s View ↗
Additional runs (52) ✅ Succeeded ... View ↗

☁️ Nx Cloud last updated this comment at 2024-12-29 14:32:38 UTC

@evereq evereq merged commit 1a841e6 into develop Dec 29, 2024
16 of 17 checks passed
@evereq evereq deleted the fix/server-api-not-started branch December 29, 2024 18:54
evereq added a commit that referenced this pull request Dec 29, 2024
Fix/server api not started (#8645)
evereq added a commit that referenced this pull request Dec 29, 2024
Fix/server api not started (#8645)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Fix] Desktop Timer and Gauzy Server
2 participants