[GUIDE] How to Overcome the new API Changes to Refresh/IP Throttle after 10 tries

[UPDATE] Issue Resolved in v5.2.0 Release
Due to some new changes in the CoWIN Private APIs there has been the following observations:

Seems like they removed Captcha requirement for Booking
They have added some hard refresh limit of the APIs so that users can't keep on hitting their server. Currently, based on User Inputs and analysis, it has been found that the Limit is of 10/20 Requests after which IP is throttled. {'message': 'User is not authorized to access this resource with an explicit deny'}

So, a temporary workaround to go around this for the moment till we get a solution is this:

This is a two step Process: FindingSlot and BookingSlot.
Step For Finding Slot:

Run the Application as usual  (CoWinVaccineSlotFinder.exe for Windows, or run.sh for Linux/Mac) and then after you receive the OTP and enter the OTP, you'll be shown that your OTP is stored in authToken.json file. Once that is done, close the application.

There is an option in the config file appsettings.json "ProtectedAPI": { "IsToBeUsed": true CHANGE it to "IsToBeUsed": false This would make use of the Public API to find the Slots for the meantime, since there is no hard limit of 10/20 requests. It'll work till 100 requests/5 minutes.

After making the change in the Config, save it and Run the Application (CoWinVaccineSlotFinder.exe for Windows, or run.sh for Linux/Mac) and let it run until it finds a slot.  Proof below that it runs even after 10 tries as well.

After the Application starts running, again go to the config file and  CHANGE it to "IsToBeUsed": true . We are doing this because for Booking of Slot we need the Protected API and we don't want to waste any time when slot is found

Following will be shown when you run the Application as it will keep on searching and when Slot is found it'll crash the application as booking is not allowed using Public API. You just need to close the Application and following the next step for booking.

Step For Booking Slot

As soon as you find slot is available from the above step, close the Running Application as the Application will automatically crash.

Make sure  "ProtectedAPI": { "IsToBeUsed": true is set in the config file appsettings.json

Run the Application once again (CoWinVaccineSlotFinder.exe for Windows, or run.sh for Linux/Mac)

This will not need the OTP again as your OTP is already being asked in the above step and your authentication credentials are saved in authToken.json.

You'll right away see the slot and your booking will be done. Since Captcha is still not removed from Code, so use "AutoReadCaptcha": true

This is just a hot-fix without making any changes in the Code. Please do let us know if this trick works so that we can work on fixing it and releasing a new release version.

Getting following error with 5.1.
It started showing the IP throttling error after fixed 10 numbers of try and does not resume even after restart or change of IP address or anything....pls look into this matter

@Suren1978 Have you tried by changing the config as suggested in the description. Please do that and inform. Otherwise it won't work directly due to changes in the API made by COWIN Team this evening.

I tried the above suggested method but facing a new problem as it could not establish session even i m entering correct and valid OTP (see above image)

actually it could not establish session with public API

I tried the above suggested method but facing a new problem as it could not establish session even i m entering correct and valid OTP (see above image)

@Suren1978 bro. Hide ur mobile no

I tried the above suggested method but facing a new problem as it could not establish session even i m entering correct and valid OTP (see above image)

@Suren1978 bro. Hide ur mobile no

bro pls delete image in your reply

bro pls delete images i send ...it is request
On Thu, Jun 3, 2021, 23:12 520rahul @.***> wrote:

[image: Screenshot (21)]
https://user-images.githubusercontent.com/85307388/120686047-31025980-c4be-11eb-9edd-57e3ead4b328.png
I tried the above suggested method but facing a new problem as it could
not establish session even i m entering correct and valid OTP (see above
image)
@Suren1978 https://github.com/Suren1978 bro. Hide ur mobile no
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SRvSaha/CoWinVaccineSlotFinder/issues/79#issuecomment-854057981,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUK277CIOECOYGPMDYLF7N3TQ65HHANCNFSM46BFFU2Q
.

Not sure but in the evening when I tried using the 5.1 for Autocaptcha set as true, it entered captcha automatically and didnt book the slot (as the captcha was disabled on the cowin by default) but again i tried setting the autocaptcha as false, then it popped up captcha  and when i entered it, slot got booked.
is it somehow related @SRvSaha

This will have to be a 3 step process I guess...

Let the Protected API be set to true for login
After login, close the app. Change it to false and then open again.
When slot opens, close the app, change the protected API to true and open again.

I tried doing this, and not facing any login related issues.

This will have to be a 3 step process I guess...

Let the Protected API be set to true for login
After login, close the app. Change it to false and then open again.
When slot opens, close the app, change the protected API to true and open again.

I tried doing this, and not facing any login related issues.

Correct it is working in this way only but 10 tries are fixed even you switch between true nfalse

bro pls delete images i send ...it is request
…

Sorry. I couldn’t see it.  I have deleted the same

Every time you receive a new OTP ...Cowin will give you 10 tries only ...therefore authToken file doesn't work ....you just remove this file to generate OTP again and then only Cowin portal give you another 10 chance to hit.....is there any solution of this problem....

Not sure but in the evening when I tried using the 5.1 for Autocaptcha set as true, it entered captcha automatically and didnt book the slot (as the captcha was disabled on the cowin by default) but again i tried setting the autocaptcha as false, then it popped up captcha and when i entered it, slot got booked.
is it somehow related @SRvSaha

No. Seems like captcha is disabled by CoWin. If possible share screnshot from CoWIN Portal so that Captcha can be removed from Code. Even through they removed captcha, there is no issue with Auto-Captcha, booking still work. Only issue is due to very harsh limits for Protected APIs to stop API-Abuse.

This will have to be a 3 step process I guess...
1. Let the Protected API be set to true for login

2. After login, close the app. Change it to false and then open again.

3. When slot opens, close the app, change the protected API to true and open again.

I tried doing this, and not facing any login related issues.

Perfect! This is correct. Actually this is what I was trying to explain in detail.
@govindasomani @520rahul @Suren1978 @Tnu02

This will have to be a 3 step process I guess...
1. Let the Protected API be set to true for login

2. After login, close the app. Change it to false and then open again.

3. When slot opens, close the app, change the protected API to true and open again.

I tried doing this, and not facing any login related issues.

Perfect! This is correct. Actually this is what I was trying to explain in detail.
@govindasomani @520rahul @Suren1978 @Tnu02

Let me try this...

Every time you receive a new OTP ...Cowin will give you 10 tries only ...therefore authToken file doesn't work ....you just remove this file to generate OTP again and then only Cowin portal give you another 10 chance to hit.....is there any solution of this problem....

See, AuthToken is needed only for Protected APIs. We are trying to shift the searching of slots part from Protected APIs (which needs AuthToken) to Public APIs (which doesn't need Auth Token, but are rate limited to 100/5 mins). In this way, we will have our Session Logged In using the AuthToken, so that when we get a slot using the Public API, we close the App, change the setting to use the Protected API and then booking can get done without waiting for OTP

Every time you receive a new OTP ...Cowin will give you 10 tries only ...therefore authToken file doesn't work ....you just remove this file to generate OTP again and then only Cowin portal give you another 10 chance to hit.....is there any solution of this problem....

See, AuthToken is needed only for Protected APIs. We are trying to shift the searching of slots part from Protected APIs (which needs AuthToken) to Public APIs (which doesn't need Auth Token, but are rate limited to 100/5 mins). In this way, we will have our Session Logged In using the AuthToken, so that when we get a slot using the Public API, we close the App, change the setting to use the Protected API and then booking can get done without waiting for OTP

The only problem that can come with this, is that because public API is cached, you may not get the slot immediately after it opens. And if there is too much time gap between the slot opening and showing on public API, then those might get booked too. As a workaround, you can shift from public to protected API once you see a telegram notification of slot opening. Just a thought, have not tested this.

Every time you receive a new OTP ...Cowin will give you 10 tries only ...therefore authToken file doesn't work ....you just remove this file to generate OTP again and then only Cowin portal give you another 10 chance to hit.....is there any solution of this problem....

See, AuthToken is needed only for Protected APIs. We are trying to shift the searching of slots part from Protected APIs (which needs AuthToken) to Public APIs (which doesn't need Auth Token, but are rate limited to 100/5 mins). In this way, we will have our Session Logged In using the AuthToken, so that when we get a slot using the Public API, we close the App, change the setting to use the Protected API and then booking can get done without waiting for OTP

The only problem that can come with this, is that because public API is cached, you may not get the slot immediately after it opens. And if there is too much time gap between the slot opening and showing on public API, then those might get booked too. As a workaround, you can shift from public to protected API once you see a telegram notification of slot opening. Just a thought, have not tested this.

True. But usually Public APIs also get more or less data at similar times as 99% of Telegram or other notifiers using Public APIs only for notifying.

This will have to be a 3 step process I guess...
1. Let the Protected API be set to true for login

2. After login, close the app. Change it to false and then open again.

3. When slot opens, close the app, change the protected API to true and open again.

I tried doing this, and not facing any login related issues.

Perfect! This is correct. Actually this is what I was trying to explain in detail.
@govindasomani @520rahul @Suren1978 @Tnu02

I am updating the description with screenshots

Getting catpcha while booking with 5.1 and not on manual.

Getting catpcha while booking with 5.1 and not on manual.

@Tnu02 @520rahul @Suren1978 Screenshots updated and tested in personal system, found it to be working. Try it out as per the screenshots and instructions in the description of the Issue. @govindasomani Thanks for pointing out

Getting catpcha while booking with 5.1 and not on manual.

Make sure you have set this properly.

Getting catpcha while booking with 5.1 and not on manual.

Make sure you have set this properly.

Yup.. I did it false intentionally, just to check whether captcha appear or not..

Getting catpcha while booking with 5.1 and not on manual.

Make sure you have set this properly.

Yup.. I did it false intentionally, just to check whether captcha appear or not..

Please check and delete the image as mobile number is showing @SRvSaha

@Tnu02 @520rahul @Suren1978 Screenshots updated and tested in personal system, found it to be working. Try it out as per the screenshots and instructions in the description of the Issue. @govindasomani Thanks for pointing out

I hv already tried and mentioned to @govindasomani that this is working in this way only...

@Tnu02 Cool. Had to delete the comments as it had the mobile number. See the updated Description.
@Suren1978 Yeah, updated the steps mentioned by @govindasomani in the description.

I hv just tried for booking a slot for 45+ on trial basis ...no captcha was needed for this....I am not sure that it was previously needed for 45+ before amending in API

I hv just tried for booking a slot for 45+ on trial basis ...no captcha was needed for this....I am not sure that it was previously needed for 45+ before amending in API

Okay cool @Suren1978, so now it is confirm that they removed Captcha. Can you please go to the Network Tab and then Select XHR like below, that will make sure what is being passed in the API. It was needed Previously. They made changes today evening

Getting catpcha while booking with 5.1 and not on manual.

Make sure you have set this properly the setting "AutoReadCaptcha": true

Sorry I had to delete your comment.
Just curious, could you book the slot after following the steps?

I hv just tried for booking a slot for 45+ on trial basis ...no captcha was needed for this....I am not sure that it was previously needed for 45+ before amending in API

Okay cool @Suren1978, so now it is confirm that they removed Captcha. Can you please go to the Network Tab and then Select XHR like below, that will make sure what is being passed in the API. It was needed Previously. They made changes today evening

They removed captcha for manual process but still we get it when booking it with the exe

Getting catpcha while booking with 5.1 and not on manual.

Make sure you have set this properly the setting "AutoReadCaptcha": true

Sorry I had to delete your comment.
Just curious, could you book the slot after following the steps?

Yes.. Checked with both manually entering captcha and autocaptcha true...

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs. What say? Do you see any flaws in this?
We will remove the captcha from the Application so it works without it and saves some time.

@SRvSaha even tho autocaptcha is set to false, still getting the pop up for it..

I hv just tried for booking a slot for 45+ on trial basis ...no captcha was needed for this....I am not sure that it was previously needed for 45+ before amending in API

Okay cool @Suren1978, so now it is confirm that they removed Captcha. Can you please go to the Network Tab and then Select XHR like below, that will make sure what is being passed in the API. It was needed Previously. They made changes today evening

They removed captcha for manual process but still we get it when booking thru the exe

Yes it is because we have not removed it yet from the Application yet. Who knows if they again come up with Captcha tomorrow? Also, removing captcha is not tough, just need assurance that it works with Captcha as well that that users can still book without upgrade till a new version will all the fixes are done.

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs

The description is perfect. Need to test it in a live environment when slots are releasing.  Conceptually though, there seems to be no problem with the flow.

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs

The description is perfect. Need to test it in a live environment when slots are releasing. Conceptually though, there seems to be no problem with the flow.

Agree with @govindasomani

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs. What say? Do you see any flaws in this?
We will remove the captcha from the Application so it works without it and saves some time.

@SRvSaha even tho autocaptcha is set to false, still getting the pop up for it..

@Tnu02 Yes you are supposed to get. False => Manual Captcha, true => Auto Captcha

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs. What say? Do you see any flaws in this?
We will remove the captcha from the Application so it works without it and saves some time.

@SRvSaha even tho autocaptcha is set to false, still getting the pop up for it..

@Tnu02 Yes you are supposed to get. False => Manual Captcha, true => Auto Captcha

Thou they removed it for manual user !!

@SRvSaha i think this will work.  I shall tell u my experience. Thanks again brother. And eagerly waiting for v 5.1.1 as mentioned by u. God bless u

3\. We will remove the captcha from the Application so it works without it and saves some time.

Read this part: "We will remove the captcha from the Application so it works without it and saves some time."
They have removed it (hidden it). But since our Code still has it so you are getting the Captcha. That's why I am saying it is not hampering the core functionality though, as bookings are still successful. So, we can remove it only after testing of it as mentioned in previous chat

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs

The description is perfect. Need to test it in a live environment when slots are releasing. Conceptually though, there seems to be no problem with the flow.

Agree with @govindasomani

@govindasomani @Tnu02 @520rahul @Suren1978 Okay cool. Let's wait till tomorrow 8 pm, since most bookings come from 4pm to 8 pm. See if you can do the testing and tally the results will Telegram/other realtime notifiers if we are getting the slots in correct time. And then is booking successful. If these things are okay, I will make the changes and release by EOD around 11 pm when traffic is low. Your support and comment please?

Sure. Will keep you posted on the experience.

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs

The description is perfect. Need to test it in a live environment when slots are releasing. Conceptually though, there seems to be no problem with the flow.

Agree with @govindasomani

@govindasomani @Tnu02 @520rahul @Suren1978 Okay cool. Let's wait till tomorrow 8 pm, since most bookings come from 4pm to 8 pm. See if you can do the testing and tally the results will Telegram/other realtime notifiers if we are getting the slots in correct time. And then is booking successful. If these things are okay, I will make the changes and release by EOD around 11 pm when traffic is low. Your support and comment please?

As of now it seems that it is working but ya need to check in real time scenario and then only would able to share with you @SRvSaha . Thanks

@SRvSaha i think this will work. I shall tell u my experience. Thanks again brother. And eagerly waiting for v 5.1.1 as mentioned by u. God bless u

Thanks @520rahul. Please do testing in the live environment along with all details. I don't want the release to hamper bookings of users.

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs

The description is perfect. Need to test it in a live environment when slots are releasing. Conceptually though, there seems to be no problem with the flow.

Agree with @govindasomani

@govindasomani @Tnu02 @520rahul @Suren1978 Okay cool. Let's wait till tomorrow 8 pm, since most bookings come from 4pm to 8 pm. See if you can do the testing and tally the results will Telegram/other realtime notifiers if we are getting the slots in correct time. And then is booking successful. If these things are okay, I will make the changes and release by EOD around 11 pm when traffic is low. Your support and comment please?

As of now it seems that it is working but ya need to check in real time scenario and then only would able to share with you @SRvSaha . Thanks

Yes do test and inform by 20:00 Hrs tomorrow.

the above is the image without asking for captcha but I hv not confirmed the booking

the above is the image without asking for captcha but I hv not confirmed the booking

Ok cool. Seems like they aren't calling the captcha endpoint. Do the testing of the application in live booking and let me know. We'll make the fixes.

the above is the image without asking for captcha but I hv not confirmed the booking

Ok cool. Seems like they aren't calling the captcha endpoint. Do the testing of the application in live booking and let me know. We'll make the fixes.

Sure boss. @SRvSaha i will keep u posted after checking in real time situation so that u can modify the new version accordingly

@govindasomani @Tnu02 @520rahul @Suren1978 At the time of Testing, please change the URLs to use findByPIN and findByDistrict as well. Based on user feedback from multiple places, people are telling that findByDistrict usually is used in Telegram as it has near real-time data and doesn't cache.
I am adding the block here:
       "FetchCalenderByDistrictUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/public/findByDistrict",       "FetchCalenderByPINUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/public/findByPin"

Just trying again with autocaptcha set as false.. pop up appear for captcha and if we  cancel it then also it is booking the slot...

Just trying again with autocaptcha set as false.. pop up appear for captcha and if we cancel it then also it is booking the slot...

Yeah @Tnu02, that is happening because when you are closing the Captcha Popup, Captcha Value is Blank. But since the API doesn't consider the Captcha Value for Booking, hence it works. Same is the reason when Auto-Captcha is turned on. It computes and sends the captcha, however it is neglected at the Server Side that's why our Application is still working. Otherwise it would have broken.

@SRvSaha boss i m facing 2 issues-

When i changed public api to find by pin and find by district then error shown as per screenshot attahced.
When i changed it back to calendar by pin and district then though it was searching for slots but even i set my refresh limit to 3000 millisecods. It started giving me fatel error even on public api and even after restarting the application fatel errror did not stopped

@govindasomani @Tnu02 @520rahul @Suren1978 At the time of Testing, please change the URLs to use findByPIN and findByDistrict as well. Based on user feedback from multiple places, people are telling that findByDistrict usually is used in Telegram as it has near real-time data and doesn't cache.
I am adding the block here:
 "FetchCalenderByDistrictUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/public/findByDistrict", "FetchCalenderByPINUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/public/findByPin"

Guys, yet another test case.
Please use the ProtectedAPI and changes the URLs to the following. Saw discussions that only CalenderAPIs has the hard refresh limit of 10/20. For FindAPIs it is not there.
Test Case 1: This can be tested now
    "ProtectedAPI": {
      "IsToBeUsed": true,
      "FetchCalenderByDistrictUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/findByDistrict",
      "FetchCalenderByPINUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/findByPin"
    }

Test Case 2: This can be tested now
    "PublicAPI": {
      "FetchCalenderByDistrictUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/public/findByDistrict",
      "FetchCalenderByPINUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/public/findByPin"
    },
   "ProtectedAPI": {
      "IsToBeUsed": false,
   }

https://cdn-api.co-vin.in/api/v2/appointment/sessions/findByDistrict

this is the error as mentioned in point 1

@SRvSaha boss i m facing 2 issues-
1. When i changed public api to find by pin and find by district then error shown as per screenshot attahced.

2. When i changed it back to calendar by pin and district then though it was searching for slots but even i set my refresh limit to 3000 millisecods. It started giving me fatel error even on public api and even after restarting the application fatel errror did not stopped

Ok @520rahul I will check it out. I got the reason why it is failing. Basically structures of the APIs are not same
I will have to test it myself. Meanwhile just check with the description of the Issue to see that flow works.

@SRvSaha this error is coming after changing public api to find by pin. Though session is not expired still it is showing this

@govindasomani @Tnu02 @520rahul @Suren1978 At the time of Testing, please change the URLs to use findByPIN and findByDistrict as well. Based on user feedback from multiple places, people are telling that findByDistrict usually is used in Telegram as it has near real-time data and doesn't cache.
I am adding the block here:
 "FetchCalenderByDistrictUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/public/findByDistrict", "FetchCalenderByPINUrl": "https://cdn-api.co-vin.in/api/v2/appointment/sessions/public/findByPin"

@520rahul @govindasomani @Tnu02 @govindasomani @Suren1978 Guys, sorry you won't be able to test the findBy APIs. There are some difference in the response structure of calenderAPIs and findAPIs.
So, ignore the testing of findAPIs. Just do the testing as per the Issue description in Peak Hours in Live Scenario.
Need changes in Code for intergation of findAPIs
Thanks @520rahul for pointing it out

Also, a request to all those who haven't starred the Repo. Please give it a star so that it will be easily available in Github Search and together we can help out to more people!
P.S: I don't get any benefit for having more Stars, it's just for the community to reach out to more people.

@Tnu02 @520rahul @Suren1978 @govindasomani Guys need your feedback on the following:

Is the current description working? We need to test it and then I will make changes and release v5.1.1 where these things will be taken case automatically.
What I am planning to do is: By Default after OTP verification all searching will be based on Public APIs and then Booking will be tried using Protected APIs

The description is perfect. Need to test it in a live environment when slots are releasing. Conceptually though, there seems to be no problem with the flow.

Agree with @govindasomani

@govindasomani @Tnu02 @520rahul @Suren1978 Okay cool. Let's wait till tomorrow 8 pm, since most bookings come from 4pm to 8 pm. See if you can do the testing and tally the results will Telegram/other realtime notifiers if we are getting the slots in correct time. And then is booking successful. If these things are okay, I will make the changes and release by EOD around 11 pm when traffic is low. Your support and comment please?

Sure. Will keep you posted on the experience.

@SRvSaha Just tried in a couple of locations. The public API did not detect the slots till much later, even though the telegram notifications had come for the same location. By the time I changed to protected API basis the telegram notification, the slots were booked. Will continue testing for a few more locations where I know the timing of release and revert if this pattern continues.

@govindasomani Thanks for the feedback. Yeah, I guess Telegram Alerts are based on findByDistrict API. As per many threads, that has near real-time data. Unfortunately, due to different structure of API response for findAPIs wrt calenderAPIs, we won't be able to port it as is. Need changes.

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

Please tally the Notifications of slot availability from these Telegram channels. They are usind findAPIs.
https://covialerts.in/ (Claims faster than U45)
https://under45.in/
@govindasomani @Tnu02 @520rahul  @Suren1978

@SRvSaha brother i was wondering if is this possible that u make 2 exe files one operates on public api and other one on protected.  The exe of public api wil run continuously and will find out the slots.  And on the other hand we will be logging in every 15 min in protected api exe but call will be only made after we hit enter/manual cal, not automatic cal with 15 min token expiry warning. Do u think this kind of repo possible.

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

Please tally the Notifications of slot availability from these Telegram channels. They are usind findAPIs.
https://covialerts.in/ (Claims faster than U45)
https://under45.in/
@govindasomani @Tnu02 @520rahul @Suren1978

Just booked a slot basis U45 notification... the public API did not detect it at all even after the booking. I switched to true immediately on seeing U45's msg, and got hit on the 1st refresh.

I have tried this method, but due to difference between data of protected api and public api, when I use public api for finding center it shows "XYZ" center, but when I tries to use protected api for booking it does not shows "XYZ" center at all. I am able to book 2 times but it was different centers and due to sher luck. If I had searched for specific pincode or center I will not be able to book as per this method.

I also tried checking with IsToBeUsed": false and it just keep on searching thou the slots are available, and as soon as i closed and changed it to true, slot got booked.
One more thing i have noticed is that slot are showing via exe but not on the cowin website (got notification thru U45) but how come it was not visible on the website and later showed as booked. I checked with mobile and exe.

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

Bro i dont think so ...once i entered OTP and exhausted with 10 tries...i just delete the authToken file and immediately re run the exe..it is asking for OTP again and gives 10 tries again ....this repeated process i tried for five six times and it worked...but we have to enter OTP again n again to get 10 tries....this all process i done on same IP

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

Bro i dont think so ...once i entered OTP and exhausted with 10 tries...i just delete the authToken file and immediately re run the exe..it is asking for OTP again and gives 10 tries again ....this repeated process i tried for five six times and it worked...but we have to enter OTP again n again to get 10 tries....this all process i done on same IP

I think if this process can be automate in application then it will work fine.....only hurdle is we have to enter OTP again n again

https://quickslot.in/
this is a cowin watcher app and this link helps to find the slot availability other than telegram....you just run n forget.... it automatically refresh and gives alert for slot availability ....just run on side window and as soon as an alert knocks just try our exe

I just confirmed the limits, the whole cowin system is changed. Now, one can have only a maximum of 20 requests per session, if one goes more than that which means if one makes 20 requests in a row one will be logged out. Besides this, there's an overall boundation of 100 requests per 5 mins. So, which means if one re-login and make more than 20 requests and one repeat this thing within 5mins (20*5) = 100 requests in 5 mins (with the same IP) One will be blocked again

Don't try for slot searching, try for booking only. I am not a technical person . It might work .

I just confirmed the limits, the whole cowin system is changed. Now, one can have only a maximum of 20 requests per session, if one goes more than that which means if one makes 20 requests in a row one will be logged out. Besides this, there's an overall boundation of 100 requests per 5 mins. So, which means if one re-login and make more than 20 requests and one repeat this thing within 5mins (20*5) = 100 requests in 5 mins (with the same IP) One will be blocked again

You can use VPN to change IPs frequently ....but to get 10 tries again n again you have to enter OTP again n again ...if his is automated and as @520rahul said make it optional to search for slot on manual basis ...it will be more helpful to book slots

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

Bro i dont think so ...once i entered OTP and exhausted with 10 tries...i just delete the authToken file and immediately re run the exe..it is asking for OTP again and gives 10 tries again ....this repeated process i tried for five six times and it worked...but we have to enter OTP again n again to get 10 tries....this all process i done on same IP

There is noissue of same IP .....I have tried more then 10 times with different OTPs after deleting authToken file ...it is working fine and given 10 tries each time

@SRvSaha brother i was wondering if is this possible that u make 2 exe files one operates on public api and other one on protected. The exe of public api wil run continuously and will find out the slots. And on the other hand we will be logging in every 15 min in protected api exe but call will be only made after we hit enter/manual cal, not automatic cal with 15 min token expiry warning. Do u think this kind of repo possible.

Hi @520rahul, the point you have raised is valid. I am trying to automate the part that you have mentioned from the same Application. Planning to switch between find* APIs of Protected and Public as per the Rate Limit and Refresh Rate. Thanks for your feedback.

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

Please tally the Notifications of slot availability from these Telegram channels. They are usind findAPIs.
https://covialerts.in/ (Claims faster than U45)
https://under45.in/
@govindasomani @Tnu02 @520rahul @Suren1978

Just booked a slot basis U45 notification... the public API did not detect it at all even after the booking. I switched to true immediately on seeing U45's msg, and got hit on the 1st refresh.

Yes, got it @govindasomani Actually after lots of research figured out that they are using find* APIs. Our by default calender APIs won't work due to caching. So I will fix this to let it work using Protected APIs if Possible. When it breaks, we will switch to public find* API. In that way we will circumvent the issue. Only problem will be that we are going to be searching only for the next day. Glad that you could still book.

I have tried this method, but due to difference between data of protected api and public api, when I use public api for finding center it shows "XYZ" center, but when I tries to use protected api for booking it does not shows "XYZ" center at all. I am able to book 2 times but it was different centers and due to sher luck. If I had searched for specific pincode or center I will not be able to book as per this method.

Yes @deepgandhi the Public and Private Calender APIs have the issue with caching, we'll shift to find* APIs

I also tried checking with IsToBeUsed": false and it just keep on searching thou the slots are available, and as soon as i closed and changed it to true, slot got booked.
One more thing i have noticed is that slot are showing via exe but not on the cowin website (got notification thru U45) but how come it was not visible on the website and later showed as booked. I checked with mobile and exe.

Actually there may be some difference in timing of showing the slots in website vs our app. Because we don't need to deal with lots of UI jargon, we're lightweight hence whenever slots come, we'll get it faster. Now coming to the point that U45 got early notification, I am guessing the reason being usage of find* APIs. As per the community concurrent, those have either no or very minimum caching level.

Can you explain find* API @SRvSaha ?

find* APIs: findByDistrict, findByPIN @deepgandhi

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

Bro i dont think so ...once i entered OTP and exhausted with 10 tries...i just delete the authToken file and immediately re run the exe..it is asking for OTP again and gives 10 tries again ....this repeated process i tried for five six times and it worked...but we have to enter OTP again n again to get 10 tries....this all process i done on same IP

True, even I experienced the same. The OTP they send has validity of 3 minutes but usually you can get OTP before that as well.
Also, yeah the issue of deleting and re-entering is tedious. We'll try to fix this.

@govindasomani @520rahul @Tnu02 @Suren1978 I see a flaw in the Process. Let's say, we are able to identify that slots are available using Telegram Notifications or Public API (findByAPIs after integration). Even after that, there may be let's say 3 Centres where slots are available. And assume each center has 4 slots. So overall there are 12 booking attempts we need to make. However, since we would need the ProtectedAPI where refresh limit is 10, we will get stuck up after the 10th Request if we aren't lucky enough to get the slot booked in the first 10 attempts. That's a gamble. How do we go about that? Any thoughts?
So far I saw in discussion threads, basically after 10/20 attempts, CoWIN Portal forcefully logouts the account. Now, the interesting part of the puzzle is, will they allow a new OTP if say I get blocked after 10 attempts. If they are allowing then, we can handle the scenario by regeneration of OTP, validating it and then proceeding as usual like we do in case of Session Timeout in case of Booking or say Searching. That logic is fine. Only thing to research about is, whether they are issuing OTPs or not. I feel that they might issue the OTP since we will login only once with OTP and then rest of the things will be done using Public APIs. Not sure though. See if you can find any proofs or this.

They are allowing renewed OTP after 3 mins from previous one. So effectively, you will have to keep a higher refresh rate to avoid getting blocked within 3 minutes.

Bro i dont think so ...once i entered OTP and exhausted with 10 tries...i just delete the authToken file and immediately re run the exe..it is asking for OTP again and gives 10 tries again ....this repeated process i tried for five six times and it worked...but we have to enter OTP again n again to get 10 tries....this all process i done on same IP

I think if this process can be automate in application then it will work fine.....only hurdle is we have to enter OTP again n again

There is a chance that they might blacklist your number if so frequently OTPs are requested. Haven't see this happening but might happen. We'll keep the Automation part for v5.2.0, as of now we need to focus on fixing the existing issue to overcome the hard refresh limit.

@SRvSaha I have already tried it, actually before using your application I has made a
Python script, bare minimum. I was using find* API. But I too faced the same issue of request limits.

@SRvSaha I have already tried it, actually before using your application I has made a
Python script, bare minimum. I was using find* API. But I too faced the same issue of request limits.

The request limits of 100 requests/5 mins will still be there. The hard limit of 10 requests is the main concern here which should get solved. Are you saying it has the hard limit of 10 requests as in the calender APIs as well ? can you please cheeck by running your script now

I just confirmed the limits, the whole cowin system is changed. Now, one can have only a maximum of 20 requests per session, if one goes more than that which means if one makes 20 requests in a row one will be logged out. Besides this, there's an overall boundation of 100 requests per 5 mins. So, which means if one re-login and make more than 20 requests and one repeat this thing within 5mins (20*5) = 100 requests in 5 mins (with the same IP) One will be blocked again

You can use VPN to change IPs frequently ....but to get 10 tries again n again you have to enter OTP again n again ...if his is automated and as @520rahul said make it optional to search for slot on manual basis ...it will be more helpful to book slots

First attempt would be to go with manual OTP and fixing the issue with the hard refresh limit. Once that is done, we can see how to efficiently do Auto OTP

@SRvSaha in my opinion if u make changes in exe and after login make it optional to search for slot on manual basis (like hitting enter whenever slot comes by getting notification on telegtam) insteqd of automatic basis that would may work

Yes that would be a work around that we leave the finding part and focus on only the booking part. But however issue what happens is the slots get booked from the time notifications are received to the time booking is attempted (includes time for OTP as well)

Guys, this is what is on my mind:

Try to search for slots based on Protected find* APIs
If hard refresh limit is met then regenerate OTP and then use Public find* APIs
Once slot if found, directly proceed for booking using Protected API
In case during Booking, 10+ attempted are made and hard refresh limit is hit, resend OTP as done for Session Regeneration.
Remove the Captcha thing so that time reduces
Also, when searching for slots, somehow sort centers found in Descending order so that changes of booking is higher (usually people attempt for the first one in the list)

I think this flow would work. Shall make the necessary changes and release a new v5.1.1 version. Shall inform once done, please check it out and see if it is working. I will try to do testing from my end.

@SRvSaha I have tried find* API. There is no hard limit of 10, but it stopped giving response of 194, I don't know why such odd number?

@SRvSaha I have tried find* API. There is no hard limit of 10, but it stopped giving response of 194, I don't know why such odd number?

Okay thanks for the confirmation @deepgandhi  I'll check

@SRvSaha I have tried using Bearer token only, I have submitted the merge request, you can check my entire python script there.

@SRvSaha I was able to do more then 500 request using Bearer token in Protected findByDistrict API.

Thanks a lot @deepgandhi. I shall check that. Shall be busy tonight and tomorrow, once I get time shall check it.

@SRvSaha I was able to do more then 500 request using Bearer token in Protected findByDistrict API.

Try the same with findByPIN API as well. Also, tally the difference in response of findByPIN Protected vs findByPIN Public as most of our users use PIN to search rather than district.

@SRvSaha I was able to do more then 500 request using Bearer token in Protected findByDistrict API.

Try the same with findByPIN API as well. Also, tally the difference in response of findByPIN Protected vs findByPIN Public as most of our users use PIN to search rather than district.
If you see that both are almost having same results at the same time, there there is almost no caching and we are good to go. Otherwise we will be in trouble as we faced with calender Public APIs.
@deepgandhi

I will try the same @SRvSaha

I used this application for two days on 4th and 5th June and I haven't been able to login to CoWIN since today evening. It is giving USRAUT0018 error and not generating OTP. I checked today morning and it was working fine. Is it a known problem? Are they blocking numbers which are using automated methods?

I used this application for two days on 4th and 5th June and I haven't been able to login to CoWIN since today evening. It is giving USRAUT0018 error and not generating OTP. I checked today morning and it was working fine. Is it a known problem? Are they blocking numbers which are using automated methods?

@SRvSaha @kukzile me also faced the same issue today.  And i found out many people have also faced the same issue. I think cowin has put blocking period after certain no. Of login on the portal

I found this video on youtube regarding cowin cache.  @SRvSaha can it be useful???
https://youtu.be/hf44_-qqddY

@betagoyal @deepgandhi @kukzile @govindasomani @520rahul @Tnu02 Version 5.2.0 is out now will all the fixes suggested here along with new features for better UX. Thank you all for your patience and support. Check it out and share your feedback!

I found this video on youtube regarding cowin cache. @SRvSaha can it be useful???
https://youtu.be/hf44_-qqddY

May be yes. But since we dropped calender* APIs, it's not going to help us!

I used this application for two days on 4th and 5th June and I haven't been able to login to CoWIN since today evening. It is giving USRAUT0018 error and not generating OTP. I checked today morning and it was working fine. Is it a known problem? Are they blocking numbers which are using automated methods?

@SRvSaha @kukzile me also faced the same issue today. And i found out many people have also faced the same issue. I think cowin has put blocking period after certain no. Of login on the portal

There may be the chance that OTPs are not sent to mobile number for certain time. But I get OTPs ample number of times today. Probably Auto OTP Readers are the reason for this blocking. I tried by best to minimize the requirement of OTP in v5.2.0, see if that helps

I used this application for two days on 4th and 5th June and I haven't been able to login to CoWIN since today evening. It is giving USRAUT0018 error and not generating OTP. I checked today morning and it was working fine. Is it a known problem? Are they blocking numbers which are using automated methods?

https://www.dqindia.com/cowin-otp-issues-arise-citizens-platform-displays-generate-otp-failed-message/

@betagoyal @deepgandhi @kukzile @Suren1978 @govindasomani @520rahul @Tnu02 Version 5.2.0 is out now will all the fixes suggested here along with new features for better UX. Thank you all for your patience and support. Check it out and share your feedback!

Shall check it today. Thanks @SRvSaha

working well...

working well...

Were u able to book slot

yes ....and try now with Rajasthan bundi location

just tried again...working as i need.

@betagoyal Please confirm is the appointment slip is downloaded as well after booking is successful.

just tried again...working as i need.

Plz tell me what refresh rate u put and did u face throttling error any time

just tried again...working as i need.

Plz tell me what refresh rate u put and did u face throttling error any time

@520rahul Let the refresh rate be at default, it will be handled automatically!

just tried again...working as i need.

Plz tell me what refresh rate u put and did u face throttling error any time

yes its downloaded

just tried again...working as i need.

Plz tell me what refresh rate u put and did u face throttling error any time

my refresh rate is 500

i have multiple wifi and i created small bat file for autoswitching in 120 sec

@520rahul Keep refresh rate low only when you are sure of the timing of the slot opening. Otherwise you'll get IP Throttled more frequently, But yeah, when everything is known beforehand, it is better to keep it low.

@SRvSaha I also tried it and working great.. Shall wait to try it in real time..

i have multiple wifi and i created small bat file for autoswitching in 120 sec

Thats cool... :D

i have multiple wifi and i created small bat file for autoswitching in 120 sec

Can u share how to use auto switching

i have multiple wifi and i created small bat file for autoswitching in 120 sec

Can u share how to use auto switching

@SRvSaha @520rahul can i share here...with owner permission ?

@betagoyal Yes you can. Hide all personal info

@echo off
cls
:start
netsh wlan connect ssid="Beta" name="Beta"
timeout 120
netsh wlan connect ssid="Home" name="Home"
Timeout 120
goto start

@520rahul Keep refresh rate low only when you are sure of the timing of the slot opening. Otherwise you'll get IP Throttled more frequently, But yeah, when everything is known beforehand, it is better to keep it low.
@SRvSaha i kept my rate at 2000. It showed fatel error after sometime but automatically again started searching for centres, then after some calls it again showed fatel error and started searching for centres again. Then after again continuously showed fatel error. Can u guide what shud b done when we face such issue and it start again to search for centres after fatel
Error whether v need to close the session

@echo off
cls
:start
netsh wlan connect ssid="Beta" name="Beta"
timeout 120
netsh wlan connect ssid="Home" name="Home"
Timeout 120
goto start

Thanks buddy

@520rahul See if you are exceeding 100 requests/5 mins, you will face Rate Limiting Error. Application will halt for 5 seconds and then again continue. You just keep the App running, it will work. Another way if Set ProtectedAPI:IsToBeUsed: false, that'll forcefully using the Public API to search like Telegram Notifiers. Otherwise it is automatically handled to switch between APIs

@520rahul See if you are exceeding 100 requests/5 mins, you will face Rate Limiting Error. Application will halt for 5 seconds and then again continue. You just keep the App running, it will work. Another way if Set ProtectedAPI:IsToBeUsed: false, that'll forcefully using the Public API to search like Telegram Notifiers. Otherwise it is automatically handled to switch between APIs

@SRvSaha boss i have put intervel  rate after ip throttled to 1 second, still it is searching for centres, whether do i need to increase to 5 seconds or continue using of 1 seconds as it is working in 1 sec also

There is no such exact number. Basically we compute based on your number of PIN Codes what should be the throlling interval. So, in case you are putting some number and that is working, go ahead with it. No issues. I generally keep 2 sec for normal and 1 sec for peak time.

There is no such exact number. Basically we compute based on your number of PIN Codes what should be the throlling interval. So, in case you are putting some number and that is working, go ahead with it. No issues. I generally keep 2 sec for normal and 1 sec for peak time. I usually keep changing this "SleepIntervalInMilliseconds": 3500 to 1000 or 2000
I'd suggest not to change ThrottlingRefreshTimeInSeconds: 5 as this is the cool-off time when IP gets throttled. If IP doesn't get throttled, you can definitely keep it to 1.
Maybe you can keep as 1 and see if you get FATAL IP Throttling error, increase it.
@520rahul

@SRvSaha thanks u so much boss

I used this application for two days on 4th and 5th June and I haven't been able to login to CoWIN since today evening. It is giving USRAUT0018 error and not generating OTP. I checked today morning and it was working fine. Is it a known problem? Are they blocking numbers which are using automated methods?

https://www.dqindia.com/cowin-otp-issues-arise-citizens-platform-displays-generate-otp-failed-message/
https://www.dqindia.com/cowin-displays-generate-otp-failed-usraut0018-errors-citizens-unable-book-slots-second-dose-covid-19-vaccine/
@520rahul @kukzile

https://github.com/cowinapi/developer.cowin/issues/409

@betagoyal @deepgandhi @kukzile @Suren1978 @govindasomani @520rahul @Tnu02 Version 5.2.0 is out now will all the fixes suggested here along with new features for better UX. Thank you all for your patience and support. Check it out and share your feedback!

It is now working like a charm! Thank you for the cool addition of appointment slip download as well...

@betagoyal @deepgandhi @kukzile @Suren1978 @govindasomani @520rahul @Tnu02 Version 5.2.0 is out now will all the fixes suggested here along with new features for better UX. Thank you all for your patience and support. Check it out and share your feedback!

It is now working like a charm! Thank you for the cool addition of appointment slip download as well...

Yup.. I also booked using it and it's blazing fast 😀.. Thanks @SRvSaha for all your efforts.. I really appreciate it...

Glad I could help! Share it with others!

@SRvSaha it worked like a charm. I was able to book 3 slots of neighbours who were trying for more then a month to get a slot. Got their blessings. Thank us so much boss. U rock. God bless u bcoz of u only i was able to book slots. Thanks a ton. 🙏🏻🙏🏻🙏🏻🙏🏻

@520rahul Glad I could help! Please share and help others in booking. This is what we can do for #covid19help by giving back to the community.
@betagoyal @deepgandhi @Tnu02 @betagoyal ^^

@520rahul Glad I could help! Please share and help others in booking. This is what we can do for #covid19help by giving back to the community.
@betagoyal @deepgandhi @Tnu02 @betagoyal ^^

@SRvSaha definitely boss.  Because of u we can help the needy ones who are not technically sound or not have internet facilities.

@SRvSaha sure, I will share with as many as possible. And if they are unable to do themself, I will try to help them by booking for them.

Guys, Check this out https://shawt.io/r/sYK. This is the User Guide Demo Video how to use the Software and the Latest Version of the Software for Windows/Linux/macOS. Might help someone.
@betagoyal @deepgandhi @kukzile @govindasomani @Tnu02 @520rahul @Suren1978 @aman-3003 @AkulRastogi


Not reporting acceptance test failures

Am seeing that acceptance test failures are ignored with a fresh install (ember 2.12.0) of ember-cli-mocha and ember-cli-yadda (separateSteps: true) with<EMAIL_ADDRESS>and upwards<EMAIL_ADDRESS>works ok). Eg, the following test is passing:
// make-a-feature-steps.js

import steps from './steps';
import { expect } from 'chai';

export default function() {
  return steps()
    .then('I should find a file', function(next) {
      expect(false).ok;
      next();
    });
}

Possibly related https://github.com/acuminous/yadda/tree/0.18.0#latest-version

We're having the same problem. @adamjmcgrath did you find a workaround for this?

We downgraded to<EMAIL_ADDRESS>

Completely missed this, I'll look into it.

Better late then never. But it's fixed in master.


Add dotted bottom border for abbr and acronym.

Bug 543307

change https://github.com/jbalogh/zamboni/blob/master/apps/users/widgets.py#L30 to use a span or something that's not an abbr. otherwise, looks okay to me.


Rough edges when reading from stdin

When using PyPrql  to read a set of prql commands from a file, the user experience is a little rough. Or maybe my intuition about how the program should work is faulty (and I am really asking for documentation...)
Here is a sample file and the resulting output. Invoke with: pyprql 'sqlite:///chinook.sqlite' < pq4.prql
# This file - pq4.prql - is for testing PyPrql
# Ensure the chinook database is in the same directory.
# (https://github.com/lerocha/chinook-database)
# Invoke with pyprql 'sqlite:///chinook.sqlite' < pq4.prql

from albums
select title
take 20
;

Here are my observations about the process. Refer to the output (below):

The final blank line in the input file appears to be mandatory. If that blank line is missing, the SQL command won't execute.
There's a warning about stdin not being a terminal. Is this necessary?
There's a warning about an exceptions when handling the comments (leading up to "... SyntaxError('No pipelines?'))
The PRQL parsed from the input file appears to be correct, as is the SQL output
The displayed output (from the SQL query) also seems to be correct
After outputting the result table, PyPrql remains at a PRQL> prompt. I had expected that PyPrql would terminate after it read all the lines of the input file.
There's also a cursor-position-request warning as well.
It doesn't show in the copy-pasted terminal session, but there are some VT100-ish cursor positioning codes displayed in the terminal
I had to hit Ctl-C to abort from PyPrql entirely - otherwise, there are VT100 codes left in terminal.
I also tried typing the commands into the command line (not reading from a file). They seemed to work as expected; typing exitended the program cleanly. Note that typing comments at the PRQL> prompt caused a "no pipelines" error.

√ pqtest % pyprql 'sqlite:///chinook.sqlite' < pq4.prql
Connecting to sqlite:///chinook.sqlite
Warning: Input is not a terminal (fd=0).
PRQL> ^[PRQL> # This file - pq4.prql - is for testing PyPrql
....># Ensure the chinook database is in the same directory.
....># (https://github.com/lerocha/chinook-database)
....># Invoke with pyprql 'sqlite:///chinook.sqlite' < pq4.prql
....>
PRQL:	# This file - pq4.prql - is for testing PyPrql|# Ensure the chinook database is in the same directory.|# (https://github.com/lerocha/chinook-database)|# Invoke with pyprql 'sqlite:///chinook.sqlite' < pq4.prql

Exception when handling the input: No pipelines?,SyntaxError('No pipelines?')
Continuing...
PRQL> from albums
....>select title
....>take 20
....>;
PRQL:	from albums|select title|take 20

SQL:
	SELECT
  title
FROM
  albums
LIMIT
  20

Results:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ title                                    ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ title                                    │
│ For Those About To Rock We Salute You    │
│ Balls to the Wall                        │
│ Restless and Wild                        │
│ Let There Be Rock                        │
│ Big Ones                                 │
│ Jagged Little Pill                       │
│ Facelift                                 │
│ Warner 25 Anos                           │
│ Plays Metallica By Four Cellos           │
│ Audioslave                               │
│ Out Of Exile                             │
│ BackBeat Soundtrack                      │
│ The Best Of Billy Cobham                 │
│ Alcohol Fueled Brewtality Live! [Disc 1] │
│ Alcohol Fueled Brewtality Live! [Disc 2] │
│ Black Sabbath                            │
│ Black Sabbath Vol. 4 (Remaster)          │
│ Body Count                               │
│ Chemical Wedding                         │
└──────────────────────────────────────────┘
PRQL> ^[WARNING: your terminal doesn't support cursor position requests (CPR).
PRQL>

Closing as TUI


Fatal error on terminal job

What this PR does / why we need it:
At the moment, the TaskApply waits for all resources to become healthy. Healthy for a job is defined as Successful. But there are jobs which may never reach that state, as they fail and reach their backOfLimit.
KUDO should acknowledge this and set the task to a FATAL_ERROR so the user gets a feedback and a different job can be executed.
Fixes #1367

I think we should talk about this... I'm not sure if job = complete == health is accidental or intentional... I find it odd

I think we should talk about this... I'm not sure if job = complete == health is accidental or intentional... I find it odd

Yeah, let's have a talk about this later. I think it makes sense in the case of a Job - it either completes or it doesn't. For something like the CronJob, which spawns new jobs regularly, it's more complicated.


docs(cpus): correct default of CPUs usage

Background

In the Readme is stated that the number of CPUs used defaults to 8 which isn't correct, see: https://github.com/tsenart/vegeta/blob/0cabfc957a3db953c27ffaccff3ac2327a0dbcde/main.go#L24
BTW: is the commit message okay or how should I name it?
Checklist

[ ] Git commit messages conform to community standards.
[ ] Each Git commit represents meaningful milestones or atomic units of work.
[ ] Changed or added code is covered by appropriate tests.

This is just the output of running the command in my machine.

But on another machine it would be a different number, so I've updated the readme correctly.


[master] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative-sandbox/channel-wg-leads
/assign knative-sandbox/channel-wg-leads
Produced via:
./hack/update-deps.sh --upgrade --release v0.21
./hack/update-codegen.sh

Details:
bumping knative.dev/eventing c4e9c3b...1c771ce:
  > 1c771ce Change broker spec to indicate brokerclass should be immutable (# 4827)
  > d7cf344 tracing fixed for apiserversource (# 4842)
  > 1efec2b expose ChannelReference in UnknownChannelError (# 4875)
  > 47d7a02 Update deps (# 4874)
  > 47ee8fa Update common github actions (# 4869)
bumping knative.dev/pkg a02dcff...448ae65:
  > 448ae65 Metric unit fixes (# 2018)
  > e38bb89 Update common github actions (# 2017)

/retest

/test pull-knative-sandbox-eventing-kafka-broker-integration-tests

/retest


Add ansible-roster

Looking good!, I am merging this, I have to squash it though, GitLab wont let me Rebase it.
Thank you very much!


Bug: ios_unit_test doesn't work when ios_simulator_cpus = x86_64

What happened?
Under emulator, xctest cannot load tests due to incorrect cpu arch.
2023-03-25 13:17:16.157309+0800 xctest[46694:38247828] The bundle “iOSAppObjCUnitTests” couldn’t be loaded because it doesn’t contain a version for the current architecture. Try installing a universal version of the bundle.
2023-03-25 13:17:16.157367+0800 xctest[46694:38247828] (dlopen_preflight(/Users/xinzhengzhang/Library/Developer/Xcode/DerivedData/proj-eijormkzssexfnfzzduxilzirkiy/Build/Products/Debug-iphonesimulator/bazel-out/applebin_ios-ios_x86_64-dbg-ST-c7ac62f2e810/bin/iOSApp/Test/ObjCUnitTests/iOSAppObjCUnitTests.xctest/iOSAppObjCUnitTests) => false, tried: '/Users/xinzhengzhang/Library/Developer/Xcode/DerivedData/proj-eijormkzssexfnfzzduxilzirkiy/Build/Products/Debug-iphonesimulator/bazel-out/applebin_ios-ios_x86_64-dbg-ST-c7ac62f2e810/bin/iOSApp/Test/ObjCUnitTests/iOSAppObjCUnitTests' (stat() failed with errno=2), '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/lib/iOSAppObjCUnitTests' (stat() failed with errno=2), '/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/Users/xinzhengzhang/Library/Developer/Xcode/DerivedData/proj-eijormkzssexfnfzzduxilzirkiy/Build/Products/Debug-iphonesimulator/bazel-out/applebin_ios-ios_x86_64-dbg-ST-c7ac62f2e810/bin/iOSApp/Test/ObjCUnitTests/iOSAppObjCUnitTests.xctest/iOSAppObjCUnitTests' (stat() failed with errno=2), '/Users/xinzhengzhang/Library/Developer/Xcode/DerivedData/proj-eijormkzssexfnfzzduxilzirkiy/Build/Products/Debug-iphonesimulator/bazel-out/applebin_ios-ios_x86_64-dbg-ST-c7ac62f2e810/bin/iOSApp/Test/ObjCUnitTests/iOSAppObjCUnitTests.xctest/iOSAppObjCUnitTests' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64')))
Program ended with exit code: 80

Reproduction steps

Apply patch reproduce.patch

diff --git a/examples/integration/iOSApp/Test/ObjCUnitTests/BUILD b/examples/integration/iOSApp/Test/ObjCUnitTests/BUILD
index 0c7a86c6..1258ae61 100644
--- a/examples/integration/iOSApp/Test/ObjCUnitTests/BUILD
+++ b/examples/integration/iOSApp/Test/ObjCUnitTests/BUILD
@@ -1,4 +1,13 @@
 load("@build_bazel_rules_apple//apple:ios.bzl", "ios_unit_test")
+load("@rules_xcodeproj//xcodeproj:defs.bzl", "xcodeproj")
+
+xcodeproj(
+    name = "proj",
+    top_level_targets = [
+        ":iOSAppObjCUnitTests",
+    ],
+    ios_simulator_cpus = "x86_64",
+)

 ios_unit_test(
     name = "iOSAppObjCUnitTests",
@@ -7,7 +16,7 @@ ios_unit_test(
         "IOS_APP_UNIT_TESTS": "CUSTOM_ENV_VALUE",
     },
     minimum_os_version = "15.0",
-    test_host = "//iOSApp",
+    # test_host = "//iOSApp",
     visibility = ["@rules_xcodeproj//xcodeproj:generated"],
     deps = [":iOSAppObjCUnitTests.library"],
 )

bazel run //iOSApp/Test/ObjCUnitTests:proj
Command + U or Test any test functions

Expected behavior
Can be interacted with lldb
rules_xcodeproj version
ef0eb8f4189116001846f5579a8bdc0e97a8bab9
Bazel version
6.1.1
rules_apple version
2.1.0
rules_swift version
1.6.0
Additional information
I found how to solve the agent's architecture mismatch problem here in xctestrun.
but same issue for logic test in google/xctestrunner

This is more a problem with Xcode and Rosetta than rules_xcodeproj, right? How would you make a normal Xcode project have this work?
Also of note, with Xcode 14.3, Xcode/Simulator no longer work with Rosetta.

You are right, I tested it and even a normal xcode project has the same problem.
Previously, I modified the compatibility rules of testrunner under the x86_64 arch, so there was no problem in bazel test but in this way I cannot debug the testbundle, which is why I want to use rules_xcodeproj.
At present, it seems that I can provide ios_unit_test with a dummy test_host to bypass this problem. Do you have any other suggestions?


Improve display of executable install errors during uv python install

e.g.,
error: Failed to install cpython-3.13.0-macos-aarch64-none
  Caused by: Executable already exists at `/Users/zb/.local/bin/python3` but is not managed by uv; use `--force` to replace it
error: Failed to install cpython-3.13.0-macos-aarch64-none
  Caused by: Executable already exists at `/Users/zb/.local/bin/python` but is not managed by uv; use `--force` to replace it

we show ~the same message twice. It'd be nice to group these.

Hi, I'd like to work on this. Is there an easy way to reproduce this?


[FEATURE] vmi needs to be displayed in the vm list

Is your feature request related to a problem? Please describe.
If vm is deleted, but vmi still exists, then vmi needs to be displayed in the vm list

vm and vmi exist at the same time, showing vm
vm does not exist, vmi exists, display vmi

Validate version master-95a5828a-head

Create a vm, check the status of vm and vmi at this time

vm and vmi exist at the same time, showing vm

First "kubectl edit vmi vm2, add a "test" to the finalizers field, then "kubectl delete vm vm2"

vm does not exist, vmi exists, display vmi


Search-Elasticsearch-Cxn-NetCurl-6.80: test suite fails (with older Search::Elasticsearch?)

On some of my smoker systems:
#   Failed test 'No body - format'
#   at t/30_Logger/40_trace_request.t line 28.
#          got: '# Request to: https://foo.bar:444/some/path
# curl -XPOST 'http://localhost:9200/xyz?foo=bar&pretty=1'
# '
#     expected: '# Request to: https://foo.bar:444/some/path
# curl -XPOST 'http://localhost:9200/xyz?foo=bar&pretty=true'
# '

#   Failed test 'Body - format'
#   at t/30_Logger/40_trace_request.t line 48.
#          got: '# Request to: https://foo.bar:444/some/path
# curl -H "Content-type: application/json" -XPOST 'http://localhost:9200/xyz?foo=bar&pretty=1' -d '
# {
#    "foo" : "bar\n\u0027baz"
# }
# '
# '
#     expected: '# Request to: https://foo.bar:444/some/path
# curl -H "Content-type: application/json" -XPOST 'http://localhost:9200/xyz?foo=bar&pretty=true' -d '
# {
#    "foo" : "bar\n\u0027baz"
# }
# '
# '

#   Failed test 'Bulk - format'
#   at t/30_Logger/40_trace_request.t line 72.
#          got: '# Request to: https://foo.bar:444/some/path
# curl -H "Content-type: application/json" -XPOST 'http://localhost:9200/xyz?foo=bar&pretty=1' -d '
# {"foo":"bar\n\u0027baz"}
# {"foo":"bar\n\u0027baz"}
# '
# '
#     expected: '# Request to: https://foo.bar:444/some/path
# curl -H "Content-type: application/json" -XPOST 'http://localhost:9200/xyz?foo=bar&pretty=true' -d '
# {"foo":"bar\n\u0027baz"}
# {"foo":"bar\n\u0027baz"}
# '
# '

#   Failed test 'Body string - format'
#   at t/30_Logger/40_trace_request.t line 94.
#          got: '# Request to: https://foo.bar:444/some/path
# curl -H "Content-type: application/json" -XPOST 'http://localhost:9200/xyz?foo=bar&pretty=1' -d '
# The quick brown fox
# jumped over the lazy dog\u0027s basket'
# '
#     expected: '# Request to: https://foo.bar:444/some/path
# curl -H "Content-type: application/json" -XPOST 'http://localhost:9200/xyz?foo=bar&pretty=true' -d '
# The quick brown fox
# jumped over the lazy dog\u0027s basket'
# '
# Looks like you failed 4 tests of 11.
t/30_Logger/40_trace_request.t ................
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/11 subtests
...
Undefined subroutine &Search::Elasticsearch::Role::Cxn::get_user_agent called at t/60_Cxn/30_http.t line 14.
t/60_Cxn/30_http.t ............................
Dubious, test returned 255 (wstat 65280, 0xff00)
No subtests run

This seems to happen if older Search::Elasticsearch (e.g. 6.00) is installed. Statistical analysis:
****************************************************************
Regression 'mod:Search::Elasticsearch'
****************************************************************
Name           	       Theta	      StdErr	 T-stat
[0='const']    	      0.0000	      0.0000	  18.95
[1='eq_6.80']  	      1.0000	      0.0000<PHONE_NUMBER>1837192.00

R^2= 1.000, N= 89, K= 2
****************************************************************

@eserte Thanks for reporting! I'm investigating more. I'll update you asap.

Fixed with #189


Memories sent fix

Fixes a memories_sent assignment part of #1072, part of general effort in #1022

LGTM!


Pub sub dead letter

Allow to define dead letter policy for subscriptions for generated pub/sub resources

Also please fix formatting by running mvn spotless:apply. Thanks

code formatted with spotless plugin


"run at startup" setting doesn't persist after closing settings window

Microsoft PowerToys version
0.35.0
Running as admin
Area(s) with issue?
Settings
Steps to reproduce

Open PowerToys settings
Under General, Toggle "Run at startup" to "On"
Close settings window
Open settings window again

✔ Expected Behavior
"Run at startup" is still On
❌ Actual Behavior
"Run at startup" is Off
Other Software
No response
PowerToysReport_2021-04-06-10-42-10.zip

Similar to https://github.com/microsoft/PowerToys/issues/10400, as PowerToys/settings.json is not persisted to the disk.

Are you still experiencing this issue? /needinfo

I no longer use powertoys so I can't check

I'll close this out for now and then if folks see it again we can reopen :)


[Event Request] codeunit 5816 "Undo Return Receipt Line" - OnBeforeGetCorrectionLineNo

Can we please get the following event?
local procedure GetCorrectionLineNo(ReturnRcptLine: Record "Return Receipt Line"): Integer;
var
    ReturnRcptLine2: Record "Return Receipt Line";
    LineSpacing: Integer;
begin
    //+EVENT
    IsHandled := false;
    OnBeforeGetCorrectionLineNo(ReturnRcptLine, Result, IsHandled);
    if IsHandled then
        exit(Result);
    //-EVENT
    with ReturnRcptLine do begin
        ReturnRcptLine2.SetRange("Document No.", "Document No.");
        ReturnRcptLine2."Document No." := "Document No.";
        ReturnRcptLine2."Line No." := "Line No.";
        ReturnRcptLine2.Find('=');

        if ReturnRcptLine2.Find('>') then begin
            LineSpacing := (ReturnRcptLine2."Line No." - "Line No.") div 2;
            if LineSpacing = 0 then
                Error(Text002);
        end else
            LineSpacing := 10000;

        exit("Line No." + LineSpacing);
    end;
end;

[IntegrationEvent(false, false)]
local procedure OnBeforeGetCorrectionLineNo(ReturnRcptLine: Record "Return Receipt Line"; var Result: Integer; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


refactor: Separate settings out of GlobalFilter

Description
Refactor GlobalFilter to not access or update Settings.
This is a step on the way to making GlobalFilter behave like GlobalQuery.
/CC @ilandikov for info.
Motivation and Context
This is part 1 of #2281

#2281

How has this been tested?

Adding tests
Running all existing tests
Thorough exploratory testing in the demo vault.
I will also work through the smoke tests before merging the PR.

Screenshots (if appropriate)
Types of changes

Internal changes:

[x] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[x] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] My change has adequate Unit Test coverage.

Terms

[x] My contribution follow this project's contributing guide
[x] I agree to follow this project's Code of Conduct

Cyclic dependencies before:
Processed 122 files (1s) (15 warnings)

1) Config/GlobalFilter.ts > Config/Settings.ts > Suggestor/Suggestor.ts
2) Config/Settings.ts > Suggestor/Suggestor.ts
3) Task.ts > Config/GlobalFilter.ts > Config/Settings.ts > Suggestor/Suggestor.ts
4) Task.ts > Config/GlobalFilter.ts > Config/Settings.ts > Suggestor/Suggestor.ts > TaskSerializer/DefaultTaskSerializer.ts
5) Task.ts > Config/GlobalFilter.ts > Config/Settings.ts > TaskSerializer/DataviewTaskSerializer.ts
6) Task.ts > DateFallback.ts
7) Task.ts > Scripting/TasksDate.ts
8) Task.ts > TaskLineRenderer.ts > File.ts
9) Task.ts > TaskLineRenderer.ts > File.ts > lib/MockDataCreator.ts
10) Task.ts > TaskLineRenderer.ts
11) Task.ts > TaskLineRenderer.ts > lib/PriorityTools.ts
12) Task.ts > Urgency.ts
13) Cache.ts > TasksEvents.ts
14) Query/FilterParser.ts > Query/Filter/BooleanField.ts
15) Config/SettingsTab.ts > main.ts

And after:
Processed 122 files (1.2s) (15 warnings)

1) Config/Settings.ts > Suggestor/Suggestor.ts
2) Task.ts > Config/Settings.ts > Suggestor/Suggestor.ts
3) Task.ts > Config/Settings.ts > Suggestor/Suggestor.ts > TaskSerializer/DefaultTaskSerializer.ts
4) Task.ts > Config/Settings.ts > TaskSerializer/DataviewTaskSerializer.ts
5) Task.ts > DateFallback.ts
6) Task.ts > Scripting/TasksDate.ts
7) Task.ts > TaskLineRenderer.ts > File.ts
8) Task.ts > TaskLineRenderer.ts > File.ts > lib/MockDataCreator.ts
9) Task.ts > TaskLineRenderer.ts
10) Task.ts > TaskLineRenderer.ts > lib/PriorityTools.ts
11) Task.ts > Urgency.ts
12) Cache.ts > TasksEvents.ts
13) Query/FilterParser.ts > Query/Filter/BooleanField.ts
14) Config/SettingsTab.ts > main.ts

Diffs:


Unhandled Exception: MissingPluginException(No implementation found for method pickImage on channel plugins.flutter.io/image_picker)

E/flutter ( 3417): [ERROR:flutter/lib/ui/ui_dart_state.cc(177)] Unhandled Exception: MissingPluginException(No implementation found for method pickImage on channel plugins.flutter.io/image_picker)
E/flutter ( 3417): #0      MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:160:7)
E/flutter ( 3417):
E/flutter ( 3417): #1      MethodChannelImagePicker.pickImage (package:image_picker_platform_interface/src/method_channel/method_channel_image_picker.dart:30:19)
E/flutter ( 3417):
E/flutter ( 3417): #2      _MyAppState.openCamera (package:flutter_app/screen/my_app.dart:759:24)
E/flutter ( 3417):
E/flutter ( 3417):
I am getting this error can any one help me with this?

Hi @UjjawalPanchal
Please see if this solve this issue for you, if not, can you please provide your flutter doctor -v,  and your pubspec.yaml.
Thank you

Hi @UjjawalPanchal
Please see if this solve this issue for you, if not, can you please provide your flutter doctor -v,  and your pubspec.yaml.
Thank you

Okay, thanks.

Hi @UjjawalPanchal
Please see if this solve this issue for you, if not, can you please provide your flutter doctor -v, and your pubspec.yaml.
Thank you

Okay, thanks.

Hi @UjjawalPanchal
Please see if this solve this issue for you, if not, can you please provide your flutter doctor -v, and your pubspec.yaml.
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


[🐛 in esl-utils]:  @exadel/esl/modules/esl-utils/misc/object.js#set doesn't support arrays

Doesn't support arrays in the path
@exadel/esl/modules/esl-utils/misc/object.js#set doesn't support array in the path.
Input Code
const family= {};
set(family, 'children[0].name', 'Alex'); // { 'children[0]': { name: 'Alex' } }

Expected behavior/code
const family= {};
set(family, 'children[0].name', 'Alex'); // { 'children': [{ name: 'Alex' }] }

Possible Solution
Will be nice, if it will support 2 variation with(change/replace) and without index(push).

children[1] => { children: [ , { name: 'Alex' }] }
children[] =>  { children: [{ name: 'Alex' }] }

Triaged to Release 3.14.0. (~ 02/21)
Technical notes:
Proposed to be done as an option to the current set utility API:
set(obj: object, path: string, value: any, handleArr: boolean = false): void
Default is the current behavior. The new behavior is optional.
Example:
set(family, 'children[0].name', 'Alex', true);

The current set behavior works just in terms of objects, so array indexes are available in the object syntax, e. g.
set(family, 'children.0.name', 'Alex');

But "foo" is not Array :) :
{
    "foo": {
        "0": {
            "bar":"fail"
        }
     }
}

API:
set(obj: object, path: string, value: any, handleArr: boolean = false): void

I don't see any reasons to add handleArr param. Because if path contains [\d], then we should handle it as array :)

Thanks for the response @dmantsevich !
As I already mentioned, the current set behavior is object-oriented.
So in the case the property is not already defined as an Array, then set will create it as an object, by default.
Another point to consider is that [ ] are valid parts of the object key names. (other words, [0] is a proper object key)
CC: @exadel-inc/esl-core-team , guys, if you feel that we need to reconsider our decision here, feel free to raise this ticket again

:tada: This issue has been resolved in version 3.14.0-beta.4 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Visual Studio option for public signing

I believe the documentation in regards to setting this option via Visual Studio to be incorrect. Doing the follwoing in VS 15.8.1 only triggers the "/delaysign+" compiler option:

Open the Properties page for the project.
Modify the Delay sign only property.

In order to trigger the "/publicsign+" compiler option, the project file must be edited and the "<publicsign>true</publicsign>" property must be set. There appears to be no way to configure this behavior from within the Visual Studio UI itself.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0a7871f3-e680-0424-01fe-9fd91b154275
Version Independent ID: b2f4b5bd-d13b-36b2-a064-9b4d519c4348
Content: -publicsign (C# Compiler Options)
Content Source: docs/csharp/language-reference/compiler-options/publicsign-compiler-option.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

I can confirm this issue. There is no option in the Visual Studio GUI to select public signing. Am running
latest as of today (15.8.4).

Of note, plans to (possibly) add a UI for this switch appear to be tracked in https://github.com/dotnet/project-system/issues/126.
Until then, the entire "To set this compiler option in the Visual Studio development environment" section should be removed, as there is clearly no UI for /publicsign at this point; you have to edit the file by hand (which as of VS 2019 can be done by double-clicking the project).

I think this issue can be closed because the duplicate #18772 was fixed with PR #20047.


Branch hard-coded to main - should use config branch

At first my Checkout step was failing, and then i updated my autopr.yml file with the correct ref
AFter that passed my AutoPR step failed:
Checking out main...
service=commit Traceback (most recent call last): File "/venv/lib/python3.9/site-packages/git/util.py",
line 1095, in __getitem__ return getattr(self, index) File "/venv/lib/python3.9/site-packages/git/util.py",
line 1083, in __getattr__ return list.__getattribute__(self, attr)
AttributeError: 'IterableList' object has no attribute 'main'

i cannot find this in your codebase, but cannot see where else main is referenced

Wow. Sorry. I RTFM but missed this.
https://github.com/irgolic/AutoPR/blob/main/USAGE.md?plain=1#L79


Tests & Documentation

The code is pretty much completely undocumented and untested. This is definitely a part that has to change.

Move to v0.2.0. Allows for easier testing as twisted server won't exist anymore. Also the documentation would be much better.


dataConnectorValidator.ts missing AzureDevOpsAuditing datatype

Describe the bug
An error occurs on the pull request because Native Microsoft tables are not understood by the script.
To Reproduce
Steps to reproduce the behavior:
See links:
Pull Request
Pipeline error
Expected behavior
Default table, ehich is not a custom table in Log Analytics should be accepted.
Screenshots

I've created a Pull Request for this issue with ID: #4738

We are looking into this.

Closing the issue since PR for this (https://github.com/Azure/Azure-Sentinel/pull/4738) is merged


set url user set before

It's useful feature. Please add this feature.
But I din't test because my Version 8.2.1 Xcode can't open your project. sorry.

not yet?

This project already finished??

look at #188 for what I think you want to do :)

@scottwarren Thank you!

I will throw pull-request your project.
I succeeded to build your project.

JadenGeller/Helium is no longer update?
I hope he publish for AppStore.
https://github.com/alexzye/Helium/

Try Helium 3.0.3596.

If I understand correctly, this implements state restoration? If so, I think we should use Cocoa-native state restoration APIs so the app respects System Preferences.


[bug]: error "module 'signal' has no attribute 'SIGKILL'" when running "python scripts/preload_models.py" on install

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
8gb
What happened?
When installing using the 'easy peasy windows install' instructions, on the "python scripts/preload_models.py" step it exits with a "module 'signal' has no attribute 'SIGKILL' "error and exits without downloading anything.
Full text of the error is attached.
edit: I just tried the conda method to install and got the same error at the same step. If that helps.
error.txt
Screenshots
No response
Additional context
No response
Contact Details
<EMAIL_ADDRESS>

You can refer to #1264 , A temporary solution was suggested:

I guess for now users will have to rollback and/or wait for a fix. Or, of course, patch it themselves (you can just find-and-replace signal.SIGKILL with signal.SIGTERM and it should work).

I managed a workaround using information in the thread linked by @FreeBlues
changing these lines in environment.yml

dependencies:
  - python>=3.9
  - pip>=22.2
  - cudatoolkit=11.3
  - pytorch=1.11.0
  - torchvision=0.12.0
  - numpy=1.19.2

and in requirements-lin-win-colab-CUDA.txt changed:
torch==1.11.0
--extra-index-url https://download.pytorch.org/whl/cu113

then rebuilt the environment with:
pew new --python 3.10 -r requirements-lin-win-colab-CUDA.txt invokeai
seemed to do the trick.

@tildebyte and @blessedcoolant , can you advise whether this workaround should be committed? I'm reluctant to make any substantial changes to the dependencies files.

🤷 My long-running environment has torch==1.12.1+cu116 and I have no issues. I just re-ran the preload script and likewise it's fine.
TL;DR - we probably should pin torch, but I don't think we should go back as far as 1.11+cu113

The current environment.yml file fixes this bug. You need to do a conda update. The requirements.txt file for the easy Peasy install needs updating. Look for a pr