Unable to find modules for some sources. No meaningful information provided on compile error.

flutter build web --verbose
[  +26 ms] executing: [/Users/omontoya/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +41 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 919cc97f6a3067faf84a0946132319933d0743a5
[        ] executing: [/Users/omontoya/flutter/] git describe --match v*.*.* --first-parent --long --tags
[  +23 ms] Exit code 0 from: git describe --match v*.*.* --first-parent --long --tags
[        ] v1.10.5-29-g919cc97f6
[   +8 ms] executing: [/Users/omontoya/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +9 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] executing: [/Users/omontoya/flutter/] git ls-remote --get-url origin
[   +8 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +53 ms] executing: [/Users/omontoya/flutter/] git rev-parse --abbrev-ref HEAD
[  +10 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] master
[   +6 ms] executing: sw_vers -productName
[  +15 ms] Exit code 0 from: sw_vers -productName
[        ] Mac OS X
[        ] executing: sw_vers -productVersion
[  +14 ms] Exit code 0 from: sw_vers -productVersion
[        ] 10.14.6
[        ] executing: sw_vers -buildVersion
[  +13 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 18G95
[  +13 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[ +282 ms] Compiling lib/main.dart for the Web...
[+8103 ms] Starting daemon...
[ +247 ms] Initializing inputs
[  +11 ms] Reading cached asset graph...
[ +278 ms] Reading cached asset graph completed, took 276ms

[ +254 ms] Checking for updates since last build...
[+1008 ms] Checking for updates since last build completed, took 1.0s

[  +14 ms] Initializing inputs
[   +2 ms] Reading cached asset graph...
[        ] Reading cached asset graph completed, took 276ms
[        ] Checking for updates since last build...
[        ] Checking for updates since last build completed, took 1.0s
[+1250 ms] About to build [web, test]...
[   +6 ms] Running build...
[ +254 ms] Running build completed, took 122ms

[   +1 ms] Caching finalized dependency graph...
[   +9 ms] Caching finalized dependency graph completed, took 168ms

[  +10 ms] Unable to find modules for some sources, this is usually the result of either a
           bad import, a missing dependency in a package (or possibly a dev_dependency
           needs to move to a real dependency), or a build failure (if importing a
           generated file).

           Please check the following imports:

[   +1 ms] #0      Module.computeTransitiveDependencies (package:build_modules/src/modules.dart:172:7)
           <asynchronous suspension>
           #1      _ensureTransitiveJsModules (package:build_web_compilers/src/dev_compiler_bootstrap.dart:144:37)
           <asynchronous suspension>
           #2      bootstrapDdc (package:build_web_compilers/src/dev_compiler_bootstrap.dart:37:33)
           <asynchronous suspension>
           #3      FlutterWebTestEntrypointBuilder.build (package:flutter_tools/src/build_runner/build_script.dart:221:11)
           <asynchronous suspension>
           #4      runBuilder.buildForInput (package:build/src/generate/run_builder.dart:45:21)
           <asynchronous suspension>
           #5      MappedListIterable.elementAt (dart:_internal/iterable.dart:415:29)
           #6      ListIterator.moveNext (dart:_internal/iterable.dart:344:26)
           #7      Future.wait (dart:async/future.dart:393:26)
           #8      runBuilder.<anonymous closure> (package:build/src/generate/run_builder.dart:51:36)
           #9      _rootRun (dart:async/zone.dart:1124:13)
           #10     _CustomZone.run (dart:async/zone.dart:1021:19)
           #11     _runZoned (dart:async/zone.dart:1516:10)
           #12     runZoned (dart:async/zone.dart:1500:12)
           #13     scopeLogAsync (package:build/src/builder/logging.dart:22:3)
           #14     runBuilder (package:build/src/generate/run_builder.dart:51:9)
           <asynchronous suspension>
           #15     _SingleBuild._runForInput.<anonymous closure>.<anonymous closure>.<anonymous closure>
           (package:build_runner_core/src/generate/build_impl.dart:472:19)
           #16     _NoOpBuilderActionTracker.trackStage (package:build_runner_core/src/generate/performance_tracker.dart:300:15)
           #17     _SingleBuild._runForInput.<anonymous closure>.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:470:23)
           <asynchronous suspension>
           #18     NoOpTimeTracker.track (package:timing/src/timing.dart:222:44)
           #19     _SingleBuild._runForInput.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:429:22)
           #20     Pool.withResource (package:pool/pool.dart:127:28)
           <asynchronous suspension>
           #21     _SingleBuild._runForInput (package:build_runner_core/src/generate/build_impl.dart:425:17)
           #22     _SingleBuild._runBuilder.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:373:38)
           #23     MappedIterator.moveNext (dart:_internal/iterable.dart:393:18)
           #24     Future.wait (dart:async/future.dart:393:26)
           #25     _SingleBuild._runBuilder (package:build_runner_core/src/generate/build_impl.dart:372:36)
           <asynchronous suspension>
           #26     _SingleBuild._runPhases.<anonymous closure>.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:319:20)
           <asynchronous suspension>
           #27     _NoOpBuildPerformanceTracker.trackBuildPhase (package:build_runner_core/src/generate/performance_tracker.dart:184:15)
           #28     _SingleBuild._runPhases.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:315:47)
           <asynchronous suspension>
           #29     NoOpTimeTracker.track (package:timing/src/timing.dart:222:44)
           #30     _SingleBuild._runPhases (package:build_runner_core/src/generate/build_impl.dart:309:32)
           #31     logTimedAsync (package:build_runner_core/src/logging/logging.dart:25:30)
           <asynchronous suspension>
           #32     _SingleBuild._safeBuild.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:266:26)
           <asynchronous suspension>
           #33     _rootRun (dart:async/zone.dart:1124:13)
           #34     _CustomZone.run (dart:async/zone.dart:1021:19)
           #35     _runZoned (dart:async/zone.dart:1516:10)
           #36     runZoned (dart:async/zone.dart:1500:12)
           #37     _SingleBuild._safeBuild (package:build_runner_core/src/generate/build_impl.dart:261:5)
           #38     _SingleBuild.run (package:build_runner_core/src/generate/build_impl.dart:208:24)
           <asynchronous suspension>
           #39     BuildImpl.run (package:build_runner_core/src/generate/build_impl.dart:96:42)
           #40     BuildRunnerDaemonBuilder.build (package:build_runner/src/daemon/daemon_builder.dart:100:35)
           <asynchronous suspension>
           #41     Server._build.<anonymous closure> (package:build_daemon/src/server.dart:122:25)
           #42     Pool.withResource (package:pool/pool.dart:127:28)
           <asynchronous suspension>
           #43     Server._build (package:build_daemon/src/server.dart:119:13)
           #44     Server.listen.<anonymous closure>.<anonymous closure> (package:build_daemon/src/server.dart:85:17)
           <asynchronous suspension>
           #45     _rootRunUnary (dart:async/zone.dart:1132:38)
           #46     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #47     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
           #48     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
           #49     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
           #50     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
           #51     _StreamController._add (dart:async/stream_controller.dart:640:7)
           #52     _StreamController.add (dart:async/stream_controller.dart:586:5)
           #53     new WebSocketImpl.fromSocket.<anonymous closure> (package:web_socket_channel/src/copy/web_socket_impl.dart:719:21)
           #54     _rootRunUnary (dart:async/zone.dart:1132:38)
           #55     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #56     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
           #57     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
           #58     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
           #59     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:68:11)
           #60     _EventSinkWrapper.add (dart:async/stream_transformers.dart:15:11)
           #61     _WebSocketProtocolTransformer._messageFrameEnd (package:web_socket_channel/src/copy/web_socket_impl.dart:316:22)
           #62     _WebSocketProtocolTransformer.add (package:web_socket_channel/src/copy/web_socket_impl.dart:214:46)
           #63     _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:120:24)
           #64     _rootRunUnary (dart:async/zone.dart:1132:38)
           #65     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #66     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
           #67     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
           #68     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
           #69     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
           #70     _StreamController._add (dart:async/stream_controller.dart:640:7)
           #71     _StreamController.add (dart:async/stream_controller.dart:586:5)
           #72     _Socket._onData (dart:io-patch/socket_patch.dart:1829:41)
           #73     _rootRunUnary (dart:async/zone.dart:1136:13)
           #74     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #75     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
           #76     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
           #77     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
           #78     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
           #79     _StreamController._add (dart:async/stream_controller.dart:640:7)
           #80     _StreamController.add (dart:async/stream_controller.dart:586:5)
           #81     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1377:33)
           #82     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:897:14)
           #83     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #84     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #85     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
           #86     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

[   +5 ms] Unable to find modules for some sources, this is usually the result of either a
           bad import, a missing dependency in a package (or possibly a dev_dependency
           needs to move to a real dependency), or a build failure (if importing a
           generated file).

           Please check the following imports:

[        ] #0      Module.computeTransitiveDependencies (package:build_modules/src/modules.dart:172:7)
           <asynchronous suspension>
           #1      bootstrapDart2Js (package:flutter_tools/src/build_runner/build_script.dart:425:45)
           <asynchronous suspension>
           #2      FlutterWebEntrypointBuilder.build (package:flutter_tools/src/build_runner/build_script.dart:248:13)
           <asynchronous suspension>
           #3      runBuilder.buildForInput (package:build/src/generate/run_builder.dart:45:21)
           <asynchronous suspension>
           #4      MappedListIterable.elementAt (dart:_internal/iterable.dart:415:29)
           #5      ListIterator.moveNext (dart:_internal/iterable.dart:344:26)
           #6      Future.wait (dart:async/future.dart:393:26)
           #7      runBuilder.<anonymous closure> (package:build/src/generate/run_builder.dart:51:36)
           #8      _rootRun (dart:async/zone.dart:1124:13)
           #9      _CustomZone.run (dart:async/zone.dart:1021:19)
           #10     _runZoned (dart:async/zone.dart:1516:10)
           #11     runZoned (dart:async/zone.dart:1500:12)
           #12     scopeLogAsync (package:build/src/builder/logging.dart:22:3)
           #13     runBuilder (package:build/src/generate/run_builder.dart:51:9)
           <asynchronous suspension>
           #14     _SingleBuild._runForInput.<anonymous closure>.<anonymous closure>.<anonymous closure>
           (package:build_runner_core/src/generate/build_impl.dart:472:19)
           #15     _NoOpBuilderActionTracker.trackStage (package:build_runner_core/src/generate/performance_tracker.dart:300:15)
           #16     _SingleBuild._runForInput.<anonymous closure>.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:470:23)
           <asynchronous suspension>
           #17     NoOpTimeTracker.track (package:timing/src/timing.dart:222:44)
           #18     _SingleBuild._runForInput.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:429:22)
           #19     Pool.withResource (package:pool/pool.dart:127:28)
           <asynchronous suspension>
           #20     _SingleBuild._runForInput (package:build_runner_core/src/generate/build_impl.dart:425:17)
           #21     _SingleBuild._runBuilder.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:373:38)
           #22     MappedIterator.moveNext (dart:_internal/iterable.dart:393:18)
           #23     Future.wait (dart:async/future.dart:393:26)
           #24     _SingleBuild._runBuilder (package:build_runner_core/src/generate/build_impl.dart:372:36)
           <asynchronous suspension>
           #25     _SingleBuild._runPhases.<anonymous closure>.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:319:20)
           <asynchronous suspension>
           #26     _NoOpBuildPerformanceTracker.trackBuildPhase (package:build_runner_core/src/generate/performance_tracker.dart:184:15)
           #27     _SingleBuild._runPhases.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:315:47)
           <asynchronous suspension>
           #28     NoOpTimeTracker.track (package:timing/src/timing.dart:222:44)
           #29     _SingleBuild._runPhases (package:build_runner_core/src/generate/build_impl.dart:309:32)
           #30     logTimedAsync (package:build_runner_core/src/logging/logging.dart:25:30)
           <asynchronous suspension>
           #31     _SingleBuild._safeBuild.<anonymous closure> (package:build_runner_core/src/generate/build_impl.dart:266:26)
           <asynchronous suspension>
           #32     _rootRun (dart:async/zone.dart:1124:13)
           #33     _CustomZone.run (dart:async/zone.dart:1021:19)
           #34     _runZoned (dart:async/zone.dart:1516:10)
           #35     runZoned (dart:async/zone.dart:1500:12)
           #36     _SingleBuild._safeBuild (package:build_runner_core/src/generate/build_impl.dart:261:5)
           #37     _SingleBuild.run (package:build_runner_core/src/generate/build_impl.dart:208:24)
           <asynchronous suspension>
           #38     BuildImpl.run (package:build_runner_core/src/generate/build_impl.dart:96:42)
           #39     BuildRunnerDaemonBuilder.build (package:build_runner/src/daemon/daemon_builder.dart:100:35)
           <asynchronous suspension>
           #40     Server._build.<anonymous closure> (package:build_daemon/src/server.dart:122:25)
           #41     Pool.withResource (package:pool/pool.dart:127:28)
           <asynchronous suspension>
           #42     Server._build (package:build_daemon/src/server.dart:119:13)
           #43     Server.listen.<anonymous closure>.<anonymous closure> (package:build_daemon/src/server.dart:85:17)
           <asynchronous suspension>
           #44     _rootRunUnary (dart:async/zone.dart:1132:38)
           #45     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #46     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
           #47     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
           #48     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
           #49     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
           #50     _StreamController._add (dart:async/stream_controller.dart:640:7)
           #51     _StreamController.add (dart:async/stream_controller.dart:586:5)
           #52     new WebSocketImpl.fromSocket.<anonymous closure> (package:web_socket_channel/src/copy/web_socket_impl.dart:719:21)
           #53     _rootRunUnary (dart:async/zone.dart:1132:38)
           #54     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #55     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
           #56     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
           #57     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
           #58     _SinkTransformerStreamSubscription._add (dart:async/stream_transformers.dart:68:11)
           #59     _EventSinkWrapper.add (dart:async/stream_transformers.dart:15:11)
           #60     _WebSocketProtocolTransformer._messageFrameEnd (package:web_socket_channel/src/copy/web_socket_impl.dart:316:22)
           #61     _WebSocketProtocolTransformer.add (package:web_socket_channel/src/copy/web_socket_impl.dart:214:46)
           #62     _SinkTransformerStreamSubscription._handleData (dart:async/stream_transformers.dart:120:24)
           #63     _rootRunUnary (dart:async/zone.dart:1132:38)
           #64     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #65     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
           #66     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
           #67     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
           #68     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
           #69     _StreamController._add (dart:async/stream_controller.dart:640:7)
           #70     _StreamController.add (dart:async/stream_controller.dart:586:5)
           #71     _Socket._onData (dart:io-patch/socket_patch.dart:1829:41)
           #72     _rootRunUnary (dart:async/zone.dart:1136:13)
           #73     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
           #74     _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
           #75     _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
           #76     _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
           #77     _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
           #78     _StreamController._add (dart:async/stream_controller.dart:640:7)
           #79     _StreamController.add (dart:async/stream_controller.dart:586:5)
           #80     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1377:33)
           #81     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:897:14)
           #82     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
           #83     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
           #84     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
           #85     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

[   +2 ms] Failed after 305ms
[  +13 ms] Compiling lib/main.dart for the Web... (completed in 11.5s)
[   +4 ms] "flutter web" took 11,848ms.
Failed to compile lib/main.dart for the Web.

#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      buildWeb (package:flutter_tools/src/web/compile.dart:62:5)
<asynchronous suspension>
#2      BuildWebCommand.runCommand (package:flutter_tools/src/commands/build_web.dart:56:11)
<asynchronous suspension>
#3      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:527:18)
#4      _asyncThenWrapperHelper.<anonymous closure> (dart:async-patch/async_patch.dart:71:64)
#5      _rootRunUnary (dart:async/zone.dart:1132:38)
#6      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#7      _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#8      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#9      Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#10     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#11     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:552:7)
#12     _rootRun (dart:async/zone.dart:1124:13)
#13     _CustomZone.run (dart:async/zone.dart:1021:19)
#14     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#15     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:963:23)
#16     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#17     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#18     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#19     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.10.6-pre.29, on Mac OS X 10.14.6 18G95, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.5)
[✓] IntelliJ IDEA Community Edition (version 2019.2)
[✓] VS Code
[✓] Connected device (2 available)
• No issues found!

This has been "fixed" at master - "flutter build web" was never supposed to allow creating web debug builds.

Nevermind, possibly same issue as https://github.com/flutter/flutter/issues/40996

@vsmenon does this look dart:io related?

I don't think it'd be related to dart:io directly - those sources are in the SDK itself.
@jakemac53 @grouma - anything we can do to improve that error?

We have seen a few reports of this from flutter_web - one thing I noticed here is that it looks like this is doing a dart2js compile, which I didn't think we would ever do through build_runner for flutter_web (I thought it used dart2js directly)?
We previously added support to bootstrapDdc to skip these checks entirely, and I did add them to  bootstrapDart2js at the same time but the previous functionality we had only existed on bootstrapDdc (it let you skip the checks on certain whitelisted packages).
This message does try to give you the actual location of the file with the unsupported import, so something is going wrong and it wasn't able to find it.

@jonahwilliams will https://github.com/flutter/flutter/issues/41951 also fix this issue?

Yes - that workflow won't do this check at all.

Ok, closing as duplicate of #41951 then.

Thanks @jakemac53. I don't know why, but just waiting 3 days, switching flutter channels 3 times and running flutter clean 3 times fixed the problem 🙃😃


STATISTICS-69: Add an unconditioned exact test for 2x2 tables

Support computing a test conditioned on the column sums using a configurable method to identify more extreme tables. The p-value is computed by maximising the probability over the more extreme tables.
The Commons Math BrentOptimizer has been extracted for use as a univariate function optimizer. This has been modified to remove unused functionality and support bounds on the function.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@85cdb9f). Click here to learn what that means.
The diff coverage is 99.26%.

@@            Coverage Diff            @@
##             master      #43   +/-   ##
=========================================
  Coverage          ?   99.82%
  Complexity        ?     1688
=========================================
  Files             ?       65
  Lines             ?     4472
  Branches          ?      756
=========================================
  Hits              ?     4464
  Misses            ?        4
  Partials          ?        4

Impacted Files
Coverage Δ

...mmons/statistics/inference/InferenceException.java
100.00% <ø> (ø)

...s/statistics/inference/UnconditionedExactTest.java
98.63% <98.63%> (ø)

...apache/commons/statistics/inference/Arguments.java
100.00% <100.00%> (ø)

...he/commons/statistics/inference/BracketFinder.java
100.00% <100.00%> (ø)

...e/commons/statistics/inference/BrentOptimizer.java
100.00% <100.00%> (ø)

...apache/commons/statistics/inference/Hypergeom.java
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Closed by 60b26ebca6a46f80651074daf895910051092c65


version bump to 0.13.0

Version 0.13.0 releases the following updates (details in change log):

major refactor of entire package
clean up API and namespace
new consolidate_intersections function with topological option
generalize POIs module to query with a flexible tags dict
allow folium functions to accept FeatureGroup and kwargs
all graph saving functions now take a filepath argument instead of filename/folder
save shapefiles in single folder containing both nodes and edges
optionally return distance and/or geometry in nearest edge search
expose timeout and memory parameters in pois and footprints modules
define default crs via epsg code instead of proj4 string
update and simplify logging with timestamps
graph metadata: add creation date and version, remove name
replace inconsistent distance parameters with consistent dist parameters
deprecate old clean_intersections function in favor of new consolidate_intersections
deprecate old gdfs_to_graph function in favor of graph_from_gdfs
deprecate old graph_from_file function in favor of graph_from_xml
rename save_as_osm function -> save_graph_xml for consistency
rename save_load module -> io
remove old save_gdf_shapefile function
drop support for python 3.5 and lower

Coverage decreased (-0.2%) to 92.557% when pulling 731b51aca8f1044602676fa380e7a98f97e45eab on release into cfb7de4a9bc01998b23963484520ff396bc8f6b3 on master.


[ligue-1] Does not work anymore "Something went wrong"

Extension
https://www.raycast.com/anhthang/ligue-1
Raycast Version
1.79.1
macOS Version
14.5
Description
Does not display anything for any date and any command, exept for the error "Something went wrong"

Steps To Reproduce
Launch any command
Current Behaviour
"Something went wrong"
Expected Behaviour
Show data

It looks like Ligue1 website got a full redesign (https://ligue1.com/), thus the scraping code @anhthang implemented back then does not work anymore

Thanks for your investigation. I will look into it and update later.


[ISSUE #2344]use encapsulated method

fix #2344

please fix the ci checkStyle error. @keranbingaa


[Bug]: jest transform ignore patterns not working for msal react library

Version
29.7.0
Steps to reproduce
https://github.com/AzureAD/microsoft-authentication-library-for-js
Expected behavior
I am trying to write test cases for my application, it has msal library authentication because of this i am not able to run test cases.
Actual behavior

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
aipl6759lt14310:typescript-sample sgorle$ yarn test
yarn run v1.22.18
$ jest
 FAIL   TypeScript  test/App.test.tsx
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/sgorle/Desktop/typescript-sample/node_modules/@azure/msal-react/dist/index.js:4
    export { MsalConsumer, MsalContext } from './MsalContext.js';
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      1 | import { render, screen } from '@testing-library/react';
      2 | import React from 'react';
    > 3 | import { MsalProvider } from "@azure/msal-react";
        | ^
      4 | import { msalInstance } from '../src/index'
      5 | import App from '../src/App'
      6 |

      at Runtime.createScriptFromCode (node_modules/jest-config/node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (test/App.test.tsx:3:1)

jest.config.js
module.exports = {
    displayName: "TypeScript",
    collectCoverage: true,
    collectCoverageFrom: [ 'src/**/*.{ts,tsx}' ],
    coverageDirectory: 'coverage',
    setupFilesAfterEnv: [ '<rootDir>/jest.setup.js' ],
    transformIgnorePatterns: [
        "<rootDir>/node_modules/(?!(@azure/msal-react))",
    ],
    testEnvironment: 'jsdom',

};

App.test.tsx
import { render, screen } from '@testing-library/react';
import React from 'react';
import { MsalProvider } from "@azure/msal-react";
import { msalInstance } from '../src/index'
import App from '../src/App'

describe('App tests', () => {
	it('should contains the heading 1', () => {
		render(
			<MsalProvider instance={msalInstance}>
				<App />
			</MsalProvider>
		);
		const heading = screen.getByText(/Hello world! I am using React/i);
		expect(heading).toBeInTheDocument()
	});
});

jest.setup.ts
import '@testing-library/jest-dom'
Additional context
No response
Environment
Mac Os ventura 13.4.1

I have had some what same issue .Try to change   transformIgnorePatterns: [
"/node_modules/(?!(@azure/msal-react))",
],   to     transformIgnorePatterns: [
node_modules/(?!@azure)",
]

Try to change your  transformIgnorePatterns in jest.config.js to:    transformIgnorePatterns: [         "node_modules/(?!@azure)"     ] . Hope this helps..

issue in msal https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/6487

Any updates here? This issue should not be stale...


Create page for increasing inbound capacity

We have a general flow to open a channel (Figma). But it does not yet differentiate for the user between increasing inbound and increasing outbound.
We also want to integrate different LSPs to buy inbound liquidity according to the LSPS1 spec: https://github.com/BitcoinAndLightningLayerSpecs/lsp/tree/main/LSPS1
A very first step could be to add a "Increase Receiving Capacity" button to the wallet view of the Hub and link to this page
A second step could be a page in the Hub that lets the user set:

Funding Method (bitcoin/lightning)
Receiving Capacity in sats
Spending Balance in sats
Funding Method (bitcoin/lightning)
time in weeks the channel remains open
set private/public
channel peer
show invoice/ deposit address

Blocktank's widget is a great inspiration. Feel free to refine.

I think this can be closed with the new design and a version with those two inputs seperated @MoritzKa


correct max-pods for t3/t2.small instances

With the latest CNI version (1.3.0) a maximum of 11 pods should be schedulable for the above mentioned instance types.

Fixed in #231


fix warnings from wdk

windows driver kit claims on several implicit typecasts. simple patch to fix it:
diff -up D:\work\src\crypto\mbedtls-2.3.0\library/asn1write.c D:\work\src\mbedtls-2.3.0\library/asn1write.c
*** D:\work\src\crypto\mbedtls-2.3.0\library/asn1write.c	Mon Jun 27 21:50:36 2016
--- D:\work\src\mbedtls-2.3.0\library/asn1write.c	Tue Aug 30 19:30:17 2016
*************** int mbedtls_asn1_write_int( unsigned cha
*** 213,219 ****
          return( MBEDTLS_ERR_ASN1_BUF_TOO_SMALL );

      len += 1;
!     *--(*p) = val;

      if( val > 0 && **p & 0x80 )
      {
--- 213,219 ----
          return( MBEDTLS_ERR_ASN1_BUF_TOO_SMALL );

      len += 1;
!     *--(*p) = (unsigned char)val;

      if( val > 0 && **p & 0x80 )
      {
diff -up D:\work\src\crypto\mbedtls-2.3.0\library/ctr_drbg.c D:\work\src\mbedtls-2.3.0\library/ctr_drbg.c
*** D:\work\src\crypto\mbedtls-2.3.0\library/ctr_drbg.c	Mon Jun 27 21:50:36 2016
--- D:\work\src\mbedtls-2.3.0\library/ctr_drbg.c	Tue Aug 30 18:04:09 2016
*************** static int block_cipher_df( unsigned cha
*** 178,184 ****
      buf_len = MBEDTLS_CTR_DRBG_BLOCKSIZE + 8 + data_len + 1;

      for( i = 0; i < MBEDTLS_CTR_DRBG_KEYSIZE; i++ )
!         key[i] = i;

      mbedtls_aes_setkey_enc( &aes_ctx, key, MBEDTLS_CTR_DRBG_KEYBITS );

--- 178,184 ----
      buf_len = MBEDTLS_CTR_DRBG_BLOCKSIZE + 8 + data_len + 1;

      for( i = 0; i < MBEDTLS_CTR_DRBG_KEYSIZE; i++ )
!         key[i] = (unsigned char)i;

      mbedtls_aes_setkey_enc( &aes_ctx, key, MBEDTLS_CTR_DRBG_KEYBITS );

diff -up D:\work\src\crypto\mbedtls-2.3.0\library/ecp.c D:\work\src\mbedtls-2.3.0\library/ecp.c
*** D:\work\src\crypto\mbedtls-2.3.0\library/ecp.c	Mon Jun 27 21:50:36 2016
--- D:\work\src\mbedtls-2.3.0\library/ecp.c	Tue Aug 30 18:04:35 2016
*************** static int ecp_mul_mxz( mbedtls_ecp_grou
*** 1580,1586 ****
      i = mbedtls_mpi_bitlen( m ); /* one past the (zero-based) most significant bit */
      while( i-- > 0 )
      {
!         b = mbedtls_mpi_get_bit( m, i );
          /*
           *  if (b) R = 2R + P else R = 2R,
           * which is:
--- 1580,1586 ----
      i = mbedtls_mpi_bitlen( m ); /* one past the (zero-based) most significant bit */
      while( i-- > 0 )
      {
!         b = (unsigned char)mbedtls_mpi_get_bit( m, i );
          /*
           *  if (b) R = 2R + P else R = 2R,
           * which is:
diff -up D:\work\src\crypto\mbedtls-2.3.0\library/md.c D:\work\src\mbedtls-2.3.0\library/md.c
*** D:\work\src\crypto\mbedtls-2.3.0\library/md.c	Mon Jun 27 21:50:36 2016
--- D:\work\src\mbedtls-2.3.0\library/md.c	Tue Aug 30 18:05:03 2016
*************** unsigned char mbedtls_md_get_size( const
*** 449,455 ****
      if( md_info == NULL )
          return( 0 );

!     return md_info->size;
  }

  mbedtls_md_type_t mbedtls_md_get_type( const mbedtls_md_info_t *md_info )
--- 449,455 ----
      if( md_info == NULL )
          return( 0 );

!     return (unsigned char)md_info->size;
  }

  mbedtls_md_type_t mbedtls_md_get_type( const mbedtls_md_info_t *md_info )
diff -up D:\work\src\crypto\mbedtls-2.3.0\library/rsa.c D:\work\src\mbedtls-2.3.0\library/rsa.c
*** D:\work\src\crypto\mbedtls-2.3.0\library/rsa.c	Mon Jun 27 21:50:36 2016
--- D:\work\src\mbedtls-2.3.0\library/rsa.c	Tue Aug 30 18:06:17 2016
*************** int mbedtls_rsa_rsassa_pkcs1_v15_sign( m
*** 1096,1102 ****
          *p++ = MBEDTLS_ASN1_NULL;
          *p++ = 0x00;
          *p++ = MBEDTLS_ASN1_OCTET_STRING;
!         *p++ = hashlen;
          memcpy( p, hash, hashlen );
      }

--- 1096,1102 ----
          *p++ = MBEDTLS_ASN1_NULL;
          *p++ = 0x00;
          *p++ = MBEDTLS_ASN1_OCTET_STRING;
!         *p++ = (unsigned char)hashlen;
          memcpy( p, hash, hashlen );
      }

ARM Internal Ref: IOTSSL-947


Download files from Coursera Jupyter notebook

Hi Bro,
How do you download all files via the Coursera Jupyter? Click each file and then download them one by one? Any more efficient method? ☹

Oh.. I saw

Saw issue#6..


Some problem in APIHander

Even though I change the status to bad_request, the return json is still as followed:
{   "status": "success",   "data": {     "message": "bad request!"   } }
and ajax dosen't response for status code 400
function return like this
          self.set_status(httplib.BAD_REQUEST)             return {                 "message": "bad request!"             }
And I can't use self.fail() since the server will throw exception like this:
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/tornado_json/jsend.py", line 20, in success
    self.write({'status': 'success', 'data': data})
  File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/tornado/web.py", line 690, in write
    raise RuntimeError("Cannot write() after finish()")
RuntimeError: Cannot write() after finish()

So what can I do?

You need to use api_assert or raise APIError if you want to throw HTTP errors. This is discussed in the documentation here, and if you want to see some examples, look here for an api_assert example, and here for an APIError example.

You'll also notice that the documentation says not to use self.fail directly. ;)

So sooooory I am not careful enough. Thanks for your response!


[RFE] Having a level of privacy on a per rule basis

Today we can disable code snippets in the reports. That's very useful for privacy reason. But this is done on a per-assessment basis: either you show the code snippets in the report or not. But sometimes you want to show the code snippets in the report, except for specific rules (e.g. a rule that looks for hard-coded passwords and displays the password in the code snippet).
It would be good if there was a privacy level on a per-rule basis. We could have several levels, going from public to private, something like:

Public: By default the code snippet of this rule is displayed
Confidential: Code snipped could be restricted to a select group of individuals who have a need to know
Private: The highest level of privacy, the code snipped is not to be shown
....

And when you run an analysis, you could specify the minimum level of privacy.
This mechanism is inspired from the Logging level of logging frameworks

Hello!
Thanks for the request, I can see how this could be useful for rule authors, I do have a question if you can help me think of other use cases along with the hard coded password type of rule?

@shawn-hurley I can imagine organizations wanting to build custom rules to update their custom security libraries/frameworks, and not wanting snippets of that code living outside of their secured repositories. @agoncal any other use cases?


Empty result issue

Hey, thanks for the great work!
When the search function returns empty list, this line returns True, and the searchbox returns the last result which is not empty.
Behavior:

Expected:

Solution:
https://github.com/m-wrzr/streamlit-searchbox/pull/14

Hey, thanks a lot for your PR & Bugfix!
Merged in it and released a new version with your change. 👍


Feature request: Add option to show the result of the 3 way diff, i.e. the real patch that will be applied

It would be really great if Helm could print the generated patch from the 3 way diff.
This would allow us to see exactly what will be applied to the cluster. I know there's the --dry-run option for helm upgrade but this is just prints the whole rendered chart and it's very difficult to tell what has changed in complex charts.
Maybe something like this?
$ helm upgrade my-chart deliveryhero/hoppscotch --values=path/to/my/values.yaml --dry-run --diff

Comparing release=my-chart, chart=deliveryhero/hoppscotch
default, hoppscotch, Deployment (apps/v1) has changed:

  # Source: hoppscotch/templates/deployment.yaml
  apiVersion: apps/v1
  kind: Deployment
  metadata:
    name: hoppscotch
    labels:
      app.kubernetes.io/name: hoppscotch
      helm.sh/chart: hoppscotch-0.2.7
      app.kubernetes.io/instance: hoppscotch
  spec:
-   replicas: 2
+   replicas: 6
    selector:
      matchLabels:
        app.kubernetes.io/name: hoppscotch
        app.kubernetes.io/instance: hoppscotch
    template:
      metadata:
        labels:
          app.kubernetes.io/name: hoppscotch
          app.kubernetes.io/instance: hoppscotch
      spec:
-       serviceAccountName: hoppscotch-default
+       serviceAccountName: my-custom-serviceaccount
        securityContext:
          {}
        containers:
          - name: hoppscotch

Or simply just print the patch as is like this:
  # Source: hoppscotch/templates/deployment.yaml
  spec:
    replicas: 6
    template:
      spec:
        serviceAccountName: my-custom-serviceaccount

I know helm-diff plugin exists this is broken in Helm 3, background is in https://github.com/databus23/helm-diff/issues/176

This seems like a useful idea for a plugin. The patch can be generated without helm’s assistance by using the same logic available in pkg/kube/client.go.

@bacongobbler

This seems like a useful idea for a plugin.

We already have the plugin and it doesn't work with Helm 3. That's what https://github.com/databus23/helm-diff/issues/176 is about.
I think getting Helm to simply show what it's sending to the API sounds more like a debug option for Helm itself as opposed to a plugin? Something like --show-patch?

Okay. I wrote something up in a few spare hours this morning. It's much more complex than a feature flag addition to Helm, which is why I suggested it should be a standalone plugin similar to helm-diff. This is just a proof of concept, but it generates the JSON diff that Helm generates internally before sending it to Kubernetes. Feel free to take a look.
https://github.com/bacongobbler/helm-patchdiff

OK thanks very much @bacongobbler, let's see if we can move the helm-diff issue forwards with this code.

closing this; looks like there's enough information to move forward on either helmfile's end or to write another plugin to handle this use case.


Support running FRR

I'd like to help adding support for FRR in bgperf. Since @benerudolph seems busy with other things, I'd like to address @ishidawataru 's issues in this Pull Request. (Here is the old PR: https://github.com/osrg/bgperf/pull/22 ).
Notes:

I squashed some of @benerudolph commits to make the history clearer, but I kept the credits
the frr.py file was licensed with NetDEF as author, because I and others at NetDEF would like to see this feature in bgperf. Feel free to change the license if it is in someway bad for your project
regarding disabling frr features: I think it would be fair to keep using the default/recommended settings from upstream projects as that is how most users use the software (or how it is packaged)
I'm not sure what @benerudolph found with the changes in pip-requirements, but since it was pointed out I removed those changes

@rzalamena Thanks!


vuestic-select enhancements

Some enhancements that I could think for the vuestic-select component:

Display of vertical scrollbars to denote that there are more items on the list.
Possibility of providing an option to specify number of items to be displayed.
Auto-scroll when typing the first letter in the select list.
Allow keyboard navigation to go up and down the select list.

@AngeloAnolin thanks, will include in one of the milestones

Done
2)You can change ites per page yourself in styles

3)Done

4)Added next miliestone


Fix JSON-LD bugs

@peacekeeper Thanks for this fix. It exposes a doubt that has nagged at me for the past 18 months, and I'm not surprised that you submitted a fix, since I knew when I wrote this that I wasn't following the pattern in the DID spec--but I've never understood those patterns. Can you please teach me more about them? I told @msporny long ago that I felt like DID Docs were confusing the distinct concepts of "ID" and "ID ref" from XML and even SGML days. Is this a JSON-LD-ism that I don't understand? How can you distinguish between an ID and a reference to an ID, when both appearances of it have the same form? Is it because only one of the appearances of the value is associated with a JSON key named "id"? To me, it makes sense that # would be used to navigate to a fragment from either within or outside a document, but it seems very weird that the "fragment navigation" token would be part of the ID value itself. Given the notation you are suggesting, if I wanted to refer to "key-1" inside the doc, I would expect to have to do "did:xyz##key-1", not "did:xyz#key-1".

Is it because only one of the appearances of the value is associated with a JSON key named "id"?

Yes that's basically it. Or do be more precise, id is defined as a term in the JSON-LD context to be equal to @id. If you open the DID JSON-LD context, you will see that it says in the beginning:
"id": "@id",
@id is a core, built-in keyword in JSON-LD which means that the value #key-1 in your DID Document is the identifier (relative to the base IRI) of the node (an RDF resource) described by the current JSON-LD object.  If the same value #key-1 appears as the value of a different term (e.g. publicKey), then it's a reference (an RDF property) pointing to the node. This assumes that the property publicKey is also defined in the JSON-LD context with "@type": "@id", again you can also see that in the DID JSON-LD context.

Thank you. That helped me understand how JSON-LD overloads the meaning of "id" (although not why this was thought to be a good idea).
But half of my puzzlement remains.
Section 3.5 of RFC 3986 (https://tools.ietf.org/html/rfc3986#section-3.5):
   The semantics of a fragment identifier are defined by the set of
   representations that might result from a retrieval action on the
   primary resource.  The fragment's format and resolution is therefore
   dependent on the media type [RFC2046] of a potentially retrieved
   representation, even though such a retrieval is only performed if the
   URI is dereferenced.

So, a fragment identifier is what is passed to the handler of the media type (the JSON-LD library, I suppose). This identifier cannot include the # character, since the ABNF of fragment is:
fragment    = *( pchar / "/" / "?" )
pchar         = unreserved / pct-encoded / sub-delims / ":" / "@"

...where # is in the general reserved chars and not in pchar. The absence of # from the fragment is also made clear early in section 3:
URI         = scheme ":" hier-part [ "?" query ] [ "#" fragment ]

         foo://example.com:8042/over/there?name=ferret#nose
         \_/   \______________/\_________/ \_________/ \__/
          |           |            |            |        |
       scheme     authority       path        query   fragment

So, if "#" is not a legal character in a fragment, and that's what the JSON-LD library can count on receiving from an external piece of software, does the JSON-LD library prepend the "#" to the value of the fragment before it goes looking for it? If so, why?

That helped me understand how JSON-LD overloads the meaning of "id" (although not why this was thought to be a good idea).

JSON-LD was a mechanism that was designed to be "additive" to existing JSON documents. We had considered saying "The way you specify the identifier for something in the graph is by using the id keyword", but then, LOTS of developers complained that there are tons of JSON documents out there that use id to specify identifiers that are not URLs... and that's where that funky @ syntax came from for all JSON-LD keywords. We also had a LOT of developers complaining simultaneously that if we kept the @ syntax, that pure JSON developers would find that weird because no self respecting JSON developer uses microsyntaxes in their markup. :)
... and that's what typically happens in standards, you have half of the developer community wanting one thing and the other half wanting something diametrically opposed to the initial set. In order to cast as wide of a net as possible, without creating so much cognitive dissonance that neither side would pick up the technology, we said - "Ok, so we'll use the @ character for JSON-LD keywords to ensure we don't conflict with existing JSON developers that might want to use JSON-LD, and then provide an aliasing mechanism that lets developers avoid the microsyntax stuff so that the JSON-LD looks and feels like standard JSON in the vast majority of the use cases".
There are a plethora of trade-offs that the decision above kicked off that would take much longer to explain than I have time right now, but hopefully the above answers the question you asked above, @dhh1128.

URI RFC says that the fragment should be identified inside the doc by "nose", not "#nose"

Unfortunately, I'm rushing to try and get the VC spec wrapped up, so I can't dive into the specific language you're referring to. My expectation is that you're mis-interpreting the specification (based on how I have experienced these things as implemented by various libraries).
Let me try to explain from a different direction:
Let's say you have a document at this URL: https://example.com/foo
... and let's say that the MIME Type for that document allows you to use fragment identifiers to identify "things". Typically, there will be two ways to "reference those things" ... implicitly, and explicitly. I will assert that there are good reasons for doing both (based on whether or not your document always stays at https://example.com/foo or if it might be moved to https://example.com/fnurt).
If I wanted to talk about https://example.com/foo#bar, within the document identified by https://example.com/foo then I could reference it implicitly by using:
#bar

or explicitly, by using:
https://example.com/foo#bar

If I did the following in https://example.com/foo:
bar

Then, and here's where it gets really confusing, depending on the rules for that MIME Type on URI construction, and we haven't clarified this for DID Documents, and the use of BASE and the alignment of the moons, I may end up with https://example.com/foobar OR https://example.com/bar (the MIME Type is supposed to specify how fragments in documents are handled, IIRC... and HTML did something weird with <a id="frag"> and confused everyone).
I think we should be explicit in DID Documents (did:example:123456789#foo), as that leaves no room for confusion, which is a good thing at the expense of the extra characters. We SHOULD support relative #foo, but tell people to please not do that. We will also need to define what using foo alone means... does it mean (did:example:123456789#foo, did:example:123456789foo, did:example:123456789/foo, or something else)?
... and remember, if you have a strong opinion on the above, you are just one developers and there is a high likelihood that some other developer feels just as strongly about the opposite opinion... and that's what the standards process is about (when at its best), picking one way and then creating a logical argument why that's the best way while also ensuring that many other developers will naturally come to that conclusion as well even without knowing the actual reason for why that makes sense.
Hope that helps.

For reference, links to related issues in the DID specs:

https://github.com/w3c-ccg/did-spec/issues/97
https://github.com/w3c-ccg/did-resolution/issues/9

I am going to go ahead and merge this. Thank you, @peacekeeper, for raising the PR, and thank you, @peacekeeper and @msporny for patiently explaining. I am not feeling aligned with all of the thinking here, but I think I should work that out in DID spec tickets, not here. In the meantime, we should be aligned with the spec.


Fix error message for undefined values

The error message should contain the path to the element, not the whole
subtree.

@gombasg can you add some output with before/after this fix?

Ooh I think this would help with some of the horrible "profile-dumping" errors we've come across!
Which should make @apdibbo happier.

That would make me much happier


Internationalization

I was wondering if you might consider making the warning and error messages translatable to other languages than English.

I'm open to discuss the idea - but lack experience in how to effectively deploy and scale translations in a open source library.
What is your use case?

We've been doing a drive to standardize the error messages. So if your use case is to relay the error to the end user, I think you should catch it and translate/customize it in your app.


Add headers and footers as includes

This will allow better customization

Sorry about this one, was trying to open a PR on my fork of this. (Love the theme by the way!)


[BUG] "Ended because API returned an empty page" "Deleted 0 messagess, 0 failed" even though there are 144k more messages to delete

Describe the bug
title, this happens on both my desktop computer and laptop.
edit: i suspect this might be because the first search page only yields "started a call" messages, but what do i know.
EDIT: workaround by setting the "before" date range to not include the "started a call" messages.
To Reproduce
start from default settings, click the 3 get buttons, check include pinned, click start.
Screenshots / Logs

Affects (Add an X to items that apply)

[X] DMs
[ ] DM Groups
[ ] Channel
[ ] Channel (NSFW)
[ ] Server (All Channels)
[ ] Other (explain)

System:

OS: Windows 10
Chrome 86.0.4240.111

At first glance it seems plausible that an entire page of system messages would make the algorithm think it reached the end. I'll have to take a look at the code tho I can't quite remember of the top of my head

Duplicate of #122


Continuous integration

I think it would be nice to have some automatic checks on PRs, such as

Does build.sh still work?
Does test.sh still execute successfully?

CI should also increase the incentives to write automatic tests.
A full install takes a lot of time though, so we'd need a setup that offers sufficient CPU time. (Travis, which I'm most familiar with, has a timeout of 50 minutes).

#1023 is a case in point I guess.
I've started working on this on my travis branch.

My builds at https://travis-ci.org/sjakobi/codeworld all timed out when building aeson as a dependency for CW produced no output for >= 10 minutes.
At that point the build had already taken more than 80 minutes, which is longer than I expected Travis to allow.
Wrapping install.sh in travis_wait 120 causes it to simply time out after after two hours.
I suspect that building aeson is so slow because Travis offers only 7.5 GB of RAM. So we'd probably need more RAM than that.
Reinstalling GHCJS for a good hour on each build also seems like a waste, so we'd want some kind of caching. Maybe we can even copy some Nix bits from reflex?!

I've had people make attempts to speed up CodeWorld setup before. @Gabriel439 made an attempt at Nix migration, and @bbarker has a work-in-progress pull request to cache with Docker.  Generally speaking, I am happy to fix these, but I don't want to divert time away from development of CodeWorld itself to solve these problems.  It's not an hour per build for developes; just an hour per initial install (or major tool change).  Running ./build.sh in the CodeWorld directory works fine after the first build.  I feel like that isn't the biggest factor affecting development speed.
(But I agree that continuous build won't be so useful if it takes an hour.  On the other hand, discussions with @mightybyte suggest that Nix doesn't play so well with Travis CI either.)


Bug located in SYZ frequency sweep setup

Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug
When adding SYZ frequency sweep, there is a default frequency range that I did not define from 0-20GHz.
Additionally:

the log sweep creates multiple 2-point sweeps
the single DC point is not accurately depicted
The linear step sweep is converted to a linear count sweep

Steps To Reproduce
from pyaedt import Edb
import os.path
working = $user_file_path$ #user path omitted
temp_dir = os.path.join(working, r'Galileo.aedb')
edb = Edb(edbpath=temp_dir, edbversion="2022.2")
new_path = os.path.join(working, 'test' )
edb.save_edb_as(os.path.join(new_path, r'syz.aedb'))

#add port
edb.core_siwave.create_circuit_port_on_net("U1B5","V1P5_S3", port_name = "syzport")

# setup frequency sweep
setup1 = edb.create_siwave_syz_setup("syz_setup")

setup1.add_frequency_sweep(name = "mysweep",frequency_sweep=[
                          ["linear count", "0", "0", 1],
                          ["log scale", "100Hz", "20MHz", 30],
                          ["linear scale", "20MHz", "2GHz", "10MHz"],
                          ])

setup1.use_si_settings = False #use PI radiobutton. Produces warning during solve but desired setting is used
edb.core_siwave.create_exec_file(add_syz = True)
edb.save_edb()
edb.solve_siwave()
edb.close_edb()

expect:
linear count 0 Hz, 1 point
log 100Hz - 20MHz, 30 points per decade
linear step 20MHz - 2 GHz, 10MHz steps

Actual:

Which Operating System are you using?
Windows
Which Python version are you using?
3.7
Installed packages
certifi==2022.12.7
cffi==1.15.1
charset-normalizer==3.1.0
clr-loader==0.2.5
cycler==0.11.0
fonttools==4.38.0
idna==3.4
imageio==2.27.0
kiwisolver==1.4.4
matplotlib==3.5.3
numpy==1.21.6
packaging==23.1
Pillow==9.5.0
platformdirs==3.2.0
plumbum==1.8.1
pooch==1.7.0
psutil==5.9.4
pyaedt==0.6.70
pycparser==2.21
pyparsing==3.0.9
python-dateutil==2.8.2
pythonnet==3.0.1
pyvista==0.38.5
pywin32==306
requests==2.28.2
rpyc==5.3.0
scooby==0.7.1
six==1.16.0
typing-extensions==4.5.0
urllib3==1.26.15
vtk==9.2.6

Hi @pyAnsysUser I've fixed a bug on Freq Sweep yesterday in #2817. We were not clearing the sweep data before adding more points. Give it a try in v0.6.71 which I will create today and reopen the issue

Yes, this merge has removed the 0-20GHz sweep that was observed previously


Dart Analyzer Error 。Encountered a Dart Analysis Server error.

Analyzer Feedback from IntelliJ
Version information

IDEA AI-191.8<IP_ADDRESS>10548
2.8.4
AI-191.8<IP_ADDRESS>10548, JRE 1.8.0_202-release-1483-b49-5587405x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.15.6, screens 1440x900  Retina

Exception
Dart analysis server, SDK version 2.8.4, server version 1.27.4, FATAL error: NoSuchMethodError: The getter 'isEof' was called on null.
Receiver: null
Tried calling: isEof
#0      Driver._captureExceptions.errorFunction (package:analysis_server/src/server/driver.dart:720:7)
#1      _CustomZone.handleUncaughtError (dart:async/zone.dart:1059:19)
#2      _CustomZone.runGuarded (dart:async/zone.dart:981:7)
#3      _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1019:23)
#4      _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#5      _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#6      _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#7      _Timer._runTimers (dart:isolate-patch/timer_impl.dart:405:11)
#8      _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:429:5)
#9      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168:12)

For additional log information, please append the contents of
file:///private/var/folders/9f/9bnj44dx22d5z95j591x7z2r0000gn/T/report.txt.

This has not been reported again since Dart 2.8.4; please re-open if you see this in a recent version of Dart/Flutter.

This has not been reported again since Dart 2.8.4; please re-open if you see this in a recent version of Dart/Flutter.


Fix typo in zsh-vi-mode.zsh

Fix a typo in zsh-vi-mode.zsh

could you check again the line 631, it should be a special blank character.

Hey @jeffreytse , I've removed that change.
Sorry 😥


A 6 x 6 linprog testcase: 3 methods x sparse / dense give different results

A 6 x 6 linprog testcase from glpk: 3 methods x sparse / dense give different results
transp-linprog.py below is a 6 x 6 testcase of scipy.optimize.linprog
from a GLPK example, transp. In outline:
for method in ["interior-point", "revised simplex", "simplex"]:
    for sparse in [True, False]
        try:
            linprog( ... )

The 6 combinations give rather different results. grep transp-linprog.log:
linprog  method: interior-point  sparse: True
The algorithm terminated successfully and determined that the problem is infeasible.
final f: 0.649008  x: [0.711 0.57 0.515 0.707 0.557 0.549]

linprog  method: interior-point  sparse: False
The algorithm terminated successfully and determined that the problem is unbounded.
final f: 0.649472  x: [0.712 0.57 0.515 0.708 0.557 0.55]

linprog  method: revised simplex  sparse: True
ValueError: shapes (1,12) and (1,12) not aligned: 12 (dim 1) != 1 (dim 0)

linprog  method: revised simplex  sparse: False
final f: 153.675  x: [50 300 0 275 0 275]

linprog  method: simplex  sparse: True
ValueError: all the input arrays must have same number of dimensions

linprog  method: simplex  sparse: False
final f: 153.675  x: [0 300 0 325 0 275]

The full logfile and transp.* glpk files are under https://gist.github.com/denis-bz transp-linprog .
Transp is the smallest of the GLPK examples/, here made into a standalone testcase.
Reproducing code example:

    #!/usr/bin/env python
    """ linprog testcase from transp.glp: all 3 methods, sparse / dense """

    from __future__ import division, print_function
    import sys
    import time
    import traceback  # cf. better-exceptions
    import numpy as np
    import scipy
    from scipy import sparse
    from scipy.optimize import linprog  # $scopt13/_linprog.py
        # https://docs.scipy.org/doc/scipy/reference/optimize.linprog-interior-point.html

    __version__ = "2019-06-10 june"
    __author_email__ = "denis-bz-py t-online.de"

    np.set_printoptions( threshold=10, edgeitems=5, linewidth=140,
            formatter = dict( float = lambda x: "%.3g" % x ))  # float arrays %.3g
    print( "\n" + 80 * "=" )
    print( "from", " ".join( sys.argv ), time.strftime( "%c" ))
    print( "versions: numpy %s  scipy %s   python %s " % (
            np.__version__, scipy.__version__ , sys.version.split()[0] ))

    #...............................................................................
    disp = True
    maxiter = 50
    tol = 1e-4  # default 1e-8

        # from glpk /examples/transp.glp glp_linprog --
    c = np.r_[ 0.225, 0.153, 0.162, 0.225, 0.162, 0.126 ]
    lb = np.r_[ 0, 0, 0, 0, 0, 0 ]
    ub = np.r_[ 1e10, 1e10, 1e10, 1e10, 1e10, 1e10 ]  # grr inf
    b = np.r_[ 1e10, 350, 600, -325, -300, -275 ]

    Adense = np.array(
        [[0.225, 0.153, 0.162, 0.225, 0.162, 0.126],
        [1, 1, 1, 0, 0, 0],
        [0, 0, 0, 1, 1, 1],
        [-1, 0, 0, -1, 0, 0],
        [0, -1, 0, 0, -1, 0],
        [0, 0, -1, 0, 0, -1]]
        )

        # to change these params, run this.py  a=1  b=None  'c = expr' ...
        # in sh or ipython --
    for arg in sys.argv[1:]:
        exec( arg )

    A = [Adense, sparse.csr_matrix( Adense )]
    bounds = np.c_[ lb, ub ]
    print( "c A: \n%s \n%s \nb: %s " % (c, Adense, b) )
    print( "params: disp %s  tol %g " % (disp, tol) )

    #...............................................................................
    for method in ["interior-point", "revised simplex", "simplex"]:
      for sparse in [True, False]:
        print( "\n" +  80 * "-" )
        print( "linprog  method: %s  sparse: %s " % (method, sparse) )
        options = dict( disp=disp, maxiter=maxiter, tol=tol,
                    sparse = sparse )  # rs, simplex OptimizeWarning
        try:
            res = linprog( A_ub=A[sparse], b_ub=b, c=c, bounds=bounds,
                    method=method, options=options )
            if not disp:
                print( "linprog:", res.message )
            print( "final f: %g  x: %s " % (res.fun, res.x) )
                # glpk: 50 300 0 275 0 275
        except (IndexError, ValueError):
            traceback.print_exc()

Error messages:

above
Scipy/Numpy/Python version information:

versions: numpy 1.16.4  scipy 1.3.0   python 3.7.3

Only interior point supports the sparse option, so that disposes of two cases.
Apparently there are multiple optimal vertices with the same value of the objective function, and both simplex methods find them, so there is no problem with those here.
You've set the tolerance to be very coarse. Does running the interior point methods with the default tolerance give the same result?

I didn't notice that the interior point methods returned a non-success status. The high upper bounds (1e10) might be causing scaling issues. Try replacing them with np.inf.

Only interior point supports the sparse option

ok, but ValueError  ?

does running the interior point methods with the default tolerance give the same result?

py transp-linprog.py tol=1e-8:
linprog  method: interior-point  sparse: True
The algorithm terminated successfully and determined that the problem is infeasible.
final f: 7.59467  x: [5.96 5.52 4.84 9.64 8.71 8.29]
linprog  method: interior-point  sparse: False
The algorithm terminated successfully and determined that the problem is infeasible.
final f: 7.611  x: [5.98 5.53 4.85 9.66 8.73 8.31]
linprog  method: simplex  sparse: False
ValueError: Phase 1 of the simplex method failed to find a feasible solution. The pseudo-objective    function evaluates to 7.6e-06 which exceeds the required tolerance of 1e-08 for a solution to be considered 'close enough' to zero to be a basic solution. Consider increasing the tolerance to be greater than 7.6e-06. If this tolerance is unacceptably  large the problem may be infeasible.

Try replacing them with np.inf

that would make sense, but
_linprog_util.py _clean_inputs line 242
   if not(np.isfinite(b_ub).all()):
        raise ValueError(
            "Invalid input for linprog: b_ub must not contain values "
            "inf, nan, or None")

I'd suggest first getting the doc aka spec right:  bounds arrays or array-like only, no tuples, no None s
=> simpler code,  bounds_nx2
=> compatible with some other scipy.optimizers
(except least_squares: 2-tuple of array_like)
For the doc on bounds, how about

bounds: an n x 2 array of lower bounds and upper bounds
To constrain variables x[i] between lower bounds and upper bound, lb[i] <= x[i] <= ub[i],
make a bounds array with two columns lb and ub. For example,
lb = np.zeros(n)            # n = number of variables, len(c)
ub = np.inf * np.ones(n)    # inf: no upper bound
lb[:10] = - np.inf
ub[:10] = 1                 # constrain x[:10] <= 1, no lower bound
bounds = np.c_[ lb, ub ]    # 2 columns, lb and ub
lpres = linprog( ... bounds=bounds … )
Other forms of bounds:
bounds=None constrains all x[i] to be >= 0. This is the default.
bounds can be array-like, which means "can be converted to a numpy ndarray by np.asarray"

Scratch the above on bounds, silly: use the well-documented class Bounds in _constraints.py
like most other optimizers ?
Bounds in _linprog_util.py oughta be unified, not
def _clean_inputs
	... grungy bounds code

def _presolve
	...
	# Standard form for bounds (from _clean_inputs) is list of tuples
	# but numpy array is more convenient here
	# In retrospect, numpy array should have been the standard

Re: replacing 1e10 with np.inf, please replace the bounds with np.inf and eliminate that first constraint entirely. I would agree that we should do this automatically (although it has never come up before). I just added automatic removal of constraints with infinite upper bound to #9671.

ok, but ValueError ?
"Raised when an operation or function receives an argument that has the right type but an inappropriate value"
A suggestion for what it should be would be helpful.

Re: tolerance not fixing IP, I'm not surprised. I think it's the big numbers. Hopefully eliminating those big numbers will help.
Re: tolerance breaking simplex, this is not terribly surprising. After inclusion of revised simplex, simplex is only retained for backwards compatibility. @Kai-Striega might be interested to know about this, but there's probably nothing to be done about it as it's a tolerance issue.
Re: bounds specification, that is in #9671. I just added the possibility of specifying them as Bounds objects. When these were added to minimize, they weren't added to linprog.

Bounds in _linprog_util.py oughta be unified
Yes, that's what the comment "In retrospect, numpy array should have been the standard" meant, that they should be converted to numpy arrays at the outset (in _clean_inputs) and linprog should have been structured to accept them like that. Unfortunately, that isn't the case - the rest of linprog does not take them as arrays - so at the end of _presolve they are converted back to a list of tuples.

# *sigh* - convert bounds back to their standard form (list of tuples)
# again, in retrospect, numpy array would be standard form

It's not pretty, but it is what it is, and changing it has been on the to do list for a long time.
PR welcome unless @Kai-Striega has already started?

Matt, folks.
with inf bounds (checks in _linprog_util commented out) and tol=1e-8,
3 of the 5 smallest GLPK examples give
/opt/local/mac/big/py3/lib/python3.7/site-packages/scipy/optimize/_linprog_ip.py:514: RuntimeWarning: invalid value encountered in double_scalars
  rho_p = norm(r_p(x, tau)) / max(1, norm(r_p0))
OptimizeWarning: Solving system with option 'cholesky':True failed. It is normal for this to happen occasionally, especially as the solution is approached. However, if you see this frequently, consider setting option 'cholesky' to False.
OptimizeWarning: Solving system with option 'sym_pos':True failed. It is normal for this to happen occasionally, especially as the solution is approached. However, if you see this frequently, consider setting option 'sym_pos' to False.
OptimizeWarning: Solving system with option 'sym_pos':False failed. This may happen occasionally, especially as the solution is approached. However, if you see this frequently, your problem may be numerically challenging. If you cannot improve the formulation, consider setting 'lstsq' to True. Consider also setting `presolve` to True, if it is not already.
Numerical difficulties were encountered before the problem converged. Please check your problem formulation for errors, independence of linear equality constraints, and reasonable scaling and matrix condition numbers. If you continue to encounter this error, please submit a bug report.

GLPK solves them in ~ 0 seconds.
To run these I use a glp_sparse.py, test*py, shell scripts ...
which would certainly need some time with 1-1 contact to make pushbutton.
How could we proceed ?
Anyway in Germany it's time for a 🍺

I need to see the matrices to comment.
See #9636 for careful benchmarking against GLPK.

@denis-br can you post those matrices?

@denis-bz I refactored much of the simplex/interior-point code last year and while (to me) it's much better than it was, I'll be the first to admit that it's far from perfect. The linear programming module was written before _constraints were added and have never been updated since then. It is on the todo list (#9671) PRs or additional clean ups from there are welcome =).
@mdhaber I have started but don't think I'll finish anytime soon. I've had a friend show interest in it - but if someone else wants to start first they are free to go ahead with it.

Hi @Kai-Striega
should I use your newest _linprog*.py -- where can I find them ? (I'm not up to building all of scipy.)
Are we agreed that inf in bounds is ok ? I had to patch
b[ ~ np.isfinite(b) ] = 1e20  #bz else NaNs in _indicators rho_A
...
rho_A = norm(c.T.dot(x) - b.T.dot(y)) / (tau + norm(b.T.dot(y)))  #bz inf in b -> NaN

Do umfpack / sksparse make a difference ? I have neither.
(Testing even 4 combinations looks like no fun, let alone versionitis.)
On more tests, I have a glp_sparse.py: .glp file -> scipy sparse
to provide a path from any GMPL (gnu Mathprog, a subset of AMPL) -> .glp -> scipy.
Running *.glp is easy in shell, less so in pure python.
cheers eh
-- denis

should I use your newest _linprog*.py -- where can I find them ? (I'm not up to building all of scipy.)

His changes have already been merged with the master branch. The version you find on the GitHub repository includes his changes.
I suggest that you look into getting your development environment set up if you intend to contribute code. There are ways around it, but it's not recommended.

Are we agreed that inf in bounds is ok ?

bounds in its current state already supports np.inf.
If you mean b_ub, the right hand side of the upper bound constraints, np.inf is not ok. An upper bound on b_ub means there is no constraint, so the constraint should be removed entirely. The interior point algorithm will breaks down if you do not remove these trivial upper bound constraints.

Do umfpack / sksparse make a difference ? I have neither.

They do (see here for performance comparison) but you don't necessarily have to test with all combinations locally. You would write unit tests and test them locally without SuiteSparse, and when you submit a PR the tests would be run with SuiteSparse.

On more tests, I have a glp_sparse.py: .glp file -> scipy sparse
to provide a path from any GMPL (gnu Mathprog, a subset of AMPL) -> .glp -> scipy.
Running *.glp is easy in shell, less so in pure python.

I don't understand. Do you mean you have a system for converting GMPL to SciPy code? If so, please convert your tests to SciPy code and I can try to interpret them. It sounds like you are still including np.inf in the right hand side of upper bound constraints. Failure in that case is not a bug in the implementation; it is an inherent limitation of the algorithm combined with a lack of preprocessing to remove trivially-satisfied upper bound constraints. The solution is to add preprocessing to remove these unnecessary upper bound constraints.

RS works fine with Inf in b_ub, and I expected same input => same output from IP too --
principle of least astonishment.
Also +- Inf is standard in textbooks and in most? scipy optimizers to mean "no bound".
(To remove such rows, just
jfinite = np.isfinite( b_ub )
ninf = len(b_ub) - jfinite.sum()
if ninf > 0:
    print( "linprog ip: removing %d rows of A_ub and b_ub where b_ub == inf" % ninf )
    A_ub = A_ub[jfinite]
    b_ub = b_ub[jfinite]

I agree that we should automatically remove the infinite right hand sides, so we need to leave this issue open until that's done. As you say, the fix is easy, so that would be a great first PR if you want to give it a shot.
Note that math textbooks also write A^-1 b, which in numerical computing should be interpretted as solve Ax = b (as opposed to calculate the inverse of A and multiply). I agree that we should make it easier for the user when we can, though.

@fletcheaston This would be another good issue to tackle because it would give an excuse to make a doc change and test building the docs locally.
The change to code should probably go in scipy/optimize/_linprog_util.py, specifically in the _clean_inputs function around Line 242: before the check for all finite values, check for positive np.inf in b_ub. Remove all those entries and the corresponding rows in A_ub.
(A_ub @ x <= b_ub are the inequality constraints of a linear programming problem. An entry of b_ub that is positive infinity corresponds with a constraint of the form a_1 x_1  + ... + a_n x_n <= inf, which is trivially satisfied. These constraints can and should be removed from the problem formulation as they do not change the solution of the problem, but they do make the problem larger and can cause numerical difficulties.)
In addition, let's modify the docstring in scipy/optimize/_linprog.py, linprog function, around line 208. Something like:
The inequality constraint vector. Each element represents an upper bound on the corresponding value of `A_ub @ x`. Elements `np.inf` and corresponding rows in `A_ub` will be automatically removed, as these constraints are trivially satisfied. For a faster, more reliable solution, manually remove constraints with exceptionally large upper bounds if they are known not to affect the solution.

Please test building the docs locally, then submit a PR and check the documentation built on the cloud. I left a mistake in the text above that won't render properly : )

I agree with Matt; we should keep the issue open for now, and that this
will be a good first issue for anyone that's interested in helping.
Should we still add this to the list of existing clean-ups?
On Fri., 21 Jun. 2019, 09:26 Matt Haberland<EMAIL_ADDRESS>wrote:

@fletcheaston https://github.com/fletcheaston This would be another
good issue to tackle because it would give an excuse to make a doc change
and test building the docs locally.
The change to code should probably go in scipy/optimize/_linprog_util.py
https://github.com/scipy/scipy/blob/master/scipy/optimize/_linprog_util.py,
specifically in the _clean_inputs function around Line 242: before the
check for all finite values, check for positive np.inf in b_ub. Remove
all those entries and the corresponding rows in A_ub.
(A_ub @ x <= b_ub are the inequality constraints of a linear programming
problem. An entry of b_ub that is positive infinity corresponds with a
constraint of the form a_1 x_1 + ... + a_n x_n <= inf, which is trivially
satisfied. These constraints can and should be removed from the problem
formulation as they do not change the solution of the problem, but they do
make the problem larger and can cause numerical difficulties.)
In addition, let's modify the docstring in scipy/optimize/_linprog.py,
linprog function, around line 208. Something like:
The inequality constraint vector. Each element represents an upper bound on the corresponding value of A_ub @ x. Elements np.inf and corresponding rows in A_ub will be automatically removed, as these constraints are trivially satisfied. For a faster, more reliable solution, manually remove constraints with exceptionally large upper bounds if they are known not to affect the solution.
Please test building the docs locally, then submit a PR and check the
documentation built on the cloud. I left a mistake in the text above that
won't render properly : )
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scipy/scipy/issues/10288?email_source=notifications&email_token=AHFOJNLPSZ2EO7MKG2TZCL3P3QU6BA5CNFSM4HWTILZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYHFCVQ#issuecomment-504254806,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHFOJNNP4OVX2OBPH7DZPFDP3QU6BANCNFSM4HWTILZQ
.

@Kai-Striega it is already in the list of existing clean-ups.
@fletcheaston is working on testing the revised contributor documentation (#10286) and I think he can use this as an issue.
@Kai-Striega Do you agree with the location of the code fix I suggested above? The doc change?

@mdhaber
The code change: Positive infinity should be a valid upper bound, and so it should not raise an error. Saying that I think it would be much neater to keep cleaning/presolving as separate concerns in their respective functions. So eliminating constraints should be done in _presolve not _clean_inputs.
The docs: lgtm :+1:

OK @fletcheaston implement proposed code change around line 534, in _presolve instead of _clean_inputs.
That means that in _clean_inputs, you'll have to allow +/- inf to pass through without raising a ValueError. (I'm not sure, but np.inf and float(inf)/math.inf might be different, so be careful).
I'm guessing that _presolve doesn't have anything that will recognize that -inf as an upper bound makes the problem infeasible. If not, after dealing with +inf you'll have to check for -inf and if found return:
            status = 2
            message = ("The problem is (trivially) infeasible due to a"
                                "upper bound on a constraint being negative"
                                "infinity ")
            complete = True
            return (c, c0, A_ub, b_ub, A_eq, b_eq, bounds,
                    x, x0, undo, complete, status, message)

Other non-finite-number values should continue to raise the ValueError.
Sound good @Kai-Striega ?

@mdhaber must we let -inf pass? To me, an upper bound of negative infinity doesn't really make sense.  Also, at that point, we can expect b to be a numpy array of floats, so we won't need to worry about having math.inf.

@Kai-Striega We might as well let -inf pass. It's just as valid as +inf. It just makes the problem trivially infeasible.

@mdhaber and @fletcheaston I think there should be two changes.

[ ] line 252 should allow -/+ inf pass, so only nans trigger an error. The error message should also be updated to reflect this.
[ ] line 534 (approx)  should now remove the trivially infeasible constraints.

Further, I think it would be best to make the equality constraints match the upper bound constraints. That way the new behaviour stays consistent.

@Kai-Striega Such a problem could be either infeasible or unbounded, but I doubt the existing code will handle it properly. Do you really think it's worth the time to add the logic for determining which it is?
This brings to mind that I was wrong before - negative infinity in the right hand side of the inequality constraint could be feasible (just unbounded). It's the same as negative infinity in the right hand side of an equality constraint.
I think we're going down a rabbit hole here. So I'm going to reverse my opinion and go with what you suggested originally - let +inf pass for RHS of inequality constraint, and raise ValueError for all other infinities/NaNs.

Do you really think it's worth the time to add the logic for determining which it is?

TBH I'm not really sure. My intuition is that, we should either accept -/+ infinities as bounds - and treat them appropriately for all cases or exclude them entirely. OTOH:

I think we're going down a rabbit hole here.

Agreed. In practice, I expect infinite bounds occur rarely - if at all.

let +inf pass if it's in the RHS of an inequality constraint, but raise ValueError for all other infinities/NaNs.

This is probably the best compromise, the fix is straightforward, isn't very computationally expensive and covers the (I suspect) most common edge case.

This LP solver does not solve that type of problem.

:+1: This could always be added in a later version, but for now, there are bigger priorities.


doc: usage of connector

Description

Motivation and Context

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Enhancement (changes that improvement of current feature or performance)
[ ] Refactoring (changes that neither fixes a bug nor adds a feature)
[ ] Test Case (changes that add missing tests or correct existing tests)
[ ] Code style optimization (changes that do not affect the meaning of the code)
[x] Docs (changes that only update documentation)
[ ] Chore (changes that don't modify src or test files)

Self Check before Merge

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

怎么又改回来了

怎么又改回来了

用ES6的展开操作符 ... 被编译后实际上是使用的 apply，而这里需要根据参数个数使用 call


Is a 3d (voxel) version of this tool planned?

Hi,
I watched the talk linked in the Readme. At the end Anastasia mentions that you are currently working on bringing the 2d concept to 3d.
I am currently working on a (hobby) Voxel enigne in rust+vulkan and thought it might be easy to transfer the algorithm to 3d given a good Voxel loading/editing crate similar to the image crate.
Are there already working prototypes internally which take some 3d information and apply the algorithm to generate a new 3d model? Do you have some more crates in this direction planed or would it make sense for me to either extent this project to also worke in 3d or create a new one from scratch?
Greetings
Tendsin Mende

No current plans to extend this crate to 3D, it would likely have to work quite differently and with very different types of source material. So think if one would explore more 3d volume synthesis it would be easiest to do that as separate crate(s).


Property types for optimization

PR Type

[ ] Breaking change
[x] Feature
[ ] Patch

Brief Description

This PR introduces new property types:

MoleculeFromMolecule: As the name suggests, takes a molecule, returns a molecule. This could be used for different purposes. Here, I was mainly thinking of using it together with AOEnergy property type for a module to return optimized coordinates and energy.
Optimize<PT2Optimize, WithRespectTo>: Templated property type that mimics [Derivative property type](https://github.com/NWChemEx/SimDE/blob/d3c6743cb145370d8ff3174bc3b1a66b33124b01/include/simde/derivative/derivative_pt.hpp#L50). I am not quite happy with the type def I chose (OptimizeCoordinates), so please let me know if you have a suggestion.

Not In Scope

PR Checklist

[x] Is documented
[x] Is tested
[x] Adheres to applicable organization standards

Closing. This PR is superseded by #150.


Add request origination self identifier for Node.js API metrics

Using Telemetry, we can track feature usage at a granular level. For example, the Optic API will be tracking # of joins. We need a way to track where a request originated when coming from the Client APIs. Each client API must include some sort of identifier that the server can use to increment the correct metric (e.g. optic-joins-javascript vs optic-joins-nodejs).
This task is not for a specific metric - just adding the Node.js identifier that can be used by feature tracking mechanism.

Follow-up from #258

See here:
https://github.com/marklogic/node-client-api/issues/322


Update single fetch logic when clientLoaders are present

Change the logic for serverLoader calls from clientLoader's in single fetch mode so we're not over-fetching on the server if a clientLoader never calls serverLoader.
Todo:

[x] Update prefetching logic to align

Yeah only for that route branch.  Otherwise we nullify the main benefit of clientLoader which is to avoid hitting the server loader since the single fetch call would hit it anyway even if you pulled data from the client side cache.  serverLoader is essentially the same as the old ?_data fetch via the single fetch call/encoding.
You still get a multi-route single fetch call for any routes that do not have a client loader, so if you have a/b/c/d and only d has a clientLoader`, you'd get:
GET /a/b/c/d.data?_routes=a,b,c (always)

GET /a/b/c/d.data?_routes=d     (only if d called serverLoader())


Outlook webclient adds min-width to styles

Outlook webclient adds min-width. It is necessary to write in style and style-inline for columns in addition min-width with the same parameters as width

We can't really do that because min-width might break the mobile version for a lot of clients with horizontal scrolling.
Can you share the whole MJML ? Never saw that behavior here

@iRyusa
Yes, I also did not come across this. can I for comparison provide links to repositories for comparison in a letter where this behavior is absent. Or is it necessary to drop the code here?

<mj-column mj-class="advantages__column"
           css-class="advantages__column">

  <mj-image  mj-class="advantages__img"
             css-class="advantages__img"

             src="{{{advantages__img.src}}}"
             title="{{{advantages__img.title}}}"
             alt="{{{advantages__img.alt}}}"
             width="40px" />

  <mj-text mj-class="advantages__text"
           css-class="advantages__text">

Получите Яндекс.Станцию — умную колонку с мощным звуком и голосовым помощником Алисой внутри

  </mj-text>

</mj-column>

<mj-column mj-class="advantages__column"
           css-class="advantages__column">

  <mj-image  mj-class="advantages__img"
             css-class="advantages__img"

             src="{{{advantages__img.src}}}"
             title="{{{advantages__img.title}}}"
             alt="{{{advantages__img.alt}}}"
             width="40px" />

  <mj-text mj-class="advantages__text"
           css-class="advantages__text">

Поделитесь доступом с тремя близкими. Доплачивать не нужно, просто добавьте их в вашу семейную группу

  </mj-text>

</mj-column>

attributes
  <mj-class name="advantages"             padding-top="32px"
                                          padding-bottom="27px"
                                          padding-left="20px"
                                          padding-right="20px" />

  <mj-class name="advantages__column"     width="280px"
                                          padding-left="20px"
                                          padding-right="20px" />

  <mj-class name="advantages__img"        padding-top="10px"
                                          padding-bottom="13px"
                                          padding-left="0px"
                                          padding-right="0px" />

  <mj-class name="advantages__text"       align="center"
                                          padding-top="0px"
                                          padding-bottom="20px"
                                          padding-left="0px"
                                          padding-right="0px" />

style-inline
  .advantages__column {
    width: 280px !important;
  }

style head
@media screen and (max-width: 479px) {
  .advantages__column {
    width: 280px !important;
    max-width: 280px !important;
  }
}

@media screen and (min-width: 480px) {
  .advantages__column {
    width: 280px !important;
    max-width: 280px !important;
  }

  .gallery__column {
    min-width: 290px !important;
    width: 290px !important;
    max-width: 290px !important;
  }
}

Any template in https://mjml.io/templates works fine that's why it's a bit weird that you have this behavior here.
Can you provide the full template on https://mjml.io/try-it-live please ?

test.zip
npm i
gulp build

there is an already assembled version in the archive

You have this in your style :
body {
  min-width: 320px !important;
}

.body {
  min-width: 308px !important;
}

I think it might come from here

Corrected. Working. Thanks!


[MRESOLVER-494] The LOCAL_PATH system property is client app property

This ArtifactProperty is specific to "system" scope, tied to it. Introduce a "system scope handler" that does all, and let client app control all. Also, this component belongs to session, so expose it via session.

https://issues.apache.org/jira/browse/MRESOLVER-494

Here's what I have in mind: https://github.com/gnodet/maven-resolver/commit/791c07e3fc05a86fa383607d28db0dcdf7fcc995

@cstamas Here's what I have in mind: gnodet@791c07e The local path is only managed by the scope handler. The assumption is that for a given artifact, if it has a system scope, it also has a local path. Maybe I'm missing something though ...

You do: i.e. you have a dep w/o scope, but you define a depMgr w/ system scope (and system path), who will apply then that mgmt onto dependency? Also, this may come from n-th level now, as we introduced "transitive depmgr" etc.


Count-Search-Aggregation: refactoring

In gitlab by @sylvaingaudan on Apr 28, 2017, 13:35
factorize the code

In gitlab by @sylvaingaudan on Apr 28, 2017, 13:35
added ~1918909 label

In gitlab by @sfalquier on May 3, 2017, 11:07
added ~1918368 and removed ~1918367 labels

In gitlab by @sfalquier on May 3, 2017, 11:05
added ~1918367 and removed ~1918909 labels

In gitlab by @sfalquier on May 3, 2017, 11:07
assigned to @MohamedHamouGisaia

In gitlab by @sylvaingaudan on May 3, 2017, 15:54
created branch 35-count-search-aggregation-refactoring

In gitlab by @sfalquier on May 3, 2017, 11:11
assigned to @sylvaingaudan

In gitlab by @sylvaingaudan on May 3, 2017, 17:34
mentioned in merge request !36

In gitlab by @sylvaingaudan on May 3, 2017, 17:35
removed ~1918368 label

In gitlab by @sylvaingaudan on May 3, 2017, 17:35
closed

In gitlab by @sfalquier on May 4, 2017, 10:39
mentioned in commit edd59f01d6e62f2e75bcb87e83e31fd49323c147


Explore adding a generic wrapper creator

The middleware pattern for wrappers seems to be one that is occurring a lot in several contexts. So far, we have seen this in the OG Express application, Next.js API routes, the new Route Handlers and then now also with Server Actions.
This pattern is akin to the decorator pattern in Python as well. It might be worth exploring a generic way in which we can repeat this pattern across a different domains/types of functions and in a type-safe way.
Given a generic function such as the following, we want to create a wrapper that lets us:

perform some operations before and after executing the function
execute the wrapped function and return its value
receive the same/unbounded number of arguments as the wrapped function might receive without knowing a-priori what arguments those might be. Previous patterns restrict this by having parameters of (req, res, next) for example, assuming there are only ever two arguments, which is true in some cases. An alternate ordering I have explored is (next, req, res) allowing the list of args to be arbitrary.

function myFunc(a:int, b:int) {
   return a + b
}

const myFuncB = wrapper(myFunc)

myFuncB(1, 2) // => 3
myFunc(1, 2) // => 3

Motivation
The motivation for exploring this pattern is to avoid some of the repetition that seems to be coming with defining wrappers for the App Router, and then the Pages Router and then soon for Server Actions.

See: https://github.com/rexfordessilfie/nextwrappers/pull/20#issuecomment-1614071125


updated podspec to supporty tvOS and watchOS

Hey @bsdspas, it doesn't look like XMLParsing as currently accepting any PRs. I have a fork of it called XMLCoder that updates the podspec for tvOS and watchOS, adds support for Swift 5.1 and a few other useful features. Hope you find it useful and I'd be very happy to accept any possible contributions!


TC-TIMESYNC-2.3: yaml

@cecille FYI, needs conflict resolution.

Looks like someone else automated this. Closing for now.


Trying two ZKs using S3, they restart cycle forever

I'm using the current docker image to try out Exhibitor, so I don't know if that is part of my problem.
But I am running two aws servers, and have the S3 shared file setup (it's created as expected).
I will start exhibitor on both servers. The ZK instances start off green.  Then as the auto config churns, the Servers config value is updated (I am using local aws IPs).  Then the servers just cycle between shut down and not server forever.
Here is how I'm launching it (this is happening insider the docker container)

H=$(curl http://<IP_ADDRESS>/latest/meta-data/local-ipv4)
docker run -p 8080:8080 -p 2181:2181 -p 2888:2888 -p 3888:3888 \
calix-netflix-s3 --configtype s3 --s3config calix-zookeeper-exhibitor:exhibit.cfg \
--hostname ${H} --defaultconfig /exhibitor/defaults.conf \
--s3credentials /exhibitor/credentials.properties

Here is my defaults file

servers-spec=
zookeeper-data-directory=/zookeeper/data
zookeeper-install-directory=/zookeeper
#zookeeper-log-directory=/zookeeper/transactions
log-index-directory=
cleanup-period-ms=200000
check-ms=2000
backup-period-ms=600000
client-port=2181
cleanup-max-files=20
backup-max-store-ms=21600000
connect-port=2888
backup-extra=throttle\=&bucket-name\=calix-zookeeper-exhibitor&key-prefix\=exhibitor-&max-retries\=4&retry-sleep-ms\=30000
observer-threshold=3
election-port=3888
zoo-cfg-extra=tickTime\=2000&initLimit\=10&syncLimit\=5
auto-manage-instances-settling-period-ms=10000
auto-manage-instances=1
auto-manage-instances-fixed-ensemble-size=0
java-environment=export JAVA_OPTS\="-Xms1000m -Xmx1000m"

Well, I found a post from 2013 that said to try the tickTime=500, and that seemed to fix things. Anyone know why? Kind of freaks me out that this would shut down all my zookeepers. How can I ensure this is stable? :-/

Exhibitor seems like a good tool, but is anyone using it? Is there a reason there isn't much activity lately? Is it because it's stable? :)


[Feature] collapsible components for sections, tables and code snippets

Problem description
at times the number of pages tied to a section, or the number of rows in our tables, or the length of a code snippet can  take up a sizable amount of real-estate either on the side-nav or body of the page.
Why would it be useful?
collapsible components enable users to shrink the copy in a given page or section, allowing them to view other copy within a page with more ease.
Why would this feature be useful for Fern users?
other doc users might have similar verbose content in their pages and side-panels
Describe the solution (optional)
collapsible components for sections in the side-nav, tables and code snippets
Additional context
Add any other context or screenshots.

This is now available! https://docs.buildwithfern.com/generate-docs/overview/writing-content#nested-sections


I complete two katas but they don't mark as completed

+1

This should be fixed. I'm assuming this was about kata not marked as completed on search result page. Please let me know if I'm mistaking or if this is still happening.