Freqtrade, an open-source cryptocurrency trading bot, continues to evolve with a strong emphasis on integrating advanced machine learning features and improving user engagement through enhanced documentation and community support.
Recent issues and pull requests (PRs) indicate a concerted effort to refine the FreqAI module, addressing compatibility challenges with various exchanges and enhancing analytical capabilities. Notable issues include #10571, which highlights discrepancies in backtesting signal generation, and #10542, which reports a segmentation fault on Apple M2 systems. These issues underscore ongoing challenges in ensuring robust performance across diverse environments.
The team's activities reflect a focus on code quality, documentation clarity, and feature enhancements, indicating a commitment to both technical excellence and user education.
Timespan | Opened | Closed | Comments | Labeled | Milestones |
---|---|---|---|---|---|
7 Days | 8 | 8 | 32 | 0 | 1 |
30 Days | 39 | 41 | 156 | 0 | 1 |
90 Days | 120 | 117 | 500 | 2 | 1 |
1 Year | 214 | 200 | 902 | 3 | 1 |
All Time | 4629 | 4590 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
Developer | Avatar | Branches | PRs | Commits | Files | Changes |
---|---|---|---|---|---|---|
Matthias | 4 | 8/8/0 | 161 | 3093 | 2649060 | |
github-actions[bot] | 1 | 0/0/0 | 6 | 63 | 842 | |
dependabot[bot] | 2 | 48/43/5 | 34 | 7 | 70 | |
Stefano Ariestasia | 1 | 1/1/0 | 1 | 2 | 28 | |
Robert Davey | 1 | 3/2/1 | 3 | 2 | 24 | |
iridescentGray | 1 | 1/1/0 | 1 | 1 | 2 | |
Masoud Azizi (mablue) | 0 | 1/0/1 | 0 | 0 | 0 | |
Simon Waiblinger (simwai) | 0 | 0/1/0 | 0 | 0 | 0 | |
None (MikForge) | 0 | 1/0/1 | 0 | 0 | 0 | |
Anuj Jain (jainanuj94) | 0 | 1/1/0 | 0 | 0 | 0 | |
Nikhil Saraf (nikhilsaraf) | 0 | 1/0/1 | 0 | 0 | 0 | |
None (dingzhengxia) | 0 | 1/0/1 | 0 | 0 | 0 | |
Botting away . . . (freqtrade-bot) | 0 | 7/7/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
The Freqtrade GitHub repository has seen a notable increase in activity, with 39 open issues, including recent discussions around the integration of reinforcement learning and various bugs related to trading strategies. A significant focus is on the functionality of the FreqAI module, particularly its compatibility with different exchanges like Kraken, which has limitations due to its API not providing sufficient historical data for effective trading strategies.
Several issues highlight common problems such as discrepancies in stake amounts during trades, challenges with backtesting due to missing data, and the need for better handling of leverage in futures trading. The community appears engaged, with users actively seeking solutions and sharing insights on implementing features like dynamic pairlists and automated hyperparameter optimization.
Here are the most recently created and updated issues:
Issue #10571: Inconsistent signal generation during backtesting
Issue #10542: FreqAI segmentation fault on Apple M2 (metal)
Issue #10517: Getting episodic trades to the reward function on freqtrade-rl
Issue #7190: Hyperopt cmd line new subcommand for forward validation
Issue #10503: Is Binance supported in "Credit Trading Mode" for Perpetual Futures?
This analysis highlights ongoing challenges faced by users while also showcasing the active engagement of the community in seeking solutions and contributing to the development of Freqtrade.
The analysis covers a total of 9 open pull requests (PRs) from the Freqtrade project, highlighting enhancements, dependency updates, and ongoing discussions regarding feature implementations. The PRs reflect active development and community engagement in improving the trading bot's capabilities.
PR #10485: Add exit signals to export in backtesting
PR #10491: chore(deps): bump xgboost from 2.0.3 to 2.1.1
PR #10243: Draft: Add DDPG and TD3 model options for RL
PR #10173: Fix mutable defaults, enable bugbear ruff rule
PR #10098: Implement a parameter for skipping errors during model training in the backtest process
PR #10062: Feature: Proceed exit while having open order, for backtesting and live
PR #9989: 9985 delist schedule
PR #9305: Optimize dtypes for hyperopt and backtesting to decrease memory usage
PR #3059: Outstanding balance function
The current set of open pull requests showcases a vibrant development environment within the Freqtrade project, emphasizing both functional enhancements and technical maintenance.
A recurring theme across several PRs is the focus on enhancing analytical capabilities through improved data handling and additional features for backtesting. For instance, PR #10485 introduces exit signals into backtesting analysis, which aligns with user needs for more comprehensive performance metrics. Similarly, PR #10098 aims to improve robustness by allowing error skipping during model training, addressing potential interruptions caused by data issues.
Moreover, there is a notable emphasis on dependency management and code quality improvements. The updates to libraries such as XGBoost (#10491) and various other dependencies demonstrate an ongoing commitment to keeping the project up-to-date with external changes while ensuring compatibility with newer versions of libraries like NumPy and FastAPI.
While most PRs are progressing well, some have raised questions or concerns among contributors. For example, PR #10098 has sparked discussions about whether it should be implemented as a flag or integrated directly into the backtesting process without optionality. Such debates highlight differing opinions on how best to enhance user experience versus maintaining simplicity in usage.
Additionally, PR #10243 remains in draft status as contributors refine its implementation details for new reinforcement learning models. This indicates that while there is enthusiasm for expanding machine learning capabilities within Freqtrade, careful consideration is being taken before finalizing such significant additions.
Despite several active discussions around these PRs, there appears to be a lack of recent merge activity, particularly for older pull requests like #9305 and #3059 that have been open for an extended period (over 300 days). This could suggest potential bottlenecks in review processes or resource allocation within the development team that may need addressing to maintain momentum.
Overall, the current landscape of pull requests reflects a healthy mix of innovation and maintenance within the Freqtrade project. The community's engagement in discussions around features and improvements indicates a collaborative spirit aimed at enhancing both functionality and user experience. However, attention should be given to expediting reviews and merges for older PRs to ensure that contributions do not stagnate over time.
ccxt
, fastapi
, matplotlib
, and others, ensuring the project remains up-to-date with the latest versions.High Activity Level: Matthias is highly active, contributing a significant number of commits focused on refactoring, feature additions, and documentation improvements. This indicates a strong commitment to enhancing code quality and user guidance.
Documentation Focus: There is a consistent effort to improve documentation, making it clearer for users. This includes clarifications about features and usage scenarios, which aligns with the project's educational emphasis.
Collaborative Efforts: Collaboration is evident through merged pull requests from various contributors, indicating an engaged community contributing to different aspects of the project.
Automated Maintenance: Dependabot's presence reflects an automated approach to managing dependencies, which helps maintain project stability without manual intervention.
Feature Enhancements: Recent commits show a focus on enhancing existing features (e.g., trading history checks) and adding new functionalities that improve user experience.
The development team is actively engaged in maintaining and enhancing the Freqtrade project. The focus on refactoring, documentation, and dependency management suggests a commitment to both code quality and user experience. The collaborative nature of contributions indicates a healthy community around the project, supporting its growth and sustainability.