Telepresence Commands Pop Up an Ambassador Clouod Login Window - telepresence

For some reason, when I run some Telepresence commands, I get a browser window popping up prompting me to log in to Ambassador Cloud. But I'm not using Ambassador Cloud.
In addition to the browser window, the command shows a message to this effect. Like this:
~ % telepresence intercept my-k8s-service
Launching browser authentication flow...
How do I disable this?

I just figured this out -- there are some advanced options you can set by creating a config.yml file for telepresence. Its expected location varies by OS, see the chart here for all supported locations per OS: https://www.getambassador.io/docs/telepresence/latest/reference/config/
The setting we want, which I just tried and worked to disable opening the browser window, is:
cloud:
skipLogin: true
I am on a Mac, and these are the steps I took to fix the issue:
Create the file ~/Library/Application\ Support/telepresence/config.yml and put the above two lines in it. Note that the line break and spaces matter in yaml files like this.
telepresence quit -ur (which still popped open the browser window one last time)
telepresence connect -- no longer pops open the browser window, as it now picks up the config setting to skipLogin to their cloud.

If anyone ever suffers from this problem in the future and the config solution does not work for them, this solution worked for us:
https://github.com/telepresenceio/telepresence/issues/2667#issuecomment-1176330566

Related

h2 console glacially slow

Earlier this year I moved to El Capitan on my MacBook Pro. Ever since I've been finding the h2 console very very slow. Here are timings taken today, no other apps running:
2 min 5 sec: Launch the console and wait for it to finish loading. Uses a shell script which does the following:
cd "/Applications/h2 1.3.167/bin"
java -cp h2-1.3.167.jar org.h2.tools.Server
2 min 48 sec: Click on the console's Connect button in my browser and wait for the database to be opened and the console to be ready to work
2 min 20 sec: Run a very simple query which the DB engine takes 18ms to process
21 sec: Click on the console's disconnect button and wait to be back at the "front page" for the console
This is on 1.3.167; I tried 1.3.176 earlier today, and it's just as slow, but it gives an error about my database contents once it's finally been opened, so I'll have to look into that sometime.
Has anyone else come across this extreme slowness? What can I do to solve it?
For those who may come along after me, here is the resolution (for my configuration).
It turned out the problem was that my machine name (in Sharing preferences) consisted of my first name and then an apostrophe and then "MacBook Pro". (for example, Santa's MacBook Pro) Except, the apostrophe wasn't: it was a smart quote.
No, I didn't put it there! I didn't even know until now that it was possible to do that. The Mac did it all on its own.
And, of course, the machine name was copied through to HostName. The smart quote was in there, too. Which was causing Java's StringCoding.encode() to have problems encoding the host name string in UTF-8. Which was causing DNS resolution to take 5s instead of 80ms. Which was making the h2 Console work glacially slowly...
Here are the two threads which helped me solve the problem:
h2 google groups
another thread here
Good luck! I hope your resolution is as simple as mine turned out to be!
I had the same problem, but it was actually
sudo scutil --set HostName asdf
That fixed it for me.
In my case, running macOS Mojave, I solved the slowness simply by using localhost in URL instead of my local IP which seems to be the H2 default.

X Error: BadDrawable (invalid Pixmap or Window parameter) when launching Spyder on GNOME

sorry if this question is not as detailed and focused as it should be.
I am a Linux user (so no admin privileges of any sort) and just installed Anaconda3 from here and followed the instructions.
Note that my Linux machine is not connected to the internet, so I had to transfer the file through other means and just run bash Anaconda... as instructed in the Continuum site.
I have then succesfully launched IPython and tried to plot inline, without problems. However, when I tried to use plotting in windows, I got this kind of output from the terminal:
X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 62 (X_CopyArea)
And the created graph window was just blank.
I then tried to start Spyder and basically saw the same behaviour: a lot of those errors reported above, and the Spyder window just popped up blank.
Google search for the error gives results reported for Qt, which makes sense since when plotting "offline" (as opposed to inline) then QtAgg is used.
However, I have no clue as to where to look for the version of these libs, how to install/compile new ones, whether that is really the issue or not. I am just to ignorant about Linux.
Anybody can hint on what to look for and how to try to debug this behaviour?
I had the same error. What worked for me is to add this line in /etc/environment.
sudo nano /etc/environment
Add this line
QT_X11_NO_MITSHM=1
Source : https://github.com/P0cL4bs/WiFi-Pumpkin/issues/53#issuecomment-309120875
Note that in my case the fix didn't take effect until I rebooted my machine.
you may simply run on the terminal:
export QT_X11_NO_MITSHM=1
I had this same error, so I'll tell you what worked for me.
I think it is a permissions issue, based on the following:
I was logged in through a VNC server window through my account, but within the VNC server was setting up a user profile for "user2". In a 'user2' console I installed anaconda in user2's directory. When I typed spyder in the user2 console, I got the exact error you describe. I guessed the VNC desktop didn't like user2 trying to open a window on user1's profile. I then logged out of my VNC server window, logged into the user2 vnc server window, and in a console typed 'spyder' and it opened perfectly.
I think for some reason it is trying to open but is installed in a directory that you don't have permissions for or trying to open in a window that you don't have access to.

error: failed to attach to process ID 0

I have been reading the forums and so far none of the solutions suggested works for me. I'm running Xcode 4.4.1 and testing in iPhone 5.1 simulator. The simulator won't open the apps anymore and I'm getting the above error. Any thoughts or solutions pls?
Go to IOS Simulator tool bar and click Reset Content and Settings...
I've met the same problem
1.you can delete the App directy under
~/Library/Application Support/iPhone Simulator/6.0/Applications
and ~/Library/Developer/Xcode/DerivedData
2.then you can start Xcode ; in the menubar you can find Project -> Clean
EDIT: before copy/pasting 1 above change the Simulator Version to what
you are using!
Click on Simulator and reset the simulator by going to the “iOS Simulator” main menu and choose “Reset Content and Settings…
Back in XCode, choose the menu "Product" > "Edit Scheme". On the left menu panel, click on "Run _Your_Project_Name_.app" > "Run _Your_Project_Name.app". The info display on the right should have the "Debug Process As" radio button picked as "Me (your-user-name)". If not, make sure you do not login as root. On Stackoverflow there are many reports of running as root will have problems
Next, still in Xcode, go to the menu "Window" > "Organizer". On the top menu, click on "Projects". Go ahead and delete "Derived Data".
Finally, go to "~/Library/Application Support/iPhone Simulator/6.0/Applications" and delete everything that’s in there
Finally, I found out the problem was I had a folder called "resources" that I used to store all my images. When I changed the name of the folder to something less likely to be used by XCode somewhere else, I did the whole delete derived data/clean/restart XCode and it worked!
Nothing from mentioned above helped me.
But as I found that few moments before, I (or some other entity) had somehow removed records from my /etc/hosts file and I got the same error.
You should check whether you have in your /etc/hosts file the line "127.0.0.1 localhost".
As this line is missing, the LLDB debugger is generating issues.
So just add 127.0.0.1 if you have it missing in your /etc/hosts.
This helped me!
Delete the app on the iOS simulator.
It works for me.
Reset Simulator and quit simulator then Rebuild-Run.Its works for me
Cleaning (either deleting folders, or Product->Clean) did not worked.
I saw that in my .plist the bundle id had been removed. Thanks to git. I checkouted-- the file, and bam! deployed to simulator no problem.
Just sharing...
Sometimes this problem arises from having two targets in a project, both using the same bundle identifier but building products with distinct names.
Deleting the application on the device/simulator solves the problem, as it has been said earlier.
This happend to me after changing the Product name.
After resetting the simulator, cleaning the project, and restarting XCode, nothing worked. After shutting down and restarting the simulator everything worked as expected.
I guess there exists someone who is in case the matter happens only in a project, not in every project and failed to resolve the matter after doing a lot of solutions posted on this Question page, such as 'deleting the App directy under ~/Library/Application Support/iPhone Simulator/6.0/Applications and ~/Library/Developer/Xcode/DerivedData', 'Cleaning all the logs by doing Project -> Clean' and 'Cleaning all the log and contents in the iOS Simulator Menu' and anything else.
Yes, I also finally failed to resolve that.
For you, It might be a solution if you are in the problem I mentioned above:
Create a new project with a similar name, and copy and paste all of your classes and resourse files existing in your previous project folder to the new one and link the references between your new project and the copied files in Xcode.
Then, clean the build logs by pressing 'Shift + Command + K'.
In my case, this made me able to continue my work...
My App didn't have a proper BundleID after deleting some xcconfig files.
I had the same problem and I found that you can't be using the root account on your Mac. If you are logged in as root you are not able to attach process to the Simulator. You have to be logged in as a different account.
Every time I have this issue (that is quite often actualy), I uninstall the app from the simulator (like a user would on the device) and do a clean on XCode. Next build and run works.
I can also reset the simulator content and settings to make it work but this seems like using a bazooka to kill a fly.
This also happens if you prepare your file for enterprise distribution and end up saving the resulting .ipa and .plist in the project directory, thus overwriting your project plist. When that happens you'll know because the version information and main window in your project configuration will be blanked. If this happens restore your old plist from source control... and save your product files elsewhere !
This happens when you switch between versions of xcode.
Simple solution is to quit xcode and simulator.
Relaunch xcode and at the same time clean the simulator befor running. This should solve the problem.
I had this problem because I had another user on the same machine running the iOS simulator. Logging in as the other user and quitting the simulator (and Xcode) solved it in my case.
Step1: ping
$ ping localhost
This should return something like
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.028 ms
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
...
If this works, this answer won't fix your problem, try something else.
If ping return something else for example: ping: cannot resolve localhost: Unknown host something is screwed up with your /etc/hosts file, go to Step 2
Step2: Check /etc/hosts
Check that the top of your /etc/hosts file looks like this
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
fe80::1%lo0 localhost
If it doesn't have these entries in the file, enter them at the top of the file, flush the dns cache using $ dscacheutil -flushcache and go back to Step 1, otherwise continue to Step 3.
Step3: Correct File Format: It should be unix or LF *
$ file /etc/hosts
This should return: /etc/hosts: ASCII English text
If it returns something like /etc/hosts: ASCII English text, with CR line terminators then the file is in the wrong format and is likely being ignored.
Change the file line endings to unix or LF using your favorite text editor.
In Sublime Text 2 this can be done throught the view menue: View > Line Endings > Unix
Flush the dns cache ($ dscacheutil -flushcache) and go back to step 1
Embarrassing late-night moment, but just for completeness... when you click "reset content and settings" on the emulator, of course the big blue default button says "DON'T reset", and the little white other button says "reset". If you're not paying attention it can be quite difficult to remember to read the buttons. I can't believe I'm admitting this but hey, happens to us all (right? :))
I restart the simulator and it worked for me
Some times it happens because you have two projects with same name. Try this:
go to xCode preference choose location and click on DerivedData delete the DerivedData
Reset and force Quit Simulator
Force Quit The Xcode and restart
If it has not worked than restart your PC.
and another one for the record: (none of the suggestions worked for me)
Mountain Lion: XCode 4.6.3
I moved the whole Application to Trash and deleted following other folders
/Users/[USERNAME]/Library/Developer
/Users/[USERNAME]/Library/Caches/com.apple.dt.XCode
/Users/[USERNAME]/Library/Application Support/iPhone Simulator
reboot System and reinstall XCode

Visual Studio 2010 slow debugging

I have a problem with Visual Studio 2010. When I start debugging it works slowly.
Internet Explorer opens, but the website loads extremely slowly.
My workmate and me work on the same project and he doesn't have any problem like that.
My hardware is 4G memory + Intel Core i5 CPU 3.20 GHz.
I stopped my anti-virus program but it couldn't be resolved.
I've had the same problem for over a year! And I solved it :)
I took me about 20 seconds to start debugging, and about 1 minute to stop it. It also took 2 minutes to load the solution! My colleague had NO problems with the same solution.
I found my way out of it by a coincidence.
I CHANGED the NAME of the solution, and things suddenly happened 30 times faster.
I CHANGED the solution name back and it slowed down again!
This is probably a FUBAR error made by the Microsoft development team. Don't try to figure out why it happens :)
This might be a IPV6 issue (that shows itself in windows vista/7 when using firefox or IE). I've had that at work and this is what made pages load instantly when using localhost (instead of the 20+ seconds that could happen on image-heavy websites I was developing).
IPv6 (taken from Firefox cannot load websites but other programs can )
Firefox supports IPv6 by default, which may cause connection problems on certain systems. To disable IPv6 in Firefox:
In the Location bar, type about:config and press Enter.
The about:config "This might void your warranty!" warning page may appear. Click I'll be careful, I promise!, to continue to the about:config page.
In the Filter field, type network.dns.disableIPv6.
In the list of preferences, double-click network.dns.disableIPv6 to set its value to true.
For Internet Explorer, try using http://127.0.0.1:PORT_NUMBER/ where PORT_NUMBER is the port you can see in your address bar. If the loading of the page is faster, then you might want to go check the C:\Windows\System32\drivers\etc\HOSTS file and make sure the only line mentioning localhost looks like 127.0.0.1 localhost.
Check to see if you have _NT_SYMBOL_PATH environment variable set. Getting symbols or pdb files for the assemblies used by your application from a symbol server could be the cause of the slow startup of your application when debugging. You can also look at the symbols setting in VS>Tools>Options>Debugging. Also, take a look at the output window and the status bar down at the bottom in VS when your app is loading and taking a long time to see what VS is busy doing.
Not sure if this applies to ASP.NET applications, but disabling the 'Show Parameter Values' option in the Call Stack window's context menu considerably speeds up the debugger on my machine.
Two things to check.
1. Remove all the parameters in the watch list.
2. Build >> Config Manager , Check the Configuration Mode: Debug/Release.
I have encountered the same problem. I could make it better by deleting the Folder created in the temporary aspnet folder. For that you need to close the solution that you have opened and then delete. I don't know if there is any other solution.

Waiting for flash player to connect to debugger

Using Flex Builder 3 :
I have been getting this problem in every single debug launch for past few hours.
I used to get this earlier too, but once in a while, not with every debug launch.
I found out that flex debugger uses a certain 7935 port but I can't figure out
how to change it?
I remember getting this problem a few times. It might have to do with the Flex Profiler (I used to accidentally click that every now and then trying to launch the debugger).
If you start the Profiler and stop it too fast, it will add something to a file in your home directory that it shouldn't.
Check out /path/to/home/mm.cfg on your operating system (on mac, you can open it in textmate with mate ~/mm.cfg). The mm.cfg file stores some information about debugging in Flex
Then in that file, make sure this is the only content:
ErrorReportingEnable=1
TraceOutputFileEnable=1
If there's an extra line (can't remember/find it, something like PreloadSwf=/Users/[username]/Documents/workspace/.metadata/.plugins/com.adobe.flash.profiler/ProfilerAgent.swf?host=localhost&port=9999), delete it.
Let me know if that fixes it.
Lance
Also just make sure you're not using Chrome. Flash Player debugger (at the time of writing this) does not work in Chrome.
This worked for me: right click on a SWF, select "Open with...", choose "Other...", select the Debug player and check the "Always Open With" checkbox.
Mac OSX / FlashBuilder4
Right click your launched flash application, either in the browser or standalone flash player and click on debugger if enabled and change the radio button from localhost to other machine and enter the ip 127.0.0.1 and you are free to debug. I guess the problem maybe from your host file.
Changing the browser from default (chrome) to IE worked for me
Similar to danjp - This started happening to me after a Flash Player automatic update. I simply reinstalled the debug flash players from the Adobe Flash Player download page and everything works as expected.
Make sure there is a swf file with the proper name in your bin-debug directory and that name matches the swf name specified in index.template.html file for the project.
I had replaced index.template.html file by mistake with a similar one from another project. When I tried to debug, I got this "Waiting for flash player to connect to debugger…" status till it timed out.
To me the problem was that internet explorer opened and showed a certification problem, if i didn´t continue this the debugger would show this error. If i continued on ie, no problem happens.

Resources