-
Notifications
You must be signed in to change notification settings - Fork 41
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
[Bug] Wrong price % change #72
Labels
bug
Something isn't working
Comments
Reply to me whenever you see my message, please I messaged you on every network I had |
Hey Farshid, what's up?
…On Mon, 13 May 2024, 01:06 Farshidtbn, ***@***.***> wrote:
Reply to me whenever you see my message, please I messaged you on every
network I had
—
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APDT3NRHT7IU3L4JI63E7P3ZB6OSNAVCNFSM6AAAAAAR3GPN4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGMYTMNBUGE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Please reply me
…On Tue, 14 May 2024, 18:30 Esi Esmaeli, ***@***.***> wrote:
Brian?
> Message ID: ***@***.***
> com>
>
|
Hi brian
I have only 1 question
…On Thu, 16 May 2024, 11:14 Esi Esmaeli, ***@***.***> wrote:
Please reply me
On Tue, 14 May 2024, 18:30 Esi Esmaeli, ***@***.***> wrote:
> Brian?
>> Message ID: ***@***.***
>> com>
>>
>
|
Please help me
…On Sun, 19 May 2024, 20:03 Esi Esmaeli, ***@***.***> wrote:
Hi brian
I have only 1 question
On Thu, 16 May 2024, 11:14 Esi Esmaeli, ***@***.***> wrote:
> Please reply me
>
> On Tue, 14 May 2024, 18:30 Esi Esmaeli, ***@***.***> wrote:
>
>> Brian?
>>> Message ID: ***@***.***
>>> .com>
>>>
>>
|
1m [32m [2024-06-09 22:18:44,560] MainProcess MainThread INFO
binance-pump-alerts-app Using config file: config.yml[0m Traceback (most
recent call last): File "/home/runner/Pump-Dump/pumpAlerts.py", line 92, in
<module> main() File "/home/runner/Pump-Dump/pumpAlerts.py", line 48, in
main chat_id=config["6093033558"], KeyError: '6093033558' [?25l
…On Mon, 27 May 2024, 21:45 Esi Esmaeli, ***@***.***> wrote:
Please help me
On Sun, 19 May 2024, 20:03 Esi Esmaeli, ***@***.***> wrote:
> Hi brian
> I have only 1 question
>
> On Thu, 16 May 2024, 11:14 Esi Esmaeli, ***@***.***> wrote:
>
>> Please reply me
>>
>> On Tue, 14 May 2024, 18:30 Esi Esmaeli, ***@***.***> wrote:
>>
>>> Brian?
>>>> Message ID: <brianleect/binance-pump-alerts/issues/72/2106337459@
>>>> github.com>
>>>>
>>>
|
1m [32m [2024-06-09 22:18:44,560] MainProcess MainThread INFO
binance-pump-alerts-app Using config file: config.yml[0m Traceback (most
recent call last): File "/home/runner/Pump-Dump/pumpAlerts.py", line 92, in
<module> main() File "/home/runner/Pump-Dump/pumpAlerts.py", line 48, in
main chat_id=config["6093033558"], KeyError: '6093033558' [?25l
The token is ok, but I gave a numerical ID of the channel, I gave a user
ID, and the ID itself gives the robot a problem! I don't know what idea he
wants I will also send the first description of the site
…On Mon, 10 Jun 2024, 09:17 Esi Esmaeli, ***@***.***> wrote:
1m [32m [2024-06-09 22:18:44,560] MainProcess MainThread INFO
binance-pump-alerts-app Using config file: config.yml[0m Traceback (most
recent call last): File "/home/runner/Pump-Dump/pumpAlerts.py", line 92, in
<module> main() File "/home/runner/Pump-Dump/pumpAlerts.py", line 48, in
main chat_id=config["6093033558"], KeyError: '6093033558' [?25l
On Mon, 27 May 2024, 21:45 Esi Esmaeli, ***@***.***> wrote:
> Please help me
>
> On Sun, 19 May 2024, 20:03 Esi Esmaeli, ***@***.***> wrote:
>
>> Hi brian
>> I have only 1 question
>>
>> On Thu, 16 May 2024, 11:14 Esi Esmaeli, ***@***.***> wrote:
>>
>>> Please reply me
>>>
>>> On Tue, 14 May 2024, 18:30 Esi Esmaeli, ***@***.***>
>>> wrote:
>>>
>>>> Brian?
>>>>> Message ID: <brianleect/binance-pump-alerts/issues/72/2106337459@
>>>>> github.com>
>>>>>
>>>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Clearly it can't be 97%. Need to take a closer look at implementation. Suspect >1 price pushed in per interval resulting in wrong calculation?
The text was updated successfully, but these errors were encountered: