Address not valid during read

I am using the camera Alvium 1800 U-319. I have installed the VimbaX SDK (VimbaX_Setup-2022-1-Win64.exe), and installed VmbPy v1.0.1 in a new Python 3.11 virtual environment (pip install https://github.com/alliedvision/VmbPy/releases/download/1.0.1/vmbpy-1.0.1-py3-none-any.whl). I have tried some of the example files with no success, always getting the error FeatureEnumRange GenICam::RuntimeException: Address not valid during read (address=-1342109900; length=4).
To demonstrate the issue, I have created a basic script to get all of the cameras and print their IDs, then tries to access the first camera context:
import vmbpy

if __name__ == '__main__':
    vmb = vmbpy.VmbSystem.get_instance()
    with vmb:
        cams = vmb.get_all_cameras()
        for cam in cams:
            print(cam)
        with cams[0] as cam:
            print(cam)

This outputs the following:
Camera(id=DEV_1AB22C0235C2)
03-29-2023 15:34:49.461 [T] FeatureEnumRange GenICam::RuntimeException: Address not valid during read (address=-1342109900; length=4)
Traceback (most recent call last):
  File "D:\Development\Assembler\vmbpy-test\main.py", line 9, in <module>
    with cams[0] as cam:
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\util\tracer.py", line 134, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\camera.py", line 106, in __enter__
    self._open()
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\util\tracer.py", line 134, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\util\context_decorator.py", line 44, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\camera.py", line 517, in _open
    self._attach_feature_accessors()
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\util\tracer.py", line 134, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\featurecontainer.py", line 64, in _attach_feature_accessors
    self._feats = discover_features(self._handle)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\util\tracer.py", line 134, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\feature.py", line 1209, in discover_features
    result.append(_build_feature(handle, info))
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\feature.py", line 1174, in _build_feature
    feat = EnumFeature(handle, info)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\util\tracer.py", line 134, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\feature.py", line 489, in __init__
    self.__entries: EnumEntryTuple = _discover_enum_entries(self._handle, self._info.name)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\util\tracer.py", line 134, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\feature.py", line 594, in _discover_enum_entries
    call_vmb_c('VmbFeatureEnumRangeQuery', handle, feat_name, None, 0, byref(enums_count))
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\util\tracer.py", line 134, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\c_binding\vmb_c.py", line 891, in call_vmb_c
    getattr(_lib_instance, func_name)(*args)
  File "C:\Users\bvitaz\.virtualenvs\vmbpy-test--FxYl47t\lib\site-packages\vmbpy\c_binding\vmb_c.py", line 815, in _eval_vmberror
    raise VmbCError(result)
vmbpy.c_binding.vmb_common.VmbCError: VmbCError(<VmbError.InternalFault: -1>)

Process finished with exit code 1

VmbViewer can connect to the camera and shows images as expected.
How can I get past this error?

Apparently the camera firmware was out of date and updating it fixed the problem.


Source options should be shown in a context menu rather than dialog tabs

I don't think we've agreed on this being the right solution. It'd be better for us to work on a revamped design doc for sources to think past where we currently are.


Add cactoos-matchers

Let's add cactoos-matchers to frameworks/libraries list.

@yegor256/z please, pay attention to this pull request

@fabriciofx/z this pull request is too small, just 2 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @yegor256/z please review this and merge or reject

@fabriciofx thanks!

Job gh:yegor256/elegantobjects.github.io#59 is not assigned, can't get performer


Compute variable validations on server side

Range, invalid format, and blank (for required) value checking should be included when saving and updating sheets. Client-side inline validations are already being handled by server validators.

Also make sure that grid and checkbox variables are built correctly when checking required validations for hidden and visible variables.

[x] Build sheet_variables from passed in variables and existing variables on sheet
[ ] Build responses correctly from passed in parameters
[ ] Build grids correctly from passed in parameters


Add legend, grid, and get/remove plot components

Added the methods "legend" and "grid" to add a legend (using the already existing "Legend" type) and toggle on/off axes grids, more or less in matlab-fashion.
Also added two methods to help manipulate the components of a plot: "getcomponents" (returns the vector of components in a given FramedPlot), and "rmcomponents" (splice the vector of components of the FramedPlot).

Thanks!


DOI extraction

I've noticed that there are some cases where the DOI is correctly extracted from the article header, however, they are incorrectly mangled in the output.
Example: origin9833693929434438741.pdf
In this article the DOI is correctly extracted up to here: https://github.com/kermitt2/grobid/blob/694f0ed055e8c9a5d5efdc314ebef78e5e2640cf/grobid-core/src/main/java/org/grobid/core/engines/HeaderParser.java#L269
There are several articles (e.g. Plos) where the DOI in the header is split by a breakline, in such cases the DOI is wrongly substituted.
I'm not sure, maybe we could substitute it only when the found DOI is the same or larger than the one already extracted by the header parser.
Another thing is that we could extract the DOI exploiting the clickable URL to correct the suffix.

I'm adding more examples (CC-BY):

DOI includes the final DOI: 10.1128_msphere.00700-18.pdf
DOI includes the page numbers 10.1073_pnas.2221103120.pdf
DOI is truncated, both the header parser and the regex miss the second line 10.1172_jci.insight.159058.pdf
Same as above: 10.1172_jci.insight.166698.pdf

Related to the pariod I found a (I'm assuming) wrongly annotated training data. Adding a PR for it for version 0.8.2

Here another example:
huang-et-al-2019-transcriptional-sequencing-uncovers-survival-mechanisms-of-salmonella-enterica-serovar-enteritidis-in.pdf
Even with header consolidation enabled the DOI is mangled:
                    <idno type="MD5">155593D8B22A3FFE8735045743913815</idno>
                    <idno type="DOI">10.1128/mSphere</idno>
                    <note type="submission">Received 23 December 2018 Accepted 15 January 2019</note>

More examples:
10.1007_s13280-020-01405-w.pdf
jci.insight.159058.v2.pdf
jci.insight.166698.v2.pdf


"dotnet publish" VSTS task reorders arguments, cannot pass additional arguments to MSBuild

To repro, create an instance of the .NET Core (Preview) task, set the command to 'publish' and the arguments to the following:
--output $(Build.ArtifactStagingDirectory) --configuration $(BuildConfiguration) /p:MyProperty=true
When executed, you'll notice that the above arguments are not in the order specified. The following command ends up getting executed:
dotnet.exe publish <pathToCsproj> --configuration Release /p:MyProperty=true --output <outputPath>
Note that the argument order was switched around. This causes dotnet.exe to treat everything after '--configuration Release' as an additional argument to MSBuild. MSBuild then fails on the --output argument.

I will look into it.

https://github.com/Microsoft/vsts-tasks/pull/4013 Fixed in this PR


Add @BetaApi for exactly once delivery

We did not decorate new methods added by https://github.com/googleapis/java-pubsub/pull/1022 for exactly once delivery as @BetaApi, but we should do so until the APIs are GA.
See some examples of this for ordering (which are supposed to be removed by now):
https://github.com/googleapis/java-pubsub/blob/eaeedd8bbe31cad3810687a29c5999f76876671d/google-cloud-pubsub/src/main/java/com/google/cloud/pubsub/v1/Publisher.java#L320-L321
https://github.com/googleapis/java-pubsub/blob/eaeedd8bbe31cad3810687a29c5999f76876671d/google-cloud-pubsub/src/main/java/com/google/cloud/pubsub/v1/Publisher.java#L803-L804

@mmicatka friendly ping.


Old IE and Upload Function inside

Hi i've 2 question:

About old IE why not work? How can i make it working?
And is there a simples function to integrato for uploading file and send trough email? Using only html and jquery?
Thanks
Cris

If your issue is focused more on 'how do I do this?' rather than 'this is a broken functionality', then either ask on our Gitter or submit it to StackOverflow instead of GitHub, and make sure you add the sweetalert tag to the question.

See Contributing.md


Student course attendance overview

Ability to see a list of all the meetings for an offering so far and how a student attended those meetings

This would be a detail view for a specific student to get a better grasp of how they've been attending the course so far.
That way if someone is late, you can go and see if there is a pattern of being late


Azure Devops integrated with Permission Framework

Hey, I just made a Pull Request!
This PR solves the issue #22519

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@awanlin, I didn't integrate the Permission framework directly in the front-end using RequirePermission, instead the backend call responds with 403 and the front-end shows the EmptyState with Not authorized.
Potentially we can integrate the Front-End take to permission framework without azure-devops backend call and shows Not authorized.  When you have time feel free to start taking a look 👍

Hi @deepan10, just want to re-enforce that I really appreciate the work that you are doing and please don't take my reviews as being critical of your work. You are doing a great job! 🏆  I'm just terribly picky about DX and documentation.

@vinzscam can you give this another look, please? Good to go on my end!

Needs a rebase too :pray:

@awanlin @vinzscam @benjdlambert
No rush. Just want to check if anything pending from my end.

Looking at your branch here - https://github.com/deepan10/backstage/tree/azure-devops-permission - right now it's 192 commits behind. Can you update your fork and then rebase?

@awanlin
Rebase done.

Thanks :tada:

Thanks again for getting this done @deepan10 🚀
Thanks for the reviews @vinzscam and @benjdlambert 👍


Datetime-local is not taking seconds

Hi Team,
I am not sure whether its right or wrong but when I try input type datetime-local its not taking milliseconds, shows error this field required. Thanks.

Hi @vinaykhegde
Could create a stackblitz recreating the issue?
It will help us to investigate what might be causing it and whether there is a workaround for it.

Hi Team,
Here is the stackblitz.
https://clarity-light-theme-v012.stackblitz.io

The datetime-local requires setting AM or PM, which validates the field in your example. So I'm not sure what you're experiencing?

Also I just realized that datetime-local does not support seconds itself. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/datetime-local
I'm going to close as I suspect this is an implementation issue.


[WIP] Prelaunch Home

What does this PR do?
This PR does another refactor of the layout on top of the one done in #16, to adapt to the new home for prelaunch design. We still need to do some work on the layout to make it flexible enough to handle the other sections (@homer0 let's talk later about this).
Other than that, added the new elements and re-ordered already existing parts of the page to conform to the new design for the home.
How should it be tested manually?
Open the now deploy for this PR and compare against the design mentioned above.

@homer0 @asermax Let's hide the menu and deploy this so we can the party started :D


Add mapping sets required by Monarch KG

All biolink:PhenotypicFeature are aligned in uPheno (we should still add the sssom files here)

All anatomical entities are aligned in Uberon (+bridges) (we should still add the sssom files here)

All Diseases are aligned in Mondo (we should still add the sssom files here)

[ ] Disease Mappings

"Orphanet": 5078,# biolink:Disease?
"UMLS": 8353,# biolink:Disease?
"DOID": 4368,# biolink:Disease
MONDO
OMIM

[ ] Gene mappings

"biolink:Gene": {
     "ZFIN": 38059,
     "WB": 48773,
     "RGD": 51406,
     "SGD": 15292,
     "FB": 249446,
     "MGI": 76175,
     "HGNC": 22513,
     "POMBASE": 12818,
     "Xenbase": 50259
   },

[ ] Literature mappings?

      "biolink:Publication": {
        "PMID": 718683,
        "SGD": 526,
        "MGI": 8085,
        "ZFIN": 26533,
        "WB": 27457,
        "RGD": 304,
        "FB": 140315
      }

cc @kevinschaper

@kevinschaper can you add a list of all mappings we need for the Monarch KG?

Cross species anatomy (species specific to Uberon)
Disease (everything to Mondo)
Gene (the stuff you did in the genemappings repo I assume covers it)

What else? Do we need cross phenotype mappings for the Monarch KG, or is everything covered by uPheno in PHENIO?

Right now we're only doing the Mondo mapping for diseases and monarch-gene-mapping for genes.
I don't have a good sense of what the requirements are for anatomy or phenotype mapping, but I'm hoping that as we get the UI up and running against the new graph those kinds of things will get more visible and that'll drive changes.

Ok, whenever this issue comes up (anatomy/phenotype mappings), make sure to loop me in! Thank you!

sorry, i'm a little confused what the to-do here is?

You already finished it! Just close it with the words, its done!


Add tests for compact/readable representations

Ended up completing the compact/readable serde_test API so here are the
tests missing from https://github.com/rust-lang-nursery/uuid/pull/104.
I also replaced the serde_json roundtrip test with plain assert_tokens
tests which do essentially the same thing. I can re-add it if it seems
worthwhile to keep it though.

👍


Add repo.yml

Change-type: patch

@balena-ci retest

@balena-ci retest

@jviotti this should be set to type: node. It is not necessary however as node is the default type, you can simply drop the repo.yml here

@balena-ci retest


Poor performance casued by fancy-regex

While trying to make a rfm report with 40_000 objects it took 40+ secs to finish it.
After a little digging around found out fancy-regex was the perpetrator.
SOLUTION('s)?
1 - create them at runtime using lazy_static
2 - in some cases, it requires to be dynamic, so maybe create a function and use this to cache them
3 - a mix of 1 and 2
3 - Look for another crate that supports lookahead and lookbehind (most likely no one else)

Performance should be better on version 1.2.0


patch: Update test.yaml test matrix to include new versions of python

Updating test matrix

Looks like using the exact prerelease alpha version this was last tested on is not having a good time. Abandoning this in favour of wholesale updating poetry


Spotify Support?

Hi,
it's possible to integrate Spotify playlist or single song?
Kind regards.

dupes #155 #519

Not planned.


Chess: Move G4 to D1

Please do not change the title. Just click "Submit new issue". You don't need to do anything else :D

Bishop takes Queen

Bishop takes Queen


Wrong type after parse

Hi all!
I have written this schema:
export const createEmployeeAbsence = z
  .object({
    startDate: z.date(),
    endDate: z.date().optional(),
    employeeId: z.string(),
    absence: absenceReasons,
  })
    .superRefine((val, ctx) => {
      if (val.absence !== "LONGTERMSICK" && val.endDate === undefined) {
        return ctx.addIssue({
          code: z.ZodIssueCode.invalid_date,
          message: "Slutdato skal være udfyldt",
          path: ["endDate"],
        })
      }

    if (
      val.endDate &&
      isBefore(val.endDate, val.startDate) &&
      val.absence !== "LONGTERMSICK"
    ) {
      return ctx.addIssue({
        code: z.ZodIssueCode.invalid_date,
        message: "Slutdato skal være efter startdato",
        path: ["endDate"],
      })
    }
  })
  .transform((val) => {
    if (val.absence === "LONGTERMSICK") {
      return {
        ...val,
        endDate: generateUTC(new Date(2150, 0, 1)),
      }
    }

    return val
  })

I try to prompt the user to always provide an endDate unless absence of LONGTERMSICK is chosen, hence the first issue in the superrefine. If LONGTERMSICK is chosen, then I will transform the endDate to a date. So in every case, the endDate will be set.
When I try to parse the schema, the endDate type is set to Date | undefined.
I dont know if this is an bug or just me?
Thank you in advance! :)

your code example is missing some vars so I can't fully understand what is going on, but perhaps this would be helpful:
https://github.com/colinhacks/zod#discriminated-unions


bevy_reflect: Improve debug formatting for reflected types

Objective
Debugging reflected types can be somewhat frustrating since all dyn Reflect trait objects return something like Reflect(core::option::Option<alloc::string::String>).
It would be much nicer to be able to see the actual value— or even use a custom Debug implementation.
Solution
Added Reflect::debug which allows users to customize the debug output. It sets defaults for all ReflectRef subtraits and falls back to Reflect(type_name) if no Debug implementation was registered.
To register a custom Debug impl, users can add #[reflect(Debug)] like they can with other traits.
Example
Using the following structs:
#[derive(Reflect)]
pub struct Foo {
    a: usize,
    nested: Bar,
    #[reflect(ignore)]
    _ignored: NonReflectedValue,
}

#[derive(Reflect)]
pub struct Bar {
    value: Vec2,
    tuple_value: (i32, String),
    list_value: Vec<usize>,
    // We can't determine debug formatting for Option<T> yet
    unknown_value: Option<String>,
    custom_debug: CustomDebug
}

#[derive(Reflect)]
#[reflect(Debug)]
struct CustomDebug;

impl Debug for CustomDebug {
    fn fmt(&self, f: &mut Formatter<'_>) -> std::fmt::Result {
        write!(f, "This is a custom debug!")
    }
}

pub struct NonReflectedValue {
    _a: usize,
}

We can do:
let value = Foo {
  a: 1,
  _ignored: NonReflectedValue { _a: 10 },
  nested: Bar {
    value: Vec2::new(1.23, 3.21),
    tuple_value: (123, String::from("Hello")),
    list_value: vec![1, 2, 3],
    unknown_value: Some(String::from("World")),
    custom_debug: CustomDebug
  },
};
let reflected_value: &dyn Reflect = &value;
println!("{:#?}", reflected_value)

Which results in:
Foo {
  a: 2,
  nested: Bar {
    value: Vec2(
      1.23,
      3.21,
    ),
    tuple_value: (
      123,
      "Hello",
    ),
    list_value: [
      1,
      2,
      3,
    ],
    unknown_value: Reflect(core::option::Option<alloc::string::String>),
    custom_debug: This is a custom debug!,
  },
}

Notice that neither Foo nor Bar implement Debug, yet we can still deduce it. This might be a concern if we're worried about leaking internal values. If it is, we might want to consider a way to exclude fields (possibly with a #[reflect(hide)] macro) or make it purely opt in (as opposed to the default implementation automatically handled by ReflectRef subtraits).

Should we wrap the debug output with Reflect(...)? 🤔

Looks good! I think this'll be really convenient for debugging scripts.

Yeah it was really annoying not being able to debug reflected types well 😖
Also, @PROMETHIA-27 any thoughts on wrapping output with Reflect(...)? Still unsure if that's desired or not.

I think that's a good idea. Seems like it could very easily cause a very confusing situation trying to compare two seemingly equivalent things and not realizing that one is reflected, or something like that.
Though, if it causes heavy nesting of Reflect() (if there are structures being debugged that are reflected, and contain reflected things, and those contain more reflected things for example) then that could get noisy and problematic.
I would keep it for now; if it turns out to be largely just noise then it can be pretty trivially removed with a future PR.

hough, if it causes heavy nesting of Reflect() (if there are structures being debugged that are reflected, and contain reflected things, and those contain more reflected things for example) then that could get noisy and problematic.

Hm 🤔
Reflect(bevy_reflect::tests::should_reflect_debug::Test {
    value: 123,
    list: Reflect([
        "A",
        "B",
        "C",
    ]),
    array: Reflect([
        1.0,
        2.0,
        3.0,
    ]),
    map: Reflect({
        123: 1.23,
    }),
    a_struct: Reflect(bevy_reflect::tests::should_reflect_debug::SomeStruct {
        foo: "A Struct!",
    }),
    a_tuple_struct: Reflect(bevy_reflect::tests::should_reflect_debug::SomeTupleStruct(
        "A Tuple Struct!",
    )),
    custom: Cool debug!,
    unknown: Reflect(core::option::Option<alloc::string::String>),
})

It doesn't seem too bad. I think it's worth adding since we can just remove it pretty easily, like you said.

We could maybe make Reflect::debug() instead return &dyn Debug? Then the Debug impl for Reflect could be the one to add the Reflect(...) wrapper. This would result in only the top level struct/list/etc. being wrapped, while most other types contained are not wrapped (except for the "unknown" types). But this means that each type or other implementor will need to define their own debug type (e.g. StructDebug, ListDebug, etc.).
If anyone else has any other thoughts on this whole Reflect(...) formatting thing, that would be very helpful in deciding which path to take 😅

Definitely seems nice to have. Looks like there are some merge conflicts, though.

Conflicts resolved!

This is very nice; simple useful functionality implemented in the obvious way.

bors r+


Sc 1273 publish settings

Short summary
Adds the publish and preview buttons.

I'm going to close this but not merge it in as most of this was covered by the PR for sc-1174.
The branch I'm going to keep alive as I want to refactor how the form implemented to how it is done here.


Updated: mumble 1.3.0

Newer version of mumble (1.3.1) is now available in master. 993a0f7988c450901e0e541dd197bd43e8138bc5


[WIP] Add filtering prop tables by excluding or including

closes Issue: #159
Hi, first I'm really sorry for being late on this new feature. I've been pretty ok before I said I would take this feature, but as soon as I take it I've got a lot of tasks from my work(magically) I'll try to be as responsive as possible, but I predict my heavy workload goes until next 1 or 2 weeks,
Basically, I've implemented as we talked at #159. I chose putting actual React components instead of string of React component names because something like
import WhateverNameFromDefault from "./DefaultButton";
import { ExplicitButton as AnotherButton} from "./ExplicitButton";

would not work with string of names. However if actual React component is used, its displayName and name can be tracked to its real value.
Please take a look and give me some feedbacks. Aside from code reviews, I think more can be added after the main logic is acceptable(adding more examples, Docs, examples on Vue etc...)

LGFM
Let's merge it?

LGFM
Let's merge it?

That sounds good. I will add more docs and examples little bit later

@lonyele released at 5.0.4-alpha.2+6bd5f8d

I tried using both includePropTables  and excludePropTables, but it seems includePropTables being ignore. But if I use example-react in master branch, the one that being ignored is excludePropTables @lonyele @tuchk4

storybook-readme: 5.0.4-alpha.2

@archansel hm... what you are saying is that example-react at master branch is working fine but it is not working at your project? Can you give me more information?

At your project, can you see any of console.warn(...) messages such as storybook-readme: excludePropTables is not an array. It must be an ' ...
If you can't see any of these storybook-readme warning messages, I found that storybook itself can be sometimes flaky, so would you restart storybook again and see the same thing happens again?

If none of the above works, then can you show me the code where you use excludePropTables and includePropTables and the story where you used these feature.

Both (master branch and my project) gave incorrect behavior
Master Branch
Steps:

Clone repo
npm install && npm run storybook in example-react directory
Goto PropsTable stories, the Exclude globally story shows INCORRECT behavior. Even the readme says You can notice from below that the component is showing but propTable is not showing eventhough <!-- PROPS --> is specified., the props table still showing up

I don't know whether Include locally gave a correct result or not because the props table not excluded globally
My Project
This is my story
import React, { useState } from 'react';
import { storiesOf } from '@storybook/react';

import { CheckboxInput } from '../index';
import CheckboxInputReadme from './CheckboxInput.readme.md';

/* eslint-disable react/prop-types */
const value = [{ value: 'option-2', label: 'My Option #2' }];
const options = [{ value: 'option-1', label: 'My Option #1' }, { value: 'option-2', label: 'My Option #2' }, { value: 'option-3', label: 'My Option #3' }];
const StoryComponent = ({ value: propValue, onChange: propOnChange, ...props }) => {
  const [currentValue, setCurrentValue] = useState(propValue);
  const onChange = values => {
    setCurrentValue(values);
    if (propOnChange) propOnChange(values);
  };
  return <CheckboxInput value={currentValue} onChange={onChange} {...props} />;
};

storiesOf('Forms|Input.CheckboxInput', module)
  .addParameters({
    readme: {
      sidebar: CheckboxInputReadme,
    },
  })
  .add('Default', () => <StoryComponent name="my-options" value={value} options={options} />)
  .add('With Disabled State', () => <CheckboxInput name="my-options" value={value} options={options} disabled />);

It has two stories Default and With Disabled State, my goal is to include CheckboxInput props table in all of my stories for the current context Forms|Input.CheckboxInput. So I added includePropTables in addParameters
.addParameters({
    readme: {
      sidebar: CheckboxInputReadme,
      includePropTables: [CheckboxInput],
    },
  })

Originally, the Default story doesn't show any props table and the With Disabled State story shows CheckboxInput props table. Now, even using includePropTables: [CheckboxInput] option, the Default story still doesn't have props table from CheckboxInput. In the other hand, if I put excludePropTables: [CheckboxInput] in option, both Default and With Disabled State don't have CheckboxInput props table. Am I doing it wrong?
So, as you can see (I hope its clearer now), in master branch, the incorrect behavior is excludePropTables but in my project the incorrect behavior is includePropTables
PS: No warning in the console

@archansel  hm... first I tested this official repo's exmple-react on windows 10(chrome, firefox) and ubuntu 18.04(chrome, firefox) both cloning this repo and make up fresh CRA project with storybook-readme setting. From my laptop, everything works fine(I can't reproduce your case)
@tuchk4 would you try reproduce this behaviour? or I'd like to see if anyone seeing this problem too.(yes! you... now reading this comment)
My guesses are that

Originally, the Default story doesn't show any props table

-> This part is the problem of general propTables feature, not filteringPropTables feature. Though, I think I can investigate and make it better.

Now, even using includePropTables: [CheckboxInput] option, the Default story still doesn't have props table from CheckboxInput

-> This part is the same problem as above. From the beginning it is not showing the propTables, thus with includePropTables, it is still not showing anything.

In the other hand, if I put excludePropTables: [CheckboxInput] in option, both Default and With Disabled State don't have CheckboxInput props table. Am I doing it wrong?

-> This is a correct behaviour. Default's propTable is not showing because of above reason(propTables problem) With Disabled State's propTable is not showing because of excludePropTables
I have made some examples here(also covers your case) https://github.com/lonyele/storybook-readme-filtering-proptables-example
you can just

git clone https://github.com/lonyele/storybook-readme-filtering-proptables-example
yarn or npm install
yarn storybook or npm run storybook
I would investigate the propTables feature(I have some guess) while can you check my repo's example and see if it is working or not.

btw I may not be that responsive, it's still a weekday, so I don't have much time

I know the problem here, master by "default" still using version 5.0.3, after updating the version to 5.0.4-alpha.2, the example works perfectlly https://github.com/tuchk4/storybook-readme/blob/11d76cad634f07f6fcc6475ae904d6982be984f9/packages/example-react/package.json#L36
I think I got a better understanding of this feature. I thought includePropTables add ADDITIONAL props table (as the name implied) even if the component not in the story itself. It seems just an example without the docs still make some people (at least me) got confused 😄

This part is the problem of general propTables feature

as for general propTables issue, is there any specific issue that I can follow to get the update?

@archansel hm... maybe... It was working fine for me. I maybe wrong but other examples(example-react etc) on this repo is linked directly to storybook-readme folder using lerna/workspace so always with the latest version I guess.
Anyway, If it's not a bug then It sounds good to me. I should probably finish additional things(more examples, docs) this weekend
About the propTables issue, I don't even know If it is a but since current behaviour can be an intended outcome. However, I'll also investigate that on this weekend.
sorry for the confusion and I'll make explanation and usage more clear soon

It's a wrap then 😄
Nice additional feature, by the way. Looking forward to the stable release


SDL: Call multiplayer->update() from the user code thread

The multiplayer update scans for messages and passes them in to the
user defined function on_message(). This should be done in the user
code thread for two reasons:

Calling it from a different thread means on_message() and update()
are being run in different threads, and therefore all code in both of
them has to be thread safe. This is pretty hard to do with the 32blit
API and not really in the spirit of what this is supposed to be.

on_message() is a user-supplied function and so bugs can make it
hang. We can detect hangs in update() and render() thanks to running
them on the user thread (via blit::tick()). Running on_message() on
that thread allows to detect hangs there too.

This didn't actually fix the problems I'm seeing with multiplayer.
Also it will lock the SDL framerate to 50 fps. I'm not sure if calling render outside the user thread does any better job there though.

Multiplayer does seem to be completely solid after this change, but I'm not totally sure this is the reason, or if it is just because I fixed all the bugs in my code. On the other hand I have not noticed anything behaving worse with this change, and it is technically the right thing to do. The idea behind the thread is that any code written by the user (init, update, render, on_message) can potentially go into an infinite loop and we want to detect it. So for that reason it is (supposed to) all run on the user thread.


TabularMDP-v0 : data type not understood

I tried to use your TabularMDP-v0, but got an error: data type not understood
Thanks for your help!

Thank you very much for the notice! It was a typo in TabularMDPEnv.


Android installation fails

Is this a bug report?
Yes

Have you read the Installation Instructions?
Yes
Environment
"@react-native-community/async-storage": "^1.3.3",
"i18n-js": "^3.2.1",
"react": "16.8.3",
"react-native": "0.59.4",
"react-native-device-info": "^1.5.0",
"react-native-elements": "^1.1.0",
"react-native-gesture-handler": "^1.1.0",
"react-native-maps": "^0.24.2",
"react-native-settings-list": "^1.8.0",
"react-native-vector-icons": "^6.4.2",
"react-navigation": "^3.8.1",
"react-redux": "^5.0.6",
"redux": "^3.7.2",
"redux-thunk": "^2.2.0"

Target Platform: Android 9.0/Nexus 5X

Steps to Reproduce

yarn install
react-native start
react-native run-android

Expected Behavior

Application load normally
Actual Behavior

Got error after followings steps from installation instruction

Reproducible Demo

https://github.com/Darkiman/react-native-app/tree/maps

You forgot to install the modules correctly, In this case is not the map module but the i18n.
(Check you imported the packages and then call them in MainAplication.java )

We're experiencing this same issue in our project. We tried a project branch without react-native-maps and the project loads ok on the Android emulator, but after installing react-native-maps we get this error:

package.json
"dependencies": {
    "babel-preset-react-native": "^4.0.1",
    "i18n-js": "^3.2.1",
    "immutable": "^4.0.0-rc.12",
    "moment": "^2.24.0",
    "react": "16.8.3",
    "react-native": "0.59.4",
    "react-native-device-info": "^0.26.1",
    "react-native-elements": "^1.0.0",
    "react-native-gesture-handler": "^1.1.0",
    "react-native-keyboard-aware-scroll-view": "^0.8.0",
    "react-native-localize": "^1.1.2",
    "react-native-maps": "0.24.2",
    "react-native-sqlite-storage": "3.3.9",
    "react-native-vector-icons": "^6.2.0",
    "react-navigation": "^3.2.1",
    "sinon": "^7.3.1",
    "styled-components": "^4.2.0"
  }

Android SDK tools

Android SDK platforms

We also updated react-native-languages to react-native-localize just in case, but the error keeps appearing, and as we commented before, before installing react-native-maps, the project loaded ok, so we think this is unrelated. On iOS, the maps work ok.

You forgot to install the modules correctly, In this case is not the map module but the i18n.
(Check you imported the packages and then call them in MainAplication.java )

It works fine unitll adding
        googlePlayServicesVersion = "11.8.0"
        androidMapsUtilsVersion = "0.5+"

and full file looks like:
// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {
    ext {
        buildToolsVersion = "28.0.3"
        minSdkVersion = 16
        compileSdkVersion = 28
        targetSdkVersion = 28
        supportLibVersion = "28.0.0"
        googlePlayServicesVersion = "11.8.0"
        androidMapsUtilsVersion = "0.5+"
    }
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.3.1'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        mavenLocal()
        google()
        jcenter()
        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url "$rootDir/../node_modules/react-native/android"
        }
    }
}

Maps on ios working fine

@Darkiman  try googlePlayServicesVersion = "16.1.0" and if it works maybe you can make a PR to update the docs 😊

@Darkiman try googlePlayServicesVersion = "16.1.0" and if it works maybe you can make a PR to update the docs 😊

Thanks 👍
Now it works
But I got second error

Google play Service installed

And emulator has Play Store

@Darkiman https://github.com/react-native-community/react-native-maps/issues/2778

fixed by this

@Darkiman try googlePlayServicesVersion = "16.1.0" and if it works maybe you can make a PR to update the docs

This worked for our project too :+1: . Then we experienced the same problem with Google Play Services and some one more related with the android build.gradle tools and sdk versions, which we finally solved, thanks :)


[WIP][SPARK-41990][SQL] Fix bug for FieldReference

What changes were proposed in this pull request?
The pr aims to fix bug for FieldReference.
Why are the changes needed?
Bug fix

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Manual test result as follow:

cc @huaxingao @cloud-fan

Can one of the admins verify this patch?

@huaxingao I think the v1 filter to v2 translation has a bug
case class IsNotNull(attribute: String) extends Filter {
  override def references: Array[String] = Array(attribute)
  override def toV2: Predicate = new Predicate("IS_NOT_NULL", Array(FieldReference(attribute)))
}

The attribute can either be the parsed name (no quoting) if nested filter is disabled, or a SQL name otherwise. But FieldReference.apply only accepts SQL name.


[Bug] TC recovery takes too much time

Search before asking

[X] I searched in the issues and found nothing similar.

Version
branch-2.9
master
Minimal reproduce step
This is a issue need to be tracked from comment https://github.com/apache/pulsar/pull/18936.
What did you expect to see?
ThresholdShedder won't affect TC recovery too much time.
What did you see instead?
TC recovery too much time.
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

I will submit a PR to fix it.


Should specify this is using the "docker run" command

File: config/containers/container-networking.md
For people really familiar with docker, this might be obvious, but for those just learning how docker works, the "-p" options should be specified as "docker run -p" to prevent possible confusion for those of us who are new to the whole docker thing.
Thanks!

Thanks!

Thanks for reporting!


GPU use in custom MLServer runtime

I have deployed the PyTorch model using custom MLServer runtime on the CPU and making gRPC inference requests. As our payload is vast, we need to speed up the inferencing process, so we are looking forward to using GPU. Can you please suggest the most efficient ways to use GPU on ModelMesh for custom MLServer runtime? Is there any document or resource available to know how to use GPU on ModelMesh?
@njhill @lizzzcai

Hi @MLHafizur , I haven't started any testing on GPU node yet, will be happy to see some benchmark results as well.
I think if your cluster has GPU nodes, you should be able to use the GPU resources in your servingruntime like this. However, to enable GPU nodes in your cluster, you probably need to find some tutorials, like this if you are using gcp or this for self-host cluster.


is-promise error with ng update

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[x] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
It's a regression in the underlying lib or rather angular didn't catch up with changes with the underlying lib.
Description
 A clear and concise description of the problem...
ng update fails because of npm package is-promise had an update and probably the update command didn't take versioning into consideration.
🔬 Minimal Reproduction

have an angular 8 project
try upgrading with ng update

🔥 Exception or Error

ng update
Your global Angular CLI version (9.1.3) is greater than your local
version (8.3.20). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
The installed Angular CLI version is older than the latest stable version.
Installing a temporary version to perform the update.
Installing packages for tooling via npm.
Installed packages for tooling via npm.
Unknown error: Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /tmp/.ng-temp-packages-l4NeIR/node_modules/is-promise/index.js
require() of ES modules is not supported.
require() of /tmp/.ng-temp-packages-l4NeIR/node_modules/is-promise/index.js from /tmp/.ng-temp-packages-l4NeIR/node_modules/run-async/index.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename /tmp/.ng-temp-packages-l4NeIR/node_modules/is-promise/index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /tmp/.ng-temp-packages-l4NeIR/node_modules/is-promise/package.json.

🌍 Your Environment

Angular CLI: 8.3.20
Node: 12.16.1
OS: linux x64
Angular: 8.2.14
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.803.20
@angular-devkit/build-angular     0.803.20
@angular-devkit/build-optimizer   0.803.20
@angular-devkit/build-webpack     0.803.20
@angular-devkit/core              8.3.20
@angular-devkit/schematics        8.3.20
@angular/cdk                      8.2.3
@angular/cli                      8.3.20
@angular/flex-layout              8.0.0-beta.27
@angular/material                 8.2.3
@ngtools/webpack                  8.3.20
@schematics/angular               8.3.20
@schematics/update                0.803.20
rxjs                              6.4.0
typescript                        3.5.3
webpack                           4.39.2

Anything else relevant?

https://github.com/then/is-promise/issues/18
or rather
https://github.com/then/is-promise/issues/12
PR in is-promise
https://github.com/then/is-promise/pull/15
It will probably resolve itself but version pinning in ng update should be desirable

broken here as well, uninstalled and reinstalled npm, node, angular cli, vscode - all with no success

broken here as well, ng is simply dead, but am (and was) on Angular 9.1.2. First could not update to @angular/cli 9.1.3 (due this error), and then ng rendered unusable as I installed<EMAIL_ADDRESS>``
cstamas@Albert ~/Worx/matesze/search01  (master *)$ node -v
v14.0.0
cstamas@Albert ~/Worx/matesze/search01  (master *)$ npm -v
6.14.4
cstamas@Albert ~/Worx/matesze/search01  (master *)$ npm ls -g --depth 0
/home/linuxbrew/.linuxbrew/lib
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>cstamas@Albert ~/Worx/matesze/search01  (master *)$ npm ls --depth 0
<EMAIL_ADDRESS>/home/cstamas/Worx/matesze/search01
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>cstamas@Albert ~/Worx/matesze/search01  (master *)$ ng version
Unknown error: Error [ERR_INVALID_PACKAGE_TARGET]: Invalid "exports" main target "index.js" defined in the package config<EMAIL_ADDRESS>cstamas@Albert ~/Worx/matesze/search01  (master *)$

This seems related to node, as I used (wrongly) Linuxbrew so far, and it pushed me to 14.0.0. Will downgrade node to 13.x and try again.

Nope, am wrong. After downgrading to Node 13.3.0, same error:
cstamas@Albert ~/Worx/matesze/search01  (master *)$ nvm ls
->     v13.13.0
         system
default -> 13 (-> v13.13.0)
node -> stable (-> v13.13.0) (default)
stable -> 13.13 (-> v13.13.0) (default)
iojs -> N/A (default)
unstable -> N/A (default)
lts/* -> lts/erbium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.20.1 (-> N/A)
lts/erbium -> v12.16.2 (-> N/A)
cstamas@Albert ~/Worx/matesze/search01  (master *)$ node -v
v13.13.0
cstamas@Albert ~/Worx/matesze/search01  (master *)$ npm -v
6.14.4
cstamas@Albert ~/Worx/matesze/search01  (master *)$ npm ls -g --depth 0
/home/cstamas/.nvm/versions/node/v13.13.0/lib
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
cstamas@Albert ~/Worx/matesze/search01  (master *)$ ng version
Unknown error: Error [ERR_INVALID_PACKAGE_TARGET]: Invalid "exports" main target "index.js" defined in the package config<EMAIL_ADDRESS>cstamas@Albert ~/Worx/matesze/search01  (master *)$

Issue now resolved

is-promise just a released 2.2.1, that should solve this issue.

Comfirmed, ng CLI is back now. Tx

The take away from this is, version pinning.

The Angular CLI currently pins direct dependencies.  However, transitive dependencies are out of the control of the main package (the CLI in this case).  This is a fundamental limitation of the node package ecosystem.
There is also the semver element to this situation.  In that, there is intended to be a guarantee that minor and patch versions do not introduce breaking changes.  However, this requires cooperation from all parties and mistakes sometimes do happen.


Improve ARIMA correction

The performance and speed of ARIMA correction might be improved by limiting the window of piecewise model development to 2-6 times the length of the gap.

Make this use one parameter that limits the forecasting and backcasting data to x number of days to build the model from.


doesn't install

Seems promising but I got multiple errors for gyp and node-pre-gyp and install failed, 2 times.
Pasting all because errors are at different places and to help others.
npm i node-red-contrib-onesignal

><EMAIL_ADDRESS>install /home/user/.node-red/node_modules/bcrypt
> node-gyp rebuild

gyp WARN EACCES user "user" does not have permission to access the dev dir "/home/user/.node-gyp/6.10.3"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
make: Entering directory '/home/user/.node-red/node_modules/bcrypt/build'
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
In file included from ../../nan/nan.h:184:0,
                 from ../src/bcrypt_node.cc:1:
../../nan/nan_maybe_43_inl.h: In function ‘Nan::MaybeLocal<v8::Object> Nan::CloneElementAt(v8::Local<v8::Array>, uint32_t)’:
../../nan/nan_maybe_43_inl.h:221:58: warning: ‘v8::MaybeLocal<v8::Object> v8::Array::CloneElementAt(v8::Local<v8::Context>, uint32_t)’ is deprecated: Cloning is not supported. [-Wdeprecated-declarations]
   return array->CloneElementAt(GetCurrentContext(), index);
                                                          ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from /tmp/.node-gyp/6.10.3/include/node/node.h:42,
                 from ../../nan/nan.h:24,
                 from ../src/bcrypt_node.cc:1:
/tmp/.node-gyp/6.10.3/include/node/v8.h:3032:36: note: declared here
                 MaybeLocal<Object> CloneElementAt(Local<Context> context,
                                    ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
In file included from ../../nan/nan_new.h:189:0,
                 from ../../nan/nan.h:190,
                 from ../src/bcrypt_node.cc:1:
../../nan/nan_implementation_12_inl.h: In static member function ‘static Nan::imp::FactoryBase<v8::BooleanObject>::return_t Nan::imp::Factory<v8::BooleanObject>::New(bool)’:
../../nan/nan_implementation_12_inl.h:40:38: warning: ‘static v8::Local<v8::Value> v8::BooleanObject::New(bool)’ is deprecated: Pass an isolate [-Wdeprecated-declarations]
   return v8::BooleanObject::New(value).As<v8::BooleanObject>();
                                      ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from /tmp/.node-gyp/6.10.3/include/node/node.h:42,
                 from ../../nan/nan.h:24,
                 from ../src/bcrypt_node.cc:1:
/tmp/.node-gyp/6.10.3/include/node/v8.h:4008:56: note: declared here
   V8_DEPRECATED("Pass an isolate", static Local<Value> New(bool value));
                                                        ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
In file included from ../src/bcrypt_node.cc:1:0:
../../nan/nan.h: At global scope:
../../nan/nan.h:592:20: error: variable or field ‘AddGCEpilogueCallback’ declared void
       v8::Isolate::GCEpilogueCallback callback
                    ^
../../nan/nan.h:592:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCEpilogueCallback callback
       ^
../../nan/nan.h:593:18: error: expected primary-expression before ‘gc_type_filter’
     , v8::GCType gc_type_filter = v8::kGCTypeAll) {
                  ^
../../nan/nan.h:598:20: error: variable or field ‘RemoveGCEpilogueCallback’ declared void
       v8::Isolate::GCEpilogueCallback callback) {
                    ^
../../nan/nan.h:598:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCEpilogueCallback callback) {
       ^
../../nan/nan.h:603:20: error: variable or field ‘AddGCPrologueCallback’ declared void
       v8::Isolate::GCPrologueCallback callback
                    ^
../../nan/nan.h:603:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCPrologueCallback callback
       ^
../../nan/nan.h:604:18: error: expected primary-expression before ‘gc_type_filter’
     , v8::GCType gc_type_filter = v8::kGCTypeAll) {
                  ^
../../nan/nan.h:609:20: error: variable or field ‘RemoveGCPrologueCallback’ declared void
       v8::Isolate::GCPrologueCallback callback) {
                    ^
../../nan/nan.h:609:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCPrologueCallback callback) {
       ^
../../nan/nan.h: In function ‘bool Nan::SetAccessor(v8::Local<v8::Object>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’:
../../nan/nan.h:1939:16: warning: ‘bool v8::Object::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     , attribute);
                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from /tmp/.node-gyp/6.10.3/include/node/node.h:42,
                 from ../../nan/nan.h:24,
                 from ../src/bcrypt_node.cc:1:
/tmp/.node-gyp/6.10.3/include/node/v8.h:2751:22: note: declared here
                 bool SetAccessor(Local<Name> name,
                      ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
bcrypt_lib.target.mk:96: recipe for target 'Release/obj.target/bcrypt_lib/src/bcrypt_node.o' failed
make: *** [Release/obj.target/bcrypt_lib/src/bcrypt_node.o] Error 1
make: Leaving directory '/home/user/.node-red/node_modules/bcrypt/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.4.0-72-generic
gyp ERR! command "/usr/bin/nodejs" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/user/.node-red/node_modules/bcrypt
gyp ERR! node -v v6.10.3
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

><EMAIL_ADDRESS>install /home/user/.node-red/node_modules/bufferutil
> node-gyp rebuild

gyp WARN EACCES user "user" does not have permission to access the dev dir "/home/user/.node-gyp/6.10.3"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
make: Entering directory '/home/user/.node-red/node_modules/bufferutil/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
In file included from ../../nan/nan.h:184:0,
                 from ../src/bufferutil.cc:16:
../../nan/nan_maybe_43_inl.h: In function ‘Nan::MaybeLocal<v8::Object> Nan::CloneElementAt(v8::Local<v8::Array>, uint32_t)’:
../../nan/nan_maybe_43_inl.h:221:58: warning: ‘v8::MaybeLocal<v8::Object> v8::Array::CloneElementAt(v8::Local<v8::Context>, uint32_t)’ is deprecated: Cloning is not supported. [-Wdeprecated-declarations]
   return array->CloneElementAt(GetCurrentContext(), index);
                                                          ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from ../src/bufferutil.cc:7:
/tmp/.node-gyp/6.10.3/include/node/v8.h:3032:36: note: declared here
                 MaybeLocal<Object> CloneElementAt(Local<Context> context,
                                    ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
In file included from ../../nan/nan_new.h:189:0,
                 from ../../nan/nan.h:190,
                 from ../src/bufferutil.cc:16:
../../nan/nan_implementation_12_inl.h: In static member function ‘static Nan::imp::FactoryBase<v8::BooleanObject>::return_t Nan::imp::Factory<v8::BooleanObject>::New(bool)’:
../../nan/nan_implementation_12_inl.h:40:38: warning: ‘static v8::Local<v8::Value> v8::BooleanObject::New(bool)’ is deprecated: Pass an isolate [-Wdeprecated-declarations]
   return v8::BooleanObject::New(value).As<v8::BooleanObject>();
                                      ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from ../src/bufferutil.cc:7:
/tmp/.node-gyp/6.10.3/include/node/v8.h:4008:56: note: declared here
   V8_DEPRECATED("Pass an isolate", static Local<Value> New(bool value));
                                                        ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
In file included from ../src/bufferutil.cc:16:0:
../../nan/nan.h: At global scope:
../../nan/nan.h:592:20: error: variable or field ‘AddGCEpilogueCallback’ declared void
       v8::Isolate::GCEpilogueCallback callback
                    ^
../../nan/nan.h:592:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCEpilogueCallback callback
       ^
../../nan/nan.h:593:18: error: expected primary-expression before ‘gc_type_filter’
     , v8::GCType gc_type_filter = v8::kGCTypeAll) {
                  ^
../../nan/nan.h:598:20: error: variable or field ‘RemoveGCEpilogueCallback’ declared void
       v8::Isolate::GCEpilogueCallback callback) {
                    ^
../../nan/nan.h:598:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCEpilogueCallback callback) {
       ^
../../nan/nan.h:603:20: error: variable or field ‘AddGCPrologueCallback’ declared void
       v8::Isolate::GCPrologueCallback callback
                    ^
../../nan/nan.h:603:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCPrologueCallback callback
       ^
../../nan/nan.h:604:18: error: expected primary-expression before ‘gc_type_filter’
     , v8::GCType gc_type_filter = v8::kGCTypeAll) {
                  ^
../../nan/nan.h:609:20: error: variable or field ‘RemoveGCPrologueCallback’ declared void
       v8::Isolate::GCPrologueCallback callback) {
                    ^
../../nan/nan.h:609:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCPrologueCallback callback) {
       ^
../../nan/nan.h: In function ‘bool Nan::SetAccessor(v8::Local<v8::Object>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’:
../../nan/nan.h:1939:16: warning: ‘bool v8::Object::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     , attribute);
                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from ../src/bufferutil.cc:7:
/tmp/.node-gyp/6.10.3/include/node/v8.h:2751:22: note: declared here
                 bool SetAccessor(Local<Name> name,
                      ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
bufferutil.target.mk:95: recipe for target 'Release/obj.target/bufferutil/src/bufferutil.o' failed
make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Error 1
make: Leaving directory '/home/user/.node-red/node_modules/bufferutil/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.4.0-72-generic
gyp ERR! command "/usr/bin/nodejs" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/user/.node-red/node_modules/bufferutil
gyp ERR! node -v v6.10.3
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

><EMAIL_ADDRESS>install /home/user/.node-red/node_modules/serialport
> node-pre-gyp install --fallback-to-build

gyp WARN EACCES user "user" does not have permission to access the dev dir "/home/user/.node-gyp/6.10.3"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/tmp/.node-gyp"
make: Entering directory '/home/user/.node-red/node_modules/serialport/build'
  CXX(target) Release/obj.target/serialport/src/serialport.o
In file included from ../../nan/nan.h:184:0,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
../../nan/nan_maybe_43_inl.h: In function ‘Nan::MaybeLocal<v8::Object> Nan::CloneElementAt(v8::Local<v8::Array>, uint32_t)’:
../../nan/nan_maybe_43_inl.h:221:58: warning: ‘v8::MaybeLocal<v8::Object> v8::Array::CloneElementAt(v8::Local<v8::Context>, uint32_t)’ is deprecated: Cloning is not supported. [-Wdeprecated-declarations]
   return array->CloneElementAt(GetCurrentContext(), index);
                                                          ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from /tmp/.node-gyp/6.10.3/include/node/node.h:42,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:3032:36: note: declared here
                 MaybeLocal<Object> CloneElementAt(Local<Context> context,
                                    ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
In file included from ../../nan/nan_new.h:189:0,
                 from ../../nan/nan.h:190,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
../../nan/nan_implementation_12_inl.h: In static member function ‘static Nan::imp::FactoryBase<v8::BooleanObject>::return_t Nan::imp::Factory<v8::BooleanObject>::New(bool)’:
../../nan/nan_implementation_12_inl.h:40:38: warning: ‘static v8::Local<v8::Value> v8::BooleanObject::New(bool)’ is deprecated: Pass an isolate [-Wdeprecated-declarations]
   return v8::BooleanObject::New(value).As<v8::BooleanObject>();
                                      ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from /tmp/.node-gyp/6.10.3/include/node/node.h:42,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:4008:56: note: declared here
   V8_DEPRECATED("Pass an isolate", static Local<Value> New(bool value));
                                                        ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
In file included from ../src/serialport.h:5:0,
                 from ../src/serialport.cpp:3:
../../nan/nan.h: At global scope:
../../nan/nan.h:592:20: error: variable or field ‘AddGCEpilogueCallback’ declared void
       v8::Isolate::GCEpilogueCallback callback
                    ^
../../nan/nan.h:592:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCEpilogueCallback callback
       ^
../../nan/nan.h:593:18: error: expected primary-expression before ‘gc_type_filter’
     , v8::GCType gc_type_filter = v8::kGCTypeAll) {
                  ^
../../nan/nan.h:598:20: error: variable or field ‘RemoveGCEpilogueCallback’ declared void
       v8::Isolate::GCEpilogueCallback callback) {
                    ^
../../nan/nan.h:598:7: error: ‘GCEpilogueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCEpilogueCallback callback) {
       ^
../../nan/nan.h:603:20: error: variable or field ‘AddGCPrologueCallback’ declared void
       v8::Isolate::GCPrologueCallback callback
                    ^
../../nan/nan.h:603:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCPrologueCallback callback
       ^
../../nan/nan.h:604:18: error: expected primary-expression before ‘gc_type_filter’
     , v8::GCType gc_type_filter = v8::kGCTypeAll) {
                  ^
../../nan/nan.h:609:20: error: variable or field ‘RemoveGCPrologueCallback’ declared void
       v8::Isolate::GCPrologueCallback callback) {
                    ^
../../nan/nan.h:609:7: error: ‘GCPrologueCallback’ is not a member of ‘v8::Isolate’
       v8::Isolate::GCPrologueCallback callback) {
       ^
../../nan/nan.h: In function ‘bool Nan::SetAccessor(v8::Local<v8::Object>, v8::Local<v8::String>, Nan::GetterCallback, Nan::SetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’:
../../nan/nan.h:1939:16: warning: ‘bool v8::Object::SetAccessor(v8::Local<v8::Name>, v8::AccessorNameGetterCallback, v8::AccessorNameSetterCallback, v8::Local<v8::Value>, v8::AccessControl, v8::PropertyAttribute)’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     , attribute);
                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/v8.h:25:0,
                 from /tmp/.node-gyp/6.10.3/include/node/node.h:42,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:2751:22: note: declared here
                 bool SetAccessor(Local<Name> name,
                      ^
/tmp/.node-gyp/6.10.3/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:115:116: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   baton->baudRate = Nan::Get(options, Nan::New<v8::String>("baudRate").ToLocalChecked()).ToLocalChecked()->ToInt32()->Int32Value(
                                                                                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp:116:116: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   baton->dataBits = Nan::Get(options, Nan::New<v8::String>("dataBits").ToLocalChecked()).ToLocalChecked()->ToInt32()->Int32Value(
                                                                                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp:117:120: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
  baton->bufferSize = Nan::Get(options, Nan::New<v8::String>("bufferSize").ToLocalChecked()).ToLocalChecked()->ToInt32()->Int32Val
                                                                                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp:119:131: warning: ‘v8::Local<v8::Number> v8::Value::ToNumber() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 pBits = ToStopBitEnum(Nan::Get(options, Nan::New<v8::String>("stopBits").ToLocalChecked()).ToLocalChecked()->ToNumber()->NumberVa
                                                                                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8166:15: note: declared here
 Local<Number> Value::ToNumber() const {
               ^
../src/serialport.cpp: In function ‘void EIO_AfterOpen(uv_work_t*)’:
../src/serialport.cpp:159:31: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     int fd = argv[1]->ToInt32()->Int32Value();
                               ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:180:29: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   int fd = info[0]->ToInt32()->Int32Value();
                             ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp:199:116: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   baton->baudRate = Nan::Get(options, Nan::New<v8::String>("baudRate").ToLocalChecked()).ToLocalChecked()->ToInt32()->Int32Value(
                                                                                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp:200:116: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   baton->dataBits = Nan::Get(options, Nan::New<v8::String>("dataBits").ToLocalChecked()).ToLocalChecked()->ToInt32()->Int32Value(
                                                                                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp:201:120: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
  baton->bufferSize = Nan::Get(options, Nan::New<v8::String>("bufferSize").ToLocalChecked()).ToLocalChecked()->ToInt32()->Int32Val
                                                                                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp:203:131: warning: ‘v8::Local<v8::Number> v8::Value::ToNumber() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
 pBits = ToStopBitEnum(Nan::Get(options, Nan::New<v8::String>("stopBits").ToLocalChecked()).ToLocalChecked()->ToNumber()->NumberVa
                                                                                ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8166:15: note: declared here
 Local<Number> Value::ToNumber() const {
               ^
../src/serialport.cpp: In function ‘void EIO_AfterUpdate(uv_work_t*)’:
../src/serialport.cpp:242:31: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     int fd = argv[1]->ToInt32()->Int32Value();
                               ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Write(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:263:29: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   int fd = info[0]->ToInt32()->Int32Value();
                             ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:374:29: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   int fd = info[0]->ToInt32()->Int32Value();
                             ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:493:29: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   int fd = info[0]->ToInt32()->Int32Value();
                             ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:542:29: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   int fd = info[0]->ToInt32()->Int32Value();
                             ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
../src/serialport.cpp:603:29: warning: ‘v8::Local<v8::Int32> v8::Value::ToInt32() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
   int fd = info[0]->ToInt32()->Int32Value();
                             ^
In file included from /tmp/.node-gyp/6.10.3/include/node/node.h:42:0,
                 from ../../nan/nan.h:24,
                 from ../src/serialport.h:5,
                 from ../src/serialport.cpp:3:
/tmp/.node-gyp/6.10.3/include/node/v8.h:8202:14: note: declared here
 Local<Int32> Value::ToInt32() const {
              ^
serialport.target.mk:96: recipe for target 'Release/obj.target/serialport/src/serialport.o' failed
make: *** [Release/obj.target/serialport/src/serialport.o] Error 1
make: Leaving directory '/home/user/.node-red/node_modules/serialport/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/user/.node-red/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Linux 4.4.0-72-generic
gyp ERR! command "/usr/bin/nodejs" "/home/user/.node-red/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/home/user/.node-red/node_modules/serialport/build/Release/node-v48-linux-x64/serialport.node" "--module_name=serialport" "--module_path=/home/user/.node-red/node_modules/serialport/build/Release/node-v48-linux-x64"
gyp ERR! cwd /home/user/.node-red/node_modules/serialport
gyp ERR! node -v v6.10.3
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/nodejs /home/user/.node-red/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/user/.node-red/node_modules/serialport/build/Release/node-v48-linux-x64/serialport.node --module_name=serialport --module_path=/home/user/.node-red/node_modules/serialport/build/Release/node-v48-linux-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/home/user/.node-red/node_modules/serialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at emitTwo (events.js:106:13)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:886:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
node-pre-gyp ERR! System Linux 4.4.0-72-generic
node-pre-gyp ERR! command "/usr/bin/nodejs" "/home/user/.node-red/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /home/user/.node-red/node_modules/serialport
node-pre-gyp ERR! node -v v6.10.3
node-pre-gyp ERR! node-pre-gyp -v v0.6.18
node-pre-gyp ERR! not ok
Failed to execute '/usr/bin/nodejs /home/user/.node-red/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/user/.node-red/node_modules/serialport/build/Release/node-v48-linux-x64/serialport.node --module_name=serialport --module_path=/home/user/.node-red/node_modules/serialport/build/Release/node-v48-linux-x64' (1)
/home/user/.node-red
└──<EMAIL_ADDRESS>
npm WARN enoent ENOENT: no such file or directory, open '/home/user/.node-red/package.json'
npm WARN .node-red No description
npm WARN .node-red No repository field.
npm WARN .node-red No README data
npm WARN .node-red No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/bcrypt):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/bufferutil):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/serialport):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

I fixed .node-gyp/ ownership error but still get many.


[3.2.2] Fix incorrect initialize notification in language server

Fixes #38766
This PR fixes the currently incorrect initialize notification sent by the language server to accurately reflect the capabilities of the server.  Additionally, I have added a minor improvement to the JSONRPC module's error reporting to improve the quality of later bug reports related to the language server.

Thanks!

Cherry-picked for the master branch as 3d09edeaef7274af1a794d2933ddde383be60578 and 6815bf42b38c7c3dfde419d86dbc1bf012b035b2.

The errors still persist for me.


feat(user-agent): add custom header User-Agent to AWS SDK requests

Issue number: #2284
Summary
Implement standard user-agent in Powertools
Changes

AWS SDK request created by/with Powertools will include standard powertools user-agent string
Feature specific user-agent added for idempotency and parameters feature

User experience

UX is not affect by this change

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[x] Meet tenets criteria
[x] I have performed a self-review of this change
[x] Changes have been tested
[ ] Changes are documented -> Document after review finalized
[x] PR title follows conventional commit semantics

Is this a breaking change?
**RFC issue number**:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Codecov Report
Patch coverage: 74.46% and project coverage change: -0.15 :warning:

Comparison is base (099487e) 97.46% compared to head (6404ee2) 97.31%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2267      +/-   ##
===========================================
- Coverage    97.46%   97.31%   -0.15%
===========================================
  Files          149      150       +1
  Lines         6894     6936      +42
  Branches       492      494       +2
===========================================
+ Hits          6719     6750      +31
- Misses         137      147      +10
- Partials        38       39       +1

Impacted Files
Coverage Δ

aws_lambda_powertools/shared/user_agent.py
64.70% <64.70%> (ø)

aws_lambda_powertools/__init__.py
100.00% <100.00%> (ø)

...ools/utilities/idempotency/persistence/dynamodb.py
100.00% <100.00%> (ø)

aws_lambda_powertools/utilities/parameters/base.py
99.15% <100.00%> (+0.04%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Hi @heitorlessa! After some hard work and efforts put into research, PoC, and exhaustive tests done by Roger and me, I think we need one last review from you on this PR before the merge.
Thanks for all the effort @roger-zhangg!

Hey Heitor,
Thanks for this detailed review. I've updated all files related to your comments. Please check.
Thanks!
Roger

Just missing this additional area for user-agent:

awslabs.github.io/aws-lambda-powertools-python/2.15.0/utilities/data_classes/#codepipeline-job

Code: develop/aws_lambda_powertools/utilities/data_classes/code_pipeline_job_event.py#L206

Thank you for indicating this area @heitorlessa! I Didn't remember we made life easier to get objects from S3 when using CodePipelineJob :)


Add FledgePower detailed and realization view

@Laurentjg made and suggests the following changes to the detailed and realization view of FledgePower:

Updated OperatorFabric realization view based on actual state of github.com/opfab
Redefined the application function "Alarm management" as a specific form of event management
Added application components to OperatorFabric and Generic Application Components
Added business functions to Operatorfabric
Positioned Let's Coordinate as application components and application function related to it.

The updated view will be discussed and reviewed during 8 March meeting with the FedgePower team.


Incorporate the updated Adapter changes for EcmaScriptVersion,W3CDomVersion, CallBack

Once this https://github.com/dotnet/systemweb-adapters/pull/404 is merged and version is updated, bring it back to this project.

this is available


[dependabot] use v2 dependabot, and set tags for docker images we build.

Motivation
Use newer version of dependabot with gha/docker/cargo support
Pin docker images with sha256 digests.
Have you read the [Contributing Guidelines on pull requests]
Yes
Test Plan
CI
Related PRs
None

also pinned the docker image to last month's release so we get a pr to update it.
gha check will also result in an update.

/land

:broken_heart: Test Failed - Build images and run cluster test

/land

:broken_heart: Test Failed - Build images and run cluster test

/land

/land

@rexhoffman :bulb: This PR is already queued for landing


[Compaction] Fix NPE when TTL_UPDATE has not prior PUT

This PR would fix a NPE caused by TTL_UPDATE index value having no PUT index value before. This case could happen when the PUT and TTL_UPDATE don't belong to the same log segment, but PUT's log segment is compacted and PUT is gone, while TTL_UPDATE is still there.

Codecov Report

Merging #1909 (38e5c47) into master (cdcb57d) will decrease coverage by 58.49%.
The diff coverage is 100.00%.

:exclamation: Current head 38e5c47 differs from pull request most recent head 82c0b0c. Consider uploading reports for the commit 82c0b0c to get more accurate results

@@              Coverage Diff              @@
##             master    #1909       +/-   ##
=============================================
- Coverage     73.97%   15.47%   -58.50%
+ Complexity     9674     2283     -7391
=============================================
  Files           690      690
  Lines         53129    53132        +3
  Branches       6619     6620        +1
=============================================
- Hits          39300     8222    -31078
- Misses        11766    44433    +32667
+ Partials       2063      477     -1586

Impacted Files
Coverage Δ

...ava/com/github/ambry/store/BlobStoreCompactor.java
87.16% <100.00%> (+0.04%)
:arrow_up:

.../src/main/java/com/github/ambry/router/Router.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../src/main/java/com/github/ambry/store/Message.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/named/PutResult.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/quota/QuotaMode.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/quota/QuotaName.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...rc/main/java/com/github/ambry/rest/RestMethod.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...c/main/java/com/github/ambry/config/KMSConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...c/main/java/com/github/ambry/config/SSLConfig.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...c/main/java/com/github/ambry/router/ByteRange.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 540 more

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 cdcb57d...82c0b0c. Read the comment docs.


⚠ Bofrost.be has degraded performance

In c539521, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2002 ms

Resolved: Bofrost.be performance has improved in 85e6403.


Crash if loading world

What you were trying to do
I tried to load ANY world
What actually happened
The Client closed, the server was still running.
How to reproduce

start the game
load any world
when the healthboxes do appear it crashes

Log details and game version
https://pastebin.com/Ebnjwitq
Computer details
Ubuntu 17.10, Processos: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4 Graphics:  GeForce GTX 1050 Ti/PCIe/SSE2 Desktop: GNOME 3.26.2

It crashes at all servers. I'm using Version "v1.6.0 - Alpha 9"

Apologies on the delay in responding to this.
Hmm. This is odd, there's nothing I can see in the log that indicates the cause of the crash. Is this log from the server or from the client?
Additionally can you try and load a new world with no modules except Core enabled.

One potential clue: Java 9. We haven't done a lot of testing on it. Alternatively the ~princess could be in another castle~ error could be in another log file

It's the log from the crash reporter...

Closed because I fixed it a long time ago by redownloading Terasology.


Terraform tool installer does not allow to specify specific download url

Hi team,
in some protected environments/networks it is not possible to access url like: https://releases.hashicorp.com/terraform/${version}/terraform_${version}_${platform}_${architecture}.zip
It would be very beneficial to enable users to specify url to their own Nexus/File Share/Storage Account.
IMHO, most simple way to achieve it would be to have environment variable or if-statement that will check if version starts with 'http'
Here is where code in question is located: https://github.com/microsoft/azure-pipelines-extensions/blob/5dd1dba15c474153c8b8d971c77959112f0b12a3/Extensions/Terraform/Src/Tasks/TerraformInstaller/src/terraform-installer.ts#L81
Regards,
Yury

@yakuramori If you already know the fix, please feel free to raise PR. We will be happy to review that :)

Hi @20shivangi  I would just add an environment variable there. Something like this before line 81:
if (process.env.TERRAFORM_EXTERNAL_URL_TO_ZIP) {
//maybe check for .zip
return process.env.TERRAFORM_EXTERNAL_URL_TO_ZIP
}
This way no need to add any extra checks, people should provide proper zip.

moving to new repo location


Add a Chatbot option

This will be helpful for user to ask anything  related to crypto currency if they want  to this chatbot. It will answer everything. Please assign this task to me with proper badge and level.

 This will be helpful for user to ask anything related to crypto currency if they want to this chatbot. It will answer everything. Please assign this task to me with proper badge and level.

Okay do it bro and all the best


null safety errors

we try to run app and when some errors in app then its not correct suggest thats whats line no have errors and whats type of variables is not correct and suggetions whats to to change with others means others hand solution to wrap with  this this this and null safety have a big problem also With Rxint have a 2 day to solve an issue from group chats and from chat gpt but cannot solve i am disheart when want to store a values from getxcontroller class and read to a variable when make int its give errors RxInt and when RxInt its give int whats a joke also have some others stupped types of errors  but we write like a example thats you understand whats i say to fix i have try to flutter from 2020 but on this time can not handle some things to understand thats whats type of errors says and where have on line no and whats type of error and wich type of case whats to to better mens suggests but its not when runing app its run and in terminal have a different types of errors whith no suggetions causes and no of line its only says have errors but where ? because have thousends of lines and same others veriaables where to find where have issue whats do width where and plz make it with suggetions and clarifyng types off errors   @@@@ __ Plz make its with clarify thats whats where wrong with variables if null safet and where line no and whats type of variaable wrong with him and whats to do next suggetions and also ignord type of others hand solution plz i hope its will coverd soon as possible Step:2 make every widgets thats called with exmple when wrap or call its show a example in snippets box thats its this type and in wich this type of code can includes and next as you wish to change like future builder call its call completely with example and with simple types and also example like in box where shown becaus its take a time to finde example code thats whats type of variables and can be includeds and on google caht gpt its take half or more time to find an example but if in a box suddenly can understand with example thats whats its taked @@@@  best regards thank you for advance to do

Hi @HassanAmeer
The goal of this Github repo is not to give assistance on personal code or the whole package/plugin project, but to improve flutter reporting bugs or feature requests.
If you encounter behavior that you believe could be a bug, please try to provide all or some of the information indicated in the template so that we can address this issue properly. Please follow the provided format so that the issue is clear to others as well.

Issue Template
If you are looking for support, please check out our documentation
or consider asking a question on Stack Overflow:
- https://flutter.dev/
- https://api.flutter.dev/
- https://stackoverflow.com/questions/tagged/flutter?sort=frequent

If you have found a bug or if our documentation doesn't have an answer
to what you're looking for, then fill our the template below. Please read
our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports

Steps to Reproduce

Please tell us exactly how to reproduce the problem you are running into.

Please attach a small application (ideally just one main.dart file) that
reproduces the problem. You could use https://gist.github.com/ for this.

If the problem is with your application's rendering, then please attach
a screenshot and explain what the problem is.

1. ...
2. ...
3. ...

Please tell us which target platform(s) the problem occurs (Android / iOS / Web / macOS / Linux / Windows)
Which target OS version, for Web, browser, is the test system running?
Does the problem occur on emulator/simulator as well as on physical devices?

Target Platform:
Target OS version/browser:
Devices:

Run your application with `flutter run --verbose` and attach all the
log output below between the lines with the backticks. If there is an
exception, please see if the error message includes enough information
to explain how to solve the issue.

Run `flutter analyze` and attach any output of that command below.
If there are any analysis errors, try resolving them before filing this issue.

Finally, paste the output of running `flutter doctor -v` here.

Instead, if you think that the issue might depend on your implementation, please see flutter's community for resources and ask questions like this. You may also get some help if you post it on Stack Overflow and flutterhelp.
Thank you!


Collaboration with other screen filter apps

Hi, just making this in case you have mention notifications off and didn't see https://github.com/LibreShift/red-moon/issues/222. If you saw it but haven't gotten a chance to respond yet, sorry for another notification.
By the way, "I'm not interested" is a fine response, although I hope you will be :)

I am sorry I completely missed out this. I would gladly like to collaborate.


Stripe Elements? 2

Hello there!
I check this issue and seems like the problem hasn't been answered properly here (https://github.com/fuentesloic/nuxt-stripe/issues/21) so I'm re-posting with my issue here...
I'm getting the same error both onNuxtReady or onMounted
Has anyone solved this?
It will be much appreciated if I can get a help on this
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'elements')
const stripe = await useClientStripe() as Stripe
const elements = ref<StripeElements | undefined>()

const collectAddress = async () => {
  const addressElement = elements.value?.getElement('address')
  if (addressElement) {
    const { complete, value } = await addressElement.getValue()
    if (complete) {
    // completed logic here

    }
  }
}
const init = async () => {
  const options = {
    mode: 'setup',
    currency: 'jpy',
  }

  elements.value = await stripe.value.elements(options)
  const addressElement = elements?.value?.create('address', {
    mode: 'billing',
  })

  addressElement?.mount('#payment-element')
}

onNuxtReady(async () => {
  await init()
})

hey @azoom-sidonie-abe sure can you provide me again stripe element documentation I will have a look next week

Hi @flozero
Sorry to bother you and I appreciate for your help!
Is it his one below that you are looking for?
https://docs.stripe.com/js/elements_object/create

No worry if something its not clear we can try to help. I think so I will have a look next week or this weekend If I can. Hope the timeline will be good for you

Hi @flozero , I hope you had a nice weekend!
Any luck with this one by any chance?

hey sorry no. Will try this weekend

Thank you!
My company is actually planning on launching next week so it will be much appreciated if I can get this solved....!

Hi, any updates here ?
I'm having a : "TypeError: stripe.elements is not a function". Should I add the v3 script in the head ?
<script setup lang="ts">
  import type {
    Stripe,
    StripeElements,
    StripePaymentElement,
  } from '@stripe/stripe-js'

  const user = useUserStore().getUser()
  const plan = useCartStore().getSelectedPlan()

  const stripe = (await useClientStripe()) as Stripe
  const elements = ref<StripeElements | undefined>()
  const paymentElement = ref<StripePaymentElement | undefined>()

  const res = await $fetch<{
    subscriptionId: string
    clientSecret: string
  }>('/api/billing/newSubscription', {
    method: 'POST',
    body: {
      customerId: user.value?.stripeCustomerId,
      priceId: plan.value?,
    },
  })

  onMounted(async () => {
    if (stripe) {
      elements.value = stripe.elements({
        clientSecret: res.clientSecret,
      })
      paymentElement.value = elements.value.create('payment')
      paymentElement.value.mount('#payment-element')
    }
  })
</script>

hey @azoom-sidonie-abe sorry for the long time between you demands and the example.
I believe this https://github.com/flozero/nuxt-stripe/pull/40 is going to solve your problem. Once merged and published its going to close this one. Feel free to re open if its not answering you issue
Also don't hesitate to validate the implementation.


Need to create Wiki or other docs on Testing

FYI -- the messages you get from react_on_rails when you open up the failed test from Capybara are not relevant generally, because the application.js is not loaded, so then you get other messages.
We need to put this information in a wiki, but it's not clear how to add images to a github wiki right now, so this is just a placeholder.

@justin808 is this still relevant or can we close?


Any().such_that()

PR to address issue #10 .
From that issue:
I would like to use mockextras in all my testing, but first I would like to add a couple of features I see as very generic and useful to everyone, if you agree.  The first on my wishlist is the ability to specify arbitrary predicates to an Any matcher.
loud_short_string = (
    Any(str)
    .such_that(lambda s: len(s) < 6)
    .such_that(lambda s: s.upper() == s)
)
assert loud_short_string == "HEY"

positive_int = Any(int).such_that(lambda x: x > 0)
assert positive_int != -2

My solution is tested and I think it fits in with the rest of the fluent interface.  I'm happy to battle-harden it in the real world for a time, too, since I just finished the feature.

Coverage increased (+0.2%) to 96.992% when pulling 4a75cab30ff38049000ac9f1c79f77e8b80d49c9 on Jdsleppy:jdsleppy/such-that into 86e5c218b97b31348521fa7b9018234e7ea5744f on manahl:master.

Coverage increased (+0.1%) to 96.947% when pulling 9188e17034fb418e08b3264638da18806872a2da on Jdsleppy:jdsleppy/such-that into 86e5c218b97b31348521fa7b9018234e7ea5744f on manahl:master.

Coverage increased (+0.1%) to 96.947% when pulling fa4d5493d3148c52bff44c9141f8e850fec6ca04 on Jdsleppy:jdsleppy/such-that into 86e5c218b97b31348521fa7b9018234e7ea5744f on manahl:master.

Good points, I made those changes.  Let me know if there's anything else you see, or have thoughts on that parametrized test.