Font extension on jasper reports occurs flickering issues on browsers - jasper-reports

Could anyone help me to understand next behavior?
on server (Centos VM) installed font google-crosextra-
carlito-fonts.noarch (only this one contains necessary calibri font for my customer):
yum search calibri
google-crosextra-carlito-fonts.noarch : Sans-serif font metric-compatible with Calibri font
yum install google-crosextra-carlito-fonts.noarch
ls -l /usr/share/fonts/google-crosextra-carlito
-rw-r--r-- 1 root root 816716 Sep 20 2013 Carlito-BoldItalic.ttf
-rw-r--r-- 1 root root 690516 Sep 20 2013 Carlito-Bold.ttf
-rw-r--r-- 1 root root 623416 Sep 20 2013 Carlito-Italic.ttf
-rw-r--r-- 1 root root 635996 Sep 20 2013 Carlito-Regular.ttf
"registered" new font in the system with command (but also reboot server):
fc-cache -f -v
created simple report on Jasper Studio with some text fields (Blank_A4.jrxml)
added font Carlito-Regular.ttf (from Centos server) to Studio (see screen)
exported Carlito-Regular.jar file from Carlito-Regular.ttf copied to WEB-INF/lib folder; restarted application server + removed all caches from /temp & /work
added to report font extension, saved it and published to Jasper server (JRS)
As result - on JRS it seems flickering problem with fonts during report execution. Please see screencast:
https://www.screencast.com/t/O3EH5FAE5n1L
Tried to apply a few different font to the report (Blank_A4_2 & Blank_A4_3 on video) as well as calibri.ttf downloaded from internet - the same result (on Chrome, Firefox, IE).
It looks like report is trying at first to load the some default font form OS and then the applied font of font family.

Related

Using Render hosting app to deploy my project- Error Cannot find module

Follows Heroku becoming a paid app, I am trying other options.
Does anyone have experience uploading a MongoDB server-based project to "Render" Application Hosting?
This is the repo I want to deploy:
https://github.com/myyoss/FUNDLE_A_WORDLE_CLONE
On the app settings I use for the Build Command: "yarn" (and it seems to works cause I get "Build successful" message).
But for the Start Command I can't get the correct command/path.
I keep getting this error:
==> Build successful :
Oct 7 06:41:33 PM ==> Deploying…
Oct 7 06:42:01 PM ==> Starting service with ‘node dist/server.js’
Oct 7 06:42:06 PM internal/modules/cjs/loader.js:888
Oct 7 06:42:06 PM throw err;
Oct 7 06:42:06 PM ^
Oct 7 06:42:06 PM
Oct 7 06:42:06 PM Error: Cannot find module ‘…/routes/userRoutes’
Can someone please take a look at the repo LINK and tell me what I'm doing wrong?
On an other project I used "node dist/server.js" for the Start Command and it worked just fine.
I think your problem may be here, where you use "../routes/userRoutes". You want to use "./routes/userRoutes" since the location of that file is relative to the root directory, ./
This answer may be helpful re: routing errors, and Render's quickstart for Node/Express is also worth a look.

Uploading/Downloading file from Artifactory OSS while preserving file permissions

I have a binary file named node_exporter, which has executable file permissions:
-rwxr-xr-x. 1 root root 16834973 Jul 29 08:35 node_exporter
I use the Artifactory CLI to upload the file:
./jfrog rt u node_exporter {repo}/node_exporter.
And then to download the file:
./jfrog rt dl {repo}/node_exporter.
Once downloaded, the file loses executable permissions.
-rw-r--r--. 1 root root 16834973 Jul 29 08:44 node_exporter
I know that using cURL doesn't deal with metadata, but I'm not sure why the official CLI doesn't as well. Is it possible at all to upload/download while preserving file permissions? This is being used in integration with Jenkins, so I would rather not have to set the file permissions after downloading the binary for each build.

AWS Lambda Function Can't Find Package - Psycopg2

Here's my issue:
START RequestId: 3ef6bbb9-62da-11e8-82ba-81e0afb0b224 Version: $LATEST
Unable to import module 'lambda_insertEmailAddress': No module named psycopg2
END RequestId: 3ef6bbb9-62da-11e8-82ba-81e0afb0b224
REPORT RequestId: 3ef6bbb9-62da-11e8-82ba-81e0afb0b224 Duration: 0.44 ms Billed Duration: 100 ms Memory Size: 128 MB Max Memory Used: 19 MB
My zip file has the following structure file name: lambdaInsertEmail.zip:
total 98784
drwxrwxrwx 20 chauncey staff 680B May 27 13:22 psycopg2
drwxrwxrwx 22 chauncey staff 748B May 27 12:55 postgresql-9.4.3
-rwxrwxrwx 1 chauncey staff 1.8K Apr 30 15:41 lambda_insertEmailAddress.py
-rw-r--r-- 1 chauncey staff 48M May 30 12:09 lambdaInsertEmail.zip
In case you want to know my setup.cfg file has the following changes:
pg_config=/Users/chauncey/Desktop/portfolio/aws_lambda_files/lambda_insertEmailAddress/postgresql-9.4.3/src/bin/pg_config/pg_config
static_libpq=1
I'm trying to get this lambda function working.
The problem is being cause because psycopg2 needs to be build an compiled with statically linked libraries for Linux. Please reference Using psycopg2 with Lambda to Update Redshift (Python) for more details on this issue. Another reference of problems of compiling psycopg2 on OSX.
One Solution is to compile the library using an Amazon Linux AMI. Once you have connected to the AMI with SSH:
Set up aws credentials using aws configure
sudo su -
pip install psycopg2 -t /path/to/project-dir
Zip directory zip project-dir.zip project-dir
Upload to Lambda using CLI
Hopefully this helps you understand the issue and a possible solution solution. There are additional solutions in the above references, such as using boto3 or this repo https://github.com/jkehler/awslambda-psycopg2, but this is the solution that worked for me.
pip install psycopg2-binary
fixed it for me

Maillog /bin/sh: /usr/lib/dovecot/dovecot-lda: No such file or directory 4.2.1

I just moved to a new server with Plesk pre-installed on it, my sites work now but when I try to send mails I get the following error:
Mar 5 13:43:14 www postfix/qmgr[2271]: 9351512650BA:
from=, size=572, nrcpt=1 (queue active) Mar 5
13:43:14 www postfix-local[3080]: postfix-local:
from=info#[MY_DOMAIN].nl, to=servers#[MY_DOMAIN].nl,
dirname=/var/qmail/mailnames Mar 5 13:43:14 www
postfix/pipe[3079]: 9351512650BA: to=,
relay=plesk_virtual, delay=1307, delays=1307/0.04/0/0.05, dsn=4.3.0,
status=deferred (temporary failure. Command output: /bin/sh:
/usr/lib/dovecot/dovecot-lda: No such file or directory 4.2.1
Message can not be delivered at this time )
I have been looking for over an hour but I have not found a fix yet.
The directory /usr/lib/dovecot does not exists, the directory /usr/lib64/dovecot does exists.
The server runs on Centos.
SOLVED: I found out that I copied the full mail directories, including the config files. I removed the mailboxes and moved over the mail directories without config files. Now the mailbox works again.
So for everybody with the same problem when moving. Don't copy your mail config files.
Various options exist:
ln -s /usr/lib64/dovecot/dovecot-lda /usr/lib/dovecot/dovecot-lda,
Edit your postfix/master.cf file and change the /usr/lib/dovecot path to /usr/lib64/dovecot,
Install a 32-bit version of Dovecot on that box.
All have their disadvantages, the best thing is to coordinate with the people who wrote the software that manages the email config and let them know your trouble.

TYPO3 - PHP errors after server restart

We had to restart a server that has a TYPO3 site on it. We made no changes to the database of any of the TYPO3 files themselves, just a standard restart. The issue is that now the server is spewing php errors. I would like to stress that no server configuration changes were made.
A sample of our error logs:
[Wed Jun 27 23:55:19 2012] [error] [client ****************] PHP Strict Standards:
Declaration of tx_commerce_db_article::get_attributes() should be compatible with tx_commerce_db_alib::get_attributes($uid, $attribute_corelation_type_list = '')
in /var/www/html/***********/class.tx_commerce_db_article.php on line 63
Anyone have any ideas of what might have cause typ03 to make a deposit on the living room rug?
The server will take the request but admin page and main page will not display.
Someone updated PHP to version 5.4 on the server. Only the latest dev versions in the git repositories include a fix to the display error pattern that explicitly excludes E_STRICT.
Have a look at this issue and the according patches:
http://forge.typo3.org/issues/35154