Skip to content
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

FileSystemException: Directory watcher closed unexpectedly #3150

Closed
insinfo opened this issue Jul 21, 2021 · 38 comments · Fixed by #3165
Closed

FileSystemException: Directory watcher closed unexpectedly #3150

insinfo opened this issue Jul 21, 2021 · 38 comments · Fixed by #3165

Comments

@insinfo
Copy link

insinfo commented Jul 21, 2021

FileSystemException: Directory watcher closed unexpectedly

  • Dart SDK Version 2.12.4
  • Whether you are using Windows / Linux
  • Whether you are using Chrome
pubspec.yaml
name: cmpop_browser
description: A web app that uses AngularDart Components

environment:
  sdk: ">=2.7.1 <3.0.0"

dependencies:
  angular: ^6.0.0
  angular_components: ^1.0.2
  angular_router: ^2.0.0
  angular_forms: ^3.0.0
  sembast_web: ^1.2.0
  angular_recaptcha: ^0.1.5
  stream_transform: #^0.0.19
  sass_builder: ^2.1.3
  intl: ^0.16.1
  uuid: ^2.2.2
  crossplat_objectid: ^2.1.4  
  http: ^0.12.2
  quiver: ^2.1.5

dev_dependencies: 
  angular_test: ^3.0.0                                                                                                 
  build_runner: ^1.10.4                                                                                                   
  build_test: ^1.3.0                                                                                              
  build_web_compilers: ^2.12.0                                                                                
  pedantic: ^1.9.2                                                                                               
  test: ^1.15.4
webdev build
[INFO] Reading cached asset graph completed, took 722ms
[INFO] Checking for updates since last build completed, took 1.1s
[INFO] Running build completed, took 437ms
[INFO] Caching finalized dependency graph completed, took 581ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
@jakemac53
Copy link
Contributor

We can't unfortunately do much about this error - if you are seeing it regularly you can try using the --use-polling-watcher flag, but that may consume more resources than normal watch mode.

@insinfo
Copy link
Author

insinfo commented Jul 22, 2021

@jakemac53
yes i am seeing this regurlamnete after updating webdev and running pub update
What is causing this, as this problem did not occur before

@jakemac53
Copy link
Contributor

We are just handling an exception from your file system so it is a bit hard to say exactly what the issue is, but you may have ran out of file handles or something like that. It is possible that rebooting your computer could fix it also... maybe some rogue process somewhere is hogging a lot of file handles.

@insinfo
Copy link
Author

insinfo commented Jul 22, 2021

Thank you very much for the feedback, I will check your suggestions

@jakemac53
Copy link
Contributor

Actually thinking more on this... @annagrin did we just release a webdev version that allows for higher parallelism when serving files? Maybe that is what is causing you to run out of file handles.

@jakemac53
Copy link
Contributor

@insinfo I think that change was specific to the mode that webdev uses for build_runner, could you try running normal standalone build_runner: pub run build_runner serve web and see if you still experience the issue? That might help narrow things down.

@insinfo
Copy link
Author

insinfo commented Jul 22, 2021

@jakemac53
I tested it with "pub run build_runner serve web" and "pub run build_runner build web" and it worked perfectly.

I took the test several times.
I found that the problem is only in the "webdev build" when run at odd time, at even time the error doesn't occur.

As can be seen in the log, the error only occurs the second time.

PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 856ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 457ms
[INFO] Caching finalized dependency graph completed, took 553ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 22ms
[INFO] Creating merged output dir `build` completed, took 781ms
[INFO] Succeeded after 4.3s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 932ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 438ms
[INFO] Caching finalized dependency graph completed, took 533ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 205ms
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 753ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 424ms
[INFO] Caching finalized dependency graph completed, took 543ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 21ms
[INFO] Creating merged output dir `build` completed, took 725ms
[INFO] Writing asset manifest completed, took 6ms
[INFO] Succeeded after 4.2s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 738ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 436ms
[INFO] Caching finalized dependency graph completed, took 555ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 753ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 424ms
[INFO] Caching finalized dependency graph completed, took 543ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 21ms
[INFO] Creating merged output dir `build` completed, took 725ms
[INFO] Writing asset manifest completed, took 6ms
[INFO] Succeeded after 4.2s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 738ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 436ms
[INFO] Caching finalized dependency graph completed, took 555ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 753ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 424ms
[INFO] Caching finalized dependency graph completed, took 543ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 21ms
[INFO] Creating merged output dir `build` completed, took 725ms
[INFO] Writing asset manifest completed, took 6ms
[INFO] Succeeded after 4.2s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 738ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 436ms
[INFO] Caching finalized dependency graph completed, took 555ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 753ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 424ms
[INFO] Caching finalized dependency graph completed, took 543ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 21ms
[INFO] Creating merged output dir `build` completed, took 725ms
[INFO] Writing asset manifest completed, took 6ms
[INFO] Succeeded after 4.2s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 738ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 436ms
[INFO] Caching finalized dependency graph completed, took 555ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 753ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 424ms
[INFO] Caching finalized dependency graph completed, took 543ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 21ms
[INFO] Creating merged output dir `build` completed, took 725ms
[INFO] Writing asset manifest completed, took 6ms
[INFO] Succeeded after 4.2s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 738ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 436ms
[INFO] Caching finalized dependency graph completed, took 555ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 753ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 424ms
[INFO] Caching finalized dependency graph completed, took 543ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 21ms
[INFO] Creating merged output dir `build` completed, took 725ms
[INFO] Writing asset manifest completed, took 6ms
[INFO] Succeeded after 4.2s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 738ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 436ms
[INFO] Caching finalized dependency graph completed, took 555ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 753ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 424ms
[INFO] Caching finalized dependency graph completed, took 543ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 21ms
[INFO] Creating merged output dir `build` completed, took 725ms
[INFO] Writing asset manifest completed, took 6ms
[INFO] Succeeded after 4.2s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 738ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 436ms
[INFO] Caching finalized dependency graph completed, took 555ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 753ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 424ms
[INFO] Caching finalized dependency graph completed, took 543ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[INFO] Deleting previous outputs in `build` completed, took 21ms
[INFO] Creating merged output dir `build` completed, took 725ms
[INFO] Writing asset manifest completed, took 6ms
[INFO] Succeeded after 4.2s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 738ms
[INFO] Checking for updates since last build completed, took 1.2s
[INFO] Running build completed, took 436ms
[INFO] Caching finalized dependency graph completed, took 555ms
[INFO] Reading manifest at build\.build.manifest completed, took 0ms
[SEVERE]
[SEVERE]
[SEVERE] You have hit a bug in build_runner
[SEVERE] Please file an issue with reproduction steps at https://github.com/dart-lang/build/issues
[SEVERE]
[SEVERE]
[SEVERE] FileSystemException: Directory watcher closed unexpectedly, path = 'd:\mydartprojects\cmpop\cmpop_browser'
[SEVERE] dart:isolate  _RawReceivePortImpl._handleMessage
[SEVERE]

I noticed that in the command "webdev serves" the problem does not occur, and also that in linux the problem does not occur

@jakemac53
Copy link
Contributor

That is very odd indeed that it is happening with webdev build. We should not even be setting up file watchers in that case?

@jakemac53 jakemac53 reopened this Jul 22, 2021
@jakemac53
Copy link
Contributor

Re-opening as that seems like a different issue, maybe daemon mode always sets up watchers but I wonder if we can somehow avoid this.

@insinfo
Copy link
Author

insinfo commented Jul 22, 2021

I downgraded dart 2.12 to 2.10 and ran some more tests and saw that with dart 2.10 the problem does not occur

@insinfo
Copy link
Author

insinfo commented Jul 22, 2021

in Dart 2.13.4 the problem persists

@jakemac53
Copy link
Contributor

I downgraded dart 2.12 to 2.10 and ran some more tests and saw that with dart 2.10 the problem does not occur

I think that probably this is related to your version solve (you likely got a very different set of packages in 2.10).

@jakemac53
Copy link
Contributor

@annagrin I do think this is most likely related to the recent asset server change, given the timing and description.

@annagrin
Copy link
Contributor

Looking!

@annagrin
Copy link
Contributor

annagrin commented Jul 26, 2021

Actually thinking more on this... @annagrin did we just release a webdev version that allows for higher parallelism when serving files? Maybe that is what is causing you to run out of file handles.

We released dwds 11.1.2, but webdev from pub global activate and SDK 2.13.4 brings dwds version dwds 11.0.2 for me, so it does not contain my latest changes to the http clients.

@insinfo I tried to repro the failure in example directory (on mac and windows) with the same dependencies listed above, with SDK 2.12 and 2.13.4, no luck. Is it possible to share your repro with us?

@jakemac53 On windows, webdev.bat build gives this output:

Can't load Kernel binary: Invalid binary format version.
[INFO] Reading cashed asset graph completed, took 318 ms
... 
[INFO] Succeded after 883ms with 0 outputs (0 actions)

And finishes successfully. Looks like the build tries to run something built with another SDK version in a isolate - do you know what it might be?

@jakemac53
Copy link
Contributor

And finishes successfully. Looks like the build tries to run something built with another SDK version in a isolate - do you know what it might be?

That is normal output from pub after updating your sdk (its a bit weird but... 🤷‍♂️ )

@jakemac53
Copy link
Contributor

If we aren't pulling down the latest asset server changes @annagrin then you probably don't need to investigate much further yourself (its also fairly unlikely you will be able to actually reproduce the issue).

@annagrin
Copy link
Contributor

@jakemac53 I don't know if it helps but I thought the watcher should restart on this failure, according to the fix for dart-lang/sdk#38853. Not sure if something changed there...

@insinfo
Copy link
Author

insinfo commented Jul 27, 2021

@annagrin
I put a copy without sensitive data of the project on github, to demonstrate the problem
https://github.com/insinfo/cmpop/tree/main/cmpop_browser

Did you run on a clean windows virtual machine? Or on a working machine?

I ran it on three working windows 10 computers, one Version 20H2 build 19042.1110 and two other Version 21H1 build 19043.1110 and they all had the same problem.

dart version 2.13.4

It's strange because in dart 2.10 this problem doesn't happen

dart-lang/sdk#37233

Apparently this problem had been resolved, but it seems to have returned from dart 2.12.

the strangest thing is that on the first run it goes well, but on the second time I run "webdev build" the problem occurs

@annagrin
Copy link
Contributor

annagrin commented Jul 27, 2021

Apparently this problem had been resolved, but it seems to have returned from dart 2.12.

it was resolved in the dart-lang/watcher, which just restarted the watcher recursively as infinitum. But I does not seem to restart here, I am not sure why.

the strangest thing is that on the first run it goes well, but on the second time I run "webdev build" the problem occurs

Yeah I have seen something like that with webdev serve in situations when the daemon from the first run was still running and the second one would connect to it, not sure if this is possible here as I am not very familiar with the implementation details. In my case the problem would disappear if I killed all suspicious dart processes in between builds.

@annagrin
Copy link
Contributor

Update: brushed up on webdev build implementation details:) I does indeed use the daemon, so I wonder if the problem is that the daemon does not exit after the build is done. @insinfo let me know if killing dart processes in between build helps in your case.

@annagrin
Copy link
Contributor

forgot to anser this:

Did you run on a clean windows virtual machine? Or on a working machine?

I run it on my windows laptop. I will try to repro now that I have your code.

@annagrin
Copy link
Contributor

@insinfo I can very predictably repro the issue on my windows laptop using your code. There are no dart processes left in between runs, so it looks like the issue is not due to webdev setup.

@jakemac53 I think the issue might be in the build_runner after all.

@jakemac53
Copy link
Contributor

jakemac53 commented Jul 28, 2021

So one difference with webdev build compared with other commands is that it creates an output directory (for deployment). When this happens the watcher gets flooded with events, because we watch the root of the package. We discard those events, but there are a lot, and on the 2nd build there are likely even more events because we delete the old files and write the new ones.

@insinfo If you delete the output directory (defaults to build/ I think?) between builds, then does that make it stop happening on the second build?

@insinfo
Copy link
Author

insinfo commented Jul 28, 2021

yes, deleting the directory every time it compiles, the error doesn't occur

PS D:\MyDartProjects\cmpop\cmpop_browser> rm -r .\build\
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 728ms
[INFO] Checking for updates since last build completed, took 1.1s
[INFO] Running build completed, took 406ms
[INFO] Caching finalized dependency graph completed, took 509ms
[INFO] Creating merged output dir `build` completed, took 1.0s
[INFO] Writing asset manifest completed, took 4ms
[INFO] Succeeded after 4.3s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> rm -r .\build\
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 735ms
[INFO] Checking for updates since last build completed, took 1.1s
[INFO] Running build completed, took 414ms
[INFO] Caching finalized dependency graph completed, took 507ms
[INFO] Creating merged output dir `build` completed, took 621ms
[INFO] Writing asset manifest completed, took 3ms
[INFO] Succeeded after 3.9s with 0 outputs (0 actions)
PS D:\MyDartProjects\cmpop\cmpop_browser> rm -r .\build\
PS D:\MyDartProjects\cmpop\cmpop_browser> webdev build
[INFO] Reading cached asset graph completed, took 729ms
[INFO] Checking for updates since last build completed, took 1.1s
[INFO] Running build completed, took 420ms
[INFO] Caching finalized dependency graph completed, took 513ms
[INFO] Creating merged output dir `build` completed, took 1.1s
[INFO] Writing asset manifest completed, took 5ms
[INFO] Succeeded after 4.4s with 0 outputs (0 actions)

@jakemac53
Copy link
Contributor

Ok, so it seems like the problem is to do with that build/ directory. Note that you can use I think --output=NONE to disable this.

I don't know what would cause this to not occur on older sdks though.

@annagrin
Copy link
Contributor

The fix that was done in watcher just restarted it forever, but it seems like it does not anymore in this example. I wonder if something changed in the watcher or the use of it...

@annagrin
Copy link
Contributor

@jakemac53 Is it possible to configure the watcher in build_daemon not to monitor that directory?

@jakemac53
Copy link
Contributor

It isn't practical to unfortunately, no. We can't exclude certain dirs from the watcher. And we have to watch the root dir of the package to detect file/directory changes at that level.

@annagrin
Copy link
Contributor

annagrin commented Jul 29, 2021

@jakemac53 I've got a theory - could it be this change: #2505
Looks like we exit immediately after watcher reports its error, so it it does not help that it is restarting...

I've tried to verify that by using my local build clone but got stuck in dependency resolution loop....

@jakemac53
Copy link
Contributor

Should we just be ignoring these errors? If we did, would the watcher would just restart?

@annagrin
Copy link
Contributor

I think so... but it would be nice to test:)

@insinfo
Copy link
Author

insinfo commented Aug 5, 2021

#3167
It was not possible to use this solution as it is incompatible with angular

https://github.com/insinfo/app

Resolving dependencies...
Because no versions of sass_builder match >2.1.3 <2.1.4 and sass_builder >=2.1.4 depends on build_config ^1.0.0, sass_builder >2.1.3 requires build_config ^1.0.0.
And because sass_builder 2.1.3 depends on build >=0.12.5 <2.0.0, sass_builder >=2.1.3 requires build >=0.12.5 <2.0.0 or build_config ^1.0.0.
And because every version of build_runner from git depends on both build >=2.0.0 <2.1.0 and build_config >=0.4.7 <0.4.8, build_runner from git is incompatible with sass_builder >=2.1.3.
So, because turismo_browser depends on both sass_builder ^2.1.3 and build_runner from git, version solving failed.
exit code 1
--
[turismo_browser] dart pub get
Resolving dependencies...
Because every version of build_runner from git depends on build >=2.0.0 <2.1.0 and angular_components >=1.0.0 depends on build ^1.0.0, build_runner from git is incompatible with angular_components >=1.0.0.
So, because turismo_browser depends on both angular_components ^1.0.2 and build_runner from git, version solving failed.
exit code 1
name: turismo_browser
description: A web app that uses AngularDart Components
# version: 1.0.0
# homepage: https://www.example.com

environment:
  sdk: '>=2.10.0 <3.0.0'

dependencies:
  angular: ^6.0.0
  angular_components: ^1.0.2
  angular_router: ^2.0.0
  angular_forms: ^3.0.0
  sembast_web: ^1.2.0
  angular_recaptcha: ^0.1.5
  stream_transform: #^0.0.19

  sass_builder: any
  intl: '>=0.16.1 < 0.17.9'
  uuid: '>=2.2.2 < 3.0.9'
  crossplat_objectid: ^2.1.4  
  #dio: ^3.0.10
  http: '>=0.12.2 < 0.13.5'
  quiver: ^2.1.5

  turismo_core:
    path: ../turismo_core

dependency_overrides:
  build_runner:
    git:
      url: https://github.com/dart-lang/build.git
      ref: backport-watcher-fix
      path: build_runner

dev_dependencies: 
  angular_test: ^3.0.0                                                                                                 
  build_runner: ^1.10.4                                                                                                   
  build_test: ^1.3.0                                                                                              
  build_web_compilers: ^2.12.0                                                                                
  pedantic: ^1.9.2                                                                                               
  test: ^1.15.4

build_runner: ^1.10.4

@annagrin
Copy link
Contributor

@jake @insinfo is this really solved? Do we need to make an update in an earlier version of build_runner?

@annagrin
Copy link
Contributor

Related: dart-lang/webdev#1362

@jakemac53
Copy link
Contributor

I did backport this to an earlier version of build_runner yes (version 1.11.1+1 which we confirmed you can get with angular).

@insinfo
Copy link
Author

insinfo commented Aug 19, 2021

Has this version 1.11.1+1 been published?

@jakemac53
Copy link
Contributor

Yes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants