I am currently working on a jhipster project.
I had to encounter some difficulties with jhipster translation-not-found[error.url.not.found],
that I was able to solve and I would like to share the result of my research.
here is my problem in a few pictures.
After refreshing the page, the credentials no longer work
Infos :
jhipsterVersion: 6.10.5
applicationType: monolith
clientFramework: angularX
Environment and Tools
java version "11.0.12" 2021-07-20 LTS
Java(TM) SE Runtime Environment 18.9 (build 11.0.12+8-LTS-237)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.12+8-LTS-237, mixed mode)
git version 2.15.0
node: v12.16.1
npm: 6.13.4
Docker version 20.10.7, build f0df350
docker-compose version 1.29.2, build 5becea4c
Resolution,
The problem is due to the high size of the headers at the FRONT (Angular) and BACKEND (Spring-boot) level.
1- FRONT correction :
Edit package.json (Edit the package.json file and add the following parameter On title webpack-dev-server and webpack : --max-http-header-size=102400000)
2- BACKEND correction :
Edit application.propertie files (application-dev.yml and application-prod.yml), add : server.max-http-header-size: 102400000
I humbly hope this helps you
Translator: Google translate
Related
Trying to upgrade an existing React app running on AWS Amplify from node v16 to v18
The image used is the provided Amazon Linux 2
Expected it to install node 18 on the machine it spun up and build the application, since this is the LTS version
Here is the error I get in the build process:
2022-11-15T19:19:02.924Z [WARNING]: node: /lib64/libm.so.6: version GLIBC_2.27' not found (required by node)
node: /lib64/libc.so.6: version GLIBC_2.28' not found (required by node)
The same problem happened to me, I fixed it by adding a custom image in the build config.
You can see the steps to add a custom image in the following link
The image that worked for me was the following:
public.ecr.aws/t7o4u3y2/node-18.2.0:latest
Amazon Linux 2 includes Glibc 2.26 or under. To use a higher glibc version, you need to consider other AMI, for example Amazon Linux 2022 (al2022-ami) as it includes glibc 2.34.
You can also revert back to Node.js 16 as it uses a lower version of Glibc.
Thanks for opening this issue. Amazon Linux 2 doesn't support the right GLIBC version at the moment, we're coordinating internally to get that updated. As #saharl-neosec mentions, you can provide a custom docker image until we fully support it:
https://github.com/aws-amplify/amplify-hosting/issues/3109
I have gitlab omnibus install on a linux debian server. Yesterday, the installation was upgraded to 14.12 (from 14.11) - and now I'm unable to access the web UI. On investigation, it seems that the issue was caused by a conflict of versions of ruby and passenger. I'm using an external nginx on the server, as the tail server has other virtual hosts. I have the latest version of passenger installed - 6.0.9. Gitlab latest version comes with ruby version 2.7.2 - but passenger 6.0.9 has no support for that version, it support 2.7.3 instead.
I downgraded passenger to version 6.0.8 - now the passenger_native error is resolved (by direct downloading exact version). However I'm getting the following error in the log:
Could not spawn process for application /opt/gitlab/embedded/service/gitlab-rails:
A timeout occurred while starting a preloader process.
There's not much more info. There is one question I found on SO from years ago - this one - with the same error - but it's not solved. I'm in no position to install/run docker on the server.
How can I get gitlab UI to show?
Note: this is cross-posted to ServerFault here.
So this is really strange.
Local dev environment :
OS : Win x64
Node version : 8.x (LTS)
The project does not build with the AOT flag. It throws "xyz" does not exist in object of type {}.The fix to this is very obvious.
Remote env:
OS : linux x64
Node version : 6.x (LTS)
The project builds successfully without the above-mentioned compiler errors!
Both environments have the same CLI version. The only difference being the node version, local being higher.
Can anyone shed some light on this? Does the compiler behave differently on node versions higher than 6.x LTS?
I am having an out of memory problem with running a build of an Ionic application with --release and --prod flag. Unfortunately, as it seams, the space of memory that Node is allowed to use is not sufficient for the process and it's producing the following error (probably after no memory blocks are available to carry out the operation):
As suggested in this answer, I tried to exploit the max_old_space_size flag from the package.json start script before the build command to no avail. Mainly because the node process is run internally by the Ionic CLI way after the flag is set.
I also tried to re-install Ionic with a bigger heap size as suggested in this answer, but that seems to only address memory limitations during installation of the Ionic package itself, and not any subsequent operations with Ionic via the CLI.
Thanks in advance for any help. :)
Ionic Info:
cli packages: (D:\ionic\<...>\node_modules)
#ionic/cli-utils : 1.9.2
ionic (Ionic CLI) : 3.9.2
global packages:
Cordova CLI : 7.0.1
Gulp CLI : CLI version 3.9.1 Local version 3.9.1
local packages:
#ionic/app-scripts : 2.1.4
Cordova Platforms : android 6.2.3 ios 4.5.0
Ionic Framework : ionic-angular 3.3.0
System:
Android SDK Tools : 25.2.2
Node : v6.10.2
npm : 4.0.5
OS : Windows 7
The only solution was to increase the memory size for Javascript heap internally (from Ionic's point of view) as and when the Ionic CLI kicks the process.
The post on Github by #timothybclayton on a similar issue under ionic-app-scripts helped me figure this out.
However, I had to do it in quite different way than that because I had Nodist as package manager for NodeJS. So, I had to go to the /bin folder under Nodist installation directory and tweak the ionic.cmd file.
This is how the ionic.cmd file looks as it has now allows plenty of memory for NodeJS to carry out the process:
#IF EXIST "%~dp0\node.exe" (
"%~dp0\node.exe" --max_old_space_size=12288 "%~dp0\node_modules\ionic\bin\ionic" %*
) ELSE (
#SETLOCAL
#SET PATHEXT=%PATHEXT:;.JS;=;%
node --max_old_space_size=12288 "%~dp0\node_modules\ionic\bin\ionic" %*
)
Hope this helps anyone else with a similar issue, not only for Ionic, but for any other memory-intensive process with NodeJS.
I flagged this as a duplicate, but in case anyone happens across it before it is consolidated, I posted the modern solution to this problem over at https://stackoverflow.com/a/48895989/4200039:
As of v8.0 shipped August 2017, the NODE_OPTIONS environment variable exposes this configuration (see NODE_OPTIONS has landed in 8.x!). Per the article, only options whitelisted in the source are permitted, which includes "--max_old_space_size".
So I put in my .bashrc:
export NODE_OPTIONS=--max_old_space_size=4096
I am currently using ionic2 to try creating a cross plattform app. I know that ionic2 still is under heavy construction and that things (may) change at any time.
Still i wonder how I could install the latest components/api stuff from the nightly builds (or whereever they reside).
I am especially referring to the infiniteScroll Component that is mentioned in the API-Documents of ionic2.
Since i don't understand the layout of the components inside my project fully, i checked where i could see some of them in the directory structure. If i get this right, they all reside in <projectHome>/node_modules/ionic-framework/components?
At least lots of the components mentioned in the documentation above are listed there.
But as i can't find the infiniteScroll Component there, i would like to get some hints on how to install this (and the other missing ones) either by directly giving the respective commands or by pointing to appropriate documentation (i simply did not find anything although searched quite a while for it).
ionic info shows:
Your system information:
Cordova CLI: 6.0.0
Ionic Version: 2.0.0-beta.1
Ionic CLI Version: 2.0.0-beta.17
Ionic App Lib Version: 2.0.0-beta.8
ios-deploy version: 1.7.0
ios-sim version: 4.1.1
OS: Mac OS X El Capitan
Node Version: v5.6.0
Xcode version: Xcode 7.0 Build version 7A220
Sir,
Ionic made some changes in their latest commit. You could see the changes here in the changelog. (Mar 1)
The components are not present in 'ionic-framework/ionic' anymore and they are now present in 'ionic-angular'.
Infinite scroll was added in the release 2.0.0-beta.2, whereas you use the previous release 2.0.0-beta.1 So you might not be able to add it. You could change your package.json to reflect the latest version like shown below.
"ionic-angular": "2.0.0-beta.2",
I would recommend you to read the changelog as it would give a better idea. Hope this was helpful. Thanks.