Notes and comments from ORM Designer development
When user use ESC to close the dialog and press it very quickly two or more times in a row, QDialog::reject can be invoked also multiple times.
This is very dangerous and unpredictable because in case your reject will contain some one-time-execute routine the application will start crashing.
The only solution I found is to add these routines to QDialog destructor instead of to reject/accept.
curl -X POST --user user:apitoken http://server/job/JOB_NAME/build?delay=0sec
Api token:
http://server/user/USER_NAME/configure
to fix that, it’s sufficient to configure certificate to allow any application to use it without asking:
sudo locale-gen en_US en_US.UTF-8 sudo dpkg-reconfigure locales sudo update-locale
Everything is perfectly explained in this post:
http://ubuntuhandbook.org/index.php/2013/08/install-gcc-4-8-via-ppa-in-ubuntu-12-04-13-04/
List of commands
sudo add-apt-repository ppa:ubuntu-toolchain-r/test sudo apt-get update; sudo apt-get install gcc-4.8 g++-4.8 sudo update-alternatives --remove-all gcc sudo update-alternatives --remove-all g++ sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.8 20 sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.8 20 sudo update-alternatives --config gcc sudo update-alternatives --config g++ gcc --version
Starting with OS X 10.10 existing code signing method doesn’t work. If you have application signed for 10.9 and application works without problems, with 10.10 you will get following error:
How to verify application sign status from command line:
codesign -dvvv /Applications/APP.app Executable=/Applications/Skipper.app/Contents/MacOS/Skipper Identifier=com.skipper.Skipper Format=bundle with Mach-O thin (x86_64) CodeDirectory v=20100 size=239848 flags=0x0(none) hashes=11986+3 location=embedded Hash type=sha1 size=20 CDHash=98839e7aa72de4105ac5ad8a2612682ba3bca53f Signature size=4237 Authority=Developer ID Application: Inventic s.r.o. (6BYV46LH6T) Authority=Developer ID Certification Authority Authority=Apple Root CA Signed Time=03 Feb 2015 17:38:21 Info.plist entries=10 TeamIdentifier=not set Sealed Resources version=1 rules=4 files=44 Internal requirements count=1 size=300
As it’s seems from the verification output, application is correctly signed but OSX doesn’t accept it. Another way how to verify application sign status is via spctl command:
spctl --assess --type execute --verbose Skipper.app/ Skipper.app/: rejected source=obsolete resource envelope
We have some error at least. Now it’s necessary to find out what is wrong. We can try one more test:
codesign -v Skipper.app/ Skipper.app/: resource envelope is obsolete (version 1 signature)
where we dest little bit more details. All these errors we get only on 10.10 mac, not on 10.9 or older.
After another investigation I found following article. The most important part is:
“Important: For your apps to run on updated versions of OSX they must be signed on OS X version 10.9 or later and thus have a version 2 signature.”
Another post about this topic is in felix-schwarz.org blog.
So ,it’s bad. We need to update our build machine to 10.9 or at least create new “sign machine” and make sure that everything will work as expected.
It’s necessary to connect via FTP to azure VM and update ftp://host/site/wwwroot/web.config file.
<rewrite>
<rules>
<rule name="Rewrite tcS3_media">
<match url="^tcS3_media/(.*)" />
<action type="Redirect" url="http://downloads.vodnici.net/{R:1}" appendQueryString="false" redirectType="Permanent" />
</rule>
</rules>
</rewrite>
Step by step for installation
Rom managers
Root telefon
Clockwork mod
Enable debugging
Android SDK
Other
CyanogenMod
SET GLOBAL sql_mode = 'STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'; SET GLOBAL sql_mode = 'modes'; SET SESSION sql_mode = 'modes'; SELECT @@GLOBAL.sql_mode; SELECT @@SESSION.sql_mode;
The problem is probably caused by too large backup/restore script or SQL commands. The solution which works for me is increasing `max_allowed_packet` setting in my.ini
External sources:
edit file sudoers
sudo nano /etc/sudoers or sudo visudo
and modify
%sudo ALL=(ALL) ALL
to
%sudo ALL=(ALL) NOPASSWD: ALL
and add following line to the end of the file:
user ALL=NOPASSWD: ALL
When editing sudoers, it’s necessary to be very careful. Any error cause that you will not be able to edit this file anymore and also not to use sudo ;-).
Here are links how to fix it (verified 😉 )
Use -g swith after -L section to forward ports to whole network
autossh -M 40008 -f -N [email protected] -L 33061:127.0.0.1:3306 -g -L 6380:127.0.0.1:6380 -o "ServerAliveInterval 60" -o "ServerAliveCountMax 3" -o BatchMode=yes -o StrictHostKeyChecking=no -i /root/.ssh/id_rsa
Configuration file : /etc/init/autossh.conf
Start service:
sudo service autossh start
pstrReturn = mg_set_option(serverHttps, "listening_port", "ssl://443:ssl.pem"); // Open port 443 with ssl.pem certificate
# openssl version OpenSSL 1.0.0-beta2 21 Apr 2009 # openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 1000 -nodes # cat key.pem > ssl.pem; cat cert.pem >> ssl.pem
Testing mongoose server via command line (curl), Switch -k allow to use self-signed certificates.
curl -X OPTIONS --header "Access-Control-Request-Method:GET" --header "Access-Control-Request-Headers: accept, x-coral-api-key" https://server.a18/v1/service/method -k
