hardsource fails with out of memory error on windows 10

I am running node v4.4.3 (npm 2.15.8) with
node --max_old_space_size=4096 node_modules/webpack-dev-server/bin/webpack-dev-server.js
(my app has around 5000 modules)
Here's what I get:
HardSourceWebpackPlugin is writing to a new confighash path for the first time: C:\code\hana_epm_fpa\webpack\build-cache\hardsource\start
  build [==============      ] 69%
<--- Last few GCs --->

  247449 ms: Mark-sweep 3965.0 (4197.1) -> 3965.0 (4197.1) MB, 298.2 / 0 ms [allocation failure] [scavenge might not succeed].
  247730 ms: Mark-sweep 3965.0 (4197.1) -> 3965.0 (4197.1) MB, 281.3 / 0 ms [allocation failure] [scavenge might not succeed].
  248013 ms: Mark-sweep 3965.0 (4197.1) -> 3964.3 (4197.1) MB, 282.9 / 0 ms [last resort gc].
  248296 ms: Mark-sweep 3964.3 (4197.1) -> 3965.0 (4197.1) MB, 282.2 / 0 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 00000082FE6B4639 <JS Object>
    1: stringify [native json.js:157] [pc=0000000EED9385E4] (this=00000082FE6AD511 <a JSON with map 00000322AE3614E1>,u=000003FB5633AB51 <an Object with map 00000322AE3C1D59>,v=00000082FE6041B9 <undefined>,I=00000082FE6041B9 <undefined>)
    2: arguments adaptor frame: 1->3
    3: /* anonymous */ [C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:796] [pc=0000000EF...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

Thank you for opening this issue @MagicDuck.
I tried to give some thought to what could be going on here and I'm really not sure. The line in the stack trace is stringifying the resolve cache. Which for a 5000 module project would still be pretty small. Couldn't be more then a meg. But really it'd probably be the stringifying of the modules before that and the resolve cache is just knocking over into this error. I'm not sure how I'll be able to track down a memory leak that might cause this without a representative project that breaks on a machine I have access to.
Can you do a run without HardSource with a plugin like:
{
  apply: function(compiler) {
    compiler.plugin('done', function() {
      console.log(require('util').inspect(process.memoryUsage()));
    });
  }
}

Knowing the comparative memory without HardSource would be really useful. If HardSource is just adding a 100 megs or something to knock your project into this territory or if its adding 3 gigs, that'd be really useful info.
What plugins are you running? I wonder if there may be something HardSource is interacting with to create a really large stringified modules when caching to disk.
And just to cover a basic base: What version of webpack are you using?

I got another stack trace for you. NodeJS v7.1.0 under Mac OS Sierra:

<--- Last few GCs --->

[80586:0x103000000]     4764 ms: Mark-sweep 814.3 (844.9) -> 634.6 (700.6) MB, 61.6 / 0.0 ms  (+ 88.1 ms in 3 steps since start of marking, biggest step 62.0 ms) GC interrupt GC in old space requested
[80586:0x103000000]     7301 ms: Mark-sweep 989.4 (1055.5) -> 417.9 (468.9) MB, 94.7 / 0.0 ms  allocation failure GC in old space requested
[80586:0x103000000]     9744 ms: Mark-sweep 950.2 (1001.2) -> 590.1 (645.3) MB, 100.2 / 0.0 ms  allocation failure GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x323c789c0d11 <JS Object>
    2: applyChunkIds [/Users/Sebastian/Workspace/sebastian-software/advanced-boilerplate/node_modules/webpack/lib/Compilation.js:~791] [pc=0x37df997a9493](this=0x29e843baea91 <a Compilation with map 0x30382e6bb269>)
    3: /* anonymous */ [/Users/Sebastian/Workspace/sebastian-software/advanced-boilerplate/node_modules/webpack/lib/Compilation.js:580] [pc=0x37df9971da88](this=0x231235099779 <JS G...

FATAL ERROR: invalid array length Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/usr/local/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
 3: v8::Utils::ReportOOMFailure(char const*, bool) [/usr/local/bin/node]
 4: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
 5: v8::internal::Heap::AllocateRawFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
 6: v8::internal::Heap::AllocateUninitializedFixedArray(int) [/usr/local/bin/node]
 7: v8::internal::Factory::NewUninitializedFixedArray(int) [/usr/local/bin/node]
 8: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedSmiElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)0> >::ConvertElementsWithCapacity(v8::internal::Handle<v8::internal::JSObject>, v8::internal::Handle<v8::internal::FixedArrayBase>, v8::internal::ElementsKind, unsigned int, unsigned int, unsigned int, int) [/usr/local/bin/node]
 9: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedSmiElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)0> >::GrowCapacityAndConvertImpl(v8::internal::Handle<v8::internal::JSObject>, unsigned int) [/usr/local/bin/node]
10: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
11: 0x37df98e063a7
12: 0x37df9973797c

It works the first time, but using it the second time it crashes.
This is coming out of my first steps trying to integrate it with Advanced Boilerplate
Relevant commit: https://github.com/sebastian-software/advanced-boilerplate/commit/2fef83a36c6018e1feb1d0f5e3f8a8e9464ea585

Here is the plugin output you suggested to send:
Before cache:

Client: { rss: 355536896, heapTotal: 299081728, heapUsed: 229826752 }
Server: { rss: 598425600, heapTotal: 523952128, heapUsed: 375952152 }

With cache crashes before sending out this info. How helpful...
But this might help - I added some debugging to see the different steps Webpack is doing (for another thing I am working on right now):

Executing: sealing
Executing: optimizing
Executing: basic module optimization
Executing: module optimization
Executing: advanced module optimization
Executing: basic chunk optimization
Executing: basic chunk optimization
Executing: chunk optimization
Executing: advanced chunk optimization
module and chunk tree optimization
Executing: module reviving
Executing: module order optimization
Executing: module id optimization
Executing: chunk reviving
Executing: chunk order optimization

Therefor it seems to fail in the compilation phase "optimize-chunk-ids". This would also explain the stack trace at position #2: applyChunkIds

the problematic code is somewhere here in Webpack:
	if(this.usedChunkIds) {
		var usedIds = Object.keys(this.usedChunkIds).map(function(key) {
			return this.usedChunkIds[key];
		}, this).sort();
		console.log("PHASE-1-1")
		var usedNumberIds = usedIds.filter(function(id) {
			return typeof id === "number";
		});
		console.log("PHASE-1-2")
		nextFreeChunkId = usedNumberIds.reduce(function(a, b) {
			return Math.max(a, b);
		}, -1) + 1;
		console.log("PHASE-1-3", nextFreeChunkId)
		for(var i = 0; i < nextFreeChunkId; i++) {
			if(this.usedChunkIds[i] !== i)
				unusedIds.push(i);
		}
		unusedIds.reverse();
	}

It passes "PHASE-1-3" and reports that nextFreeChunkId is being computed as 820075193.
The following loop crashes afterwards.

The used IDs are a result of the RecordIdsPlugin which stores the IDs on the compilation object: compilation.usedChunkIds = records.chunks.usedIds;

I am not sure what should be inside the usedIds section inside the records.json file but it seems to contain some faulty entries for me e.g.
        "usedIds": {
          "0": 0,
          "1": 1,
          "2": 2,
          "3": 3,
          "4": 4,
          "880c63": "880c63"
        }

inside some part "extract-text-webpack-plugin".

And this is the final section of my records.json file:
"chunks": {
"byName": {
"home": 3208415,
"main": 3343801,
"about": 92611469,
"vendor": 820075192
},
"byBlocks": {
"node_modules/babel-loader/lib/index.js?{"cacheDirectory":true,"env":{"production":{"comments":false,"plugins":["react-intl","transform-react-remove-prop-types"]},"development":{"plugins":["react-hot-loader/babel"]}},"babelrc":false,"compact":true,"sourceMaps":true,"comments":false,"presets":[["babel-preset-es2015",{"modules":false}],"babel-preset-es2016","babel-preset-es2017","babel-preset-react"],"plugins":["lodash","transform-class-properties","transform-object-rest-spread",["transform-runtime",{"regenerator":false}],["code-split-component/babel",{"disabled":false,"role":"client"}]]}!src/app/App.js:0/1": 3208415,
"node_modules/babel-loader/lib/index.js?{"cacheDirectory":true,"env":{"production":{"comments":false,"plugins":["react-intl","transform-react-remove-prop-types"]},"development":{"plugins":["react-hot-loader/babel"]}},"babelrc":false,"compact":true,"sourceMaps":true,"comments":false,"presets":[["babel-preset-es2015",{"modules":false}],"babel-preset-es2016","babel-preset-es2017","babel-preset-react"],"plugins":["lodash","transform-class-properties","transform-object-rest-spread",["transform-runtime",{"regenerator":false}],["code-split-component/babel",{"disabled":false,"role":"client"}]]}!src/app/App.js:1/1": 92611469
},
"usedIds": {
"3208415": 3208415,
"3343801": 3343801,
"92611469": 92611469,
"820075192": 820075192
}
}

There you can see that it uses the number `820075192` here - which would explain why the next free ID is `820075193`

When I am commenting out this line in the RecordsPlugin it's working:
compilation.usedChunkIds = records.chunks.usedIds;

I did some more tests. The issue seems to be related to having multiple entry chunks. When I comment out my "vendor" chunk everything seems to work fine:
    entry: {
      main: [
        ifDevClient("react-hot-loader/patch"),
        ifDevClient(`webpack-hot-middleware/client?reload=true&path=http://localhost:${process.env.CLIENT_DEVSERVER_PORT}/__webpack_hmr`),
        options.entry ? options.entry : ifIsFile(`./src/${target}/index.js`),
      ],

      // vendor: `./src/${target}/vendor.js`
    },

@swernerx I checked out your repo and you were close to the cause in regards to:
compilation.usedChunkIds = records.chunks.usedIds;

The issue you are experiencing isn't directly due to HardSource. Its using CodeSplit component and its supporting plugin alongside RecordIdsPlugin, which HardSource relies on to ensure module and chunk ids are immutable once assigned. RecordIdsPlugin being a first party plugin has some direct support in webpack's Compilation. When Compilation applies ids to chunks without ids it first builds an array based on usedChunkIds passed by RecordIdsPlugin. In your case webpack is trying to build an array with 820075189 members because vendor has the larger chunk id. An array that size of 32 bit integers would need something like 3.3 gigs of memory. When you disable the vendor chunk, the next chunk hash id down needs 370megs to create the array. (I'm assuming an efficient c style array, which these probably wouldn't be.)
The issue is CodeSplit and RecordIds (and webpack's Compilation) are making different assumptions about how chunk ids should look. I don't think HardSource should offer a solution for this. I think the best option for you if you wanted to use HardSource at this point is to a small compatibility plugin. I think its fair for you to disable usedChunkIds since CodeSplit is providing them through its hash.
{
  apply: function(compiler) {
    compiler.plugin('compilation', function(compilation) {
      compilation.plugin('optimize-chunk-order', function() {
        compilation.usedChunkIds = null;
      });
    });
  },
},

Think I'm going to open an issue on CodeSplit in the meantime.

Thanks! I mentioned the issue here is well. https://github.com/ctrlplusb/code-split-component/issues/18

@swernerx Just though in case CodeSplit doesn't provide an ID for say an unnamed chunk a better compat plugin would be:
{
  apply: function(compiler) {
    compiler.plugin('compilation', function(compilation) {
      compilation.plugin('optimize-chunk-order', function() {
        if (Array.isArray(compilation.usedChunkIds)) {
          compilation.usedChunkIds = compilation.usedChunkIds.filter(function(usedId) {
            return usedId < 100000;
          });
        }
      });
    });
  },
},

Thanks @mzgoddard I'll check this out.

With the proposed additional plugin building the development version works fine. But this is not actually using the code split thing as far as I understand (it's only enabled in production).
When building production the first time it works. The second build still fails though.
Creating a production build for client...
- Sealing 8 modules...
- Optimizing modules/chunks/tree...

<--- Last few GCs --->

   10746 ms: Mark-sweep 945.3 (1001.2) -> 585.9 (646.3) MB, 95.5 / 0.0 ms [allocation failure] [GC in old space requested].
   10874 ms: Mark-sweep 585.9 (646.3) -> 584.9 (641.3) MB, 127.9 / 0.0 ms [allocation failure] [GC in old space requested].
   10991 ms: Mark-sweep 584.9 (641.3) -> 584.8 (597.3) MB, 117.5 / 0.0 ms [last resort gc].
   11088 ms: Mark-sweep 584.8 (597.3) -> 584.8 (595.3) MB, 96.6 / 0.0 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x2f205dcfb51 <JS Object>
    2: applyChunkIds [/Users/Sebastian/Workspace/sebastian-software/advanced-boilerplate/node_modules/webpack/lib/Compilation.js:~791] [pc=0x1bbb1825b296] (this=0x2be14af24b71 <a Compilation with map 0x232c315f3e99>)
    3: /* anonymous */ [/Users/Sebastian/Workspace/sebastian-software/advanced-boilerplate/node_modules/webpack/lib/Compilation.js:580] [pc=0x1bbb1837ee90] (this=0x2f205de6f21 <JS G...

FATAL ERROR: invalid array length Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/usr/local/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node]
 3: v8::Utils::ReportApiFailure(char const*, char const*) [/usr/local/bin/node]
 4: v8::Utils::ApiCheck(bool, char const*, char const*) [/usr/local/bin/node]
 5: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
 6: v8::internal::Heap::AllocateRawFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
 7: v8::internal::Heap::AllocateUninitializedFixedArray(int) [/usr/local/bin/node]
 8: v8::internal::Factory::NewUninitializedFixedArray(int) [/usr/local/bin/node]
 9: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedSmiElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)0> >::ConvertElementsWithCapacity(v8::internal::Handle<v8::internal::JSObject>, v8::internal::Handle<v8::internal::FixedArrayBase>, v8::internal::ElementsKind, unsigned int, unsigned int, unsigned int, int) [/usr/local/bin/node]
10: v8::internal::(anonymous namespace)::ElementsAccessorBase<v8::internal::(anonymous namespace)::FastPackedSmiElementsAccessor, v8::internal::(anonymous namespace)::ElementsKindTraits<(v8::internal::ElementsKind)0> >::GrowCapacityAndConvertImpl(v8::internal::Handle<v8::internal::JSObject>, unsigned int) [/usr/local/bin/node]
11: v8::internal::Runtime_GrowArrayElements(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
12: 0x1bbb175079a7
13: 0x1bbb1752e9c5
14: 0x1bbb1825b296
15: 0x1bbb1837ee90
sh: line 1: 89203 Abort trap: 6           node bin/advanced-script.js build

npm ERR! Darwin 16.1.0
npm ERR! argv "/usr/local/Cellar/node6-lts/6.9.1/bin/node" "/usr/local/bin/npm" "run" "prod"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prod: `npm run prescript && node bin/advanced-script.js build`
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prod script 'npm run prescript && node bin/advanced-script.js build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the advanced-boilerplate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run prescript && node bin/advanced-script.js build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs advanced-boilerplate
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls advanced-boilerplate
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Sebastian/Workspace/sebastian-software/advanced-boilerplate/npm-debug.log

npm ERR! Darwin 16.1.0
npm ERR! argv "/usr/local/Cellar/node6-lts/6.9.1/bin/node" "/usr/local/bin/npm" "run" "prod:start"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prod:start: `npm run prod && node build/server/main.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prod:start script 'npm run prod && node build/server/main.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the advanced-boilerplate package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run prod && node build/server/main.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs advanced-boilerplate
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls advanced-boilerplate
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/Sebastian/Workspace/sebastian-software/advanced-boilerplate/npm-debug.log

This happens for both suggestions regarding fixes. Setting to null and filter.

Heh. My second suggestion assumed usedChunkIds was an array when its an object. This worked for me (along with my first suggestion of assigning null).
Here's it where I put it. https://github.com/sebastian-software/advanced-boilerplate/compare/master...mzgoddard:code-split-records-compat
{
  apply: function(compiler) {
    compiler.plugin('compilation', function(compilation) {
      compilation.plugin('optimize-chunk-order', function() {
        console.log('optimize-chunk-order', compilation.usedChunkIds);
        if (compilation.usedChunkIds) {
          var usedChunkIds = {};
          for (var key in compilation.usedChunkIds) {
            if (compilation.usedChunkIds[key] < 100000) {
              usedChunkIds[key] = compilation.usedChunkIds[key];
            }
          }
          compilation.usedChunkIds = usedChunkIds;
        }
      });
    });
  },
},

sorry I didn't reply earlier, I was on vacation...
But am glad that there is a workaround now :)

hmm, I now get a different error:
Unhandled rejection RangeError: Maximum call stack size exceeded
    at Promise._rejectCallback (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise.js:473:10)
    at Promise._resolveFromExecutor (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise.js:490:17)
    at new Promise (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise.js:77:14)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:762:23
    at addPromise (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:697:21)
    at Array.forEach (native)
    at walkDependencyBlock (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:703:30)
    at getModuleCacheItem (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:714:9)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:984:19
    at fromCache (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:963:18)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:969:20
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:981:12
    at C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\NormalModuleFactory.js:28:4
    at C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\NormalModuleFactory.js:159:3
    at NormalModuleFactory.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\tapable\lib\Tapable.js:82:11)
    at NormalModuleFactory.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:1073:39)
    at NormalModuleFactory.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\tapable\lib\Tapable.js:84:14)
    at BIFrameworkPlugin.resolveServiceReq (C:\code\hana_epm_fpa\webpack\sap.webpack\plugins\BIFrameworkPlugin.js:262:9)
    at .<anonymous> (C:\code\hana_epm_fpa\webpack\sap.webpack\plugins\BIFrameworkPlugin.js:186:22)
    at NormalModuleFactory.applyPluginsAsyncWaterfall (C:\code\hana_epm_fpa\webpack\node_modules\tapable\lib\Tapable.js:86:13)
    at NormalModuleFactory.create (C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\NormalModuleFactory.js:144:8)
    at callFactory (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:774:29)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:777:17
    at Promise._execute (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\debuggability.js:299:9)
    at Promise._resolveFromExecutor (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise.js:481:18)
    at new Promise (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise.js:77:14)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:762:23
    at addPromise (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:697:21)
    at Array.forEach (native)
    at walkDependencyBlock (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:703:30)

Unhandled rejection RangeError: Maximum call stack size exceeded
    at PromiseArray._iterate (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise_array.js:99:30)
    at PromiseArray.init [as _init] (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise_array.js:77:10)
    at new PromiseArray (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise_array.js:23:10)
    at Function.Promise.all (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise.js:188:12)
    at getModuleCacheItem (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:804:26)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:984:19
    at fromCache (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:963:18)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:969:20
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:981:12
    at C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\NormalModuleFactory.js:28:4
    at C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\NormalModuleFactory.js:159:3
    at NormalModuleFactory.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\tapable\lib\Tapable.js:82:11)
    at NormalModuleFactory.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:1073:39)
    at NormalModuleFactory.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\tapable\lib\Tapable.js:84:14)
    at BIFrameworkPlugin.resolveServiceReq (C:\code\hana_epm_fpa\webpack\sap.webpack\plugins\BIFrameworkPlugin.js:262:9)
    at .<anonymous> (C:\code\hana_epm_fpa\webpack\sap.webpack\plugins\BIFrameworkPlugin.js:186:22)
    at NormalModuleFactory.applyPluginsAsyncWaterfall (C:\code\hana_epm_fpa\webpack\node_modules\tapable\lib\Tapable.js:86:13)
    at NormalModuleFactory.create (C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\NormalModuleFactory.js:144:8)
    at callFactory (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:774:29)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:777:17
    at Promise._execute (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\debuggability.js:299:9)
    at Promise._resolveFromExecutor (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise.js:481:18)
    at new Promise (C:\code\hana_epm_fpa\webpack\node_modules\bluebird\js\release\promise.js:77:14)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:762:23
    at addPromise (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:697:21)
    at Array.forEach (native)
    at walkDependencyBlock (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:703:30)
    at getModuleCacheItem (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:714:9)
    at C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:984:19
    at fromCache (C:\code\hana_epm_fpa\webpack\node_modules\hard-source-webpack-plugin\index.js:963:18)

I am not sure if this would affect it in any way, but I do have a custom plugin that does some fancy stuff to support legacy code:
    // handle special module resolution requests before they go through the normal (more expensive) process
    compiler.plugin("normal-module-factory", function(nmf) {
        nmf.plugin("before-resolve", function(req, callback) {
            if (req.request.startsWith("service!")) {
                this.resolveServiceReq(req, callback);
            } else if (req.request.startsWith("serviceLazy!*")) {
                this.resolveServiceLazyReq(req, callback);
            } else if (req.request.startsWith("serviceLoader!")) {
                this.resolveServiceLoaderReq(req, callback);
            } else if (req.request.startsWith("$bundle/")) {
                this.resolveBundleRelativeReq(req, callback);
            } else if (req.request.startsWith("$bundle-strings")) {
                this.resolveBundleStringsReq(req, callback);
            } else if (req.request.endsWith("-bundle.js")) {
                // Note: in this case, we don't care about the contents. The parts we care about from the content will
                // go into the services metadata part of the bootstrap anyways.
                callback(null, assign(req, {
                    request: "dependent-null!" + req.request
                }));
            } else {
                callback(null, req);
            }
        }.bind(this));
    }.bind(this));

ah, it looks like it's choking on a circular dependency. Basically, I have the situation where module A depends on module B and module B depends on module A.

hmm, using the webpack-dev-server causes it to crash with:
C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\Stats.js:263
                                                module: origin.module ? origin.module.identifier() : "",
                                                                                ^

TypeError: origin.module.identifier is not a function
    at C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\Stats.js:263:45
    at Array.map (native)
    at C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\Stats.js:260:33
    at Array.map (native)
    at Stats.toJson (C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\Stats.js:237:35)
    at Server.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\webpack-dev-server\lib\Server.js:34:39)
    at Compiler.applyPlugins (C:\code\hana_epm_fpa\webpack\node_modules\tapable\lib\Tapable.js:26:37)
    at Watching._done (C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\Compiler.js:78:17)
    at Watching.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\Compiler.js:61:18)
    at MemoryFileSystem.writeFile (C:\code\hana_epm_fpa\webpack\node_modules\memory-fs\lib\MemoryFileSystem.js:328:9)
    at Compiler.writeFile (C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\Compiler.js:295:25)
    at Compiler.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\webpack\lib\Compiler.js:291:13)
    at Immediate.<anonymous> (C:\code\hana_epm_fpa\webpack\node_modules\memory-fs\lib\MemoryFileSystem.js:288:4)
    at runCallback (timers.js:637:20)
    at tryOnImmediate (timers.js:610:5)
    at processImmediate [as _immediateCallback] (timers.js:582:5)

If I comment out the following lines from Stats.js (around line 263):
						// module: origin.module ? origin.module.identifier() : "",
						// moduleIdentifier: origin.module ? origin.module.identifier() : "",
						// moduleName: origin.module ? origin.module.readableIdentifier(requestShortener) : "",

it starts up, but now I get 404s for certain chunks...

Firstly, thanks @mzgoddard for making this brings my TS build times down to sanity.
I've also started experiencing out of memory exceptions since I started using the HardSource Plugin. I'm running MacOS Sierra.
Sometimes it can run for an hour and not crash, other times it crashes after 10 minutes.
Happy to do any analysis that might help.
webpack: Compiled successfully.
webpack: Compiling...
webpack: wait until bundle finished: /resources/a0L6F000018dFfgUAE?ufb=%7B%22disabled%22%3A%5B%22Urgency%22%5D%2C%22Resource+Type%22%3A%5B%22Person%22%5D%2C%22Region%22%3A%5B%22a0J6F00000xuvkJUAQ%22%5D%2C%22Urgency%22%3A%5B%22Normal%22%5D%7D

<--- Last few GCs --->

 6211905 ms: Mark-sweep 1365.2 (1410.2) -> 1365.2 (1410.2) MB, 279.3 / 0.0 ms [allocation failure] [GC in old space requested].
 6212171 ms: Mark-sweep 1365.2 (1410.2) -> 1365.2 (1410.2) MB, 266.4 / 0.1 ms [allocation failure] [GC in old space requested].
 6212434 ms: Mark-sweep 1365.2 (1410.2) -> 1365.2 (1403.2) MB, 262.5 / 0.0 ms [last resort gc].
 6212695 ms: Mark-sweep 1365.2 (1403.2) -> 1365.2 (1403.2) MB, 261.5 / 0.1 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x2edcf1acfb51 <JS Object>
    1: toString(aka CallSiteToString) [native messages.js:~416] [pc=0x1b47b82d471c] (this=0x3439b7356469 <a CallSite with map 0x293c64c95eb1>)
    2: FormatStackTrace [native messages.js:576] [pc=0x1b47b820d2a1] (this=0x2edcf1ae6f19 <JS Global Object>,Q=0x13aec5ce4b69 <a CapturedTrace with map 0x85fb3041819>,aT=0x2d73d2587f9 <JS Array[0]>)
    3: get stack [native messages.js:~597] [pc=0x1b47b8...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 4: v8::internal::Factory::NewRawOneByteString(int, v8::internal::PretenureFlag) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 5: v8::internal::Factory::NumberToString(v8::internal::Handle<v8::internal::Object>, bool) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 6: v8::internal::Runtime_NumberToStringSkipCache(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]

<--- Last few GCs --->

 3256274 ms: Mark-sweep 1367.4 (1434.8) -> 1367.3 (1434.8) MB, 291.2 / 0.1 ms [allocation failure] [GC in old space requested].
 3256551 ms: Mark-sweep 1367.3 (1434.8) -> 1367.3 (1434.8) MB, 277.4 / 0.1 ms [allocation failure] [GC in old space requested].
 3256851 ms: Mark-sweep 1367.3 (1434.8) -> 1367.3 (1411.8) MB, 299.6 / 0.1 ms [last resort gc].
 3257165 ms: Mark-sweep 1367.3 (1411.8) -> 1367.3 (1411.8) MB, 314.0 / 0.1 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x1e99265cfb51 <JS Object>
    1: uncycle [/Users/jake/dev/phoenix/node_modules/hard-source-webpack-plugin/node_modules/bluebird/js/release/debuggability.js:~724] [pc=0x1d3d5b5a29c9] (this=0x143c1ac25c51 <a CapturedTrace with map 0x1cd0fcd417c1>)
    2: attachExtraTrace [/Users/jake/dev/phoenix/node_modules/hard-source-webpack-plugin/node_modules/bluebird/js/release/debuggability.js:774] [pc=0x1d3d5d652fc4] (this=0x143c1...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 4: v8::internal::Factory::NewTransitionArray(int) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 5: v8::internal::TransitionArray::Insert(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::Name>, v8::internal::Handle<v8::internal::Map>, v8::internal::SimpleTransitionFlag) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 6: v8::internal::Map::CopyReplaceDescriptors(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::DescriptorArray>, v8::internal::Handle<v8::internal::LayoutDescriptor>, v8::internal::TransitionFlag, v8::internal::MaybeHandle<v8::internal::Name>, char const*, v8::internal::SimpleTransitionFlag) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 7: v8::internal::Map::CopyAddDescriptor(v8::internal::Handle<v8::internal::Map>, v8::internal::Descriptor*, v8::internal::TransitionFlag) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 8: v8::internal::Map::CopyWithField(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::Name>, v8::internal::Handle<v8::internal::FieldType>, v8::internal::PropertyAttributes, v8::internal::Representation, v8::internal::TransitionFlag) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
 9: v8::internal::Map::TransitionToDataProperty(v8::internal::Handle<v8::internal::Map>, v8::internal::Handle<v8::internal::Name>, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::Object::StoreFromKeyed) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
10: v8::internal::LookupIterator::PrepareTransitionToDataProperty(v8::internal::Handle<v8::internal::JSObject>, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::Object::StoreFromKeyed) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
11: v8::internal::Object::AddDataProperty(v8::internal::LookupIterator*, v8::internal::Handle<v8::internal::Object>, v8::internal::PropertyAttributes, v8::internal::Object::ShouldThrow, v8::internal::Object::StoreFromKeyed) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
12: v8::internal::Runtime::SetObjectProperty(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, v8::internal::LanguageMode) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]
13: v8::internal::Runtime_SetProperty(int, v8::internal::Object**, v8::internal::Isolate*) [/Users/jake/.nvm/versions/node/v6.9.4/bin/node]

I think at the time this was likely due to Node versions (like 5 and 7) that were leakier than other versions. I personally remember running into this with Node 7 and switching back to Node 6. Node 8  doesn't have 7's issues and I've added a lot of memory usage improvements itself since this was opened, especially recently. Hopefully that all has fixed this generally.


Sending asset fails in latest master and development branch

Current behavior
I just tried to send my received testnet Gas from the multisig contract to my address. It fails with "Verifying tx result ... failed". Same for sending from normal addresses.
Switching to an older branch I had (Nov 17) and sending from that version works.
UPDATED:
Seems like it is not only affecting multisig contracts, but any transaction that is using this imported NEP2 address.
Expected behavior
Sending of Gas should work with relaying the transaction
How to reproduce
Clone the latest master and send from a multi signature address to a normal address and it will fail.
Your environment
Let us know in what environment you're running into the issue:

OS: Linux
neo-python version: latest master (v0.8.3)
Python version: 3.6.7

@corck
I tested today in testnet and everyting worked fine. First, I made sure to merge https://github.com/CityOfZion/neo-python/pull/860 with my local branch. Then I imported the address, no problem. Then I rebuilt my wallet and sent the funds to default address, no problem. Then I claimed gas, no problem. I am not sure how to reproduce your issue, except that you may have imported the wrong address because of this issue solved here https://github.com/CityOfZion/neo-python/pull/860.
neo> wallet import multisig_addr 03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39 1 03c02a93134f98d9c78ec54b1b1f97fc64cd81360f53a293f41e4ad54aac3c5717
Added multi-sig contract address AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1 to wallet
neo> wallet
[I 190202 11:32:29 UserWallet:480] Script hash b'\x19\xae\x11\x8e\xf7\x95\x171\xc3B\xd2k\xba\xc9T\xc5n\x8b5\xd2' <class 'bytes'>
[I 190202 11:32:29 UserWallet:480] Script hash b'\x90{\xbf\xb7\x81LC\x8e\xc8\xc4`\xdc\x8b\xe0\xc3l\xc9\xfb\x03\xbd' <class 'bytes'>
Wallet {
    "path": "/mnt/e/NEO_wallets/testnet_wallet.wallet",
    "addresses": [
        {
            "address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "script_hash": "19ae118ef7951731c342d26bbac954c56e8b35d2",
            "tokens": null
        },
        {
            "version": 0,
            "address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "script_hash": "bd03fbc96cc3e08bdc60c4c88e434c81b7bf7b90",
            "frozen": false,
            "votes": [],
            "balances": [
                {
                    "asset": "0xc56f33fc6ecfcd0c225c4ab356fee59390af8560be0e930faebe74a6daff7c9b",
                    "value": "100.0"
                },
                {
                    "asset": "0x602c79718b16e442de58778e148d0b1084e3b2dffd5de6b7b16cee7969282de7",
                    "value": "500.0"
                }
            ],
            "is_watch_only": false
        }
    ],
    "height": 2272714,
    "percent_synced": 100,
    "synced_balances": [],
    "public_keys": [
        {
            "Address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        },
        {
            "Address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        }
    ],
    "tokens": [],
    "claims": {
        "available": "0.0",
        "unavailable": "0.0"
    }
}
neo> wallet rebuild 2272200
Restarting at block 2272200
wallet
neo> wallet
[I 190202 12:55:10 UserWallet:480] Script hash b'\x19\xae\x11\x8e\xf7\x95\x171\xc3B\xd2k\xba\xc9T\xc5n\x8b5\xd2' <class 'bytes'>
[I 190202 12:55:10 UserWallet:480] Script hash b'\x90{\xbf\xb7\x81LC\x8e\xc8\xc4`\xdc\x8b\xe0\xc3l\xc9\xfb\x03\xbd' <class 'bytes'>
Wallet {
    "path": "/mnt/e/NEO_wallets/testnet_wallet.wallet",
    "addresses": [
        {
            "address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "script_hash": "19ae118ef7951731c342d26bbac954c56e8b35d2",
            "tokens": null
        },
        {
            "version": 0,
            "address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "script_hash": "bd03fbc96cc3e08bdc60c4c88e434c81b7bf7b90",
            "frozen": false,
            "votes": [],
            "balances": [
                {
                    "asset": "0xc56f33fc6ecfcd0c225c4ab356fee59390af8560be0e930faebe74a6daff7c9b",
                    "value": "100.0"
                },
                {
                    "asset": "0x602c79718b16e442de58778e148d0b1084e3b2dffd5de6b7b16cee7969282de7",
                    "value": "500.0"
                }
            ],
            "is_watch_only": false
        }
    ],
    "height": 2272999,
    "percent_synced": 100,
    "synced_balances": [
        "[NEO]: 100.0 ",
        "[NEOGas]: 500.0 "
    ],
    "public_keys": [
        {
            "Address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        },
        {
            "Address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        }
    ],
    "tokens": [],
    "claims": {
        "available": "0.0",
        "unavailable": "0.005537"
    }
}
neo> wallet send neo AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ 100 --from-addr=AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1
Sending with fee: 0.0
Validate your transaction details
---------------------------------
Sending 100.0 NEO from AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1 to AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ

Enter your password to send to the network
[Password]> *****************
[I 190202 12:58:48 Transaction:619] Verifying transaction: b'26a11940c105503b44578457add7723d8136e98d68bb8754648f65f42df2774e'
Relayed Tx: 26a11940c105503b44578457add7723d8136e98d68bb8754648f65f42df2774e
neo> wallet
[I 190202 12:59:04 UserWallet:480] Script hash b'\x19\xae\x11\x8e\xf7\x95\x171\xc3B\xd2k\xba\xc9T\xc5n\x8b5\xd2' <class 'bytes'>
[I 190202 12:59:04 UserWallet:480] Script hash b'\x90{\xbf\xb7\x81LC\x8e\xc8\xc4`\xdc\x8b\xe0\xc3l\xc9\xfb\x03\xbd' <class 'bytes'>
Wallet {
    "path": "/mnt/e/NEO_wallets/testnet_wallet.wallet",
    "addresses": [
        {
            "version": 0,
            "address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "script_hash": "d2358b6ec554c9ba6bd242c3311795f78e11ae19",
            "frozen": false,
            "votes": [],
            "balances": [
                {
                    "asset": "0xc56f33fc6ecfcd0c225c4ab356fee59390af8560be0e930faebe74a6daff7c9b",
                    "value": "100.0"
                }
            ],
            "is_watch_only": false
        },
        {
            "version": 0,
            "address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "script_hash": "bd03fbc96cc3e08bdc60c4c88e434c81b7bf7b90",
            "frozen": false,
            "votes": [],
            "balances": [
                {
                    "asset": "0xc56f33fc6ecfcd0c225c4ab356fee59390af8560be0e930faebe74a6daff7c9b",
                    "value": "0.0"
                },
                {
                    "asset": "0x602c79718b16e442de58778e148d0b1084e3b2dffd5de6b7b16cee7969282de7",
                    "value": "500.0"
                }
            ],
            "is_watch_only": false
        }
    ],
    "height": 2273013,
    "percent_synced": 100,
    "synced_balances": [
        "[NEO]: 100.0 ",
        "[NEOGas]: 500.0 "
    ],
    "public_keys": [
        {
            "Address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        },
        {
            "Address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        }
    ],
    "tokens": [],
    "claims": {
        "available": "0.005628",
        "unavailable": "7e-06"
    }
}
neo> wallet send gas AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ 500 --from-addr=AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1
Sending with fee: 0.0
Validate your transaction details
---------------------------------
Sending 500.0 GAS from AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1 to AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ

Enter your password to send to the network
[Password]> *****************
[I 190202 12:59:47 Transaction:619] Verifying transaction: b'31430be14dd660ad097b6ada1a36019541093a846521733199702a46d115658b'
Relayed Tx: 31430be14dd660ad097b6ada1a36019541093a846521733199702a46d115658b
neo> wallet
[I 190202 13:01:14 UserWallet:480] Script hash b'\x19\xae\x11\x8e\xf7\x95\x171\xc3B\xd2k\xba\xc9T\xc5n\x8b5\xd2' <class 'bytes'>
[I 190202 13:01:14 UserWallet:480] Script hash b'\x90{\xbf\xb7\x81LC\x8e\xc8\xc4`\xdc\x8b\xe0\xc3l\xc9\xfb\x03\xbd' <class 'bytes'>
Wallet {
    "path": "/mnt/e/NEO_wallets/testnet_wallet.wallet",
    "addresses": [
        {
            "version": 0,
            "address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "script_hash": "d2358b6ec554c9ba6bd242c3311795f78e11ae19",
            "frozen": false,
            "votes": [],
            "balances": [
                {
                    "asset": "0xc56f33fc6ecfcd0c225c4ab356fee59390af8560be0e930faebe74a6daff7c9b",
                    "value": "100.0"
                },
                {
                    "asset": "0x602c79718b16e442de58778e148d0b1084e3b2dffd5de6b7b16cee7969282de7",
                    "value": "500.0"
                }
            ],
            "is_watch_only": false
        },
        {
            "address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "script_hash": "907bbfb7814c438ec8c460dc8be0c36cc9fb03bd",
            "tokens": null
        }
    ],
    "height": 2273020,
    "percent_synced": 100,
    "synced_balances": [
        "[NEO]: 100.0 ",
        "[NEOGas]: 500.0 "
    ],
    "public_keys": [
        {
            "Address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        },
        {
            "Address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        }
    ],
    "tokens": [],
    "claims": {
        "available": "0.005628",
        "unavailable": "5.6e-05"
    }
}
neo> wallet claim

---------------------------------------------------------------
Will make claim for 0.005628 GAS
------------------------------------------------------------------

Enter your password to complete this claim
[Password]> *****************
claim tx: {
    "txid": "0xe91b9cd896343a02034250a74a20e1f664a504fcfd2eb91ffd68a7fde412ba71",
    "size": 239,
    "type": "ClaimTransaction",
    "version": 0,
    "attributes": [],
    "vout": [
        {
            "n": 0,
            "asset": "0x602c79718b16e442de58778e148d0b1084e3b2dffd5de6b7b16cee7969282de7",
            "value": "0.005628",
            "address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ"
        }
    ],
    "vin": [],
    "sys_fee": "0",
    "net_fee": "0",
    "scripts": [
        {
            "invocation": "408c57a93cf46fb3b89c132c7de1ebdc6d1f82ec50d0956ee6dacf26e76eb32f844264d9c811340a2bc8d16265129257a0e096070d3f23c80aba4d66d0c451fd58",
            "verification": "512103c02a93134f98d9c78ec54b1b1f97fc64cd81360f53a293f41e4ad54aac3c57172103cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d3952ae"
        }
    ],
    "claims": [
        {
            "txid": "0x07a77ca06017b5ac805488b50263b1cdaf10940fb9f26f3841df5582a587c2bf",
            "vout": 0
        }
    ]
}
[I 190202 13:01:48 Transaction:619] Verifying transaction: b'e91b9cd896343a02034250a74a20e1f664a504fcfd2eb91ffd68a7fde412ba71'
Relayed Tx: e91b9cd896343a02034250a74a20e1f664a504fcfd2eb91ffd68a7fde412ba71
neo> wallet
[I 190202 13:02:12 UserWallet:480] Script hash b'\x19\xae\x11\x8e\xf7\x95\x171\xc3B\xd2k\xba\xc9T\xc5n\x8b5\xd2' <class 'bytes'>
[I 190202 13:02:12 UserWallet:480] Script hash b'\x90{\xbf\xb7\x81LC\x8e\xc8\xc4`\xdc\x8b\xe0\xc3l\xc9\xfb\x03\xbd' <class 'bytes'>
Wallet {
    "path": "/mnt/e/NEO_wallets/testnet_wallet.wallet",
    "addresses": [
        {
            "version": 0,
            "address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "script_hash": "d2358b6ec554c9ba6bd242c3311795f78e11ae19",
            "frozen": false,
            "votes": [],
            "balances": [
                {
                    "asset": "0xc56f33fc6ecfcd0c225c4ab356fee59390af8560be0e930faebe74a6daff7c9b",
                    "value": "100.0"
                },
                {
                    "asset": "0x602c79718b16e442de58778e148d0b1084e3b2dffd5de6b7b16cee7969282de7",
                    "value": "500.005628"
                }
            ],
            "is_watch_only": false
        },
        {
            "address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "script_hash": "907bbfb7814c438ec8c460dc8be0c36cc9fb03bd",
            "tokens": null
        }
    ],
    "height": 2273024,
    "percent_synced": 100,
    "synced_balances": [
        "[NEO]: 100.0 ",
        "[NEOGas]: 500.005628 "
    ],
    "public_keys": [
        {
            "Address": "AJ7f4nsBXxTBddgHGyKPjF9n11aK73G3oZ",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        },
        {
            "Address": "AUwqCM1UtPqxumCq3bx5PHSPyRRjTBfTK1",
            "Public Key": "03cfb3ad2685ad402dd5122ab83dc1d6a026e8363c905a2c73668825ad2f922d39"
        }
    ],
    "tokens": [],
    "claims": {
        "available": "0.0",
        "unavailable": "8.4e-05"
    }
}

I sent now all my Gas from the multi sig address to the my other imported NEP2 address using the old version.
Now I switched to 0.8.3 and am trying to send from that address but it fails, with the error above.
Just created now a new wallet (bug.json) and imported again the NEP2 address, waiting for the wallet to sync and will try again to send the 1 gas to another address.

I just applied for testnet GAS such that I can try to debug from a point of view as close as possible to yours.

ok so here what I did right now
# switched to neo-python tag v0.8.3
#created a new wallet
neo>wallet create bug.json
neo>wallet import nep2 WIF_KEY
#waited for the wallet to sync to 100%
neo> wallet send GAS NEW_ADDRESS 1 --from-addr=WIF_ADDRESS
Sending with fee: 0.0
Validate your transaction details
---------------------------------
Sending 1.0 GAS from WIF_ADDR to NEW_ADDR
Returning 1518.999 GAS as change to AafMvKajXuGp5YsqCbxziuyDhhGy7joYhT
Enter your password to send to the network
[Password]> **********
[I 190205 06:39:33 Transaction:619] Verifying transaction: b'221b3a67c27a04b0eedf36accab17256ff93e73007c6a2bef27391780719510d'
[E 190205 06:39:33 NodeLeader:615] Verifying tx result... failed
Could not relay tx 221b3a67c27a04b0eedf36accab17256ff93e73007c6a2bef27391780719510d

really odd.

here whats wallet prints out for my newly created wallet
Wallet {
    "path": "bug.json",
    "addresses": [
        {
            "address": "AXYzZNxuQ8Gb9eVGEFUQ6W1P6oaxR4q6oo",
            "script_hash": "ad125fea6e0a277e55be4397a8f194a6b5b240ee",
            "tokens": null
        },
        {
            "version": 0,
            "address": "WIF_ADDR",
            "script_hash": "WIF_SCRIPT",
            "frozen": false,
            "votes": [],
            "balances": [
                {
                    "asset": "0x602c79718b16e442de58778e148d0b1084e3b2dffd5de6b7b16cee7969282d[0/96858]
                    "value": "1519.999"
                },
                {
                    "asset": "0xc56f33fc6ecfcd0c225c4ab356fee59390af8560be0e930faebe74a6daff7c9b",
                    "value": "10.0"
                }
            ],
            "is_watch_only": false
        }
    ],
    "height": 2283206,
    "percent_synced": 100,
    "synced_balances": [
        "[NEO]: 10.0 ",
        "[NEOGas]: 1519.999 "
    ],
    "public_keys": [
        {
            "Address": "AXYzZNxuQ8Gb9eVGEFUQ6W1P6oaxR4q6oo",
            "Public Key": "029b025e736f86ca1b5689534afc23ac6b9b1602cba4de0b53fd57d9aabfc0b5c4"
        },
        {
            "Address": "WIF_ADDR",
            "Public Key": "PUBKEY"
        }
    ],
    "tokens": [],
    "claims": {
        "available": "0.0",
        "unavailable": "29600.03057183"
    }
}

@corck I see nothing immediately wrong with your wallet. Perhaps it is a neo-local issue?

@jseagrave21 not using neo-local here. Have a dedicated server running with a cloned neo-python github repo, that keeps the testnet up to date.

So switching back to an older version e3780126f9cf8175f9f3c7ad27f36f2baae20508, nov 17th, with updated seed list, sending gas works as expected.
neo> send GAS AXYzZNxuQ8Gb9eVGEFUQ6W1P6oaxR4q6oo 1 --from-addr=WIF_ADDR
[Password]> **********
[I 190205 07:11:42 Transaction:617] Verifying transaction: b'071bc9bb39a45e32d03128a8cdbf93260eb8332ab74a7071fdfb3ee8b1d712a8'
Relayed Tx: 071bc9bb39a45e32d03128a8cdbf93260eb8332ab74a7071fdfb3ee8b1d712a8

Can you please apply this patch and re-run the test that resulted in
[I 190205 06:39:33 Transaction:619] Verifying transaction: b'221b3a67c27a04b0eedf36accab17256ff93e73007c6a2bef27391780719510d' [E 190205 06:39:33 NodeLeader:615] Verifying tx result... failed Could not relay tx 221b3a67c27a04b0eedf36accab17256ff93e73007c6a2bef27391780719510d

That should give at least a bit more information where it is failing in the verification.
diff --git a/neo/Core/Helper.py b/neo/Core/Helper.py
index d17b6e9b..71ffd653 100644
--- a/neo/Core/Helper.py
+++ b/neo/Core/Helper.py
@@ -182,6 +182,7 @@ class Helper:
             return False

         if len(hashes) != len(verifiable.Scripts):
+            logger.debug(f"hash - verification script length mismatch ({len(hashes)}/{len(verifiable.Scripts)})")
             return False

         blockchain = GetBlockchain()
@@ -196,6 +197,7 @@ class Helper:
             else:
                 verification_hash = Crypto.ToScriptHash(verification, unhex=False)
                 if hashes[i] != verification_hash:
+                    logger.debug(f"hash {hashes[i]} does not match verification hash {verification_hash}")
                     return False

             state_reader = GetStateReader()
@@ -214,6 +216,10 @@ class Helper:

             if engine.ResultStack.Count != 1 or not engine.ResultStack.Pop().GetBoolean():
                 Helper.EmitServiceEvents(state_reader)
+                if engine.ResultStack.Count > 0:
+                    logger.debug(f"Result stack failure! Count: {engine.ResultStack.Count} bool value: {engine.ResultStack.Pop().GetBoolean()}")
+                else:
+                    logger.debug(f"Result stack failure! Count: {engine.ResultStack.Count}")
                 return False

             Helper.EmitServiceEvents(state_reader)

Output
[I 190205 08:53:49 Transaction:619] Verifying transaction: b'd69c8925703a7c0fc7ab489e43e49babfcbb4d40c3ffa6a3095234a4f8f56406'
[D 190205 08:53:49 Helper:222] Result stack failure! Count: 0
[E 190205 08:53:49 NodeLeader:615] Verifying tx result... failed
Could not relay tx d69c8925703a7c0fc7ab489e43e49babfcbb4d40c3ffa6a3095234a4f8f56406

vm to debug:
[I 190205 09:47:13 Transaction:619] Verifying transaction: b'd69c8925703a7c0fc7ab489e43e49babfcbb4d40c3ffa6a3095234a4f8f56406'
[D 190205 09:47:13 ExecutionEngine:1096] (9) Unknown opcode found: b'\xf8'
[D 190205 09:47:13 Helper:222] Result stack failure! Count: 0
[E 190205 09:47:13 NodeLeader:615] Verifying tx result... failed
Could not relay tx d69c8925703a7c0fc7ab489e43e49babfcbb4d40c3ffa6a3095234a4f8f56406

I understood from @hal0x2328 that this issue is resolved. Can you please confirm?

Starting up a new instance and pulling freshly the code from Github resolved my issues.
I actually haven't figured out what really caused it, I guess its unproducable. Will close.


Add  accelerate framework support for burn-ndarray

Feature description
blas-src has a support for Accelerate framework  in Mac.
Feature motivation
Instead of only relying on CPU compute in ndarray for mac, Accelerate gives additional boost in training.
(Optional) Suggest a Solution
Enable "accelerate" flag in blas-src dependency.

The PR was merged and now this ticket will be closed.


Parser returns terms incorrectly

In OrchardCore, when you search text:"some where", the FilterResult returns text:some where.  It changes from a phrase search to a OR search.
Expected: the original terms are returned.
Ref: https://github.com/OrchardCMS/OrchardCore/blob/8ff2453b72b3bcfc3e2c0181b220be5bc720fd96/src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs#L241-L246

Thanks, yes we will just need to track if the Term is quoted or not, when it is parsed


[docs][joy-ui] Change dark theme component background color without affecting other states

Related page
https://mui.com/joy-ui/customization/themed-components/
Kind of issue
Missing information
Issue description
I would assume that changing backgroundColor of a Joy UI component would not override other states such as hover and use the color from the default style for these states.
It is the case observed for the light mode. See the sandbox, hover the button and the color changes. However, when trying to do the same in dark mode, it overrides other states (see sandbox).
I couldn't find out from the documentation if this is intended behavior or not and what should be done to get a similar effect for the dark mode.
Context
I am trying to apply a custom backgroundColor to a Joy UI Button component which is in dark mode. However, it also overrides all other states which I do not wish to change and changing them all manually is tedious.
Search keywords: button, component, theme, background

Thanks for reporting the issue! Joy UI development is temporarily on hold as the maintainers focus on the next two major releases of Material UI


Heap Sort on cpp is added

Hey @basu0001,
Something went wrong with the build.
TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.
View build log
TravisBuddy Request Identifier: 1c032bb0-e4ee-11e9-950a-c74496fc22d4


BrowserSync opens a blank new tab instead of localhost:4000

The current iteration of the Gulpfile isn't working as intended. When running the default Gulp task, a new blank tab is opened instead of localhost:4000.

8cfb404f93838dc5e8277f5fdb57e3797cb63a5a fixes this issue.


WFLY-6218 upgrade to jboss-parent 20

to make build work on recent JDK9 builds

Linux with security manager Build 4200 outcome was FAILURE using a merge of dab429b8795b9f754aee937d2e2cf359e4b2cbb6
Summary: Tests passed: 47, ignored: 12; exit code 1 (new) Build time: 00:01:19

Linux Build 9391 outcome was FAILURE using a merge of dab429b8795b9f754aee937d2e2cf359e4b2cbb6
Summary: Tests passed: 47, ignored: 12; exit code 1 (new) Build time: 00:01:37

Windows Build 4414 outcome was FAILURE using a merge of dab429b8795b9f754aee937d2e2cf359e4b2cbb6
Summary: Tests passed: 47, ignored: 12; exit code 1 (new) Build time: 00:01:44

Linux with security manager Build 4202 outcome was FAILURE using a merge of f533578315a4f6be4faa8fe557c0c18e210f45a7
Summary: Tests passed: 47, ignored: 12; exit code 1 Build time: 00:01:57

Linux Build 9393 outcome was FAILURE using a merge of f533578315a4f6be4faa8fe557c0c18e210f45a7
Summary: Tests passed: 47, ignored: 12; exit code 1 Build time: 00:02:11

Windows Build 4416 outcome was FAILURE using a merge of f533578315a4f6be4faa8fe557c0c18e210f45a7
Summary: Tests passed: 47, ignored: 12; exit code 1 Build time: 00:02:31

Linux Build 9394 outcome was FAILURE using a merge of 72035f9efb46cd82cdc3e305f28d610dbaf825ce
Summary: Tests failed: 16 (16 new), passed: 3108, ignored: 193 Build time: 00:53:12
Failed tests
org.jboss.as.test.integration.domain.suites.CLITestSuite: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.suites.CLITestSuite.start(CLITestSuite.java:89)
	at org.jboss.as.test.integration.domain.suites.CLITestSuite.initSuite(CLITestSuite.java:103)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.suites.CLITestSuite.start(CLITestSuite.java:87)
	at org.jboss.as.test.integration.domain.suites.CLITestSuite.initSuite(CLITestSuite.java:103)
Caused by: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.suites.CLITestSuite.start(CLITestSuite.java:87)
	at org.jboss.as.test.integration.domain.suites.CLITestSuite.initSuite(CLITestSuite.java:103)
Caused by: java.util.concurrent.TimeoutException: Managed servers were not started within [120] seconds
	at org.jboss.as.test.integration.domain.suites.CLITestSuite.start(CLITestSuite.java:87)
	at org.jboss.as.test.integration.domain.suites.CLITestSuite.initSuite(CLITestSuite.java:103)
------- Stdout: -------
INFO  [org.xnio] XNIO version 3.3.4.Final
INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.3.4.Final
INFO  [org.jboss.remoting] JBoss Remoting version 4.0.18.Final
 [0m19:11:38,630 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:11:38,784 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:11:39,291 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]

org.jboss.as.test.integration.domain.suites.DomainTestSuite: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.suites.DomainTestSuite.start(DomainTestSuite.java:71)
	at org.jboss.as.test.integration.domain.suites.DomainTestSuite.beforeClass(DomainTestSuite.java:85)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.suites.DomainTestSuite.start(DomainTestSuite.java:69)
	at org.jboss.as.test.integration.domain.suites.DomainTestSuite.beforeClass(DomainTestSuite.java:85)
Caused by: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.suites.DomainTestSuite.start(DomainTestSuite.java:69)
	at org.jboss.as.test.integration.domain.suites.DomainTestSuite.beforeClass(DomainTestSuite.java:85)
Caused by: java.util.concurrent.TimeoutException: Managed servers were not started within [120] seconds
	at org.jboss.as.test.integration.domain.suites.DomainTestSuite.start(DomainTestSuite.java:69)
	at org.jboss.as.test.integration.domain.suites.DomainTestSuite.beforeClass(DomainTestSuite.java:85)
------- Stdout: -------
 [0m19:11:40,620 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:11:40,767 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:11:41,306 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the

org.jboss.as.test.integration.domain.DefaultConfigSmokeTestCase.testStandardHost: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.DefaultConfigSmokeTestCase.testStandardHost(DefaultConfigSmokeTestCase.java:64)
Caused by: java.util.concurrent.TimeoutException: Managed servers were not started within [120] seconds
	at org.jboss.as.test.integration.domain.DefaultConfigSmokeTestCase.testStandardHost(DefaultConfigSmokeTestCase.java:64)
------- Stdout: -------
 [0m19:11:42,670 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:11:42,834 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:11:43,416 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the
[Host Controller]                                         Domain Controller at boot, boot using a
[Host Controller]                                         locally cached copy of the domain
[Host Controller]                                         configuration (see --backup)
[Host Controller]
[Host Controller]
[Host Controller]     -D<name>[=<value>]                  Set a system property
[Host Controller]
[Host Controller]

org.jboss.as.test.integration.domain.DefaultConfigSmokeTestCase.testMasterAndSlave: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.DefaultConfigSmokeTestCase.testMasterAndSlave(DefaultConfigSmokeTestCase.java:85)
Caused by: java.util.concurrent.TimeoutException: Managed servers were not started within [120] seconds
	at org.jboss.as.test.integration.domain.DefaultConfigSmokeTestCase.testMasterAndSlave(DefaultConfigSmokeTestCase.java:85)
------- Stdout: -------
 [0m19:11:44,752 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:11:44,940 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:11:45,511 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the
[Host Controller]                                         Domain Controller at boot, boot using a
[Host Controller]                                         locally cached copy of the domain
[Host Controller]                                         configuration (see --backup)
[Host Controller]
[Host Controller]
[Host Controller]     -D<name>[=<value>]                  Set a system property
[Host Controller]
[Host Controller]

org.jboss.as.test.integration.domain.OrderedChildResourcesTestCase.testOrderedChildResources: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.OrderedChildResourcesTestCase.testOrderedChildResources(OrderedChildResourcesTestCase.java:78)
Caused by: java.util.concurrent.TimeoutException: Managed servers were not started within [120] seconds
	at org.jboss.as.test.integration.domain.OrderedChildResourcesTestCase.testOrderedChildResources(OrderedChildResourcesTestCase.java:78)
------- Stdout: -------
 [0m19:11:46,856 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:11:47,023 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:11:47,532 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the
[Host Controller]                                         Domain Controller at boot, boot using a
[Host Controller]                                         locally cached copy of the domain
[Host Controller]                                         configuration (see --backup)
[Host Controller]
[Host Controller]
[Host Controller]     -D<name>[=<value>]                  Set a system property
[Host Controller]
[Host Controller]

org.jboss.as.test.integration.domain.SlaveHostControllerAuthenticationTestCase: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.SlaveHostControllerAuthenticationTestCase.setupDomain(SlaveHostControllerAuthenticationTestCase.java:99)
Caused by: java.util.concurrent.TimeoutException: Managed servers were not started within [120] seconds
	at org.jboss.as.test.integration.domain.SlaveHostControllerAuthenticationTestCase.setupDomain(SlaveHostControllerAuthenticationTestCase.java:99)
------- Stdout: -------
 [0m19:11:48,794 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:11:48,942 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:11:49,545 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the
[Host Controller]                                         Domain Controller at boot, boot using a
[Host Controller]                                         locally cached copy of the domain
[Host Controller]                                         configuration (see --backup)
[Host Controller]
[Host Controller]
[Host Controller]     -D<name>[=<value>]                  Set a system property
[Host Controller]
[Host Controller]

org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.setUp(ExpressionSupportSmokeTestCase.java:168)
Caused by: java.util.concurrent.TimeoutException: HostController was not started within [120] seconds
	at org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.setUp(ExpressionSupportSmokeTestCase.java:168)
------- Stdout: -------
 [0m19:11:51,029 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:11:51,272 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:11:51,852 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the
[Host Controller]                                         Domain Controller at boot, boot using a
[Host Controller]                                         locally cached copy of the domain
[Host Controller]                                         configuration (see --backup)
[Host Controller]
[Host Controller]
[Host Controller]     -D<name>[=<value>]                  Set a system property
[Host Controller]
[Host Controller]

org.jboss.as.test.integration.domain.mixed.eap620.KernelBehavior620TestSuite: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.mixed.eap620.KernelBehavior620TestSuite.initializeDomain(KernelBehavior620TestSuite.java:42)
Caused by: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.mixed.eap620.KernelBehavior620TestSuite.initializeDomain(KernelBehavior620TestSuite.java:42)
Caused by: java.util.concurrent.TimeoutException: Managed servers were not started within [120] seconds
	at org.jboss.as.test.integration.domain.mixed.eap620.KernelBehavior620TestSuite.initializeDomain(KernelBehavior620TestSuite.java:42)
------- Stdout: -------
INFO  [org.xnio] XNIO version 3.3.4.Final
INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.3.4.Final
INFO  [org.jboss.remoting] JBoss Remoting version 4.0.18.Final
 [0m19:12:22,655 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:12:22,802 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:12:23,249 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the
[Host Controller]                                         Domain Controller at boot, boot using a
[Host Controller]                                         locally cached copy of the domain
[Host Controller]                                         configuration (see --backup)

org.jboss.as.test.integration.domain.mixed.eap620.LegacyConfig620TestSuite: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.mixed.eap620.LegacyConfig620TestSuite.initializeDomain(LegacyConfig620TestSuite.java:37)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.mixed.eap620.LegacyConfig620TestSuite.initializeDomain(LegacyConfig620TestSuite.java:37)
Caused by: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.mixed.eap620.LegacyConfig620TestSuite.initializeDomain(LegacyConfig620TestSuite.java:37)
Caused by: java.util.concurrent.TimeoutException: HostController was not started within [120] seconds
	at org.jboss.as.test.integration.domain.mixed.eap620.LegacyConfig620TestSuite.initializeDomain(LegacyConfig620TestSuite.java:37)
------- Stdout: -------
 [0m19:12:27,467 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:12:27,608 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:12:28,120 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the
[Host Controller]                                         Domain Controller at boot, boot using a
[Host Controller]                                         locally cached copy of the domain
[Host Controller]                                         configuration (see --backup)
[Host Controller]

org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite.initializeDomain(MixedDomain620TestSuite.java:43)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite.initializeDomain(MixedDomain620TestSuite.java:43)
Caused by: java.lang.RuntimeException: Could not start container
	at org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite.initializeDomain(MixedDomain620TestSuite.java:43)
Caused by: java.util.concurrent.TimeoutException: HostController was not started within [120] seconds
	at org.jboss.as.test.integration.domain.mixed.eap620.MixedDomain620TestSuite.initializeDomain(MixedDomain620TestSuite.java:43)
------- Stdout: -------
 [0m19:12:25,238 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
 [0m [0m19:12:25,405 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
 [0m[Host Controller]  [0m19:12:25,912 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final [0m
[Host Controller] WFLYHC0062: Invalid option ''. Use domain.sh --help for information on valid command line arguments and their syntax.
[Host Controller]  [0m [0m
[Host Controller] Usage: domain.sh [args...]
[Host Controller] where args include:
[Host Controller]     --admin-only                        Set the host controller's running type
[Host Controller]                                         to ADMIN_ONLY causing it to open
[Host Controller]                                         administrative interfaces and accept
[Host Controller]                                         management requests but not start
[Host Controller]                                         servers or, if this host controller is
[Host Controller]                                         the master for the domain, accept
[Host Controller]                                         incoming connections from slave host
[Host Controller]                                         controllers.
[Host Controller]
[Host Controller]
[Host Controller]     -b <value>, -b=<value>              Set system property jboss.bind.address
[Host Controller]                                         to the given value
[Host Controller]
[Host Controller]
[Host Controller]     -b<interface>=<value>               Set system property
[Host Controller]                                         jboss.bind.address.<interface> to the
[Host Controller]                                         given value
[Host Controller]
[Host Controller]
[Host Controller]     --backup                            Keep a copy of the persistent domain
[Host Controller]                                         configuration even if this host is not
[Host Controller]                                         the Domain Controller
[Host Controller]
[Host Controller]
[Host Controller]     -c <config>, -c=<config>            Name of the domain configuration file
[Host Controller]                                         to use (default is "domain.xml") (Same
[Host Controller]                                         as --domain-config)
[Host Controller]
[Host Controller]
[Host Controller]     --cached-dc                         If this host is not the Domain
[Host Controller]                                         Controller and cannot contact the
[Host Controller]                                         Domain Controller at boot, boot using a
[Host Controller]                                         locally cached copy of the domain
[Host Controller]                                         configuration (see --backup)
[Host Controller]

org.jboss.as.test.integration.domain.mixed.eap630.KernelBehavior630TestSuite: java.lang.AssertionError: expected:<EAP_6_2_0> but was:<EAP_6_3_0>
	at org.jboss.as.test.integration.domain.mixed.eap630.KernelBehavior630TestSuite.initializeDomain(KernelBehavior630TestSuite.java:44)

##### there are 6 more failed tests, see build details

will reopen once we get fix for domain testsuite into core


User can view a list of books and view details for a single book

Look into a possibility to fetch cover photo, description etc. through some free API.

Bare-bones functionality is completed. New issues to be added for further functionality.


pull request for e2e test at 11/30/2016 07:26:05

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Design a search bar

If you go into the git history (or look at the pictures from the old documentation), you can find the legacy code. We can base our search bar design off the legacy code. We can tweak it up a bit if we wish, but be sure to test this component

This can now be postponed to next semester


Implicit type conversion of lists in to_pandas

Describe the bug
ds = Dataset.from_list([{'a':[1,2,3]}])
ds.to_pandas().a.values[0]

Results in array([1, 2, 3])  -- a rather unexpected conversion of types which made downstream tools expecting lists not happy.
Steps to reproduce the bug
See snippet
Expected behavior
Keep the original type
Environment info
datasets 2.6.1
python 3.8.10

I think this behavior comes from PyArrow:
import pyarrow as pa
t = pa.table({"a": [[0]]})
t.to_pandas().a.values[0]
# array([0])

I believe this has to do with zero-copy: you can get a pandas DataFrame without copying the buffers from arrow, and have the data as numpy arrays.

That's interesting, I guess not much to do here then.


Clarify use of X509V3_set_ctx()

This has been carved out from #16998 because it should be mergeable earlier.
This brings clarifications to the documentation and the code regarding the use of the subject and req parameters of X509V3_set_ctx().
Also document the email:move config option value, which so far was missing from x509v3_config.pod.
Checklist

[x] documentation is added or updated
[ ] tests are added or updated

I suggest having this also in 3.0 because it does not change the API,
and the doc improvements should be good to have there, too.

Closed and re-opened to kick the CI after (intermittent) package installation trouble: https://github.com/openssl/openssl/runs/4332277845?check_suite_focus=true

This pull request is ready to merge

Thanks @t8m and @kaduk for your comments and the approval.
I've adapted the commit messages as suggested, rebased, and merged the PR.