How to use with next.js?

I tried following next.config.js
const LicensePlugin = require('webpack-license-plugin');

const nextConfig = {
  // If you change the basePaths, also change path for favicon in _document.js
  basePath: '/mica-tool-wGlobal/python/front_end/out',
  reactStrictMode: true,
  images: {
    unoptimized: true // required for static export to work
  },
  webpack: (config) => {
    config.resolve.fallback = {
      'fs': false
    };

    config.plugins = [new LicensePlugin()]

    return config;
  }

};

// eslint-disable-next-line unicorn/prefer-module
module.exports = nextConfig;

and got
npm run build

><EMAIL_ADDRESS>build
> next build && next export

- info Linting and checking validity of types
- info Disabled SWC as replacement for Babel because of custom Babel configuration "babel.config.json" https://nextjs.org/docs/messages/swc-disabled
(node:17744) [DEP_WEBPACK_COMPILATION_OPTIMIZE_CHUNK_ASSETS] DeprecationWarning: optimizeChunkAssets is deprecated (use Compilation.hooks.processAssets instead and use one of Compilation.PROCESS_ASSETS_STAGE_* as stage option)
(Use `node --trace-deprecation ...` to show where the warning was created)
Failed to compile.

./node_modules/next/dist/pages/_app.js
TypeError: Cannot read properties of undefined (reading 'traceChild')
    at Object.nextBabelLoaderOuter (C:\python_env\workspace\micat\front_end\node_modules\next\dist\build\babel\loader\index.js:31:46)

./node_modules/next/dist/pages/_document.js
TypeError: Cannot read properties of undefined (reading 'traceChild')
    at Object.nextBabelLoaderOuter (C:\python_env\workspace\micat\front_end\node_modules\next\dist\build\babel\loader\index.js:31:46)

./node_modules/next/dist/pages/_error.js
TypeError: Cannot read properties of undefined (reading 'traceChild')
    at Object.nextBabelLoaderOuter (C:\python_env\workspace\micat\front_end\node_modules\next\dist\build\babel\loader\index.js:31:46)

Import trace for requested module:
./node_modules/next/dist/pages/_error.js

./src/pages/[id-mode]/[id-region]/index.js
TypeError: Cannot read properties of undefined (reading 'traceChild')
    at Object.nextBabelLoaderOuter (C:\python_env\workspace\micat\front_end\node_modules\next\dist\build\babel\loader\index.js:31:46)

Import trace for requested module:
./src/pages/[id-mode]/[id-region]/index.js

HookWebpackError: Cannot read properties of undefined (reading 'traceChild')
    at makeWebpackError (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:28:311139)
    at C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:28:105980
    at eval (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:58:1)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
-- inner error --
TypeError: Cannot read properties of undefined (reading 'traceChild')
    at TerserPlugin.optimize (C:\python_env\workspace\micat\front_end\node_modules\next\dist\build\webpack\plugins\terser-webpack-plugin\src\index.js:92:44)
    at C:\python_env\workspace\micat\front_end\node_modules\next\dist\build\webpack\plugins\terser-webpack-plugin\src\index.js:259:31
    at fn (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:28:69698)
    at _next0 (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:50:17)
    at eval (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:66:1)
    at eval (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:11:1)
    at C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:28:69336
    at Hook.eval [as callAsync] (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:7:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:26021)
    at C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:28:69505
caused by plugins in Compilation.hooks.processAssets
TypeError: Cannot read properties of undefined (reading 'traceChild')
    at TerserPlugin.optimize (C:\python_env\workspace\micat\front_end\node_modules\next\dist\build\webpack\plugins\terser-webpack-plugin\src\index.js:92:44)
    at C:\python_env\workspace\micat\front_end\node_modules\next\dist\build\webpack\plugins\terser-webpack-plugin\src\index.js:259:31
    at fn (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:28:69698)
    at _next0 (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:50:17)
    at eval (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:66:1)
    at eval (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:11:1)
    at C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:28:69336
    at Hook.eval [as callAsync] (eval at create (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:28867), <anonymous>:7:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:13:26021)
    at C:\python_env\workspace\micat\front_end\node_modules\next\dist\compiled\webpack\bundle5.js:28:69505

> Build failed because of webpack errors
- info Creating an optimized production build .

Without the extra plugin entry npm run build works fine.

@fhg-isi Afaik next already uses webpack plugins, so the way you'd use add this plugin is this - which we're using successfully with the latest next major version at @cosuno:
const nextConfig = {
  webpack: (config, { dev }) => {
      // Add OSS license information to production bundle
      if (!dev) {
        const WebpackLicensePlugin = require('webpack-license-plugin');
        config.plugins.push(new WebpackLicensePlugin(/* options */))
      }

      return config;
    },
};


Improve editor popups with multiple screens

Hopefully this PR will be able to fix multi-screen support.
Fixes #37320
Fixes #38591

I saw your comment on IRC, I was unable to fix two screen bugs because hardware limitation (I'm trapped on Brazil because Coronavirus, and only have my notebook with limited hardware).
Set the position and size with XSizeHints is obsolete (https://tronche.com/gui/x/xlib/ICC/client-to-window-manager/wm-normal-hints.html), to set the position.
A better aproach is with https://tronche.com/gui/x/xlib/window/configure.html
But I was unable to do that for my condition. If you need to talk something you can write here or send me a IRC Private message.

Oh sorry. I didn't saw you are working on it...

I tested this PR and #37320 doesn't happen anymore.

X11 comments:
Cannot continue due to window position checks returning (0,0) sometimes and sometimes not. I have tried combining XGetWindowAttributes with XQueryTree and XTranslateCoordinates but it doesn't fix the problem. It may be the window manager being insane, but I still don't know.
Having initial coordinates at (0,0) is a problem if the function Point2i DisplayServerX11::window_get_position(WindowID p_window) is called before getting the real ones so that function could be replace with one that recomputes the coordinates using a working method. That race could happen in DisplayServerX11::window_set_current_screen(int p_screen, WindowID p_window).
I have tried setting XConfigureWindow as @kuruk-mm (I hope you are well) suggested on the create window function but I didn't get different results. I will be pushing that structure so he won't have to make these changes.
To set a new screen for the window, the trick could be taking the current coordinates and subtracting the current screen offset (screen_get_position). Then getting the new screen offset and adding it to the previous subtraction. But we require the window position to be the real one.
X11 in conclusion: XGetWindowAttributes or XTranslateCoordinates sometimes returns incorrect positions when the editor is not in the default/primary screen. Watch the print_line() in _window_changed and the print_line() in _create_window while randomly clicking "Scene, Project, Debug, Editor and Help"  dropdown menus in the editor. This must be fixed to allow moving windows within screens reliably.
Due to being a problem that a lot of people will encounter I have decided to simply adapt this PR to be merged so that it is not tried to be solved multiple times.
@HaSa1002 if you're able to test your PR after this one gets merged as I tried your fix but it didn't work on Linux so you will be able to merge your changes on the gui tooltip_popup (I didn't try the tooltip tho).
This PR doesn't fix popups at all on non default/primary screens when using > 1 screens on X11.

In X11, we're  currently saving the coordinates in the _create_window() function to the rect provided as argument to the function but after making a  XMoveResizeWindow() call. The problem of this is that we may not be able to set the first window position (the WM will probably place it somewhere else, like would happen with tiling WMs but it doesn't have to be tiled to ignore your placement). As a consequence, the saved coordinates may not be correct and up to date with the real position when making the window (this should only happen once).
I would recommend to use ConfigureNotify event as a source of truth for the real position of the window, which means that only _window_changed() function should modify and save coordinates of the window structure.
Having said that, XSync only makes sure that the command is sent, received and processed by the X server which means that it still has to give us the REAL coordinates back sending the client a ConfigureNotify event.
In conclusion, I have not found any other method to get real coordinates other than waiting for ConfigureNotify event and updating the saved coordinates accordingly (without using any type of transformation as coordinates should be global like happens in MacOS and should happen in Windows) when jumping on the callback to set the new rect in the popup class.
Future work could concentrate on waiting for the first ConfigureNotify event inside the _create_window() function or searching for another way to retrieve real coordinates (which I don't recommend if you're not an expert with X11).

Requesting rebase.

Sorry for the late review. It seems that we have now another PR to solve this problem: https://github.com/godotengine/godot/pull/52280. But it looks like this one might solve more situation. Would you mind a rebase?
This PR will likely need a review from @reduz, as I am not familiar enough with windows positioning.

This one is more exhaustive.
It will also fix #47217 issue if merge.

As this PR has 10 conflicting files (which would require me to download, compile and test the code after changes or patch the code from the open PRs only and add the code changes that have been left out) I would suggest merging #52280 and #42117.
#41395 mitigated tooltip positioning and with #40922 it is possible that X11 may work correctly after these two are merged.
However, if after merging  #52280 and #42117, someone finds that in X11 windows (tooltips will be probably be already fixed) are still placed in the first screen and not in the screen where the editor (which is the parent window) is running, create a new PR adding the changes from the scene/main/window.cpp file from this PR.
If in X11 anyone still has problems after merging these two PR mentioned above, compile the engine with both the changes from scene/main/window.cpp and platform/linuxbsd/display_server_x11.cpp and if it works, create a new PR with only these changes.
Be aware that when this PR was made, the code here was tested on at least 2 KDE desktops and an Ubuntu one (Gnome or Unity, I don't remember), working fine (tiling WMs worked but the windows or tooltips ocuppied a big screen area and I don't know if they were supposed to).

Alright, closing as per the above comment. :)


Jail Command

I reckon Simpleserver should merge the jail command with master and add a disable option to the config.xml...
I donno, It is just an idea...

The jail feature isn't complete yet, that's why it's on its own branch.

Why what is wrong with it? Couldn't you create a system where you can create custom commands and custom combination of commands in the config file like:
/jail =

demote player to lower rank
warp player to location : i.e. jail

And then add an area protection around the jail...


DXLinkStreamer sends a CHANNEL_REQUEST for a channel that is already open

It could be useful to call subscribe multiple times with the same event type on a given DXLinkStreamer—for example, to request quotes for more symbols than can fit in one WebSocket message. However, when I actually try to do it, the first call to subscribe works, but subsequent ones cause the DXLinkStreamer to incorrectly send a CHANNEL_REQUEST again.
Here's a script that demonstrates the problem on tastytrade version 6.3:
import asyncio
import itertools
import logging

import dotenv
import tastytrade

logging.basicConfig(level=logging.DEBUG)
LOG = logging.getLogger(__name__)

async def main():
    env = dotenv.dotenv_values()
    user = env["TASTYTRADE_USERNAME"]
    password = env["TASTYTRADE_PASSWORD"]

    session = tastytrade.ProductionSession(user, password)

    options = tastytrade.instruments.get_option_chain(session, "SPX")
    example_options = list(itertools.chain(*options.values()))[:3]

    async with tastytrade.DXLinkStreamer(session) as streamer:
        for option in example_options:
            LOG.info("Subscribing to %s", option.streamer_symbol)
            await streamer.subscribe(
                tastytrade.dxfeed.EventType.QUOTE,
                [option.streamer_symbol])

        for _ in example_options:
            quote = await streamer.get_event(tastytrade.dxfeed.EventType.QUOTE)
            LOG.info("Received quote for %s", quote.eventSymbol)

if __name__ == "__main__":
    asyncio.run(main())

After the usual authentication messages, it produces these logs:
INFO:__main__:Subscribing to .SPXW231205C1200
DEBUG:tastytrade:sending subscription: {'type': 'CHANNEL_REQUEST', 'channel': 7, 'service': 'FEED', 'parameters': {'contract': 'AUTO'}}
DEBUG:websockets.client:> TEXT '{"type": "CHANNEL_REQUEST", "channel": 7, "serv...: {"contract": "AUTO"}}' [96 bytes]
DEBUG:websockets.client:< TEXT '{"type":"CHANNEL_OPENED","channel":7,"service":...O","subFormat":"LIST"}}' [106 bytes]
DEBUG:tastytrade:received: {'type': 'CHANNEL_OPENED', 'channel': 7, 'service': 'FEED', 'parameters': {'contract': 'AUTO', 'subFormat': 'LIST'}}
DEBUG:tastytrade:sending subscription: {'type': 'FEED_SUBSCRIPTION', 'channel': 7, 'add': [{'symbol': '.SPXW231205C1200', 'type': 'Quote'}]}
DEBUG:websockets.client:> TEXT '{"type": "FEED_SUBSCRIPTION", "channel": 7, "ad...00", "type": "Quote"}]}' [101 bytes]
INFO:__main__:Subscribing to .SPXW231205P1200
DEBUG:tastytrade:sending subscription: {'type': 'CHANNEL_REQUEST', 'channel': 7, 'service': 'FEED', 'parameters': {'contract': 'AUTO'}}
DEBUG:websockets.client:> TEXT '{"type": "CHANNEL_REQUEST", "channel": 7, "serv...: {"contract": "AUTO"}}' [96 bytes]
DEBUG:tastytrade:sending subscription: {'type': 'FEED_SUBSCRIPTION', 'channel': 7, 'add': [{'symbol': '.SPXW231205P1200', 'type': 'Quote'}]}
DEBUG:websockets.client:> TEXT '{"type": "FEED_SUBSCRIPTION", "channel": 7, "ad...00", "type": "Quote"}]}' [101 bytes]
INFO:__main__:Subscribing to .SPXW231205C1400
DEBUG:tastytrade:sending subscription: {'type': 'CHANNEL_REQUEST', 'channel': 7, 'service': 'FEED', 'parameters': {'contract': 'AUTO'}}
DEBUG:websockets.client:> TEXT '{"type": "CHANNEL_REQUEST", "channel": 7, "serv...: {"contract": "AUTO"}}' [96 bytes]
DEBUG:tastytrade:sending subscription: {'type': 'FEED_SUBSCRIPTION', 'channel': 7, 'add': [{'symbol': '.SPXW231205C1400', 'type': 'Quote'}]}
DEBUG:websockets.client:> TEXT '{"type": "FEED_SUBSCRIPTION", "channel": 7, "ad...00", "type": "Quote"}]}' [101 bytes]
DEBUG:websockets.client:< TEXT '{"type":"FEED_CONFIG","channel":7,"dataFormat":..."askPrice","askSize"]}}' [266 bytes]
DEBUG:tastytrade:received: {'type': 'FEED_CONFIG', 'channel': 7, 'dataFormat': 'FULL', 'aggregationPeriod': 0.0, 'eventFields': {'Quote': ['eventType', 'eventSymbol', 'eventTime', 'sequence', 'timeNanoPart', 'bidTime', 'bidExchangeCode', 'bidPrice', 'bidSize', 'askTime', 'askExchangeCode', 'askPrice', 'askSize']}}
DEBUG:websockets.client:< TEXT '{"type":"ERROR","channel":7,"error":"BAD_ACTION...h id already exists 7"}' [94 bytes]
DEBUG:websockets.client:< TEXT '{"type":"ERROR","channel":7,"error":"BAD_ACTION...h id already exists 7"}' [94 bytes]
DEBUG:websockets.client:< TEXT '{"type":"FEED_DATA","channel":7,"data":[{"event...3171.8,"askSize":1.0}]}' [735 bytes]
DEBUG:tastytrade:received: {'type': 'ERROR', 'channel': 7, 'error': 'BAD_ACTION', 'message': 'Channel with id already exists 7'}
DEBUG:websockets.client:= connection is CLOSING
DEBUG:websockets.client:> CLOSE 1000 (OK) [2 bytes]
DEBUG:websockets.client:< CLOSE 1000 (OK) [2 bytes]
DEBUG:websockets.client:= connection is CLOSED
DEBUG:websockets.client:x closing TCP connection
DEBUG:tastytrade:sending keepalive message: {'type': 'KEEPALIVE', 'channel': 0}

And then the program freezes.
It seems that DXLinkStreamer already has a _subscription_state variable to track which channels are open, so to solve the issue, could be enough to add a self._subscription_state[event_type] != 'CHANNEL_OPENED' check.
However, I also wanted to draw attention to the fact that the error doesn't get propagated to the caller. Instead of terminating with an exception, the program just freezes forever. If you don't have debug logging enabled, you won't know what the problem is. This seems like something that's worth changing in order to make future problems easier to notice.

Thanks for opening this! That definitely wasn't intended behavior. Fixing it!


Doesn't seem to work with current Chipotle order site

Looks like the new order site broke chipsandguac. None of the API works for me, logged-in or not.

You're not wrong =). It basically broke when the new site launched late last year. I've been working on an update to this module and I've just about finished it. The new ordering site is easier in some ways and harder in others, but I think I've got most of the updates made. It ended up being a rewrite. Would love to get someone else to test it; I'll update this issue when it's checked into a branch!

Is this working for the current Chipotle website now? I'm getting an exception thrown every time I tried to log in.

Know it's been a long time, but I'd be more than willing to help out in any way that I can. Looking at making an easier way for my company to place their orders online for me to pick up on my way into work and this library has a lot of promise!

Yeah does not seem to work at all anymore. Would be willing to help out as well.

Has anyone made progress on getting it to work with the new website?

Has anyone made progress on getting it to work with the new website?


Fix Dockerfile after latests deps updates

📖 Description
The Docker image crash on startup with the following error:
Error loading shared library libstdc++.so.6: No such file or directory (needed by /app/erts-12.0.2/bin/beam.smp)
Error loading shared library libgcc_s.so.1: No such file or directory (needed by /app/erts-12.0.2/bin/beam.smp)
...

Installing the missing runtime dependencies seems to resolve this issues.
📓 References
https://elixirforum.com/t/docker-run-error-loading-shared-library-libstdc-so-6-and-libgcc-s-so-1/40496
🦀 Dispatch

#dispatch/elixir

🦀 Requesting reviewers for this pull request:

@remi (contributor with 0 commits in the last 90 days and 188 commits overall)
@alarochelle (reviewer for the elixir stack)


Microsoft.DotNet.Props was not found

Windows 10 x64
node v6.7.0
npm v4.0.2
.NET Core 1.0.1 tools Preview 2
.NET Core 1.1 SDK
tsc v2.0.10 (same results with v1.8)
VS Code
VS2015
VS2017
I get the following error when I run the React generator (yarn v0.17.8):
C:\MyFiles\ViewModel\repros\wReact>yo
? 'Allo ManuelDeLeon! What would you like to do? Aspnetcore Spa

Make sure you are in the directory you want to scaffold into.
This generator can also be run with: yo aspnetcore-spa

     _-----_     ╭──────────────────────────╮
    |       |    │  Welcome to the ASP.NET  │
    |--(o)--|    │   Core Single-Page App   │
   `---------´   │        generator!        │
    ( _´U`_ )    ╰──────────────────────────╯
    /___A___\   /
     |  ~  |
   __'.___.'__
 ´   `  |° ´ Y `

? Framework React
? Your project name wReact
Will restore NPM dependencies using 'yarn' installed at C:\Users\manuel.de.leon\AppData\Roaming\npm\yarn.CMD

I'm all done. Running npm install for you to install the required dependencies. If this fails, try running the command yourself.

   create package.json
   create .babelrc
   create appsettings.json
   create ClientApp\boot.tsx
   create ClientApp\components\Counter.tsx
   create ClientApp\components\FetchData.tsx
   create ClientApp\components\Home.tsx
   create ClientApp\components\Layout.tsx
   create ClientApp\components\NavMenu.tsx
   create ClientApp\css\site.css
   create ClientApp\routes.tsx
   create Controllers\HomeController.cs
   create Controllers\SampleDataController.cs
   create Dockerfile
   create package.json.tmp
   create Program.cs
   create project.json
   create README.md
   create Startup.cs
   create .gitignore
   create node_modules\_placeholder.txt
   create WReact.xproj
   create tsconfig.json
   create Views\_ViewImports.cshtml
   create Views\_ViewStart.cshtml
   create Views\Home\Index.cshtml
   create Views\Shared\_Layout.cshtml
   create Views\Shared\Error.cshtml
   create web.config
   create webpack.config.js
   create webpack.config.vendor.js
   create wwwroot\dist\_placeholder.txt
   create wwwroot\favicon.ico
yarn install v0.17.8
info No lockfile found.
warning<EMAIL_ADDRESS>No license field
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@types%2freact-router: self signed certificate in certificate chain".
info If you think this is a bug, please open a bug report with the information provided in "C:\\MyFiles\\ViewModel\\repros\\wReact\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
C:\MyFiles\ViewModel\repros\wReact\WReact.xproj(8,3): error MSB4019: The imported project "C:\Program Files\dotnet\sdk\1.0.0-preview3-004056\Extensions\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
The system cannot find the path specified.
The system cannot find the path specified.

     _-----_     ╭───────────────────────╮
    |       |    │      Bye from us!     │
    |--(o)--|    │       Chat soon.      │
   `---------´   │      Yeoman team      │
    ( _´U`_ )    │    http://yeoman.io   │
    /___A___\   /╰───────────────────────╯
     |  ~  |
   __'.___.'__
 ´   `  |° ´ Y `

By the way, with yarn v0.16.1 I get the following set of errors:
C:\MyFiles\ViewModel\repros\wReact>yo
? 'Allo ManuelDeLeon! What would you like to do? Aspnetcore Spa

Make sure you are in the directory you want to scaffold into.
This generator can also be run with: yo aspnetcore-spa

     _-----_     ╭──────────────────────────╮
    |       |    │  Welcome to the ASP.NET  │
    |--(o)--|    │   Core Single-Page App   │
   `---------´   │        generator!        │
    ( _´U`_ )    ╰──────────────────────────╯
    /___A___\   /
     |  ~  |
   __'.___.'__
 ´   `  |° ´ Y `

? Framework React
? Your project name wReact
Will restore NPM dependencies using 'yarn' installed at C:\Users\manuel.de.leon\AppData\Roaming\npm\yarn.CMD

I'm all done. Running npm install for you to install the required dependencies. If this fails, try running the command yourself.

   create package.json
   create .babelrc
   create appsettings.json
   create ClientApp\boot.tsx
   create ClientApp\components\Counter.tsx
   create ClientApp\components\FetchData.tsx
   create ClientApp\components\Home.tsx
   create ClientApp\components\Layout.tsx
   create ClientApp\components\NavMenu.tsx
   create ClientApp\css\site.css
   create ClientApp\routes.tsx
   create Controllers\HomeController.cs
   create Controllers\SampleDataController.cs
   create Dockerfile
   create package.json.tmp
   create Program.cs
   create project.json
   create README.md
   create Startup.cs
   create .gitignore
   create node_modules\_placeholder.txt
   create WReact.xproj
   create tsconfig.json
   create Views\_ViewImports.cshtml
   create Views\_ViewStart.cshtml
   create Views\Home\Index.cshtml
   create Views\Shared\_Layout.cshtml
   create Views\Shared\Error.cshtml
   create web.config
   create webpack.config.js
   create webpack.config.vendor.js
   create wwwroot\dist\_placeholder.txt
   create wwwroot\favicon.ico
yarn install v0.16.1
info No lockfile found.
warning<EMAIL_ADDRESS>No license field
[1/4] Resolving packages...
[2/4] Fetching packages...
warning<EMAIL_ADDRESS>The platform "win32" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
[4/4] Building fresh packages...
[1/1] ⠁ fsevents: node-pre-gyp ERR!
[-/1] ⠁ waiting...
[-/1] ⠁ waiting...
[-/1] ⠁ waiting...
error Error running install script for optional dependency: "C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents: Command failed.\nExit code: 1\nCommand: C:\\windows\\system32\\cmd.exe\nArguments: /d /s /c node-pre-gyp install --fallback-to-build\nDirectory: C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\nOutput:\nnode-pre-gyp info it worked if it ends with ok\nnode-pre-gyp info using<EMAIL_ADDRESS>info using<EMAIL_ADDRESS>| win32 | x64\nnode-pre-gyp info check checked for \"C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node\" (not found)\nnode-pre-gyp http GET https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v48-win32-x64.tar.gz\nnode-pre-gyp http 404 https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v48-win32-x64.tar.gz\nnode-pre-gyp ERR! Tried to download: https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v48-win32-x64.tar.gz \nnode-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v48 ABI) (falling back to source compile with node-gyp) \nnode-pre-gyp http Pre-built binary not available for your system, looked for https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.0.15/fse-v1.0.15-node-v48-win32-x64.tar.gz \n\r\nC:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents>if not defined npm_config_node_gyp (node \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\bin\\node-gyp-bin\\\\..\\..\\node_modules\\node-gyp\\bin\\node-gyp.js\" clean )  else (node  clean ) \r\ngyp info it worked if it ends with ok\ngyp info using<EMAIL_ADDRESS>info using<EMAIL_ADDRESS>| win32 | x64\ngyp info ok \n\r\nC:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents>if not defined npm_config_node_gyp (node \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\bin\\node-gyp-bin\\\\..\\..\\node_modules\\node-gyp\\bin\\node-gyp.js\" configure --fallback-to-build --module=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node --module_name=fse --module_path=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64 )  else (node  configure --fallback-to-build --module=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node --module_name=fse --module_path=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64 ) \r\ngyp info it worked if it ends with ok\ngyp info using<EMAIL_ADDRESS>info using<EMAIL_ADDRESS>| win32 | x64\ngyp info spawn C:\\Python27\\python.EXE\ngyp info spawn args [ 'C:\\\\Users\\\\manuel.de.leon\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\yarn\\\\node_modules\\\\node-gyp\\\\gyp\\\\gyp_main.py',\ngyp info spawn args   'binding.gyp',\ngyp info spawn args   '-f',\ngyp info spawn args   'msvs',\ngyp info spawn args   '-G',\ngyp info spawn args   'msvs_version=auto',\ngyp info spawn args   '-I',\ngyp info spawn args   'C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\build\\\\config.gypi',\ngyp info spawn args   '-I',\ngyp info spawn args   'C:\\\\Users\\\\manuel.de.leon\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\yarn\\\\node_modules\\\\node-gyp\\\\addon.gypi',\ngyp info spawn args   '-I',\ngyp info spawn args   'C:\\\\Users\\\\manuel.de.leon\\\\.node-gyp\\\\6.7.0\\\\include\\\\node\\\\common.gypi',\ngyp info spawn args   '-Dlibrary=shared_library',\ngyp info spawn args   '-Dvisibility=default',\ngyp info spawn args   '-Dnode_root_dir=C:\\\\Users\\\\manuel.de.leon\\\\.node-gyp\\\\6.7.0',\ngyp info spawn args   '-Dnode_gyp_dir=C:\\\\Users\\\\manuel.de.leon\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\yarn\\\\node_modules\\\\node-gyp',\ngyp info spawn args   '-Dnode_lib_file=node.lib',\ngyp info spawn args   '-Dmodule_root_dir=C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents',\ngyp info spawn args   '--depth=.',\ngyp info spawn args   '--no-parallel',\ngyp info spawn args   '--generator-output',\ngyp info spawn args   'C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\build',\ngyp info spawn args   '-Goutput_dir=.' ]\nTraceback (most recent call last):\r\n  File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\gyp_main.py\", line 16, in <module>\r\n    sys.exit(gyp.script_main())\r\n  File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\__init__.py\", line 545, in script_main\r\n    return main(sys.argv[1:])\r\n  File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\__init__.py\", line 538, in main\r\n    return gyp_main(args)\r\n  File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\__init__.py\", line 523, in gyp_main\r\n    generator.GenerateOutput(flat_list, targets, data, params)\r\n  File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\generator\\msvs.py\", line 2003, in GenerateOutput\r\n    sln_projects, project_objects, flat=msvs_version.FlatSolution())\r\n  File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\generator\\msvs.py\", line 1762, in _GatherSolutionFolders\r\n    return _DictsToFolders('', root, flat)\r\n  File \"C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\gyp\\pylib\\gyp\\generator\\msvs.py\", line 1715, in _DictsToFolders\r\n    for folder, contents in bucket.iteritems():\r\nAttributeError: 'MSVSProject' object has no attribute 'iteritems'\r\ngyp ERR! configure error \ngyp ERR! stack Error: `gyp` failed with exit code: 1\ngyp ERR! stack     at ChildProcess.onCpExit (C:\\Users\\manuel.de.leon\\AppData\\Roaming\\npm\\node_modules\\yarn\\node_modules\\node-gyp\\lib\\configure.js:305:16)\ngyp ERR! stack     at emitTwo (events.js:106:13)\ngyp ERR! stack     at ChildProcess.emit (events.js:191:7)\ngyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)\ngyp ERR! System Windows_NT 10.0.10586\ngyp ERR! command \"C:\\\\Program Files\\\\nodejs\\\\node.exe\" \"C:\\\\Users\\\\manuel.de.leon\\\\AppData\\\\Roaming\\\\npm\\\\node_modules\\\\yarn\\\\node_modules\\\\node-gyp\\\\bin\\\\node-gyp.js\" \"configure\" \"--fallback-to-build\" \"--module=C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\lib\\\\binding\\\\Release\\\\node-v48-win32-x64\\\\fse.node\" \"--module_name=fse\" \"--module_path=C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\lib\\\\binding\\\\Release\\\\node-v48-win32-x64\"\ngyp ERR! cwd C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\ngyp ERR! node -v v6.7.0\ngyp ERR! node-gyp -v v3.4.0\ngyp ERR! not ok \nnode-pre-gyp ERR! build error \nnode-pre-gyp ERR! stack Error: Failed to execute 'node-gyp.cmd configure --fallback-to-build --module=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64\\fse.node --module_name=fse --module_path=C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\lib\\binding\\Release\\node-v48-win32-x64' (1)\nnode-pre-gyp ERR! stack     at ChildProcess.<anonymous> (C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\\node_modules\\node-pre-gyp\\lib\\util\\compile.js:83:29)\nnode-pre-gyp ERR! stack     at emitTwo (events.js:106:13)\nnode-pre-gyp ERR! stack     at ChildProcess.emit (events.js:191:7)\nnode-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:877:16)\nnode-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)\nnode-pre-gyp ERR! System Windows_NT 10.0.10586\nnode-pre-gyp ERR! command \"C:\\\\Program Files\\\\nodejs\\\\node.exe\" \"C:\\\\MyFiles\\\\ViewModel\\\\repros\\\\wReact\\\\node_modules\\\\fsevents\\\\node_modules\\\\node-pre-gyp\\\\bin\\\\node-pre-gyp\" \"install\" \"--fallback-to-build\"\nnode-pre-gyp ERR! cwd C:\\MyFiles\\ViewModel\\repros\\wReact\\node_modules\\fsevents\nnode-pre-gyp ERR! node -v v6.7.0\nnode-pre-gyp ERR! node-pre-gyp -v v0.6.29\nnode-pre-gyp ERR! not success Saved lockfile.
Done in 23.66s.
C:\MyFiles\ViewModel\repros\wReact\WReact.xproj(8,3): error MSB4019: The imported project "C:\Program Files\dotnet\sdk\1.0.0-preview3-004056\Extensions\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
Hash: a3af6b1f3df9e38bd254
Version: webpack 1.13.3
Time: 3217ms
                               Asset     Size  Chunks             Chunk Names
89889688147bd7575d6327160d64e760.svg   109 kB          [emitted]
                           vendor.js  1.48 MB       0  [emitted]  vendor
                          vendor.css   315 kB       0  [emitted]  vendor
   [0] dll vendor 12 bytes {0} [built]
    + 294 hidden modules
Child extract-text-webpack-plugin:
        + 7 hidden modules
Hash: 4f2367645d019aede5f4
Version: webpack 1.13.3
Time: 4380ms
      Asset     Size  Chunks             Chunk Names
    main.js  45.4 kB       0  [emitted]  main
main.js.map  30.3 kB       0  [emitted]  main
    + 16 hidden modules

ERROR in ./ClientApp/components/FetchData.tsx
(16,19): error TS2345: Argument of type '(data: WeatherForecast[]) => void' is not assignable to parameter of type '(value: IResponse) => void | PromiseLike<void>'.
  Types of parameters 'data' and 'value' are incompatible.
    Type 'IResponse' is not assignable to type 'WeatherForecast[]'.
      Property 'length' is missing in type 'IResponse'.

     _-----_     ╭───────────────────────╮
    |       |    │      Bye from us!     │
    |--(o)--|    │       Chat soon.      │
   `---------´   │      Yeoman team      │
    ( _´U`_ )    │    http://yeoman.io   │
    /___A___\   /╰───────────────────────╯
     |  ~  |
   __'.___.'__
 ´   `  |° ´ Y `

Did you install VS2017, it installs .NET Core 1.1 with it, I believe this is part of the problem. Since the projects are setup for 1.0.1.

I'll try removing .NET Core 1.1 SDK and installing v1.0.1

Duplicate of #440 ?
Probably

Yep,  removing .NET Core 1.1 SDK and installing v1.0.1 fixed it (didn't uninstall VS2017)

The other fix is adding a global.json that tells the project to use your local 1.0.1 copy.
https://github.com/MarkPieszak/aspnetcore-angular2-universal/blob/master/global.json#L3
Glad you got it fixed! @ManuelDeLeon

@MarkPieszak
I get the same error when I try to deploy to Azure App Services:
     1>Project "D:\home\site\repository\Jsservicesviewmodel.xproj" on node 1 (Publish target(s)).
     1>D:\home\site\repository\Jsservicesviewmodel.xproj(8,3): error MSB4019: The imported project "D:\Program Files (x86)\dotnet\sdk\1.0.0-preview3-004056\Extensions\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
     1>Done Building Project "D:\home\site\repository\Jsservicesviewmodel.xproj" (Publish target(s)) -- FAILED.

Build FAILED.

What can I do to deploy it on Azure App Services since it doesn't like the default .xproj?

The error came up even after adding a global.json file?

I then get "path too long" =/
Command: "D:\home\site\deployments\tools\deploy.cmd"
Handling ASP.NET Core Web Application deployment.
Restoring packages for D:\home\site\repository\project.json...
  GET https://api.nuget.org/v3-flatcontainer/microsoft.aspnetcore.reactservices/index.json
  OK https://api.nuget.org/v3-flatcontainer/microsoft.aspnetcore.reactservices/index.json 160ms
  GET https://api.nuget.org/v3-flatcontainer/microsoft.aspnetcore.reactservices/1.0.0-beta-000019/microsoft.aspnetcore.reactservices.1.0.0-beta-000019.nupkg
  OK https://api.nuget.org/v3-flatcontainer/microsoft.aspnetcore.reactservices/1.0.0-beta-000019/microsoft.aspnetcore.reactservices.1.0.0-beta-000019.nupkg 141ms
Restoring packages for tool 'Microsoft.AspNetCore.Razor.Tools' in D:\home\site\repository\project.json...
Restoring packages for tool 'Microsoft.AspNetCore.Server.IISIntegration.Tools' in D:\home\site\repository\project.json...
Restoring packages for tool 'Microsoft.DotNet.Watcher.Tools' in D:\home\site\repository\project.json...
Committing restore...
Lock file has not changed. Skipping lock file write. Path: D:\home\site\repository\project.lock.json
D:\home\site\repository\project.json
Restore completed in 6374ms.

NuGet Config files used:
    C:\DWASFiles\Sites\#1jssviewmodel\AppData\NuGet\NuGet.Config

Feeds used:
    https://api.nuget.org/v3/index.json
Publishing repository for .NETCoreApp,Version=v1.0
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>No license field.
Hash: 14681ea815803bf8a9a8
Version: webpack 1.13.3
Time: 22721ms
    Asset    Size  Chunks             Chunk Names
vendor.js  437 kB       0  [emitted]  vendor
   [0] dll vendor 12 bytes {0} [built] [1 error]
    + 285 hidden modules
ERROR in Cannot find module 'caniuse-db/features-json/transforms2d.json'
 @ dll vendor
Hash: 7152126a5b6cfc6a8d0d4870620e3462c6bfa961
Version: webpack 1.13.3
Child
    Hash: 7152126a5b6cfc6a8d0d
    Version: webpack 1.13.3
    Time: 267ms
        + 1 hidden modules

    ERROR in Cannot find module 'core-js/library/fn/symbol/iterator'
Child
    Hash: 4870620e3462c6bfa961
    Version: webpack 1.13.3
    Time: 251ms
        + 1 hidden modules

    ERROR in Cannot find module 'core-js/library/fn/symbol/iterator'
Project repository (.NETCoreApp,Version=v1.0) will be compiled because expected outputs are missing
Compiling repository for .NETCoreApp,Version=v1.0

Compilation succeeded.
    0 Warning(s)
    0 Error(s)

Time elapsed 00:00:50.9344088

Configuring the following project for use with IIS: 'D:\local\Temp\8d41556b6683d27'
Updating web.config at 'D:\local\Temp\8d41556b6683d27\web.config'
Configuring project completed successfully
publish: Published to D:\local\Temp\8d41556b6683d27
Published 1/1 projects successfully
KuduSync.NET from: 'D:\local\Temp\8d41556b6683d27' to: 'D:\home\site\wwwroot'
Deleting file: 'hostingstart.html'
Copying file: 'appsettings.json'
Copying file: 'Microsoft.AspNetCore.Antiforgery.dll'
Copying file: 'Microsoft.AspNetCore.Authorization.dll'
Copying file: 'Microsoft.AspNetCore.Cors.dll'
Copying file: 'Microsoft.AspNetCore.Cryptography.Internal.dll'
Copying file: 'Microsoft.AspNetCore.DataProtection.Abstractions.dll'
Copying file: 'Microsoft.AspNetCore.DataProtection.dll'
Copying file: 'Microsoft.AspNetCore.Diagnostics.Abstractions.dll'
Copying file: 'Microsoft.AspNetCore.Diagnostics.dll'
Copying file: 'Microsoft.AspNetCore.Hosting.Abstractions.dll'
Copying file: 'Microsoft.AspNetCore.Hosting.dll'
Copying file: 'Microsoft.AspNetCore.Hosting.Server.Abstractions.dll'
Copying file: 'Microsoft.AspNetCore.Html.Abstractions.dll'
Copying file: 'Microsoft.AspNetCore.Http.Abstractions.dll'
Copying file: 'Microsoft.AspNetCore.Http.dll'
Copying file: 'Microsoft.AspNetCore.Http.Extensions.dll'
Copying file: 'Microsoft.AspNetCore.Http.Features.dll'
Copying file: 'Microsoft.AspNetCore.HttpOverrides.dll'
Copying file: 'Microsoft.AspNetCore.JsonPatch.dll'
Copying file: 'Microsoft.AspNetCore.Localization.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.Abstractions.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.ApiExplorer.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.Core.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.Cors.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.DataAnnotations.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.Formatters.Json.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.Localization.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.Razor.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.Razor.Host.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.TagHelpers.dll'
Copying file: 'Microsoft.AspNetCore.Mvc.ViewFeatures.dll'
Copying file: 'Microsoft.AspNetCore.NodeServices.dll'
Copying file: 'Microsoft.AspNetCore.Razor.dll'
Copying file: 'Microsoft.AspNetCore.Razor.Runtime.dll'
Copying file: 'Microsoft.AspNetCore.Routing.Abstractions.dll'
Copying file: 'Microsoft.AspNetCore.Routing.dll'
Copying file: 'Microsoft.AspNetCore.Server.IISIntegration.dll'
Copying file: 'Microsoft.AspNetCore.Server.Kestrel.dll'
Copying file: 'Microsoft.AspNetCore.SpaServices.dll'
Copying file: 'Microsoft.AspNetCore.StaticFiles.dll'
Copying file: 'Microsoft.AspNetCore.WebUtilities.dll'
Copying file: 'Microsoft.DotNet.InternalAbstractions.dll'
Copying file: 'Microsoft.Extensions.Caching.Abstractions.dll'
Copying file: 'Microsoft.Extensions.Caching.Memory.dll'
Copying file: 'Microsoft.Extensions.Configuration.Abstractions.dll'
Copying file: 'Microsoft.Extensions.Configuration.Binder.dll'
Copying file: 'Microsoft.Extensions.Configuration.CommandLine.dll'
Omitting next output lines...
Processed 2000 files...
Processed 4260 files...
Processed 6507 files...
Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Failed exitCode=1, command="kudusync" -v 50 -f "D:\local\Temp\8d41556b6683d27" -t "D:\home\site\wwwroot" -n "D:\home\site\deployments\7d6a896e5d4affe6efc616b19b684b16ca392f1b\manifest" -p "D:\Program Files (x86)\SiteExtensions\Kudu\59.51122.2559\bin\Scripts\firstDeploymentManifest" -i ".git;.hg;.deployment;deploy.cmd"
An error has occurred during web site deployment.
npm WARN package.json<EMAIL_ADDRESS>No repository field.\r\nnpm WARN package.json<EMAIL_ADDRESS>No license field.\r\nError: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.\r\nD:\Program Files (x86)\SiteExtensions\Kudu\59.51122.2559\bin\Scripts\starter.cmd "D:\home\site\deployments\tools\deploy.cmd"

@SteveSandersonMS Any ideas what could be causing this one, we figured out the 1.1 Core issue, but now he's getting path too long etc when deploying to Azure.
It almost looks like some things didn't get installed properly through npm?

Did you remember to specify a Node version for Azure to use via WEBSITE_NODE_DEFAULT_VERSION on the Azure management portal? If you don't, it will use NPM 2.x which fails with path-too-long errors. See deployment steps at http://blog.stevensanderson.com/2016/10/04/angular2-template-for-visual-studio/#now-lets-deploy.

It has the default: WEBSITE_NODE_DEFAULT_VERSION: 4.4.7

4.4.7 is too old. It includes NPM version 2.15.8. You need NPM >=3.0 for it to work properly on Windows.
Let us know how you go with Node 6.7.0.

Different log but it still ends up with "path too long" plus there's ERROR in Cannot find module 'core-js/library/fn/symbol/iterator' in the middle.
Command: "D:\home\site\deployments\tools\deploy.cmd"
Handling ASP.NET Core Web Application deployment.
Restoring packages for D:\home\site\repository\project.json...
  GET https://api.nuget.org/v3-flatcontainer/microsoft.aspnetcore.reactservices/index.json
  OK https://api.nuget.org/v3-flatcontainer/microsoft.aspnetcore.reactservices/index.json 152ms
  GET https://api.nuget.org/v3-flatcontainer/microsoft.aspnetcore.reactservices/1.0.0-beta-000019/microsoft.aspnetcore.reactservices.1.0.0-beta-000019.nupkg
  OK https://api.nuget.org/v3-flatcontainer/microsoft.aspnetcore.reactservices/1.0.0-beta-000019/microsoft.aspnetcore.reactservices.1.0.0-beta-000019.nupkg 137ms
Restoring packages for tool 'Microsoft.AspNetCore.Razor.Tools' in D:\home\site\repository\project.json...
Restoring packages for tool 'Microsoft.AspNetCore.Server.IISIntegration.Tools' in D:\home\site\repository\project.json...
Restoring packages for tool 'Microsoft.DotNet.Watcher.Tools' in D:\home\site\repository\project.json...
Committing restore...
Lock file has not changed. Skipping lock file write. Path: D:\home\site\repository\project.lock.json
D:\home\site\repository\project.json
Restore completed in 6155ms.

NuGet Config files used:
    C:\DWASFiles\Sites\#1jssviewmodel\AppData\NuGet\NuGet.Config

Feeds used:
    https://api.nuget.org/v3/index.json
Publishing repository for .NETCoreApp,Version=v1.0
<EMAIL_ADDRESS>D:\home\site\repository
npm WARN optional Skipping failed optional dependency /webpack/watchpack/chokidar/fsevents:
+--<EMAIL_ADDRESS>npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>| `--<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No repository field.
|   +--<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>No license field.
|   | `--<EMAIL_ADDRESS>|   |   `--<EMAIL_ADDRESS>|   |     +--<EMAIL_ADDRESS>|   |     | +--<EMAIL_ADDRESS>|   |     | | +--<EMAIL_ADDRESS>|   |     | | +--<EMAIL_ADDRESS>|   |     | | +--<EMAIL_ADDRESS>|   |     | | +--<EMAIL_ADDRESS>|   |     | | `--<EMAIL_ADDRESS>|   |     | +--<EMAIL_ADDRESS>|   |     | `--<EMAIL_ADDRESS>|   |     +--<EMAIL_ADDRESS>|   |     | `--<EMAIL_ADDRESS>|   |     `--<EMAIL_ADDRESS>|   |       `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>|     `--<EMAIL_ADDRESS>|       `--<EMAIL_ADDRESS>|         `--<EMAIL_ADDRESS>|           `--<EMAIL_ADDRESS>|             `--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>    +--<EMAIL_ADDRESS>    | `--<EMAIL_ADDRESS>    |   +--<EMAIL_ADDRESS>    |   | `--<EMAIL_ADDRESS>    |   `--<EMAIL_ADDRESS>    `--<EMAIL_ADDRESS>      `--<EMAIL_ADDRESS>Hash: e61cc3dc474d9ac688fa
Version: webpack 1.13.3
Time: 27030ms
    Asset    Size  Chunks             Chunk Names
vendor.js  437 kB       0  [emitted]  vendor
   [0] dll vendor 12 bytes {0} [built] [1 error]
    + 285 hidden modules
ERROR in Cannot find module 'caniuse-db/features-json/transforms2d.json'
 @ dll vendor
Hash: 7152126a5b6cfc6a8d0d4870620e3462c6bfa961
Version: webpack 1.13.3
Child
    Hash: 7152126a5b6cfc6a8d0d
    Version: webpack 1.13.3
    Time: 314ms
        + 1 hidden modules

    ERROR in Cannot find module 'core-js/library/fn/symbol/iterator'
Child
    Hash: 4870620e3462c6bfa961
    Version: webpack 1.13.3
    Time: 299ms
        + 1 hidden modules

    ERROR in Cannot find module 'core-js/library/fn/symbol/iterator'
Project repository (.NETCoreApp,Version=v1.0) was previously compiled. Skipping compilation.
Configuring the following project for use with IIS: 'D:\local\Temp\8d415675f51018c'
Updating web.config at 'D:\local\Temp\8d415675f51018c\web.config'
Configuring project completed successfully
publish: Published to D:\local\Temp\8d415675f51018c
Published 1/1 projects successfully
KuduSync.NET from: 'D:\local\Temp\8d415675f51018c' to: 'D:\home\site\wwwroot'
Copying file: 'repository.deps.json'
Copying file: 'repository.runtimeconfig.json'
Copying file: 'node_modules\.bin\loose-envify'
Copying file: 'node_modules\.bin\loose-envify.cmd'
Copying file: 'node_modules\ansi-regex\index.js'
Copying file: 'node_modules\ansi-regex\license'
Copying file: 'node_modules\ansi-regex\package.json'
Copying file: 'node_modules\ansi-regex\readme.md'
Copying file: 'node_modules\ansi-styles\index.js'
Copying file: 'node_modules\ansi-styles\license'
Copying file: 'node_modules\ansi-styles\package.json'
Copying file: 'node_modules\ansi-styles\readme.md'
Copying file: 'node_modules\asap\asap.js'
Copying file: 'node_modules\asap\browser-asap.js'
Copying file: 'node_modules\asap\browser-raw.js'
Copying file: 'node_modules\asap\CHANGES.md'
Copying file: 'node_modules\asap\LICENSE.md'
Copying file: 'node_modules\asap\package.json'
Copying file: 'node_modules\asap\raw.js'
Copying file: 'node_modules\asap\README.md'
Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.
Copying file: 'node_modules\babel-preset-es2015\node_modules\babel-plugin-transform-es2015-computed-properties\node_modules\babel-helper-define-map\node_modules\babel-helper-function-name\node_modules\babel-helper-get-function-arity\package.json'
Failed exitCode=1, command="kudusync" -v 50 -f "D:\local\Temp\8d415675f51018c" -t "D:\home\site\wwwroot" -n "D:\home\site\deployments\7d6a896e5d4affe6efc616b19b684b16ca392f1b\manifest" -p "D:\Program Files (x86)\SiteExtensions\Kudu\59.51122.2559\bin\Scripts\firstDeploymentManifest" -i ".git;.hg;.deployment;deploy.cmd"
An error has occurred during web site deployment.
npm WARN optional Skipping failed optional dependency /webpack/watchpack/chokidar/fsevents:\r\nnpm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>WARN<EMAIL_ADDRESS>No repository field.\r\nnpm WARN<EMAIL_ADDRESS>No license field.\r\nError: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.\r\nD:\Program Files (x86)\SiteExtensions\Kudu\59.51122.2559\bin\Scripts\starter.cmd "D:\home\site\deployments\tools\deploy.cmd"

I'm afraid I don't know why you'd still be getting the path-too-long issue if it's now actually using NPM v3.x during deployment.
One bit of good news is that pretty soon, issues like this will no longer be a concern. The templates are changing so that you will no longer need to deploy package.json or node_modules to production at all. The server-side prerendering feature will be able to run from completely self-contained bundles that never invoke require at runtime. So, deployments will be much faster, and won't involve NPM at all.
I know that doesn't fix your immediate issue right now (since the new feature hasn't shipped yet). If you're able to repro the deployment issue in a simpler way (e.g., try just deploying a completely empty site that has nothing except your package.json, and see if Kudu still fails to restore the dependencies), then you might want to report that to the Azure/Kudu teams.

That's the whole log. I there another way to specify the node version? (in
the project maybe)
On Nov 25, 2016 4:23 PM, "Steve Sanderson"<EMAIL_ADDRESS>wrote:

I'm afraid I don't know why you'd still be getting the path-too-long issue
if it's now actually using NPM v3.x during deployment.
One bit of good news is that pretty soon, issues like this will no longer
be a concern. The templates are changing so that you will no longer need to
deploy package.json or node_modules to production at all. The server-side
prerendering feature will be able to run from completely self-contained
bundles that never invoke require at runtime. So, deployments will be
much faster, and won't involve NPM at all.
I know that doesn't fix your immediate issue right now (since the new
feature hasn't shipped yet). If you're able to repro the deployment issue
in a simpler way (e.g., try just deploying a completely empty site that has
nothing except your package.json, and see if Kudu still fails to restore
the dependencies), then you might want to report that to the Azure/Kudu
teams.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/JavaScriptServices/issues/456#issuecomment-263031857,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AED31opHTTkRkCWugFf-wthVBGYFiW2Dks5rB23qgaJpZM4K50tT
.

Can't wait for it. What's the time frame we're talking about here? If it's a few weeks then I'll probably just wait.
About my issue, it's definitely using a new node/npm (confirmed via Azure's command line):
  "engines": {
    "node": "7.1.0",
    "npm": "3.10.9"
  },

But I'm still getting these two errors:
ERROR in ./ClientApp/boot-client.js
Module build failed: Error: Couldn't find preset "es2015" relative to directory "D:\\home\\site\\repository"

and further down:
Error: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

Are either of these due to JS Services configuration? If not, how can I contact the Azure or Kudu people?
Thanks for all the help.

Interesting, the babel-preset-es2015 folder is empty:

Maybe it's a problem with the es2015 preset version. I'll keep looking.

I'm very sorry for the trouble. As it turns out updating the node version in Azure still leaves all the deeply nested files in node_modules. It works correctly if you use a new app service and create the global.json file + set the node version from the get go. In my case I didn't know how to reset it so I had to delete the app and create it again.
Thank you for your patience.

Oh great so, just for clarity if anyone else runs into it:

Deleted the app from Azure.
Set the Azure Node version to 7 (since we require npm3+)
Added the global.json file to pinpoint the version of .NET Core we need (1.0.1 at the moment)
Git push the app back onto Azure

Glad you got it working!

@MarkPieszak:

Is this a new upcoming feature to azure you're talking about, or to .NET Core and somehow caching node modules you want?

It's just a change to the default Webpack config that prepares a completely standalone server-side prerendering bundle (like how the client-side bundle is completely self-contained). This means that at runtime, it never calls Node's require to load anything from node_modules, so you don't even have to deploy that dir to production.

I love it, that's a great idea. Yeah it seems to be a reoccurring issue :)

That feature is published now (get the latest generator-aspnetcore-spa version 0.6.1 to see it - notice that dotnet publish won't emit a node_modules dir any more, yet it still works). Let me know if you can think of any issues with this!

Will do, thanks again Steve!


remove non-metabolic genes from Fructose and mannose metabolism

Description of the issue:

Four non-metabolic genes are discovered in the GPR rules of Fructose and mannose metabolism:

gene
Reasons
Subsystems
RxnIDs

ENSG00000108813
inconsistent function annotation with reaction
Fructose and mannose metabolism
MAR04706

ENSG00000144591
annotated as a regulatory subunit and allow allosteric feedback inhibition of GMPPB by GDP-mannose
Fructose and mannose metabolism
MAR04386;MAR04387

ENSG00000167363
involved in protein deglycation by mediating phosphorylation of fructoselysine residues on glycated proteins, instead of fructose and mannose metabolism
Fructose and mannose metabolism;Isolated;Pyrimidine metabolism
MAR04317;MAR04318;MAR04320;MAR04182;MAR09466;MAR09467

ENSG00000176020
may mediate heterophilic cell-cell interaction, and contribute to signal transduction
Fructose and mannose metabolism
MAR04386;MAR04387

Current feature/value/output:

The association of these genes is lack of evidence according to the provided reasons

Expected feature/value/output:

Remove above genes from Human-GEM

I hereby confirm that I have:

[X] Done this analysis in the main branch of the repository
[X] Checked that a similar issue does not exist already

The gene product of ENSG00000167363 is known to catalyze protein deglycation by mediating phosphorylation of fructoselysine residues on glycated proteins, to generate fructoselysine-3 phosphate. Even though it is not involved in Fructose and mannose metabolism, but should be retained in the model.


##[error]git : Switched to a new branch 'master'

Agent Version and Platform
Agent Version: 2.146.0
Platform: Windows Server 2019
Azure DevOps Type and Version
Azure DevOps Type:
dev.azure.com
Organization name:
https://dev.azure.com/CarbonDevOps
What's not working?

@wangfeng19890 makes share you have Fail on standard error unchecked, since git.exe print out status update to standard error.

@TingluoHuang After I make it checked, I got detailed log and it is attached.
It looks like a powershell error.
log_5_209.zip

@wangfeng19890 makes sure you have Fail on standard error unchecked

@TingluoHuang Yes, unchecked. But same error.

can you share the log?

log_5_209.zip
This is the log.

that's the log for build 209, where is log for 210?

Sorry.
log_5_210.zip

@wangfeng19890 did you provide credential when executing git pull?
i think git checkout master succeed but git pull failed.

you mean this one?

@TingluoHuang I have the same agent installed on my PC, it is running correctly. But when I switch it to the agent installed on server, the error happens.

Which agent pool you are using that have this problem?

I create a pool and it is called CarbonAgentPool

what's the version of powershell you have?

On the server, the version is:

The version on VS2017 hosted pool is 5.1.14393.2636 and i can't repro your issue with it.
2019-02-15T13:48:29.3142524Z Name             : ConsoleHost
2019-02-15T13:48:29.3143190Z Version          : 5.1.14393.2636
2019-02-15T13:48:29.3144015Z InstanceId       : 8f9940cc-4bf5-4c5f-b2a1-1afbf0eec39e
2019-02-15T13:48:29.3144591Z UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
2019-02-15T13:48:29.3145371Z CurrentCulture   : en-US
2019-02-15T13:48:29.3146719Z CurrentUICulture : en-US
2019-02-15T13:48:29.3147357Z PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
2019-02-15T13:48:29.3148512Z DebuggerEnabled  : True
2019-02-15T13:48:29.3148624Z IsRunspacePushed : False
2019-02-15T13:48:29.3148687Z Runspace         : System.Management.Automation.Runspaces.LocalRunspace

@TingluoHuang Yes, I installed the same agent on my laptop and it is working well without this issue.
But it is not working on Server side, so I hope we can find out the root cause and fix it.
Could you please help me? I have reinstalled the agent on server but no luck.

@wangfeng19890 i don't think your issue is caused by the agent, might be something about powershell or environment.
the command that agent runs:
"C:\windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'C:\GeneratedScript.ps1'"

The generate script looks like:
$ErrorActionPreference = 'stop'
$host
git checkout master
git pull
if (!(Test-Path -LiteralPath variable:\LASTEXITCODE)) {
    Write-Host '##vso[task.debug]$LASTEXITCODE is not set.'
} else {
    Write-Host ('##vso[task.debug]$LASTEXITCODE: {0}' -f $LASTEXITCODE)
    exit $LASTEXITCODE
}

Can you try create the generated file yourself on the the build server that has the problem, and run powershell command line directly see whether powershell can return cleanly?


Fields which are dropdowns in esp cant be edited

Describe wanted Enhancement !
I'd like to have to have ESPhome drop downs, like pulse, being editable (as drop down?) and pushed to device.
Why should we put effort in it ?
Yo can not change them in iobroker. The are shown correctly, but editing them will not result in a chage.
Additional context
yaml example:
light:
  # ... and then make a light out of it.
  - platform: monochromatic
    name: "${device_name} Green LED"
    output: s26_green_led
    effects:
    - pulse:
    - pulse:
        name: "Fast Pulse"
        transition_length: 0.5s
        update_interval: 0.5s
    - pulse:
          name: "Slow Pulse"
          # transition_length: 1s      # defaults to 1s
          update_interval: 2s

object definition of generated state in iob
{
  "type": "state",
  "common": {
    "modify": "",
    "name": "effect of wohnzimmer-tv Green LED",
    "type": "string",
    "role": "state",
    "read": true,
    "unit": "",
    "write": true
  },
  "from": "system.adapter.esphome.0",
  "user": "system.user.admin",
  "ts":<PHONE_NUMBER>716,
  "_id": "esphome.0.4855194680A1.Light.3747644526.effect",
  "acl": {
    "object": 1636,
    "state": 1636,
    "owner": "system.user.admin",
    "ownerGroup": "system.group.administrator"
  }
}

the effectList inside the config shows "["None","Pulse","Fast Pulse","Slow Pulse"]" as value

@volkerrichert can you please check if an fix similar to https://github.com/DrozmotiX/ioBroker.esphome/issues/169 would be helpful ?

@DutchmanNL I'll check the new release. I already read that PR.

Ok, dropdowns can now be changed. You have to write the text into the state. That's solves this issue. Using a drop down in ioBroker would be nice, but that's another story.
THX

owns can now be changed. You have to write the text into the state. That's solves this issue. Using a drop down in ioBroker would be nice, but that's another story.

we did implement also drop-down, see: https://github.com/DrozmotiX/ioBroker.esphome/issues/169
you should be able to do that by adding options, like mentioned in that issue:
    options:
      0: Manual
      1: Schedule
      2: Holiday -> only for Koenighaus


rustify context_switch

Thank you!

Published as 0.3.9

Oh, I just found an issue with this PR. The problem is the .spin: jmp spin part: Inline Assembly has no special support for . labels, so .spin is just a global label with the name .spin. But jmp spin jumps to the completely different spin label, which is defined somewhere in the assembly code. I created a fix at https://github.com/rust-osdev/bootloader/pull/40. Sorry that I didn't see it in my first review.


Running the init command with changes to config file doesn’t seem to actually change the conf file

Running the init command with changes to config file doesn’t seem to actually change the conf file

I have been unable to replicate this bug, @zanbel any input you can provide here?

Sure. Here are the steps to try and reproduce:

make sure you don't already have an ~/.ecctl directory
download the relevant artifact from the release page
extract and run the ./ecctl init command
complete the initial set up

Issue: although the initial setup appears to complete successfully the directory is not created and config file is not created or saved as expected.

That issue was fixed in https://github.com/elastic/ecctl/pull/51, which was a bug that was easily reproducible, however the description of this PR does not match what I'm seeing. When there's a config file already created and init is called, and the properties change. the file is actually saved if the credentials are valid, which makes me think the described bug is non-existent.

I didn't experience the scenario you are describing so hard for me to comment. If it's not reproducible let's close the issue.

Closing as unable to reproduce


feat[next]: DaCe support for temporaries

Description
Lift operators are removed by an ITIR transformation by introducing temporaries. Temporaries are implemented in DaCe backend as transient arrays. This PR adds extraction of temporaries and generation of corresponding transient arrays in the SDFG representation.

@tehrengruber Thank you for the review comments. At last week's DaCe workshop, we were informed that array offsets will be deprecated in DaCe. The reason is that offsets are difficult to translate across nested-SDFG boundaries, and therefore very error prone during SDFG transformation. The SDFG generated by this PR works, but It's not guarantee to still work in the future. In DaCe front-ends, in order to avoid offsets, they are running a pass to normalize all array access to be 0-based. We could discuss how to do it in ITIR as well.

I would like to merge this PR, in order to stop overriding lift_mode in gt4py unit tests, which is misleading. The support for temporaries will be extended once the improvement on the temporary pass is merged. This extension includes, for example, a generic ITIR pass to sanitize unicode symbols, if we still see the need for it. Another extension could be the normalization of field domain in order to avoid array offsets, if we see that DaCe cannot handle it in SDFG transformations.


feat(WPApi):Added Wordpress Api

Functionality:
Added Wordpress API for Blogs
Solution:
Added Wordpress API for Blogs
Risk level:

[ ] high
[x] medium
[ ] low

Please resolve merge conflict


HBASE-28672 Ensure large batches are not indefinitely blocked by quotas

https://issues.apache.org/jira/browse/HBASE-28672
At my day job we are trying to implement default quotas for a variety of access patterns. We began by introducing a default read IO limit per-user, per-machine — this has been very successful in reducing hotspots, even on clusters with thousands of distinct users.
While implementing a default writes/second throttle, I realized that doing so would put us in a precarious situation where large enough batches may never succeed. If your batch size is greater than your TimeLimiter's max throughput, then you will always fail in the quota estimation stage; this will stick the client in a backoff-and-retry loop until it times out. Meanwhile IO estimates are more optimistic, deliberately, which can let large requests do targeted oversubscription of an IO quota:
// assume 1 block required for reads. this is probably a low estimate, which is okay
readConsumed = numReads > 0 ? blockSizeBytes : 0;

This is okay because the Limiter's availability will go negative and force a longer backoff on subsequent requests. I believe this is preferable UX compared to a doomed throttling loop.
In this PR I introduce batch estimation that takes the limiter's max throughput into account, and I've added unit tests to validate the intended behavior.
@ndimiduk @hgromer @bozzkar

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.

That's a good question. Despite the existing behavior, I think the intention was always for this to be more of a soft limit — the TimedQuota proto actually calls the field soft_limit:
message TimedQuota {
  required TimeUnit time_unit = 1;
  optional uint64 soft_limit  = 2;
  optional float share = 3;
  optional QuotaScope scope  = 4 [default = MACHINE];
}

That said, intention is one thing and reality is another. I could also see people missing the hard limits if that's how they're using quotas.
I'd probably prefer to make the addition of a hard limit a separate effort, though, because my guess is that it will actually be quite a bit of work relative to its value. For example, coming up with good enough estimations of IO-heavy request load to earnestly guarantee any sort of "hard limit" is going to be tricky/impossible

Ideally for a multi request it would be able to execute whatever actions fit within the available quota. This maintains the hard limit but also gives a user more likelihood to eventually finish their request. Similar to the handle of MultiActionResultTooLarge.

I agree with you, and considered the MARTL approach internally but didn't do a good job of documenting this publicly.
My pushback is not that we shouldn't add support for some sort of MultiActionBatchTooLarge exception, but rather that it would be a pretty significant lift and is, imo, not necessarily in the scope of this issue. It's always been possible to oversubscribe IO quotas, and this is advertised as a soft limit. Despite it being a soft limit, there's a bug here which throws certain request shapes into indefinite backoff/retry loops.
It's definitely righteous work to also think about improving the server's respect of the limit via request chunking, but I think that's sort of its own task and, given the difference in changeset required, I don't think a lack of MABTL exceptions should block our fixing of this bug

Would we have the same problem with write size?

Oh yeah, good point. I bet we would. I can look into a fix there too

Actually, there's no realistic problem we write size. At least, no more than read size. Both make very naive lowball estimates based on the number of reads/writes: https://github.com/apache/hbase/blob/1ffa127be8abf2b4ab0be1a6ebb148a539e7a73f/hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/DefaultOperationQuota.java#L191-L203
It's theoretically possible for the estimate to exceed the max IO allowed though, so maybe it's worth putting limits in place for both the read and write size estimates here? What do you guys think?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 25s
Docker mode activated.

I pushed an addition which ensures we don't block requests indefinitely for read, write, or request size estimates

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 44s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 24s

master passed

+1 :green_heart:
compile
3m 13s

master passed

+1 :green_heart:
checkstyle
0m 42s

master passed

+1 :green_heart:
spotbugs
1m 55s

master passed

+1 :green_heart:
spotless
1m  0s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 40s

the patch passed

+1 :green_heart:
compile
3m 28s

the patch passed

+1 :green_heart:
javac
3m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 43s

the patch passed

+1 :green_heart:
spotbugs
1m 52s

the patch passed

+1 :green_heart:
hadoopcheck
6m  2s

Patch does not cause any errors with Hadoop 3.3.6.

+1 :green_heart:
spotless
0m 58s

patch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 42s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
javadoc
0m 22s

the patch passed

+1 :green_heart:
shadedjars
5m 32s

patch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m 27s

the patch passed

+1 :green_heart:
compile
1m  9s

the patch passed

+1 :green_heart:
javac
1m  9s

the patch passed

+1 :green_heart:
javadoc
0m 33s

the patch passed

+1 :green_heart:
shadedjars
6m 34s

patch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 26s

the patch passed

+1 :green_heart:
compile
0m 40s

the patch passed

+1 :green_heart:
javac
0m 40s

the patch passed

+1 :green_heart:
javadoc
0m 23s

the patch passed

+1 :green_heart:
shadedjars
5m 43s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
238m 10s
/patch-unit-hbase-server.txt
hbase-server in the patch failed.

262m 36s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6003/3/artifact/yetus-jdk8-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6003

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux eb7daa586d3f 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / c5cccfc5dae5b1d7c4737a8f723530baf9f49509

Default Java
Temurin-1.8.0_352-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6003/3/testReport/

Max. process+thread count
5283 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6003/3/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 35s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 53s

master passed

+1 :green_heart:
compile
3m 37s

master passed

+1 :green_heart:
checkstyle
0m 51s

master passed

+1 :green_heart:
spotbugs
1m 51s

master passed

+1 :green_heart:
spotless
0m 53s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 51s

the patch passed

+1 :green_heart:
compile
2m 56s

the patch passed

+1 :green_heart:
javac
2m 56s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 34s

the patch passed

+1 :green_heart:
spotbugs
1m 37s

the patch passed

+1 :green_heart:
hadoopcheck
5m 14s

Patch does not cause any errors with Hadoop 3.3.6.

+1 :green_heart:
spotless
0m 40s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m  9s

The patch does not generate ASF License warnings.

32m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6003/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6003

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 54b12a07b010 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 15b58667defe17d1ade6f177079da01d19b7e82b

Default Java
Eclipse Adoptium-17.0.10+7

Max. process+thread count
87 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6003/4/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


added new Go logo

Replace old mascot Go label with brand new Go Label
Please check this issue : https://github.com/prasmussen/glot-www/issues/32

Thanks, this closes #32


How do you npm install?

sorry i typed npm install into the command prompt and i could not install the dependencies

just had to install node js and cd into the rmse directory


Update index-gallery.md

specified the in PFX/PEM format for the certs. CER will not work. just making it more clear.

Docs Build status updates of commit b25918c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

gallery-sdk/generated/index-gallery.md
:warning:Warning
View
Details

gallery-sdk/generated/index-gallery.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 57: [Warning] Markdown content is not allowed before H1.
Line 504: [Warning] Link 'https://azure.microsoft.com/en-us/services/search/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 149: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 580: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 707: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 759: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 809: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 842: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 918: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 968: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.
Line 979: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 04/01/2020.

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

used https://msazure.visualstudio.com/One/_git/AzureUX-PortalFx?path=%2Fdocs


Fix error handling of wrapped errors

This PR fixes error handling for wrapped errors.
This bug was caused by wrong parameter order in the usage of errors.Is
The added test case shows a use case.
@richzw This changes the behaviour of the middleware: Now - errors which may deeply wrap other errors could match in the middleware where they previously didn't. I think this change fixes a bug but maybe you want the behaviour do not change? LMK.

Thx for the feedback. I think it is useful to move the error matching into it's own function which allowed for far simpler unit testing.
After I applied you change, which I don't yet fully get, I wanted to test if we even need two comparisons. Have a look at the changes and tell me what you think. I think only one comparison is actually needed.
Tests are green.


Fix pod install problem

I can’t run pod install with some error when i link this library and i’ve fixed it in this pull request.

Thank you Long :-d


[CARBONDATA-2189] Add DataMapProvider developer interface

This PR is based on #1510
Add developer interface for 2 types of DataMap:

IndexDataMap: DataMap leveraging index to accelerate filter query
MVDataMap: DataMap leveraging Materialized View to accelerate olap style query, like SPJG query (select, predicate, join, groupby)

This PR adds support for ADD/DROP operation of DataMap

[X] Any interfaces changed?
New developer interface added
[X] Any backward compatibility impacted?
No
[X] Document update required?
Yes
[X] Testing done
Yes
[X] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
NA

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3781/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2536/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3784/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2539/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3567/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3570/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2542/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3787/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2543/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3788/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2544/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2545/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3789/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3573/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3574/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3575/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3576/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3810/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2566/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2568/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3812/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3600/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3602/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3818/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2575/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3822/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2578/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3609/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3824/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2580/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3611/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3826/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2582/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3613/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3615/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2584/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3828/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3616/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2590/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3838/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2593/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3621/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3623/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2606/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/3851/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/3634/

LGTM


Cloud Shell version conflict

Cloud Shell in the GCP org that I used for testing has TF v1.0 (at the time of writing this issue), whereas the multi-mig-http-lb example has the version constraint:
required_version = "~> 0.13.0"

So when I ran terraform init from Cloud Shell, an “unsupported TF version” error occurred, as expected.
Users who use TF v0.13 (say, from their local host) won’t run into this error. But because the README displays the Cloud Shell button prominently, users might be tempted to try that method.
I was able to work around the error by changing the constraint to:
required_version = “>= 0.13.0”
But after changing the version constraint, I ran into a minor issue with the following command in the README:
echo http://$(terraform output load-balancer-ip)

This command returns: http://“<address>” … i.e., the output value is enclosed in double quotes (which appears to be a breaking change since TF v0.14), making the URL unusable. This is a minor issue, but I wanted to report it for completeness.
Suggested fix: Change the version constraint to >= 0.13.0 and update the echo http://$(terraform output load-balancer-ip) step to strip out any double quotes.

For root modules, the general recommendation and best practice is to pin to a specific major version. Examples should follow this best practice, so I'm not comfortable with updating this to >= 0.13.0. We can upgrade it to ~> 1.0.0 though.

@kumar-dhanagopal is this still an issue?


Why does TLBIMP not mark event accessors it generates (add_X, remove_X) with the IL specialname flag?

The .NET Framework ships with the TLBIMP command-line tool (".NET Framework Type Library to Assembly Converter"), so hopefully asking a question about this tool here isn't off-topic. Otherwise, kindly direct me at the right place to ask.
Say I have a type library matching these IDL definitions:
[uuid(…)]
library X
{
    importlib("stdole32.tlb");

    [uuid(…)]
    interface IFoo : IUnknown
    {
    }

    [uuid(…)]
    interface IFooEvents : IUnknown
    {
        HRESULT SomeEvent();
    }

    [uuid(…)]
    coclass Foo
    {
        [default] interface IFoo;
        [default, source] interface IFooEvents;
    }
}

When invoking TLBIMP on that type library, it will auto-generate (among other things) an event interface IFooEvents_Event. Inspecting this with e.g. ILDASM, I'm seeing that the SomeEvent's event accessor methods add_SomeEvent and remove_SomeEvent are not marked with the specialname IL flag (as is normally the case with ctors, property & event accessors):
.method public hidebysig newslot abstract virtual
        instance void  add_SomeEvent(class IFooEvents_SomeEventEventHandler A_1) runtime managed internalcall
{
}

Was this simply an oversight when the tool was originally implemented, or are there specific reasons why these event accessor methods aren't marked with specialname?

I'm assuming that the almost year-long silence means that Microsoft has no interest in doing anything about this. Closing.


contrib: Add default value for missing {{target}} option

Most of the contrib recipes use the target option but do not come with a default value.
Therefore using those recipes will lead to an exception.
This PR adds the target option to all recipes and sets the hostname as default.

[x] Bug fix #2238
[x] Changelog updated

This is not the way)) Did it myself. Actual way is much simpler: c747a5945bcf678bf2a2143e9eef67f74a733d46