-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JHipster upgrade always fails initially but usually will eventually work #19554
Comments
Can you try |
That is what I have been doing. |
I tried installing JHipster 7.0.1 and generator-jhipster-primeng-blueprint@7.0.4, then used your
|
If I use JHipster version 7.6.0 (as specified in your
|
You have to create the project using JHipster version 7.0.1 and node 15 as that is the only version that currently works with generator-jhipster-primeng-blueprint blueprint. that blueprint hasn't been updated for quite a while and I have been working on my companies projects for 60-80 hours/week so have not had the time to try to figure out the code and attempt to update it myself. Side note, commenting and then immediately closing this on a Saturday is a pretty crappy move. Not everyone works 24/7, even people working >60 hours/week. I have no problems generating a project. I'll look into it as soon as I can get back to my work environment an try it. I also happen to have family responsibilities that prevents me from working on some, especially, weekend days. |
You are correct. I'm sorry about that. I probably shouldn't work weekends. I'll try with Node 15. |
If I use Node.js 15, creating the project fails as well.
If I remove the If I run
|
The changelogDate makes me think it might be caused by having no entities, so I created entities using the JDL for the entities you provided. Then, I tried
I upgraded to Node 16.17.0 and tried again.
It still fails:
I'll add a bug bounty to this issue in hopes of getting it fixed. |
Hmm.. I just checked and I actually have Node 16 and I am able to create a project
|
And the upgrade then fails as show above:
|
Hmm... Those are different errors than what I saw :/ |
Updating from 7.8.1 to 7.9.0 fails with a different error that doesn't resolve itself with multiple attempts like the previous error does :(
|
I think it might have something to do with peer dependancies. I removed the package lock json when i got the npm issue and that corrected the issue. |
I have tried upgrading from 7.8.1 to 7.9.0 again, after unwinding the git commits of previous failed attempts and it fails when it attempts to call node_modules\shelljs\src\exec-child.js right after it removes the node_modules directory :/ Though it did merge stuff to the branch I started from so it might be done?
|
I found out why it tried to run bash. Something dropped a .npmrc file with this in it :/
Deleting that fixed the bash problem. I also deleted package_lock.json. |
I have run into an issue attempting to upgrade my project again and ran into several problems: Error: Cannot find module 'C:\src\totalfact\node_modules\shelljs\src\exec-child.js' |
Overview of the issue
Every Time I upgrade a project (any project form any version to any other version of jhipster) it always fails with:
Fortunately I can usually revert the changes and/or abort pending merge if there is one, re-checkout the original branch and it usually works the 2nd or 3rd time.
I am using the generator-jhipster-primeng-blueprint (which is why I had to generate the app using version 7.0.1 of JHipster), but as I mention the upgrade usually works the 2nd or 3rd time. I really don't think this error is due to this blueprint.
Motivation for or Use Case
This is really annoying. Especially since I have to upgrade form version 7.0.1, one version at a time, to the current version.
Reproduce the error
Generate a jhipster application. Upgrade it.
Related issues
Suggest a Fix
JHipster Version(s)
All 7.x versions
JHipster configuration
total-fact@0.0.1-SNAPSHOT C:\src\totalfact
+-- generator-jhipster-primeng-blueprint@7.0.4
|
-- generator-jhipster@7.0.1
-- generator-jhipster@7.7.0If you have a JDL please wrap it in below structure
JDL definitions
**********************************************************/
@filter
@paginate(pagination)
entity UPCHistory {
upcKey String maxlength(15)
name String maxlength(250) required
description String maxlength(1024)
keywords TextBlob
userNotes TextBlob
restrictedResellerFlag Boolean
hidden Boolean
createUser String required
createDate Date required
modifyUser String
modifyDate Date
attributeId BigDecimal
categoryId BigDecimal
protectedClassId BigDecimal
}
@filter
@paginate(pagination)
entity PlatformHistory {
primarySymbol String maxlength(128) required
fieldName String maxlength(250) required
fieldDescription String
fieldLength Integer
inUse Boolean
premiumField Boolean
approvalRequired Boolean
token String maxlength(50)
sasKey String maxlength(10)
rateId String maxlength(10)
caseable Boolean
sanRequired Boolean
waiverRequired Boolean
createUser String
createDate Date
modifyUser String
modifyDate Date
releaseId BigDecimal
platformTypeId BigDecimal
categoryId BigDecimal
upcId BigDecimal
}
@filter
@paginate(pagination)
entity PlatformDEHistory {
ecapsId Integer
defaultValue String maxlength(10)
usedInBilling Boolean
displayZeroCounts Boolean
countFrequency Boolean
countRange Boolean
areaFillinRequired Boolean
omniKvp String maxlength(30)
createUser String
createDate Date
modifyUser String
modifyDate Date
platformId BigDecimal
sectionId BigDecimal
}
@filter
@paginate(pagination)
entity PlatformInstHistory {
pricingFlag Boolean
selectFlag Boolean
outputFlag Boolean
crosstabFlag Boolean
omniKvp String maxlength(30)
createUser String
createDate Date
modifyUser String
modifyDate Date
platformId BigDecimal
}
@filter
@paginate(pagination)
entity PlatformListHistory {
pricingFlag Boolean
selectFlag Boolean
outputFlag Boolean
crosstabFlag Boolean
createUser String
createDate Date
modifyUser String
modifyDate Date
platformId BigDecimal
}
@filter
@paginate(pagination)
entity FieldValueHistory {
fieldValue String maxlength(10) required
valueDefinition String
averageMatchRate Float min(0) max(100)
displayOrder Integer
activeFlag Boolean
createUser String
createDate Date
modifyUser String
modifyDate Date
platformId BigDecimal
}
/*******************************************************
@filter
@paginate(pagination)
entity ProductHistory {
name String
createUser String
createDate Date
modifyUser String
modifyDate Date
}
@filter
@paginate(pagination)
entity DimensionHistory {
name String maxlength(128) required
description String
createUser String required
createDate Date required
modifyUser String
modifyDate Date
}
@filter
@paginate(pagination)
entity CategoryHistory {
name String maxlength(128) required
createUser String required
createDate Date required
modifyUser String
modifyDate Date
}
@filter
@paginate(pagination)
entity AttributeHistory {
fieldLevel String maxlength(128)
createUser String required
createDate Date required
modifyUser String
modifyDate Date
}
@filter
@paginate(pagination)
entity SectionHistory {
sectionId String maxlength(10) required
name String maxlength(128) required
selfReported Boolean
modeled Boolean
thirdParty Boolean
areaLevel Boolean
compiled Boolean
updatedDaily Boolean
updatedWeekly Boolean
updatedBiWeeekly Boolean
updatedMonthly Boolean
updatedSixWeeeks Boolean
updatedQuatrerly Boolean
updatedSemiAnnually Boolean
createUser String
createDate Date
modifyUser String
modifyDate Date
}
********************************************************/
/*******************************************************
relationship OneToOne {
UPCHistory{attribute required} to AttributeHistory
UPCHistory{dimension required} to DimensionHistory
UPCHistory{category required} to CategoryHistory
UPCHistory{product required} to PlatformHistory{upc required}
}
relationship OneToMany {
PlatformHistory{values required} to FieldValueHistory
DimensionHistory{categories required} to CategoryHistory
UPCHistory{rules} to UPCRule{upc required}
}
*******************************************************/
The text was updated successfully, but these errors were encountered: