cant verify smart contract on bscscan - smartcontracts

i have created and deployed a smart contract on BSCScan:
https://www.bscscan.com/address/0x363baC78013aA9Bc546597e5059943Eedb2D0cBb
i used the code from openzeppelin:
https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/token/ERC20/ERC20.sol
for some reason i keep getting errors. i have limited experience with smart contracts but i have tried everything: flattening the code, removing the imports and replacing with code, hardhat, truffle... i can not figure out what i am doing wrong.
i would really like someone to explain to me where i am going wrong or even point me in the right direction.
thank you :)

Related

What does the label "triaged" mean on TensorFlow issues?

I'm interested to make some contributions to TensorFlow in future. I saw that some labels have "contributions welcome" and "triaged" at the same time. Can someone explain to me what "triaged" means?
https://github.com/tensorflow/tensorflow/labels/triaged
That's part of our internal process, to help us make sure we look through all of the Github issues that the community submits. Having the label is an indication that we've seen the issue, and usually means we've marked it as something we'd welcome help with, assigned it to a team member to be worked on, or taken some other action to handle it appropriately.
Does that help?

How can understanding logs help a tester?

I am an automation + manual tester. I would like to understand the reason how understanding the logs of an application(which i am working on) help me in improving my testing skills.
By viewing logs you will get some ideas about the error, if it is data level fix you can release and fix directly without dev team help.
In Java some times Runtime exception will occur, it will not convey messages to you in the interface about the exact problem. By viewing log you can get some ideas about the Runtime exception.
You see, I am really new into android, but the reason logs are important is because they can help you track down issues, such as Java.NullPointerExceptions and can help you trace back to where the issues were. I think there is also a way to create an error dialogue in the log, which can tell you that an error occurred. This is particularly essential in debugging, where you need to solve a problem in your app. I hope this helps, and best of luck. I think you can search up how to write stuff into a log at certain areas. I think the way on how to Log is to access Log class. http://developer.android.com/reference/android/util/Log.html

Microsoft.VisualBasic.Compatibility.VB6.GroupBoxArray' is obsolete

I was converting VB6 to VB.NET and now I came across this warning.
I made research before and the result is comment relate statement then add new code if necessary. it is so far so good until I faced an others problem that after comment.
I commented obsolete warning but it made AxMSFlexGrid Array.AxMSFlexGrid Array.GetIndex not found(I got 7 warning about this). The problem made the design view can not show fully which just like the following picture. http://chanmingman.files.wordpress.com/2011/06/couldfindtype.jpg
But no longer, I don't know what happen or what have I done, it gone.
I want to know why. Anyone came across this situation like that?
It is obsolete in .Net 4. That means it works now, but it might be removed in future versions of .Net. You should probably just leave it, since you are having trouble understanding the code.

Missing proxy for identifier IBFilesOwner

We've got an application that on rare occasions crashes with the error:
Missing proxy for identifier IBFilesOwner
We understand it to be implying that it can't find File's Owner for one of our nibs (xibs) but we've been through and confirmed they all have valid ones set.
There's practically zero on Google, can anyone offer any suggestions?
Thanks.
Hey I had the same problem and it turned out that I was doing some threading and I was executing code that should be on the main thread on another thread.
I don't know what you're doing in your app, but hopefully that might give you a clue.
If you share some code we can try and figure out what's going on.

COM/OLE, Old code and Headaches

I'm currently living in 90's and I've been handed this piece of legacy code. I'm not knowledgeable when it comes to COM/OLE/MFC/ATL so I'm asking this, hoping that someone with experience from way back then, could help me to track down this issue.
What I have is this really old/legacy MFC/ATL application.
It launches, but eventually crashes in CFormView::HandleInitDialog (atlmfc\src\mfc\viewform.cpp)
The debug output I get is this:
CoCreateInstance of OLE control {6A24B340-7634-11D3-A5B0-0050044A7E1A} failed.
>>> Result code: 0x80040154
>>> Is the control is properly registered?
I know as much that this is due to some component registration failure, or resolution but what I do not know is how to figure out what this dependency is, I have a working old executable of the code, and maybe I could use a bit of reverse engineering to figure out if any DLLs are missing, but I really don't know, I have know idea what OLE is, and I would really appreciate some help on how to debug this.
that looks like it is dxDBGrid.dll. OLE is just Object Linking and Embedding. You need to find the dxDBGrid.dll and make sure it is registered. you can use regsvr32 to register it.
explanation of regsvr32