devops: wait before lhci, fix vercel build

[gaboesquivel]

Summary by CodeRabbit

• New Features
  • Enhanced token retrieval process with improved error handling and verification.
• Refactor
  • Updated the JWT token access method to ensure smoother operation.
  • Modified the thread fetching limit to improve performance.
• Chores
  • Adjusted the workflow to wait for 2 minutes before capturing the Vercel preview URL.
• Style
  • Temporarily removed the ChatLayoutSection component from the chat layout for a streamlined structure.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
masterbots	✅ Ready (Inspect)	Visit Preview	Apr 8, 2024 8:26pm

[coderabbitai]

Walkthrough

The recent updates focus on improving user experience and system efficiency across the Masterbots.ai platform. Enhancements include a strategic delay in capturing Vercel preview URLs, refined token retrieval mechanisms with better error handling, a streamlined layout adjustment, and an optimization in thread fetching. These changes collectively aim to enhance performance, reliability, and user interaction within the platform.

Changes

File Path	Change Summary
.github/workflows/lighthouse.yml	Added a step to wait for 2 minutes before capturing the Vercel preview URL.
apps/.../[chatbot]/[threadId]/page.tsx apps/.../[chatbot]/page.tsx	Updated JWT token retrieval using optional chaining (?.) for smoother access.
apps/.../layout.tsx	Commented out ChatLayoutSection component rendering, altering layout structure.
apps/.../components/shared/thread-list.tsx	Changed thread fetch limit from 50 to 25.

🐇✨
In the land of code and pixel,
Changes come, both big and minuscule.
A rabbit hops, leaving behind,
A trail of tweaks, refined and aligned.
🌟 For better days, through digital maze.
🥕🖥️

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 0

Review Status

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 05ac1af and 1c370f9.

Files selected for processing (5)

• .github/workflows/lighthouse.yml (1 hunks)
• apps/masterbots.ai/app/c/[chatbot]/[threadId]/page.tsx (1 hunks)
• apps/masterbots.ai/app/c/[chatbot]/page.tsx (1 hunks)
• apps/masterbots.ai/app/c/layout.tsx (1 hunks)
• apps/masterbots.ai/components/shared/thread-list.tsx (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/lighthouse.yml

Additional comments not posted (4)

apps/masterbots.ai/app/c/layout.tsx (1)

13-13: Commenting out ChatLayoutSection affects the chat layout structure. Please confirm this change aligns with the intended design and verify its impact on the user interface.

apps/masterbots.ai/components/shared/thread-list.tsx (1)

30-30: Reduced thread fetch limit from 50 to 25. Please ensure this change improves performance without negatively impacting user expectations.

apps/masterbots.ai/app/c/[chatbot]/[threadId]/page.tsx (1)

16-16: Introduced optional chaining for JWT token access. Ensure thorough testing, especially for missing or expired tokens.

apps/masterbots.ai/app/c/[chatbot]/page.tsx (1)

30-30: Introduced optional chaining for JWT token access. Ensure thorough testing, especially for missing or expired tokens.

[github-actions]

⚡️ Lighthouse report

Page: https://masterbots-za22a8ufn-bitcash.vercel.app/
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712608473810-38949.report.html

Category	Score
🔴 Performance	43
🟠 Accessibility	59
🟠 Best practices	74
🔴 SEO	42
🔴 PWA	13

Page: https://masterbots-za22a8ufn-bitcash.vercel.app/b/moneybot
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712608474250-64721.report.html

Category	Score
🟠 Performance	59
🟠 Accessibility	59
🟠 Best practices	74
🔴 SEO	42
🔴 PWA	13

Page: https://masterbots-za22a8ufn-bitcash.vercel.app/u/slug-1
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712608474636-5982.report.html

Category	Score
🟠 Performance	55
🟠 Accessibility	59
🟠 Best practices	74
🔴 SEO	42
🔴 PWA	13

Page: https://masterbots-za22a8ufn-bitcash.vercel.app/p
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712608474994-86039.report.html

Category	Score
🟠 Performance	58
🟠 Accessibility	59
🟠 Best practices	74
🔴 SEO	42
🔴 PWA	13

Page: https://masterbots-za22a8ufn-bitcash.vercel.app/health
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712608475472-36854.report.html

Category	Score
🟠 Performance	57
🟠 Accessibility	59
🟠 Best practices	74
🔴 SEO	42
🔴 PWA	13

Page: https://masterbots-za22a8ufn-bitcash.vercel.app/health/a8103808-14a3-48ed-aa5a-9e490cfdcf0e
Report https://storage.googleapis.com/lighthouse-infrastructure.appspot.com/reports/1712608476029-10618.report.html

Category	Score
🟠 Performance	55
🟠 Accessibility	59
🟠 Best practices	74
🔴 SEO	42
🔴 PWA	13