fregate / sgbot Goto Github PK

https://freesteam.ru/category/active/

If there error in config while web-editing, all service will down.
Have to update confg and stay web-interface alive to have a chance to change something back

Если в конфигах, которые через веб интерфейс поправили, вдруг какая-то ошибка, то весь сервис падает. Необходимо оставлять работать веб-интерфейс, что бы была возможность починить кривые данные.

Now everything in main package (dedicated bot, cloud bot)
Separate it between packages to remove unnecessary dependencies (for dedicated an least)

Check is some followed games from steam is filtered out in steamgifts

`
05:15:17, 14.07.2022
INFO
START RequestID: 05eb81c3-af64-4d3b-b4fa-a9dc60e30d36 Version: d4eat2uqt6l2ugd958q0

05:15:22, 14.07.2022
{"errorMessage":"execution timeout exceeded","errorType":"JobExecutionTimeoutExceeded","stackTrace":null}

05:15:22, 14.07.2022
INFO
END RequestID: 05eb81c3-af64-4d3b-b4fa-a9dc60e30d36
05:15:22, 14.07.2022
ERROR RequestID: 05eb81c3-af64-4d3b-b4fa-a9dc60e30d36 Code: 504 Message: Execution timeout exceeded

05:15:22, 14.07.2022
INFO
REPORT RequestID: 05eb81c3-af64-4d3b-b4fa-a9dc60e30d36 Duration: 5174.763 ms Billed Duration: 5200 ms Memory Size: 128 MB Max Memory Used: 115 MB Queuing Duration: 0.062 ms Function Init Duration: 173.120 ms
`

In some case, Cloud couldn't send digest, but all records already deleted.

1. Do not remove records before digest successful sending
2. Can could function get info from somewhere - why and what is the error and reschedule itself?

• set this cookies
• use direct link to claim giveaway
• in function - set check period

NodeJS? + some front

If some points are left after entering in giveaways, they can be accumulated in further "heavy" GA's.

0. Check GA for apply. If some points left (more than threshold, 15 for example)
1. Go to a last pages
2. Select GA's more than 15 (for example) points, enter - save.
3. After bot starts get all entered GA's, check for whitelisted games, all other GA's is accumulators. Store for bot lifetime
4. When check GA's for apply and if there is no points available - check accumulators. If any available, and accumulated points is more than GA need - remove some Accumulator GA and use this points to enter to whitelisted GA.

Collateral damage: if there is no need in points - some unnecessary (accumulated) GA could be won ))) - in this case bot remove points from recent accumulators and reenter into much further.

Make one-timer function to create tables

All parameters for mailer is env variables - so you have to update function version if you change some of these params. But if you put parameters into DB, you can change any of them without change cloud-function.

StamGifts change html - giveaways status check returns with errors

It's kind of statistics.
Store all the interesting GA in map and remove entered GA at the end of the day.
It gives some statistics about missing GAs
After that you can decide about improve or not this bot )

Create db with stats for entered GA (how many times title gave away in site and the bot entered) by year )))

And later when fy.py used - get this stat also to decide - remove from followed or not