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
yarn blank-state fails with UnhandledPromiseRejectionWarning: TypeError: Cannot destructure property languages
of 'undefined' or 'null'.
#2576
Comments
I hit this when the db was not fully set up yet. Why are you running
./database/blank_state.sh and not "yarn blank-state"?
…On Fri, Oct 11, 2019 at 11:24 PM Michael Vorburger ⛑️ < ***@***.***> wrote:
@konzz <https://github.com/konzz> @bdittes <https://github.com/bdittes>
in the context of #2559 <#2559>
(including #2575 <#2575>) I'm
hitting this error - any idea?
***@***.*** uwazi]# yarn blank-state
yarn run v1.19.1
$ ./database/blank_state.sh; yarn migrate; yarn reindex
Deleting uwazi_development database on mongo
MongoDB shell version v3.4.23
connecting to: mongodb://mongo:27017/uwazi_development
MongoDB server version: 3.4.23
{ "ok" : 1 }
2019-10-11T21:08:56.771+0000 the --db and --collection args should only be used when restoring from a BSON file. Other uses are deprecated and will not exist in the future; use --nsInclude instead
2019-10-11T21:08:56.771+0000 building a list of collections to restore from blank_state/uwazi_development dir
(...)
2019-10-11T21:08:56.974+0000 done
$ node run.js ./app/api/migrations/migrate.js
entities_override_mongo_language...
processed -> 1
sanitize_empty_geolocations...
processed -> 1
fullText_to_per_page...
pdf_thumbnails...
geolocation_fields...
Sanitizing connections...
(node:283) UnhandledPromiseRejectionWarning: TypeError: Cannot destructure property `languages` of 'undefined' or 'null'.
at Object.settings [as up] (/root/uwazi/app/api/migrations/migrations/6-connections_sanitizing/index.js:14:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
(node:283) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async fu
nction without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:283) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not han
dled will terminate the Node.js process with a non-zero exit code.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2576?email_source=notifications&email_token=ABR33OQZSBZHXQM5DXH54M3QODVIRA5CNFSM4I77O2T2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRJ5UFA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR33OWT2HPFE5SFFLSF5ALQODVIRANCNFSM4I77O2TQ>
.
|
Closing. (Stale) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@konzz @bdittes in the context of #2559 (including #2575) I'm hitting this error - any idea?
The text was updated successfully, but these errors were encountered: