UniversalDataTool / universal-data-tool

Collaborate & label any type of data, images, text, or documents, in an easy web interface or desktop app.
https://universaldatatool.com
MIT License
1.94k stars 192 forks source link

Cannot find the executable in the release downloads #453

Closed johann-petrak closed 3 years ago

johann-petrak commented 3 years ago

The documentation states that one can run the software on the desktop but there is no explanation how, or which file to actually run. https://docs.universaldatatool.com/installation

The releases seem to just contain the same directory as one gets when cloning the repo, and there is no linux appimage or similar to be found.

Just to be sure I tried to run npm install (though I know nothing about npm or nodejs):

The command npm install fails:

While resolving: universal-data-tool@0.14.22
Found: react@16.14.0
node_modules/react
  peer react@">= ^16.8.0" from react-data-table-component@6.9.7
  node_modules/react-data-table-component
    react-data-table-component@"^6.2.2" from the root project
  peer react@">= 16.8.0" from styled-components@5.1.1
  node_modules/styled-components
    styled-components@"^5.0.0" from the root project
    peer styled-components@">= ^3.2.3 || >= ^4.0.0 || >= ^5.0.0" from react-data-table-component@6.9.7
    node_modules/react-data-table-component
      react-data-table-component@"^6.2.2" from the root project

Could not resolve dependency:
peer react@"17.0.1" from react-dom@17.0.1
node_modules/react-dom
  peer react-dom@">= 16.8.0" from styled-components@5.1.1
  node_modules/styled-components
    styled-components@"^5.0.0" from the root project
    peer styled-components@">= ^3.2.3 || >= ^4.0.0 || >= ^5.0.0" from react-data-table-component@6.9.7
    node_modules/react-data-table-component
      react-data-table-component@"^6.2.2" from the root project

Tried this on Ubuntu 18.04 mit nvm/node/npm install manually using nvm as described here: https://linuxize.com/post/how-to-install-node-js-on-ubuntu-18.04/#2-installing-nodejs-and-npm

johann-petrak commented 3 years ago

OK, on an Ubuntu 20.04 with npm installed from the Ubuntu repos, i was able to run npm install but npm build failed. ` FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory 1: 0x7fa324ac046c node::Abort() [/lib/x86_64-linux-gnu/libnode.so.64] 2: 0x7fa324ac04b5 [/lib/x86_64-linux-gnu/libnode.so.64] 3: 0x7fa324cece6a v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, bool) [/lib/x86_64-linux-gnu/libnode.so.64] 4: 0x7fa324ced0e1 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, bool) [/lib/x86_64-linux-gnu/libnode.so.64] 5: 0x7fa325087c66 [/lib/x86_64-linux-gnu/libnode.so.64] 6: 0x7fa325099043 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/lib/x86_64-linux-gnu/libnode.

... .... npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! universal-data-tool@0.14.22 build:web: rimraf build && react-scripts build && cp -r build ./build-copy && mv build-copy build/app npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the universal-data-tool@0.14.22 build:web script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. `

CedricProfessionnel commented 3 years ago

Hi @johann-petrak ,

Can you send me your system information ? (OS, RAM ...)

I think i already encounter the reason why npm failed.

and for the command the command to launch the desktop app is : (yarn or npm run) start:desktop:static

seveibar commented 3 years ago

Note that the current desktop build is failing, there are executables available for the v0.14.16 release.

image

seveibar commented 3 years ago

We should make it so the release does not appear without those executables, or fix the build so that the executables are included.

johann-petrak commented 3 years ago

Hm, I have in the meantime changed my system configurations on all systems I tried this earlier.

Now on Ubuntu 18.04 with npm 7.4.3 version manually installed using nvm (instead of the version that comes as a system package), the installation with npm install -g udt-collaboration-server seemed to succeed ok.

Then running npm run start:desktop:static from within the cloned and updated git repo gives this error:


> universal-data-tool@0.14.23 start:desktop:static
> electron ./desktop

sh: 1: electron: not found
npm ERR! code 127
npm ERR! path /data/johann/misc/GIT/universal-data-tool
npm ERR! command failed
npm ERR! command sh -c electron ./desktop

I tried to just do npm install electron but that failed and complained about being unable to resolve dependency tree.

CedricProfessionnel commented 3 years ago

You should have access to the .exe to : https://github.com/UniversalDataTool/universal-data-tool/releases/download/v0.14.16/Universal-Data-Tool-Setup-0.14.16.exe

If it's not the version you wish, you can always go to : https://github.com/UniversalDataTool/universal-data-tool/releases and find the .exe of the version you wish

You can actually try to build from the source (like you do now), but I don't advised it.

Note : You should run npm uninstall -g udt-collaboration-server. It will undo npm install -g udt-collaboration-server since it's not a step needed to install the sources or running the app Note 2: I just reword the solution seveibar offer who is clearly easier in your case

johann-petrak commented 3 years ago

When I look at the https://github.com/UniversalDataTool/universal-data-tool/releases page, the only downloadable assets are a zip and a tar of the source code, no compiled programs or exes. As I am using Ubuntu (Linus) the exe is not much use, but I also cannot see a pre-compiled Linux app anywhere either. Oddly the link to the exe you gave works, however there is nothing shown on the release page that would link to the exe or any other executable.

CedricProfessionnel commented 3 years ago

As seveibar said, the newer build currently fails and therefore does not provide the .exe or the linux build, but the link I sent you gives you the latest .exe of the version whose build is successful. If you want to access via the release page, you must scroll down the page until you reach version 0.14.16 or a previous one.

CedricProfessionnel commented 3 years ago

Version who's the build succeed :

image

Version who's the build doesn't succeed :

image

johann-petrak commented 3 years ago

Ah ok, so it appears the latest Linux appimage is from version 0.14.16

illtellyoulater commented 2 years ago

@CedricProfessionnel @seveibar

Guys... sorry to say but this is a total mess! I'm a new user and I just followed what the repository REAMDE says:

"Trying to run the web app locally? Run npm install then npm run start after cloning this repository to start the web server."

So I've only done the only one thing that this repository says to do, and I'm getting the following errors:

PS C:\Users\my-username\downloads\universal-data-tool-0.14.26> npm install
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: universal-data-tool@0.14.26
npm ERR! Found: webpack@5.72.1
npm ERR! node_modules/webpack
npm ERR!   peer webpack@">=2" from babel-loader@8.2.5
npm ERR!   node_modules/babel-loader
npm ERR!     peerOptional babel-loader@"^=8.x" from @cypress/react@4.16.4
npm ERR!     node_modules/@cypress/react
npm ERR!       dev @cypress/react@"^4.16.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional webpack@"^=3.x" from @cypress/react@4.16.4
npm ERR! node_modules/@cypress/react
npm ERR!   dev @cypress/react@"^4.16.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\my-username\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\my-username\AppData\Local\npm-cache\_logs\2022-05-27T01_31_09_817Z-debug-0.log

I've not used node so much, so honestly I have no idea about the severity of the above issues. I'm on Windows 10, running node v16.15.0. I hope you can point me to the right direction...

Thanks!