Copilot Github problems

Wappler General
1

Hi
today I received this message from github:

On behalf of the GitHub Security team, I want to first extend our gratitude for your continued use of GitHub and for being a valued member of the GitHub community.

Recent activity on your account has caught the attention of our abuse-detection systems. This activity may have included use of Copilot via scripted interactions, an otherwise deliberately unusual or strenuous nature, or use of multiple accounts to circumvent usage limits.

While we have not yet restricted Copilot access for your account, further anomalous activity could result in a temporary suspension of your Copilot access.

While I’m unable to share specifics on rate limits, we prohibit all use of our servers for any form of excessive automated bulk activity, as well as any activity that places undue burden on our servers through automated means. Please refer to our Acceptable Use Policies on this topic: GitHub Acceptable Use Policies - GitHub Docs.

Please also refer to our Terms for Additional Products and Features for GitHub Copilot for specific terms: GitHub Terms for Additional Products and Features - GitHub Docs.

What could be the problem ?

Thanks for your help.

2 Likes
2

Everyone should stop using the new Wappler AI features until this problem is solved, you're the third person affected by this issue

3 Likes
3

Yes for the same. Problem is that now wappler is sending all the page code but copilot has a 8.000 tokens limit per each request.

1 Like
4

We will be limiting the request size indeed as currently the whole current page is send and it can be too big for GitHub copilot and hit the limits.

So try using it on smaller pages or wait indeed till we implemented the limits.

1 Like
5

Yeah, got that too ... the new build uses up tokens very fast. I would avoid using the AI until this is fixed.

6

Thanks to all

7

Hello @George and team! I would like to know if Wappler is following the policy as GITHUB asks below! I had my account blocked there, I requested it and they unblocked it! but if there is another block it will be permanent!

Hi there,

I have now removed the restriction from your account. We kindly ask that you use Copilot strictly within our supported extensions and comply with our Terms of Service going forward to prevent any future restrictions.

It seems that your access to Copilot was restricted due to excessive and/or automated usage, usage through a proxy that interferes with how Copilot works, or credential sharing. This type of activity is in violation of our Terms of Service.

For basic security hygiene, please ensure that your credentials are being used exclusively by you. Please note that scripting against our API, including automated or excessive usage and programmatic token generation, is prohibited. You should research WAPPLER to make sure it does not go against GitHub's Terms of Service.

Please be aware that any subsequent violations of our Terms of Service and our Acceptable Use Policies may lead to the permanent revocation of your Copilot access and a permanent suspension of your GitHub account.

If you have any further questions or concerns, please don’t hesitate to reach out to us.

8

Hi Juliano,

Thanks for letting us know. We are already limiting the data we send copilot, so it doesn't trigger any limits on the acceptable usage.

How was your usage? Did you try it maybe on a large page in Wappler?
What did you requests it to do?

9

Not to sound too opinionated, but this is crazy that people keep running into this. @George I would disable the copilot feature until it's fully understood and resolved. It's bordering on irresponsible.

1 Like
10

They weren't big pages, I made several small and medium pages, I have the habit of asking to do it in excerpts!

11

In the update for tomorrow we will be making the AI Assistant request size for Github copilot and usage tokens more visible and will be limiting the send context more to the current selection. so the over usage limits shouldn't trigger.

See also as discussed:

3 Likes
12

Is there a way in the Copilot dashboard on GitHub to see how many tokens I have used and how many I have left? And when do they reset?

I haven't used the AI at all since I got a warning email. I can't afford to have my GitHub account suspended. I am scared to use the AI tool.

13

I would rather hear an exact RCA on what's causing the issues and whether the mitigation strategy of sending partial documents is going to resolve it. At this point, I agree with Brad, it's concerning that people are getting threats of having Github accounts suspended and deactivated based on normal use of the Wappler product. Is there an understanding of whether this is something that only impacts folks on the free tier? If so, should a paid tier be required by Wappler to protect the users? Is the Wappler team actively working with Github on the resolution?

1 Like
14

Yes we are busy exactly with that but it is difficult for us as well GitHub to pinpoint the exact cause because they have millions of users and also many additional rate limiting and security rules that can be easily triggered.

Currently it seem more that it happen to new users on the free GitHub copilot plan as those are handled with extra limits and security. So sending directly large requests can create such warnings.

We and many other pro users don’t experience any problems.

Anyway we hope to smoothen up things in the next Wappler beta tomorrow and we are also working with GitHub to improve the copilot integration even further.

5 Likes
15

I'm surprised to see nothing in the b21 release notes that acknowledges the issues people are having with Github Acceptable Use violations. The Wappler feature updates sound promising, but I'm not sure how you could recommend anyone actually use them without specifically addressing the fundamental issues with the copilot integration. You ask in the post "why not try it out?" sadly the answer is that you might lose your github account by trying it out...

16

We have established now a trusted usage by clearly identifying the Wappler requests and following all the GitHub rules, so users shouldn’t get blocked.

But of course GitHub has thousands additional security checks and some might trigger depending on your questions. And they can’t change those overnight.

So if you do get block and you thing is wrongly, just file an issue with GitHub and add me to the CC so we can investigate the case.

Btw we are now also official GitHub technology partner

1 Like