Installer does not support nativeSystemd

Bug description
nativeSystemd doesn't seem to work yet.
To Reproduce
Steps to reproduce the behavior:
Specify wsl.nativeSystemd = true; in configuration.nix, build nixos-wsl-installer.tar.gz, import and run it.
Expected behavior
The installer script should start.
Logs
PS C:\Users\terrorjack\Downloads> wsl -d NixOS
Catastrophic failure
Error code: Wsl/Service/CreateInstance/E_UNEXPECTED

PS C:\Users\terrorjack\Downloads> wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.47
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.900

Can you reproduce this when changing in on an already installed system?

When wsl.nativeSystemd = false or the line removed, the first launch is stuck infinitely after 14.34 MiB freed by hard-linking 6765 files and didn't even make it to Starting systemd.... This is the tarball built with main branch and nixos-unstable, I'll try other configurations later.

the first launch is stuck infinitely after 14.34 MiB freed by hard-linking 6765 files and didn't even make it to Starting systemd....

Does it start after your restart wsl?

After restarting it's stuck after:
setting up /etc...
setting up /bin...

First installation seems to work after switching to nixos-22.11 :)

Switching to wsl.nativeSystemd = true after installation also seems to work. Feel free to close this ticket and thanks a lot for your awesome work! It would be nice to check invalid fields at installer build-time though.

I also have the same issue on first boot. Didn't changed Anything. Just run the import and it's broken
<3>WSL (8) ERROR: CreateProcessEntryCommon:559: chdir(/root) failed 2
Unpacking root file system...
 307MiB 0:00:08 [34.9MiB/s] [========================================================================>] 100%
Activating nix configuration...
Copying /usr/share/applications
Copying /usr/share/icons
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
setting up /etc...
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = (unset),
        LC_ALL = (unset),
        LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
setting up /bin...
Cleaning up installer files...
finding garbage collector roots...
removing stale link from '/nix/var/nix/gcroots/auto/6yfbrv8wfkyl40wq6827lamr9m29z7wg' to '/build/nix/var/nix/profiles/per-user/root/channels-1-link'
removing stale link from '/nix/var/nix/gcroots/auto/zxi8v969la5n36bg7gs016wgcif4qjhp' to '/build/nix/var/nix/profiles/system-1-link'
deleting garbage...
deleting '/nix/store/5mism3qrfc3ah9ahvf7sczxy4bax9cgq-pv-1.6.20'
deleting '/nix/store/0p9v7yvblgxsds9pbsrir3af6gw0x77s-busybox-1.35.0'
deleting '/nix/store/cq6l0b0iv2y3gln3xi6nzxs57mz5rxws-tarball'
deleting '/nix/store/ab5mixyq1zg0x5lnr5i7m4l5815fp1h8-wsl-prepare'
deleting '/nix/store/scr6balqjknqpgm7igd0b4pagmp2ldbl-installer.sh'
deleting '/nix/store/pmb55f6rk98cdycqf589vb3xpbg15k28-source'
deleting unused links...
note: currently hard linking saves -0.00 MiB
6 store paths deleted, 309.05 MiB freed
Optimizing store...
5.74 MiB freed by hard-linking 3714 files
Starting systemd...

Imported directly the other file like described in https://github.com/nix-community/NixOS-WSL/pull/143 and it works lol

@shyim Your problem wasn't related to native systemd, but another known bug with the container-based implementation, that should be fixed with the next release. See also #156

Schwerwiegender Fehler

translation: critical error

Possibly. What does wsl --version output?

@nzbr

➜  wsl --version
WSL-Version: <IP_ADDRESS>
Kernelversion: <IP_ADDRESS>
WSLg-Version: 1.0.48
MSRDC-Version: 1.2.3770
Direct3D-Version: 1.608.2-61064218
DXCore-Version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows Version: 10.0.19045.2486

@K900 is this the version that's affected by #199?

Yes.

So I seem to be getting the same problem after building the tarball from the master branch on the following wsl version:
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.49
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22000.1696

@shadowrylander did you modify configuration.nix? If yes, what changes did you make?

No changes other than adding nativeSystemd = true;.

Yeah, that's the problem: The installer does not support nativeSystemd yet. You'll need to disable it, install and then re-enable it

I enabled it and rebuilt it the first time, but /sbin/init apparently linked to a wsl shim or something like that? Is it not supposed to be pointing to systemctl or similar?

Normally, it's linked to systemd, but NixOS needs to execute the activation scripts first. So we have the shim that does all the setup tasks and then execs systemd

Fixed in 23.05.


Zack pnpm and segment build and test

Looks like an issue with pnpm's symlinking and the dts() rollup plugin: https://github.com/Swatinem/rollup-plugin-dts/issues/143

fixed the vue issue, but svelte still having some issues here, will have to look up TS error: TS4058 and come back with some fresh eyes

pnpm has been implemented now and working with nx


New title and menu bar glitch on minimize and maximize buttons

VSCode Version: 1.28.1
OS Version: Windows 10 Pro (version 1709)
OS Build: 16299.665

Additional Info:

Version: 1.28.1 (system setup)
Commit: 3368db6750222d319c851f6d90eb619d886e08f5
Date: 2018-10-11T18:13:53.910Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

Steps to Reproduce:

Open VS Code
Hover on either minimize or maximize button

Does this issue occur when all extensions are disabled?: Yes
Screenshots:
Color theme: Dark (Visual Studio)
Window Active State

Hover on minimize button

Hover on maximize button

Color theme: Light (Visual Studio)
Window Active State

Hover on minimize button

Hover on maximize button

I believe this is a duplicate of #60430


Elfeed parsing description seems to fail

Hi,
I recently came across some feeds whose content elfeed seems to be unable to parse,
and I've made a small sample "feed" to reproduce the error, publicly accessible at https://pastebin.com/raw/Ts1uVwJt .
When I add  and update this feed, it does list the item "test item", but the description is empty, both in the ui and upon inspecting it by running (elfeed-deref (elfeed-entry-content (with-elfeed-db-visit (entry feed) (when (equal "test item" (elfeed-entry-title entry)) (elfeed-db-return entry))))) it seems like the item's content is parsed as an empty string.
I'm guessing this is because the html in the description was not properly xmlencoded - is this a failure on the part of the feeds formatted in such a manner, or a bug in elfeed?
Thanks in advance,
pinoaffe

Never mind, I'm fairly certain this is a fault on the part of the RSS feed, and I've written a small parse hook to dejumblify the feeds

Never mind, I'm fairly certain this is a fault on the part of the RSS feed, and I've written a small parse hook to dejumblify the feeds


feat(hero): support isLoading prop

Summary

Add isLoading prop to Hero

Change List (commits, features, bugs, etc)

fix(TableSkeletonHeaders): assume 10 rowcount if not passed

Acceptance Test (how to verify the PR)

Check out new isLoading story for Hero

:tada: This PR is included in version 1.76.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.9 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.76.0 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


Option to change Reading Font

There is an option to change Editor Font, but not Reading Font. I would like to use a preferentially better font. Was this deliberate? If so, why?

You can already do this in Obsidian Appearance menu


Table Component: add Striped Mono variant

https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?type=design&node-id=13296-61817&mode=design&t=IrOKEs6RNrRPXgLH-0

Assigning to Loïc because he's already done it in a project.


Modify CVE Scan Schedule

Support Question
@yinan-symphony can you help make a modification to the CVE Scan GitHub Action so that GitHub will recognise you as the scan owner? I am still getting failure notifications because I was the last editor of that file. Strange way that GitHub implements notification owners.
https://github.com/finos/symphony-wdk/blob/master/.github/workflows/cve-scanning-gradle.yml#L5
https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/notifications-for-workflow-runs

Notifications for scheduled workflows are sent to the user who initially created the workflow. If a different user updates the cron syntax in the workflow file, subsequent notifications will be sent to that user instead. If a scheduled workflow is disabled and then re-enabled, notifications will be sent to the user who re-enabled the workflow rather than the user who last modified the cron syntax.

@ystxn yes, i will update it.


RUMM 2180 Add eslint rules

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
Bring the project closer to other datadog projects by adding some of the eslint rules in use
Additional Notes
Please review https://github.com/DataDog/dd-sdk-reactnative/pull/177 first

be careful with the conversion of double equality into triple equality

Review checklist (to be filled by reviewers)

[x] Feature or bugfix MUST have appropriate tests
[x] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[x] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
[x] If this PR is auto-generated, please make sure also to manually update the code related to the change

@louiszawadzki Let's maybe target branch of #177 to reduce the final diff and simplify the review? Once #177 is merged target here will be updated.


Flutter test: How to check the background color of a widget during integration test

I have a simple flutter app available on github having both Light and dark themes with a "Theme switch" button. On the home page, I have a Scaffold widget that takes it's background color property from the theme. Is there a way to check the background color of the Scaffold before and after switching themes during integration test with driver ?
full integration test here
My goal is getting the background color of the Scaffold before and after switching themes with driver
I tried checking the active theme, but fails:
    final themeButton = find.byValueKey('Button');
    final themeProvider = ThemeProvider();

    test('Switch between light and dark themes', () async {
      expect(themeProvider.mode, ThemeMode.light); //check initial theme
      await driver.tap(themeButton);
      expect(themeProvider.mode, ThemeMode.dark);  //check new theme
    });
  });```

Hi @Joshuaerinosho
You can test color, found this
  testWidgets('Test Scaffold color', (WidgetTester tester) async {
    await tester.pumpWidget(MyApp());

    expect(
        (tester.firstWidget(find.byType(Scaffold)) as Scaffold).backgroundColor,
        Colors.black);
  });

Just tried, it works, you can switch Scaffold or any Widget
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you

Hi @TahaTesser I tried doing that already. But it fails when I try changing the background color.
here's a snippet:
  testWidgets('Backgraound Color Test', (WidgetTester tester) async {
    final switchButton = find.byType(RoundButton);
    // Build app and trigger a frame.
    await tester.pumpWidget(MyApp());

    // Verify initial background color
    expect(
        (tester.firstWidget(find.byType(Scaffold)) as Scaffold).backgroundColor,
        Colors.white);

    // taps theme switch button
    await tester.tap(switchButton);
    await tester.pump(Duration(seconds: 2));

    // Verify new background color
    expect(
        (tester.firstWidget(find.byType(Scaffold)) as Scaffold).backgroundColor,
        Colors.grey);
  });```

My goal is checking the background color property of the Scaffold widget using driver before and after switching themes in the  INTEGRATION TEST

Hi @Joshuaerinosho
https://github.com/flutter/flutter/issues/86859#issuecomment-884975890 is from integration_test, if that wasn't clear for you.
Just tried  simpler example of chaning Scaffold color
class _EmptyScreenState extends State<EmptyScreen> {
  Color scaffoldColor = Colors.white;
  @override
  Widget build(BuildContext context) {
    return Scaffold(
        backgroundColor: scaffoldColor,
        appBar: AppBar(),
        body: Center(
          child: Text(widget.message),
        ),
        floatingActionButton: FloatingActionButton(
          child: Icon(Icons.color_lens),
          onPressed: () {
            setState(() {
              scaffoldColor = Colors.blue;
            });
          },
        ));
  }
}

void main() {
  IntegrationTestWidgetsFlutterBinding.ensureInitialized();
  testWidgets('Test Scaffold color', (WidgetTester tester) async {
    await tester.pumpWidget(MyApp());
    expect((tester.firstWidget(find.byType(Scaffold)) as Scaffold).backgroundColor, Colors.white);
    await tester.tap(find.byType(FloatingActionButton));
    await tester.pumpAndSettle();
    expect((tester.firstWidget(find.byType(Scaffold)) as Scaffold).backgroundColor, Colors.blue);
  });
}

This is better suited for Stack Overflow and  if you need help with your code, please see https://www.reddit.com/r/flutterhelp/

@TahaTesser  Thank you so much! 🙏🏼


docs: use server load function in the setHeaders example

Describe the bug
Current setHeaders documentation uses the universal load function in its example:
// src/routes/products/+page.js

/** @type {import('./$types').PageLoad} */
export async function load({ fetch, setHeaders }) {
  const url = `https://cms.example.com/products.json`;
  const response = await fetch(url);

  // cache the page for the same length of time
  // as the underlying data
  setHeaders({
    age: response.headers.get('age'),
    'cache-control': response.headers.get('cache-control')
  });

  return response.json();
}

However, the page is cached only if both criteria are matched (or if CSR is disabled)

SSR is enabled in the /products route
The /products pages is directly accessed

Reproduction
https://github.com/sveltejs/kit/issues/12473#issuecomment-2228582258
If the API does not respond with a cache-control header, it will be fetched every time the page is client-side rendered.
Also in a universal load function, the developer does not have control over the above API response caching.
The browser simply adheres to the API's HTTP response headers.
However, in a server load function, the developer can always have control using setHeaders.
Logs
No response
System Info
System:
  OS: macOS 14.5
  CPU: (10) arm64 Apple M1 Pro
  Memory: 37.39 MB / 16.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 20.15.1 - ~/.local/state/fnm_multishells/11115_1721012439034/bin/node
  npm: 10.7.0 - ~/.local/state/fnm_multishells/11115_1721012439034/bin/npm
  pnpm: 9.5.0 - ~/.local/state/fnm_multishells/11115_1721012439034/bin/pnpm
Browsers:
  Chrome: 126.0.6478.127
  Edge: 126.0.2592.102
  Safari: 17.5
npmPackages:
  @sveltejs/adapter-auto: ^3.0.0 => 3.2.2
  @sveltejs/kit: ^2.0.0 => 2.5.18
  @sveltejs/vite-plugin-svelte: ^3.0.0 => 3.1.1
  svelte: ^4.2.7 => 4.2.18
  vite: ^5.0.3 => 5.3.3

Severity
annoyance
Additional Information
The universal load function's caveat is documented.

When running in the browser, setHeaders has no effect.

Isn’t the data.json that’s fetched during CSR being cached correctly?

This is the reproduction I've used:
Navigating between / and /profile, the JSONPlaceholder is continuously fetched in the browser.

Profile

Home

// src/routes/profile/+page.ts
export const load = async ({ fetch, setHeaders }) => {
  await fetch('https://jsonplaceholder.typicode.com/users/1');
  setHeaders({ 'cache-control': 'public, max-age=604800' });
  return {};
};

When the /profile page is accessed directly, the HTML is properly cached.
HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
cache-control: public, max-age=604800
content-length: 871
content-type: text/html

@eltigerchino in the documentation example, the CMS fetch request would have been cached in the client.
/** @type {import('./$types').PageLoad} */
export async function load({ fetch, setHeaders }) {
  const url = `https://cms.example.com/products.json`;
  const response = await fetch(url); // has 'cache-control' header

  setHeaders({
    age: response.headers.get('age'),
    'cache-control': response.headers.get('cache-control')
  });

I have updated the above comment with a API response without a cache-control header.

I'm not sure if we want to change it to a server load function in this case because that would incur an additional network request roundtrip instead of directly fetching from the CMS itself. It's also likely that the developer would have control over cache-control headers of that CMS.

I've personally written this issue after facing the following Reddit question:

My homepage makes about 15 API calls to an external API in the +page.server.ts file. The data does not change very often, and I don't want those API calls made every time the homepage is loaded or navigated to. Instead, I'd like the API to be called the first time a user navigates to the homepage, and then cached data to be used for that user for the next 24hr.

To my surprise, no one was mentioning the setHeaders API.

Would there be a better example other than a CMS fetch request?
e.g. change it to a / route which a user might directly revisit multiple times?
If a server-side rendered HTML must be cached in the client (which is not the default behavior), shouldn't it be because the SSR is slow or computationally heavy? (similar to the question above)
Please correct me if I am misunderstanding the example code from the documentation.

I've personally written this issue after facing the following Reddit question:

My homepage makes about 15 API calls to an external API in the +page.server.ts file. The data does not change very often, and I don't want those API calls made every time the homepage is loaded or navigated to. Instead, I'd like the API to be called the first time a user navigates to the homepage, and then cached data to be used for that user for the next 24hr.

To my surprise, no one was mentioning the setHeaders API.
Would there be a better example other than a CMS fetch request?
e.g. change it to a / route which a user might directly revisit multiple times?
If a server-side rendered HTML must be cached in the client (which is not the default behavior), shouldn't it be because the SSR is slow or computationally heavy? (similar to the question above)
Please correct me if I am misunderstanding the example code from the documentation.

I think the meaning in the example is conveyed well enough: if you want to cache the page, then set a cache control header. In the user's reddit question, they may be calling an external API with a secret key, so they can't use a universal load function without exposing the secret.
If no secrets or server-only APIs are needed, a universal load function is almost always preferred.


Using Query Builder instead of Eloquent model?

Is it possible to use a Query Builder instead of Eloquent model with this? I have tried and it fails. Basically I want to join tables in a dynamic query and get the results to display. But even something as simple as
$rows = DB::table('users')->get();
$table = Table::create($rows);
return view('reports.generic', ['table' => $table]);

falls over.

This capability will be included in the next version.  Thanks for bringing it to my attention.

Thanks. Do you have any idea of the timeframe for this?

I went ahead and pushed this upstream from the new version so you can use it now.  It isn't sortable, but the 0.3.1 release allows for basic rendering.

Thanks. I downloaded your update and tried the example exactly as I posted at the start of this thread and it falls over with:
FatalErrorException in Table.php line 114:
Call to a member function first() on array

It looks like you have an older version installed, but that wouldn't really have mattered since the version I directed you to was fully broken due to a typo.  I just pushed another update, so please make sure your composer.json is requesting dev-master or 0.3.2.

I have checked and I am using your latest version, I have compared Table.php line by line between my local copy and the version here on Github. But I get the error I posted above, that first() cannot be used on an array at line 114 in Table.php.

OK, I've been digging deeper.  It looks like I was doing simple testing via a $query->paginate(), while the error occurs specifically with the standard $query->get().  I just pushed 0.3.3, please see if this works for your scenario.

Thanks - that works a treat!


Prevent msgspec.field from being called with too many arguments

Pull Request Checklist

[ ] New code has 100% test coverage
[ ] (If applicable) The prose documentation has been updated to reflect the changes introduced by this PR
[ ] (If applicable) The reference documentation has been updated to reflect the changes introduced by this PR

Description
Close Issue(s)

@all-contributors add @MatthewNewland for bug.


Feature/add upstream features

Insert the upstream features
The features and commits do work; the issue seems to be that the systems for EC2 are not loaded into the systems.

@nox-do Can be merged. Those are the features from Sean and friends.


How to deal with mobile devices

How do we deal with mobile devices?
Do we copy the current system?

As discussed on discord we'll just support static layouts that resize depending on the screensize (container queries). We'll not have breakpoints that change the amount of columns on a board.
See https://discord.com/channels/972958686051962910/1240640882932453396


is there a way to just get the information if the back or forward button isclicked ?

It might looks a little hacky but you can get it by confirm function which always returns true:
useNavigationGuard({
  confirm: ({ type }) => {
    if (type === 'popstate') onBackForward()
    return true
  }
})


Fix boot order handling

The way we handle boot order is deprecated and should be fixed.
The problem
Proxstar is still using the old boot order format, which means that when it creates a new vm, proxmox sees no boot hard disk, and it will reboot into the installer ad nauseam. This is fixable, you can manually set the boot order in the vm's options page, but in doing so, proxstar won't be able to read the boot order, and thus the vm won't be viewable at all from proxstar, so users will need a proxmox account with at least PVEVMConsole permissions to access the vm, and PVEVMUSER to edit anything.
Stuff you probably need to fix this
d44698a959d02986d4400f80fbd13c5fdbe6b9cd will need to be reverted, and then the boot order handling form, route, and methods in vm.py will need to be adapted.
See the qm conf file docs for the boot parameter to see what needs to be handled.

Also seeing 500's trying to view the VM when I do the workaround through proxmox.
2021-08-12 13:14:59,780 ERROR Exception on /vm/186 [GET]
Traceback (most recent call last):
  File "/opt/app-root/lib64/python3.8/site-packages/flask/app.py", line 2447, in wsgi_app
    response = self.full_dispatch_request()
  File "/opt/app-root/lib64/python3.8/site-packages/flask/app.py", line 1952, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/opt/app-root/lib64/python3.8/site-packages/flask/app.py", line 1821, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/opt/app-root/lib64/python3.8/site-packages/flask/_compat.py", line 39, in reraise
    raise value
  File "/opt/app-root/lib64/python3.8/site-packages/flask/app.py", line 1950, in full_dispatch_request
    rv = self.dispatch_request()
  File "/opt/app-root/lib64/python3.8/site-packages/flask/app.py", line 1936, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/opt/app-root/lib64/python3.8/site-packages/flask_pyoidc/flask_pyoidc.py", line 253, in wrapper
    return view_func(*args, **kwargs)
  File "/opt/app-root/src/proxstar/__init__.py", line 220, in vm_details
    return render_template(
  File "/opt/app-root/lib64/python3.8/site-packages/flask/templating.py", line 137, in render_template
    return _render(
  File "/opt/app-root/lib64/python3.8/site-packages/flask/templating.py", line 120, in _render
    rv = template.render(context)
  File "/opt/app-root/lib64/python3.8/site-packages/jinja2/environment.py", line 1090, in render
    self.environment.handle_exception()
  File "/opt/app-root/lib64/python3.8/site-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/opt/app-root/lib64/python3.8/site-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "/opt/app-root/src/proxstar/templates/vm_details.html", line 1, in top-level template code
    {% extends "base.html" %}
  File "/opt/app-root/src/proxstar/templates/base.html", line 90, in top-level template code
    {% block body %}
  File "/opt/app-root/src/proxstar/templates/vm_details.html", line 15, in block "body"
    {{ vm.boot_order|join(', ') }}
  File "/opt/app-root/lib64/python3.8/site-packages/jinja2/environment.py", line 471, in getattr
    return getattr(obj, attribute)
  File "/opt/app-root/src/proxstar/util.py", line 18, in _lazy_property
    setattr(self, attr_name, fn(self))
  File "/opt/app-root/src/proxstar/vm.py", line 126, in boot_order
    boot_order.append(boot_order_lookup[order])
KeyError: 'o'


Errors during reapp installation (OS X)

I removed nvm and installed node from scratch (brew install node). There are many errors during installation. I use OS X 10.10.3.
$ uname -a
Darwin hipertrackers-MacBook-Pro.local 14.3.0 Darwin Kernel Version 14.3.0: Thu Jan 22 23:54:42 PST 2015; root:xnu-2782.20.26~5/RELEASE_X86_64 x86_64

$ node -v
v0.12.0

$ npm -v
2.5.1

$ npm install -g reapp

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/6to5/node_modules/kexec
> node-gyp configure build

child_process: customFds option is deprecated, use stdio instead.
  CXX(target) Release/obj.target/kexec/src/kexec.o
../src/kexec.cc:22:30: error: use of undeclared identifier 'F_GETFD'
    int flags = fcntl (desc, F_GETFD, 0);
                             ^
../src/kexec.cc:26:15: error: use of undeclared identifier 'FD_CLOEXEC'
    flags &= ~FD_CLOEXEC; //clear FD_CLOEXEC bit
              ^
../src/kexec.cc:27:25: error: use of undeclared identifier 'F_SETFD'
    return fcntl (desc, F_SETFD, flags);
                        ^
../src/kexec.cc:43:34: error: unknown type name 'Arguments'; did you mean 'v8::internal::Arguments'?
static Handle<Value> kexec(const Arguments& args) {
                                 ^~~~~~~~~
                                 v8::internal::Arguments
/Users/hipertracker/.node-gyp/0.12.0/deps/v8/include/v8.h:127:7: note: 'v8::internal::Arguments' declared here
class Arguments;
      ^
../src/kexec.cc:44:17: error: calling a protected constructor of class 'v8::HandleScope'
    HandleScope scope;
                ^
/Users/hipertracker/.node-gyp/0.12.0/deps/v8/include/v8.h:816:13: note: declared protected here
  V8_INLINE HandleScope() {}
            ^
../src/kexec.cc:67:19: error: member access into incomplete type 'const v8::internal::Arguments'
    if ( 1 == args.Length() && args[0]->IsString() )
                  ^
/Users/hipertracker/.node-gyp/0.12.0/deps/v8/include/v8.h:127:7: note: forward declaration of 'v8::internal::Arguments'
class Arguments;
      ^
../src/kexec.cc:69:37: error: type 'const v8::internal::Arguments' does not provide a subscript operator
        String::Utf8Value v8str(args[0]);
                                ~~~~^~
../src/kexec.cc:78:44: error: too few arguments to function call, expected 2, have 1
        Local<Number> num = Number::New(err);
                            ~~~~~~~~~~~    ^
/Users/hipertracker/.node-gyp/0.12.0/deps/v8/include/v8.h:1999:3: note: 'New' declared here
  static Local<Number> New(Isolate* isolate, double value);
  ^
../src/kexec.cc:79:22: error: no member named 'Close' in 'v8::HandleScope'
        return scope.Close(num/*Undefined()*/);
               ~~~~~ ^
../src/kexec.cc:83:19: error: member access into incomplete type 'const v8::internal::Arguments'
    if ( 2 == args.Length() && args[0]->IsString() && args[1]->IsArray() )
                  ^
/Users/hipertracker/.node-gyp/0.12.0/deps/v8/include/v8.h:127:7: note: forward declaration of 'v8::internal::Arguments'
class Arguments;
      ^
../src/kexec.cc:85:37: error: type 'const v8::internal::Arguments' does not provide a subscript operator
        String::Utf8Value v8str(args[0]);
                                ~~~~^~
../src/kexec.cc:89:59: error: type 'const v8::internal::Arguments' does not provide a subscript operator
        Local<Array> argv_handle = Local<Array>::Cast(args[1]);
                                                      ~~~~^~
../src/kexec.cc:101:66: error: too few arguments to function call, expected 2, have 1
            String::Utf8Value arg(argv_handle->Get(Integer::New(i))->ToString());
                                                   ~~~~~~~~~~~~  ^
/Users/hipertracker/.node-gyp/0.12.0/deps/v8/include/v8.h:2012:3: note: 'New' declared here
  static Local<Integer> New(Isolate* isolate, int32_t value);
  ^
../src/kexec.cc:118:44: error: too few arguments to function call, expected 2, have 1
        Local<Number> num = Number::New(err);
                            ~~~~~~~~~~~    ^
/Users/hipertracker/.node-gyp/0.12.0/deps/v8/include/v8.h:1999:3: note: 'New' declared here
  static Local<Number> New(Isolate* isolate, double value);
  ^
../src/kexec.cc:119:22: error: no member named 'Close' in 'v8::HandleScope'
        return scope.Close(num/*Undefined()*/);
               ~~~~~ ^
../src/kexec.cc:127:49: error: no member named 'New' in 'v8::String'
    ThrowException(Exception::TypeError(String::New("kexec: invalid arguments")));
                                        ~~~~~~~~^
../src/kexec.cc:128:18: error: no member named 'Close' in 'v8::HandleScope'
    return scope.Close(Undefined());
           ~~~~~ ^
../src/kexec.cc:128:24: error: no matching function for call to 'Undefined'
    return scope.Close(Undefined());
                       ^~~~~~~~~
/Users/hipertracker/.node-gyp/0.12.0/deps/v8/include/v8.h:305:28: note: candidate function not viable: requires single argument 'isolate', but no arguments were provided
  friend Handle<Primitive> Undefined(Isolate* isolate);
                           ^
../src/kexec.cc:134:9: error: no matching function for call to 'NODE_SET_METHOD'
        NODE_SET_METHOD(target, "kexec", kexec);
        ^~~~~~~~~~~~~~~
/Users/hipertracker/.node-gyp/0.12.0/src/node.h:240:25: note: expanded from macro 'NODE_SET_METHOD'
#define NODE_SET_METHOD node::NODE_SET_METHOD
                        ^~~~~~~~~~~~~~~~~~~~~
/Users/hipertracker/.node-gyp/0.12.0/src/node.h:228:13: note: candidate function [with TypeName = v8::Handle<v8::Object>] not viable: no known conversion from
      'Handle<v8::Value> (const v8::internal::Arguments &)' to 'v8::FunctionCallback' (aka 'void (*)(const FunctionCallbackInfo<v8::Value> &)') for 3rd argument
inline void NODE_SET_METHOD(const TypeName& recv,
            ^
19 errors generated.
make: *** [Release/obj.target/kexec/src/kexec.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1067:12)
gyp ERR! System Darwin 14.3.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
gyp ERR! cwd /usr/local/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/6to5/node_modules/kexec
gyp ERR! node -v v0.12.0
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/webpack/node_modules/watchpack/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

child_process: customFds option is deprecated, use stdio instead.
  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node: Finished
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>
><EMAIL_ADDRESS>install /usr/local/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/6to5/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

child_process: customFds option is deprecated, use stdio instead.
  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node: Finished
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished

><EMAIL_ADDRESS>install /usr/local/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/webpack-dev-server/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
/usr/local/bin/reapp -> /usr/local/lib/node_modules/reapp/reapp
/usr/local/bin/reapp-new -> /usr/local/lib/node_modules/reapp/reapp-new
/usr/local/bin/reapp-build -> /usr/local/lib/node_modules/reapp/reapp-build
/usr/local/bin/reapp-debug -> /usr/local/lib/node_modules/reapp/reapp-debug
/usr/local/bin/reapp-run -> /usr/local/lib/node_modules/reapp/reapp-run
<EMAIL_ADDRESS>/usr/local/lib/node_modules/reapp
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

@hipertracker ok, just looking at version differences here.. i'm on 10.10.2, 10.36 for node (not sure how homebrew is neglecting to update me here), and 2.5.0 for npm.
let me get updated to 0.12 and go from there. though i believe 10.10.3 for osx is beta (can't imagine that mattering at all).

@hipertracker i was able to duplicate your errors.
I upgraded from node 0.10.36 to 0.12.0 via homebrew and am getting the same errors. v0.10.36 yielded successful install of reapp via npm. /cc @natew
a bit of additional logging from the node install: i haven't read through the entire stack that we're both seeing, but wanted to document it here along with the stack above..
==> Installing node
==> Downloading https://downloads.sf.net/project/machomebrew/Bottles/node-0.12.0.yosemite.bottle.tar.gz
######################################################################## 100.0%
==> Pouring node-0.12.0.yosemite.bottle.tar.gz
Warning: node dependency icu4c was built with a different C++ standard
library (libc++ from clang). This may cause problems at runtime.
==> Caveats
If you update npm itself, do NOT use the npm update command.
The upstream-recommended way to update npm is:
  npm install -g npm@latest

Bash completion has been installed to:
  /usr/local/etc/bash_completion.d
==> Summary
🍺  /usr/local/Cellar/node/0.12.0: 2196 files, 26M

could the difference compilation used for that icu4c lib cause these issues? again i haven't gone through the stack to validate this thought.

Nice! I've seen those as well and had trouble debugging. It's from node-gyp which comes from 6to5.
I've actually found that sometimes, not always, despite the errors it still works. In Ubuntu I needed to do:
sudo apt-get install build-essential
From the node-gyp docs:
On Unix:
python (v2.7 recommended, v3.x.x is not supported)
make
A proper C/C++ compiler toolchain, like GCC
On Windows:
Python (v2.7.3 recommended, v3.x.x is not supported)
Windows XP/Vista/7:
Microsoft Visual Studio C++ 2010 (Express version works well)
For 64-bit builds of node and native modules you will also need the Windows 7 64-bit SDK
If the install fails, try uninstalling any C++ 2010 x64&x86 Redistributable that you have installed first.
If you get errors that the 64-bit compilers are not installed you may also need the compiler update for the Windows SDK 7.1
Windows 7/8:
Microsoft Visual Studio C++ 2012/13 for Windows Desktop (Express version works well)

Perhaps I should look at outputting that message if node-gyp fails?

this issue occurs on both node and io.js

Hi, I think reapp installed correctly, but failing to run reapp kitchen-sink. Thank you in advance for help, as I'm fresh to both node + express, but excited to dive in after reading about reapp. Thanks!
See below for terminal results from the following commands:

♥ node -v
♥ npm -v
npm install -g reapp
♥ reapp run (in kitchen-sink repo pulled from https://github.com/reapp/kitchen-sink)
♥ npm install -g reapp-pack
♥ reapp run

♥ node -v
v0.10.36

♥ npm -v
1.4.28

♥ npm install -g reapp
|
><EMAIL_ADDRESS>install /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/webpack/node_modules/watchpack/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node: Finished
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished

><EMAIL_ADDRESS>install /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/6to5/node_modules/kexec
> node-gyp configure build

  CXX(target) Release/obj.target/kexec/src/kexec.o
  SOLINK_MODULE(target) Release/kexec.node
  SOLINK_MODULE(target) Release/kexec.node: Finished

><EMAIL_ADDRESS>install /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/6to5/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node: Finished
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished
-
><EMAIL_ADDRESS>install /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/node_modules/reapp-pack/node_modules/webpack-dev-server/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
/Users/Alex/.nvm/v0.10.36/bin/reapp-new -> /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/reapp-new
/Users/Alex/.nvm/v0.10.36/bin/reapp -> /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/reapp
/Users/Alex/.nvm/v0.10.36/bin/reapp-run -> /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/reapp-run
/Users/Alex/.nvm/v0.10.36/bin/reapp-debug -> /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/reapp-debug
/Users/Alex/.nvm/v0.10.36/bin/reapp-build -> /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp/reapp-build
<EMAIL_ADDRESS>/Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
[16:38:29] (master) kitchen-sink
♥ reapp run
Error! Make sure you have run npm install in reapp-pack
Error! Make sure you have run npm install in reapp-pack
Starting...
Running express server on 3010 ...
Starting Webpack server on localhost 3011 ...

[16:42:03] (master) kitchen-sink
♥ npm install -g reapp-pack
/
><EMAIL_ADDRESS>install /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp-pack/node_modules/webpack/node_modules/watchpack/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node: Finished
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished

><EMAIL_ADDRESS>install /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp-pack/node_modules/6to5/node_modules/kexec
> node-gyp configure build

  CXX(target) Release/obj.target/kexec/src/kexec.o
  SOLINK_MODULE(target) Release/kexec.node
  SOLINK_MODULE(target) Release/kexec.node: Finished

><EMAIL_ADDRESS>install /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp-pack/node_modules/6to5/node_modules/chokidar/node_modules/fsevents
> node-gyp rebuild

  SOLINK_MODULE(target) Release/.node
  SOLINK_MODULE(target) Release/.node: Finished
  CXX(target) Release/obj.target/fse/fsevents.o
  SOLINK_MODULE(target) Release/fse.node
  SOLINK_MODULE(target) Release/fse.node: Finished
/
><EMAIL_ADDRESS>install /Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp-pack/node_modules/webpack-dev-server/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/bufferutil.node
  SOLINK_MODULE(target) Release/bufferutil.node: Finished
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/validation.node
  SOLINK_MODULE(target) Release/validation.node: Finished
<EMAIL_ADDRESS>/Users/Alex/.nvm/v0.10.36/lib/node_modules/reapp-pack
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
[16:45:07] (master) kitchen-sink
♥ reapp run
Error! Make sure you have run npm install in reapp-pack
Error! Make sure you have run npm install in reapp-pack
Starting...
Running express server on 3010 ...
Starting Webpack server on localhost 3011 ...

Ok, I've updated 6to5, the new version avoids this dependency. @fibric @megalithic @hipertracker let me know if that fixed the bug, try re-installing reapp and running again.

reapp is installing now on OS X 10.3.3. tnx

yes its works now on node and io.js :)

it does work on company windows machine too.


Release Testing: Register paragraph could be reworded

ref #2583
In https://wallaroo-docs-rc.netlify.com/book/getting-started/vagrant-setup.html

Register today and receive a Wallaroo T-shirt and a one-hour phone consultation with Sean, our V.P. of Engineering, to discuss your streaming data questions. Not sure if you have a streaming data problem? Not sure how to go about architecting a streaming data system? Looking to improve an existing system? Not sure how Wallaroo can help? Sean has extensive experience and is happy to help you work through your questions.

The first sentence in the paragraph could be rewritten to something like:
Register today to receive a Wallaroo T-Shirt. We'll also have Sean T. Allen, our V.P. of Engineering reach out to answer your streaming data questions in a one hour phone call.

@enilsen16 I'm assigning this to you, but I'd say check with either @SeanTAllen or @chuckblake to see if they agree the re-wording is wanted for this paragraph.

Remove it for now.

@SeanTAllen to confirm. You want me to remove the entire paragraph?

Confirmed. Kill it.

Closed in #2606


[T4A2][W15-B4]Jasper Lee

Ready for review

you need to update the parser test file as well that uses the parseCommand method :-)
I think this is a good PR in general.

@jasperlee27
Some comments added. Please ack & close the PR after reading comments.

Acknowledged!


[BUG] instance-manager-e emits Wait for process pvc-xxxx to shutdown constantly

Describe the bug (🐛 if you encounter this issue)
The issue is found when investigating the issue https://github.com/longhorn/longhorn/issues/5507.
If the share manager (SM) pod mounts a problematic volume, whose engine fails to read/write/unmap because the replicas are gone, the SM controller will mark the SM resource as error. We can see the IO errors in the engine logs.
2023-03-16T05:28:42.207283947Z time="2023-03-16T05:28:42Z" level=error msg="I/O error" error="tcp://<IP_ADDRESS>:10000: EOF; tcp://<IP_ADDRESS>:10000: EOF; tcp://<IP_ADDRESS>:10000: EOF"
2023-03-16T05:28:42.207288939Z time="2023-03-16T05:28:42Z" level=info msg="Monitoring stopped tcp://<IP_ADDRESS>:10000"
2023-03-16T05:28:42.207293234Z time="2023-03-16T05:28:42Z" level=info msg="Monitoring stopped tcp://<IP_ADDRESS>:10000"
2023-03-16T05:28:42.207297593Z time="2023-03-16T05:28:42Z" level=info msg="Monitoring stopped tcp://<IP_ADDRESS>:10000"
2023-03-16T05:28:42.220541473Z response_process: Receive error for response 3 of seq 325
2023-03-16T05:28:42.229637741Z tgtd: bs_longhorn_request(97) fail to write at 536870912 for 4096
2023-03-16T05:28:42.229650947Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 2a -14 4096 536870912, Success
2023-03-16T05:28:42.220560331Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:42Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:42.250720622Z response_process: Receive error for response 3 of seq 326
2023-03-16T05:28:42.250740144Z tgtd: bs_longhorn_request(97) fail to write at 0 for 4096
2023-03-16T05:28:42.250745873Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 2a -14 4096 0, Success
2023-03-16T05:28:42.282634342Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:42Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:42.291009586Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:42Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:42.291015913Z response_process: Receive error for response 3 of seq 327
2023-03-16T05:28:42.291047274Z tgtd: bs_longhorn_request(97) fail to write at 0 for 4096
2023-03-16T05:28:42.291053603Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 2a -14 4096 0, Success
2023-03-16T05:28:43.753494513Z response_process: Receive error for response 3 of seq 328
2023-03-16T05:28:43.753532361Z tgtd: bs_longhorn_request(111) fail to read at<PHONE_NUMBER> for 4096
2023-03-16T05:28:43.753538820Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096<PHONE_NUMBER>, Success
2023-03-16T05:28:43.753881127Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:43Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:43.773457307Z response_process: Receive error for response 3 of seq 329
2023-03-16T05:28:43.773477422Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:43Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:43.773585654Z tgtd: bs_longhorn_request(111) fail to read at<PHONE_NUMBER> for 4096
2023-03-16T05:28:43.773594580Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096<PHONE_NUMBER>, Success
2023-03-16T05:28:43.862087171Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:43Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:43.862160559Z response_process: Receive error for response 3 of seq 330
2023-03-16T05:28:43.862168745Z tgtd: bs_longhorn_request(111) fail to read at<PHONE_NUMBER> for 4096
2023-03-16T05:28:43.862174029Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096<PHONE_NUMBER>, Success
2023-03-16T05:28:43.881179610Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:43Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:43.881223320Z response_process: Receive error for response 3 of seq 331
2023-03-16T05:28:43.881351649Z tgtd: bs_longhorn_request(111) fail to read at<PHONE_NUMBER> for 4096
2023-03-16T05:28:43.881360995Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096<PHONE_NUMBER>, Success
2023-03-16T05:28:44.021443381Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:44Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:44.021496644Z response_process: Receive error for response 3 of seq 332
2023-03-16T05:28:44.021503726Z tgtd: bs_longhorn_request(111) fail to read at<PHONE_NUMBER> for 4096
2023-03-16T05:28:44.021509131Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096<PHONE_NUMBER>, Success
2023-03-16T05:28:44.037261380Z response_process: Receive error for response 3 of seq 333
2023-03-16T05:28:44.037351656Z tgtd: bs_longhorn_request(111) fail to read at<PHONE_NUMBER> for 4096
2023-03-16T05:28:44.037382317Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096<PHONE_NUMBER>, Success
2023-03-16T05:28:44.040139748Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:44Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:44.064401757Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:44Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:44.064453910Z response_process: Receive error for response 3 of seq 334
2023-03-16T05:28:44.064468087Z tgtd: bs_longhorn_request(111) fail to read at 0 for 16384
2023-03-16T05:28:44.064473712Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 16384 0, Success
2023-03-16T05:28:44.065004140Z response_process: Receive error for response 3 of seq 335
2023-03-16T05:28:44.065693182Z tgtd: bs_longhorn_request(111) fail to read at 0 for 4096
2023-03-16T05:28:44.065758027Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096 0, Success
2023-03-16T05:28:44.066361284Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:44Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:44.075005057Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:28:44Z" level=error msg="I/O error" error="no backend available"
2023-03-16T05:28:44.075059306Z response_process: Receive error for response 3 of seq 336
2023-03-16T05:28:44.075087059Z tgtd: bs_longhorn_request(111) fail to read at 0 for 4096
2023-03-16T05:28:44.075092959Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096 0, Success
2023-03-16T05:28:59.085143113Z timeout_handler: Timeout request 337 due to disconnection
2023-03-16T05:28:59.085168263Z tgtd: bs_longhorn_request(183) Failed to punch hole for UNMAP at offset:0 length:4096
2023-03-16T05:28:59.085175241Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 42 0 16 0, Success
2023-03-16T05:28:59.101596459Z timeout_handler: Timeout request 338 due to disconnection
2023-03-16T05:28:59.101664819Z tgtd: bs_longhorn_request(111) fail to read at 0 for 4096
2023-03-16T05:28:59.101672437Z tgtd: bs_longhorn_request(210) io error 0x1f8f340 28 -14 4096 0, Success
2023-03-16T05:29:14.117335725Z timeout_handler: Timeout request 339 due to disconnection

The volume controller will be aware of the error and request remount. Afterwards, the problematic volume will be detached. However, the engine instance deletion is stuck because of the deadlock caused by the previous failed UNMAP operation (code).
2023-03-16T05:32:03.925923472Z [longhorn-instance-manager] time="2023-03-16T05:32:03Z" level=info msg="Process Manager: prepare to delete process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6"
2023-03-16T05:32:03.925957061Z [longhorn-instance-manager] time="2023-03-16T05:32:03Z" level=info msg="Process Manager: deleted process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6"
2023-03-16T05:32:03.925991047Z [longhorn-instance-manager] time="2023-03-16T05:32:03Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:03.926008473Z [longhorn-instance-manager] time="2023-03-16T05:32:03Z" level=info msg="Process Manager: trying to stop process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6"
2023-03-16T05:32:03.926067372Z [longhorn-instance-manager] time="2023-03-16T05:32:03Z" level=info msg="Wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown"
2023-03-16T05:32:03.926495690Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:32:03Z" level=warning msg="Received signal interrupt to shutdown"
2023-03-16T05:32:03.929002376Z [pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6] time="2023-03-16T05:32:03Z" level=warning msg="Starting to execute registered shutdown func github.com/longhorn/longhorn-engine/app/cmd.startController.func1"
2023-03-16T05:32:04.026913598Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown"
2023-03-16T05:32:04.026943452Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.059550306Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Process Manager: prepare to delete process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6"
2023-03-16T05:32:04.059703724Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Process Manager: deleted process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6"
2023-03-16T05:32:04.059889110Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.127919537Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.127948565Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown"
2023-03-16T05:32:04.161176151Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.228405560Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown"
2023-03-16T05:32:04.228511921Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.261722762Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.328553008Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.328635348Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown"
2023-03-16T05:32:04.330718903Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Process Manager: prepare to delete process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6"
2023-03-16T05:32:04.330737099Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Process Manager: deleted process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6"
2023-03-16T05:32:04.330776189Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.362030183Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=debug msg="Process Manager: wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown before unregistering process"
2023-03-16T05:32:04.429279851Z [longhorn-instance-manager] time="2023-03-16T05:32:04Z" level=info msg="Wait for process pvc-d17761d6-a38a-4c87-8b63-2f85b0426cd6-e-2b1510e6 to shutdown"

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Perform '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version: v1.4.0
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of management node in the cluster:
Number of worker node in the cluster:

Node config

OS type and version:
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:

Additional context
https://github.com/longhorn/longhorn/issues/5537

Trim (unmap) feature is not in v1.3.3, so we don't need to backport to v1.3.3. cc @innobead

Well done!!
@derekbit what's the workaround? reattach the volume to make the engine restart? I should add this issue to https://github.com/longhorn/longhorn/wiki/Outstanding-Known-Issues-of-Releases.

Yes. Probably the simplest workaround is killing the stuck engine...

Verified on master-head 20230329

longhorn master-head (6764850)
longhorn-manager master-head (79acd76)

The test steps
The case 4 of https://longhorn.github.io/longhorn-tests/manual/pre-release/node/kubelet-restart-on-a-node/.
Result Passed
We can see in the instance-manager-e log that the PVC deletion process was successful.
supportbundle_9ba22ba5-77f3-4e9e-96d1-44e4bed09566_2023-03-29T11-09-21Z.zip


Relative pronouns

Consider the below sentence
50 year old Male with history of alcohol abuse and hypertension who presents with emesis with blood clots.
Is relative pronoun outside the scope of coreference? How do I relate the relative pronoun 'who' to 'Male'?
Best Regards,
Vishal

Hmm, I think (at least one of) the problem is that it is not a well formed sentence. So the parser can get a good parse tree. (see https://en.wikipedia.org/wiki/Well-formedness for example)


chore: chores

Codecov Report

Merging #9 (78f8402) into master (b60cddf) will increase coverage by 0.87%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master       #9      +/-   ##
==========================================
+ Coverage   87.37%   88.24%   +0.87%
==========================================
  Files          11       11
  Lines         689      689
==========================================
+ Hits          602      608       +6
+ Misses         87       81       -6

Impacted Files
Coverage Δ

src/lib/tkill.c
85.29% <0.00%> (+5.88%)
:arrow_up:

src/judger/general.c
69.81% <0.00%> (+7.54%)
:arrow_up:

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 b60cddf...78f8402. Read the comment docs.


Fix json parameter to support Flask 0.9

Flask 0.10 introduced the Request.get_json method, which webargs expects
to exist. This tiny change lets webargs work with Flask 0.9 to parse
JSON data in HTTP POST content.

I am hesitant to promise that webargs will be completely compatible with Flask<=0.10.0 moving forward, but this change is AOK. Thanks!


TELEWORK: Re-Name Task Tab

User Story
As a manager/reviewer I want know where I am and what actions are expected of me, so I can  process an employee telework agreement efficiently as possible
Tasks

[ ] Change the label on the 'Task' tab to 'Review and Process Applications"

in all environments
Acceptance Criteria

[ ] tab now reads 'Review and Process Applications"
[ ] visible to manager/reviewer role
[ ] visible in TEST and PROD environments

The logic for which tab is displayed to which roles will be implemented in #343. The estimate in this ticket only covers the text change.

Based on my discussion with @HasanSifat, the Reviewer/supervisor will see both the "Review and Process Applications" and "Forms" tabs.

Slight change on this one, Reviewers/supervisors AND Submitters will both NOT have access to the Forms tab and will also NOT be able to see the tab once inside the formsflow tool/dashboard interface.

Quick question about this ticket; What should be done about the text inside the previously named 'Tasks' tab? In the attached image, i'm referring to the text still showing 'Tasks'.

Hi David! Is it possible to take this popup box out completely? The tab name at the top is sufficient information for users.

@HasanSifat definitely, i'll make the changes and note this conversation in the PR description

thank you!

I don't see this in any environment

Tested successfully in TEST environment. ready to be deployed to PROD

Tested successfully in PROD. Closing ticket!


Clarify expected behavior if remote signer URL is not provided

As per spec, importing remote keys does not require to provide the url as part of the remote signer definition as only the pubkey is required.
https://github.com/ethereum/keymanager-APIs/blob/f99e41560b0db7cb922baa3be52735d611280f8b/types/import_remote_signer_definition.yaml#L2
At least in Lodestar, we require the url to be present and to be a valid URL, otherwise the key will not be imported due to an error.
What I would like to clarify is the following

is it by mistake that the url is optional and should it be required instead
or is the validator client expected to infer the URL from CLI args such as --externalSigner.url

The later is not always possible, at least in Lodestar, as the --externalSigner.url flag is optional and is not strictly required to use a remote signer. Using the keymanager API also allows to import remote signer keys from different remote signers while the CLI flag has a 1:1 relationship.
As the URL will be required when the validator client has to send a remote signing request , the spec should at a minimum clarify the expected behavior if the remote signer URL is not provided.

In Lighthouse the url field is required
https://github.com/sigp/lighthouse/blob/3058b96f2560f1da04ada4f9d8ba8e5651794ff6/common/eth2/src/lighthouse_vc/std_types.rs#L139-L142

Based on reviewing other clients (and if I got this correctly)

Nimbus requires url field (ref)
Teku has it marked as optional (ref)
Prysm allows to provide url field but logs a warning and only supports URL from CLI flag (ref)

And as noted in Lodestar and Lighthouse the url field is required. This means 3 out of 5 clients are not spec compliant right now.
We could set it as required in the spec and it wouldn't really require a change on server side but api client implementations that currently assume that the URL can be omitted would require a breaking change but since those api clients already don't work with most server implementations it might be for the best.

it was quite intentionally optional...  Making it required i'd class as a breaking change. I do understand what you're saying about some clients being required now, but that doesn't validate considering breaking the api...
To me the clear answer is the clients marking it required should probably become compliant with the spec, and if that means they 400 when a url isn't present, at least it's consistent.

I'm fairly sure the reason that it's 'optional' is because a default url from another source is one of the flows.

Might be that I am not fully aware of the use case of this API but so far I have just seen it being misused to fix some other shortcomings clients have, e.g. keeping keys between validator client and remote signer in sync (https://github.com/ChainSafe/lodestar/issues/6624).
For example, Diva has implemented a custom reload script to import missing keys but it does not provide the url right now which is why it fails with Lodestar and also does not remove any keys, meaning if a key is removed from Diva is will cause noisy errors as Lodestar will still try to handle duties for the validator.
In my opinion, the remote keys api only makes sense if you either don't have a 1:1 setup or the remote signer is not configured via CLI.
And if a client has a remote signer configured via CLI flag (e.g. --externalSigner.url) it should make sure to keep the keys in sync itself by updating the in-memory validator store based on response from GET /api/v1/eth2/publicKeys API of the remote signer.
As of right now, only Nimbus keeps the keys in sync but I feel like this would remove a headache for tooling around remote signers if clients could handle this internally.
Curious, what other teams think about this

and if that means they 400 when a url isn't present, at least it's consistent.

Agreed that it's probably not worth a spec change, and keeping it as optional leaves the option open for the implementation to get it from another source.
If the implementation returns a 400 if the url is not provided it is probably not strictly spec compliant but at least in case of Lodestar it is better than setting a default value which might not be transparent to the user.
This clarifies the expected behavior, although it could be more well-defined in the spec, but likely not worth the effort / coordination considering the limited use cases for this api


Artists: Additional Info

Hello, your code is a lifesaver. Thanks so much!
Is it possible to add Gallery Images and/or Social Media Links to artistInfo?

Thought the /artistInfo endpoint included those, but I guess not :P


Fix a python2.6 regression code

Jenkins are complaining about these py2.6 code that was recently inserted.

test this please

test failure doesn't seems to be related to this.

test this please


v2.2.4 "Jenkins pod not found" - Pipeline not re-creating services

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Delete Pipeline services
Delete Pipeline
Re-authenticate to Gitlab

Result:
Pipeline required services are not re-created

Other details that may be helpful:
The Pipeline was showing that it was pushing to the private registry, but the image did not exist on the private registry
I deleted the Pipeline services to start over.
But upon re-authenticating to Gitlab, and starting a new run, the Pipeline didn't re-create its required services
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.2.4
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): metal
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:           18.09.6
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        481bc77
 Built:             Sat May  4 02:35:27 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.6
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       481bc77
  Built:            Sat May  4 01:59:36 2019
  OS/Arch:          linux/amd64
  Experimental:     false

I think this is related https://github.com/rancher/rancher/issues/18779#issuecomment-471478221

That did it.


Occasional Crash with Cubic Chunks installed

https://pastebin.com/cT0tP4LX
Happens occasionally, but only on world-loading.

Actually are you sure this doesn't happen without cubic chunks with otherwise the same mod list?

I've been using TickDynamic since beginning at the start of making my modpack, which is a long time - and after the addition of CC I've beginning to get it.


Temp Chains Duration Calc is Wrong

Temp Chains duration modifier should (duration/(1-.4)) instead of (duration/.4). Also, the 0.4 needs to account for increased curse effect. So with the max 40% increase on the passive tree, that's 56% slower. So the numbers would be (duration/(1-0.56)).

What you're describing is exactly how it's currently implemented.
With no increased curse effect:

With 40% increased curse effect:


Build pre-compute framework

[x] Build pre-compute framework, most likely as a scheduled job, e.g. via celery/huey

Pre-compute framework was built with Apache Kafka and runs immediately after the import pipeline.  Leaving this in review column until the end of the project in case there is any feedback in the final stages of development.

As we approach the end of the project, closing this one off


This project is dead?

@reg2005 please, reply the issues and build a complete instructions to configure and use.
We need a complete documentation to use.

I totally agree! I've been trying to make a Schedule for 1 week and the documentation doesn't help me and nothing

Hi @filipe-mariz, I solve with this structure

Hello! Sorry for waiting. Please upgrade to 2.0.2


[iOS] Swipe Crash CarouselView 1.5.6

Hy,
i used the Carousel with webviews in 1.5.0 and everything was fine. But in 1.5.6 i get a crash in iOS after about 10 swipes. (if i switch back to 1.5.0 everything is fine again)
I catched the bug with Hockeyapp  -> Collection <CALayerArray: 0x61000024c660> was mutated while being enumerated.'

Hi @BlackRamsis thank you very much for your feedback
Could you please create small sample with this issue?
It means, that i need to lock something in additional palace..

i tried to reproduce this with an simple app, but the error is not showing. seems like  a race condition only happening while heavy load

since the new update, I have some lag and crashes to

hmmm, how can we emulate it?
Maybe, you can download source code and debug it with your heavy project.
Probably, we can retrieve more info..

and this issue too =)

could you please update package step by step and tell me, what version breaks your app =)
It isn't very difficult, use binary search for it)
firstly check version 1.5.3, and
if it's fine, check 1.5.2 - 1.5.1,
else check version 1.5.4 - 1.5.5

@BlackRamsis any updates?)

@BlackRamsis  upd.

@BlackRamsis  upd.

closed for now) i will reopen it, if you send me reproduction)
thx