- This is either due to a require() error during initialisation or failure to call AppRegistry.registerComponent.
I had been struggling with this for some time and the answer was right there… I had to make sure I called AppRegistry.registerComponent with the right params/appname – I had renamed my app and forgot to update the class name and also the name passed to registerComponent.
And, one way to rename a project is by renaming in package.json and then running react-native upgrade.
I was stunned to learn I could set the opacity of a background image like this:
background: linear-gradient(rgba(0,0,0,0.5), rgba(0,0,0,0.5)), url('/path/to/image');
and darken the background image.
After upgrading a webserver running Apache to Debian Jessie (from Wheezy), I noticed that the system CPU usage was higher. Running an strace on one of the Apache processes was giving me very little info:
strace -c -p 10112
Process 10112 attached - interrupt to quit
^CProcess 10112 detached
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
95.71 28.549784 3172198 9 4 futex
I had previously tried to spread interrupts across cores and also limited network activity – as they are something one can do to work out why System CPU is high – but they didn’t bring down the CPU usage.
One culprit remained: Futex/Mutex locks. I changed the default Mutex [1] to file and magically the System CPU usage went down.
After converting a site to be served over TLS, we noticed the drop off rates increasing on some pages. This was because: user was being redirected to a payment page on another domain that was also served over TLS. As, now both sites were served over TLS, Google Analytics was picking up the referrer (HTTPS -> HTTP would pass no referrer, HTTPS -> HTTPS does) and was counting the payment page/domain as a new source. Thus, counting the redirect as an exit. Fix was simple, I excluded the payment domain in the referral list.
Documenting what I had to do.
Used XSLT from here:
nosetest xslt
Problems and Fixes:
doctype-public="-//W3C//DTD HTML 4.0//EN"/
to
<xsl:output |
And removed the doctype declartion in the above xslt
xmlns="http://www.w3.org/1999/xhtml |
After unsuccessfully trying to match the namespace in the xslt, I gave up and removed the namespace from the xunit xml, by
sed -i 's@ xmlns="http://www.w3.org/1999/xhtml" @ @' "output.xml" |
sed -i 's@ encoding="UTF-8"?>@ encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="nosetests.xslt" ?>@' "output.xml" |
Create phabricator user to be used in phabricator config
Grant the above user CREATE TABLESPACE permission so he can create DB
Grant all permissions on the phabricator tables to the above user (daemons/upgrade scripts require different permissions – the permission list from the doc wasn’t enough, so I granted all permission to the user)
CREATE USER 'phabricator'@'%' IDENTIFIED BY '{password}';
GRANT CREATE TABLESPACE ON `phabricator\_%` TO 'phabricator'@'%';
GRANT ALL ON `phabricator\_%`.* TO 'phabricator'@'%';
When a monitored interface goes down, the instance immediately enters FAILED state and the other instance gets into the MASTER state.
But, if you have a script block to check – say you are monitoring HAProxy – and HAProxy goes down the MASTER will not enter FAILED state, unless you do this:
Set the weight to a negative number (if MASTER priority is 101 and BACKUP priority is 100, the weight could be -2).
This way when HAProxy goes down, the Priority of the master will become 101 -2 = 99, the Backup with a priority of 100 will win the election and enter into MASTER state.
When HAProxy on the master comes back, it’s priority increases by 2 to become 101 again and if you have nopreempt disabled, this instance will enter the MASTER state.
Discourse can cause you trouble if you have it running(listening) on a non-standard port inside the Docker instance. (the feed, google auth return url have the port and host info in them) (assuming you would like to serve requests from a standard http(s) port).
To make it work smoothly, I had to make it listen on standard port (80 in my case).
This is what I ended up doing:
Nginx(hostip:80) -> Nginx(dockerinsideip:80)
This method also extends to having multiple docker instance for different sites.
This is my nginx config on the host:
server {
#where discourse sits
server_name forum.mydomain.com;
location / {
#this is also important for discourse to work as expected
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $http_host;
proxy_redirect off;
#my docker instances internal ip
proxy_pass http://172.17.0.2;
}
} |
And, I removed http port mappings on my app.yml file.