Closed aykutdemirel closed 9 months ago
this is the 3rd issue that you open about this topic, and the 3rd time you
This is the same exact information i requested in your other issue, https://github.com/freqtrade/freqtrade/issues/9495#issuecomment-1837882826, and https://github.com/freqtrade/freqtrade/issues/9495#issuecomment-1844517041
To quote from the above issues:
Please provide at least 20 lines (more is better, including startup logs would be best) up to the creation of the trade - so we can determine if other problems might cause this.
We asked for more logs - which were not provided. We still don't know the version you've been using when you encountered the problem (issue template!)
so let me repeat this request again for clarity:
Please provide the actual version (the issue template tells you HOW to get the version. Neither stable, nor develop nor "latest docker image" will suffice).
Please provide at least 20 lines (more is better, including startup logs would be best) up to the creation of the trade - so we can determine if other problems might cause this.
please note: as this is the 3rd issue about the same topic where the information we're requesting is missing, I feel obliged to issue an official warning.
I expect your next comment to include this information. If it does not, i'll close this issue as a clear sign that you do not intend to receive help and are simply trying to waste our time.
Opening another issue about the same topic with the same information missing again will force me to block you from interacting with this organization, as that's just trolly behavior, without actually wanting to provide us with the information necessary to actually assist you.
unfortunately, from your description it's unclear if it's working in the older images (before july) - or in the newer images (after july).
To clarify this - can you please use the following to provide us with the precise versions (for both the version you think it's working,and the version it's not):
docker compose run --rm freqtrade -V
(taken from the issue template).
As a side note: please submit this as a new comment below - that will give us a "ping" (notification) - whereas an edit to the original comment will not.
Hi, I really would like to provide logs and try out "docker compose run --rm freqtrade -V" part. Unfortunately, we changed our server just a few days ago and on the new server we are using the freqtradeorg/freqtrade:2023.7 version.
I can provide the logs in 2 weeks. You can keep this issue open, or please close it, I can re-create it when I tryout with the new version again. @xmatthias
I've just tested a binance futures position with the latest develop (2023.12-x) - and leverage is working just fine. I'll not do the reverse test with 2023.7, as that version is not something i'll even attempt to support (to properly invest our limited resources (speak, our free time) we do support the current stable, and unreleased develop versions only).
(using tiny sizes as i'm not actually going to stick to that position - i've just opened it to test for this issue.
your logs you indicate don't really show much other than "open a position at 1x". As mentioned before, using a wrong strategy (duplicate class names) can be a quite common cause for this.
What i can advise though: do not use outdated versions. Exchange API's update all the time, so does ccxt. Using a version that's 6 months old on something that's managing my money is not something i'd personally do.
I'll close this for now, as it's not something i'm able to even remotely recreate, however the issue won't be locked, and i'll get a notification if you respond below - so if you still encounter this with a supported version (2023.11 or 2023.12-dev) please let me know so we can have a look what's wrong in your environment (for now, i doubt it's a freqtrade issue - as it's working perfectly fine for me).
Environment
Note: All issues other than enhancement requests will be closed without further comment if the above template is deleted or not filled out.
The problem:
After I pulled the new docker image my leverage got stuck as 1.
Steps to reproduce:
Observed Results:
What happened? Before pulling the image leverage was working perfectly. After pulling the latest image, leverage set as 1 no matter what I set in the strategy.
What did you expect to happen? It should have worked before how was working
Relevant code exceptions or logs
CONFIG
DOCKER-COMPOSE
CODE