Skip to content

Help with first steps #538

Open
Open
Help with first steps#538

Description

@m-carrasco
m-carrasco
opened on Jul 11, 2020

Hi.

Sharplab has been really useful to me and I'd like to extend its functionality. Although, I'm having some issues getting started with local development.

I read the instructions and executed sl setup. It successfully builds everything. However, when I run Server and try to locally connect, I get 404 on my browser.

  1. sl setup outputs Server -> D:\dev\sharplab-vanilla\source\Server\bin\Debug\netcoreapp3.1\publish\
  2. From my cmd I do D:\dev\sharplab-vanilla\source\Server\bin\Debug\netcoreapp3.1\SharpLab.Server.exe which outputs:
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: http://localhost:5000
info: Microsoft.Hosting.Lifetime[0]
      Now listening on: https://localhost:5001
info: Microsoft.Hosting.Lifetime[0]
      Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
      Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
      Content root path: D:\dev\sharplab-vanilla
  1. I connect from my browser to: http://localhost:5000, https://localhost:5001 and http://localhost:49891/. Everytime I try, I get 404. The first URL outputs in the Server.exe console:
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
      Request starting HTTP/1.1 GET http://localhost:5000/
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
      Request finished in 24.7209ms 404

Alternatively, I also run Server with IIS Express from Visual Studio (green play button). The browser pops up and I get 404.

I'm pretty sure I must be forgetting something stupid. The truth is that it is my very first time regarding C# web development.

I work on a three address code representation of CIL bytecode. I'd really like to integrate it into your website!

Best,
Manuel.

Activity

  1. ashmind commented on Jul 20, 2020

    @ashmind
    ashmind
    on Jul 20, 2020
    Owner

    Thanks for the detailed report!
    Yep, setup is a bit broken at the moment, I'm looking to improve it.

    I think one of the main problems is that you are running Server, but without WebApp it will have no UI.

    I recommend installing https://github.com/dotnet/tye and running dotnet tye run in the main folder.
    If that is successful, you should have both frontend and backend built and running.

    I am going to look into improving setup as part of #488, however can't promise any specific timeline.

  2. ashmind commented on Jul 20, 2020

    @ashmind
    ashmind
    on Jul 20, 2020
    Owner

    I just fixed sl setup which will install correct version of tye for you.

  3. m-carrasco commented on Jul 20, 2020

    @m-carrasco
    m-carrasco
    on Jul 20, 2020
    Author

    Awesome! \0/

    As soon as I can, I'll try to test it and tell you if it is working.

  4. m-carrasco commented on Jul 21, 2020

    @m-carrasco
    m-carrasco
    on Jul 21, 2020
    Author

    @ashmind I had the chance to test your latest commit. I deleted the old repo and cloned it again.

    I ran sl setup and it built. Then, I executed dotnet tye run yielding the following error.

    D:\dev\sharplab-vanilla>dotnet tye run
Loading Application Details...
Launching Tye Host...

[22:53:00 INF] Executing application from D:\dev\sharplab-vanilla\tye.yaml
[22:53:01 INF] Dashboard running on http://127.0.0.1:8000
[22:53:01 INF] Building projects
[22:53:07 INF] Launching service webapp-assets_f16509fa-e: pwsh -Command "npm run watch"
[22:53:07 INF] Launching service webapp-dotnet_7651076c-b: D:\dev\sharplab-vanilla\source\WebApp\bin\Debug\netcoreapp3.1\SharpLab.WebApp.exe
[22:53:07 ERR] Failed to launch process for service webapp-assets_f16509fa-e
System.ComponentModel.Win32Exception (2): The system cannot find the file specified.
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at Microsoft.Tye.ProcessUtil.RunAsync(String filename, String arguments, String workingDirectory, Boolean throwOnError, IDictionary`2 environmentVariables, Action`1 outputDataReceived, Action`1 errorDataReceived, Action`1 onStart, CancellationToken cancellationToken) in /_/src/Microsoft.Tye.Core/ProcessUtil.cs:line 106
   at Microsoft.Tye.Hosting.ProcessRunner.<>c__DisplayClass8_0.<<LaunchService>g__RunApplicationAsync|0>d.MoveNext() in /_/src/Microsoft.Tye.Hosting/ProcessRunner.cs:line 267

    In case you need more information, please tell me. I didn't find any log error.

    Thanks for your support!

  5. m-carrasco commented on Jul 21, 2020

    @m-carrasco
    m-carrasco
    on Jul 21, 2020
    Author

    Here goes more info.

    I can access the Tye Dashboard (http://localhost:8000/). There are two services listed:

    image

    webapp-assets's log is:

    [webapp-assets_35adf907-b]:pwsh -Command "npm run watch"
[webapp-assets_875b0e8e-3]:pwsh -Command "npm run watch"
[webapp-assets_7200745b-5]:pwsh -Command "npm run watch"
[webapp-assets_986c37e2-3]:pwsh -Command "npm run watch"

    webapp-dotnet's log is:

    []([webapp-dotnet_422ae9ec-6]:D:\dev\sharplab-vanilla\source\WebApp\bin\Debug\netcoreapp3.1\SharpLab.WebApp.exe
[webapp-dotnet_422ae9ec-6]: info: Microsoft.Hosting.Lifetime[0]
[webapp-dotnet_422ae9ec-6]: Now listening on: http://localhost:54100
[webapp-dotnet_422ae9ec-6]: info: Microsoft.Hosting.Lifetime[0]
[webapp-dotnet_422ae9ec-6]: Application started. Press Ctrl+C to shut down.
[webapp-dotnet_422ae9ec-6]: info: Microsoft.Hosting.Lifetime[0]
[webapp-dotnet_422ae9ec-6]: Hosting environment: Development
[webapp-dotnet_422ae9ec-6]: info: Microsoft.Hosting.Lifetime[0]
[webapp-dotnet_422ae9ec-6]: Content root path: D:\dev\sharplab-vanilla\source\WebApp
[webapp-dotnet_422ae9ec-6]: info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
[webapp-dotnet_422ae9ec-6]: Request starting HTTP/1.1 GET http://localhost:54100/
[webapp-dotnet_422ae9ec-6]: info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
[webapp-dotnet_422ae9ec-6]: Request finished in 104.7038ms 404)

    Accessing http://localhost:54100/ returns 404.

    Not sure if it is relevant but npm seems to be installed and available through my cmd.

    D:\dev\sharplab-vanilla>npm

Usage: npm <command>

where <command> is one of:
    access, adduser, audit, bin, bugs, c, cache, ci, cit,
    clean-install, clean-install-test, completion, config,
    create, ddp, dedupe, deprecate, dist-tag, docs, doctor,
    edit, explore, fund, get, help, help-search, hook, i, init,
    install, install-ci-test, install-test, it, link, list, ln,
    login, logout, ls, org, outdated, owner, pack, ping, prefix,
    profile, prune, publish, rb, rebuild, repo, restart, root,
    run, run-script, s, se, search, set, shrinkwrap, star,
    stars, start, stop, t, team, test, token, tst, un,
    uninstall, unpublish, unstar, up, update, v, version, view,
    whoami

npm <command> -h  quick help on <command>
npm -l            display full usage info
npm help <term>   search for help on <term>
npm help npm      involved overview

Specify configs in the ini-formatted file:
    C:\Users\Manuel\.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config

npm@6.14.4 C:\Program Files\nodejs\node_modules\npm

  6. ashmind commented on Aug 8, 2020

    @ashmind
    ashmind
    on Aug 8, 2020
    Owner

    Interesting. Do you have pwsh on PATH?

  7. m-carrasco commented on Aug 16, 2020

    @m-carrasco
    m-carrasco
    on Aug 16, 2020
    Author

    Sorry for the long pause @ashmind

    After a Windows update my laptop was not working anymore. So I had to re install Windows on it. I lost the original working environment. However, I tried again from a fresh install.

    I'm still not able to run it, although here are some issues I faced and how I solved them. All this happened while running sl setup and dotnet run tye from a cmd.

    File C:\dev\SharpLab\#scripts\setup.ps1 cannot be loaded. The file C:\dev\SharpLab\#scripts\setup.ps1 is not digitally
signed. You cannot run this script on the current system. For more information about running scripts and setting
execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
    + CategoryInfo          : SecurityError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnauthorizedAccess

    I solved it by running a Powershell instance and executing: Set-ExecutionPolicy Unrestricted (I know this is not the best way to do it probably - security wise).

    Then I had:

    Installing node modules
npm : The term 'npm' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At C:\dev\SharpLab\#scripts\setup.ps1:24 char:5
+     npm ci
+     ~~~
    + CategoryInfo          : ObjectNotFound: (npm:String) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : CommandNotFoundException

    I solved it by installing NodeJS LTS from its official website. The strange thing is that when I installed VS I had choosen to install NodeJS stuff.

    Lastly, I had an issue where I didn't have pwsh available on the cmd. I solved it by running dotnet tool install -g powershell.

    After sl setup executes I run dotnet tye run but the browser loads a blank page.

    
[12:45:07 INF] Executing application from C:\dev\SharpLab\tye.yaml
[12:45:07 INF] Dashboard running on http://127.0.0.1:8000
[12:45:07 INF] Building projects
[12:45:09 INF] Launching service webapp-assets_bf60f0d2-f: pwsh -Command "npm run watch"
[12:45:09 INF] Launching service webapp-dotnet_3255b876-a: C:\dev\SharpLab\source\WebApp\bin\Debug\netcoreapp3.1\SharpLab.WebApp.exe
[12:45:09 INF] webapp-assets_bf60f0d2-f running on process id 2896
[12:45:09 INF] No process was selected. Waiting.
[12:45:09 INF] webapp-dotnet_3255b876-a running on process id 12404 bound to http://localhost:54100
[12:45:09 INF] No process was selected. Waiting.
[12:45:10 INF] Selected process 2896.
[12:45:10 INF] Listening for event pipe events for webapp-assets_bf60f0d2-f on process id 2896
[12:45:10 INF] Selected process 12404.
[12:45:10 INF] Listening for event pipe events for webapp-dotnet_3255b876-a on process id 12404
[12:45:10 INF] Event pipe collection completed for webapp-assets_bf60f0d2-f on process id 2896
[12:45:11 INF] webapp-assets_bf60f0d2-f process exited with exit code 1
[12:45:11 INF] Launching service webapp-assets_b92f130b-6: pwsh -Command "npm run watch"
[12:45:11 INF] webapp-assets_b92f130b-6 running on process id 1548
[12:45:11 INF] No process was selected. Waiting.
[12:45:11 INF] Selected process 1548.
[12:45:11 INF] Listening for event pipe events for webapp-assets_b92f130b-6 on process id 1548
[12:45:11 INF] Event pipe collection completed for webapp-assets_b92f130b-6 on process id 1548
[12:45:12 INF] webapp-assets_b92f130b-6 process exited with exit code 1
[12:45:12 INF] Launching service webapp-assets_99bffc4c-6: pwsh -Command "npm run watch"
[12:45:12 INF] webapp-assets_99bffc4c-6 running on process id 7736
[12:45:12 INF] No process was selected. Waiting.

    Similarly happens if I run it through Visual Studio.

  8. ashmind commented on Aug 17, 2020

    @ashmind
    ashmind
    on Aug 17, 2020
    Owner

    Thanks for the thorough approach! What do you see if you manually run npm run build under source\WebApp\?

  9. m-carrasco commented on Aug 17, 2020

    @m-carrasco
    m-carrasco
    on Aug 17, 2020
    Author

    Thanks @ashmind

    Hmm... I think I have another missing dependency! Am I missing TypeScript or something like it?

    C:\dev\SharpLab\source\WebApp>npm run build

> sharplab@0.0.0 build C:\dev\SharpLab\source\WebApp
> ts-node-script ./build.ts

(node:3048) ExperimentalWarning: The ESM module loader is experimental.
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for C:\dev\SharpLab\source\WebApp\build.ts
    at Loader.defaultGetFormat [as _getFormat] (internal/modules/esm/get_format.js:65:15)
    at Loader.getFormat (internal/modules/esm/loader.js:113:42)
    at Loader.getModuleJob (internal/modules/esm/loader.js:244:31)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at Loader.import (internal/modules/esm/loader.js:178:17)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sharplab@0.0.0 build: `ts-node-script ./build.ts`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sharplab@0.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Manuel\AppData\Roaming\npm-cache\_logs\2020-08-17T18_58_35_653Z-debug.log

  10. m-carrasco commented on Aug 17, 2020

    @m-carrasco
    m-carrasco
    on Aug 17, 2020
    Author

    Here you have the log

    0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build'
1 verbose cli ]
2 info using npm@6.14.6
3 info using node@v12.18.3
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle sharplab@0.0.0~prebuild: sharplab@0.0.0
6 info lifecycle sharplab@0.0.0~build: sharplab@0.0.0
7 verbose lifecycle sharplab@0.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle sharplab@0.0.0~build: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\dev\SharpLab\source\WebApp\node_modules\.bin;C:\Python38\Scripts\;C:\Python38\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\Git\cmd;C:\Program Files\nodejs\;C:\ProgramData\chocolatey\bin;C:\Users\Manuel\AppData\Local\Microsoft\WindowsApps;C:\Users\Manuel\.dotnet\tools;C:\Users\Manuel\AppData\Roaming\npm
9 verbose lifecycle sharplab@0.0.0~build: CWD: C:\dev\SharpLab\source\WebApp
10 silly lifecycle sharplab@0.0.0~build: Args: [ '/d /s /c', 'ts-node-script ./build.ts' ]
11 silly lifecycle sharplab@0.0.0~build: Returned: code: 1  signal: null
12 info lifecycle sharplab@0.0.0~build: Failed to exec build script
13 verbose stack Error: sharplab@0.0.0 build: `ts-node-script ./build.ts`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:315:20)
13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:315:20)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid sharplab@0.0.0
15 verbose cwd C:\dev\SharpLab\source\WebApp
16 verbose Windows_NT 10.0.19041
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v12.18.3
19 verbose npm  v6.14.6
20 error code ELIFECYCLE
21 error errno 1
22 error sharplab@0.0.0 build: `ts-node-script ./build.ts`
22 error Exit status 1
23 error Failed at the sharplab@0.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

  11. ashmind commented on Aug 17, 2020

    @ashmind
    ashmind
    on Aug 17, 2020
    Owner

    Thanks! I can reproduce it in node 12.18.3 (but not in the older version of node I had before).
    I'll investigate and get back to you (can't promise any specific time yet).

  12. m-carrasco commented on Aug 17, 2020

    @m-carrasco
    m-carrasco
    on Aug 17, 2020
    Author

    No worries. Take your time.

  13. ashmind commented on Aug 17, 2020

    @ashmind
    ashmind
    on Aug 17, 2020
    Owner

    Please try branch edge, added a potential fix there (don't remember if it has any other implications, so not in main branch yet).

  14. m-carrasco commented on Aug 17, 2020

    @m-carrasco
    m-carrasco
    on Aug 17, 2020
    Author

    EDIT: Ignore this post, I made a mistake while testing.

    I checked out branch edge.

    Then, I tried sl setup and still I only get a blank page.

    Lastly, I tried npm run build in WebApp and I got the same error as before.

    C:\dev\SharpLab\source\WebApp>npm run build

> sharplab@0.0.0 build C:\dev\SharpLab\source\WebApp
> ts-node-script ./build.ts

(node:8228) ExperimentalWarning: The ESM module loader is experimental.
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for C:\dev\SharpLab\source\WebApp\build.ts
    at Loader.defaultGetFormat [as _getFormat] (internal/modules/esm/get_format.js:65:15)
    at Loader.getFormat (internal/modules/esm/loader.js:113:42)
    at Loader.getModuleJob (internal/modules/esm/loader.js:244:31)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at Loader.import (internal/modules/esm/loader.js:178:17)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sharplab@0.0.0 build: `ts-node-script ./build.ts`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sharplab@0.0.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Manuel\AppData\Roaming\npm-cache\_logs\2020-08-17T21_13_32_723Z-debug.log

  15. m-carrasco commented on Aug 17, 2020

    @m-carrasco
    m-carrasco
    on Aug 17, 2020
    Author

    Arghhh. Forget my last update, I did something wrong. On edge, npm run build works! \0/

    C:\dev\SharpLab\source\WebApp>npm run build

> sharplab@0.0.0 build C:\dev\SharpLab\source\WebApp
> ts-node-script ./build.ts

task default starting...
task icons starting...
task manifest starting...
task less starting...
task ts starting...
task ts-lint starting...
task manifest completed [94ms]
task icons completed [99ms]
task less completed [466ms]
task ts-lint completed [9.914s]
task ts-main starting...

./ts/app.ts → ./wwwroot/app.min.js...
created ./wwwroot/app.min.js in 14.3s
task ts-main completed [15.4s]
task ts completed [24.920s]
task html starting...
task html completed [43ms]
task default completed [24.969s]

  16. 1 remaining item

  17. ashmind commented on Aug 18, 2020

    @ashmind
    ashmind
    on Aug 18, 2020
    Owner

    Glad to hear it works! (even if the flow is awkward for now).
    I'll investigate sl setup && dotnet tye run issue further (when I have some time).

  18. m-carrasco commented on Jan 3, 2021

    @m-carrasco
    m-carrasco
    on Jan 3, 2021
    Author

    @ashmind How are you? I hope you are doing great.

    I found some time to resume my work with Sharplab. I started again by running sl setup (on a fresh repository) and I'm having the following error. This happens in main and edge branches.

    Command: sl setup

    Copy-Item : Cannot find path 'C:\Users\Manuel\Desktop\SharpLab\source\WebApp\.env.template' because it does not exist.
At C:\Users\Manuel\Desktop\SharpLab\#scripts\setup.ps1:12 char:5
+     Copy-Item './source/WebApp/.env.template' './source/WebApp/.env'
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\Users\Manuel...p\.env.template:String) [Copy-Item], ItemNotFoundExce
   ption
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.CopyItemCommand

  19. m-carrasco commented on Jan 3, 2021

    @m-carrasco
    m-carrasco
    on Jan 3, 2021
    Author

    @ashmind I think I got it:

    diff --git a/#scripts/setup.ps1 b/#scripts/setup.ps1
index ad37bc4..2e13826 100644
--- a/#scripts/setup.ps1
+++ b/#scripts/setup.ps1
@@ -8,8 +8,8 @@ if ($LastExitCode -ne 0) {
 }

 Write-Host "Creating stub .env" -ForegroundColor White
-if (!(Test-Path './source/WebApp/.env')) {
-    Copy-Item './source/WebApp/.env.template' './source/WebApp/.env'
+if (!(Test-Path './source/WebApp.Server/.env')) {^M
+    Copy-Item './source/WebApp.Server/.env.template' './source/WebApp.Server/.env'^M
 }

 Write-Host "Installing local tools" -ForegroundColor White

    Based on changes done here: 38e8412

  20. ashmind commented on Jan 3, 2021

    @ashmind
    ashmind
    on Jan 3, 2021
    Owner

    Yep that's very unlucky timing, it was OK for a while, but I literally just broke it yesterday and was going to revisit it (need to make sure dotnet tye run actually works as well).

  21. kkokosa commented on Mar 30, 2021

    @kkokosa
    kkokosa
    on Mar 30, 2021
    Contributor

    Hm.. any updates on this? Fresh repository gives the same error while sl setup. I could help but it seems pretty deep change made here...👀

  22. ashmind
    added this to the n+41 milestone on Mar 31, 2021
  23. ashmind
    added a commit that references this issue on Mar 31, 2021

    [gh-538] Fix local setup and run issues

    6afc3f2

  24. ashmind commented on Mar 31, 2021

    @ashmind
    ashmind
    on Mar 31, 2021
    Owner

    Sure -- applied a fix, please give it a try.

  25. kkokosa commented on May 21, 2021

    @kkokosa
    kkokosa
    on May 21, 2021
    Contributor

    Yes, it helped @ashmind, thank you! Issue may be closed.

  26. joelpryde commented on May 28, 2021

    @joelpryde
    joelpryde
    on May 28, 2021

    I seem to still be getting this on main branch:

    10:31:59 ERR] Failed to launch process for service webapp-assets_c2027d2c-6
System.ComponentModel.Win32Exception (2): The system cannot find the file specified.
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at Microsoft.Tye.ProcessUtil.RunAsync(String filename, String arguments, String workingDirectory, Boolean throwOnError, IDictionary`2 environmentVariables, Action`1 outputDataReceived, Action`1 errorDataReceived, Action`1 onStart, Action`1 onStop, CancellationToken cancellationToken) in /_/src/Microsoft.Tye.Core/ProcessUtil.cs:line 113
   at Microsoft.Tye.Hosting.ProcessRunner.<>c__DisplayClass8_0.<<LaunchService>g__RunApplicationAsync|0>d.MoveNext() in /_/src/Microsoft.Tye.Hosting/ProcessRunner.cs:line 402

    pwsh is in my path and I have run sl setup and npm run build successfully.

  27. kkokosa commented on May 28, 2021

    @kkokosa
    kkokosa
    on May 28, 2021
    Contributor

    Are you able to execute: pwsh -Command "npm run start" in source/WebApp? Beacause this is what Tye is trying to execute here.

  28. joelpryde commented on May 28, 2021

    @joelpryde
    joelpryde
    on May 28, 2021

    I am not unfortunately:

    C:\Users\joelp\Documents\repos\SharpLab\source\WebApp>pwsh -Command "npm run start"

...

TypeError: Cannot read property 'split' of undefined
    at oldowan_1.task.watch (C:\Users\joelp\Documents\repos\SharpLab\source\WebApp\scripts.ts:80:10)
    at task.run (C:\Users\joelp\Documents\repos\SharpLab\source\WebApp\node_modules\oldowan\dist\index.js:74:13)
    at C:\Users\joelp\Documents\repos\SharpLab\source\WebApp\scripts.ts:90:5
    at task.run (C:\Users\joelp\Documents\repos\SharpLab\source\WebApp\node_modules\oldowan\dist\index.js:74:13)
    at async Promise.all (index 1)
    at C:\Users\joelp\Documents\repos\SharpLab\source\WebApp\scripts.ts:149:5
    at task.run (C:\Users\joelp\Documents\repos\SharpLab\source\WebApp\node_modules\oldowan\dist\index.js:74:13)
    at Object.task.run (C:\Users\joelp\Documents\repos\SharpLab\source\WebApp\node_modules\oldowan\dist\index.js:74:13)
    at Object.build (C:\Users\joelp\Documents\repos\SharpLab\source\WebApp\node_modules\oldowan\dist\index.js:107:9)
task ts failed: task asm failed
task build failed: task ts failed
task start failed: task build failed

    Strangely doing a git clean and re-running sl setup did let me run pwsh -Command "npm run start" ok
    (or at least, I can get to the following:

    Starting up http-server, serving C:\Users\joelp\Documents\repos\SharpLab\source\WebApp/public
Available on:
  http://192.168.68.113:54200
  http://127.0.0.1:54200
Hit CTRL-C to stop the server
rollup v2.9.1
bundles ./ts/app.ts → public\1622206636676\app.min.js...
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db
created public\1622206636676\app.min.js in 16.8s

[2021-05-28 14:58:03] waiting for changes...

    but I still get the same System.ComponentModel.Win32Exception error on sl run (diffed the error/callstack to make sure).

  29. ashmind commented on Jun 20, 2021

    @ashmind
    ashmind
    on Jun 20, 2021
    Owner
    Cannot read property 'split' of undefined

    Hmm -- looking at the code it would seem like you are missing source/WebApp/components/internal/codemirror/mode-asm-instructions.txt for some reason. I'll have to add more logging to this. (might take a bit of time given current priorities)

  30. ashmind
    removed this from the n+41 milestone on Jun 20, 2021

  31. Meir017 commented on Jun 2, 2025

    @Meir017
    Meir017
    on Jun 2, 2025

    Try #1365

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions