Web server STDERR output color - meteor

I would really like to change STDERR (web server) colors using Meteor on Windows 7. They are blue at the moment and I can't see it on my Powershell (black background) screen. I spent half day on changing Powershell colors but found out that none of them were blue, so it must be some meteor setting.

You can try enabling raw-logs to remove the colours by passing it as a flag when you run meteor
meteor --raw-logs

Related

Telepresence Commands Pop Up an Ambassador Clouod Login Window

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

Ionic DevApp debugging in chrome console?

I am using ionic DevApp (ionic v4) for the first time, i’m trying to display a json object using the function console.log(). when i run the application in ionic DevApp i see the object only displays in the commande line console (cli) not in the remote devices from google.
Please, is there anyone of you who knows how to solve this issue.
Thank you in advance.
As far as I know, this is not possible. If you want to see the console output, add the parameter -c to the ionic serve:
ionic s -c --devapp
this will output the console in the terminal, but you will not have it as pretty as in Chrome.
Anyway, in my experience, DevApp is not a good solution whatsoever. On one hand, you have the console issue, on the other, plugins will not work. There is no significant pro compared to see your app in the browser directly.
I think you would rather use the --livereload modifier when running the app. This will make the app to quick recompile and reload every time you save some change (just like in ionic serve). You will get the Chrome inspector, your plugins will work normally and your app will quickly recompile and reload on any change save. Just run this:
ionic cordova run android --device --livereload

PWA Workbox Wizard is stopping after the first step

I am setting up a PWA and trying to add a Service Worker using Work Box. When I type 'Workbox Wizard' in to the terminal, only the first question about the root file is being asked and then the terminal freezes and I can't type anything else. Please help!

AEM Launcher run mode issue in Publish Instance

I am running a launcher in publish instance,the launcher doesn't invoke the workflow when run mode is publish or publish and author but it works when I make run mode as author
Can someone help me with this behaviour of AEM?
Wrokflow launchers are tied to run-modes and you can change the behavior to run to either or both of them. The default dialog height is less hence it is not visible you need to scroll down.
Taken from the Adobe documentation:
When using one of the above run modes (author, publish, samplecontent, nosamplecontent), the value used at installation time defines the run mode for the entire lifetime of that installation.
For these run modes you cannot change them after installation.
You cannot use runmodes author AND publish at the same time (I wonder what AEM will do if you try to set both runmodes) and switching the runmode is also a bad idea.
See https://docs.adobe.com/docs/en/aem/6-0/deploy/configuring/configure-runmodes.html for details.
There must be something wrong with your instance. Any log messages?

Beaglebone Black, Qt Application, and startup procedure

I have a BBB running Debian 3.18.13-bone70. I have made a Qt application that works great. I would like this application to run on startup.
Currently, I have made a script, placed it in /etc/init.d and made a symbolic link to it in /etc/rc5.d/S05application. This all functions correctly.
The issue that I'm having is when my system boots up, I see my application briefly (<1 second) before the CLI login screen appears and hides my application.
I've tried playing around with the startup script location (moving it to rc2.d, but the same issue persists.
I have a splash screen that times out after 10 seconds, and it moves on to the next screen. After moving to the next screen the application is never hidden again. I would like to see the splash screen the entire time and hide the CLI login screen entirely. How could I go about doing this?
EDIT:
#!/bin/bash
export QWS_MOUSE_PROTO=tslib:/dev/input/event1
export TSLIB_CALIBFILE=/etc/pointercal
export TSLIB_CONFFILE=/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts
export TSLIB_TSDEVICE=/dev/input/event1
/home/root/./Scanscale -qws
This is the script that I use to start the application. The Qt window service is used when I start the program.
EDIT 2:
I'm running Debian 7 using the Debian 7 image from http://elinux.org/Beagleboard:BeagleBoneBlack_Debian from March 1, 2015. This is maintained by Robert Nelson, I'm not sure if it's a yocto build or something else.
Furthermore, it doesn't appear to be an X issue. I've stopped loading X, I no longer boot into the application and just sit on the command line waiting to log in. The system flickers at about the same point in time. Any thoughts?
I should probably also mention that I'm running it on a 4.3" LCD cape, not on the HDMI interface.
You weren't specific about your system and what else is running on it. For example, is it a yocto build and does it run the sato user interface, or is it more traditional X server with a display manager, window manager, etc? Either way, there is a session-specific file which directs what programs get launched when the Xserver starts up. Using matchbox, that file is .matchbox/session. With X, it's usually xinit, which is driven by .xinitrc or .xserverrc. Also, look at startx as another poster mentioned. The latter can either be in your home directory or /etc/X11. Depending on your system and configuration, likely one of those methods, customized, is what you're looking for. See man xinit for more info.

Resources