I have no idea about this.
I thought it was because of source verify in etherscan, but it wasn't
Related
I want to learn more about sketchapp to build a plugin for it, I was looking at the JSON files we can extract from a project and i noticed all the "classes" (i look them up and they show up as headers) tagged in it like: "MSRect", "MSColor", "MSExportOptions", etc.
I've looked at the sketchapp developer webpage, and some forums and i found some mentions to this classes but i couldn't get anything usefull at basic level.
The question would be, where i can find information about what are those classes and what they do?
Thank you.
https://github.com/abynim/Sketch-Headers, here I could find all the information i needed about this "classes", some one took the time to use the dump command to get all the information ( Methods, properties, etc.), and upload it to github.
This files took some time to understand and manage, but they solved all the problems i had with the creation of my plugin for Sketch.
I can't get rspec to work. I did the first level on codeschool, only i followed on my own computer, and it worked fine (had to change should with expect). But now it suddenly stopped doin it thing.
I'm not sure if I did anything to make this happen.
I know this probobly isn't sufficient to figure out whats wrong, but do anyone have a clue, or know where I can fix this.
I'm a novice in this so go easy.
Thanks.
Rspec is telling you that it can't find the specification file you're trying to run. Can you confirm that calc_spec.rb exists in the folder c:/King Kong/Desktop/the_odin_project/rspec?
(Please include code/output samples as text, not images, for ease of reference.)
If your writing a go command (not a package) that is large how do you layout its internals? I would love to have some utility packages etc but not have those exposed for anything except the command's code. If it's all in the same repo I don't see whats stopping someone from importing those internal use packages.
You might make your utility packages internal to your package — like this. This won't prevent anyone from using them but a) why would you care anyway? b) the package's structure would give a clear hint on that these "subpackages" are internal to the project.
The answer is simple (but most probably not what you'd like to hear): Do whatever you like and is allowed. Having utility packages living somewhere is perfectly fine, either in the same repo as a "sub-package" or in a different repo.
Regarding
I don't see whats stopping someone from importing those internal use packages
Why do you care? If the packages encapsulate distinct and usable functionalities someone might benefit from importing them. Keeping those function together with the command does not "protect" them in the sense of "nobody should be able to look at my code". Just make it clear in the docs that you'll feel free to do incompatible changes at any time. Go is not about preventing each and any stupidity and protecting the lazy and incapable ones who deliberately ignore any documentation from shooting their foot.
LuaInterface uses two .dlls: lua51 and luanet.
While being able to rebuild lua51 to liblua5.1.dylib (and code actually found all necessary entry points) im completely stuck with luanet.dll.
Does anyone have an idea how to build it on Mac OS or if I have to avoid using it entirely (at cost of losing such stuff as ObjectTranslator and MetaFunctions)?
I already know that there are alternatives like http://github.com/jsimmons/LuaSharp.
You need to configure your DllMap to tell it that luanet.dll should be looked for at lua51.dylib
http://www.mono-project.com/Config_DllMap
My team uses the Radiator View plugin for Jenkins for fast feedback on the build status of a few different projects. One thing we discussed that would be helpful is if the SVN revision number were included in this view. After only a quick Google search, I haven't found a clear answer on whether this plugin is configurable or not; does anyone know if there's a straightforward way to add this information?
I dont think there are customizable figures there but what you can do is, pull down the source and get the revsion numbers for all the failing builds, you will have to write the code yourself, but from what I can see there is no way of doing this with the configuration options.
What you might want to try if you just need to get that information is the recent changes on the build page of the recently broken build.
Goodluck.
Can I ask why it would be helpful to have the svn revision number on display? As far as I understand it, a build radiator is supposed to 'radiate' meaningful information into the room. The svn number is fairly meaningless unless you can look up the number in the repository, in which case you could have just looked up the revision number on Jenkins anyway.
I'm just guessing, and do correct me if I'm wrong, but I suspect that your real desire is to have some way of quickly working out who might be responsible for a failing build. If this is the case, then processing check-in comments and displaying pictures of the users involved is a far more effective way of getting developers to react to failing builds. I've experienced this first hand at my company.
With this in mind, I have developed a standalone build radiator webapp that talks to Jenkins over its REST API. CI-Eye is trivial to set up, and will probably give you better results in the workplace than the Radiator View plug-in. Give it a try, and let me know what you think -- I'm quite actively improving it, and welcome any feedback.
CI-Eye is free and open source -- see the CI-Eye wiki for more details.