Run error on Windows 10, branch master.

Everything seemed to be ok when I was still in branch 'Add windows support', then I saw the branch had been merged to master, I cloned the app again and built it without any errors, but when I ran the app after npm run pack, I got this error:

Windows 10, branch master, latest code.

same problem

Me too!

@lednhatkhanh @c0b41 @withtobi I had this issue also, it will need some debugging to figure out what exactly is the cause.

Check the version of Node and npm, you should be on the most recent LTS or Latest.
Node -v
npm -v

Install the dependencies
2.1 Python 2.7
2.2 Install the C++ build tools http://landinghub.visualstudio.com/visual-cpp-build-tools ( or if you have Visual Studio installed, open it, start new project, find C++ and install the tools from there if you already have not. )
2.3 npm install --global --production windows-build-tools

Set the Python PATH in the variables and run this
npm config set python C:\tools\python2\python.exe

Install all the npm dependencies
npm i

Build the code
npm start

If it still shows the error :

Go to pty.js
cd app/node_modules/pty.js

Install it
npm i

Try to run the test
npm run test-windows

@stefanivic
Node version:
{ npm: '4.0.2',
  ares: '1.10.1-DEV',
  http_parser: '2.7.0',
  icu: '57.1',
  modules: '51',
  node: '7.0.0',
  openssl: '1.0.2j',
  uv: '1.9.1',
  v8: '5.4.500.36',
  zlib: '1.2.8' }

Result when run npm run test-windows
><EMAIL_ADDRESS>test-windows C:\Users\lednh\Documents\hyper\app\node_modules\pty.js
> set "NODE_ENV=test" && mocha -R spec test-windows

(node:4184) DeprecationWarning: child_process: options.customFds option is deprecated.  System Windows_NT 10.0.14393
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\lednh\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure"
gyp ERR! cwd C:\Users\lednh\Documents\hyper
gyp ERR! node -v v7.1.0
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

Now I tried to delete everything and reclone the repo, now even the npm i failed
><EMAIL_ADDRESS>install C:\Users\lednh\Documents\hyper\node_modules\electron-chromedriver
> node ./download-chromedriver.js

><EMAIL_ADDRESS>install C:\Users\lednh\Documents\hyper\node_modules\husky
> node ./bin/install.js

husky
setting up hooks in .git/hooks
done

><EMAIL_ADDRESS>postinstall C:\Users\lednh\Documents\hyper\node_modules\spawn-sync
> node postinstall

><EMAIL_ADDRESS>postinstall C:\Users\lednh\Documents\hyper\node_modules\electron
> node install.js

events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: write EINVAL
    at exports._errnoException (util.js:1022:11)
    at WriteStream.Socket._writeGeneric (net.js:715:26)
    at WriteStream.Socket._write (net.js:734:8)
    at doWrite (_stream_writable.js:334:12)
    at writeOrBuffer (_stream_writable.js:320:5)
    at WriteStream.Writable.write (_stream_writable.js:247:11)
    at WriteStream.Socket.write (net.js:661:40)
    at WriteStream.stream.write (C:\Users\lednh\Documents\hyper\node_modules\single-line-log\index.js:12:16)
    at process.<anonymous> (C:\Users\lednh\Documents\hyper\node_modules\single-line-log\index.js:17:29)
    at emitOne (events.js:101:20)

@lednhatkhanh are you on Node v7 ?
If yes, uninstall and go to 6.9, this is a known issue.
https://github.com/nodejs/node/issues/9542

But I can run the windows branch smoothly on node 7

Oh, downgrade to node v6 work for the first time. Now I can install deps, the first npm start ends with a blank windows, the second one works, and the third one fails.

pty.js has no Windows binaries afaik.. :/

After attempting to bundle on node 6.9.1 it will fail with the error related to pty.js, and npm start will fail as well with this:
C:\Users\aluca\git\hyper>npm start

> @ start C:\Users\aluca\git\hyper
> concurrently --kill-others --raw "npm run dev" "npm run app"

> @ app C:\Users\aluca\git\hyper
> electron app

> @ dev C:\Users\aluca\git\hyper
> webpack -w

Webpack is watching the files…

A dynamic link library (DLL) initialization routine failed.
\\?\C:\Users\aluca\git\hyper\app\node_modules\pty.js\build\Release\pty.node
App threw an error during load
Error: `pty.js` failed to load. Typically this means that it was built incorrectly. Please check the `README.me` to more info.
    at createPtyJsError (C:\Users\aluca\git\hyper\app\session.js:11:32)
    at Object.<anonymous> (C:\Users\aluca\git\hyper\app\session.js:17:9)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\aluca\git\hyper\app\index.js:30:17)
Hash: 9ac2b66db58c8756562c
Version: webpack 2.1.0-beta.25
Time: 4664ms
           Asset     Size  Chunks             Chunk Names
       bundle.js  4.39 MB       0  [emitted]  main
assets\icons.svg  2.81 kB          [emitted]
    + 316 hidden modules

@alucard0134 I was also getting this issue on Node 7.1 on Arch Linux (not Windows, but I thought this would be nice to mention) x64. It would work fine (npm start) but after trying to npm run pack it would fail, and subsequent npm starts would fail with the same error every time -- pty.js failed to load.

Same error.
Maybe will be better release pre-build version of Hyper for Windows? Thanks.

^ thats difficult if you cant even pack it :^)
@sliceofcode exact same here just running node 6.9, pty.js tests pass as well

That's really strange – I can build it without problems here and on AppVeyor. Also, many people can build it as well 😕
I'll spend some time today or tomorrow on this – I'll reset my Windows 10 VM and write down every step that I follow to make it work.
Meanwhile: here's a .exe and a .deb 😄

thanks sugar daddy ^

also @matheuss probably doubt it but incase M$ inappropiately touched windows so pty wouldnt work my current version/build is 1607, build 14931

Same issue on ubuntu 16.04, @matheuss thanks for the .deb

Same issue on macOS Sierra (10.12.1) when I launched npm start or I ran Hyper.app after npm run pack

Me too

This is really strange as it works fine on my part.
node -v
v6.9.1
npm -v
3.10.9
node-gyp -v
v3.4.0
electron -v
v1.3.2

if this helps, i got this error message upon trying to start ./hyper in linux-unpacked:
Module version mismatch. Expected 50, got 51.
A JavaScript error occurred in the main process
Uncaught Exception:
Error: `pty.js` failed to load. Typically this means that it was built incorrectly. Please check the `README.me` to more info.
    at createPtyJsError (/home/cheesy/dev/prg/hyper/dist/linux-unpacked/resources/app/session.js:11:32)
    at Object.<anonymous> (/home/cheesy/dev/prg/hyper/dist/linux-unpacked/resources/app/session.js:17:9)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/cheesy/dev/prg/hyper/dist/linux-unpacked/resources/app/index.js:30:17)

this line:
Module version mismatch. Expected 50, got 51.

looks really suspicious.
node v7.1.0 and npm 3.10.9 btw.
looking in session.js, you can find this code:
...
  spawn = require('pty.js').spawn;
} catch (err) {
  throw createPtyJsError();
}
...

Adding console.log(err); above createPtyJsError gives me:
Module version mismatch. Expected 50, got 51.
{ Error: Cannot find module '../bin/linux/x64.m50.node'
    at Module._resolveFilename (module.js:455:15)
    at Function.Module._resolveFilename (/home/cheesy/dev/prg/hyper/dist/linux-unpacked/resources/electron.asar/common/reset-search-paths.js:35:12)
    at Function.Module._load (module.js:403:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/cheesy/dev/prg/hyper/dist/linux-unpacked/resources/app/node_modules/pty.js/lib/pty.js:18:9)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12) code: 'MODULE_NOT_FOUND' }
A JavaScript error occurred in the main process
Uncaught Exception:
Error: `pty.js` failed to load. Typically this means that it was built incorrectly. Please check the `README.me` to more info.
    at createPtyJsError (/home/cheesy/dev/prg/hyper/dist/linux-unpacked/resources/app/session.js:11:32)
    at Object.<anonymous> (/home/cheesy/dev/prg/hyper/dist/linux-unpacked/resources/app/session.js:18:9)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/home/cheesy/dev/prg/hyper/dist/linux-unpacked/resources/app/index.js:30:17)

i have no idea what x64.m50.node is. google returns nothing helpful. apparently though, my system can't find it, which i guess is causing the error.
hope this helps.

@sliceofcode try npm rebuild.

@stefanivic that help, unfortunately. 😢 but i did find this on my std{out,err}:
node-pre-gyp ERR! Tried to download: https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v51-linux-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v51 ABI) (falling back to source compile with node-gyp)
make: Entering directory '/home/cheesy/dev/prg/hyper/node_modules/fsevents/build'
  SOLINK_MODULE(target) Release/obj.target/.node
  COPY Release/.node

don't know if that helps.

here it is for windows:
{ Error: Cannot find module '..\bin\win32\x64.m49.node'
    at Module._resolveFilename (module.js:440:15)
    at Function.Module._resolveFilename (C:\Users\aluca\git\hyper\node_modules\electron\dist\resources\electron.asar\common\reset-search-paths.js:35:12)
    at Function.Module._load (module.js:388:25)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\aluca\git\hyper\app\node_modules\pty.js\lib\pty.js:18:9)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12) code: 'MODULE_NOT_FOUND' }
App threw an error during load
Error: `pty.js` failed to load. Typically this means that it was built incorrectly. Please check the `README.me` to more info.
    at createPtyJsError (C:\Users\aluca\git\hyper\app\session.js:11:32)
    at Object.<anonymous> (C:\Users\aluca\git\hyper\app\session.js:18:9)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:458:32)
    at tryModuleLoad (module.js:417:12)
    at Function.Module._load (module.js:409:3)
    at Module.require (module.js:468:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\aluca\git\hyper\app\index.js:30:17)

@alucard0134 try do delete the node_modules from Hyper folder root and from the /app folder. Then do npm install and npm start again.
I'll setup a VirtualBox with Linux and Windows to try and replicate these.
As on my Windows 10 Pro x64 Version 1608, Build 14393.447 it works just fine.

for my fellow arch linux users, i have constructed a pkgbuild that is available here it installs the deb that @matheuss provided, so you can use hyper with first class linux support now!
cd $DIR_WITH_PKGBUILD
makepkg
sudo pacman -U *.tar.xz

nicely done @sliceofcode

So, I'm pretty sure this stems from an issue with electron's custom node runtime and node-gyp'd modules, but I'm not 100% sure. After experiencing the problems listed above I poked and prodded and ended up with a moderately working build after following these steps:
[C:\scratch\hyper]> npm i --save-dev electron-rebuild
[C:\scratch\hyper]> # Added new entry to package.json's scripts:
[C:\scratch\hyper]> # "electron-rebuild": "electron-rebuild -m app/node_modules -w pty.js"
[C:\scratch\hyper]> npm run electron-rebuild
[C:\scratch\hyper]> npm start

This gets me a window that loads, the first tab/shell doesn't work, but a second one does. I believe that this is most likely due to pty.js issues and may be more easily diagnosed/resolvable than the "unable to build" issues:

Error 87:
[C:\scratch\hyper]> net helpmsg 87

The parameter is incorrect.

Running Windows 10 and tested this using node v6.9.1 and v7.1.0, which helps reinforce that it's related to the electron runtime and compiled/native node modules. It's not a complete fix, but it has gotten me further than an error and failure to launch every time. I haven't had more time to play with it, but hopefully this is helpful in some way.

I just installed Ubuntu 16.04 in the VirtualBox and i was able to run Hyper from source. Here is what i did.
1. Fresh install of Ubuntu 16.04
2. Install all the depdendencies
sudo apt-get install nodejs git npm icnsutils graphicsmagick xz-utils
3. Update the nodejs to the latest version :
sudo npm install -g n
sudo n stable
4. Link Nodejs to node
sudo ln -sf /usr/local/n/versions/node//bin/node /usr/bin/node
5. Clone the hyper repo
git clone https://github.com/zeit/hyper.git
6. Change the directory
cd hyper
7. Install all the npm dependencies
npm install
8. Start the Hyper.app
npm start

At this point i had an error :
Error while loading devtools extensions Error: Exited with code 9
at ChildProcess. (/hyper/hyper/hyper/node_modules/cross-unzip/index.js:38:21)

9. Change directory to cross-unizp
cd node_modules/cross-unizp/
10. Install it
npm install
11. Change directory to Hyper root folder
cd .. && cd ..
12. Start the Hyper.app again and it worked.

@stefanivic npm start will work ay ok. but try building it

Thank @matheuss for your .exe file!
I just notice some issues on windows 10 64bit:

It's quite laggy when typing quickly, or use tab key too often. And how can I specify the default path when open hyper on windows 10?
Thank you.

hey babe @matheuss were you ever able to reproduce?

@lednhatkhanh noticed the same problem when using tab for autocomplete: sometimes text switches like this.

I was able to reproduce 😅 #1001 will fix this if it passes on CI 🙏

@matheuss
I still get same error:
E:\hyper (master)
λ npm start

> @ start E:\hyper
> concurrently --kill-others --raw "npm run dev" "npm run app"

[[....................................] - : ] - : infoinfo  usingus[[....................................] | : ] | : infoinfo  usingus

> @ dev E:\hyper
> webpack -w

> @ app E:\hyper
> electron app

Webpack is watching the files…

Cannot find module '..\build\Release\pty.node'
App threw an error during load
Error: `pty.js` failed to load. Typically this means that it was built incorrectly. Please check the `README.me` to more info.
    at createPtyJsError (E:\hyper\app\session.js:11:32)
    at Object.<anonymous> (E:\hyper\app\session.js:17:9)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (E:\hyper\app\index.js:30:17)
Hash: 94c9d99493e090df9905
Version: webpack 2.1.0-beta.27
Time: 3128ms
           Asset     Size  Chunks             Chunk Names
       bundle.js   4.4 MB       0  [emitted]  main
assets/icons.svg  2.85 kB          [emitted]
    + 316 hidden modules

Environment
Operating system and version:
Windows 32-bit 10.0.14393
Node:
6.7.0
npm:
3.10.9
Microsoft Visual C++ Build Tools 2015
2015.3
Thanks.

@Kristinita have you run npm install after you got the latest master?

@matheuss, npm install is successful for me. (I'm sorry, I can not insert more lines, I increased scrollbar's memory in my terminal, but «this will not work on things you've already done — only on things you do after making the change».)

Click here to see output
| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | |     `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | | `--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| |     `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   | +--<EMAIL_ADDRESS>| | |   | | `--<EMAIL_ADDRESS>| | |   | |   +--<EMAIL_ADDRESS>| | |   | |   +--<EMAIL_ADDRESS>| | |   | |   `--<EMAIL_ADDRESS>| | |   | +--<EMAIL_ADDRESS>| | |   | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   | +--<EMAIL_ADDRESS>| | |   | | `--<EMAIL_ADDRESS>| | |   | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   | +--<EMAIL_ADDRESS>| | |   | `--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | |     +--<EMAIL_ADDRESS>| | |     `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | |     `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   |   +--<EMAIL_ADDRESS>|   |   | +--<EMAIL_ADDRESS>|   |   | | `--<EMAIL_ADDRESS>|   |   | +--<EMAIL_ADDRESS>|   |   | +--<EMAIL_ADDRESS>|   |   | +--<EMAIL_ADDRESS>|   |   | +--<EMAIL_ADDRESS>|   |   | +--<EMAIL_ADDRESS>|   |   | `--<EMAIL_ADDRESS>|   |   |   `--<EMAIL_ADDRESS>|   |   +--<EMAIL_ADDRESS>|   |   `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>|     `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>|     `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>|     `--<EMAIL_ADDRESS>|       `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| |     `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| |     `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   |   `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>|     `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   | `--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   +--<EMAIL_ADDRESS>| | |   `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>|     `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | |   `--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   |   +--<EMAIL_ADDRESS>| |   |   `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | | +--<EMAIL_ADDRESS>| |   | | | `--<EMAIL_ADDRESS>| |   | | +--<EMAIL_ADDRESS>| |   | | +--<EMAIL_ADDRESS>| |   | | `--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | | `--<EMAIL_ADDRESS>| |   | |   `--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   |   `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | | `--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | | `--<EMAIL_ADDRESS>| |   | |   `--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   |   `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | | `--<EMAIL_ADDRESS>| |   | |   `--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   |   `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     | +--<EMAIL_ADDRESS>| |     | | `--<EMAIL_ADDRESS>| |     | `--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     | +--<EMAIL_ADDRESS>| |     | +--<EMAIL_ADDRESS>| |     | | +--<EMAIL_ADDRESS>| |     | | | `--<EMAIL_ADDRESS>| |     | | `--<EMAIL_ADDRESS>| |     | +--<EMAIL_ADDRESS>| |     | +--<EMAIL_ADDRESS>| |     | | `--<EMAIL_ADDRESS>| |     | |   `--<EMAIL_ADDRESS>| |     | +--<EMAIL_ADDRESS>| |     | | `--<EMAIL_ADDRESS>| |     | `--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     | `--<EMAIL_ADDRESS>| |     +--<EMAIL_ADDRESS>| |     `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   |   +--<EMAIL_ADDRESS>|   |   | `--<EMAIL_ADDRESS>|   |   +--<EMAIL_ADDRESS>|   |   | +--<EMAIL_ADDRESS>|   |   | +--<EMAIL_ADDRESS>|   |   | `--<EMAIL_ADDRESS>|   |   `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | | +--<EMAIL_ADDRESS>|   | | | `--<EMAIL_ADDRESS>|   | | `--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | | `--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   +--<EMAIL_ADDRESS>|   | `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | | `--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | | `--<EMAIL_ADDRESS>| | | | |   `--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | | +--<EMAIL_ADDRESS>| | | | | `--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | |   `--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | +--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | | `--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | | `--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   +--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | | +--<EMAIL_ADDRESS>| |   | | | +--<EMAIL_ADDRESS>| |   | | | `--<EMAIL_ADDRESS>| |   | | `--<EMAIL_ADDRESS>| |   | +--<EMAIL_ADDRESS>| |   | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   +--<EMAIL_ADDRESS>  | |   | +--<EMAIL_ADDRESS>  | |   | `--<EMAIL_ADDRESS>  | |   |   `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | | `--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  |   `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | |   `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  |   `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | +--<EMAIL_ADDRESS>  | | `--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>  |   `--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    +--<EMAIL_ADDRESS>    | +--<EMAIL_ADDRESS>    | +--<EMAIL_ADDRESS>    | +--<EMAIL_ADDRESS>    | | `--<EMAIL_ADDRESS>    | `--<EMAIL_ADDRESS>    +--<EMAIL_ADDRESS>    +--<EMAIL_ADDRESS>    +--<EMAIL_ADDRESS>    | +--<EMAIL_ADDRESS>    | | `--<EMAIL_ADDRESS>    | `--<EMAIL_ADDRESS>    |   +--<EMAIL_ADDRESS>    |   | `--<EMAIL_ADDRESS>    |   `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>      `--<EMAIL_ADDRESS>
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\7zip-bin\node_modules\7zip-bin-mac):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\7zip-bin\node_modules\7zip-bin-linux):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux","arch":"any"} (current: {"os":"win32","arch":"ia32"})

E:\hyper (master)

Thanks.

@matheuss Are there more recent (Widnows) builds ? I cannot build it here but would like to help and test it.


Have fixtures tab/menu item and page rather than Events

Pointing the Events menu item at Staverton 10 at the moment.


Add OIDC Testuite to CI

There is an (official?) oidc testuite to test IDPs for standard conformance. Needs some research if/how it is usable.
https://github.com/openid-certification
https://github.com/openid-certification/oidctest
https://openid.net/certification/

@IljaN @DeepDiver1975 this is an old issue that was transferred from the archived ocis-konnectd repo a few weeks ago.
Please close if no longer relevant.


NPE in NodeChecker On First Run w/ ES Cluster Down

Fixes #375 - resolves an NPE on the first NodeChecker run if elasticsearch is down.

Coverage increased (+0.01%) to 54.505% when pulling 93f3c481af2e8fa9d7a421d8b4e5e7dbe8cb4066 on gilbode:node_checker_npe into f34fa45e34c9230d58069f8f3e9b86cabfabf603 on searchbox-io:master.

Coverage increased (+0.01%) to 54.505% when pulling b791389caead679d526b648bf140298e0a82ea3e on gilbode:node_checker_npe into f34fa45e34c9230d58069f8f3e9b86cabfabf603 on searchbox-io:master.


Error: recognition request failed

          "BepInEx console output is as follows:

[Info: Console] Broadcasting started
[Info: Unity Log] Error: recognition request failed
[Info: Console] Error: recognition request failed"
Originally posted by @chilianer in https://github.com/Judiks/VoiceShipControl/issues/1#issuecomment-1932150445

@chilianer i have few question.

You sending commands with button or voise activation?
You see that error message each time or sometimes text recognized as well?

Bathicaly this mod working with WEB Speech API and sending request to it with listened audio. Can be a lot cases for your problem. I need more info to envestigate it.
Try to check rocognizer with this page.

1.I use a key.
2.Each time I try to use it, I see the same error message.
Error occurred in recognition: network
It seems like the cause of the problem has been identified as the network.

@chilianer not sure that i able to fix API or Network issue in this case.


GraphQL voyager breaks with large schemas (only with mutations)

When I try to switch queries to mutation GraphQL voyager with a schema that is about 400,000 lines long it breaks, (it just displays a blank screen). It seems though that this schema is just big enough to cause this issue. Can you fix this problem on online version ?

When a schema loaded, Queries are fine

But when i switched to mutations

After few minutes display a blank screen

This is first time for me. I used this tool frequently, this is the best tool to understand and representation of GraphQL Schema. I have already put 200,000 lines of code but never got this error. Can you fix this online version of graphql voyager @IvanGoncharov ?

Now I open console when i switch to mutations, got error.

@IvanGoncharov

can you fix this error online version @IvanGoncharov ?

can you fix this error on online version @IvanGoncharov @RomanHotsiy @knidarkness  ?

the way I see it you have two options-

break your schema in subdomains
increase your machine memory

We are also having this 'non-issue' ;) Is there a reason why ALLOW_MEMORY_GROWTH cannot be used? Can you point to the part of the project where this emscripten compilation is done?

The issue seems to be coming from viz.js  - it has a limit to 256mb.
Looks like this fork https://github.com/aduh95/viz.js would solve the issue. as it has support for ALLOW_MEMORY_GROWTH
Now I am not sure what it will take to reimplement voyager around it.


请问能否支持设置复选框呢

https://stackoverflow.com/questions/58728103/work-with-checkboxes-in-docx-file-with-apache-poi
https://stackoverflow.com/questions/57589810/how-to-create-checkbox-and-input-text-fields-in-docx-document


Add missing tests

These test were missing on #6330 to ensure that the exclusion work as expected.
I need to add this tests because I want to refactor this code without breaking anything.
Waiting for #6829 because this PR goes on top of it.

Warnings

:warning:
This PR is approved with no milestone set. If merged, it won't appear in the detekt release notes.

  Generated by :no_entry_sign: dangerJS against b31283f80601aa15b4e67a18668e3b54794355f0


Add Groq API support and integration

Introduced the Groq API integration into the existing service. Made changes to necessary files to include Groq types, models and updated error handling. Now, users can get Groq service access by adding GROQ_API_KEY to the environment configuration file.

To test this PR you need an Groq API key. You can get one for free here: https://console.groq.com/playground

Thanks for the great contribution! I will check it, and add an option to enter the groq api key in the frontend.
Also it seems that we need to find a better solution in smartgpt.ts to replace the if-statements, this will become messy, in particular if we add even more providers like Google Gemini (which is planned in the near future).
I could imagine an easier solution with a mapping of types, maybe similar to:
  const availableStreams = {
   'openai': OpenAIStream,
   'claude: AnthropicStream,
   'groq': GroqStream
  }

  const stream = await availableStreams[modelName](model, initialSystemPrompt, temperatureToUse, openAIkey, await messages, undefined);

If you find the time to look at this, it would be amazing.
Also, please try to check if 'npm build' runs through before commiting. Thanks already :)

The PR works but still has some rough edged, let me do some fine-tuning before you merge it into main.

Now after the refactoring most of the changes are in teh streamFactory when a new provider is added and the change will be reflected in chat and smartgpt. All providers that follow the openAI API are very easy to add. For providers that dont follow the openAI API also the parsing of the response has to be modified within the streamFactory.
I moved the api-keys into the settings modal to have more space for many more keys.
Due to missing unit tests I am not fully sure if the previous behaviour is still exactly the same but I did a handful of manual tests and it looked  fine.

Thank you again for the awesome contribution! I really like your solutions with the stream factory and the keys. I renamed "Settings" to "API Keys & Settings", that should avoid any confusion.
I still got a faulty output for SmartGPT, when using a Groq model as a resolver or researcher (due to getProvider not working correctly), but i think i fixed this. I integrated all your changes (among others, and including my hotfix) in a new branch (https://github.com/ymetz/smartgpt_ui/tree/we_need_more_speed--adding-groq). If you like, you can have a final look. If you have no objections, i will merge it into main later. Thanks a lot!

thanks for the fix. You can merge it.
I saw that in the home.tsx the handling of the defaultModelId is not yet correct. I can have a look into that once the other branch is merged into main.
The worst that can happen in the current form is that you only set the Groq-key. Opening a new chat the default model still is gpt-3.5. You then have to go to the settings in the header and toggle back to a groq model.


One more fix to has_gen() - to remove it

Wonderful! I was bit by this bug just last night.

Sorry, I've been messing around trying to fix it without seeing much of the big picture.
We are certainly lacking in tests for the entity deletion/creation.
Besides, @malleusinferni reports that some rare stuff is still missing, albeit no panics any more (yay!).


London | Ali Qassab | Module-User-Focused-Data | Form Controls | Week 2

Learners, PR Template
Self checklist

[x] I have committed my files one by one, on purpose, and for a reason
[x] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
[x] I have tested my changes
[x] My changes follow the style guide
[x] My changes meet the requirements of this task

Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.

I have just saw that you have 1 PR for both weeks. Was that intended and spoken from your mentors?
I suppose these should be 2 different PRs.

Yes, you have both week's solutions in this PR. In your terminal, you can checkout main branch, git pull, and create and checkout to a new branch for week 2. This way you will not have your changes from week1 branch.

I have just saw that you have 1 PR for both weeks. Was that intended and spoken from your mentors? I suppose these should be 2 different PRs.

I actually created two separate PRs, one for each week, but I forgot to request a review for the first one. As a result, I submitted both PRs for review at the same time. I apologize for any confusion this may have caused, and I'll make sure to request reviews in a more timely manner moving forward.

I have just saw that you have 1 PR for both weeks. Was that intended and spoken from your mentors? I suppose these should be 2 different PRs.

I actually created two separate PRs, one for each week, but I forgot to request a review for the first one. As a result, I submitted both PRs for review at the same time. I apologize for any confusion this may have caused, and I'll make sure to request reviews in a more timely manner moving forward.


yquake2: init at 7.20

Motivation for this change
Package the Yamagi Quake II client and its related add-on game libraries.
I nested this under pkgs/games/quake2 to accommodate other Quake II engines and hopefully game/demo asset packages in the future.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build yquake2 yquake2-ctf yquake2-ground-zero yquake2-the-reckoning yquake2-all-games

Success on x86_64-linux (full log)
Attempted: yquake2
The following builds were skipped because they don't evaluate on x86_64-linux: yquake2-ctf, yquake2-ground-zero, yquake2-the-reckoning, yquake2-all-games
Partial log (click to expand)
shrinking /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20/lib/yquake2/baseq2/game.so
shrinking /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20/lib/yquake2/ref_soft.so
shrinking /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20/lib/yquake2/quake2
shrinking /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20/lib/yquake2/ref_gl1.so
shrinking /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20/lib/yquake2/q2ded
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20/lib  /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20/bin
patching script interpreter paths in /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20
checking for references to /tmp/nix-build-yquake2-7.20.drv-0 in /nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20...
/nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20

Success on aarch64-linux (full log)
Attempted: yquake2
The following builds were skipped because they don't evaluate on aarch64-linux: yquake2-ctf, yquake2-ground-zero, yquake2-the-reckoning, yquake2-all-games
Partial log (click to expand)
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/ref_gl3.so
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/ref_gl1.so
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/quake2
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/q2ded
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/baseq2/game.so
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib  /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/bin
patching script interpreter paths in /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20
checking for references to /build in /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20...
/nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20

Success on x86_64-linux (full log)
Attempted: yquake2
Partial log (click to expand)
/nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20

Success on aarch64-linux (full log)
Attempted: yquake2
Partial log (click to expand)
/nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20

@GrahamcOfBorg build yquake2 yquake2-ctf yquake2-ground-zero yquake2-the-reckoning yquake2-all-games

Success on aarch64-linux (full log)
Attempted: yquake2
The following builds were skipped because they don't evaluate on aarch64-linux: yquake2-ctf, yquake2-ground-zero, yquake2-the-reckoning, yquake2-all-games
Partial log (click to expand)
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/ref_gl3.so
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/ref_gl1.so
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/quake2
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/q2ded
shrinking /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib/yquake2/baseq2/game.so
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/lib  /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20/bin
patching script interpreter paths in /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20
checking for references to /build in /nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20...
/nix/store/lk3sgdbnq94ix6hyp0jkxs7q11d5d9y0-yquake2-7.20

Failure on x86_64-darwin (full log)
Attempted: yquake2
The following builds were skipped because they don't evaluate on x86_64-darwin: yquake2-ctf, yquake2-ground-zero, yquake2-the-reckoning, yquake2-all-games
Partial log (click to expand)
clang-5.0: warning: argument unused during compilation: '-fno-strict-overflow' [-Wunused-command-line-argument]
[ 68%] Building C object CMakeFiles/game.dir/src/game/player/weapon.c.o
clang-5.0: warning: argument unused during compilation: '-fno-strict-overflow' [-Wunused-command-line-argument]
[ 68%] Building C object CMakeFiles/game.dir/src/game/savegame/savegame.c.o
clang-5.0: warning: argument unused during compilation: '-fno-strict-overflow' [-Wunused-command-line-argument]
[ 69%] Linking C shared module release/baseq2/game.dylib
[ 69%] Built target game
make: *** [Makefile:84: all] Error 2
builder for '/nix/store/rj4dm6cqvb71f58h73yw1mdz7qabfxfv-yquake2-7.20.drv' failed with exit code 2
error: build of '/nix/store/rj4dm6cqvb71f58h73yw1mdz7qabfxfv-yquake2-7.20.drv' failed

Success on x86_64-linux (full log)
Attempted: yquake2
The following builds were skipped because they don't evaluate on x86_64-linux: yquake2-ctf, yquake2-ground-zero, yquake2-the-reckoning, yquake2-all-games
Partial log (click to expand)
copying path '/nix/store/ra2lngp19j822ll5m80z45qvnczq2yb5-libXrandr-1.5.1' from 'https://cache.nixos.org'...
copying path '/nix/store/731aa3qy6v1v6awc24c0frza5d13k7ki-dbus-1.12.6-lib' from 'https://cache.nixos.org'...
copying path '/nix/store/fk455c81dijrbmqirfkngy5y5p5q7i02-libXxf86vm-1.1.4' from 'https://cache.nixos.org'...
copying path '/nix/store/z1awd0gkjajkvc4n2wpdld90hn89llg4-libglvnd-1.0.0' from 'https://cache.nixos.org'...
copying path '/nix/store/r5fdmgpxfsidpgclimp4ykqmh5kakrm5-libpulseaudio-11.1' from 'https://cache.nixos.org'...
copying path '/nix/store/p5j2c7ldxpj9dibz9psm3kswagrpzpd8-libGL-1.0.0' from 'https://cache.nixos.org'...
copying path '/nix/store/580y11zq14xag6ybrvzcbr7k93naman4-SDL2-2.0.8' from 'https://cache.nixos.org'...
copying path '/nix/store/fvmjhyw3gbk73zvrsa24m7v5xvp60hn4-openal-soft-1.18.2' from 'https://cache.nixos.org'...
copying path '/nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20' from 'https://cache.nixos.org'...
/nix/store/id82a5709nmcc74jpk97riv2gwj6adbj-yquake2-7.20


Update Character “tiat-honorskull”

Automatically generated by Netlify CMS

👷 Deploy Preview for 4shame processing.

Name
Link

🔨 Latest commit
52db47db3e077b08b835eaf40efe5826c7024322

🔍 Latest deploy log
https://app.netlify.com/sites/4shame/deploys/63a75b64e6fcdf0008be2242


removing spvcm from meta release -- archived - #1330

This PR removing spvcm from meta release, as it is now archived - https://github.com/pysal/spvcm/issues/18

resolves #1330

I'm not sure whether we deprecated spvcm before, so removing it from meta may be pretty drastic in case we haven't. If we haven't, we should deprecate spvcm during the 24.07 meta cycle with documentation, then remove in 25.01.

dunno either, but also not sure how would we issue a deprecation warning in meta?

OK, so I shouldn't have arched it like we discussed? Should I "unarchive"?

OK, so I shouldn't have arched it like we discussed? Should I "unarchive"?

No, archiving is fine, I don't think we need to revert that.
I'm wondering about the best way to surface the archiving in the meta release.

What about updating the meta README.md like:

Works for me.

So we would keep this pr open until 25.01 release, but I can add the warning to the docs in the 24.07 release.

So we would keep this pr open until the 25.01 release, but I can add the warning to the docs in the 24.07 release.

Probably the best idea. --> Should also post a notice like I suggest in https://github.com/pysal/pysal.github.io/issues/229?


An error

I cant compile through you guide because of error
Error:Could not GET 'https://dl.bintray.com/sdsmdg/Croller/com/sdsmdg/harjot/croller/1.0.0/croller-1.0.0.pom'. Received status code 403 from server: Forbidden

Can you please try again. I am able to compile the library in a new project without any issues.

tried again - nothing changes. Even when i click to this link 'https://dl.bintray.com/sdsmdg/Croller/com/sdsmdg/harjot/croller/1.0.0/croller-1.0.0.pom' in my browser i got "Forbidden" signature

OK, the issue was with my bintray account. I unknowingly chose the "Trial" version instead of the "open source" one. Hopefully it will shifted to an open source account, in a day or two.
Till then you can copy the Croller.java from : here and paste it in  your main java project directory.
Also copy attrs.xml from : here and paste it under /res/values/
Now you can use the library as you like.

Updated the bintray account 👍 . New instructions added in the README.


update cluster-networking dashboard for node level metrics

Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>related issue: https://github.com/open-cluster-management/backlog/issues/12404

@marco - noticed that sum() is baked into these rules
      - instance:node_network_receive_bytes_excluding_lo:rate1m
      - instance:node_network_receive_drop_excluding_lo:rate1m
      - instance:node_network_transmit_bytes_excluding_lo:rate1m
      - instance:node_network_transmit_drop_excluding_lo:rate1m

... so avg() will return same values.
Looking into updating panels for averages

@marco - noticed that sum() is baked into these rules
      - instance:node_network_receive_bytes_excluding_lo:rate1m
      - instance:node_network_receive_drop_excluding_lo:rate1m
      - instance:node_network_transmit_bytes_excluding_lo:rate1m
      - instance:node_network_transmit_drop_excluding_lo:rate1m

... so avg() will return same values.
Looking into updating panels for averages

Discussed with @marcolan018 that we should remove avg queries and related avg panels so only current data is shown.

/retest


Fix error message sanitiziation

Fixes two sanitization issues:

Previous usage of the HandleCloneUserCredentials function did not cover the case where a message contained a sensitive URLs multiple times; only the first usage would be sanitized.
In the MigratePost handler, an unsanitized error could reach the handleCreateError(..) function, which itself does not do any sanitization. As a result, unsanitized URL could be printed in logs.

This PR additionally:

moves shared URL-sanitization code to modules/util
does some refactoring to use net/url instead of manually parsing urls (https://github.com/go-gitea/gitea/pull/3078#discussion_r154536291)

Codecov Report

Merging #3082 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3082      +/-   ##
==========================================
- Coverage   33.43%   33.42%   -0.01%
==========================================
  Files         270      271       +1
  Lines       39595    39603       +8
==========================================
  Hits        13239    13239
- Misses      24466    24474       +8
  Partials     1890     1890

Impacted Files
Coverage Δ

routers/repo/repo.go
21.81% <0%> (-0.16%)
:arrow_down:

models/repo_mirror.go
3.46% <0%> (+0.25%)
:arrow_up:

modules/util/sanitize.go
0% <0%> (ø)

routers/api/v1/repo/repo.go
32.99% <0%> (-0.09%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e59adcd...4f0c5ea. Read the comment docs.

LGTM

LGTM

make LG-TM work

@ethantkoenig please backport this also to #3057.

@ethantkoenig please backport this also to #3078


ImportError: OpenCV loader: missing configuration file: ['config.py'].

Expected behaviour
Using pyinstaller -F MyProgram.py to build exe, but it got error.
Actual behaviour
I write my program with cv2, and it run well,
but after I build it into exe file by pyinstaller -F MyProgram.py it can't run.
below is error log:
Traceback (most recent call last):
File "AutomaticTestTool.py", line 12, in
File "PyInstaller\loader\pyimod03_importers.py", line 546, in exec_module
File "cv2_init_.py", line 180, in
File "cv2_init_.py", line 110, in bootstrap
File "cv2_init_.py", line 108, in load_first_config
ImportError: OpenCV loader: missing configuration file: ['config.py']. Check OpenCV installation.
[12104] Failed to execute script 'AutomaticTestTool' due to unhandled exception!
I have tried:
pip3 install --upgrade opencv-python pip3 install --upgrade pyinstaller
but it no use.
and below is log of pyinstaller :
pyinstaller AutomaticTestTool.py
112 INFO: PyInstaller: 4.5.1
112 INFO: Python: 3.9.1
112 INFO: Platform: Windows-10-10.0.19041-SP0
126 INFO: wrote C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018\AutomaticTestTool.spec
127 INFO: UPX is not available.
130 INFO: Extending PYTHONPATH with paths
['C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018',
'C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018']
456 INFO: checking Analysis
456 INFO: Building Analysis because Analysis-00.toc is non existent
456 INFO: Initializing module dependency graph...
456 INFO: Caching module graph hooks...
472 INFO: Analyzing base_library.zip ...
2559 INFO: Processing pre-find module path hook distutils from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks\pre_find_module_path\hook-distutils.py'.
2559 INFO: distutils: retargeting to non-venv dir 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib'
4096 INFO: Caching module dependency graph...
4309 INFO: running Analysis Analysis-00.toc
4321 INFO: Adding Microsoft.Windows.Common-Controls to dependent assemblies of final executable
required by c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\python.exe
4353 WARNING: lib not found: api-ms-win-core-path-l1-1-0.dll dependency of c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\python39.dll
4369 INFO: Analyzing C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018\AutomaticTestTool.py
4480 INFO: Processing pre-safe import module hook urllib3.packages.six.moves from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks\pre_safe_import_module\hook-urllib3.packages.six.moves.py'.
5703 INFO: Processing pre-find module path hook site from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks\pre_find_module_path\hook-site.py'.
5718 INFO: site: retargeting to fake-dir 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\fake-modules'
6416 INFO: Processing pre-safe import module hook setuptools.extern.six.moves from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks\pre_safe_import_module\hook-setuptools.extern.six.moves.py'.
8234 INFO: Processing module hooks...
8234 INFO: Loading module hook 'hook-certifi.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\_pyinstaller_hooks_contrib\hooks\stdhooks'...
8234 INFO: Loading module hook 'hook-cv2.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\_pyinstaller_hooks_contrib\hooks\stdhooks'...
8249 INFO: Loading module hook 'hook-difflib.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8254 INFO: Loading module hook 'hook-distutils.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8254 INFO: Loading module hook 'hook-distutils.util.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8258 INFO: Loading module hook 'hook-encodings.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8405 INFO: Loading module hook 'hook-heapq.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8405 INFO: Loading module hook 'hook-lib2to3.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8444 INFO: Loading module hook 'hook-multiprocessing.util.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8460 INFO: Loading module hook 'hook-numpy.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8507 INFO: Import to be excluded not found: 'f2py'
8522 INFO: Loading module hook 'hook-numpy._pytesttester.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8527 INFO: Loading module hook 'hook-pickle.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8530 INFO: Loading module hook 'hook-pkg_resources.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
8983 INFO: Processing pre-safe import module hook win32com from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\_pyinstaller_hooks_contrib\hooks\pre_safe_import_module\hook-win32com.py'.
9071 WARNING: Hidden import "pkg_resources.py2_warn" not found!
9071 WARNING: Hidden import "pkg_resources.markers" not found!
9087 INFO: Loading module hook 'hook-setuptools.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\setuptools\distutils_patch.py:25: UserWarning: Distutils was imported before Setuptools. This usage is discouraged and may exhibit undesirable behaviors or errors. Please use Setuptools' objects directly or at least import Setuptools first.
warnings.warn(
9641 INFO: Loading module hook 'hook-sysconfig.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
9641 INFO: Loading module hook 'hook-win32ctypes.core.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
9894 INFO: Loading module hook 'hook-xml.dom.domreg.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
9894 INFO: Loading module hook 'hook-xml.etree.cElementTree.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
9909 INFO: Loading module hook 'hook-xml.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
9909 INFO: Loading module hook 'hook-_tkinter.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
10149 INFO: checking Tree
10149 INFO: Building Tree because Tree-00.toc is non existent
10149 INFO: Building Tree Tree-00.toc
10228 INFO: checking Tree
10228 INFO: Building Tree because Tree-01.toc is non existent
10228 INFO: Building Tree Tree-01.toc
10396 INFO: checking Tree
10396 INFO: Building Tree because Tree-02.toc is non existent
10396 INFO: Building Tree Tree-02.toc
10396 INFO: Loading module hook 'hook-setuptools.msvc.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks'...
10428 INFO: Looking for ctypes DLLs
10474 INFO: Analyzing run-time hooks ...
10474 INFO: Including run-time hook 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_pkgutil.py'
10474 INFO: Including run-time hook 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_multiprocessing.py'
10490 INFO: Including run-time hook 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth_inspect.py'
10495 INFO: Including run-time hook 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\hooks\rthooks\pyi_rth__tkinter.py'
10498 INFO: Including run-time hook 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\_pyinstaller_hooks_contrib\hooks\rthooks\pyi_rth_certifi.py'
10500 INFO: Looking for dynamic libraries
10920 INFO: Looking for eggs
10920 INFO: Using Python library c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\python39.dll
10920 INFO: Found binding redirects:
[]
10920 INFO: Warnings written to C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018\build\AutomaticTestTool\warn-AutomaticTestTool.txt
10983 INFO: Graph cross-reference written to C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018\build\AutomaticTestTool\xref-AutomaticTestTool.html
11034 INFO: checking PYZ
11034 INFO: Building PYZ because PYZ-00.toc is non existent
11034 INFO: Building PYZ (ZlibArchive) C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018\build\AutomaticTestTool\PYZ-00.pyz
11625 INFO: Building PYZ (ZlibArchive) C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018\build\AutomaticTestTool\PYZ-00.pyz completed successfully.
11650 INFO: checking PKG
11650 INFO: Building PKG because PKG-00.toc is non existent
11650 INFO: Building PKG (CArchive) PKG-00.pkg
11690 INFO: Building PKG (CArchive) PKG-00.pkg completed successfully.
11703 INFO: Bootloader c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\bootloader\Windows-64bit\run.exe
11703 INFO: checking EXE
11703 INFO: Building EXE because EXE-00.toc is non existent
11703 INFO: Building EXE from EXE-00.toc
11742 INFO: Copying icons from ['c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\PyInstaller\bootloader\images\icon-console.ico']
11744 INFO: Writing RT_GROUP_ICON 0 resource with 104 bytes
11744 INFO: Writing RT_ICON 1 resource with 3752 bytes
11744 INFO: Writing RT_ICON 2 resource with 2216 bytes
11744 INFO: Writing RT_ICON 3 resource with 1384 bytes
11744 INFO: Writing RT_ICON 4 resource with 37019 bytes
11744 INFO: Writing RT_ICON 5 resource with 9640 bytes
11744 INFO: Writing RT_ICON 6 resource with 4264 bytes
11744 INFO: Writing RT_ICON 7 resource with 1128 bytes
11788 INFO: Appending archive to EXE C:\Users\WNC.T1-1-1-Q-52026\Desktop\1018\build\AutomaticTestTool\AutomaticTestTool.exe
12297 INFO: Building EXE from EXE-00.toc completed successfully.
12304 INFO: checking COLLECT
12304 INFO: Building COLLECT because COLLECT-00.toc is non existent
12304 INFO: Building COLLECT COLLECT-00.toc
21584 INFO: Building COLLECT COLLECT-00.toc completed successfully.
Steps to reproduce
PyInstaller: 4.5.1
Python: 3.9.1
Platform: Windows-10-10.0.19041-SP0(architecture : x64)

opencv-python version
numpy                     1.21.3
opencv-python             <IP_ADDRESS>

Issue submission checklist

[v ] This is not a generic OpenCV usage question (looking for help for coding, other usage questions, homework etc.)

[ v] I have read the README of this repository and understand that this repository provides only an automated build toolchain for OpenCV Python packages (there is no actual OpenCV code here)

[ v] The issue is related to the build scripts in this repository, to the pre-built binaries or is a feature request (such as "please enable this additional dependency")

[ v]  I'm using the latest version of opencv-python

It's already in use, from your logs above:
8234 INFO: Loading module hook 'hook-cv2.py' from 'c:\users\wnc.t1-1-1-q-52026\appdata\local\programs\python\python39\lib\site-packages\_pyinstaller_hooks_contrib\hooks\stdhooks'...
Someone needs to fix it because it doesn't work with the new opencv-python version. Please open an issue to the PyInstaller hook repository, your issue is not really related to this repository: https://github.com/pyinstaller/pyinstaller-hooks-contrib/issues

Thank you!
It's a great help for me!

There is already related issue: https://github.com/pyinstaller/pyinstaller-hooks-contrib/issues/110

which version of opencv-python is work well with pyinstaller?

Try previous release <IP_ADDRESS>: https://pypi.org/project/opencv-python/#history

Hi @clouds1203!
Could you try to reproduce using the latest release of OpenCV Python packages - <IP_ADDRESS>? Some issues with imports were fixed right there.
In addition, I couldn't reproduce this issue with the latest opencv-python version.

In my case, Opencv-python version <IP_ADDRESS> solves this problem.
My PyInstaller: 4.7.

I've taken a deeper look at the problem and reproduced the issue with the latest release (<IP_ADDRESS>).
What I've done:

Firstly, I've installed opencv-python package (<IP_ADDRESS> version), which has all components in <path>\site-packages\cv2, even config.py file is there.

python3 -m pip install -U opencv-python==<IP_ADDRESS>

As the next step I've installed pyinstaller (latest version):

python3 -m pip install -U pyinstaller

I've added test lines for custom app myapp.py:

import cv2

print(cv2.getBuildInformation())

Then I've run pyinstaller for my myapp.py:

python3 -m pyinstaller myapp.py

After building, I've run myapp.exe file.
Error from this issue has appeared:

ImportError: OpenCV loader: missing configuration file: ['config.py']

That's strange that I have config.py file in the cv2 package, but I don't have it in my "app". I've printed LOADER_DIR variable (added print(LOADER_DIR) in <path>\site-packages\cv2\__init__.py) to get the information where I am. So, it showed me the path not to the package, but to some temporary directory (e.g. C:\Users\user\AppData\Local\Temp\_MEI21362\cv2) which is created every time to run my "app". This directory has only cv2.*.pyd and opencv_videoio_ffmpeg*.dll files, but we hardly depends on config*.py files.
I guess to solve this issue, need to fix it here as @skvark mentioned before.
Another temporary solution which has worked for me is to define an absolute path to cv2 package. For example (change <path_to_python>:
python3 -m pyinstaller -F myapp.py --paths="<path_to_python>\Lib\site-packages\cv2"

The fix has been merged in pyinstaller-hooks-contrib repository. When the next release happens there, this problem will be fixed.

The release of pyinstaller-hooks-contrib has happened today and I've tested it - the issue did not happen.
I've done the same pipeline as above, but also upgrading pyinstaller package with --force-reinstall. The steps:

Firstly, I've installed opencv-python package (<IP_ADDRESS> version):

python3 -m pip install -U opencv-python==<IP_ADDRESS>

As the next step I've installed pyinstaller (latest version):

python3 -m pip install -U --force-reinstall pyinstaller

I've added test lines for custom app myapp.py:

import cv2

print(cv2.getBuildInformation())

Then I've run pyinstaller for my myapp.py:

python3 -m pyinstaller myapp.py

After building, I've run myapp.exe file.
I've seen a build information of opencv without any issues.

Closing this issue.


Update VariantRecalibration annotations

Changed 'maxGaussian' [4] to always be enabled for indels
Added '-an SOR'

Validatet!


Containers are out of sync with releases

Deis 1.8.0
Today I've encountered weird issue: deis ps reports all containers as 'destroyed':
web.1 destroyed (v77)
...

deis releases reports last release as v77:
v77     Пн 27 июл 2015 20:18:06 MSK circleci deployed 690d49b

But containers currently running are of version 79:
engine-staging_v79.web.1.service
...

So it looks like two releases are lost somewhere, though containers are there.

@ineu we haven't seen anything like this happen before. Did you have new releases fail to deploy? Any idea how we could reproduce this situation?

No, after rebooting all machines in the cluster it's fine, except one problem: for almost all applications deis releases shows releases older than containers running. Looks like there's been some synchronization problem and information about new releases was lost after rebooting server. Though it was not hardware reset, but normal reboot command.
Maybe it's old fleet/etcd in CoreOS 653 that causes synchronization problems. Don't know where Deis stores its releases information.
ceph -s reported OK.
Anyway, it's fine now and I cannot reproduce it any longer, so I think the ticket can be closed.

Data is stored in the database (postgres) so I don't think it's a sync issue.
In the future, a pg_dump would probably be the easiest way to confirm that the data is the same as expected after a reboot. Thanks!


commit hash added for bitcoin libs

Specify a commit hash for sensitive and critical dependency modules:

Added commit hash for the tested version of depemdency for pdf issue
Added commit hash for bitcoin and crypto libraries

Travis fails for some reason, don't know why

Switched and did a build on this branch, here are the issues that I faced:

yarn install is taking relatively longer (probably due to commit hashes) but is livable
the build is failing due to an error in resolving crypto-js module

Closing due to no further action. Please re-open if required.


error log has insufficient information when type not supported

this error is thrown when a certain is not supported in controller
java.lang.Error: not support def type: class io.swagger.models.properties.BaseIntegerProperty

the type BaseIntegerProperty is not what user specified and the user specified type is not shown in log

related to https://github.com/ServiceComb/ServiceComb-Java-Chassis/issues/210

this JIRA had closed , if it occur again, we will reopen it


Allow invalid styles and show errors

Editing a Maputnik style can be a pain right now. In many places entering an invalid value will cause the input to get in a funny state or just refuse to let you complete the action. For example changing a color input with the value rgba(255, 0, 0, 1) to rgb(255, 0, 0) and you'll see the issue.
Also editing a style via the JSON editor is next to impossible at the moment for similar reasons.
I think we should allow errors to be present in the style, and indicate what layers have errors.
Here's a prototype https://696-84182601-gh.circle-artifacts.com/0/artifacts/build/index.html#0.26/0/0 (working branch https://github.com/maputnik/editor/compare/master...orangemug:feature/allow-invalid-values)
Below is an example where I've modified a layer type to be invalid, backgroun instead of background

Below is an example where I am part way through modifying a color from hsl to hsla and am still missing the forth argument.

Any thoughts or feedback welcome and encouraged 😄

This issue appears in the answers to question “What annoys you about Maputnik?” in the survey (original spelling):

sometimes ctl+v doesnt work if theres is mismatch,it should give error by underline or something

Black Screen with often no error messge once you make a mistake editing the local style file.

Bugs to refresh style (I need to play with JSON to fix issues)

There is already something similar to indicate parse errors:

Closed by PR #620


Claire/buyer profile

Add routing for editing email and password

Styles devise artist/edit and buyer/edit pages
Adds routes through "settings" tab in navbar
Adds preliminary styling for buyers#show method

Related PRs
@melodywei861016 your edit user feature. You should be able to edit all schema attributes except password and email, since this is managed through devise. I've completed the devise portion in this PR, you should manage the avatars and editing other account information.
Screenshots

CC: @clairelin135

Everything looks good! I will let you know if I run into any problems when I work on the edit user feature


Fixed typedoc not working under Windows

Fixes #1

Thank you very much for your work. Everything works well done 😍.


Make bin fails

It seems that some recent changes have broken the clone tool. The install steps of README.md give an error message when make bin is run:
src/github.com/whosonfirst/go-whosonfirst-clone/clone.go:125: cannot use abs_path (type string) as type io.Reader in argument to "github.com/whosonfirst/go-whosonfirst-csv".NewDict:
string does not implement io.Reader (missing Read method)

Oh, oops. Those changes happened on Tuesday. I will fix the underlying
issue and look in to "vendoring" dependencies for the future...
On May 20, 2016 12:39 AM, "Vesa Meskanen"<EMAIL_ADDRESS>wrote:

It seems that some recent changes have broken the clone tool. The install
steps of README.md give an error message when make bin is run:
src/github.com/whosonfirst/go-whosonfirst-clone/clone.go:125: cannot use
abs_path (type string) as type io.Reader in argument to "
github.com/whosonfirst/go-whosonfirst-csv".NewDict:
string does not implement io.Reader (missing Read method)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/whosonfirst/go-whosonfirst-clone/issues/10

Fixed. Apologies for the bad craziness...

Thank you! That was a quick  fix .)

There is a vendor branch which should work with all the dependencies bundled in place. Do you have a moment to try it out and confirm it works?
https://github.com/whosonfirst/go-whosonfirst-clone/tree/vendor
Where "should work" means you just type "make build" as usual :-)
Cheers,

Hi @thisisaaronland, I tested the vendor branch with  'make build' and after that, running a custom data cloning script for finnish data. Everything seemed to work fine.

Thanks!


[BUG] Failure in entitlements process

Is there an existing issue for this?

[X] I have searched the existing issues

What version of the Terraform provider are you using?
1.0.0
What version of the Terraform CLI are you using?
1.5.7
What type of issue are you facing
bug report
Describe the bug
There are errors in the entitlements process
In the beginning, I had 2 resources for the entitlements, one for shared and the other for amount.
I tried to reduce the number of entitlements for each resource up to 9 and also to change the terraform code to work with dependencies, but still, the code failed.
Erros Log
TerraformFile
entitlements_file
Expected Behavior
The expected behavior is that I will have only 2 entitlements resources like before
Entitlements_before
and that the process will end successfully
Steps To Reproduce

you can use the entitlements from Entitlements
You can use the two entitlements resources from here Terraform_code

User's Role Collections

Subaccount Viewer
Subaccount Administrator
Subaccount Service Administrator

Add screenshots to help explain your problem
No response
Additional context
No response

I can give you permission to subaccount

Trying to reproduce the issue on a BTP life  landscape using the following setup:
variables.tf
###
# Entitlements - that needs to configure with amount
# Count: 12
###
variable "entitlements_amount" {
  description = "List of entitlements defined with amount for a BTP subaccount"
  type = list(object({
    description = string
    name        = string
    plan        = string
    amount      = number
  }))

  default = [
    {
      description = "Application Logging Service"
      name        = "application-logs"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "Cloud Foundry Runtime"
      name        = "APPLICATION_RUNTIME"
      plan        = "MEMORY"
      amount      = 2
    },
    {
      description = "auditlog"
      name        = "auditlog"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "auditlog"
      name        = "auditlog"
      plan        = "oauth2"
      amount      = 1
    },
    {
      description = "Credential Store"
      name        = "credstore"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "ABAP Environment"
      name        = "abap"
      plan        = "abap_compute_unit"
      amount      = 1
    },
    {
      description = "ABAP Environment"
      name        = "abap"
      plan        = "hana_compute_unit"
      amount      = 1
    },
    {
      description = "ABAP Solution"
      name        = "abap-solution"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "Custom Domain Service"
      name        = "custom-domain-manager"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "Application Autoscaler"
      name        = "autoscaler"
      plan        = "lite"
      amount      = 2
    },
    {
      description = "Cloud Logging"
      name        = "cloud-logging"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "Kyma Runtime"
      name        = "kymaruntime"
      plan        = "aws"
      amount      = 1
    }

  ]
}

###
# Entitlements shared units, not need to set an amount
# Count: 18
###
variable "entitlements_shared_units" {
  description = "List of entitlements shared units for a BTP subaccount"
  type = list(object({
    description = string
    name        = string
    plan        = string
  }))

  default = [
    {
      description = "Cloud Portal Service"
      name        = "PortalApplication"
      plan        = "standard"
    },
    {
      description = "Cloud Portal Service (Application)"
      name        = "portal"
      plan        = "standard"
    },
    {
      description = "Connectivity Service"
      name        = "connectivity"
      plan        = "lite"
    },
    {
      description = "SAP Content Agent Service"
      name        = "content-agent"
      plan        = "application"
    },
    {
      description = "Destination Service"
      name        = "destination"
      plan        = "lite"
    },
    {
      description = "Feature Flags"
      name        = "feature-flags-dashboard"
      plan        = "dashboard"
    },
    {
      description = "Feature Flags"
      name        = "feature-flags"
      plan        = "standard"
    },
    {
      description = "Feature Flags"
      name        = "feature-flags"
      plan        = "lite"
    },
    {
      description = "HTML5 Application Repository Service"
      name        = "html5-apps-repo"
      plan        = "app-host"
    },
    {
      description = "HTML5 Application Repository Service"
      name        = "html5-apps-repo"
      plan        = "app-runtime"
    },
    {
      description = "SAP Malware Scanning Service"
      name        = "malware-scanner"
      plan        = "clamav"
    },
    {
      description = "SAP Business Application Studio"
      name        = "sapappstudio"
      plan        = "standard-edition"
    },
    {
      description = "SAP Build Work Zone, standard edition"
      name        = "SAPLaunchpad"
      plan        = "standard"
    },
    {
      description = "SAP Content Agent Service"
      name        = "content-agent"
      plan        = "standard"
    },
    {
      description = "Cloud Portal Service"
      name        = "portal"
      plan        = "standard"
    },
    {
      description = "SAP HANA Cloud"
      name        = "hana-cloud"
      plan        = "hana"
    },
    {
      description = "SAP HANA Schemas & HDI Containers"
      name        = "hana"
      plan        = "hdi-shared"
    },
    {
      description = "Alert Notification"
      name        = "alert-notification"
      plan        = "standard"
    }
  ]
}

main.tf
## create subaccount
resource "btp_subaccount" "my_project" {
  name      = "Subbacount Retest 537"
  subdomain = "my-subaccount-retest537"
  region    = "us10"
}

## Add entitlement to subaccount with amount
resource "btp_subaccount_entitlement" "entitlements" {
  for_each = {
    for index, entitlement in var.entitlements_amount :
    index => entitlement
  }

  amount        = each.value.amount
  plan_name     = each.value.plan
  service_name  = each.value.name
  subaccount_id = btp_subaccount.my_project.id
}

resource "btp_subaccount_entitlement" "entitlements_shared_units" {
  for_each = {
    for index, entitlement in var.entitlements_shared_units :
    index => entitlement
  }

  plan_name     = each.value.plan
  service_name  = each.value.name
  subaccount_id = btp_subaccount.my_project.id
}

Count: 12 entitlements with amount; 18 entitlements without amount
Result: Creation of subaccount with entitlements was successful. Execution happened in parallel to check for throttling issues

@MatanElitzur : Currently error is not reproducible. Does the error occur with specific service/service plan combinations? If yes can you please add the corresponding service and plan combinations that cause the error.
After an error, does a subsequent execution of terraform apply fix the issue?

@MatanElitzur : Currently error is not reproducible. Does the error occur with specific service/service plan combinations? If yes can you please add the corresponding service and plan combinations that cause the error.
After an error, does a subsequent execution of terraform apply fix the issue?

I will try to find the problematic service

This is the first problematic
{
group  = "UI5 Flexibility Design and Configuration"
name   = "ui5-flexibility-design-and-configuration"
plan   = "design-and-configuration"
amount = 3
},

Adjusted the variable entitlements_amount according to problematic services. The updated variables.tf file looks like this:
###
# Entitlements - that needs to configure with amount
# Count: 14
###
variable "entitlements_amount" {
  description = "List of entitlements defined with amount for a BTP subaccount"
  type = list(object({
    description = string
    name        = string
    plan        = string
    amount      = number
  }))

  default = [
    {
      description = "Application Logging Service"
      name        = "application-logs"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "Cloud Foundry Runtime"
      name        = "APPLICATION_RUNTIME"
      plan        = "MEMORY"
      amount      = 2
    },
    {
      description = "auditlog"
      name        = "auditlog"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "auditlog"
      name        = "auditlog"
      plan        = "oauth2"
      amount      = 1
    },
    {
      description = "Credential Store"
      name        = "credstore"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "ABAP Environment"
      name        = "abap"
      plan        = "abap_compute_unit"
      amount      = 1
    },
    {
      description = "ABAP Environment"
      name        = "abap"
      plan        = "hana_compute_unit"
      amount      = 1
    },
    {
      description = "ABAP Solution"
      name        = "abap-solution"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "Custom Domain Service"
      name        = "custom-domain-manager"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "Application Autoscaler"
      name        = "autoscaler"
      plan        = "lite"
      amount      = 2
    },
    {
      description = "Cloud Logging"
      name        = "cloud-logging"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "Kyma Runtime"
      name        = "kymaruntime"
      plan        = "aws"
      amount      = 1
    },
    {
      description = "Mobile Services"
      name        = "mobile-services"
      plan        = "standard"
      amount      = 1
    },
    {
      description = "UI5 Flexibility Design and Configuration"
      name        = "ui5-flexibility-design-and-configuration"
      plan        = "design-and-configuration"
      amount      = 1
    }
  ]
}

###
# Entitlements shared units, not need to set an amount
# Count: 18
###
variable "entitlements_shared_units" {
  description = "List of entitlements shared units for a BTP subaccount"
  type = list(object({
    description = string
    name        = string
    plan        = string
  }))

  default = [
    {
      description = "Cloud Portal Service"
      name        = "PortalApplication"
      plan        = "standard"
    },
    {
      description = "Cloud Portal Service (Application)"
      name        = "portal"
      plan        = "standard"
    },
    {
      description = "Connectivity Service"
      name        = "connectivity"
      plan        = "lite"
    },
    {
      description = "SAP Content Agent Service"
      name        = "content-agent"
      plan        = "application"
    },
    {
      description = "Destination Service"
      name        = "destination"
      plan        = "lite"
    },
    {
      description = "Feature Flags"
      name        = "feature-flags-dashboard"
      plan        = "dashboard"
    },
    {
      description = "Feature Flags"
      name        = "feature-flags"
      plan        = "standard"
    },
    {
      description = "Feature Flags"
      name        = "feature-flags"
      plan        = "lite"
    },
    {
      description = "HTML5 Application Repository Service"
      name        = "html5-apps-repo"
      plan        = "app-host"
    },
    {
      description = "HTML5 Application Repository Service"
      name        = "html5-apps-repo"
      plan        = "app-runtime"
    },
    {
      description = "SAP Malware Scanning Service"
      name        = "malware-scanner"
      plan        = "clamav"
    },
    {
      description = "SAP Business Application Studio"
      name        = "sapappstudio"
      plan        = "standard-edition"
    },
    {
      description = "SAP Build Work Zone, standard edition"
      name        = "SAPLaunchpad"
      plan        = "standard"
    },
    {
      description = "SAP Content Agent Service"
      name        = "content-agent"
      plan        = "standard"
    },
    {
      description = "Cloud Portal Service"
      name        = "portal"
      plan        = "standard"
    },
    {
      description = "SAP HANA Cloud"
      name        = "hana-cloud"
      plan        = "hana"
    },
    {
      description = "SAP HANA Schemas & HDI Containers"
      name        = "hana"
      plan        = "hdi-shared"
    },
    {
      description = "Alert Notification"
      name        = "alert-notification"
      plan        = "standard"
    }
  ]
}

I executed the following retest setups:
Scenario	Expected Result	Result after application
Entitlement of the two problematic services only	The two entitlements are added successfully	✅
Entitlement of type entitlements_amount only including problematic services	All 14 entitlements are added successfully	✅
Entitlement of all types (entitlements_amount + entitlements_shared_units)	All 32 entitlements are added successfully	✅

Hi @lechnerc77
what about if you will add another entitlement or add quota to a not problematic service and update the subaccount
Does this scenario pass as well?

@MatanElitzur
Retest:

Create a subaccount with 14 entitlements
Update subaccount with one additional new entitlement and changed quota of an entitlement from step 1.

Result: New entitlement is created and quota is updated successfully

Remark: As the loop is index based, new entitlements must be added at the end of the array defined in the variables as otherwise unwanted deletion and re-creations might occur.

I close this issue as non reproduceable as the create in parallel as well as updates work. Deletion also can be executed successfully.


Add retrieval of record status (in CS or not) to Response

Support a Handler.config option check_record_status which defaults to true

resolved by #87


Using mamba with a small terminal gives weird outputs

Note: On the gif you see I typed conda, but it's of course an alias for mamba on my machine ;)

I also encountered the same problem. But this surprise to me that it depends on term size.
Seems it is really depends on term size, because mamba works well only in full screen now.
But all other functions works well.
Terminal: Alacritty
mamba    0.3.8    py37h6d3251c_0    conda-forge
Operating System: Manjaro Linux
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0
Kernel Version: 5.7.0-3-MANJARO
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 11,4 GiB


Remove Vector feature flag

Related to https://github.com/CartoDB/cartodb/issues/13461
We need to remove the feature flag that enables vector (tangram) rendering from the backend and from the DB. We won't support tangram anymore.
What do you think about this @javitonino ?

Can we close this one?

I'm checking the code base and I don't see any place where vector_vs_raster flag is being used so I think we can remove that flag without a problem. What do you think @javitonino ?

I think so :fire:

Deleted


WIQL samples in tables aren't rendering correctly

The "Include these query clauses" columns appear to be using triple backticks and some underscores that aren't rendering correctly on the doc site or GH

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0efcf77b-29e3-61fe-2dfb-cbea0561e720
Version Independent ID: e17b1af0-a501-9bf7-53ee-94492479c06b
Content: Query by account, user name, workflow or board changes - VSTS & TFS
Content Source: docs/work/track/query-by-workflow-changes.md
Product: devops
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

@nschonni - Thank you for the feedback. I'm not seeing any issue viewing in Chrome or Edge. Can you be more specific as to what the format issue is?

I think maybe i'm getting confused by the use of _ in the code blocks

@nschonni - OK. I'm closing this as the underscores are in the code syntax by design.


Gem v2.9.0 doesn't include the docker transport

It's most likely that I'm really bad at this, but when trying to use transport name:docker I get Could not load the 'docker' transport from the load path. and when I look in gem environment gemdir/gems/kitchen-docker-2.9.0/lib/kitchen there is no transport directory. This is weird, because here in GH it's sitting there.
I can install the gem from GH but I'm wondering if maybe the lib is missing from the gemspec?

As stated here https://github.com/test-kitchen/kitchen-docker/pull/340#issuecomment-533171077, nobody is able to relase this gem for over 3 monthe now...
@stuartpreston @jeffreycoe When will this finally be done?

Yes I'm afraid it's difficult to say when this will happen. This project is fully staffed by volunteers and a limited number of those volunteers have the ability to build/release the gem. Until then, to get the latest fixes and patches, you will need to build the gem locally from the master branch and then install it into your environment.

@stuartpreston Could you provide instructions on how to build the gem locally in the meantime?

Sure, you clone the repo and then:
gem build .\kitchen-docker.gemspec
gem install .\kitchen-docker-version.gem
If you’re installing into the Chef DK or Workstation Ruby then prefix these commands with chef

Thanks!

@robertlabrie We were able to get a new release created, and version 2.10 contains the new docker transport. Please open a new issue if you have any problems with using this release.


Playground changes

New playground changes:

Playgrounds can be loaded with a full URL, for example: https://playgroundcdn1.azureedge.net/pg/QY1WYT/revision/0
fixed frame.html to fit the new architecture
caching and page speed improvements

This is the version deployed to https://playgroundcdn1.azureedge.net/, which is not yet the version on playground.babylonjs.com

URL-Lowercasing is being deployed, might experience a few 404s in the next hour