Yaswanth Mangalagiri

  Django   deployment never fails unless it is at the Database drivers. The required version of mysqlclient isn't found. is the common error you get in  Amazon Web Services  server logs If you are here after reading my pervious post then you must have wasted days while deploying your  Django  app on ElasticBean The only reason of failure could be the installion of the mysql drivers. The regular DB driver that django installs or in your requirement.txt file is mysqlclient You try the below mysql Drivers:  mysql-python mysql-connector-python For my app  mysql-connector-python worked. Go through this site https://dev.mysql.com/downloads/connector/python/

There is always an issue with  Amazon Web Services  ElasticBean while deploying applications and always a scary part. It was a cakewalk on Heroku hosting platform but it's nightmare here and wastes days  The Rails Application   use Puma as default server, recently it has updated to 5.2.2 at the time of writing this post. During the recent deployments to AWS elasticbean all have been failing, The main reason is the Gem File isn't being obeyed.  The specified version of the Puma isn't being instaled by the AWS serves when  A revolution for server I decided to go back to Django again. You can read this post to encounter what all I encountered duint the deployments of Django Application. So going back to Rails. Everything has been installed properly except the Puma server.  I specified 4.3.2 in my Gem File but AWS was installing the 5.2.2. And all the Load Balancers have been showing the status of 502 or 400. The Server health is shown as degraded or ...

https://codingcompetitions.withgoogle.com/codejam/round/000000000043580a/00000000006d0a5c          

Solution to Google Code Jam 2021 First Problem Moons and Umbrellas   Problem can be found here  https://codingcompetitions.withgoogle.com/codejam/round/000000000043580a/00000000006d1145

  Bug Bounty has become the bread and jam for many developers and it is getting tough since the year 2014. Only the hackers with deep research can get through it and those who find XSS in a intellectual way get paid. If you find and IDOR bug they defininetly say it is already know or there are changes or it is an intentional and works as expected. But what's the truth  no one knows or they wantedly close the report. Find a bug which is difficult to exploit by others. The more easy the bug the more easy it is for them to get it rejected and throw nothing at you. But if it is more difficult to reproduce. It would be tougher for them to Reject the report. I have found pretty easy bug and it was told that it is working intented or either they marked it as duplicate.. The truth..??? No one knows. Either they wantedly marked as duplicate just to escape the payment or just it is easy and anyone can find it.

  In the Settings  of YT Studio.  The Community tab has Advanced Filters  tab, that lets you enter the "Blocked Words".  For example if you enter the word "Hello" and save. Enter the Hello in different styles like "HElLo", and it gets Held for Review. But if you append an emoji it could bypass the filter at the server  and goes for review and gets displayed in the the comment section.

  In the Facebook Page General settings, the section " Page Moderation " allows you to input a list of words that never gets displayed if someone enter them in the comments. But when a Page manager, it may be an analyst, Advertiser enter those words It gets shown in the comments.  Keeping the page managers at risk of their names getting disclosed in the comments section of any post.