Dep Ensure Not Working Following New Computer Install From Git - go

I just finished up my first big project for a software engineering company, but when I tried to install the code on my personal computer tonight I am having trouble with Go. I set up my GOPATH and GOROOT and things seem to be okay. Here are those:
Everything worked GREAT today on the work computer, but now its just a pain. I'm getting all kinds of errors, but the biggest is that it "cannot find package." It is also giving me an error for "use of internal package not allowed" when it worked just fine on my work computer. I worked primarily in the front end so I'm a little ignorant on the subject, but I texted a co-intern and he didn't know either. I am thinking its my Go installation.
We used dep ensure for the dependencies and it is looking in the wrong place. for the vendor files. Here is an example of the file structure:
I would LOVE some help with this because I was so excited to show this thing off we worked so hard on, If anyone is interested here is the GitHub link!
https://github.com/acstech/doppler-events
Thank you everyone!

Related

Xamarin.Forms.DefaultItems.props Not Found

So, I have been trying to fix this error I am getting over a month now, but with no success. I am currently working on a personal app project in collaboration with one other friend and surprisingly the project compiles perfectly fine on my friend's machine.
I am getting the below error:
"The imported project "C:\Users\divye\Documents\NHSF Xamarin App\packages\Xamarin.Forms.2.5.0.280555\build\netstandard1.0\Xamarin.Forms.DefaultItems.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk".
I can't understand why my code will not compile. I have gone through lots and lots of Stack Overflow posts already and tried pretty much all the proposed solutions without any success. As a last resort I am having to post on here.
I have tried the following:
Deleted the project locally from my machine and re-cloned the git repository and then tried running the project
Cleaned the project out and tried rebuilding again
Have spoken with my friend who is also working on the project, and matched my local project set out to his
I have gone into the Xamarin.iOS and Xamarin.Android .csproject files and also manually added in the Import statement for 'Xamarin.Forms.DefaultItems.props'
I have manually checked the folder '$..\netstandard1.0\ folder path to make sure the 'Xamarin.Forms.DefaultItems.props' file physically exists in the folder and it does for both iOS and Android.
Updated all packages in Xamarin Studio for the project to make sure latest versions of the packages are being used
Downgraded the Xamarin.Forms package to see if it could be to do with a bug in the latest package but this does not seem to be the issue.
A suggested fix that worked for my friend was recreating the project to contain the ASP.NET backend for mobile packages. I have tried this as well.
I was initially getting the error on my Mac so I thought I would give it a go on my Windows machine. Same thing happens on there too.
I am stumped at the issue. It is failing to build at all. Neither iOS or Android work.
I am hoping someone from here can help.
Thanks,
Divyesh!
Remove the whitespaces in the pathname of the project!

macOS project failing on runtime

So I have an xcode project that fails every time I run it on my computer. Works on other computers though. I get the following error:
dyld: Library not loaded: /System/Library/PrivateFrameworks/Swift/libswiftCoreFoundation.dylib
Now, when I look in /System/Library/PrivateFrameworks/Swift/ I can't find the libswiftCoreFoundation.dylib file. But other swift projects work just fine. I have no idea how to fix this. I've tried cleaning, restarting my computer, creating a copy of the project, updating Xcode, updating command line tools, everything I could think of.
The project was working just fine a few hours ago. Something went wrong by itself. No clue how to fix things.
After spending 6 straight hours debugging and trying to fix things, I found the solution. For some reason, my "Library Search Paths" was filled with the wrong directory. I never set it to that directory. But it was set.
Here is what I mean:
The highlighted field was filled with the following: macosx/System/Library/PrivateFrameworks/Swift
I just took that out. I hope this helps save some future traveler the pain and torture I went through

Build or Compile Webkit on Windows7 64bit

I'm trying to just build webkit on windows. As usual I started with webkit site and trying to get developer tools setup. I'm struck basically at the cygwin Installation itself.
The cygwin-downloader gets all the packages and runs the setup normally.
As per the installation instructions, I selected the Install from Local Directory Option (cygwin install and source package directories are different).
There was some initial turbulance in finding the packages, somehow i could let it find the packages. The screen looks like this now.
I selected the packages (all) and then proceeded with next. It just ran very fast and exited saying nothing needs to be installed. It looked like this.
After I ran the cygwin shorcut from the desktop its shouting something is missing.
I don't understand what am I missing here. Also at some link it says we need a port to build webkit. If thats the case, how does anyone port webkit to their applications without building the webkit alone?
I know this is not a programming question. but this will help most of the people who are taking baby steps in understanding and build WebKit. Thanks!
According to this, it's seems a cygwin-downloader's bug.
However, there is a workaround...
Just copy {cygwin-downloader}\setup.ini file to a {cygwin-downloader}\x86\ directory. Then reopen setup.exe. It will show you a package list without turbulence. You don't need to click all from the package list. Just click Next.

Red5 demos don't work

I just installed red5 on my server, and the install seems to work fine. As you can see here: http://onelifemedia.com:5080
I got this far by using this walkthrough: http://www.webhostingtalk.com/showthread.php?t=1046590
The /demos page gives me a 404 error. So I logged onto the server, and checked to see if the "demo" directory was already there. It was not.
The applications that I installed were a directory up from the root directory. I'm not sure if this is right or not.
Either way, my end goal is to actually get something working besides the main page. If I can get the demos to work, then hopefully I should be well on my way.
I guess my questions can be broken down like this:
Does anyone know how to get the demos working?
Should I forget about the demos, and try to start writing my own code?
If I should write my own code, how should I go about installing it? Since the installer is not properly installing the demos.
Thanks
The tutorial is good but you dont need the admin app. Use the installer link in the tutorial and install the demo you want to use. The content of the "demos" directory is only the swf files used to access the server demos which you use the installer app to install. For instance , select "oflaDemo" and then from the main page navigate to demos/oflaDemo et voila.
I know I'm biased being a core developer, but we've attempted to make the server as ez as possible to use.
I could install demos from the latest svn trunk, Checkout the source, use ant&ivy to build and run the server and you can install two sample apps(oflaDemo and SOSample).
You may need to use ivy commands resolve some of the common issues during installations.
E:\dev\red5\java\server\trunk>ant ivyclear dist
()Red5 user mailing list may help you, because this is not exactly problem with Red5 source.
()http://stackoverflow.com/questions/11156222/red5-demos-not-working/11935532#11935532
I could resolve the issue based on the information in Red5 users mailing list and comments by Mr.Mondain in one of the posts in Stackoverflow

How do you know who is fixing the build?

We are working in a CI environment, with Enterprise Cruise running our builds. Developers all have CCTray installed locally to notify us if a build breaks.
CCTray has a menu option Volunteer to fix build that you can use to let your team know that you are fixing the build. However this doesn't work in our environment (reasons: Fix build not currently supported on projects monitored via HTTP).
So the question is - does anyone have a technique that they use in their team that allows someone to indicate that they are fixing a broken build?
For me, Continuous Integration is not only about tools, but also about practices. One of them is the responsibility. In others words, the one who breaks the build is also the one who will fix it!
Shooting "I take it guys" is my prefered. ( in addition of the responsability romaintaz describe )
We send an email to the Developer's mailing list to let everyone know you are taking ownership of the build break.
We're co-located, we all run cctray, and when the build breaks we have an audio alert (red alert from the Starship Enterprise). When it breaks we all shout "who broke the build"! Once we figure out who broke the build we harhass them until they tuck their tail between there legs, do that stupid embarassed laugh, and volunteer to fix the build.
It's worth noting that things that aren't monitored by the build and tests can change on a CI box. For example: maybe someone went onto the box and changed a permission. Then when the next checkin is made it looks like the person that made the checkin broke the build when really it was the person that made the manual change without telling anyone.
On the volunteer thing, tools can help but verbal face to face communication is still king.
The onus is usually on who broke the build with their checkin. That's often obvious, even with multiple checkins from different individuals. After that there's a bit of negotiation if the build remains broken. Not particularly scientific or rigorous, but it seems to work.
If the build brokes, then in CCtray there is an option for "Volunteer to fix the build".
And it tells automatically to all the developers who is fixing the build

Resources