20 Open Issues Need Help Last updated: Sep 21, 2025

Open Issues Need Help

View All on GitHub

AI Summary: This issue requires writing an integration test for `ExecuteSimpleStrategyJob` to verify its end-to-end trading orchestration. The test will enqueue and perform the job, mock the `AlpacaService` to prevent real trades, and confirm that `GenerateTargetPortfolio` and `RebalanceToTarget` are called correctly and in the expected order.

Complexity: 3/5
enhancement good first issue

AI Summary: This issue requires writing VCR-backed RSpec tests for the existing `AlpacaService` to verify its interactions with the Alpaca API. The tests should cover public methods like `get_account_equity`, `get_current_positions`, and `place_order`, ensuring correct request formation and response parsing for both successful operations and API error handling.

Complexity: 3/5
enhancement good first issue dependencies

AI Summary: This issue requires implementing an `AlpacaService` class to encapsulate interactions with the Alpaca trading API using the `alpaca-trade-api-ruby` gem. The service needs to include public methods such as `get_account_equity`, `get_current_positions`, and `place_order`, ensuring it's initialized with the configured Alpaca client and passes all specified linters.

Complexity: 2/5
enhancement good first issue
enhancement good first issue

AI Summary: This issue requires creating an ActiveRecord model `QuiverTrade` and its corresponding database migration to store raw congressional trading data. The task includes defining the `quiver_trades` table schema, placing the model in a specific directory, and adding basic model specs for key fields, all while ensuring linter compliance.

Complexity: 2/5
enhancement good first issue
enhancement good first issue dependencies
enhancement good first issue

AI Summary: This issue focuses on implementing backend API endpoints for managing `Analysis` resources within the `packs/performance_analysis` pack. It requires creating an `AnalysesController` with a `POST /api/v1/analyses` endpoint to initiate a new analysis using the `InitiatePerformanceAnalysis` command, returning its ID and pending status. Additionally, a `GET /api/v1/analyses/:id` endpoint will retrieve the analysis's status and results, with comprehensive request specs required for both.

Complexity: 3/5
enhancement good first issue
enhancement good first issue
enhancement good first issue
Setup Gems about 2 months ago
documentation enhancement good first issue dependencies
enhancement good first issue
enhancement good first issue
enhancement good first issue
enhancement good first issue
enhancement good first issue
enhancement good first issue dependencies